The journal

Team Performance · 9 July 2026 · 5 min read

Mission Control Communication Discipline for Everyday Meetings

Bring Mission Control communication discipline into everyday meetings with clear messages, useful read-backs, explicit decisions and reliable handovers.

Written by Sarah Murray

Mission Control Communication Discipline for Everyday Meetings

Photograph: MSFC Teams at MSFCC Moniter Launch Conditions for Crew 1 Mission — NASA, public domain

The meeting ends on time, yet three people leave with different versions of the decision. One believes work is approved, another thinks approval is conditional, and a third is waiting for a document nobody has been asked to produce. The problem is not necessarily a lack of discussion. It is incomplete communication.

A Mission Control lens encourages attention to message purpose, ownership and confirmation. Everyday meetings do not need specialist jargon or a rigid script. They need a few shared disciplines that help people recognise what has changed, what they must do and whether others understood the same thing.

State what the conversation is for

At the start of an agenda item, say whether the group is sharing information, testing an idea or making a decision. These are different tasks. If participants think they are exploring options while the chair thinks they are approving one, even a thoughtful discussion can end in confusion.

Name the decision owner where a choice is required. Explain what input they need and any constraints that are already settled. This lets colleagues focus their contribution. It also prevents the room drifting into a search for unanimous agreement when the actual responsibility sits with one authorised person.

Do not use urgency as a substitute for purpose. A brief meeting still needs a clear question. If the request is simply for awareness, consider whether a written update would do the job. Reserve shared discussion for work that genuinely benefits from people thinking or deciding together.

Put the important message first

Lead with the issue or action, then supply the context needed to understand it. A listener should not have to wait through a long account to discover that a deadline is at risk. This is especially important when the information changes what somebody else should do next.

Distinguish observations, interpretations and requests. An overdue approval is an observation; a belief that the sponsor is withdrawing support is an interpretation; a request for someone to contact the sponsor is an action. Keeping these separate helps the team investigate without treating an untested explanation as established fact.

Use ordinary language. Abbreviations familiar within one function may mean little elsewhere. If a term has several possible meanings, define it for the task. Precision is not the same as technical complexity; it is giving the recipient enough clarity to respond appropriately.

Close the loop where misunderstanding matters

For a critical action, name the recipient and ask them to confirm what they will do and by when. The sender then checks the summary. This closes the communication loop rather than assuming that a message delivered is a message understood. Use it selectively where the consequences justify the attention.

A confirmation should reveal interpretation, not merely receipt. A nod or a brief acknowledgement may show that someone heard you without showing what they understood. Ask for a short account of the next step when the action is consequential, unfamiliar or dependent on a precise condition.

Treat a mismatch as useful information. If a colleague summarises something different from what you intended, clarify the instruction and check again. Blaming them for not listening misses the opportunity to repair the message before it affects the work. The aim is shared understanding, not a performance of authority.

Protect the channel from competing conversations

When an important issue is being resolved, avoid parallel conversations and unrelated chat. If another matter genuinely cannot wait, make the interruption explicit and explain its relevance. Otherwise, capture it for later. People cannot reliably follow a decision while several discussions compete for the same attention.

In hybrid meetings, check that remote colleagues can hear the discussion and access the same working material. Repeat questions from the room when necessary. Do not allow the actual decision to happen in an unrecorded conversation after remote participants have left. A meeting should not have an unofficial second tier.

Agree how urgent information will be signalled between meetings. Define the channel and the expected response rather than relying on repeated messages across several platforms. Include a fallback for situations where the usual recipient is unavailable, and keep that arrangement proportionate to the importance of the work.

Record decisions in a usable form

Capture the decision as an action or boundary, not as a vague account of the conversation. Include the owner, deadline, relevant conditions and next review point. Someone absent should be able to tell what changed without reconstructing the discussion from a page of loosely connected notes.

  • Decision: what is now authorised, required or ruled out?
  • Owner: who is accountable for the next action?
  • Timing: when must it happen or be reviewed?
  • Trigger: what new information requires an earlier return?

Separate decisions from open questions in the record. If approval is conditional, write the condition explicitly and identify who will confirm it has been met. This prevents an unresolved item gradually becoming accepted as an approved instruction simply because it appears in the minutes.

Use a short handover before closing

Reserve the end of the meeting for a concise check of changed responsibilities and unresolved dependencies. Ask whether anyone has been assigned work they lack authority, information or capacity to complete. Discovering that conflict before the meeting closes is more useful than receiving an explanatory message after the deadline.

Try these disciplines in one recurring meeting rather than imposing a new communication system everywhere. At the next session, inspect an actual decision from the previous week. Could the recipient act on it without clarification? If not, revise the message structure at the point where understanding broke down.

Bring this to your team

We run NASA-style simulations, astronaut keynotes and leadership expeditions for organisations that need their leaders to make good calls under pressure.

Book a Call