High-performance team workshops

Before you book

Signs your team is underperforming

Underperformance rarely looks like a quiet office and an empty board. It looks like a busy team whose work does not stick. The signs below are the ones we listen for on a scoping call. You do not need all of them. One that is expensive is enough to shape the room.

The meeting is polite and the rework arrives later

People agree in the room and correct the work in side messages. The person who knows the flaw waits until the leader has left the thread. By the time the correction lands, the pack has been forwarded, the customer has the reply, or the build has started. The team then spends the next week undoing a decision it could have challenged while the cost was still small.

Everything is marked urgent

Two leaders want the same person on the same afternoon. A customer issue and an internal pack both claim the week. Nobody has a sentence for which one loses. A list of themes from the last planning session is still alive in full. The team is not short of effort. It is short of a rule for what is allowed to slip.

The calendar is full and the outcome is thin

The week is meetings, status, and drafts of drafts. Deep work survives only at the edges, and then it does not survive. People describe themselves as flat out. Ask what changed for a customer, a risk, or a decision, and the answer is vague. Focus has been replaced by motion. The productivity workshop is the right door when this is the whole problem. Inside this workshop it is one of five habits, because a protected hour is useless if the team is protecting the wrong work.

Decisions reopen

A choice is minuted, then walked back when a senior person who was quiet raises a late objection. Or the opposite: the choice never quite closes, so the team keeps preparing. Either pattern is a decision habit, not a personality clash. The room has no shared picture of who owns the call, what objection had to be heard first, and what would make the call wrong.

Drafts look finished too early

A tool, or a very fluent colleague, produces a paragraph that reads as done. The fee rule is wrong, the clause is not in the source, or the customer example is the wrong customer. People forward it because stopping it feels like slowing the team. The miss is blamed on the tool afterwards. The real miss is that the room had the knowledge and no path to use it while the draft was still a draft.

The team is new, reformed, or split across rooms

A new team inherits no rules, so it copies the loudest person's meeting. A team after a restructure inherits two old loyalties and a chart that says they are one group. A hybrid team loses the aside after the meeting, which is often where the real objection used to surface. None of these is a morale problem to be fixed with a social event. Each is a missing habit the people who share the work can practise.

Inside the workshop

What the workshop covers, session by session

The sessions below are the spine. We do not publish a clock time for them. Length, pace and whether they sit in one holding or across a series are tailored after an initial conversation. What does not move is the work: the team's live material, the leader in the room, and a habit practised rather than described.

Session 1. The work that is slipping

The team brings one piece of work that is late, reopened, or quietly avoided. It is not a case we carry in. The room names who is affected, what done means, and what has already been tried. The aim is a shared picture. People often discover they have been describing three different jobs with one name. Steve asks the leader to speak after at least two other people have described the work, so the session does not become a long agreement with the first account.

We also name what is out of scope for the workshop. A team will try to solve the entire system once the real friction is visible. Session 1 ends with a boundary: this is the work we will use for the habits, and this is the work we will park. Parking is a decision. It is the first small version of clarity.

Session 2. Psychological safety on that work

Using the work from session 1, the team finds the sentence people almost say and do not. It might be a wrong customer, a number that does not match the source, or a risk the plan has stepped over. They practise the minute after that sentence, and especially the leader's reply. A joke at the speaker's expense, a defence of the plan, or a promise to take it offline that never returns, all set the price for next time.

The standard stays in the same breath as the thanks. High safety with low standards turns into comfort, and the hard news stays out. We use Edmondson's distinction, as recorded in the Harvard Business School note linked above, so the room does not leave thinking the goal is to be nicer. If the team needs a full workshop on this habit alone, we will say that and point to psychological safety training. We will not pretend a short practice replaces that room when the fear is the whole problem.

Session 3. Clarity when two demands collide

The team picks two real demands that collide in the current period. They write one sentence: when these collide, this one wins, and this person may say so. If they cannot bear to disappoint either demand, they do not yet have a priority. We stay with the sentence until it is specific. Themes such as growth, risk, service and cost are not a sentence. A sentence names the work that waits.

They also name the parking place for the demand that waits, and the date they will look at it again. Without that, the losing item returns as a side project because nobody wants to be the person who dropped it. The person allowed to say the sentence is rarely only the most senior name in the room. If it is, the sentence will be applied late, after the work is done.

Session 4. Focus and the week as it is

The team looks at where the week goes, using the meetings and artefacts they actually have, not a generic time log we impose. They mark one pattern that feels like work and does not change the outcome of the job from session 1. A status meeting that restates a board, a draft that is polished because a sponsor might glance at it, a chat channel that has become the queue. They choose one pattern to stop or shrink, and one block to protect for the work the priority sentence named.

This is the productivity habit, tied to a choice. The ON Running write-up, described in the record further down, was about leaders taking techniques back to their teams. We do not turn that record into a promise for your team. We use the same discipline: notice the self-sabotage, choose a technique, and give it an owner. Teams whose only brief is the calendar should read the productivity workshop before they book this wider room.

Session 5. A decision that can still be challenged

The team takes a decision it has reopened, or one it is about to make. They name the owner. They name the objection that has to be heard before the decision closes. They name what would make the decision wrong, in a form someone can check. A decision with no owner will be reopened by whoever speaks last. A decision with no allowed objection will be reopened in the corridor. A decision with no kill test will be defended after the facts have moved.

Critical thinking shows up as a shape, not a lecture. What was the question, in the team's words, before anyone drafted the answer. What source would confirm or kill it. Who may say it is not ready. What happens if that person is out. The critical thinking workshop trains that judgement when it is the whole brief, including teams who already use AI and need the check to survive a fluent paragraph. In this session the shape is applied to one decision the team cannot afford to fake.

Session 6. AI-ready habits on a real draft

The team brings a draft, a brief, or a reply someone would be tempted to send. Before a tool is opened, they write the question, the condition that would make an answer usable, and the name of the checker. Then they look at the draft, including one a tool might have produced, and practise stopping a fluent wrong answer in front of the person who asked for it. The point is the path, not the prompt.

We do not run a feature demonstration, and we do not ask people to paste sensitive material into a public tool. If the work involves customer records, legal material, or anything your policy already fences, the team uses a scrubbed example or an admin step that never needed the sensitive file. The habit is the same. The data stays where it already belongs. Executive teams who need a written expectation for the whole organisation, and a board cadence after it, should use the leadership team AI immersion as well as, not instead of, the team habit.

Session 7. The rules the team will keep

The team writes three rules, in its own words, for the next block of work. Three is the limit so the rules are used. Each rule has a person who will notice if it slips, and a moment in a meeting that already exists where it will be checked. A new meeting is a last resort. The rules have to cover the thin habits, which might be a reply to a hard comment, the priority sentence, and the check on a draft. A team that writes eight norms will remember none of them by the second week.

The rules are read back by someone who did not draft them, to test whether a person who missed a moment could still apply them. Vague rules are rewritten. "Be open" is not a rule. "The author of a draft replies to the substance of a correction in the same thread" is closer. "We value balance" is not a priority. The collision sentence from session 3 is.

Session 8. The first week back

The leader names the first hard comment they expect and the reply they intend to give. The team names the first likely collision of priorities and who will say the sentence. They choose the meeting in which the three rules will be visible, and what "visible" means: said aloud, written in the notes, or both. They also name the signal that the workshop has failed, so failure is discussable. If nobody uses a rule, the follow-up is about that fact, not about booking a second performance of the same sessions.

Follow-up is part of the design, and its shape is tailored after the initial conversation. The agenda is the three rules against a real meeting the team picks. We are not there to admire the offsite. We are there to see whether the minute after a hard comment went the way the leader practised, and whether the priority sentence survived contact with a sponsor.

Who it is for

Who the workshop is for

The workshop suits teams that share work and a leader. It is a poor fit for a conference audience, a public class of strangers, or a group assembled because they were free. The four situations below are the ones we see most often. A team can sit in more than one.

Leadership teams

A leadership team sets the price of candour for everyone who watches it. If that group cannot disagree in the room, the teams below them will not risk it either. The workshop gives the leadership team the five habits on its own collisions: the initiatives that all stayed alive, the pack that looks finished, the decision that reopens after the meeting. It is not a substitute for the leadership team AI immersion, which writes the expectation leaders will ask of the organisation and the cadence with the board. Use the immersion when the question is how this executive group leads AI. Use this workshop when the question is how this group performs as a team. Use both when both are true.

New teams

A new team is often kind and vague. People are still working out whether a question is expensive. They copy the first strong voice. The workshop gives them rules before the first bad habit sets. Bring the work the team was formed to do, not a hypothetical. A team that has not yet been given a real job is early for this room. Give them the job, then book the workshop.

Teams after a restructure

After a restructure, the chart says one team and the habits say two. People protect old managers, old metrics, and old meetings. Silence is a way to stay safe while the new leader's reactions are still unknown. The workshop uses a piece of work the new team must do together, and practises the reply the new leader will be watched for. We do not run a session that asks people to perform trust. Trust, in this sense, is the accumulated experience of not being punished for a useful sentence.

Hybrid teams

Amy Edmondson and Mark Mortensen, writing in Harvard Business Review, describe psychological safety as the belief that you can speak up without risk of punishment or humiliation, and they argue that hybrid work pushes the conversation into a new place. Managers have long tried to make it safe to disagree about the work. Location and presence are now part of the same climate. A comment that sounds friendly can land as pressure. The aside after the meeting, which used to carry the real objection, disappears when half the team is already gone.

For a hybrid booking we design the objection into the main conversation. Someone in the hub reads the remote comments into the room as part of the session, not as a summary if there is time. There will not be time. A team split across Sydney, Melbourne and Brisbane is one team if they share the work, and they will not behave like a single table. Say which city is the hub, and who is remote, before we lock the design. City pages for Sydney, Melbourne and Brisbane describe how that room changes. They are not this page with the city name swapped.

Formats

Offsite, series, or leadership programme

Three formats carry the same sessions. We do not publish a price, a duration, or a group size. Those are tailored after an initial conversation, once we know the team, the work, and whether people are in one city or on a screen.

Offsite

An offsite is the intact team, away from the inbox, with the leader present. The sessions run as one holding so the priority sentence, the hard reply, and the draft check are built on the same piece of work. It suits a team that can leave the operation, and a problem that should not be sliced into fragments. It does not suit a team whose real constraint is that they never get the decision-maker in the room. In that case we move the date. We do not run the offsite for whoever was free.

Series

A series splits the sessions so the team can try one habit before the next. Session 2's reply can be tested in a real meeting before session 3 locks the priority sentence. The series suits leaders who cannot take the whole team out of the work in one holding, and hybrid groups who need time to design how a remote objection is heard. The risk of a series is drift. Each sitting starts from the artefact of the last one, not from a recap of theory. If the team cannot do the between-work, we will say an offsite is the better format.

Leadership programme

A leadership programme starts with the leadership team. They do the workshop on their own collisions and write the standard their managers will copy. The teams below then do the workshop on their own work, with that standard visible. This is how a restructure or a new operating rhythm stops being a chart. It is also how you avoid training staff in candour their director will punish the following week. The leadership programme is not the AI immersion. If the leadership team also needs a written AI expectation and a board cadence, we scope that separately and say how the two should be sequenced.

In person, at your office or a room in the city, is the default when the team can sit together. Hybrid is a designed format, not a camera pointed at a table. Remote-only is available when the team has no shared city. Say which one you need. We would rather change the design than pretend a hybrid team had a single-table workshop.

The record

What published work shows, and what it does not

Collective Campus does not have a stack of case studies titled as this workshop. The pages below are real work write-ups. Each supports one part of the model. None of them should be read as a claim that the client booked a high-performance team workshop under this name. If a sentence is not in the write-up, it is not in this summary.

ON Running, on leaders taking productivity back to their teams

The ON Running write-up says growth had made the company's earlier pace harder to keep, and that it asked Steve Glaveski to design a productivity and workflow workshop for leaders. The session covered team, manager and individual productivity, tools and techniques. Leaders left with takeaways they could pass to their teams, so the company could keep a fast way of working. ON Running is not an Australian organisation, and the write-up does not place the session in Sydney, Melbourne or Brisbane. It is here because it is a public record of the focus habit with leaders, not because it is a local booking. We do not turn it into a forecast for your team. Teams who want that habit book it inside this workshop, or in the narrower productivity workshop.

ASM Global, on high-performing people working as a team

The ASM Global write-up describes a LEAD programme for high-performing talent across Australia, New Zealand, Dubai, Bahrain and Malaysia. The people were already seen as strong. The gap was a shared way to tackle real company problems, not only theoretical knowledge. Collective Campus ran a design thinking workshop, coaching as the teams worked, and a pitch to executives. The write-up says all three proposed solutions were approved for implementation, and that the work fostered collaboration among those high performers. That supports a narrow claim: capable people still need a shared method and a real problem if the organisation wants them to perform together. It does not say we ran this five-habit workshop, and it does not name a psychological safety practice.

Yarra Ranges Council, on leaders of teams

Yarra Ranges Council sits on metropolitan Melbourne's eastern fringe. The write-up says the council wanted a design thinking mindset for problem solving, and asked Collective Campus to upskill the team in the method and the tools for day-to-day roles. The work included strategies to adopt behaviours that would embed the method in the culture. The outcome in the write-up is a shared understanding of the method and tools people could use in their jobs. This is not a high-performance team workshop. It is published evidence that a Melbourne team has asked us to build a shared way of working, including the behaviours that make it stick. The Melbourne page keeps that claim at that size.

Cochlear, on a Sydney team learning a method together

Cochlear is based in Sydney. The write-up says the talent development team wanted a design thinking mindset for problem solving, applied to employee experience. The group included people from global talent development, global marketing, global services and research and development. The session covered a shared method, behaviours to embed that method, and ideas pitched to management. Again, this is not this workshop. It is the published Sydney record of an intact, cross-functional group learning one way of working. The Sydney page treats it as that, and not as a local trophy.

We will not stitch these four into a single success story. They were different briefs, in different years, for different reasons. What they have in common is a team that needed a way of working, not a speech about performance. That is the standard we use when we decide a case belongs on this page.

Before and after

How we measure team performance without inventing a score

Team performance is easy to fake with a survey taken on the way out of a good room. People are tired and polite, and the numbers look like a result. We do not do that. Measurement is a comparison of observable moves, on the team's own meetings, before the workshop and after the first weeks back.

What we look at before

On the scoping call, and in a short baseline the leader can take without a research project, we ask for evidence you already have. Who speaks first in the regular meeting, and is there a gap before the decision. Did a correction appear under a polished draft, and did the author reply to the substance. If two people are asked what would lose before Friday, do they name the same work. Is there a block in the week that belongs to the priority, or only to the queue. When a decision reopened, was the missing objection in the room at the time. These are questions, not a disguised maturity model.

What we look at after

The follow-up uses the same questions on a meeting the team nominates. We also check the three rules. Were they visible. Did the named person notice a slip. Did the leader's reply match the one they practised. Did the priority sentence survive a real collision. Did a fluent draft get stopped by the named checker. A yes is evidence. A no is evidence. A story about how people felt is not, on its own, the measure.

We will not publish a percentage lift, a productivity multiple, or a psychological safety index for your team unless you already measure those things and ask us to sit beside your measure. Inventing a number to make the workshop easier to buy would break the standard this page is built on. The ON Running write-up does not give a before-and-after score. We will not invent one for them, or for you.

Leaders who want a longer view can keep the baseline questions in an existing rhythm, monthly or with the operating review they already run. The workshop does not add a new reporting line unless you ask for one. The aim is that a manager can see silence, a fake priority, and an unchecked draft without hiring us to see them.

Where to go next

Related workshops and the longer read

Use this page when the team needs the five habits together. Use the pages below when one habit, or one leadership question, is the whole brief. Each link goes to a real programme on this site.

• Psychological safety training for an intact team and the leader, when the price of speaking up is the constraint.
• Critical thinking training for judgement on live work, so people can use AI without handing over the decision.
• Productivity training for teams whose week is busy and thin.
• What makes a high-performing team in the AI world, the longer read behind this workshop.
• Leadership team AI immersion for executive teams who need a written expectation and a board cadence.
• AI programmes when the team is ready to change a workflow, not only a habit.
• City rooms: Sydney, Melbourne, Brisbane.