The One Behavior That Matters Most
Leadership competency models are everywhere. They list 15, 20, sometimes 40 behaviors a great leader is supposed to demonstrate. The problem isn't that these models are wrong. The problem is that they treat every behavior as equally important.
They're not.
After 25 years of watching leaders operate under real pressure with over 100,000 participants across six continents, one behavior predicts team performance more reliably than any other: the speed at which a leader creates shared understanding of the problem before asking for action.
That's it. Not charisma. Not decisiveness. Not vision. The ability to create shared context before demanding execution.
Why This Behavior Dominates
When a leader says "we need to fix this" without first explaining what "this" actually is, half the team starts solving the wrong problem. The other half waits for clarification. Nobody moves with confidence.
In the Save the Titanic experience, participants become Senior Officers on a sinking ship. They have 3.5 hours to save passengers and keep the vessel afloat. When officers rush to give orders without creating context, crew members hesitate. Time bleeds away. The ship takes on water.
When officers take 60 seconds to explain why the order matters, what's at stake, and what role each person plays, the entire team moves faster. Not slower. Faster. That 60-second investment in shared understanding eliminates the 10 minutes of confusion that follows unclear direction.
Creating Context is one of the six key learnings in the Save the Titanic experience. And it's the one that transfers most directly to every leadership moment back at work.
The Pattern in Real Organizations
When ArcelorMittal put 710 leaders through the experience with Duke Corporate Education, the pattern was consistent. Leaders who scored highest on Creating Context had teams that made decisions 30-40% faster. Their teams also produced fewer rework cycles and had less conflict about direction.
Learn2 clients see this across every industry. Freedom Mobile saw save rates jump from 47% to 86% when leaders created context before asking frontline teams to retain customers. Those leaders didn't give different instructions. They gave the same instructions with better context. The results were worth $4M annually.
Bell MTS grew revenue from $800M to $1.4B within a year. The shift wasn't a new strategy. It was leaders learning to create context before asking for action. Same people. Same market. Different leadership behavior.
Why Most Leaders Skip It
Leaders skip context creation for three reasons.
First, they assume everyone already knows what they know. They've been thinking about the problem for days. Their team just heard about it five seconds ago. The gap between leader knowledge and team knowledge creates the illusion that context is unnecessary.
Second, urgency feels like it requires speed. When the building is on fire, you don't want to explain the history of fire. And that's true. What you do want to explain is which exits are blocked, where the people are, and who is responsible for what. That takes 30 seconds and saves the lives that rushing past it costs.
Third, leaders confuse telling with creating context. Sending an email with the plan is telling. Creating context means ensuring every person understands why this matters, what's at stake, and what their specific role is. Those are different activities with different outcomes.
How to Develop This Behavior
You can't develop this behavior in a classroom. Lectures about Creating Context are ironic. Someone talks at you about the importance of not talking at people.
The behavior develops under pressure. When a leader faces a real problem with real time constraints and real consequences for failure, their natural patterns surface. Some leaders instinctively create context. Most don't.
The Save the Titanic simulation creates that pressure in a safe environment. Leaders discover their default behavior. They experience the consequences. And they practice the alternative until it becomes instinctive.
The first round usually reveals the gap. The second round shows improvement. By the debrief, leaders have language for what they experienced and tools they can use starting the next morning.
The Multiplier Effect
This behavior compounds. A leader who creates context before every significant request builds a team that doesn't wait for permission to act. The team understands the why behind the what. They can make decisions without checking in. They can adapt when circumstances change because they understand the intent, not just the instruction.
Teams with context-creating leaders hold fewer status meetings. They produce fewer "just checking" emails. They spend less time in the meetings where nothing gets decided because alignment happens before the meeting, not during it.
Over 90 days, a team whose leader consistently creates context becomes measurably faster, more autonomous, and more aligned than a team whose leader just gives direction. The first 90 days after a team experience are where this behavior either becomes a habit or fades.
Test Your Own Behavior
Here's a quick diagnostic. Think about the last significant request you made to your team. Did you explain why it mattered? Did you describe what was at stake if it didn't happen? Did you clarify each person's role?
If you did all three, you're in the minority. If you skipped one or more, you have an opportunity to improve the most predictive leadership behavior there is.
The results organizations achieve when leaders learn this behavior are measurable. Faster decisions. Less rework. Higher retention. Better execution. All from one behavior practiced consistently.
Book a 20-minute walkthrough and I'll show you how the simulation reveals whether your leaders create context or skip it — and how to close the gap.
Read next: Why Trust Is Built in Small Moments Not Big Gestures