Team Sessions

• The whole team is rarely in one place, and you've got that time coming up - you want it to count for something.
• There's a real reason for the day - a direction to set, a problem to crack, a year to make sense of - not just a calendar slot to fill.
• Your normal meetings can't do this work: too short, too operational, too many people half-listening with one eye on their inbox.
• You've had away days before that felt good on the day and faded by Monday, and you don't want to repeat that.

We start before the day, not on it. A short conversation about what's actually going on tells us whether the day needs to solve a problem, set a direction, repair something, or simply give the team room to think together - and the design follows from that, rather than from a template.

On the day, the job is to keep the conversation honest and moving. That means making space for the quieter people, not letting the loudest set the agenda, and noticing when the group is circling something it's avoiding. A good away day feels like real work, not a series of exercises - though the right activity at the right moment earns its place.

You'd take away the decisions the day was for, who's doing what next, and a shared sense of why it matters - not a flip-chart photo no one opens again.

• The same topic keeps coming back to the same meeting and leaving unresolved.
• People have stopped expecting it to get sorted - there's a quiet "here we go again" when it comes up.
• You suspect the real issue isn't the one on the agenda, but no one's naming it.
• The team is capable and motivated, which makes the stuckness more frustrating, not less.

Stuck usually isn't a thinking problem. It's a conversation problem - something isn't being said, or the group keeps starting in the same place and arriving in the same place. The first job is to find where the real block is, which often isn't where the team thinks it is.

From there it's about creating the conditions for a different conversation. Sometimes that's separating the problem from the personalities attached to it. Sometimes it's slowing the group down enough to question an assumption everyone's been treating as fixed. Sometimes it's as simple as someone neutral asking the question no one inside the team can ask without it landing wrong.

You'd take away the block named, a way through it the team agrees on, and - often the bigger win - a sense of how to have that kind of conversation again without us in the room.

• There's a specific, concrete problem or decision in front of the team - not a vague unease, an actual thing to work on.
• It matters enough that you don't want it half-solved in the corners of a normal meeting.
• The team has the knowledge to crack it, but needs the room and the structure to do that together.
• You want the team to own the answer, because they're the ones who'll have to live with it.

The team knows the problem better than anyone outside it ever could - so the session isn't about us solving it. It's about building the conditions in which the team can. That starts with getting the problem framed properly: a surprising amount of problem-solving goes wrong because the group is busily answering a slightly different question to the one that matters, or jumping to solutions before it's understood what it's actually solving.

From there it's structure and pace - keeping the thinking moving, making sure the team explores the problem before it rushes to fix it, drawing out the quieter ideas that get lost when a confident voice lands on an answer early. We bring tools where they help (ways of mapping a problem, pressure-testing an option, weighing trade-offs), but lightly - the work is the team's thinking, not the technique.

You'd take away a worked-through answer the team genuinely owns, the reasoning behind it, clear next steps - and a way of tackling the next live problem that doesn't always need an outside facilitator in the room.

• The work is being slowed or shaped by something between people, not by the work itself.
• Conversations have gone careful and polite on the surface, with the real thing happening in side-channels and after the meeting.
• You can feel people taking sides, or going quiet, or routing around each other.
• You've held off addressing it because you're not sure how to do it without making it worse.

The aim isn't to make everyone friends. It's to get the team to a place where the disagreement isn't quietly running the show. Often the conflict on the surface isn't the real one - two people clash about a decision, but underneath it's about feeling unheard, or unclear roles, or a history that never got resolved.

A neutral facilitator makes a real difference here. People will say things to someone from outside that they won't say to each other, and someone outside can name a pattern without it being taken as taking sides. The session is structured so it stays honest without tipping into something it shouldn't be - this is facilitation, not therapy, and knowing where that line is matters.

You'd take away the air cleared enough to function, an honest understanding of what was actually going on, and some agreements about how the team works from here.

• Something significant has just happened to the team, and everyone's been pushing on through it without pausing.
• People are in slightly different roles or relationships than before, and it hasn't quite settled.
• There's a sense of "we never really talked about that" hanging around.
• The team's functioning, but more out of habit than out of being genuinely regrouped.

Change leaves a wake. Even change that went well leaves people in slightly different roles, with slightly different relationships, carrying things they haven't had a chance to put down. Pushing straight on without acknowledging that tends to cost more later than the time it takes to do it now.

The session makes room for the honest version - what's actually changed, what people are carrying, what they're unsure of - and then turns the corner towards what's next. The balance matters: enough looking back to be real about it, not so much that it becomes a wallow. The point is to leave the change behind as a shared thing the team has processed, not an unspoken thing each person is still managing.

You'd take away the change genuinely behind you, a clearer picture of how the team works now, and momentum pointed forward.

• The team is new, or new enough that "how we do things" hasn't actually been decided yet.
• People are still feeling out how to work with each other - what's expected, who does what, how decisions get made.
• You'd rather set this on purpose than discover six months in that it set itself badly.
• There's goodwill and energy to use - a new team mostly wants to get this right.

Every team develops a way of working. The only question is whether it's chosen or inherited. New teams that never have the explicit conversation tend to default to the loudest person's preferences, or to whatever the previous team did, and then wonder why things feel off six months in.

The session is the explicit conversation, done while it's still cheap to have. How do we make decisions? What do we expect of each other? What does good look like for us? How do we want to handle it when we disagree? None of that has to be heavy - it's often energising to talk about, because a new team mostly wants to get this right.

You'd take away a shared, spoken understanding of how the team operates, the awkward questions asked early rather than avoided, and a team that's chosen its own ways of working rather than stumbled into them.

• The team works hard but the results don't quite match the effort going in.
• It's not always clear who owns what, or what "done well" actually means here.
• Things get agreed and then quietly don't happen, without anyone quite addressing it.
• You want to lift the team's game without becoming the person who nags.

Most teams that want to perform better aren't lazy. They're unclear - on priorities, on ownership, on what they've actually agreed - and the gaps get filled with assumptions that don't match. So the work starts with making the implicit explicit: what are we here to do, what does doing it well look like, and where are the soft spots in how we work?

Healthy accountability grows from there. It's the difference between "you didn't do the thing" and "we agreed this matters, so let's understand what got in the way and sort it." One shuts people down; the other keeps the team honest and moving. A facilitated session helps a team find that register and make it normal, rather than something that only shows up when things go wrong.

You'd take away clear shared expectations, an honest read on what's been getting in the way, and a way of holding each other to things that strengthens the team rather than straining it.