Workplace culture workshops for teams

What workplace culture actually is

Culture is often described as "the way we do things around here." That is a useful start but not precise enough to change anything. A more workable definition breaks culture into layers:

• Behaviours: what people actually do, say and avoid. This is the visible layer and the one a team can change most directly.
• Norms: the unwritten rules about which behaviours are expected, acceptable or risky. Whether people speak up in meetings, answer messages at night or challenge a senior colleague are all governed by norms.
• Systems: the processes, incentives, meeting rhythms, performance reviews and decision rights that make some behaviours easier than others.
• Beliefs and assumptions: what people believe about how success is achieved, what leaders really want and what happens to people who make mistakes.

Values sit across all of these, but they only matter when they show up in behaviour and systems. A team that says it values collaboration while rewarding only individual targets has a culture of individual targets.

The connection between culture and psychological safety

Psychological safety, the belief that it is safe to speak up, ask questions, admit mistakes and challenge ideas, is one of the strongest foundations of a healthy team culture. Without it, culture work tends to produce agreements nobody feels safe to hold others to. Many organisations combine a culture workshop with psychological safety training, so the team builds both the norms and the safety to keep them.

Common culture work mistakes

• Starting with values, not behaviour. New values statements rarely change anything on their own.
• Leaders excluded or exempt. If leaders do not model and are not held to the agreements, nothing changes.
• Too many priorities. Ten new behaviours is a wish list. Two or three is a plan.
• No link to systems. If meeting rhythms, incentives and decision rights stay the same, behaviour usually does too.
• One event and done. Culture is built through repetition, so there needs to be a rhythm of review.
• Unsafe conversations. If people do not feel safe being honest about the current culture, the workshop produces polite fiction.

Questions that reveal a team's real culture

Before any workshop, it helps to ask a few honest questions. These are the kinds of prompts Collective Campus uses in discovery, often anonymously.

• What gets you noticed and praised in this team? What gets you quietly sidelined?
• When someone makes a mistake, what usually happens next?
• Who speaks most in meetings, and who rarely speaks?
• If you disagreed with your manager in front of others, how would that go?
• How are decisions really made here, as opposed to how they are supposed to be made?
• What do new starters find most surprising in their first few weeks?
• What would you change about how we work if you could change one thing?
• Which of our values do we live best, and which least?
• When was the last time this team tried something new? What happened?
• How do you find out what is going on: formal channels or the grapevine?
• What do people complain about privately but never raise openly?
• How does it feel to work here at the end of a hard week?

Patterns in the answers are more important than any single response. Themes that appear across levels and roles usually point to the behaviours the workshop should focus on.

Formats (shaped after a scoping call)

Every program is tailored after a scoping call, so there is no fixed length, headcount or package. What changes from one organisation to the next is the mix of the elements below, chosen to fit the outcome the team needs and the real constraints on its time.

• Focused workshop. A single facilitated session built around one live problem the team brings into the room. Best when the goal is a shared language, a quick diagnosis and a small number of agreed next steps.
• Workshop series. A sequence of shorter sessions spaced out so people apply each idea at work between sessions and bring back what happened. Best when the goal is behaviour change rather than awareness.
• Applied program. Training combined with a real piece of work: a service, process or team challenge the group moves forward while learning. Best when leaders want a visible result, not just a completion record.
• Leadership session plus team rollout. Leaders go first so they can model the behaviour and remove blockers, and then teams follow with sessions that reflect what leaders agreed.
• Coaching and follow-up. Check-ins, clinics or office hours after the formal sessions so teams get help when they hit the hard part of applying the method.
• In person, remote or hybrid. Delivered on site in Sydney, Melbourne, Brisbane and other Australian cities, or live online for distributed teams. Remote sessions are designed for remote work rather than a slide deck streamed over video.

The scoping call covers who is in the room, what is already in place, what success looks like in practical terms and what would get in the way. The design follows from those answers.

Why capability building beats one-off training

Most training fails for a simple reason: people learn something in a room, return to a full inbox and an unchanged system, and within a few weeks behaviour drifts back to where it started. The research on learning transfer has said this for decades. What predicts whether learning sticks is less about the quality of the session and more about what happens around it: whether leaders expect and reinforce the new behaviour, whether people get to apply it immediately on real work, and whether the system they work in makes the new way easier rather than harder.

Collective Campus designs for transfer from the start. That means working on live problems rather than case studies from other companies, involving leaders so they can reinforce the change, building in practice and follow-up between sessions, and agreeing practical measures upfront. It also means being honest when training is not the answer. Sometimes the real blocker is a policy, an incentive or a system, and the most useful thing a scoping call can do is name it.

The difference shows up in what teams say afterwards. A one-off session produces "that was interesting." A capability building program produces "this is how we work now," along with the evidence of a changed process, a fixed journey or a decision made differently.

How Collective Campus scopes and runs a program

Collective Campus has been running capability building programs for teams in large organisations since 2015. The approach is the same whatever the topic.

1. Scoping call. A conversation with the sponsor, and often with a few people from the team, about the outcome, the context and the constraints. Nothing is proposed before this call, because a generic proposal would be guessing.
2. Discovery. Where it helps, short interviews or a brief survey with participants so the content reflects their real work and the language they use.
3. Design. Content, exercises and examples are built around the team's own situations. Generic case studies are kept to a minimum; the team's live work is the main material.
4. Delivery. Highly practical, facilitated sessions where most of the time is spent doing rather than listening. Participants leave with things they made, not just notes.
5. Application. Agreed actions, owners and a simple way to check progress, so the work continues after the facilitators leave.
6. Review. A debrief with the sponsor on what changed, what got stuck and what the team needs next.

Pricing, format and timing are all discussed after the scoping call, once both sides understand what the work actually involves.

Culture work in specific situations

The same principles apply everywhere, but the emphasis changes with the situation the team is in.

After a merger or restructure. The biggest risk is assuming the combined team will settle into a shared culture on its own. In practice, people hold on to the habits of their old team, and small differences in how meetings run, how decisions are made or how much autonomy people expect create friction. The workshop surfaces these differences early, treats both histories with respect and designs shared agreements the combined team owns.

During rapid growth. When a team doubles in size, the informal culture that worked with a small group stops scaling. Things that were known by everyone now need to be written down, and rituals that relied on everyone being in one room need redesigning. The focus is on making the culture explicit enough for new people to adopt it quickly.

After a crisis or a difficult period. Teams that have been through a crisis, such as a major incident, a public failure or a period of heavy redundancies, often carry fatigue and lowered trust. Culture work here starts with acknowledgement and recovery before moving on to new agreements. Pushing too quickly towards a positive future can feel dismissive.

With a new leader. A new leader has a short window in which the team watches closely to see what kind of culture they will create. A culture workshop early in that period helps the leader learn the existing culture, signal what they value and agree shared expectations openly rather than leaving the team to guess.

When adopting AI and new technology. New tools change how work is done, who does it and what skills matter. Teams can feel anxious about relevance and job security, or excited and keen to experiment. Culture work helps the team agree how it will experiment safely, share what it learns, protect quality and support people whose roles are changing. Collective Campus often combines culture work with practical AI capability building for exactly this reason.

In hybrid teams. The hardest culture problems in hybrid teams are usually fairness and connection: whether remote colleagues get the same voice, information and opportunities, and whether the team still feels like a team. Agreements about meetings, communication channels and in-person time make the biggest difference here.

Where workload and meetings are getting in the way, time management and productivity training can help. See how Collective Campus worked with Stuart, ON Running and Charter Hall.