The Memo Is the Broth: How Strategy Becomes Personal

The most overlooked fact about communication is that people are always making a private meal out of public information

What looks like a simple internal message is never simple. A memo lands in a crowded inbox, competing with dozens of other demands, and yet it still has to do three jobs at once: signal importance, compress complexity, and provoke action. That is already a strategic act. But here is the deeper twist: once the message arrives, every reader turns the same shared broth into a different bowl.

That is why so many organizations confuse communication with understanding. They think if the words are clear, the work is done. In reality, clarity is only the beginning. People do not receive information as blank slates. They receive it through their role, mood, incentives, past experiences, and immediate context. The same memo can feel like a directive, a warning, a suggestion, or a nuisance. The same strategy can become alignment for one person and resistance for another.

A message is not complete when it is sent. It is complete when each reader has made it actionable in their own context.

This is the hidden connection between the humble memo and the communal bowl of pho. Both are built from shared material, but their real meaning appears only after customization. One person adds chili, another hoisin, another lime. One manager reads the memo as an operational priority, another as political cover, another as a sign that more work is coming. The content is identical. The experience is not.

That difference matters more than we admit, because it reveals something fundamental about strategy itself: strategy is not just choosing what to do. It is choosing what others will be able to do with what you give them.

---

Shared broth, personal bowl: why identical information produces different realities

The pho metaphor is powerful because it captures a truth most management language obscures. Teams do not consume strategy in a vacuum. They season it. They interpret it. They adapt it to appetite, habit, and tolerance for risk. A centralized strategy document may describe the same future for everyone, but the lived version of that future is assembled locally, one decision at a time.

This is true in a small team and in a large company. A memo announcing a new priority does not arrive as an abstract principle. It enters a specific life. For one employee, it means, “Great, this clarifies what matters.” For another, “Now I need to renegotiate my roadmap.” For someone else, “This is probably going to be another initiative that dies in two weeks.” The document is the same, but the meaning is different because the reader’s current situation is different.

That means the real unit of strategy is not the memo itself. It is the interpretive space the memo creates. A good internal message does not merely inform. It narrows ambiguity enough to enable action while leaving enough room for local adaptation. If it is too vague, people cannot move. If it is too rigid, they cannot translate it into their actual work.

Think of it like a recipe. A recipe is not the meal. It is a framework for turning ingredients into something edible under real-world conditions. It tells you the key constraints, the order of operations, and the intended result. But every kitchen has different tools, heat, ingredients, and cooks. Good instructions anticipate variation without trying to eliminate it.

That is why the subject line of a memo matters more than we think. In a crowded inbox, a subject line is not just a label. It is an invitation to allocate attention. It says, in effect, “This is worth your limited bandwidth because it affects something you care about.” But it must do so honestly. If it overstates urgency, trust decays. If it understates consequence, the message dies unread. The best subject line is not hype. It is accurate gravity.

Here is the larger lesson: people do not have a single relationship to information. They have a relationship to its cost, its relevance, and its implications for action. The same memo can be a lifeline or noise depending on where the reader stands.

---

Strategy is choosing what the future will feel like in someone else’s hands

Most strategy discussions focus on decisions at the top: what to prioritize, what to build, what markets to enter, what to stop doing. But those choices only matter if they survive contact with the people who must execute them. Execution is where strategy stops being an abstraction and becomes a lived experience.

This is where the pho metaphor becomes more than a neat comparison. A bowl of pho is assembled from a common base, but each person’s final version depends on how much basil they add, whether they choose extra lime, how much chili they can tolerate, and what they personally want from the meal. Strategy works the same way inside organizations. A leadership team may define the broth, but the organization still has to serve bowls that people can actually eat.

That suggests a more useful definition:

Strategy is the art of designing shared constraints that produce locally useful choices.

This is more precise than saying strategy is merely “choosing what to do.” Choice matters, but the shape of the choice matters just as much. If leaders only specify goals, the organization gets ambiguity. If they only specify rules, the organization gets compliance without intelligence. The highest-leverage strategy does something subtler: it establishes a broth strong enough to unify action, then leaves enough room for each team to season the work to fit reality.

This reframes the memo as a strategic artifact. A good memo does not just announce a decision. It creates a decision environment. It tells people:

• what has changed,
• why it matters,
• what is now true,
• what tradeoffs are being made,
• and what freedom remains.

When a memo accomplishes those five things, it does not merely transfer information. It compresses uncertainty. It converts a diffuse organizational mood into a usable frame. It is no longer just a note. It is a container for alignment.

Consider a product team deciding whether to cut a feature. A weak memo says, “We’re focusing on core users.” That sounds strategic but leaves too much unsaid. A stronger memo explains the user segment being prioritized, the metric being protected, the tradeoff being accepted, and the specific behavior changes expected from the team. Now the same idea becomes actionable. Designers, engineers, and marketers can each infer their own next move, because the message has been built to survive translation.

That is the real difference between broadcasting and communicating. Broadcasting transmits a statement. Communicating designs a path from statement to interpretation to action.

The best strategy documents are not monuments to certainty. They are tools for coordinated adaptation.

---

The tension every organization avoids: consistency versus customization

Organizations love consistency because it feels controllable. They also love customization because it feels responsive. But the two are in tension. Too much consistency, and the organization becomes brittle. Too much customization, and it fragments into local kingdoms. The pho bowl solves this beautifully: same broth, different bowls. That is not chaos. It is structured variation.

This is the model many companies fail to see in their own communication. They either standardize everything into lifeless corporate language, or they let every team improvise so much that nobody can recognize the common mission. Both failures stem from misunderstanding what a message is for.

A message is not meant to eliminate interpretation. It is meant to guide interpretation.

That is why the most effective memos often have a strong internal skeleton. They begin with the essential fields, almost like a skeleton of accountability: to whom, from whom, about what, and when. These details do more than identify the sender and receiver. They establish responsibility, context, and timing. Then the body of the memo can do the real strategic work: define what matters, what has changed, and what action should follow.

The structure is important because human attention is expensive. A reader faced with a flood of communication needs immediate orientation. If the message does not quickly answer, “Why should I care, and what should I do now?” it gets mentally filed under irrelevant. But orientation is not enough by itself. The content also needs to invite ownership. People are more likely to act when they can see how the message fits their world.

This is where many leaders go wrong. They think messaging is about control, when it is actually about coordination across diverse realities. A memo that tries to remove all ambiguity becomes unreadable. A memo that leaves all ambiguity intact becomes useless. The craft lies in the middle: enough precision to set direction, enough openness for adaptation.

You can see the same pattern in strong consumer products. A good product does not force every user into one rigid workflow. It provides defaults, guardrails, and affordances, then lets people adjust to their needs. Great software, like great strategy, is opinionated but not tyrannical. It offers a shared base and encourages personal fit.

In that sense, internal communication is not unlike product design. You are designing an experience for the reader. You want them to leave the memo with less confusion, fewer competing interpretations, and a clearer next step. But you also want them to feel that the message respects their intelligence and context.

That respect matters. People can tell the difference between a memo that treats them like an audience and a memo that treats them like a participant. The first asks for attention. The second earns action.

---

A practical framework: write memos like you are serving pho, not handing out flyers

If the broth is strategy, then the memo is the serving vessel. Its job is not to contain everything. Its job is to deliver the right ingredients in a form people can actually use. That leads to a practical framework for internal communication and strategic alignment.

1. Define the broth: what is the shared core?

Start with the one idea everyone needs to share. Not five ideas. Not a mission poem. One core point.

Ask:

• What is now true?
• What has changed?
• What do we want people to believe or prioritize after reading this?

If you cannot answer these in one or two sentences, the message is not ready.

2. State the tradeoff: what are we choosing not to do?

Strategy is visible when it excludes as much as it includes. People trust priorities more when they can see the cost.

Ask:

• What are we de-emphasizing?
• What will people need to stop doing or delay?
• What false assumptions are we correcting?

This is where many memos become honest and useful. Without tradeoffs, a message sounds like a wish list. With tradeoffs, it sounds like a decision.

3. Make the bowl customizable: what can local teams adapt?

Do not confuse clarity with rigidity. Spell out the invariant parts and the variable parts.

Ask:

• What must stay consistent across teams?
• What can vary by function, geography, or customer segment?
• Where do we want smart local judgment?

This prevents both chaos and over-control. People need to know where they can add their own chili.

4. Signal the reader’s job: what should this change in behavior?

A memo should end in movement, not admiration.

Ask:

• What decision should this unlock?
• What should the reader do next?
• What is the smallest meaningful action they can take within 24 hours?

Behavior beats understanding when resources are limited. If the memo does not change behavior, it has not yet earned its keep.

5. Write the subject line like a promise, not a stunt

In a noisy inbox, the subject line is an integrity test. It should accurately convey why the reader should invest attention.

A strong subject line does not shout. It points.

Compare these:

• “Update”
• “FYI”
• “Q3 roadmap changes for product and design teams”
• “Decision: we are pausing expansion to protect core retention”

The last examples respect the reader’s time because they tell the truth about significance. That is what earns the click.

---

Key Takeaways

1. Treat communication as interpretation design. A message is not finished when it is written. It is finished when different readers can turn it into action without guessing.

2. Use strategy to define shared constraints, not to erase local judgment. The strongest plans create a common broth and still let teams season their own bowls.

3. Make tradeoffs explicit. If nothing is being deprioritized, your priorities are probably not real yet.

4. Write for limited attention, but do not flatter it. A good subject line signals real importance without exaggeration.

5. Separate what must be consistent from what should be adaptable. The more clearly you distinguish the two, the more resilient your organization becomes.

---

The best memos do not just inform the organization. They teach it how to think

The deepest connection between pho and memos is not that both are made of shared ingredients. It is that both reveal a truth about human systems: the same substance can create different experiences without losing its unity.

That is the real challenge of leadership. Not to make everyone consume identical meaning, but to create a common frame that people can inhabit differently without drifting apart. A great memo does this by respecting attention, clarifying stakes, and leaving room for intelligent adaptation. A great strategy does this by choosing a direction strong enough to unify and flexible enough to live inside real work.

So the next time you write to a team, do not ask only, “Did I say what I meant?” Ask a harder question: “Did I create a shared broth people can actually turn into their own useful bowl?”

Because in the end, organizations do not run on information alone. They run on the transformations that happen after information is received, interpreted, and made local.

That is why the memo is never just a memo. It is the first taste of strategy as lived experience.