Team development training

Team development built around real work, not games

A working session where silos get named, standards get agreed, and the friction slowing the work down gets addressed directly.

Getting on is easy. Working well together is the job.

This is not recreational team building. There are no trust falls, no ropes courses, no personality quizzes run for their own sake, and no day out designed to be remembered rather than used. This is performance-focused and workplace-relevant: sessions built around how your team operates, aimed at the friction slowing it down.

Most teams that are struggling still have plenty of effort. What they lack is shared standards, clear ownership and a way to surface disagreement before it curdles into something nobody names. Silos form between functions that need each other, decisions get made in meetings and unmade in the corridor afterwards, and new teams are expected to perform together before they have had a chance to become a team.

Sessions are built from what is happening in your team: the disagreement nobody has named, the handoff that keeps breaking, the standard that exists on paper but not in practice. We work with the team's leader first, then with the team directly, so what gets agreed in the room has a chance of surviving the return to normal working. What this will not do is fix a team that is simply short-staffed or working with broken systems. Where that is the real issue, we will say so rather than run a session that cannot address it.

What gets in a team's way

If several of these sound familiar, the team needs time on how it works.

  • Silos and cross-functional friction

    Teams that depend on each other operate like separate companies, trading handoffs and irritation instead of working towards the same outcome.

  • Conflict everyone quietly manages around

    Two people, or two functions, stopped working well together some time ago, and the team has built its workarounds instead of naming it.

  • Ownership and role boundaries left unclear

    Work that sits between roles gets done twice, or not at all, because nobody has agreed whose it is.

  • A new team, forming fast

    People assembled quickly for a project, account or launch, expected to perform as a team before they have had time to become one.

  • A team rebuilt by restructure or a change of leader

    The organisation chart has moved on; the working relationships that used to carry the team have not caught up yet.

  • Shared standards that do not exist

    Ask five people what good looks like on this team and you get five different, sincerely held answers.

  • Meetings that end without a decision

    The same items return week after week because the room discusses them rather than deciding and closing them out.

  • Departments blaming each other over customer experience

    When the customer has a bad experience, the post-mortem spends more energy proving whose fault it was than fixing where the handoff broke.

What team development sessions work on

Content is chosen around what your team needs to fix: these are the building blocks, mixed and matched for each team.

Trust and communication

  • Trust built through real work
  • Communication that holds up across the whole team
  • Reading what is happening beneath the surface
  • Giving and receiving feedback between peers

Accountability and standards

  • Role clarity, who owns what, and where it overlaps
  • Accountability without finger-pointing
  • Shared expectations and team standards, agreed out loud
  • Closing the gap between what is agreed and what happens

Working across boundaries

  • Cross-functional working and shared outcomes
  • Customer focus that survives a handoff between teams
  • Collaborative problem-solving under pressure
  • Meetings that end in decisions

Conflict, faced directly

  • Surfacing conflict that has been managed around for months
  • Settling disagreement directly, and keeping it settled
  • Team reset sessions when things have gone stale or sour
  • Rebuilding working relationships on purpose

Leading through change

  • New team formation, agreeing how a fast-assembled team will work
  • Leading a team through restructure or a change of leader
  • Leadership-and-team alignment on what happens next
  • Setting how the team will work before the pressure hits

Who this is built for

  • Cross-functional teams that depend on each other but rarely align
  • Teams formed quickly for a new project, account or launch
  • Teams rebuilding after a restructure or a change of leader
  • Departments that blame each other when something goes wrong for the customer
  • Contact centre teams working alongside sales, support or back-office functions
  • Leadership teams whose own working relationships shape everyone below them
  • Merged or combined teams following a reorganisation
  • Established teams whose standards have quietly drifted apart
  • Regional or multi-site teams that rarely work face to face

Delivered as a series of working sessions

Formats are combined to fit the team's calendar and the problem in front of it.

  • Facilitated working sessions

    Structured sessions where the team works its real issues in the room, with a facilitator keeping the conversation honest and moving.

  • Team resets

    A dedicated session for a team that has gone stale or fallen out with itself, naming the problem and agreeing how it will work from here.

  • New-team formation sessions

    Early sessions for a team assembled quickly, working out how it will operate before habits form by accident.

  • Leadership-team alignment days

    Sessions for the leadership team itself, because a team's alignment rarely outpaces its leaders'.

  • Follow-up clinics

    Short return sessions to work live cases the team has faced since the last session, so agreements do not quietly lapse.

Asked before you ask

Straight answers, and a discovery call for everything else.

Is this an away-day with games and icebreakers?

No. There are no trust falls, ropes courses or personality quizzes run for their own sake. Every session is built around the team's actual work: the friction, the standards, the decisions that are not getting made. Sessions run as working time.

Do you work with the team's leader before working with the team?

Yes. Oliver starts with the team's leader. He asks what they see, what they have already tried and what they have been avoiding, before bringing the team into the room. What the team agrees to also needs the leader's backing if it is going to survive the following month.

What if the conflict involves the manager themselves?

It is handled directly and confidentially. We talk to the manager as openly as we talk to anyone else on the team, and where something needs to be raised privately before or after a group session, it is raised that way. Nothing said to us in confidence goes into the room without agreement.

How do we know whether it worked?

We look at behaviours the team agrees to and can hold each other to, and at the operational indicators you already track: handoff delays, escalation volumes, meeting outcomes and similar measures relevant to your team. We will not promise a specific improvement figure; what changes, and by how much, depends on the team, its starting point and what happens after the session.

What size of team is this suited to?

Most sessions run with teams of six to fifteen, small enough that everyone is genuinely part of the conversation. Larger departments are usually better split into the working sub-teams that depend on each other day to day, rather than treated as one room.

Related insights

View all insights

Tell Oliver what's getting in your team's way

Describe the friction, the silo, or the standard that has slipped, and get a session designed around what is happening in your team, not a generic day out.