Connection: Why Experience Comes Before Reflection

The difference between how a team thinks it works and how it actually does.

Most team development starts in a meeting room. A survey goes out the week before. The results go up on a slide. The team talks about how it communicates, how it makes decisions and how it handles pressure.

It sounds sensible. The question is what you are actually measuring.

The problem with starting in a meeting room

Ask people how they work and they will tell you how they think they work. That isn't dishonesty. It is how self-assessment works. People answer from their best days, their intentions and the version of themselves they recognise.

A cold survey, filled in at a desk between meetings, captures the team that shows up when nothing is at stake. Calm, considered and polite. That team rarely exists when a deadline lands, a client changes the brief or two priorities collide.

If the starting data is built on that version of the team, everything that follows is built on it too.

Why experience has to come first

This isn't a preference for getting teams outdoors. It reflects how adults actually learn.

David Kolb's experiential learning cycle, one of the most widely used models in learning and development, starts with a concrete experience. Reflection, new understanding and new behaviour all follow from it. Take the experience away and reflection has nothing solid to work on. People end up reflecting on ideas about themselves, not on what they did.

The military reached the same conclusion through practice. The After Action Review, developed by the US Army and now used well beyond the military, asks four questions after every exercise. What was supposed to happen? What actually happened? Why was there a difference? What will we do next time? Every one of those questions depends on a real event to review.

Matthew Syed makes the same point in Black Box Thinking. High-performing organisations learn from what actually happened, not from what people believe happened. The gap between the two is where the learning sits.

A conversation in a meeting room skips the first step. Connection puts it back.

Why Connection comes first

Aligned is our team alignment programme, and it starts with doing, not talking.

Step 01 is Connection. Before anyone is asked to reflect on how the team works, the team works. Together, under genuine pressure, with something real to solve.

A shared experience creates an honest baseline. You see who steps forward and who steps back. How information moves, or doesn't. Who decides, who checks and who goes quiet. Whether the plan survives first contact, and how the team adapts when it doesn't.

For a leadership team, building that honest picture early matters more than anything else in the process. None of it comes out of a conversation. It comes out of doing something hard together.

What actually happens on the day

Connection is a full day of experiential team development. At its core is StratNav, a strategic navigation challenge. Part of the team sets the strategy at HQ while the rest execute it in the field, with incomplete information and the clock running.

Around it sit command tasks: short, demanding problems that need fast planning, clear communication and quick decisions.

We also add PlanX, a live operations room planning exercise where the mission changes based on the team's actions as the scenario evolves, and Nexus, a modular problem-solving challenge built around interactive challenges for purely indoor sessions.

People lead. People follow. Roles shift. Plans change.

This isn't icebreakers or trust falls. It isn't an away day with a clipboard. The challenge is real enough that people stop performing and start operating. After each task we review it honestly: what happened, what worked and what we would change. That is the difference between a team development experience and a team development presentation.

Why the team diagnostic sits here

Every Aligned engagement includes a baseline team diagnostic. Where it sits is deliberate.

We run it after the team has been tested together, not before. The experience is fresh. People have just seen how they plan, communicate and respond under pressure, and so has everyone around them. The answers are more honest because there is a shared reference point to answer from.

The data reflects how the team operates when it is tested, not how it imagines it does. That gives us, and the team, something real to measure against later in the programme.

Where this comes from

I learned in the Royal Marines that trust is never built by talking about it. It is built by going through something hard together, then looking honestly at how it went.

Commando training doesn't ask recruits to describe their teamwork. It puts them in situations where teamwork is the only way through, then debriefs every part of it. Over time, that cycle of shared challenge and honest review builds a team that trusts each other, because they have seen each other under load.

Connection applies that principle to a business team. Not the hardship of commando training. The same mechanism: real challenge, shared experience, honest review.

What teams take away

The most valuable thing a team leaves Connection with is a shared reference point.

The rest of Aligned builds on it. Identity, Cohesion, Direction and Review all come back to what happened on day one. When the team explores how each person works, they can point to the moment in StratNav where those styles met. When they talk about trust and accountability, they have a real example in front of them. When they set their direction, it is grounded in how they actually operate.

Without that shared experience, those conversations stay abstract. With it, they stay honest.

This is not an away day. It is the foundation.

If your team needs aligning, Connection is where it starts. befearsomeleadership.com