The hidden reason team development fails to stick

Sustained team development is less about the intensity of the intervention and more about the small structural changes that follow it — who meets whom, about what, and how honestly.

I love facilitating team offsites and most work. That is the confusing part. In the right environment, people are more candid, something long unsaid can gets said, the room feels different by the afternoon of day two, and everyone leaves with a genuine sense that something has shifted and hope that this can be sustained by everyone delivering on their agreed commitments.

Then Monday.

The room is not the system

For two days, the conditions were unusual. Time was protected and someone neutral was managing the conversation. Status was temporarily flattened and nobody’s phone was winning. Under those conditions, people behave differently — not because they have changed, but because the constraints changed. You go deeper and not broader and you need to go deep to make real progress.

On Monday the constraints return. The same meeting rhythm, the same reporting lines, the same pressures, the same three relationships that were carefully not discussed. The team has new insight and an unchanged system, and the system is considerably more durable than the teams ever reducing memory of the workshop and any ‘do differently’ commitments.

What usually goes unaddressed

Three things tend to survive the offsite untouched.

The first is the actual decision architecture. If it was unclear before who decides what, a shared understanding of everyone’s personality profile will not resolve it. Teams frequently mistake a structural ambiguity for an interpersonal one, because the interpersonal version is the one they can feel.

The second is the relationship between two specific people, usually senior, which everyone in the room is aware of and nobody names. A great deal of team dysfunction is a two-person problem being distributed across eight.

The third is the leader’s own behaviour. Teams are extremely responsive to whoever runs them and many a personal development programme will emphasise this ‘managing up’ focus. Where the leader’s contribution to the pattern has not been examined, the team can only change so far.

Insight without machinery

Team days generate agreements: we will challenge more openly, we will stop working in silos, we will hold each other to account. These are intentions, not mechanisms. They have no owner, no moment at which they occur and no way of noticing when they have lapsed — which they will, quietly, within about five weeks.

Compare that with an agreement that has machinery attached: the first fifteen minutes of the monthly meeting are for issues people have been avoiding; the two directors whose teams keep colliding meet fortnightly; every significant decision is written down with a named owner and reviewed at the next meeting. Duller to design. Far more likely to survive.

What makes it stick

Diagnose before the day, so the conversation starts where the real issue is rather than arriving at it late on the second afternoon, when there is no time to do anything with it.

I recently facilitated a series of quarterly top team retreats for a client and these always began with a confidential one to one with every member of the top team. The results of these informed the design of the sessions. Over time trust built and I think I was receiving pretty honest feedback from the team.

Change something structural, not only something relational. One alteration to how the team meets, decides or shares information is worth several hours of goodwill. If the team struggles with conflict then design a mechanism that helps them do it. The team I worked with agreed behavioural changes and one member stepped up to monitor these at future meetings. They were then reviewed at the end of the each meeting to see how the team had done.

Return. A half-day at six and twelve weeks does more than extending the offsite by a day. It creates the expectation that this will be looked at again, which is what keeps agreements alive. If you have gained the trust of the team then you can be pretty bullish when reviewing progress.

Work with the leader separately. Not as a criticism, but because their behaviour is the largest single variable in the room. This may include sharing uncomfortable truths that may come as a shock but if you dodge this you are just part of the self-deluding system.

The Monday test

The question is not whether the day went well. Days usually go well. The question is what a member of the team could point to, eight weeks later, that is genuinely different about how the team works. If the honest answer is “the conversation was useful”, the development has not yet stuck.

“Even if the top team has new insight, if it operates within an unchanged system then those insights will gradually fade away. The system is considerably more durable.”