Systemic Team Coaching: Peter Hawkins’s Five Disciplines

Systemic team coaching, in Peter Hawkins’s framework, examines the value a team must create together, how members work and how they engage with the people affected by their decisions. The unit of attention is the collective work and its wider relationships. A series of individual development conversations does not automatically address that work.

Hawkins’s Five Disciplines are Commissioning, Clarifying, Co-creating, Connecting and Core Learning. They provide a connected map of inquiry. They are not five consecutive workshops, a personality test or a guarantee of better performance.

This guide follows a fictional leadership team through one complete service-capacity decision, including stakeholder evidence, a working agreement, an actual trade-off, an external confirmation and a mixed review. The practical tools and case are original applications, not a reproduction of a licensed team assessment.

Understand what each discipline adds

Hawkins’s Leadership Team Coaching and his 2016 Coaching at Work account provide the model’s context. Henley Business School’s Team Coaching guide, page 3, also introduces the five disciplines and distinguishes attention to external conditions from a solely internal view of the team.

Use the map to widen a question when evidence calls for it. A difficult conversation may be partly about relationships, but it could also reflect conflicting goals or an impossible service promise. Moving into another discipline is useful when it changes what the team can understand or do. Renaming an ordinary meeting does not achieve that.

Distinguish the inside, outside, task and relationship questions

The model’s structure matters as much as remembering five names. Commissioning and Clarifying attend to the task: stakeholder expectations outside the team and the collective work inside it. Co-creating and Connecting attend to how people work together inside and across the boundary. Core Learning integrates what the team discovers. These are connected perspectives, not separate departments or a claim that a conversation belongs in only one box.

Commissioning and Connecting can otherwise sound interchangeable. In the case below, asking what the customer needs from the launch helps clarify the requirement. Later, presenting a consistent staged offer, securing acceptance and checking access develops the actual working relationship. An accurate internal statement of stakeholder needs does not establish that the stakeholder has understood or accepted the team’s response.

Clarifying and Co-creating also do different jobs. Naming Leena’s capacity authority clarifies the task arrangement. Changing a conversation in which sales and delivery repeatedly accuse one another concerns how they generate decisions together. A new authority chart may leave the blame pattern intact; a warmer conversation may leave everyone unsure who can approve a promise. The team examines both when the evidence points to both.

Core Learning asks what the collective now understands and changes. It is not an extra presentation about continuous improvement. If every member leaves with an individual task but the same missing information recurs at every handoff, the team should question whether its shared decision process has learned anything.

Check whether there is a real collective task

A group of managers can exchange information without needing to make every decision together. Ask what requires their combined judgment. If every agenda item belongs entirely to one member, consider whether coordination or facilitation is the appropriate service.

A collective task usually involves an interdependence that matters. Sales cannot promise an implementation date without delivery capacity; delivery cannot define a viable service without understanding customer requirements; finance cannot assess the trade-off without knowing the work and commercial terms. The task crosses those boundaries.

Do not imply that team coaching is inherently superior to training, facilitation or consultancy. A team may need instruction in a new system, a facilitated decision, a specialist recommendation or an ongoing coaching relationship. Explain which role you are using and why. The ICF Team Coaching Competencies emphasize the team as a collective client, clear agreements and transparency when using different development roles.

The coach does not acquire the authority to set service prices, assign staff or accept risks. The organization’s authorized people retain those decisions. Coaching supports how the team investigates, decides and learns, while specialist or governance questions receive the appropriate attention.

Worked engagement: a promise that exceeds capacity

The company, people, figures and results in this case are fictional. A six-person implementation leadership team repeatedly blames sales for promising too much and delivery for blocking customer requests. CEO Leo commissions a six-week coaching engagement to improve the team’s collective service decisions, not to identify one person to blame.

The team comprises Leena, operations lead and team chair; Noor, sales; Faye, customer experience; Tomas, product; Owen, finance; and Ari, implementation coordination. They jointly need to agree credible onboarding commitments and an exception route. Leo retains authority over additional spending and changes to existing customer commitments.

The coaching scope includes a contracting session, five short stakeholder interviews, observation and coaching of one decision meeting, and a review and closing session. Individual therapy, confidential individual coaching and a complete operational redesign are not included. If another service becomes necessary, the coach discusses and contracts for it separately.

1. Complete the agreement and evidence plan

The agreement includes what the coach will do if someone privately requests secrecy about information essential to the team task. The coach will clarify the boundary before accepting such material, rather than promising unlimited individual confidentiality and later breaching it. Separate individual coaching, if proposed, needs careful consideration of conflicts and reporting.

The tripartite contracting guide is useful for sponsor and client distinctions. A team engagement adds more parties, so the team’s agreement cannot be inferred from a conversation with its leader alone.

2. Hear stakeholders before diagnosing the team

The five fictional interviews include two customer contacts, two delivery practitioners and a partner coordinator. Each receives the purpose and proposed sharing arrangement. These five perspectives are deliberately selected to investigate handoffs, not presented as representative customer research.

The coach labels the implications as hypotheses. The interviews do not prove that sales is careless, that delivery is inflexible or that all customers would accept a staged service. The team checks actual records and asks the relevant customer about the specific choice.

A stakeholder map also identifies people not interviewed: account support staff, the existing customers whose work might be displaced and the organization’s contract owner. The team does not speak as though those people have agreed. It identifies which decision needs their input and who will obtain it.

Bring the five disciplines into one real decision

The team uses a new customer request as its working case. The next ten-working-day window has thirty available staff-days. Twenty-four are committed to existing work. A standard onboarding needs six staff-days; the customer’s requested customization adds three. Effort estimates include the stated review work, rather than treating quality checks as free capacity.

The following is a ninety-minute coaching agenda for this specific case. It is an original design, not Hawkins’s prescribed session sequence.

1. Ten minutes: Confirm the collective decision and each person’s authority. The aim is a credible customer option, not agreement that every request must be fulfilled.
2. Twenty minutes: Inspect customer requirements, effort, commitments and the partner access dependency. Distinguish verified facts from assumptions.
3. Twenty minutes: Compare options against the same capacity and customer constraints. State whose approval each option needs.
4. Twenty minutes: Observe the team’s discussion. Pause the repeated blame pattern and ask members to build on the constraint another function has identified.
5. Fifteen minutes: Complete the decision record, external question and owner. Do not write “customer agreed” before confirmation.
6. Five minutes: Record one learning point and the date for checking what actually happened.

Commissioning: which requirement is the team serving?

Leo’s request is to reduce unreliable promises, but the team also needs a workable offer for the customer and protection for existing delivery commitments. The customer’s contact confirms that the standard launch matters more than immediate customization. The team now has a different problem from the original demand for every component at once.

The coach asks, “Whose requirement disappears if we treat this as a contest between sales and delivery?” Faye identifies the existing customers who would be delayed by an unapproved swap. The team retains their commitments in the decision rather than making them invisible to win the new request.

Clarifying: what must be decided together?

The arithmetic makes the choice concrete: twenty-four committed days plus six standard days equals thirty, filling the current window. Adding three customization days gives thirty-three, exceeding capacity by three. A faster promise needs a genuine change in scope, capacity or existing commitments.

They compare three options. Deliver all nine days now by displacing existing work, subject to Leo’s approval and the affected customer arrangements. Buy extra capacity, also requiring Leo’s authorization and a realistic availability check. Or offer six standard days now and three customization days in the following window.

The following window has seventeen already committed staff-days against thirty available. Adding customization gives twenty, leaving ten. That makes a staged proposal feasible under the stated estimates. It does not establish that every prerequisite is satisfied or that available staff-days are interchangeable across skills.

Co-creating: change what happens in the meeting

Noor: Delivery always finds a reason to say no.

Leena: And sales expects us to invent three days.

Coach: Pause there. What useful constraint has the other person brought that your proposal must now address?

Noor: We cannot add the customization without changing something already committed.

Leena: The customer needs a launch, but not necessarily the custom part immediately.

Coach: What option becomes possible when both facts stay in the room?

Tomas: Standard onboarding now, customization later, if the customer accepts the boundary and the partner access is ready.

The coach comments on the interaction they observed, not an assumed personality trait. Noor and Leena restate each other’s information, and Tomas combines it into an option. This is different from asking everyone to be more positive while leaving the original contradiction untouched.

Connecting: secure the actual external agreement

Noor and Faye take one consistent proposal to the customer contact: standard onboarding in the current window, customization in the following window, with the actual access prerequisite and agreed review points stated. Ari checks access with the partner coordinator. The team does not send three competing explanations from three departments.

In the fictional result, the customer accepts the staged scope and the organization’s contract owner records the agreed change through its normal process. The partner coordinator confirms the required access is available before the first work starts. These confirmations close two dependencies that an internal workshop could not settle by itself.

Core Learning: preserve the change in how decisions are made

The team records its learning: “We treated customization as inseparable from launch without asking the customer. We also treated spare capacity as a delivery concern rather than evidence for our shared promise.” That finding changes the next decision process.

They add a short pre-promise record requiring customer priority, effort by relevant skill, existing commitments, external prerequisites and the authorized approver. The record is used for a decision, not as a bureaucratic score of whether sales behaved well. The team agrees to inspect exceptions as well as smooth cases.

The completed decision record

The decision remains a plan with acknowledged limits. An effort estimate is not a guarantee, and thirty days of capacity may be unavailable in the right specialist mix. Leena checks the skill allocation before committing the schedule. The fictional case confirms it fits; the team does not use pooled arithmetic to overrule the actual staffing evidence.

For a different view of how working arrangements support collective action, see social architecture in Appreciative Inquiry. The connection is useful when the result needs a changed decision arrangement rather than another statement of shared values.

Review a mixed result and make a second adjustment

At closing, the fictional team compares ten onboarding decisions from the baseline period with ten from the pilot. Four baseline records contained a capacity check before a promise; eight pilot records did. Seven baseline onboardings and eight pilot onboardings met their recorded agreed date. The small comparison is descriptive. It does not isolate coaching from staffing, customer mix or other changes.

Of the two pilot delays, one involved a customer-side access dependency that was not captured in the new record. The other followed an old sales template promising a date before Leena’s approval. These are different problems. The team resists the conclusion that a single extra reminder would solve both.

Ari adds the customer-side access owner and readiness date to the prerequisite check. Noor replaces the outdated template, and Leena and Noor agree that a date remains proposed until capacity approval is recorded. They check the next two decisions and find both use the updated information and approval route. Delivery outcomes for those two are still pending, so they report process use only.

The team’s final learning statement changes: “We checked partner access but overlooked access controlled by the customer. Our sales message could also contradict the decision rule.” The team keeps a fifteen-minute review of exceptions inside its existing weekly meeting. Leena owns the review; the coach does not become its permanent chair.

The six-week coaching engagement closes as agreed. The team has an operating adjustment and a way to investigate future exceptions. Continuing coaching would require another decision and scope. No universal performance improvement or financial return is claimed.

Check whether the team can conduct its own review

During the closing session, Leena chairs a fifteen-minute review while the coach observes. The team chooses the delayed case with missing customer access, rather than its most successful onboarding. Ari presents the record, Noor explains what was promised and Faye separates the customer’s account from the team’s earlier assumption. The coach does not supply the interpretation first.

Leena asks three questions: “What did we know when we promised? What did we assume? What must change before the next promise?” The team identifies that “access ready” referred only to the partner system. Customer-controlled access had no named owner. Their completed review entry reads:

Assumption found: We used one access label for two dependencies and treated confirmation of one as confirmation of both.

Change: The pre-promise record now separates partner and customer access, names an owner for each and records their actual readiness dates.

Evidence still needed: The next two decisions use the revised record, but their delivery dates have not yet occurred. Check the outcomes at the scheduled team review.

Review owner: Ari brings the two records; Leena chairs the discussion within the existing weekly meeting.

The coach’s observation is limited but useful: the team selected an exception, examined its own assumptions, changed a shared tool and named the unresolved evidence. It does not prove permanent self-sufficiency. The team also identifies a condition for seeking help again: repeated conflicting commitments that it cannot resolve through its authority and escalation route. That future request would be assessed against a new scope.

When more team inquiry is not the next answer

Consider a contrasting fictional team with thirty staff-days of capacity, forty days of mandatory work and no authority to change either. Members may benefit from expressing the conflict clearly, but improved relationships cannot create ten missing staff-days. The next output is a capacity and priority decision for the authorized sponsor.

Similarly, listening to a customer does not require accepting every demand. A team can understand a need and decline it, offer an alternative or explain a service boundary. Connecting means an honest relationship, including disagreement and limits.

If an allegation of misconduct or discrimination arises, follow appropriate processes and qualified support. Do not turn a team coaching session into an informal investigation or pressure a person to disclose sensitive evidence in front of colleagues. Recontract if the proposed work changes materially.

Keep the shared work and private evidence distinct in Coachful

Coachful is our #1 recommendation for organizing the agreed team sessions, shared resources and review prompts around this work. A dedicated Program and cohort can structure delivery for the participating client team. The software supports the agreed process; it does not grant business decision authority or verify implementation capacity.

The demo community feed illustrates discussion and a live-session entry. For the six leaders, use the intended cohort or restricted space and verify the actual membership and visibility. A workspace’s general community may include other clients. Do not post raw stakeholder interviews there or assume that the word “team” makes a space confidential.

1. Create the specific delivery scope. Add the contracted sessions and shared resources to the relevant Program or access arrangement. Describe what is included accurately.
2. Use a concise worksheet. Capture the collective decision, evidence, unresolved dependency, owner and review date. It is a working prompt, not a licensed Five Disciplines diagnostic.
3. Assign the shared materials deliberately. Check that the intended clients can open them. A private link alone does not grant access.
4. Keep interview material separate. Share only the permitted summaries. An individual form response is not automatically suitable for a team post.
5. Review the next real case. Use the saved question and selected actions to support the team’s inquiry. Task completion alone does not establish collective learning.

The form-builder screenshot shows question authoring. It is not a validated team score or evidence from this fictional engagement. When reusing a Program template for another company, review its resources and membership; do not copy a prior client’s confidential working material. Template changes and existing cohort synchronization are separate actions with their own scope.

Explore Coachful’s coaching features to assemble the delivery and recordkeeping workflow. Confirm the client-facing experience and the actual access boundaries before using it for confidential team work.

Troubleshooting common team-coaching errors

The sponsor wants the coach to fix one member. Clarify whether the contract is for the whole team or a separate individual service. Ask what collective pattern and work outcome the sponsor wants changed. Do not accept a covert performance assessment under a team-development label.

Members agree in the meeting and contradict it outside. Check whether the decision was actually recorded, who had authority and what messages remain in use. In the case, the old template contradicted the new rule. Diagnose the record and incentive problem before calling it a lack of commitment.

Stakeholder interviews produce incompatible wishes. Keep the conflict visible. Identify the decision criteria, affected people and authorized trade-off. Summarizing all perspectives does not create consensus or permission to promise all of them.

The team becomes dependent on the coach’s interpretation. Ask members to describe the pattern and evidence before offering your view. Transfer review ownership explicitly, test one team-led review and retain uncertainty about what has not yet been observed.

Frequently asked questions

What are Hawkins’s Five Disciplines?

Commissioning, Clarifying, Co-creating, Connecting and Core Learning. They connect stakeholder requirements, collective tasks, internal and external relationships, and shared learning.

Are the Five Disciplines a sequence?

No. A team may move between them within one decision, as the case demonstrates. Use the relevant inquiry rather than assigning each label a fixed session.

What makes the work systemic?

It examines the team’s collective work alongside stakeholders, dependencies and wider conditions. The case changes an internal discussion by checking customer priorities and access dependencies outside the team.

Does the coach decide the trade-off?

No. The coach supports inquiry and learning. The team and authorized organizational roles decide capacity, scope, spending and commercial commitments.

How can the team show progress?

Review actual decisions, handoffs and exceptions against clear definitions. Report small samples and alternative explanations honestly, and distinguish a changed process from a proven performance or financial effect.