When Process Replaces Purpose

A Document Covered in Comments

A document may take only a few hours to write and several weeks to approve. This is so common in large organizations that people rarely stop to question it. The first draft may already be clear, accurate, and suitable for its audience. Yet once it enters the review process, it begins a long journey through departments, managers, specialists, regional teams, legal reviewers, and communication professionals. By the time it returns to its owner, the Word file is covered in comments, tracked changes, replies, reopened threads, and minor disputes over individual words.

Many of those involved are acting in good faith. They believe that careful review is part of their responsibility. They want to protect accuracy, consistency, reputation, and organizational interests. Still, there is often another pressure at work. A reviewer who simply writes “approved” may feel that they have contributed very little. A reviewer who adds several comments appears attentive, knowledgeable, and necessary. Even when this motive is not conscious, the review process rewards visible intervention more than disciplined restraint.

This is how review theater begins. The activity of reviewing becomes a performance of professional value. A minor suggestion may be framed as an important clarification. A stylistic preference may be presented as a necessary correction. A reviewer changes a phrase, another reviewer restores the original wording, and the document owner is expected to reconcile both positions. Each comment appears small in isolation, but their cumulative cost can be considerable.

The burden is also distributed unevenly. It may take a reviewer thirty seconds to leave a comment, but the owner may spend twenty minutes interpreting it, checking the context, revising the text, explaining the decision, and confirming that the change does not create a contradiction elsewhere. The reviewer sees one local concern. The owner must protect the coherence of the whole.

Applications such as Microsoft Word did not create this behavior, but they make it easy to sustain. Commenting is effortless, visible, and attributable. Every intervention remains on the page as evidence that someone participated. Approval without revision, by contrast, leaves almost nothing behind. The technology quietly favors modification over restraint.

The result is often a strange form of deterioration. The document becomes safer, more qualified, and more acceptable to everyone involved. Yet it may also become less direct, less readable, and less alive. Nothing is clearly wrong with it, but little remains that anyone would naturally want to say.

When Every Perspective Is Reasonable

The deeper problem is not that reviewers lack intelligence. It is that each person sees the document from a limited position. Legal focuses on liability. Brand teams focus on approved terminology. Product specialists focus on technical accuracy. Regional teams focus on local relevance. Executives focus on strategic positioning. Editors focus on language and consistency.

Each perspective can be legitimate. In fact, each reviewer may be correct within the boundaries of their own responsibility. The difficulty arises when all those local corrections are added together without a strong center capable of judging their effect on the whole.

A technical specialist may add precision but weaken readability. A legal reviewer may reduce risk but also reduce clarity. A brand reviewer may replace natural language with official vocabulary that no ordinary person would use. A regional team may add a detail that matters locally but distracts from the central message. Every intervention can be defended separately, while the combined result becomes crowded and uncertain.

This is a familiar form of local optimization. Every participant improves the document according to one criterion, but the document as a whole becomes worse. The same pattern appears in software development, corporate governance, product design, public policy, and many other fields. Each part of the system is improved according to its own metric, while the total system becomes slower, more complicated, and less coherent.

Collective review is often presented as collective intelligence, but that description is not always accurate. What emerges may be a collection of fragments rather than a synthesis. Many people contribute knowledge, but very few hold the entire work in mind. The owner may be the only person who understands the intended argument, audience, tone, proportion, and purpose.

This creates a mismatch between authority and responsibility. Reviewers have the authority to demand changes, but the owner remains responsible for integrating them. Many people can delay the document, while one person must eventually make it whole. Those who add comments do not always bear the consequences of the complexity they create.

The document can therefore become strangely ownerless. It began with one purpose, but it ends as a negotiated object designed mainly to avoid objection. It no longer expresses a clear mind or intention. It represents an agreement among people who may have been trying not to be blamed.

That is why many corporate documents feel anonymous. They do not sound as though they were written by a person because, in an important sense, they were not. They were assembled through a process in which individuality, commitment, and directness were gradually removed.

The Organization Becomes Busy

The same pattern extends far beyond documents. Large organizations divide work because specialization is necessary. No single person can understand every technical, legal, financial, operational, and regional issue. Yet specialization also divides perception. People see the organization through their own roles, systems, targets, and responsibilities.

Each person tries to contribute in a responsible way. Legal adds safeguards. Finance adds controls. Marketing adds campaigns. Human resources adds procedures. Managers add oversight. Regional teams add local requirements. Project teams add trackers and progress updates. None of these additions is irrational by itself, but the organization gradually becomes dense with well-intentioned activity.

As complexity grows, more coordination is required. Meetings are created to connect departments. Reports are prepared for those meetings. Slide decks are created to summarize the reports. Action trackers are created to record the decisions. Follow-up meetings are arranged to review the trackers. Additional presentations are requested to explain why progress is slower than expected.

The tools intended to support work gradually become the work.

This is a form of coordination inflation. More participants require more communication, and more communication requires more processes. Those processes require people to manage them, and the new roles generate further reporting and review. Complexity creates activity, and the activity creates additional complexity.

Everyone feels busy because everyone is genuinely doing something. Emails are answered, comments are resolved, meetings are attended, presentations are prepared, and dashboards are updated. Yet the organization as a whole may not be moving very far. The volume of activity grows faster than the quality of the result.

This is one reason large corporations often feel scattered. Every person brings a direction, concern, or priority. Without a strong integrating principle, those directions do not combine into a coherent movement. They pull against one another. The organization becomes highly active and strangely slow at the same time.

The concept of “bullshit jobs” is often associated with positions that appear to have little social value. Yet there may be a more common condition inside otherwise necessary jobs. Many people hold roles that are genuinely important, but much of their working time is consumed by tasks that exist mainly because the organization has created a need to communicate with itself.

A manager may lead a valuable team but spend most of the week producing reports for other managers. A communication professional may have real expertise but spend days reconciling minor wording preferences. A project owner may understand the problem but spend more time updating trackers than solving it.

The job is not necessarily meaningless. The structure surrounding it may be.

The Fatigue of Participation

This condition becomes especially visible at the management level. Managers often spend their days moving from one meeting to another. They attend to represent their teams, maintain visibility, provide updates, hear concerns, show alignment, and avoid being excluded from decisions.

A full calendar creates a persuasive sense of productivity. The manager has listened, spoken, advised, clarified, and participated. At the end of the day, however, it may be difficult to identify what was completed. Many ideas were exchanged, but few decisions were made. Several concerns were raised, but the original problem remains.

The feeling of exhaustion is real. Meetings demand attention, social judgment, emotional control, and rapid changes of context. A person may move from a budget discussion to a personnel issue, then to a technical review, followed by a regional update and an executive presentation. Each meeting requires a different vocabulary, a different set of relationships, and a different form of self-presentation.

This repeated switching consumes energy. The mind remains active, but it is rarely allowed to stay with one problem long enough to produce something complete. The person spends the day exercising judgment without turning that judgment into a finished result.

This creates a peculiar combination: genuine fatigue and an uncertain sense of accomplishment. The calendar was full, so the day feels substantial. Yet busyness has become a substitute for completion.

Meetings are supposed to integrate fragmented organizations. Sometimes they do. A good meeting brings together knowledge that cannot be combined asynchronously. It resolves a question, clarifies responsibility, or allows a decision to be made. Yet many meetings serve another purpose. They display participation. They reassure stakeholders that they were included. They protect people from being blamed for not being present.

Attendance becomes defensive. A manager joins not because their contribution is essential, but because absence may later be interpreted as indifference or lack of alignment. The meeting continues because nobody wants to be the person who says it is unnecessary.

This is another form of theater. Presence becomes evidence of commitment, discussion becomes evidence of progress, and minutes become evidence that something happened.

The deeper source of exhaustion is often not the amount of work but the loss of agency. People remain responsible for outcomes they cannot fully control. They are expected to influence many processes but are not allowed to conclude them. Decisions pass through committees, reporting lines, and approval systems. The person is involved enough to feel pressure, but not empowered enough to bring the work to completion.

Responsibility without authorship is a powerful source of burnout. It asks people to care deeply while denying them the authority needed to act decisively.

Why Solitary Work Feels Different

This may explain why solitary writing can feel so satisfying, even when it requires serious effort. Writing an essay alone is not easy. It demands concentration, judgment, revision, and patience. Yet ownership, responsibility, and purpose remain connected.

The writer holds the whole work in mind. The argument, structure, tone, emphasis, and conclusion belong to one continuous intention. When a paragraph is revised, the revision serves the same larger purpose. The work may change many times, but it remains centered.

This unified intentionality creates a sense of authorship. The writer knows what the work is trying to become and has the authority to decide when it has reached that form. There is no need to satisfy unrelated interests or preserve every possible perspective.

Even collaboration can support this kind of authorship when it respects the center of the work. A good editor may identify a weakness. A knowledgeable reader may catch an error. A thoughtful interlocutor may reveal a neglected perspective. These contributions strengthen the work when they help the author see more clearly.

The problem begins when collaboration loses its relationship to a shared purpose. Each participant then adds something from their own position, and the work becomes a container for accumulated concerns. The objective shifts from expressing something clearly to ensuring that every stakeholder has been represented.

This is why press releases often become dull. They may begin with a recognizable idea or voice. Then the reviews begin. One person softens a claim. Another adds a qualification. Someone replaces a direct sentence with approved terminology. Another person inserts a message from a separate initiative. Each addition appears reasonable, but the original energy gradually disappears.

The final document may be accurate and safe, yet it sounds as though nobody truly believes it. It has been de-authored.

Strong writing requires selection. It must decide what matters, what can be left out, and what should be said directly. It requires a certain amount of risk because every clear statement excludes alternatives. Bureaucratic collaboration resists that kind of selection. It tries to include every concern, protect every interest, and avoid every possible objection.

The result is not necessarily false. It is simply lifeless.

The contrast between solitary writing and organizational communication reveals something important. Meaningful work requires not only intelligence and effort but also a center of responsibility. Without that center, collaboration may increase participation while reducing coherence.

Two Meanings of Slowness

There are two very different forms of slowness hidden inside these experiences.

The first is deliberate slowness. This is the slowness of mindfulness, reflection, deep work, and careful judgment. A person chooses to slow down because the work deserves attention. Time is used to read closely, think fully, revise meaningfully, or allow an idea to mature.

Deliberate slowness may appear inefficient from the outside. Someone may spend hours on a single page or sit quietly without producing visible output. Yet the time is not empty. It is deepening the work.

This kind of slowness preserves agency. The person understands why the work requires time and can see how the time contributes to the result. The pace may be unhurried, but the direction remains clear.

Organizational slowness is different. It is imposed by dependencies, waiting, repeated reviews, unclear authority, conflicting interests, and unnecessary procedures. The work does not move slowly because it requires depth. It moves slowly because the system cannot decide.

A press release that takes three weeks to approve is not necessarily being treated with greater care. It may simply be trapped inside a structure where many people can delay it and few people can conclude it.

The distinction is simple but important. Deliberate slowness gives important work enough time. Organizational slowness takes time away from the work.

One produces sustained attention. The other produces interruption, waiting, repetition, and dependency.

The emotional effects are also different. Deliberate slowness can be tiring, but it is often satisfying. At the end of the effort, something has deepened or taken shape. Organizational slowness produces a more confusing fatigue. Time has passed, energy has been spent, but the work itself may be almost unchanged.

This is fatigue without completion.

Modern organizations often confuse the two forms. Quiet thinking may appear unproductive because it creates little visible activity. Bureaucratic delay may appear responsible because it produces comments, meetings, records, and approvals.

Productive slowness becomes suspicious, while unproductive slowness becomes institutionalized.

A healthy organization would protect deliberate slowness and reduce organizational slowness. It would give people time to think while removing the processes that prevent them from acting.

AI and the Possibility of Simpler Work

AI may help address some of these problems, but its effect will depend on how it is used.

AI can already perform many of the tasks that support bureaucratic processes. It can compare versions of a document, group duplicate comments, identify contradictory suggestions, distinguish substantive changes from stylistic preferences, summarize meetings, extract decisions, check terminology, and prepare first drafts.

Used carefully, it could reduce the burden of coordination. It could help reviewers focus on genuine risks rather than cosmetic changes. It could show that several comments are saying the same thing. It could reveal that a meeting produced no decision or that a report is being created for an audience that rarely reads it.

AI could also help organizations observe themselves. It could identify projects with excessive approval cycles, meetings that repeatedly revisit the same issue, teams producing similar dashboards, and documents that spend most of their life waiting for review.

People inside organizations often experience these problems one task at a time. AI may be able to show the larger pattern.

Yet the same technology could easily make the situation worse. AI can generate reports, slide decks, summaries, comments, recommendations, and alternative drafts almost without limit. Because production becomes cheap, organizations may demand more of everything.

Instead of eliminating the weekly report, AI may produce a longer report. Instead of reducing reviewer comments, AI may generate dozens of possible concerns. Instead of cancelling meetings, AI may create more detailed agendas and minutes for meetings that never needed to occur.

Automated review theater is still review theater.

The decisive question is whether AI is used to perform unnecessary processes more efficiently or to question why those processes exist.

A weak use of AI automates the weekly slide deck. A stronger use asks whether the deck is needed.

A weak use drafts responses to every reviewer comment. A stronger use asks why so many people are reviewing the document.

A weak use makes bureaucracy faster. A stronger use makes bureaucracy smaller.

Technology alone cannot decide who should lose approval authority, which meetings should be cancelled, or who must accept responsibility for the final decision. These are structural and political questions. Every process has defenders, beneficiaries, and historical reasons for existing.

AI may reveal the irrationality, but leadership must still be willing to act on what becomes visible.

The deeper remedy remains clear ownership, limited veto points, proportional review, and permission to exercise judgment. A reviewer should be able to say, “No changes needed,” without appearing unhelpful. A manager should be able to cancel a meeting without appearing disengaged. A document owner should be able to reject comments that do not materially improve the work.

The goal is not speed for its own sake. Some work deserves time. Important thinking cannot always be hurried, and careful judgment should not be confused with inefficiency.

What should be protected is the slowness that allows attention to deepen. What should be removed is the slowness that prevents work from becoming whole.

When process serves purpose, coordination can strengthen human effort. When process replaces purpose, everyone becomes busy and the work quietly disappears. The challenge for organizations, especially in the age of AI, is to recover the difference.

Photo by Zdeněk Macháček on Unsplash