You completed the Meaning Risk Snapshot. You scored your team. You named some risks. Now, the question that determines whether any of this sticks.

What the next ten weeks actually feel like

You will try a repair move in a meeting, and it will come out wrong. The sentence you practiced at your desk will arrive in the room with an extra clause and a nervous qualifier tacked on the end. Someone will give you a look. You will wonder if the move made things more awkward, not less.

This is the correct experience. It means the learning is working.

Research on habit formation is consistent on one point: health-related habits take two to five months to develop, with substantial variation between individuals. Starting slowly and increasing gradually, what we’ll call habit laddering, maintains new practices 1.5 times longer than going all-in from day one. A ten-week course falls inside that window. But it means you are still mid-construction at Module 3, Module 5, and probably Module 8.

The awkwardness is not a sign that you’re failing. It is the felt experience of building a new default. The old default (swallow the doubt, let the ambiguity slide, assume everyone understood the same thing) took years to install. The new one needs time and repetition under real conditions.

So: expect the wobble. Practice the move anyway. The goal for the first three modules is frequency, not fluency. Use the repair stance once this week. Use it badly if necessary. The reps compound.

Subscribe now

What your Meaning Risk Snapshot is telling you

You now have a scored baseline. A set of numbers attached to specific communication risks on your team. Some of those numbers confirmed what you already suspected. Others may have surprised you.

Here is what to do with the snapshot before Module 2 arrives.

Look for the cluster. Most teams don’t have ten equally severe risks. They have two or three failure modes that account for the majority of their coordination problems. Which items scored lowest? Where did the numbers cluster? That cluster is your team’s drift signature, the pattern of meaning failure that repeats across meetings, handoffs, and decisions.

Notice what you couldn’t score. Some items on the snapshot may have felt unanswerable. You weren’t sure how your team handles ambiguity because you’ve never watched for it with this lens. That uncertainty is data. It tells you where your team’s communication patterns are operating below conscious awareness, which is exactly where drift lives.

Hold the cultural context field. If you filled in the Meyer dimensions (power distance, communication directness, comfort with silence), sit with those ratings for a moment. They shape which repair moves will land easily on your team and which ones will need adaptation. A team with high power distance will need different activation pathways than a team where anyone can interrupt anyone. We’ll build those pathways starting in Module 4.

You’ll retake this snapshot at Day 30 and Day 60. The numbers will move. The question is whether they move because your team’s communication actually changed, or because your awareness sharpened. Both matter.

Transfer Bridge

The Meaning Risk Snapshot was designed for work teams. But meaning drifts everywhere when people coordinate under pressure, with incomplete information, or with competing assumptions.

This week’s prompt: Where outside your current work role would this diagnostic have changed an outcome recently?

A few places to look:

A medical appointment where you and the provider were using the same words to describe different things. A family conversation about plans, where “we agreed” turned out to mean two different commitments. A negotiation, with a contractor, a landlord, a co-parent, where the key term was never pinned down, and the ambiguity surfaced later as conflict.

Pick one. Run the snapshot against it mentally. Which failure type would you flag? Where was the drift? When did you sense it? What kept you from naming it?

That last question, what kept you from naming it, is the one this entire course circles around.

Discussion

Three questions for the comments. Pick the one that pulls you.

1. What is your team’s drift signature? Which two or three risk areas clustered at the bottom of your snapshot, and does that match what you would have guessed before scoring?

2. When you think about the cultural context field, what is the single dimension (power distance, directness, silence comfort) that most shapes how your team handles ambiguity? What does that look like in practice?

3. For the Transfer Bridge: describe one non-work conversation where meaning drifted, and you noticed but didn’t repair it. What was the cost?

A standing invitation. If your example from this week — whether the repair move worked, went sideways, or revealed something you didn’t expect — would be useful as a case study for future course material, share it in the comments with the tag [CASE STUDY]. I collect these (with permission, anonymized) to strengthen the evidence base behind this framework. The more situated examples we accumulate from real teams and real conversations, the sharper the tools become for everyone who follows.

Next: Module 2 — The Taxonomy of Meaning Failures. You spotted the risks. Now you learn to name exactly what kind of failure you’re looking at. When you can classify a breakdown in real time, the repair move becomes obvious.

This is Module 1, Post 3 of Meaning Repair for High-Stakes Teams, a 10-module course on the What Time Binds Substack. New to the course? Start with the Meaning Repair Lexicon and Module 1, Post 1: Why Meaning Fails Silently.

The tools for diagnosing communication breakdowns exist. A team assessment instrument validated across 360 professionals in nine health systems (Cronbach’s α = 0.97) measures exactly the teamwork dimensions where meaning drifts. This post turns that research into something you can use this week.

Why a snapshot, and why now

In Post 1, you met the four phases and the 100%-vs.-12% gap. The framework makes conceptual sense. But concepts don’t repair meaning. Diagnosis does.

The Meaning Risk Snapshot is your team’s baseline. It tells you where meaning is most likely to fail, how your team’s culture shapes that failure, and what to measure again at Day 30 and Day 60 so you can track whether the moves in this course are landing.

D1 Meaning Risk Snapshot Fillable

46.8KB ∙ PDF file

Download

Download

Here’s how to fill one out.

The three parts of the snapshot

The snapshot has three sections, each about five minutes. Fifteen minutes total. You get a quantitative score you can track over time, a cultural context map that shapes how you adapt repair moves in later modules, and a narrative that names your specific targets.

Part 1: Meaning Drift Risk Score — ten Likert-scaled items adapted from validated instruments. This gives you a number.

Part 2: Cultural Context Map — a self-assessment based on Erin Meyer’s eight cultural dimensions. This gives you a picture of where gaps between team members might amplify drift

Example Part 2 Cultural Context Map

68KB ∙ PDF file

Download

Download

.Part 3: Narrative Risk Summary — three open questions. This gives you language.

Part 1: The Meaning Drift Risk Score

These ten items draw on the Team Assessment Tool (Ali et al., 2024), validated across nine U.S. health systems with exceptional reliability, and the Resuscitation-Specific Organizational Culture Instrument (Handley et al., 2024), which measures role clarity, shared mental models, closed-loop communication, team adaptability, and psychological safety. I’ve adapted their clinical language into terms that work for any team—project, operational, family, or community.

Score each item from 1 (strongly disagree) to 5 (strongly agree) based on your team’s typical behavior, not its best day.

1. Shared understanding of terms. When our team uses key terms (project names, status labels, priority levels, role titles), members mean the same thing.

2. Closed-loop communication. When someone makes a request or gives an update, the receiver confirms their understanding back to the sender.

3. Role clarity under pressure. During high-stakes or time-pressured work, every team member knows who is responsible for what.

4. Handoff quality. When work, decisions, or information transfer from one person or shift to another, the receiving person gets enough context to act without guessing.

5. Willingness to voice concern. Team members speak up when they notice something that seems wrong, incomplete, or unclear—even if the person they’d be questioning is more senior.

6. Leader receptivity. When someone raises a concern or questions a decision, the team’s leader(s) respond in a way that encourages continued speaking up.

7. Assumption surfacing. Our team regularly checks whether people are working from the same assumptions about scope, timeline, priorities, or definitions.

8. Debrief practice. After significant events (launches, incidents, major decisions, difficult conversations), our team reviews what happened and what to change.

9. Adaptability when plans change. When new information arrives mid-task, our team can redistribute roles and update shared understanding quickly.

10. Context travel. Information that is clear in one setting (a meeting, a document, a conversation) reliably reaches the people and settings where it’s needed next.

Scoring: Add your ten responses. Range is 10–50.

• 40–50 (Strong grounding): Your risks concentrate where pressure compresses the acceptance phase—handoffs, escalations, fast-moving situations. Focus on precision protocols (Modules 5–7).

• 25–39 (Mixed grounding): Some rhythms work; others drift. Most teams sit here. The narrative section (Part 3) helps you identify which items pull your score down.

• 10–24 (Significant drift risk): Meaning failures are generating rework and frustration on a recurring basis. The suppression-phase work (Modules 3–4) and cultural context map (Part 2) are especially important—the barriers are likely structural, not skill-based alone.

Record your score. You’ll retake this at Day 30 and Day 60.

Personal Repair History (unscored)

Before you move to the Cultural Context Map, take sixty seconds on two questions. These aren’t scored. They’re for your awareness only.

The last time it went badly. Think about the most recent time you raised a concern, asked for clarification, or questioned a decision, and it didn’t go well. Maybe you were dismissed. Maybe the conversation got uncomfortable. Maybe nothing changed. How long ago was that? Was it on this team or a different one?

The feeling that shows up first. When you imagine asking “what do you mean by that?” in your next meeting, what’s the first feeling that arrives: curiosity, caution, or dread?

That feeling is data about your own repair threshold. It was shaped by every team you’ve been on, every organization you’ve worked in, every time you spoke up and got rewarded or punished for it. Your threshold travels with you. It doesn’t reset when you change jobs. A person who has been dismissed for raising concerns across three organizations will experience “what do you mean?” differently than someone whose teams have always welcomed the question, even if both people are now sitting on the same team with the same manager.

This course can lower your threshold over ten weeks. But it helps to know where it sits right now, so you can feel it moving.

Part 2: The Cultural Context Map

Erin Meyer’s research produced a key insight: what matters for communication is the gap between team members on any dimension, not where any single person falls. A team where everyone communicates indirectly has fewer drift risks than a team split between direct and indirect communicators. The distance creates the danger.

For each of eight dimensions, place your team on the spectrum. If your team has significant spread, note the range rather than forcing a single point. The full snapshot instrument includes all eight with meaning-repair implications for each. Here are the dimensions:

1. Communication style: Low-context (explicit, precise) ←→ High-context (implicit, read-between-the-lines)

2. Feedback approach: Direct negative feedback ←→ Indirect negative feedback (softened, private)

3. Leadership expectation: Egalitarian (challenge-the-boss is normal) ←→ Hierarchical (deference to rank)

4. Decision-making: Consensual (discuss until agreement) ←→ Top-down (leader decides after input)

5. Trust basis: Task-based (competence and reliability) ←→ Relationship-based (personal connection over time)

6. Disagreement style: Confrontational (open debate is productive) ←→ Avoidant (confrontation damages relationships)

7. Scheduling orientation: Linear-time (sequential, deadline-driven) ←→ Flexible-time (adaptive, fluid)

8. Comfort with silence: Low (3 seconds feels long) ←→ High (12+ seconds is normal)

What to look for: Circle any dimension where your team spans more than half the spectrum. These are your cultural gap zones. In Module 4, you’ll use this map to decide whether leader-initiated repair, anonymous concern channels, or written pre-work would serve your team better than default verbal protocols.

One note: you’re rating your team as you see it, which means your placement reflects your own cultural lens. The goal isn’t objective measurement. It’s awareness of distance—enough to ask, later, “Would this move work the same way for everyone on my team?”

Quick inventory: where does your team’s meaning travel?

List the three channels where your team’s most consequential conversations happen. These might be live meetings, Slack threads, email chains, shared documents, presentations, or phone calls.

For each one, note whether it allows real-time correction, meaning the other person can immediately say “wait, that’s not what I meant” and you can adjust on the spot.

The channels that allow real-time correction are where repair happens naturally. The channels that don’t (a presentation deck, a policy memo, a recorded announcement, a published article) are where drift compounds fastest, because the acceptance phase has no space to occur.

This matters because teams routinely move their most important conversations from live channels to one-way channels without noticing what gets lost. A decision made in a meeting gets documented in an email. An email gets summarized in a slide. A slide gets presented to a room that has no context for the original conversation. At each step, the opportunity for someone to say “wait — what do we mean by that?” shrinks.

When you see your team moving a consequential conversation from a live channel to a one-way channel, that’s a moment to pause and ask: has everyone confirmed they mean the same thing, or are we locking in a version of shared understanding that was never actually verified?

Part 3: The Narrative Risk Summary

The score tells you how much drift you have. The map tells you the cultural terrain. This section names the specific failure points.

Answer three questions in writing. A few sentences each is enough.

1. The recurring failure. Describe one communication breakdown that has happened more than once on your team. Where does meaning typically diverge? When do people usually discover the gap?

2. The suppressed concern. Think of a time in the last month when you (or someone you observed) noticed confusion or disagreement but did not raise it. What was the context? What made speaking up feel difficult or pointless?

3. The costliest gap. What is the single communication pattern that costs your team the most—in rework, missed deadlines, strained relationships, or poor decisions? Name it as specifically as you can.

These three answers become the raw material for the rest of the course. The recurring failure is where you’ll practice spotting drift (Module 2). The suppressed concern is where you’ll practice repair stances (Module 3). The costliest gap is what your adoption plan (Module 10) should target first.

Your practice rep

Complete the full Meaning Risk Snapshot for your primary team this week. “Primary team” means the group of people whose communication quality most affects your work or life right now—your direct team at work, a project group, a family decision-making unit, a board you serve on.

Fill in all three parts. Record the date and your Drift Risk Score. File it somewhere you’ll find it at Day 30.

If you’re working through this course with a team, have each member complete the snapshot independently before comparing results. The places where your scores diverge are, themselves, meaning drift—and they’re some of the most useful data you’ll generate.

What's next: Post 3 — The Ten-Week Build. Your snapshot gave you the baseline. The next post sets the habit formation expectation for the course and introduces the Transfer Bridge — a prompt that moves repair practice beyond your primary team. Then in Module 2, you'll learn to classify the failures you named in Part 3. The taxonomy of meaning failures gives you the vocabulary to spot drift as it happens, before the cost arrives.

This is Module 1, Post 2 of Meaning Repair for High-Stakes Teams, a 10-module course on the What Time Binds Substack. The complete Meaning Repair Lexicon defines every term used in this course.

One in three patients experiences a diagnosis-related communication failure. In business, independent assessments of identical insurance cases vary by 55%. The pattern is the same everywhere: meaning drifts, and nobody notices until the cost arrives.

Before you read, think of a decision your team made this week where you later discovered someone understood the outcome differently than you did. What happened?

The meeting where everyone agreed

Tuesday afternoon. Seven people around a table—or seven tiles on a screen. The project lead says, “We need to finalize the rollout plan by Friday.” Everyone nods. A few people type notes. The meeting ends on time, which feels like a win.

By Thursday, two things become clear. The engineering lead understood “finalize” to mean lock the technical spec. The marketing director understood it to mean confirm the launch date. The product manager thought “rollout plan” referred to the internal pilot; the sales lead thought it meant the customer-facing release. Nobody was confused during the meeting. Everyone left with a clear picture. The pictures were different.

This is what meaning failure looks like from the inside: total clarity that happens to be pointed in four directions at once.

What this course is about

This course teaches a set of small, repeatable moves for catching and repairing that kind of failure before it compounds. The moves come from decades of research across operating rooms, cockpits, military operations, and organizational teams. They work. The evidence is unusually clear on this point.

Here is the statistic that frames everything we’ll do together over the next ten weeks:

When directed, closed-loop communication is used in operating room emergencies, task completion reaches 100%. A sender states the request. The receiver repeats it back. The sender confirms. Every task gets done.

That practice appears in 12% of interactions.

The gap between 100% and 12% is the entire problem this course addresses. Teams already have the tools. The tools already work. What’s missing is the cognitive and social infrastructure that makes people actually use them—consistently, under pressure, when it matters most.

That infrastructure is what we’re building here.

The four phases of meaning failure

The MRCI framework maps how meaning breaks down and how it gets repaired. Four phases. Every communication failure your team has ever experienced fits somewhere in this sequence.

Phase 1: Drift. Meaning diverges silently. Assumptions go unchecked. A key term means one thing to you and something else to the person across the table. Context that was clear in one conversation doesn’t travel to the next one. The conditions for mutual understanding aren’t met, and nobody notices—because drift doesn’t announce itself. It feels like agreement. That Tuesday meeting? Pure drift.

Phase 2: Suppression. Here is where things get worse. Someone on the team senses the drift. A flicker of doubt: Wait, are we talking about the same thing? They consider saying something. They don’t. Maybe the meeting is moving fast. Maybe the person who would need correcting is senior. Maybe they’ve raised concerns before and nothing changed, so why bother. The doubt gets swallowed, and the drift continues unchecked.

Suppression is where most communication programs lose the game. They teach people what to say. They don’t address the forces that keep people from saying it.

Phase 3: Repair Activation. Someone speaks the first sentence. “Can I check something—when we say finalize, do we mean the spec is locked, or the date is confirmed?” That sentence is a repair move. It breaks the silence, surfaces the drift, and creates a moment where meaning can be realigned.

This transition—from suppression to activation—is the single point this course targets most aggressively, because it is where proven practices most consistently fail to get used.

Phase 4: Outcome. Meaning is restored. Or it isn’t. Either way, the result feeds back into the system. If the repair works—the team realigns, the ambiguity gets pinned, the meeting produces a shared picture—it becomes slightly easier for the next person to speak up next time. If the repair fails—the concern gets dismissed, the speaker gets a sideways look, the meeting steamrolls forward—it becomes harder. Failed repairs teach teams to suppress. Successful repairs teach teams to repair.

The cycle runs continuously. It is running in your team right now.

A note about this course’s own language

The terms I just introduced (drift, suppression, repair activation, outcome) are themselves subject to the process they describe. You read those words and built your own interpretation of what each one means. That interpretation was shaped by your experience, your professional context, and the conversations about communication you’ve had before this one.

For example: later in this course, I’ll talk about “shared definitions.” If you read that phrase and imagine I mean everyone in the room must agree on one permanent, universal definition of a key term before any work can begin — that’s drift happening right now, between us, on a concept about drift. What I actually mean is narrower and faster: before a decision is made, the people in the room check whether they’re using the same keyword to point at the same thing. That check takes ten seconds. The habit takes months.

I’m flagging this early because the pattern is predictive. Every term in the Meaning Repair Lexicon will land differently depending on what you bring to it. That’s normal. It’s also the exact phenomenon this course exists to address. When a term in this course feels wrong to you, that friction is data; it means your working definition, and mine haven’t been grounded yet. Treat that friction as an invitation to check, not a reason to dismiss.

Why drift is invisible: the grounding problem

In 1991, Herbert Clark and Susan Brennan published a theory of communication that explains why meaning fails the way it does. Their insight was deceptively simple: understanding doesn’t happen automatically when words leave someone’s mouth. It has to be built, move by move, between the people in the conversation.

Clark and Brennan described three requirements for what they called “grounding”—reaching mutual understanding:

Presentation. One person says something. States a plan. Makes a request. This is the part we’re all good at.

Acceptance. The other person provides evidence that they understood. A nod. A paraphrase. A question. A repeat-back. This is the part we skip.

Grounding criterion. Both people reach a mutual belief that understanding is sufficient for the current purpose. This is the part we assume happened when it didn’t.

Closed-loop communication—the practice with the 100% completion rate—formalizes the acceptance phase. The sender states the message. The receiver repeats it back in their own words. The sender confirms or corrects. Three steps. When all three happen, tasks get completed, and meaning holds.

When teams skip the acceptance phase (which is most of the time), they’re operating on an assumption of shared understanding that may or may not be accurate. In a low-stakes conversation, the cost of a wrong assumption is small. In an operating room, a cockpit, an emergency department, a product launch, a board decision, a custody negotiation—the cost can be enormous.

The WHO Surgical Safety Checklist, which formalizes a version of this grounding process, reduces mortality by 25%. Global compliance sits at 73%. The most meaning-critical phase of the checklist—the Sign Out, where the team confirms what was done—drops to 62%.

The tools exist. They work. The challenge is making them stick.

The 12% question

Why do teams suppress the use of practices they know are effective? The evidence points to a few reinforcing forces, and none of them involve laziness or ignorance.

Speed compresses the acceptance phase. Under time pressure, the grounding criterion gets lowered. “Good enough” understanding replaces verified understanding. This is rational in the moment and expensive over time.

Hierarchy suppresses repair activation. A 2024 study of 730 nurses found that power distance orientation significantly predicted whether nurses perceived speaking up as futile. When the person who needs correcting outranks the person who spotted the error, the calculus changes. The drift continues.

Silence is socially learned. A three-year longitudinal study at a German automotive plant found that organizational silence spreads through storytelling. People learn to stay quiet by hearing what happened to others who spoke up—even if those stories are years old, even if the manager in the story has long since left. Silence becomes cultural infrastructure, inherited through narrative.

Repeated futility produces acquiescent silence. When speaking up fails to produce change again and again, people stop trying. Two experiments with 654 participants demonstrated this pattern: voice futility produces a silence that mirrors learned helplessness. People don’t just choose not to speak. They lose the expectation that speaking could matter.

These forces operate simultaneously. They explain the 12%. They also explain why telling teams to “communicate better” doesn’t move the number.

The boundary this course is honest about

There is a condition that sits before drift, and it’s worth naming early.

Sometimes a person enters a conversation with a definition so settled that no verification attempt will register. They aren’t suppressing a repair move; they’ve decided repair isn’t needed. The word means what it means. The question was closed before it was asked.

I call this meaning refusal, and it’s the boundary of what meaning repair can reach.

Meaning refusal can look like prejudice, certainty, expertise, or exhaustion. It can come from a lifetime of being ignored when you raised concerns, until asking “what do you mean?” sounds like one more institution demanding you justify yourself. It can come from a position of genuine authority where you’ve been right so often that checking feels unnecessary. It can come from a fixed frame about a loaded term — “AI,” “equity,” “leadership,” “accountability” — where the definition was locked in years ago, and new information gets filtered through it rather than allowed to change it.

This course works in the space of engaged disagreement — where people differ but are willing to check. Recognizing when you’ve hit meaning refusal is itself a skill, and it saves you from spending repair energy where it can’t produce a result. We’ll return to this distinction in Module 4, when we look at suppression and silence.

For now, hold the question: when you imagine the person on your team who is hardest to reach with a clarifying question, is the barrier fear (suppression) or certainty (refusal)? The repair move for each is different.

What we’re building

Over the next ten weeks, you’ll build a set of tools—a Meaning Repair Operating System—drawn from your own workflows and conversations. Each module introduces one named move. Each move is small enough to use in a live meeting, a handoff, a Slack thread, or a family dinner.

The course follows the four phases. Modules 1 and 2 address Drift: how to spot it, name it, and diagnose where your team is most vulnerable. Modules 3 through 7 focus on Repair Activation: the specific sentences, protocols, and meeting moves that break silence and restore shared meaning. Modules 4 and 9 tackle Suppression and Outcome: the leadership practices and after-action reviews that determine whether repair becomes a habit or a one-time event. Module 10 builds the adoption plan that carries these moves past the end of the course.

You don’t need to learn something entirely new. You need to build the conditions for consistent use of what already works.

That’s a more tractable problem than it sounds. And it starts with a diagnostic.

Next post: The Meaning Risk Snapshot → A step-by-step assessment of where meaning is failing on your team right now, with a quantitative baseline you’ll re-measure at Day 30 and Day 60.

This is Module 1, Post 1 of Meaning Repair for High-Stakes Teams, a 10-module course on the What Time Binds Substack. If you haven’t already, start with the Meaning Repair Lexicon—your reference card for the language of meaning repair.

This module includes an interactive course orientation. Tap the image above to explore the full MRCI framework, the 4-phase model, and the 10-module course map before you begin.

Learning Objective

Learners diagnose their team’s current communication vulnerabilities using a structured, evidence-based assessment and establish a quantitative baseline they will re-measure at Day 30 and Day 60.

Recall Prompt (Prior Knowledge Activation)

Before you read, think of a decision your team made this week where you later discovered someone understood the outcome differently than you did. What happened?

Substack Post Sequence

Post 1: Why Meaning Fails Silently (Concept + Why)

1,200–1,500 words | ~10 min read

Introduces the MRCI 4-phase model (Drift → Suppression → Repair Activation → Outcome). Uses the 100%-vs.-12% closed-loop statistic as the course’s motivational anchor: teams don’t need new tools, they need consistent use of proven ones. Explains meaning drift using Clark & Brennan’s grounding theory. Frames the course’s purpose: building cognitive infrastructure for consistent use of what already works.

Post 2: The Meaning Risk Snapshot (How + Practice)

1,000–1,400 words | ~8 min read

Step-by-step instructions for completing the Meaning Risk Snapshot. Includes 5–10 adapted TAT items (Ali et al., 2024; Cronbach’s α = 0.97) scored on a Likert scale for quantitative baseline. Adds a Cultural Context field using Meyer’s eight dimensions as a lightweight self-assessment (power distance, communication directness, comfort with silence). Practice rep: complete the snapshot for your primary team.

Post 3: Repair Rep + Discussion

600–800 words | ~5 min read

Sets the habit formation expectation: “This is a 10-week build. You will not master these moves by Module 3. You will feel awkward. That’s the signal that you’re building a new habit, not that you’re failing.” Transfer Bridge prompt: Where outside your current work role would this diagnostic have changed an outcome this week? Discussion thread opens.

Deliverable

D1: Meaning Risk Snapshot — Completed team assessment with TAT-adapted quantitative items, cultural context field, and narrative risk summary. Scored baseline to be repeated at Day 30 and Day 60.

Example Part 2 Cultural Context Map

68KB ∙ PDF file

Download

Download

D1 Meaning Risk Snapshot Fillable

46.8KB ∙ PDF file

Download

Download

Deliverable Reflection Prompts

• What strategy did I use to complete this deliverable?

• What was most difficult and why?

• What would I do differently next time?

Validated Instruments Referenced

Team Assessment Tool (Ali et al., 2024), Meyer’s Culture Map dimensions, ROCI subscales (Handley et al., 2024)

When teams share a name for a behavior, they can see it, call it out, and reinforce it. Research on team communication adoption found that naming practices creates recognition and reinforcement—”When you call it something… it gives that opportunity to be present, then to really recognize like, ‘Oh, this is a strategy that I’m employing’” (Albright et al., 2025). Shared language is itself an intervention.

This lexicon is the course’s naming infrastructure. Every protocol, move, template, and concept below has a name short enough to use in a live conversation. You don’t need to memorize all of them before Module 1. Start with the four phases. The rest will arrive one module at a time.

Subscribe now

The Four Phases

These are the backbone of the MRCI framework. Everything in this course maps to one of these phases.

Drift — Meaning diverges silently. Assumptions go unchecked, terms go undefined, context collapses. The grounding criteria for mutual understanding are not met, but no one notices yet. Drift is the default state of all communication under pressure. (Modules 1–2)

Suppression — Someone detects the drift but does not speak. Silence spreads through stories about what happened to others who raised concerns. Repeated voice futility teaches people to stop trying. Psychological safety erodes over time without active maintenance. Suppression is not passive—it is an active, self-reinforcing organizational process. (Modules 3–4)

Biographical Suppression Threshold — The cumulative effect of an individual's history of punished or ignored repair attempts across organizations and contexts. This threshold is portable — it travels with the person from team to team, job to job — and moderates how they receive repair attempts in any new environment, independent of the current team's actual psychological safety level. A person with a high biographical threshold may resist repair moves that would land easily with someone whose history includes more positive repair experiences. The threshold is not fixed; it can be lowered through repeated non-punitive repair reception over time. (Module 1, Module 3, Module 4)

Repair Activation — Someone speaks the first sentence. A repair move is deployed. This is the transition the course disproportionately targets, because it is where existing approaches most consistently fail. (Modules 3–7)

Outcome — Meaning is restored, or it isn’t. The result feeds back into the system. Successful repair builds psychological safety and makes the next repair easier. Failed repair reinforces suppression and makes the next silence more likely. (Modules 9–10)

Meaning Refusal — A pre-Phase 1 condition in which a person's definition of a key term is so fixed that verification attempts cannot register. The person has exited the space of engaged disagreement. Meaning refusal can result from accumulated suppression experiences across a career (biographical suppression), from deeply held convictions, or from expertise-based certainty. MRCI's repair moves operate within the space of engaged disagreement; recognizing meaning refusal is the skill of knowing when repair energy should be redirected rather than increased. (Module 1, Module 4)

The Six Failure Types

These are the categories of meaning breakdown your team will learn to spot and name. Introduced in Module 2.

Referent Ambiguity — A word or phrase points to different things for different people. “The client” means the project sponsor to you and the end user to your colleague. Neither of you knows you’re talking about different people.

Scope Drift — The boundaries of a task, decision, or conversation shift without anyone naming the shift. A meeting about launch timing becomes a meeting about product features. The original question is never answered.

Assumption Gap — A piece of context that one person holds but has not shared, because they believe everyone already knows it. The most dangerous assumption gaps feel too obvious to state aloud.

Hinge-Term Confusion — A term that carries real operational weight means something different to different team members. “Soon,” “priority,” “escalate,” “reviewed,” “approved”—these hinge terms pivot decisions, and their ambiguity is invisible until a cost reveals it.

Status Misalignment — People disagree about where a task, project, or decision stands—in progress vs. complete, pending review vs. approved, my responsibility vs. yours—without realizing they disagree.

Context Collapse — Information that was available in one setting (a meeting, a document, a conversation) does not travel to the next setting where it is needed. The meaning was clear once; it collapsed in transit.

The Repair Moves

These are the named actions you deploy in real time. Each is short enough to use mid-sentence, mid-meeting, mid-handoff.

Repair Stances (Module 3)

The first sentence of any repair. The hardest part. Three patterns:

Hypothesis Opener — “I want to check my understanding…” You state what you believe to be true and invite correction. Frames the repair as collaborative verification, not challenge.

Curiosity Opener — “Help me see what I’m missing…” You name your own incomplete picture and ask for the piece you lack. Lowers the stakes by centering your gap, not the other person’s error.

Escape-Hatch Opener — “I might be wrong, but…” You offer your observation with an explicit exit if it’s off-base. Gives the other person room to redirect without confrontation.

Precision Protocols (Module 5)

Three micro-protocols for repairing meaning at the word level:

Term Pinning — Stopping the conversation to define an ambiguous term. “When we say priority, I mean it ships this sprint. Does that match your understanding?” Converts a hinge term from vague to operational.

Zoom-In Word — Requesting specificity when language is too abstract to act on. “When you say soon, can you give me a concrete timeline?” Forces vague language into actionable form.

Grounding Verification — Confirming mutual understanding using a structured check: What was presented? What evidence of acceptance was obtained? Was the grounding criterion met? Does repair remain needed? Formalizes the acceptance phase that most conversations skip.

Meeting Moves I (Module 6)

Three moves for repairing meaning inside live meetings:

Clarity Minute — A 60-second structured pause at the meeting midpoint. The facilitator asks: “Let me check—what have we agreed to so far?” Surfaces divergent understanding before it compounds.

Term Pinning Live — Flagging and resolving an ambiguous term in real time during a meeting. The live version of the Module 5 protocol, adapted for the pace and social dynamics of group conversation.

Who/They Resolution — Replacing vague pronouns with specific names and roles. “They should handle that” becomes “[Name] will [specific action] by [date].” Converts diffuse ownership into traceable commitment.

Meeting Moves II (Module 7)

Three moves for repairing meaning around decisions:

Scope Check — Detecting when a conversation has drifted from its stated purpose. “Are we still deciding [original question], or has the question changed?” Names the drift so the team can choose whether to follow it or return.

Decision Framing — Using the Mediating Assessments Protocol to decompose a decision: define criteria independently, assess facts independently, then delay holistic judgment until all assessments are complete. Delays intuition without eliminating it.

Next-Step Precision — Closing every decision with a documented statement of who does what by when, using assigned roles. Converts agreement-in-principle into trackable action.

The Leadership Protocols

Tools for leaders who shape the climate where repair either happens or dies. Introduced in Module 4.

Silence Audit — Identify the 2–3 stories your team tells about what happened when someone raised a concern. These stories are the suppression infrastructure. Name them, then write counter-narratives: what you, as a leader, would do differently.

Visible Response Protocol — When someone raises a concern, three steps: (a) acknowledge it in the moment, (b) name the next step, (c) close the loop within a defined timeframe—even if the answer is “we considered it and decided not to change.” Directly counters the mechanism that produces learned helplessness from repeated voice futility.

PS Micro-Behavior Tracker — A weekly observation tool. Select 8–10 observable micro-behaviors associated with psychological safety (questions asked, uncertainty admitted, disagreements voiced, information volunteered) and tally them during one meeting per week. Provides behavioral data instead of self-report.

Counter-Narrative — A story you tell deliberately to replace a suppression story. If the team story is “Last time someone flagged a problem, they got sidelined,” the counter-narrative is a concrete example of a concern being raised, heard, and acted on—or at least acknowledged.

The Decision Tools

Structures for preventing the re-deciding loops that erode meaning. Introduced in Module 7.

DACI Roles — Driver (owns the process), Approver (makes the final call), Contributors (provide input), Informed (need to know the outcome). Assign before the decision begins, not after.

Decision Log — A running record: Decision ID, date, context, options considered, reasoning, who decided, and review date. Makes decisions visible and retrievable. Roughly half of decisions made in meetings are never followed through because ownership and documentation are unclear. The log is the forcing function.

Decision Hygiene Checklist — A protocol card for clean decisions: Decompose into criteria. Assess independently before group discussion. Take the outside view. Delay holistic judgment. Assign a decision observer. Document with rationale. Set a review date.

MAP (Mediating Assessments Protocol) — Define independent criteria in advance, make fact-based assessments independently, then delay holistic judgment until all assessments are complete. The formal structure behind Decision Framing.

The Debrief Tools

Structures for reviewing what happened—especially the communication events teams naturally avoid. Introduced in Module 9.

Debrief Paradox — The finding that events containing critical communication breakdowns are significantly more likely to go undebriefed than events without communication breakdowns. The very events that most need review are systematically avoided because the confusion persists and inhibits structured discussion.

Hot Debrief — 5–10 minutes, immediately post-event. Adapted from the STOP5 format for communication: Summarize what was communicated and intended → Identify what was understood correctly → Pinpoint where meaning diverged → Set action points for communication change.

Cold Debrief — 30–60 minutes, days after the event. Uses the Timeline Debriefing Tool to reconstruct the communication sequence and map MRCI phases: When did drift occur? What suppression behaviors appeared? What triggered repair? What was the outcome?

Communication Trigger Checklist — The explicit list of conditions that warrant a communication-focused debrief: ambiguity discovered after the fact, concerns raised but not acted on, assumptions that turned out to be wrong, or hierarchy that prevented someone from speaking up.

PEARLS — An alternative debrief structure with four phases: Reactions (how did that feel?), Description (what happened?), Analysis (blending self-assessment with directive feedback), and Summary (what will we do differently?). Particularly useful for teams that find open-ended debrief formats too unstructured.

The Measurement Concepts

How we track whether meaning repair is actually happening. Introduced primarily in Modules 1 and 10.

Meaning Risk Snapshot — The baseline diagnostic completed in Module 1 and repeated at Day 30 and Day 60. Combines adapted Team Assessment Tool items (quantitative, Likert-scaled) with a cultural context field and a narrative risk summary.

Leading Indicators — Metrics that predict future communication quality: structured handoff compliance, speaking-up behavior rates, debrief completion rates, psychological safety scores. Updated frequently.

Lagging Indicators — Metrics that confirm past communication quality: communication-related adverse events, rework metrics (clarification requests, re-dos, meeting-to-resolution ratio), escalation-to-resolution time. Updated less frequently.

Delta Values — A scoring method: percentage of positive responses minus percentage of negative responses. Reveals nuanced shifts that positive-only scoring misses. Applied to the 5-item communication climate pulse survey.

Rework Loop — Any cycle where work is redone because meaning failed the first time: clarification requests, task re-assignments due to misunderstanding, meetings called to re-decide what was already decided. The operational cost of unrepaired drift.

Communication Quality Scorecard — The dashboard combining leading and lagging indicators with trend tracking. The course’s measurement centerpiece.

The Adoption Concepts

How repair moves become habits instead of one-time experiments. Introduced across the course, formalized in Module 10.

COM-B Model — Every behavior requires three things: Capability (knowledge and skills), Opportunity (environmental and social support), and Motivation (reflective and automatic drivers). When a repair move isn’t happening, COM-B diagnoses which ingredient is missing.

Habit Laddering — Starting with one practice for 6–8 weeks before adding complexity. Research shows starting slowly and increasing gradually maintains habits 1.5 times longer than starting at full intensity. The course’s recommended adoption sequence.

Naming as Infrastructure — The principle that giving a practice a shared name is itself an intervention. When you call it a “Clarity Minute,” it becomes visible, recognizable, and reinforceable. Every term in this lexicon serves this function.

EAST Framework — Design heuristic for nudges and prompts: make the desired behavior Easy, Attractive, Social, and Timely. Applied to how repair moves are cued in daily workflows.

Transfer Bridge — The prompt at the end of every module asking: “Where outside your current work role would this move have changed an outcome this week?” Converts each module from workplace-specific to life-applicable.

The Course Structures

Terms for the course’s own learning design.

Repair Rep — The spaced repetition post published as Post 3 of each module. Revisits concepts from 1–2 prior modules with a new scenario. Based on evidence that spaced repetition produces 80% retention at 30 days versus 20% with traditional methods.

Cost Anchor — The one-sentence statistic at the opening of each module connecting the topic to a concrete operational or human cost. Grounds abstract concepts in real consequences.

Recall Prompt — The 2–3 sentence prior-knowledge activation at the start of each module’s first post. Creates a prediction the reading can confirm or disconfirm.

Worked Repair — A two-column example showing what happened (left) and the repair move with annotations (right). Appears in Modules 3–7 before learners attempt their own repair moves.

Progress Map — Self-assessment checkpoints at Modules 4, 7, 9, and 10 with calibrated items like: “At this point, I can diagnose a meaning failure within 60 seconds: never / sometimes / reliably under pressure.”

MR-OS (Meaning Repair Operating System) — The collective name for all 10 deliverables. Each deliverable is a component the learner builds from their own workflows and retains as a permanent team resource.

The Key Theoretical Anchors

Concepts from the research traditions the course draws on. You don’t need to cite these in conversation—but knowing where the moves come from strengthens your understanding of why they work.

Grounding Theory (Clark & Brennan, 1991) — Communication requires a presentation phase (speaker presents an utterance), an acceptance phase (the partner provides evidence of understanding), and a grounding criterion (mutual belief of sufficient understanding). Most communication failures happen because the acceptance phase is skipped.

Psychological Safety — The shared belief that the team is safe for interpersonal risk-taking. Starts high in new teams and declines over time without active maintenance. Leader behavior predicts 52% of the variance. Not the absence of conflict—the presence of conditions where people can speak without fear.

Coactive Vicarious Learning (CVL) — Learning to stay silent by hearing stories about what happened to others who spoke up, rather than from direct personal experience. The mechanism by which suppression becomes cultural.

Acquiescent Silence — Silence that results from learned helplessness: speaking up has failed so many times that the person stops trying, even when new opportunities arise. Distinct from silence driven by fear or strategic withholding.

Noise (Kahneman, Sibony, & Sunstein) — Unwanted variability in judgments that should be identical. When two people make the same decision differently for no defensible reason, that is noise. Decision churn—re-deciding what was already decided—is noise made visible in team behavior.

The Cultural Adaptation Terms

Concepts for adapting repair moves across cultural contexts. Woven into the course from Module 1.

Power Distance — The degree to which less powerful members of a team accept and expect that power is distributed unequally. In high-power-distance teams, subordinates are less likely to initiate repair with superiors. The course offers alternative pathways: leader-initiated repair and anonymous channels.

High-Context / Low-Context Communication — High-context cultures (e.g., Japan, China, much of Asia and Africa) rely on implicit, relationship-based communication where meaning lives between the words. Low-context cultures (e.g., U.S., Germany, Scandinavia) rely on explicit verbal statements. Neither is better. But undetected drift is more likely in high-context settings, and direct repair moves may feel confrontational.

Cultural Gap — What matters is not where any single culture falls on a dimension, but the distance between team members on that dimension. A team where everyone is high-context has fewer drift risks than a team where half are high-context and half are low-context.

Safety Listening — An alternative to “safety voice” for high-power-distance teams. Instead of expecting subordinates to speak up, leaders actively solicit concerns. The repair activation comes from the top, not the bottom.

Face-Saving Mechanism — Any repair pathway that allows a person to surface a concern without publicly contradicting someone of higher status. Written pre-work, anonymous channels, private 1:1 conversations, and third-party facilitation are all face-saving mechanisms.

This lexicon is a living document. It will be updated after each module with new terms, refined definitions, and examples drawn from the course community’s discussions. Bookmark it. Return when you encounter a term you’ve forgotten. Use the names in your meetings, your handoffs, your conversations. The names are the infrastructure.

Next: Module 1 — The Meaning Risk Snapshot → Where is meaning failing right now?

The question that started this

My friend Mario called me a few years ago with that particular energy people get when they’ve found the thing they want to build. He had a startup idea—a podcast, a framework, a platform. He read me his taglines and goals. In most cases, Mario’s ambitions are strong. These were planetary. Change the world. Shift the paradigm. Transform how people show up. The language was big, bright, and aimed at the horizon.

I listened. I asked questions. And the thing I kept bumping into wasn’t whether Mario’s vision was good—it was that every key term in his pitch meant something different depending on which sentence it landed in. “Framework” meant a personal philosophy in one breath and a scalable product in the next. “Unarmored” meant vulnerability in one context and authenticity in another, and those aren’t the same thing. The goals were real. The words holding them together were shifting under the weight.

Mario went on to build Unarmored Framework—a podcast worth your time. But those early conversations stuck with me, because they sounded exactly like something I kept hearing in a completely different setting.

Subscribe now

A senior leader in a meeting I attended around the same time said, “We need more accountability on this team.”

Everyone nodded. The meeting moved on.

Over the following two weeks, three people each defined “accountability” differently. One built a tracking dashboard. One started scheduling weekly check-ins. One began documenting who missed which deadlines, building a case. Same word. Same room. Same nod of agreement. Three incompatible projects, all running simultaneously, each one perfectly rational given the meaning its owner had assigned to a single word nobody thought to define.

The rework cost about two weeks and a measurable amount of trust. And nobody had done anything wrong. The word had done it.

Mario pitching his startup. A leadership team aligning on “accountability.” A family agreeing to “be more supportive.” The pattern is identical every time: the word is in the room, everyone nods, and the meanings scatter the moment people walk out the door.

That pattern is why I started writing the What Do You Mean? series. And it’s why, over the past couple of years, I’ve been building something larger.

What I’ve been researching

If you’ve been reading What Do You Mean? on the What Time Binds Substack, you’ve watched me take apart one loaded word at a time—terms like accountability, boundaries, support, alignment, urgent—and show how each one fractures into competing meanings the moment pressure arrives. Every installment follows the same move: name the word, show how it splinters, pin a workable definition, and hand readers a script they can use in their next conversation.

Those posts were the fieldwork. Each one surfaced the same pattern: teams, families, and organizations don’t fail because they lack information. They fail because they assume shared meaning where none exists. The word is in the room. The meaning isn’t.

That pattern kept leading me back to the same question: is this a communication problem or an infrastructure problem? Are people bad at talking to each other, or is something structural making it nearly impossible to catch meaning failures before they compound?

The research says it’s the second one.

What the paper found

I spent the past several months conducting a formal scoping review—a structured, systematic survey of the existing research—to find out what scholars across multiple disciplines already know about how teams build, lose, and restore shared meaning under pressure.

The paper, titled "Meaning Repair as Cognitive Infrastructure for High-Stakes Teams: A Scoping Review and Integrative Framework," is now available on SSRN as a preprint.

Here’s what the review involved. Following PRISMA-ScR guidelines—the reporting standard for scoping reviews—I searched five academic databases: PsycINFO, Web of Science, Scopus, PubMed, and Communication & Mass Media Complete. The search covered eight overlapping domains: grounding theory, conversational repair, psychological safety, voice and silence, sensemaking, shared mental models, team cognition, high-reliability organizing, and cognitive overconfidence. I screened roughly 2,340 records, conducted full-text review on 262 sources, and included 131 in the final synthesis—68 empirical studies, 22 meta-analyses and systematic reviews, 27 theoretical papers, and 14 foundational monographs.

The review wasn’t looking for a single headline finding. It was mapping a terrain. And what it revealed is that at least eight academic disciplines have been studying pieces of the same problem without talking to each other.

Linguists have mapped the micro-mechanics of how people repair misunderstandings in conversation. Psycholinguists have theorized how mutual understanding gets built move by move. Organizational behavior researchers have shown that psychological safety determines whether people voice concerns or swallow them. Safety scientists have documented how structured communication protocols prevent catastrophic errors in operating rooms and cockpits. Team cognition researchers have demonstrated that shared mental models predict performance. Sensemaking scholars have shown how meaning collapses under extreme stress.

Each tradition has a piece. None of them has the whole picture. The paper’s central contribution is connecting those pieces into a single framework.

The MRCI framework

The framework is called Meaning Repair as Cognitive Infrastructure (MRCI). The core argument: meaning repair isn’t a communication skill you can train in an afternoon workshop. It’s a form of infrastructure. Like physical infrastructure—roads, power grids, water systems—it’s invisible when it works and catastrophic when it fails. And like physical infrastructure, it requires continuous maintenance, institutional support, and investment.

MRCI models how meaning breaks down and gets repaired through four phases:

Drift. Meaning diverges silently. Assumptions go unchecked, key terms go undefined, and context that was clear in one conversation doesn’t travel to the next. The conditions for mutual understanding aren’t met, and nobody notices—because drift feels like agreement.

Suppression. Someone detects the drift. A flicker of doubt. They consider saying something and don’t. Maybe the meeting is moving fast. Maybe the person who’d need correcting is senior. Maybe they’ve spoken up before, and nothing changed. The research here is striking: silence spreads through storytelling, and repeated futility produces a pattern that mirrors learned helplessness. People don’t just choose to stay quiet. They lose the expectation that speaking could matter.

Repair Activation. Someone speaks the first sentence. “Can I check something—when we say finalize, do we mean the spec is locked, or the date is confirmed?” That sentence is a repair move. Small. Specific. And, according to the evidence, remarkably effective when it actually happens.

Outcome. Meaning is restored, or it isn’t. The result feeds back into the system. Successful repair builds the conditions for more repair. Failed repair reinforces suppression.

The paper advances ten falsifiable propositions organized around these phases—testable claims about when drift accelerates, what predicts suppression, what activates repair, and how outcomes feed back into team culture. It also identifies the major measurement gaps: no validated instrument currently exists that measures meaning repair directly. That’s a problem and an opportunity, and it’s one of the things the course is designed to address.

The number that frames everything

One finding from the review anchors the entire project.

When closed-loop communication is used in operating room emergencies, the sender states a request, the receiver repeats it, the sender confirms, and task completion reaches 100%. Every task gets done. That practice appears in 12% of interactions.

The gap between 100% and 12% is not a knowledge gap. The teams know how to do it. It’s an infrastructure gap. The conditions that make people consistently use what they know—psychological safety, time protection, leadership modeling, cultural permission—aren’t being maintained.

That gap is what the course is built to close.

What I’m building on Substack

The What Do You Mean? series was the prep work. The SSRN paper is the evidence base. The next phase is the applied work: a 10-module course called Meaning Repair for High-Stakes Teams, delivered right here on the What Time Binds Substack.

The course translates the framework into a set of named, repeatable moves—small enough to use in a live meeting, a handoff, a Slack thread, a family conversation. Each module introduces one move. Each move maps to a phase of the MRCI framework. Over ten weeks, you build what I’m calling a Meaning Repair Operating System: a set of protocols, scripts, and habits drawn from your own workflows and relationships.

Here’s the sequence, broadly:

Modules 1–2 address Drift. You’ll learn to spot it, name it, and diagnose where your team is most exposed. The first tool is the Meaning Risk Snapshot—a structured assessment that gives you a quantitative baseline you’ll re-measure at Day 30 and Day 60.

Modules 3–7 focus on Repair Activation. This is where the course spends the most time, because it’s where the evidence says teams most consistently fail. You’ll learn stance-first language for speaking the first sentence when you sense drift. You’ll practice term pinning—stopping a conversation to define the word that’s pulling everyone in different directions. You’ll work with three meeting protocols (the Clarity Minute, live term pinning, and Who/They Resolution) designed to catch meaning failures in real time.

Modules 4 and 9 tackle Suppression and Outcome. Module 4 is about leadership: how silence gets built into team culture, and what leaders can do to dismantle it. Module 9 covers after-action reviews—structured debriefs that close the feedback loop so that what your team learns from a repair actually persists.

Module 10 builds the adoption plan. Research on habit formation is clear that starting with one practice for six to eight weeks before adding complexity maintains habits significantly longer than starting at full intensity. Module 10 helps you design a realistic rollout, not a wish list.

Every module produces a deliverable: a completed protocol card, a diagnostic, a leadership stance pack, a scorecard. By the end, you have a fully operational system built from your context and your team’s language.

What I hope you’ll get from this

I’ll be direct about what this course is and isn’t.

It’s not a communication skills workshop. It doesn’t teach you to “be a better listener” or “communicate more effectively” in some vague, aspirational sense. The evidence is clear that telling teams to communicate better doesn’t change behavior. What changes behavior is building the specific conditions—psychological safety, time protection, shared vocabulary, visible leadership modeling—that make proven practices actually get used.

It’s not a one-size-fits-all program. The course includes a cultural adaptation thread from Module 1, because research on power distance, communication directness, and silence norms makes clear that repair moves that work in a flat, direct-communication culture can backfire badly in a hierarchical or high-context one. You’ll adapt each protocol to your team’s actual context.

What I hope you get: a small set of moves you can actually use under pressure. A shared vocabulary your team can adopt—because the research shows that when teams have a shared name for a behavior, they can see it, call it out, and reinforce it. A diagnostic you can re-run quarterly. And the confidence that comes from knowing the evidence base behind what you’re practicing.

The research is real. The protocols are grounded. The moves are small on purpose. And the course is built for people who are already busy, already under pressure, and already tired of being told to “just communicate better.”

What comes next

The next post is the Meaning Repair Lexicon—a living glossary of every term, protocol, and named move in the course. Bookmark it. You’ll return to it often. It grows with each module, and it serves a purpose beyond reference: shared language is itself an intervention. When you can name a thing, you can see it. When your team can name it together, you can repair it together.

After the Lexicon, Module 1 begins. We start with a diagnostic.

I’ve spent a long time sitting with that question—What do you mean?—and following it wherever it led. It led through linguistics, organizational behavior, safety science, social psychology, and team cognition. It led to an SSRN paper and a framework with ten testable propositions. And now it leads here: to a set of tools I believe are worth building together.

Mario’s vision was real. So was the senior leader’s desire for accountability. So is every team’s wish to align, coordinate, and move fast. The ambition isn’t the problem. The problem is that the words carrying the ambition mean different things to the people who have to execute on them—and nobody stops to check.

This course is the stop. The check. And the infrastructure that makes checking a habit instead of an accident.

Let’s build it.

Meaning Repair as Cognitive Infrastructure for High-Stakes Teams is available on SSRN.

The What Do You Mean? series archive is on the What Time Binds Substack.

Next post: The Meaning Repair Lexicon — your reference card for the language of meaning repair.