The room is the problem: why leadership development belongs somewhere real

Every leadership team has sat through the same day. A hotel conference room with the blinds drawn. A facilitator with a deck. Sticky notes on the wall by lunch, a photo of the sticky notes by three o'clock, and a shared, unspoken understanding that nothing said in that room will survive contact with Monday.

The strange part is that nobody in the room is at fault. The facilitator is good, the content is sound, the people are smart and genuinely willing. And still the day evaporates. When that happens often enough, the honest conclusion is not that the team failed the program. It is that the setting was never capable of producing what was being asked of it.

A conference room is built for presenting, and presenting is the one leadership behavior that is already thoroughly rehearsed. It rewards the confident speaker, the person with the prepared point, the executive who is comfortable holding the floor. What it cannot do is create the conditions in which a team has to actually coordinate, decide, adjust, and recover together, in real time, with something at stake. Those are the moments where leadership is made and where it is revealed. A room with a projector cannot manufacture them.

What the research actually supports

This is not a matter of taste. The evidence on how leaders develop points steadily away from the classroom and toward experience.

The Center for Creative Leadership's widely used model holds that leadership capability comes roughly seventy percent from challenging experiences and real assignments, twenty percent from developmental relationships, and only ten percent from formal coursework. Treat those numbers as a rule of thumb rather than a precise measurement, but the proportion is the point. The overwhelming majority of what makes someone a better leader happens while they are doing something difficult, not while they are being told about it.

A meta-analysis of three hundred thirty-five studies published in the Journal of Applied Psychology sharpens it further. Leadership training works considerably better than earlier research suggested, but the effect depends enormously on how it is delivered. Programs built on hands-on practice and feedback dramatically outperform lecture-only formats, with roughly triple the effect. Multiple delivery methods beat single ones. Extended programs beat brief workshops. Programs designed around a genuine needs assessment beat generic ones.

And when Google set out to determine what separated its best teams from the rest, studying one hundred eighty teams across some two hundred fifty attributes, the answer was not talent, seniority, or team composition. It was psychological safety: whether people felt able to speak up, question, and admit mistakes in front of each other.

Read those three findings side by side and a clear instruction emerges. Put leaders in demanding situations. Give them real practice with real feedback. Build the conditions where people can be honest with each other. Then help them carry it back.

Why place does the work

This is where setting stops being decoration and starts being method.

Back at the office, everyone knows their part. The titles, the meeting rhythms, the seating chart, even the order in which people habitually speak, all of it quietly holds each person in character. That scaffolding is efficient. It is also precisely what prevents a team from seeing itself clearly. You cannot examine a pattern while you are busy performing it.

Move the same group somewhere genuinely unfamiliar, and hand them a problem the place itself supplies, and much of that scaffolding falls away. Not because anyone announces a change, but because the usual cues are missing. The person who always speaks first has no particular advantage. The quiet engineer turns out to see the whole board. Hierarchy softens, not by decree, but because the situation does not care about the org chart.

The right place also supplies something a facilitator cannot invent: real consequences. When the outcome genuinely depends on the group coordinating well, the coordination becomes visible to everyone, including the people creating the friction. Nobody has to be told that communication broke down. They watched it happen, and they felt it.

Months later, nobody quotes a slide. They say "remember what happened at the top of the ninth," and the whole team knows exactly which pattern is being named.

That shorthand is not a souvenir. It is the mechanism by which the lesson keeps working.

The difference between a great day and a changed team

It has to be said plainly, because the experiential category has earned some of its skepticism. An outing is not a program. Novelty is not development. A team can go do something memorable together, come back genuinely closer, and change nothing about how it operates. Enjoyment is a poor proxy for impact.

What separates the two is design and debrief.

Design means the experience is chosen as a deliberate metaphor for the actual problem the team is facing, rather than for how impressive it sounds. A team struggling to make decisions with incomplete information needs a fundamentally different challenge than a team that decides well but fails to align afterward. When the experience mirrors the real dynamic, the parallels do not need to be explained. People arrive at them on their own, which is the only way an insight ever truly lands.

Debrief is where the value is made, and it is the part most often rushed. The experience itself is raw material and proves nothing on its own. The work is sitting with what happened and connecting it, out loud and specifically, to the work waiting on Monday. Which decisions stalled, and why. Who went quiet, and what that cost. What the group did when the plan stopped working. A team that names its own pattern, in its own words, has done something no framework can do for it.

How you know it worked

The fair challenge to any of this is measurement. If a program is not a line of content delivered, what exactly is being bought, and how would anyone know whether it landed?

The weakest answer is the satisfaction survey handed out at the end. It measures whether people enjoyed the day, which is worth knowing but is not evidence of change. A team can rate an experience highly and operate exactly as it did before.

A better approach begins before the program does. Agree, in the team's own words, on what should be different afterward. Not an abstraction like better communication, but something observable: decisions that stop getting re-made three times, disagreement that surfaces in the room rather than in the hallway afterward, a new leader who is genuinely brought inside the group rather than left to figure it out. Write it down while everyone is still honest about the problem.

Then look for the early signals in the weeks that follow, because they show up in the ordinary mechanics of how a team works. How meetings run. Whether the quiet people are still quiet. What happens the first time something goes wrong. Those are visible within a month, and they are the leading indicators of the slower outcomes leaders actually care about: execution, retention, the willingness of good people to stay and argue for the right thing.

The engagement research is worth holding alongside this. Gallup's long-running meta-analysis, spanning more than one hundred eighty thousand business units, finds that business units in the top half of their organization for engagement have nearly double the odds of success on financial, customer, retention, safety, and quality measures, and that roughly seventy percent of the variation in a team's engagement traces back to the quality of its manager. Developing the people who lead through other people is not a soft investment. It moves the numbers leaders are already accountable for.

What this asks of you

If your leadership team keeps circling the same problem, the temptation is to find better content. Usually the content was never the constraint. The constraint is that the setting you keep returning to cannot produce the behavior you are trying to change.

So the question worth asking before booking anything is not what the agenda covers. It is a harder one: what would this team have to actually do, together, for the truth about how they operate to become visible to all of them at once? Answer that honestly, and the right kind of program becomes obvious. So does the wrong kind.

Leaders are made by experience. Everything else is preparation for it.

Morrison Alley Leadership designs and leads custom experiential programs for senior executive teams inside large organizations, in places chosen for what they ask of a team. The research referenced here is set out in full, with sources, on our Why It Works page.

← All field notes