Systemic coaching for teams who need to do more than meet and coordinate.
Why team coaching?
Many leadership teams were never really formed as teams. They exist because the heads of several functions, programmes, or disciplines needed to meet. Each member carries their own mandate and their own stakeholders; the group exchanges information and coordinates delivery. Whether it can also lead together is a different question, and it surfaces the moment an issue cuts across functions.
Programme teams and cross-organisational working groups have their own version of the problem: assembled around a mandate or a funding cycle, often across institutions, with even less shared history to draw on.
That gap is costly. It shows up in decisions that contradict each other across functions, and in priorities reopened through side conversations. Staff and stakeholders learn quickly whether the team resolves tensions together, or whether they are better off negotiating with individual members.
The results were as quickly felt in the improvement of teamwork in the Department as in the realization of my own objectives.
The team's live work, and the patterns underneath it.
Work on trust and psychological safety has real value. It becomes leadership development only when it is connected to the team's actual work; a better climate that stays in the retreat changes little. So I connect the relationship work directly to the team's live responsibilities.
01
Start with the team's live work
Real meetings, real priorities, real decisions. Evidence from inside the team, and from the staff, sponsors, and governing bodies beyond the room, shapes the design.
02
Surface the patterns underneath
How the team thinks when stakes rise, and the conversations it never quite has. Patterns rather than incidents: the habits that decide whether decisions hold.
03
Test a different practice together
New practices are tried in the team's regular meetings, where the patterns actually live. When they shift, decisions start to hold and disagreement stays in the room. The aim is a team that carries the new way of working forward without me.
The measure of progress is whether the team leads more effectively, and whether the people it serves notice.
Collective Leadership
The team functions as a leadership unit rather than a collection of individuals who happen to meet. The clearest sign: members stand behind decisions they argued against in the room.
Strategic Clarity
Shared understanding of what the team is there to do, and the discipline to act on it. Fewer priorities, held longer; an organisation that stops receiving mixed signals.
Organizational Impact
Effectiveness visible beyond the team, in the organisation and relationships it is responsible for. Staff and stakeholders stop working around the team.
Three common starting points
These are starting points, not fixed packages; they serve leadership teams and programme teams alike. The duration and the depth of diagnostics and stakeholder work scale with the mandate. In the introductory call we clarify the situation and the objectives; I then prepare a proposal around the work.
Note. The team is the client. Individual interviews and conversations support the team's work; they do not become parallel coaching engagements. Interview findings are reported as themes, and comments are not attributed without permission. Retreats create the space for diagnosis and agreement; the follow-up coaching tests those agreements in the team's regular meetings and decisions. Every engagement includes: agreed objectives · a diagnostic suited to the mandate · sessions built into the team's real meetings · a closing review against objectives.
The new team
For a team recently formed, newly merged, or under a new leader, that wants to set its working patterns deliberately rather than inherit them.
- Duration: 1-3 months
- A team launch retreat plus 2-3 follow-up sessions
- Light diagnostic at the start: a team survey or short interviews
- Working agreements and decision rules the team actually uses
- Short review at the end
The repeating pattern
For a team where the same conversations keep returning: decisions that do not hold, and disagreement that moves outside the room.
- Duration: 4-6 months
- BRITE Team Effectiveness diagnostic and individual interviews at the start
- An opening retreat, then sessions built into the team's real meetings
- Individual conversations where needed, including with the team leader
- Closing review against agreed objectives
The restructuring
For a team carrying a major transition, a new mandate or a reorganisation, with the organisation and other stakeholders watching.
- Duration: 6-12 months
- Diagnostic plus confidential stakeholder interviews beyond the team
- Retreats at key moments, with coaching between them inside the team's real work
- Sponsor alignment where the team answers to a board or executive
- Periodic review and a closing debrief
Want to discuss what suits your team best?
Rather start in writing?
Frequently asked questions
The starting point. Standard team development improves how the team works internally. Systemic team coaching starts from the team's purpose and its stakeholders: what is this team collectively responsible for, and how effectively is it leading that? Internal dynamics matter, and they are worked on in service of external impact rather than as an end in themselves.
A retreat is a single event. Team coaching is a sustained process that tracks what is changing over time and works at a level no single event can reach. A well-designed retreat can sit inside a team coaching engagement, as a moment for deeper work or a significant decision, but it does not substitute for the ongoing process.
Carefully and directly. In systemic team coaching the leader is part of the system being worked on. If the leader's behaviour is shaping the team's functioning in ways that limit it, that gets named and worked with rather than managed around. This requires the leader to be open to that process. If they are not, the work will not go where it needs to.
That is not unusual. Some of the most productive engagements are with teams that function reasonably well internally but whose collective leadership of the wider system is less effective than they realise. The diagnostic at the start often surfaces that gap, and it is harder to dismiss when it comes from data rather than assertion.
By looking in both directions. Internally: the quality of collective thinking, and the team's capacity to have difficult conversations productively. Externally: how the team leads the wider organisation, and whether its collective voice carries more weight with its stakeholders. Team diagnostics, often BRITE Team Effectiveness, can set a baseline across both at the start.
