Available on Spotify, Apple Podcasts, and wherever you get your podcasts.
Everybody usually knows why the retreat is happening
They may not say it directly, but they know.
There has been tension on the team. People are frustrated. Communication is messy. Leadership is hoping for a reset. Staff are hoping somebody finally says out loud what has been shaping the room for months.
Then the planning starts, and something familiar happens. The conversation moves toward logistics, location, meals, bonding, and what will feel good for people. All of that has a place. But if the team never gets honest about what problem the retreat is actually supposed to address, the rest of the planning becomes a way to stay busy around the truth.
That is how a retreat can be full, expensive, and still unclear.
The problem is usually too vague to work on
A lot of teams say the retreat is about communication.
That sounds reasonable until you try to build anything concrete from it. Communication is not one problem. It might mean people are getting feedback too late. It might mean decisions are being made in side conversations and handed down without context. It might mean managers are carrying confusion from the top and passing that instability down to everyone else.
Those are different issues. They require different conversations, different accountability, and different follow-through.
When a team stays vague, it protects itself from discomfort. Nobody has to admit what is really happening. Nobody has to say whose behavior is contributing to the problem. Nobody has to define what success would actually look like after the retreat is over.
That is why so many offsites sound good while they are happening and then feel strangely unchanged once people return to work.
Fun is not the issue. Making it the center is.
There is nothing wrong with building in rest, laughter, or time for people to be together differently. The issue is when those things become the center of the retreat because the real conversation feels riskier.
You can see it happen. People light up around the spa appointment, the dinner reservation, the golf outing, the activity that asks very little of them. Meanwhile, the harder questions stay unasked.
What are we actually trying to fix?
What keeps repeating on this team?
What has leadership normalized that everyone else now has to work around?
What has to change in behavior, not just tone?
That is the work. Everything else should support it, not replace it.
Leadership behavior is already shaping the room
One of the clearest points in this episode is that retreat failure rarely starts with the activities or even the facilitation. It starts much earlier, often with the unwillingness to look at what is happening at the top.
If leaders are changing direction without explanation, avoiding conflict, glossing over recurring problems, or asking for honesty while reacting defensively to it, that behavior is already shaping the retreat before anyone arrives.
People come into the room carrying what leadership has trained them to expect.
That matters because teams are often asked to do emotional and relational labor that leadership has not modeled. Be open. Be honest. Be collaborative. Be solution-oriented. But if the people with the most power are still protected from scrutiny, the retreat quickly becomes one more place where staff are expected to stretch while leadership stays intact.
That is not a retreat design issue. That is a power issue. And if it is not named, the team will feel it anyway.
Define success in behavior, not atmosphere
A retreat should be able to answer one simple question: what needs to look different by Monday?
Not what should people feel. Not what would be nice. What should actually be different in the work?
Maybe decisions need to be documented in one place. Maybe feedback needs to happen sooner. Maybe priorities need to stop shifting without explanation. Maybe leaders need to own where their behavior has been creating confusion or mistrust.
Those are usable outcomes because they can be seen.
They also make it easier to build an agenda that does something more than create a temporary mood. If the goal is clearer decisions, then the team should practice decision-making. If the goal is better feedback, then the team should work through what direct feedback sounds like. If the goal is repairing trust after leadership inconsistency, then leadership should be doing visible ownership in the room.
Otherwise, the retreat is asking people to believe in change without showing them what change will look like.
Monday is the real test
The retreat is not the proof. Monday is.
That is when people find out whether the conversation led anywhere. Are there clearer expectations? Are there actual commitments? Did leadership name its part? Is there a follow-up structure, or did the team just have an intense conversation and then go back to business as usual?
This is where a lot of good intention gets lost. Teams have a meaningful few hours together, maybe even a brave conversation, and then nobody builds the next step. No owners. No timeline. No shared definition of what progress looks like.
Without that structure, people do not just lose momentum. They lose trust in the process.
That is why defining success ahead of time matters so much. It keeps the retreat from becoming a performance of care. It makes the room accountable to something beyond the room.
Before you finalize the agenda
Before you finalize the agenda, stop and ask what the retreat is being asked to carry.
What problem is this actually for?
What behavior needs to change?
Who needs to go first?
What needs to be visible in the work the following week?
Those questions will tell you far more than the venue ever will.
If your team needs support
If your team needs help naming the real issue and building a retreat around the conversation you have been avoiding, that is the work I do. Let’s chat.
