Team Performance · 13 July 2026 · 6 min read
Crew Resource Management Lessons for Leadership Teams
Apply crew resource management lessons to leadership meetings, handovers and escalation, with practical habits for challenge, clarity and shared awareness.
Written by Christopher Barber

Photograph: Immersive Leaders programme photography — all rights reserved by Immersive Leaders by ISSET
Your leadership team has experienced people, yet important information still arrives late or remains unspoken. The problem may not be a shortage of expertise; it may be how that expertise is coordinated. Crew resource management offers useful lessons about communication, workload and challenge, provided you do not pretend that an ordinary management meeting is a flight deck.
Transfer the principles, not the costume
Crew resource management developed in aviation to improve the use of human and other available resources. It addresses how people communicate, make decisions and work together, not merely whether an individual possesses technical skill. Related approaches appear in other high-consequence settings, with practices adapted to their operating conditions. That history does not make every aviation technique suitable for every office.
Start with the coordination problem you actually have. Perhaps a senior voice closes discussion too early, or a handover leaves the recipient guessing about unresolved risks. Borrow the relevant discipline and test it in context. Avoid importing specialist language to make routine work sound important. A plain question that exposes a missing assumption is more valuable than a briefing full of terminology nobody uses consistently.
Brief the decision before debating it
Open consequential discussions by stating the objective, current situation, relevant constraints and decision authority. Explain what is known and what remains uncertain. This gives colleagues a shared starting point and prevents an energetic debate in which everyone is solving a different problem. A briefing should be concise enough to use, not comprehensive enough to replace the entire project record.
Ask participants what has changed since the previous discussion and which assumptions need checking. Make the status of the conversation explicit: are you gathering options, testing a recommendation or making a decision? Without that distinction, a request for information can be mistaken for resistance, and a tentative suggestion can quietly become an instruction. Clarity at the beginning saves awkward corrections later.
- State the outcome required and who holds decision authority.
- Identify the assumptions and constraints that could change the decision.
- Explain how concerns will be raised and when the plan will be reviewed.
Make challenge usable across hierarchy
Telling people to speak up does not remove the risks they associate with disagreeing. Leaders need to invite specific concerns and respond without punishing the messenger through tone, interruption or later exclusion. Ask what could make the preferred option fail, then leave enough space for an answer. If every challenge receives an immediate defence, the invitation is largely decorative.
Agree how someone should escalate a concern when the first response does not address it. The method should be clear and appropriate to the risk involved, with established emergency procedures taking precedence where relevant. Do not create an elaborate ladder of phrases that delays urgent action. The useful principle is that unresolved concerns remain visible and reach someone with the authority to act, rather than disappearing beneath an apparent agreement.
Close the loop on consequential messages
A message sent is not necessarily a message understood. For important instructions or handovers, ask the recipient to summarise the action, owner and relevant limit in their own words. The sender then confirms or corrects the understanding. Used selectively, this closes gaps without turning every exchange into a ritual. Applied to trivial conversation, it becomes irritating theatre remarkably quickly.
Choose the settings where misunderstanding has a meaningful consequence. A change to a delivery commitment, a safety-related instruction or an urgent allocation of responsibility may warrant explicit confirmation. Explain the purpose so that checking understanding is not mistaken for testing intelligence. The sender shares responsibility for clarity. If a colleague cannot explain the request, the first question should concern the message, not the colleague's competence.
Treat workload as shared operational information
People under pressure can lose track of competing demands while still sounding confident. Make capacity part of coordination rather than a private admission of weakness. Before allocating new work, ask what is already in progress and which existing commitment would move. Encourage colleagues to flag overload early, with a route to reprioritise rather than merely report it.
A leader also needs to recognise their own narrowing attention. Invite someone else to track unresolved issues or challenge whether the discussion remains focused on the right problem. Distributing those functions is not the same as surrendering accountability.
- Who is carrying work that others cannot currently see?
- Which commitment changes if this request becomes the priority?
- What information would tell us that the current plan is no longer workable?
Debrief the coordination, not just the outcome
A successful result can conceal poor communication, just as a disappointing result can follow a reasonable decision made with incomplete information. Review what the team expected, what actually happened and how information travelled. Separate what was knowable at the time from what became obvious afterwards. Otherwise the discussion rewards hindsight rather than better judgement.
Select a coordination habit to improve and test it in normal work. You might change the opening brief, improve a handover or clarify an escalation route. Review whether the change made important information easier to use. Crew resource management lessons are most useful when they make ordinary teamwork more dependable. Their value is not that they make leaders sound like pilots; it is that they make preventable misunderstandings harder to overlook.
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

