One-to-one coaching and team coaching use some of the same listening and contracting skills, but the client system is different. In an individual conversation, one person owns the topic. In team coaching, the relationships, patterns and shared work are part of the client. Treating a team like several individuals in the same meeting misses the system between them.
ICP-ACC Agile Coaching training develops capability for supporting individuals and teams while choosing among professional coaching, facilitation, mentoring and teaching. That choice becomes important when a team asks for coaching but actually needs a decision process, missing knowledge or a change beyond its authority.
The scope changes the coaching contract
| Dimension | One-to-one coaching | Team coaching |
|---|---|---|
| Client | An individual | The team as a collective system |
| Agenda | Chosen by the individual | Contracted around shared purpose and capability |
| Observation | Language, meaning, choice and emotion | Interaction, participation, roles, conflict and work patterns |
| Confidentiality | Agreed with client and sponsor | Needs explicit group and sponsor boundaries |
| Evidence | Client-defined progress | Collective behaviour and work outcomes |
| Risk | Coach creates dependence | Coach sides with a person or becomes the team's manager |
Know when the team needs facilitation first
A group that cannot make a decision may need a facilitated decision rule, not open-ended coaching. A team missing basic Kanban or Scrum knowledge may need teaching. A new Scrum Master asking how another practitioner handled a similar conflict may want mentoring. Name the stance and obtain agreement instead of calling every helpful intervention coaching.
Coach the interaction, not the absent villain
Teams often explain a problem through somebody outside the room: leadership, another department or a difficult stakeholder. The external constraint may be real. Explore what the team observes, how it responds, which choices it controls and what conversation it is avoiding. Do not turn coaching into a ritual that makes systemic barriers the team's emotional responsibility.
A team-coaching observation sheet
- Who speaks first, last and not at all?
- Where does disagreement become safer or less safe?
- Which decisions return to the coach or manager?
- What happens after new evidence challenges the plan?
- How does the team handle boundaries, commitments and help?
- Which repeated pattern affects customer or delivery outcomes?
Share observations tentatively: “I noticed three decisions returned to Surya after the group had discussed options. What do you make of that?” The team decides whether the pattern is meaningful. A coach who declares a diagnosis too quickly may create compliance instead of learning.
Do not mine private coaching for team insight
If you coach team members individually, explain what will and will not travel into team work. Do not aggregate private disclosures into a supposedly anonymous diagnosis when the source can be inferred. When dual roles make safety impossible, separate the coaches or renegotiate the work.
Measure increased collective capability
A team may become better at surfacing risk, making decisions, challenging assumptions, resolving workable conflict and asking for external change. Delivery evidence can support the conversation, but coaching should not claim sole credit for outcomes shaped by product, technology, staffing and policy.
The guide to teams dependent on the Scrum Master gives one applied case. For career context, read ICP-ACC for Scrum Masters moving into Agile coaching.

