What Should a Team Culture Workshop Actually Achieve?

A team raises a concern through their leader. Something isn't working, and they want it looked at.

The first questions back from management are:

“Who said that?”

“What are their names?”

“We need to deal with them.”

I've seen versions of this happen. Usually nobody in that moment is trying to shut the team down. The instinct often comes from wanting to fix the problem fast, or from feeling criticised. But think about what the team takes away from it. Next time something isn't working, it feels safer to say nothing.

You could run a great workshop on speaking up the week before. That one response would still teach the team more about what's safe to say here.

I run workshops that help teams with exactly this, and I believe in them. I also know a workshop can't build your culture for you. So if you're a manager, business owner or People and Culture lead weighing one up, here's an honest look at what a team culture workshop should achieve, what it can't do on its own, and what needs to happen afterwards.

What should a team culture workshop achieve?

A useful team culture workshop should leave your team with four things:

• Words for what's happening. A clearer picture of the patterns that are helping or getting in the way.
• Shared language. Simple phrases and questions people can use during everyday work.
• Practice. A chance to rehearse the conversations they find hard, using situations from their own workplace.
• Some confidence to try. Enough to have a go back at work, before the day fades.

It should also leave the manager with a plan for the next few weeks.

What it shouldn't promise is a new culture by Friday.

Words for what's happening

Some of the most useful moments in a workshop come when a team finally names something they've all felt.

I recently worked with an allied health team who were young, close and genuinely appreciated each other. That was a real strength. Constructive feedback was one of the areas they wanted more confidence with. Some of them were uncomfortable giving it, because they didn't want to hurt someone's feelings or damage the relationship.

The cost is easy to miss. The person who needed the feedback misses out on something that could help them grow professionally.

One way to describe it is connection versus false harmony. Connection means people care about each other and can still be honest. False harmony means the caring gets in the way of the honesty. Short-term comfort can come at the expense of long-term growth.

A strong team isn't one that avoids tension. It's one that can use tension without turning on each other.

Once a team has words for a pattern like that, it becomes much easier to talk about.

Shared language people can use in a busy moment

Shared language can sound like workshop jargon. It isn't, if it's simple enough to use when things are busy. Things like:

• “Can I clarify something?”
• “Help me understand what happened.”
• “What do we know for certain?”
• “Is there anything we're not talking about that we should be?”

One condition matters a lot here. Language is only shared if people learn it together, including the manager. If the leader isn't in the room, the team walks away with a way of talking that the person responding to their concerns doesn't recognise.

Practice, not just insight

Knowing what a good conversation sounds like isn't the same as being able to have one when you're tired, frustrated or caught off guard.

So a good workshop gives people time to practise. Not a generic case study, but the situations that actually happen in their workplace. The handover that goes sideways. The colleague who keeps interrupting. The feedback that keeps getting put off.

Practice is also where self-awareness and self-regulation come in. Feeling frustrated or defensive is normal. The skill is noticing that reaction and choosing what you do next.

Like any skill, these get stronger with reps.

Some confidence to have a go

People often leave a good session feeling more able to try. With that allied health team, a simple before-and-after evaluation on the day showed self-reported confidence around firmer conversations went up by around 20%. That's a good start, but it's worth being honest about what it shows. It tells you how people felt on the day, not whether those conversations happened the following month. That confidence can fade quickly if it isn't used, which is why the next few weeks matter so much.

What a workshop can't do on its own

A workshop can start the change, but culture is built through the behaviours repeated afterwards.

Culture isn't really what's written on the wall. It's what happens, over and over, in small moments. Whether someone feels they can ask for help. Whether a concern gets curiosity or blame. Whether people deal with something early or let it sit.

Big moments matter too. How a leader handles a serious incident or a tough change gets remembered. But big moments mostly test the culture. The small, repeated ones build it.

In the teams I work with, the patterns that wear culture down are rarely dramatic. Avoiding the conversation. Jumping to blame. Small groups that quietly decide who's in and who's out. People who would rather guess than ask for help. None of those change because of one good day. They change when different behaviour gets repeated and reinforced, week after week.

That's the honest line I'd give any team: I can give you the foundations, but I can't build the habits for you.

The research points the same way. A large review of 89 studies on training found that whether people actually used what they learned was linked with what happened around them afterwards, including support from their manager and peers, and whether the workplace encouraged them to use it. That's worth knowing before you book anything. The workshop is one part of the investment. What happens back at work is the other.

The weeks after the workshop matter more than the day

You don't need to reinforce everything. Trying to usually means nothing sticks. A more realistic approach:

1. Pick one or two behaviours. For example, raising concerns early, or asking a question before reacting.
2. Use the same language in real conversations. If the workshop used “Help me understand…”, use it yourself in the next tricky moment.
3. Build practice into routines you already have. A huddle, a team meeting, the end of a hard shift. No extra meetings needed.
4. Keep it short. Five to ten minutes. One scenario at lunch or in a huddle is enough.
5. Ask where the skill could be used this week. It turns an idea into a plan.
6. Notice it out loud. When someone uses the skill, name the specific behaviour and why it mattered. For example: “When you asked what she needed before jumping in, it gave her room to explain what was really going on.” That lands better than “good job”.
7. Check back after a few weeks. Ask what's working, and where the team is still getting stuck.

In my own leadership, I've used short, informal debriefs. The key is structure. “How did today go?” tends to get a shrug or a vent. More useful questions are:

• What worked?
• What was hard?
• What could we improve?
• What did we learn?
• What do we do differently next time?

The goal isn't forced positivity or a complaint session. It's turning experience into learning and action.

My workshops also include practical follow-up resources, such as summary sheets and short activities, to make this easier to continue back at work.

The manager's response is the biggest lever

Come back to the opening. Imagine the same team raises the same concern a month after a workshop. This time the first response is: “Help me understand what's happening.”

That's the moment the workshop language either becomes real or doesn't.

Before deciding who's at fault, it helps to ask what kind of problem you're actually looking at:

• Is there a system or process issue?
• Is the expectation unclear?
• Is it a capability gap?
• Is it one person's behaviour?
• Or is it a mix?

This doesn't mean never looking at individuals. Unsafe behaviour, bullying, serious misconduct and repeated performance concerns need to be dealt with, and your organisation's policies and processes come first. The point is not to jump to blame before you understand the problem.

Curiosity doesn't mean avoiding decisions, either. Sometimes a leader listens, gets curious, and still needs to say, “This is the expectation.” Getting curious first gives you a better chance of making that call fairly. If you want to see what that balance can look like in a real team, here's what psychological safety looks like in practice.

How to tell if the workshop was worth it

How people feel at the end of the day is a weak measure. A fun session isn't necessarily a useful one, and an uncomfortable one isn't necessarily a failure.

Look instead for small signs a few weeks later. They aren't guarantees, but they're worth watching for:

• People use the language without being prompted.
• Concerns get raised earlier, while they're still small.
• Feedback happens closer to the moment, not in the car park afterwards.
• People ask for help sooner.
• Disagreements happen in the room rather than in side conversations.

If you see a few of these, the workshop started something. If you see none, it's worth asking what happened in the weeks after, not just on the day.

Before you book: three questions to ask

1. What do we want people doing differently in three months? Be specific. “Better communication” is hard to work toward. “Raising concerns at handover instead of afterwards” isn't.
2. Who needs to be in the room? Ideally the whole team, including the manager.
3. What will happen in the weeks after, and who's looking after it? If the honest answer is “nothing”, that's worth sorting out first.

Culture also shapes how people feel at work

Culture isn't only about how well a team performs. It also shapes whether someone can admit they're struggling, whether colleagues notice when something's wrong, and whether people go home carrying conflict that never got resolved.

That's where this series goes next: what team culture has to do with mental health.

Frequently asked questions