Available on Spotify, Apple Podcasts, and wherever you get your podcasts.
Some retreat agendas are carrying conversations that should have started months ago.
The performance issue that was never named clearly. The role confusion everyone has been working around. The decision no one wants to own. The trust issue people can feel, but leadership keeps talking around.
A retreat can help a team work through hard things. That is part of why retreats can matter. But it should not be the first place people learn what the hard thing is.
Because when the issue arrives as a surprise, the team is not just working through the conversation. They are also working through the fact that leadership waited this long to say it.
Delayed Conversations Become Retreat Work
A lot of teams do not arrive at retreats with clean slates.
They arrive with history.
They arrive with decisions that were never clearly made, roles that were never clarified, feedback that was softened or skipped, and trust that has been worn down in small, repeated ways.
The issue is not that these things show up at a retreat. Of course they do. Teams bring their patterns with them.
The issue is when leaders wait until the retreat to finally name what they have known for a while.
That changes what people are able to do with the conversation.
Now they are not just responding to the issue. They are trying to understand why this is being said now, who has been talking about it privately, and what the conversation is really going to cost them.
That is why surprise agendas are so risky.
They may look efficient from the leadership side. But for the people in the room, they often feel like being asked to process, respond, and trust the process all at once.
That is a lot to ask when the conversation should have started earlier.
Preparation Is Not Just Logistics
A lot of retreat planning focuses on the visible pieces.
The schedule. The facilitator. The food. The location. The activities. The timing. Who is leading which part of the day.
Those things matter.
But they are not the only preparation.
Leaders also have to prepare the team for the actual work. That means naming what has been avoided clearly enough that people are not blindsided when it shows up on the agenda.
It means deciding what should be said before the retreat, what needs to be handled directly with individuals, and what the full team actually needs to work through together.
When leaders skip that step, the retreat starts with confusion. People are trying to understand the issue, the timing, the subtext, and the stakes all at once.
That is not clarity.
That is a leadership gap showing up as retreat design.
Leaders Have to Hold Each Other Accountable First
One of the conversations leaders avoid most often is peer accountability.
They are willing to hold employees accountable. They are willing to talk about performance expectations, team behavior, and what other people need to change.
But when the issue is someone at their own level, the conversation gets quieter.
That is where people start to see the gap between what leadership says and what leadership does.
You cannot ask a team to take accountability seriously while leaders are protecting each other from it. People notice who gets feedback and who gets a pass. They notice who has to repair harm and who gets to move on without naming what happened.
A retreat that focuses on team accountability without addressing leadership accountability is going to feel off, even if no one says it out loud.
Before leaders ask the team to be honest, they need to be honest with each other.
Performance Gaps Should Not Become Surprises
No one should be three or four years into a role and suddenly hear that they have not been doing well.
That is not accountability. That is avoidance with a deadline.
Performance conversations need a rhythm. People need feedback while there is still time to understand it, ask questions, adjust, and see whether the expectations are realistic and clear.
The same is true at the team and department level.
If a process keeps breaking down, talk about it before resentment builds. If handoffs keep getting missed, name the gap before people start blaming each other in side conversations. If one person or group is consistently carrying more than their share, do not wait until the retreat to make it visible.
A retreat can help connect the dots.
It should not be the first place the dots are introduced.
If Everybody Owns It, Nobody Owns It
Role confusion is one of those problems that sounds small until you look at what it costs.
When no one knows who owns the task, the task gets dropped.
When everyone thinks someone else made the decision, the decision stalls.
When people are unclear about where their responsibility starts and ends, they either over-function or step back. Sometimes both, depending on the day.
That confusion creates frustration because people start assigning motives to what may actually be a structure problem.
“They don’t care.”
“They never follow through.”
“They always wait for someone else.”
Sometimes that is true. But sometimes the team has never actually clarified who owns what.
A retreat can be a useful place to clean that up. But again, people should know that role clarity is part of the work before they arrive. They should not be surprised by a conversation about where things are getting dropped.
Decision Authority Needs a Reason
Another conversation leaders avoid is who actually gets to decide.
A lot of organizations operate on habit. This person has always made that call. This department has always had the final say. This leader gets pulled in because that is how the organization has done it before.
But “this is how we have always done it” is not decision clarity.
Teams need to know who makes the decision and why.
Is it because they are closest to the work? Because they carry the risk? Because they have the expertise? Because the decision affects multiple departments and needs a different level of coordination?
When that is not clear, people pass the buck. They wait. They relitigate. They leave meetings thinking a decision was made, then find out later it was not.
That wears people down.
And it is one of the reasons retreats can become so frustrating. The same decisions people could not make during the year suddenly show up as retreat work, but without any clearer agreement about who gets the final say.
Trust Erodes in Specific Places
Trust does not usually disappear all at once.
It erodes in moments.
A deadline gets missed and no one names it. A decision changes and no one explains why. A leader asks for honesty but reacts poorly when they get it. A team says they value collaboration but keeps rewarding the people who work around everyone else.
By the time trust becomes a retreat topic, people usually have examples.
That is why leaders need to ask where trust is breaking down, not just whether trust exists.
Where do people stop sharing information?
Where do they start protecting themselves?
Where do they expect someone to drop the ball?
Where do they assume leadership already knows and is choosing not to act?
Those are the places the work has to get specific.
A vague conversation about trust will not repair what specific behavior keeps damaging.
Say Enough Before the Retreat Begins
The goal is not to solve every hard thing before the retreat begins.
The goal is to stop surprising people with conversations that leadership already knew were necessary.
Say enough ahead of time that people understand what they are walking into. Say it clearly enough that they are not left decoding the real agenda. And do enough leadership preparation that the retreat can continue the work instead of carrying all the weight of starting it.
That is what gives the hard conversation a better chance of becoming useful.
Need Support Planning a Retreat?
If your team has a retreat coming up and there are conversations that need to be named before you walk into the work, I can help.
My Retreat Reset Package supports leaders before, during, and after the retreat so the hard work is structured, facilitated, and carried forward.
