Communication Architecture

Decisions don't cascade
on their own.
This is what carries them.

Leaders produce more communication than ever. AI will produce more still. The leaders who succeed in this environment aren't the ones who communicate more — they're the ones who've built a system that makes every message land, every decision stick, and every person downstream know exactly where things stand.

Architecture Built AI Roles Mapped Cascade Ready

The Frame

Communication is how we
tell stories.

Before we get into structure or frameworks — think back to when you first learned to write a story. The criteria were simple. Not about style or length or voice. Six things every story has to answer, or it doesn't work.

The same is true for every communication system a leader builds. It doesn't matter how sophisticated the org chart is, or how many tools are in play, or how talented the team is. If the system doesn't answer these six questions, something breaks. Usually at the worst possible moment.

Click each card to reveal the principle.

Every story must answer —

Why

↻ flip

Philosophy

The operating principles every person on this team signs. How we handle information, surface conflict, close decisions, and show up for each other.

What

↻ flip

Outcome

Every communication has a job. Name it before you run it.

How

↻ flip

Procedures

One conversation, one job. A structure for going forward and looking back.

Who

↻ flip

Decision Rights

One decision, one decider. Ambiguity is the enemy of speed.

When

↻ flip

Cadence

Less volume, more structure. Each meeting does one job — not four.

Where

↻ flip

Forums

One source of truth. If you can't find it there, it doesn't exist.

Click any card to reveal · Click again to flip back

→

A communication architecture is no different from a story. Every working system answers the same six questions. Today we build yours.

The Model

A sophisticated comms system is like an air traffic control system.

Hundreds of aircraft. Different altitudes. Different directions. Different urgencies. They don't collide because the system makes sure of it — not the talent of any individual pilot, not luck, not goodwill between flights.

Five things keep it working. Remove any one and the system degrades. Remove two and things crash. The same is true for the communication system your team runs every week.

FL 360

✈ AAL 237

✈ DAL 891

FL 280

✈ UAL 514

✈ SWA 1142

FL 120

✈ JBU 78

GROUND

🛬 FDX 902

🗼

Control Tower — One System, All Traffic

Five principles that keep it working —

Every aircraft on the radar

Universal visibility. Nothing moves through the system without being seen. No surprises, no blind spots.

Designated airspace, designated controller

Each zone has one authority. No ambiguity about who's in charge of what altitude and what traffic.

Standardized phraseology

"Cleared for takeoff, runway 27 right." Same words, same meaning, every time. No room for interpretation.

Read-back required

The pilot repeats every clearance back. The loop is always closed. The controller knows the message landed.

Coordinated handoffs

When an aircraft leaves your zone, you brief the next controller with full context. Nothing gets dropped at the boundary.

70%

Of aviation accidents in the 1970s were attributed to teamwork and communication failures — not technical knowledge gaps. The pilots knew how to fly the aircraft. They didn't have a system for flying it together.

The corporate version of the same finding shows up in every organizational post-mortem. Not "we lacked capability." "We didn't know. We assumed. No one told me." That's a communication architecture failure. Every time.

U.S. National Transportation Safety Board · Aviation Accident Analysis

The AI Imperative

AI doesn't change the need for the architecture. It makes it non-negotiable.

Every leader in this program will leave with more AI-generated content than they know what to do with — drafts, summaries, analyses, recommendations. The ones who struggle won't be the ones who can't use the tools. They'll be the ones who built no system to absorb the output.

AI multiplies information velocity

Where a team once produced one memo, AI now produces ten. The bottleneck has shifted from content generation to content absorption and decision-making. Without a system, faster generation just means faster noise.

AI creates multiple versions of truth

Different people, different prompts, different outputs. Your information architecture — your single source of record — is what determines which version is authoritative. Without it, you have ten "truths" competing for adoption.

AI blurs the decision boundary

When AI recommends, who decides? When AI summarizes, who owns the conclusion? The architecture you build today answers these questions before they become the source of a three-week re-litigation.

Before we build yours — we need to know where it's breaking.

Most teams don't have one bad meeting. They have one meeting trying to do four jobs. Before we design the architecture, we name the symptoms that tell us which components are missing. Part 2 is the diagnostic.

The Diagnostic

Three symptoms.
One missing infrastructure.

These patterns show up across most senior leadership teams. They're not character flaws — they're rational responses to a system that isn't working. Each symptom tells you exactly which component of the architecture is missing.

Name which ones are live in your environment before we build. The architecture you design in Part 3 should be built to solve for what you identify here.

Symptom 01

Decision Latency & Re-litigation

Tuesday · 10:00am · Leadership Meeting

The meeting runs for 90 minutes. There's real debate. People share perspectives. The energy in the room suggests something meaningful is happening. Then it ends — and three people walk out with three different understandings of what just occurred.

🧑‍💼

"We made a call. I'm moving forward with the plan."

Decided

🧑‍💼

"We're still working through it. I assumed we'd follow up."

Aligning

🧑‍💼

"That was background context. Nothing was decided."

Informed

Same meeting. Next Tuesday. ↻

Failure Mode A

The type of conversation was never declared

Was this meeting called to Inform, to Align, or to Decide? When that's not named at the start, every participant fills in their own answer — and walks out with a different one. The meeting can't do its job if nobody named the job.

Failure Mode B

There was never a named decider

Even when a conversation reaches a conclusion, it evaporates if nobody owns it. "Everyone owns it" is how organizations say "nobody owns it." Without a single named decider, the decision exists only as long as the energy in the room lasts — which is never long enough.

The two failure modes that produce this symptom are exactly what Inform / Align / Decide and the RAPID framework resolve in Part 3. The goal isn't faster decisions — it's decisions that actually close.

Symptom 02

Artificial Harmony & Triangulation

A → C → B ✓

A → B directly ✗

Low-conflict meetings · High-volume DMs

Quiet rooms. Loud DMs.

The diagnostic signature: meetings where nothing difficult is said, followed by a flood of direct messages, side conversations, and hallway processing the moment the call ends. The tension didn't disappear — it just moved somewhere less visible.

A goes to C with the issue.

C becomes a parallel communication channel. The peer relationship between A and B never gets tested, never develops the muscle to handle friction directly. Every difficult thing routes up or sideways before it can be resolved peer-to-peer.

The org scales worse.

When every issue routes up before it can come back down, leadership becomes the communication infrastructure — and that doesn't scale. The layer below learns that they can't resolve things among themselves, so they don't try.

Symptom 03

Collaborative Overload

Weekly Sync 31 attendees

👤

Could deliver the outcome

On the call

Why they're all there — each reason is rational

"If I'm not on this call, I'll hear about the decision three days later through someone else's interpretation."

"Last time I missed this meeting, my team was affected by something I had no input on."

"I need to be in the room to make sure my function isn't pulled in a direction I can't support."

"The follow-up notes never capture what actually matters. The only way to know is to be there."

The 30 people on that call aren't there because the task requires 30 people. They're there because they've learned they have to be. Every reason they give is rational — given the system they're operating in. When the architecture works — when decision rights are clear, when there's a reliable information channel, when the operating rhythm gives everyone a legitimate forum — people stop inserting themselves into every conversation. The calendar clears. Not because someone told them to attend fewer meetings, but because they no longer need to.

The Second Symptom · Bench Strength

The same few people in every room.

Collaborative overload shows up on both ends. Too many people needed for one outcome — and too few people absorbing too much of the valuable work. If your highest performers are present for every significant conversation and decision, that's not a sign of their talent. It's a sign that you haven't developed the layer below them. The goal isn't a smaller inner circle. It's a deep enough bench that each outcome has its own capable small group — and those groups don't have to be the same people every time.

The Wedge

These symptoms don't just slow down the org.
They land on the people below you.

The point isn't that your team communicates badly. It's what these symptoms reveal about the environment your leadership has created — not through intent, but through the absence of a system.

Decision Latency

Reads as: leadership can't commit.

When decisions don't close, the team below stops waiting for direction and starts guessing. They make their own calls — some right, some wrong — because the alternative is paralysis. The re-litigation they watch above them teaches them that nothing is ever really final.

Artificial Harmony

Reads as: honesty isn't safe here.

When the leadership team won't surface conflict directly, the layer below learns the same behavior. The culture of quiet rooms and loud DMs doesn't stay at the top — it replicates downward. Feedback gets withheld. Problems stay underground until they're too big to ignore.

Collaborative Overload

Reads as: you don't trust us.

When 30 people need to be in a room to make something move, the message to the organization is clear: decisions aren't real until the right people are watching. That's a trust deficit — in the system, in the people, in the process. It replicates as learned helplessness in the layer below.

Every escalation that should have resolved itself. Every decision that needed to be made twice. Every meeting that required 30 people to produce one outcome. That's not just inefficiency — that's stress the leadership system is generating and pushing down. The architecture you build in Part 3 is what stops it.

Part 3 · The Architecture Build

You've named the symptoms.
Now build the system.

Every symptom in Part 2 maps to a missing component. Decision latency means no clear I/A/D contract and no named decider. Collaborative overload means decision rights that haven't been distributed. Triangulation means information traveling sideways instead of up.

The Architecture Build works through all six components — in the order they have to be built. You can't design decision rights before the team has agreed on principles. You can't build a cadence before you know what conversations need to happen. Start here.

Component 01 · Why

Philosophy —
the standard
every name signs.

Before the procedures, the cadence, the decision rights — the team has to agree on how they communicate. Not aspirationally. Operationally. The Philosophy is the set of principles every person on this team holds themselves to, in writing, before we build anything else.

This matters because the other five components can be designed around you. The Philosophy has to come from you. It's built through a structured exercise — and it's the only component that requires every voice in the room.

The Exercise

Defining the Standard

This exercise gives the team four specific prompts — one for each domain of communication behavior — and asks each person to name what excellence looks like in their own words. The goal is shared language. The outcome is principles every name on this team signs.

Prompt 01

Information

"When this team is operating at its best — how do we handle information?"

What adjectives describe how we share, surface, and treat information on this team?

Prompt 02

Conflict

"When this team is operating at its best — how do we surface conflict?"

What adjectives describe how we handle disagreement, tension, and difficult truths?

Prompt 03

Decisions

"When this team is operating at its best — how do we close decisions?"

What adjectives describe how we make and commit to decisions as a leadership team?

Prompt 04

Showing Up

"When this team is operating at its best — how do we show up for each other?"

What adjectives describe how we hold each other accountable and support each other's success?

How to Facilitate

Distribute sticky notes — physical or digital (Miro, Jamboard). Each person needs four sets, one per prompt.

Read each prompt aloud. Allow 90 seconds of quiet writing before moving to the next. No discussion yet — you want individual instinct, not group consensus.

Surface and cluster. After all four prompts, have participants share their words one at a time. As a group, cluster by theme. Let the board fill before you start editing.

Find the common thread. Look for words that appear across prompts and across people. These are your candidates — the language the team already shares, even if they haven't said it out loud.

Draft 4–5 principles together. These don't have to be single words — but single words carry better. Test each one: does it describe how we actually want to operate, or how we think we should sound?

Name the gap. Ask each person to name where the team falls furthest short of these principles today. This is not a critique — it's the honest accounting that makes the standard real instead of decorative.

Every name signs. The Philosophy becomes operational the moment every person on the team commits to it explicitly — not with enthusiasm, with their name.

Example Outcome — What This Looks Like

Information

Transparent · Complete · Timely · Proactive

Conflict

Direct · Respectful · Early · Honest

Decisions

Decisive · Clear · Final · Committed

Showing Up

Accountable · Consistent · Visible · Supportive

Principles Landed

Transparent

Direct

Decisive

Accountable

Timely

"These five words describe how we communicate at our best. They're not aspirational — they're the standard we hold each other to."

Component 02 · What

Outcome —
name the job
before you run the room.

Every communication has a job. A meeting is not a meeting — it's either an Inform, an Align, or a Decide. If you don't name which one it is before it starts, the room will assign its own reading. And they won't all assign the same one.

This is the mechanism behind Decision Latency. Not that the team is indecisive — but that nobody named the type of conversation they were in, so nobody knew what "done" looked like. You close that gap with a single word at the top of every agenda item.

Inform

Share context, data, or a decision that's already been made. No debate expected. The job is a shared picture — not alignment or resolution.

Done when

Everyone has the same information and knows what it means for their work.

Align

Build shared understanding before a decision is made. Surface divergence. Test assumptions. The job is to make the team ready to decide — not to decide in the room.

Done when

The group has surfaced the real divergence and is ready for a decision to be called.

Decide

Close. One decider — named before the conversation starts. The job is one answer, no revision. The room can input; one person calls it.

Done when

One named person has called the decision and the team leaves with the same answer.

Name the type before you start. If the room doesn't know whether it's an Inform, an Align, or a Decide — it will become all three, and close as none of them.

◈

AI Lens

AI can carry the Inform function at scale — it multiplies information velocity, surfaces relevant data, prepares briefing material, and can maintain multiple versions of the same context for different audiences. It cannot Align (that requires judgment about what divergence matters) or Decide (that requires accountability). The I/A/D contract makes this boundary explicit: if it's labeled Inform, AI can do most of the work. If it's labeled Decide, AI never holds the D.

Component 03 · How

Procedures —
one conversation,
one job.

The most common structural failure in leadership communication: mixing conversations that should never be in the same room. You can't look backward and forward at the same time — accountability and planning contaminate each other when they share an agenda.

Procedures are the operating agreements that govern how your conversations run. Not policies. Agreements — made by this team, for this team, before a single meeting happens.

→ Going Forward

Direction & Decisions

Planning, aligning, and deciding what happens next. These conversations create commitments — they change what the team will do.

Conversation type

A — Align D — Decide

Operating rules

Every agenda item is labeled A or D before the meeting starts. No label, no agenda item.

For D items — the decider is named in the agenda. Not in the room. In writing, in advance.

Pre-read distributed 24 hours before. The meeting is not where the room learns the context — it's where the room decides.

← Looking Back

Review & Accountability

Evaluating what happened against what was committed. These conversations create learning — they change what the team knows and how it adjusts.

Conversation type

I — Inform A — Align

Operating rules

Data arrives before the conversation, not in it. Nobody presents numbers live — the room discusses what they already read.

No revision of past decisions. This conversation is for learning and adjustment, not relitigating.

Output is adjustment, not judgment. What changes going forward — not who failed to deliver.

The Three Non-Negotiables

Every agenda item has a type before the meeting starts.

I, A, or D — written in the agenda. If a team member can't label their item, it's not ready to be discussed. The label disciplines the conversation before it begins.

Forward-looking and backward-looking conversations don't share a room.

When accountability and planning are in the same meeting, planning wins — nobody wants to sit in a room that might turn into a performance review. Keep the modes separate and both get done properly.

Decisions get recorded and distributed within 24 hours.

In writing. To everyone affected — including people who weren't in the room. The decision record is the only thing that closes the evaporation problem. If it's not in writing, it didn't happen.

◈

AI Lens

AI owns the procedural scaffolding: drafting pre-reads, maintaining the decision record, distributing post-meeting summaries. This is exactly where AI creates leverage without crossing the accountability line. The more consistently procedures are followed, the more AI can automate the wrap-around work — freeing the room to do the judgment that can't be delegated.

Component 04 · Who

Decision Rights —
one decision,
one decider.

The reason decisions don't close isn't that the team is indecisive. It's that ownership was never assigned. RAPID is a role mapping framework — for every significant decision, five roles are filled before the conversation begins. One of those roles is the only one that closes the decision: the D.

The goal is not to centralize decisions. It's to make clear who closes them so the rest of the team can stop waiting for a signal that was never coming.

Recommend

Does the analysis, develops the options, proposes the path forward. Owns the work of forming a recommendation.

AI can hold

Agree

Must sign off before the decision is made. Has veto authority. Use sparingly — each A slows the process.

AI never

Perform

Will execute once the decision is made. Needs to be consulted but doesn't determine the outcome.

AI can support

Input

Provides information or perspective. Consulted and considered — but not binding on the outcome.

AI can hold

Decide

The single accountable person. One per decision. Named before the conversation starts. Makes the call.

AI never

Every significant decision gets a RAPID map before it goes to a room. If you can't name who holds the D, the conversation isn't ready to happen. Ambiguity about ownership is not a judgment call — it's a structural gap.

◈

AI Lens

In AI-augmented workflows, the R role expands dramatically — AI can synthesize data, model options, and draft recommendations faster than any analyst. The I role also expands: AI can hold and surface relevant context across more domains than any individual could track. What doesn't change: A and D always belong to humans. The accountability that makes RAPID work cannot be delegated to a system that can't be held responsible.

Component 05 · When

Cadence —
less volume,
more structure.

The answer to too many meetings is not fewer meetings — it's better-designed ones. A nested cadence assigns each conversation type its own time horizon and purpose, so the team always knows which level of the system they're operating in.

Each meeting does one job. The frequency determines the time horizon. The I/A/D type determines what the room is there to do. Stack all four layers and you have a rhythm that carries direction from the strategic to the operational without any conversation doing work it wasn't designed for.

Daily

15 – 30 min

Standup / Check-In

State of play. Blockers visible. What moved yesterday; what's in motion today. No decisions — this is information velocity, not problem-solving. If something needs a decision, it gets scheduled separately.

I — Inform 15 – 30 min

Weekly

60 – 90 min

Team Operating Meeting

Where the work gets done. Agenda items are pre-labeled I, A, or D. Pre-read distributed 24 hours prior. This is the primary decision-making surface — where Align and Decide conversations happen against real work.

A — Align D — Decide 60 – 90 min

Monthly

2 – 3 hours

Review + Forward Planning

Backward-looking first: what happened, what it means, what adjusts. Forward-looking second: what's coming in the next 30 days, what decisions need to be pre-positioned. Separate the two modes — don't let them bleed into each other.

I — Inform A — Align 2 – 3 hours

Quarterly

Half day

Strategic Alignment Session

Direction and priorities for the next 90 days. Where are we versus where we said we'd be? What changes? What stays? This is the one session where the team steps out of the operational layer and works at the strategic level. Protect it.

A — Align D — Decide Half day

◈

AI Lens

AI creates particular pressure on the Daily and Monthly layers. At the daily level, AI can surface blockers, flag anomalies, and prepare the state-of-play — compressing what previously required human aggregation into an automated brief. At the monthly level, AI can prepare the backward-looking review automatically. The risk: when AI generates the brief, teams stop doing the synthesis themselves. The cadence structure preserves the human judgment layer by making clear which conversations require it — and which don't.

Component 06 · Where

Forums —
one source
of truth.

Information lives somewhere. The question is whether everyone on the team knows where. When there's no single source of truth, each person builds their own version — and those versions diverge. The forum architecture is the structural answer: each type of communication has a home, and that home is non-negotiable.

Three channels. One record. No exceptions.

⬡

Synchronous

Live Conversations

Real-time interaction — meetings, calls, working sessions. This is where Align and Decide conversations happen. Not where information is presented for the first time.

Used for

A — Align: working through divergence live

D — Decide: closing with a named decider in the room

Escalations that can't resolve asynchronously

⬡

Asynchronous

Non-Real-Time Channels

Email, messaging, shared documents. This is where information travels without requiring the recipient's time. The default channel for anything that doesn't need a live room.

Used for

I — Inform: distributing decisions, updates, context

Pre-reads before synchronous sessions

Low-stakes Align where written back-and-forth is sufficient

⬡

The Record

Source of Truth

The permanent home for decisions, commitments, and agreed-upon direction. Not a channel for new communication — a repository for what has already been resolved.

Lives here

Every decision, with the D owner and date

Strategic commitments and quarterly priorities

RAPID maps for standing decision types

If it's not in the Record, it didn't happen. The decision that lives only in someone's memory — or only in the meeting where it was made — is a decision waiting to be relitigated. The Record closes the evaporation problem for good.

◈

AI Lens

This is the component where AI creates the most structural risk. AI generates summaries, drafts, and derivatives at speed — and each one becomes a potential divergent version of the truth. The more AI is in the workflow, the more critical the forum architecture becomes. One source of truth isn't a nice-to-have when AI is in play — it's the only defense against information proliferation. Every AI-generated output needs a designated home and a human who owns it before it enters the system.

The Architecture is built

Now make direction travel.

You have the six components. Part 4 is how they become a living system — how direction from this team cascades to every layer of the organization, in a form each audience can act on.

Part 4 · The Cascade

The architecture exists.
Now make direction travel.

Building the architecture is the structural work. The cascade is the operational work — how you take the decisions and direction produced by the system and translate them into something every layer of the organization can understand and act on.

Most direction evaporates not because it wasn't communicated, but because it was communicated once, in the same form, to everyone. The cascade solves that: same direction, designed for each audience, carried by the right people, at the right frequency.

Framework · Message Design

Think. Feel. Know.
Design the message
before you send it.

Before any directional communication leaves this team, answer three questions about your audience. Not about the content — about the effect. What do you want them to think, feel, and know after receiving it? The answers determine the form, the tone, and the level of detail.

Most leaders design for Know — they focus on the information. The messages that actually land design for Think and Feel first, then build the Know to support them.

Think

"What conclusion do you want this audience to reach after receiving this communication?"

This is the headline.

The one idea that should stick if they remember nothing else. Design the message to arrive here.

Feel

"What emotional response should this communication create — and what would undermine it?"

This is the tone.

Confident. Informed. Motivated. Steady. Name the intended response before you write the first word.

Know

"What specific information does this audience need to have — and what context do they already carry?"

This is the evidence.

The facts, decisions, and context that support the Think. Include only what's necessary to arrive at the conclusion.

◈

AI Lens

AI can draft the Know layer with precision — synthesizing data, summarizing decisions, preparing context briefings. It cannot reliably generate the Think (the strategic conclusion the leader wants the audience to reach) or the Feel (the tone that matches this team's relationship with this audience, at this moment). The leader provides T and F. AI builds the K. That division produces communications that are both accurate and human.

Framework · Message Structure

Message Architecture —
the structure that
carries direction down.

Once you know what you want the audience to Think, Feel, and Know — you need a structure that delivers it. The Message Architecture is a three-layer template that applies to any directional communication, regardless of channel or audience size.

Every layer maps to one of the three design questions. Together they produce a message that lands at the top, holds in the middle, and moves at the bottom.

The Three Layers

Layer 01

The Headline

→ Think

The one thing. Written first, even if it's delivered last.

This is the conclusion you want the audience to reach — stated plainly, before any context or evidence. If this layer is vague, the rest of the message won't save it. Test it: can you state the headline in one sentence without qualifiers? If not, the thinking isn't clear enough yet.

Layer 02

The Evidence

→ Know

What supports the headline. Three points maximum.

Data, decisions, context — the minimum required for the audience to trust the headline. More than three points and the audience starts weighing evidence instead of accepting direction. Select the three that do the most work. Everything else belongs in an appendix or a pre-read.

Layer 03

The Ask

→ Feel → Act

What you need them to do. Specific, not general.

Every directional communication has an action outcome — even if that action is "continue what you're doing with confidence." Name it explicitly. "By Friday" beats "soon." "Bring your three blockers" beats "come prepared." The more specific the ask, the more the audience feels informed rather than managed.

Framework · Cascade Planning

Communication Calendar —
who tells whom,
when, and what.

The cascade doesn't happen by accident. Each person who receives direction from this team is also someone who gives direction to their team. That chain has to be designed — the message has to be adapted for each layer, and someone has to own each link.

The Communication Calendar maps the cascade. For every significant directional message, it answers four questions: who owns the communication, who receives it, by when, and in what form.

Sample Cascade Map — Quarterly Direction

Audience	Owner	Timing	Form	Type
Leadership Team	CEO / President	Day 0 — Quarterly session	Live strategic session	A + D
Direct Reports of LT	Each LT member	Within 48 hours	Team meeting — adapted message	I + A
Broader Manager Layer	Each manager	Within one week	Written brief + Q&A session	I
Individual Contributors	Direct manager	Within two weeks	Team standup + written summary	I

Each layer adapts the message — it doesn't rewrite the direction. The headline stays constant. What changes is the Think/Feel/Know design for that specific audience. A VP and an individual contributor need different evidence to reach the same conclusion.

◈

AI Lens — Communicating Direction During AI-Driven Change

When the change being communicated is AI-driven change itself, the cascade faces a specific challenge: people aren't just receiving direction — they're being asked to trust direction about a technology that is actively changing their work. The Feel layer becomes more important than in any other type of communication. Steady, specific, and honest beats ambitious and vague every time. What is changing, what isn't, what the team will do when something doesn't work — these answers belong in every cascade message about AI. The leaders who communicate the most clearly about AI earn the trust to lead it.

Decisions don't cascadeon their own.This is what carries them.

Communication is how wetell stories.

A sophisticated comms system is like an air traffic control system.

AI doesn't change the need for the architecture. It makes it non-negotiable.

Before we build yours — we need to know where it's breaking.

Three symptoms.One missing infrastructure.

You've named the symptoms.Now build the system.

Philosophy —the standardevery name signs.

Outcome —name the jobbefore you run the room.

Procedures —one conversation,one job.

Decision Rights —one decision,one decider.

Cadence —less volume,more structure.

Forums —one sourceof truth.

The architecture exists.Now make direction travel.

Think. Feel. Know.Design the messagebefore you send it.

Message Architecture —the structure thatcarries direction down.

Communication Calendar —who tells whom,when, and what.

Decisions don't cascade
on their own.
This is what carries them.

Communication is how we
tell stories.

Three symptoms.
One missing infrastructure.

You've named the symptoms.
Now build the system.

Philosophy —
the standard
every name signs.

Outcome —
name the job
before you run the room.

Procedures —
one conversation,
one job.

Decision Rights —
one decision,
one decider.

Cadence —
less volume,
more structure.

Forums —
one source
of truth.

The architecture exists.
Now make direction travel.

Think. Feel. Know.
Design the message
before you send it.

Message Architecture —
the structure that
carries direction down.

Communication Calendar —
who tells whom,
when, and what.