Writing Doesn’t Just Communicate Strategy. It Coordinates It.

Most organizations treat writing as the thing that happens after thinking. You develop the strategy, run the meetings, make the decisions — and then someone writes it up. A summary. A memo. A brief. A Confluence page that no one visits after the first week.

That model is broken, and most teams don't realize it until the damage is already done. This article makes the case that writing is not the record of strategic alignment — it is the mechanism that produces it. Get that distinction wrong and you will spend enormous amounts of time issuing corrections, rescoping projects, and re-explaining decisions that should have been settled the first time. Get it right, and something strange happens: your team starts moving in the same direction without you pushing.

Key Takeaways

• Writing is commonly treated as a communication tool, but its more powerful function is coordination — creating shared understanding across people who were not in the same room, the same meeting, or the same headspace.
• Most organizational misalignment is not a strategy problem. It is a writing problem disguised as one.
• The shift toward distributed and asynchronous work has made writing quality a direct operational variable, not a soft skill.
• Companies like Amazon have institutionalized writing as a thinking and coordination tool, producing measurable improvements in decision quality and meeting productivity.
• Writing for coordination requires a different set of instincts than writing for communication — and the difference is learnable.

The Classic Idea: Writing Is How Strategy Gets Shared

The traditional view goes something like this: leadership sets direction, strategy gets articulated in a document, that document travels through the organization, and people read it and proceed accordingly.

It is a logical picture. It is also, in practice, largely fictional.

The assumption buried in that model is that strategy is already complete by the time writing enters the scene. That the thinking is done, the decisions are locked, and writing is just the vessel. Under this view, a well-written strategy document is roughly equivalent to a well-labeled filing cabinet — useful for retrieval, neutral on outcome.

This is where most organizations stop asking questions.

What Everyone Gets Wrong About Writing and Strategy

Here is the distinction that changes everything: communication transmits information from one person to another. Coordination creates shared models of reality across multiple people simultaneously.

Those are not the same thing, and treating them as equivalent is how organizations produce documents that are technically clear but operationally useless.

A communication document says: here is what we decided. A coordination document says: here is how we think about the problem, what we believe to be true, what we are uncertain about, and what will count as success. One announces. The other calibrates.

The misunderstanding runs deeper than format. Most people believe that if they write something clearly, the reader will understand it correctly. But understanding something correctly is not the same as understanding it the way you do. Two people can read the same sentence about a "customer-first approach" and walk away with genuinely different working definitions of what that means in practice. The writing communicated, but it did not coordinate.

According to the Axios HQ State of Internal Communications Report, 80% of leaders believe their internal communications are clear and engaging — while only 50% of employees agree with them. That is a 30-point gap between what leaders think they are producing and what is actually landing. And it gets more striking: 27% of leaders believe their staff are entirely aligned with business goals, but only 9% of employees agree.

These numbers are not evidence of lazy employees or careless leaders. They are evidence of a coordination failure dressed up as a communication success.

What Changed: Writing Is Now the Work Itself

For most of corporate history, misalignment was correctable through proximity. People sat near each other. Confusion surfaced in hallways. Gaps got closed over lunch. The written word was important, but it existed alongside a thick web of informal, real-time contact that did a lot of invisible coordination work.

That web has thinned considerably in many organizations.

Distributed teams, asynchronous workflows, and remote-first cultures have shifted the center of gravity. Written communication is no longer a complement to in-person interaction. For many teams, it is the primary interaction. Slack messages, project briefs, strategy docs, comment threads, async updates — these are not supplements to the work. In many organizations, they are the work. And that changes the stakes considerably.

The volume of written output in organizations has increased substantially while the average quality of that writing has not kept pace. A 2016 survey by Josh Bernoff found that 81% of businesspeople reported that poorly written material wastes a significant amount of their time, and that American businesses spend 6% of total wages simply working to extract meaning from unclear writing. The total estimated cost was $396 billion.

Those figures come from a moment when distributed work was still the exception. Extend that logic into an organization where text is the dominant coordination surface and the numbers compound quickly.

What the Shift Looks Like at Scale

The organizations that have grasped this have made structural changes to how writing functions in their operations. Amazon is the most cited example, and it is worth examining seriously rather than treating as a piece of startup mythology.

In 2004, Jeff Bezos banned PowerPoint from executive meetings at Amazon. In its place, leaders were required to produce a six-page narrative memo before any significant decision meeting. These memos are not distributed in advance and then discussed. Meetings begin with 20 to 30 minutes of silent reading — every participant goes through the memo in full before a single word is spoken.

The rationale was not stylistic preference. The argument, as Bezos has explained in several shareholder letters, is that slide decks allow people to present without actually thinking. Bullet points can obscure gaps in logic that complete sentences cannot hide. Writing a coherent narrative memo forces the author to work through the argument before anyone has to sit in a room with it.

What Amazon recognized is that the act of writing is itself a form of strategic coordination. The memo does not just communicate a recommendation — it creates a shared cognitive surface. Everyone reads the same document, follows the same argument, encounters the same evidence. By the time discussion begins, the group is operating from a common understanding rather than assembling one in real time.

The result is meetings that are, by most accounts, substantively better. Not because the writing is elegant, but because it does coordination work that conversation alone cannot replicate at speed.

What This Means Operationally

So what does it actually mean to write for coordination rather than communication?

The practical difference is less about format and more about intent. Writing for communication asks: have I transmitted the information? Writing for coordination asks: have I created the conditions for someone to think the way I need them to think?

That second question is harder. It requires the writer to hold the reader's cognitive state in mind while writing, not just the information to be conveyed. It requires acknowledging uncertainty, naming assumptions, and explaining the reasoning behind conclusions rather than just announcing them.

Here is a useful table contrasting the two modes:

The difference shows up in small choices. A communication document says "we are moving to a quarterly release cycle." A coordination document says "we are moving to a quarterly release cycle because our current monthly cadence is creating integration costs that outweigh the speed benefit — if you disagree with that premise, we need to hear it before this takes effect."

The second version is longer. It is also much harder to misapply.

The Axios HQ data shows that organizations which increased investment in internal communications were 68% more likely to see better alignment with business goals than those that held investment flat or reduced it. That correlation is not accidental. The investment signal points to organizations that have started treating writing as infrastructure rather than overhead.

Three Shifts That Make Writing Coordinate

Write for the person who was not in the room. The most common failure in organizational writing is that it assumes context that only meeting participants possess. A decision that seemed obvious in the room becomes cryptic in the document because the reasoning was verbal. Writing that coordinates has to carry its own context.

Name the assumptions, not just the conclusions. Ambiguity in strategy writing does not usually appear as obviously vague language. It appears as confident-sounding conclusions that rest on unstated premises. Two team members can read "we will focus on enterprise customers" and have completely different working definitions of what "enterprise" means. Coordination writing surfaces those definitions early.

Write to expose disagreement before it becomes a problem. One of the least appreciated functions of a well-written strategy document is that it invites challenge. If a document presents a recommendation alongside its full reasoning, skeptical readers have something to push against. Documents that only state conclusions prevent disagreement from surfacing at all — until it surfaces in execution, which is the worst possible time.

The cost of getting this wrong is not abstract. According to the Axios HQ report, a single employee earning between $50,000 and $100,000 loses more than 35 working days per year to ineffective communication. For senior employees earning above $200,000, the annual cost per person reaches $54,860. Multiply that across an organization and misalignment stops being a soft culture issue and starts looking like a capital allocation problem.

Writing Is the Coordination Infrastructure Most Organizations Have Not Built

Strategy rarely fails in the articulation. It fails in the translation — the gap between what the leadership team understood when they made a decision and what everyone else understood when they read about it.

Writing that coordinates is not about eloquence or even clarity in the conventional sense. It is about building documents that create the same working model of reality in multiple people's minds simultaneously, accounting for the fact that those people are coming from different positions, contexts, and interpretations.

That is a higher bar than most organizational writing currently clears. But it is a learnable skill, and the organizations that treat it as a core operational competency tend to move with a coherence that their competitors cannot easily replicate.

Start by asking a different question. Not "did I communicate this clearly?" but "after reading this, will someone understand the problem the way I do?" The distance between those two questions is where most organizational misalignment lives.

Frequently Asked Questions

What is the difference between writing for communication and writing for coordination?

Writing for communication focuses on transmitting information from one person to another — announcing decisions, updating stakeholders, or reporting status. Writing for coordination creates shared understanding across multiple people who may have different contexts, assumptions, or interpretations. Coordination writing shows reasoning, names uncertainty, and creates a common cognitive surface. Communication writing states conclusions. Both have their place, but most organizations default to communication writing even in situations that require coordination.

Why does poor organizational writing cause misalignment, not just confusion?

Confusion is temporary. Misalignment is when people understand a document differently and then act on those different understandings. The damage accumulates over time as decisions, projects, and priorities diverge without anyone realizing the divergence started in a document. Research from the Axios HQ State of Internal Communications Report found that only 9% of employees feel fully aligned with their organization's business goals, while 27% of leaders believe their staff are. That gap is not primarily a strategy problem. It is a writing problem.

How did Amazon use writing as a coordination tool?

Amazon under Jeff Bezos replaced PowerPoint with six-page narrative memos for executive meetings. These memos are read silently at the start of each meeting, giving all participants 20 to 30 minutes to engage with the full argument before discussion begins. The practice forces the author to develop complete reasoning on paper before presenting it, and it ensures the group shares a common understanding before the conversation starts. The result is meetings that are more substantive and decisions that are better examined before they are made.

What does it cost an organization to have poor written communication?

According to research by Josh Bernoff, American businesses spend approximately 6% of total wages just trying to extract meaning from poorly written material, with an estimated total cost of $396 billion. The Axios HQ State of Internal Communications Report found that employees earning between $50,000 and $100,000 lose more than 35 working days per year to ineffective communication, equivalent to approximately $10,140 in lost salary per employee annually. For senior employees earning above $200,000, the annual cost reaches $54,860 per person.

Can writing for coordination be applied to all types of organizational writing?

Not every document needs to function as a full coordination artifact. Status updates, factual announcements, and logistical communications can remain efficient and brief. Coordination writing is most valuable for decisions that involve multiple stakeholders, strategic direction, or anything where different people operating from different contexts need to reach a shared understanding. The test is simple: if someone acting on this document could plausibly do something you did not intend, the document needs to coordinate, not just communicate.

Is this a writing skill problem or a process problem?

Both, and treating it as only one tends to produce incomplete fixes. Writing quality matters, but even skilled writers produce misalignment-generating documents when the process assumes that communication is sufficient. The most effective organizational change combines better individual writing practices — showing reasoning, naming assumptions, writing for the person who was not in the room — with process changes that build coordination documents into how decisions actually get made and transmitted.