Coaching versus directing

Coaching develops a person's judgment, and directing gives them an answer. Each has its place. Managers lean too heavily on directing, and on its most tempting form, rescuing: stepping in with the solution as soon as someone struggles. Rescuing feels helpful and is quicker today. It also teaches people that they are not trusted to think, limits the organisation's capability to the manager's own, and turns people into dependents. The competency consists of asking before telling by default, accepting a slower or different route when it serves someone's growth, and keeping directing for real emergencies, true novices and stakes that leave no room. When the manager does direct, they name it as the exception instead of sliding into it as a habit. It matters because this is how a team comes to be more capable than its manager, and because every other competency in this standard that involves developing someone (delegation, feedback, career growth, leading through leaders) depends on it. The examinations test it through the engineer who brings every decision to the manager, the manager who says "just tell me what to do", the review culture that defaults to blame whatever the policy says, and the organisation that has learned to wait for the executive's answer.

1. Ask before telling. "What options have you considered?" "What would you do if I weren't here?" Questions develop judgment, and an answer takes its place.
2. Tolerate the slower path. Someone who reaches a sound decision by a route the manager would not have chosen has learned something that the manager's answer would have stopped them learning. The discomfort of watching is what growth costs.
3. Direct deliberately and name it. In an emergency, with a true novice on a task, or where the stakes leave no room, directing is right. The manager says out loud that it is the exception, so that it does not become the default.
4. Rescuing is the failure that feels like help. Stepping in at the first wobble ends the learning and teaches the team that ownership can be taken back at any time. The alternative is support that leaves the decision with the person.
5. Coach the reasoning, especially when asked for the verdict. A manager who asks to be told what to do is asking to be made dependent. Work through the trade-offs together and decline the trade.
6. Model it, or it does not spread. Leaders build a coaching culture by asking for feedback in public, coaching where others can see and being coachable themselves. A mandate from someone who commands will never build one.

The practitioner literature on coaching is large and the experimental evidence in management settings is thin. The unit grades its models as practice and borrows one from the leadership literature.

The GROW model practice

John Whitmore, Coaching for Performance: GROWing People, Performance and Purpose (1992) sets out a coaching structure of Goal, Reality, Options and Will: what the person wants, where they are now, what they could do and what they will do. For managers its value is that it gives "ask before telling" a shape, with four questions a manager can keep hold of in a one-on-one without training. Its limit is that it structures a conversation. It does not replace the manager's judgment about when a conversation is the wrong tool.

Situational leadership practice

This is the model from Paul Hersey and Kenneth H. Blanchard, Management of Organizational Behavior: Utilizing Human Resources (1969), introduced in PL-1 Delegation, ownership, and decision rights and applied here to the choice between coaching and directing. Someone new to a task needs directing, then coaching as their competence grows, then supporting, then delegating. It explains why "always coach" is as wrong as "always direct". A true novice on a task needs direction, and coaching them amounts to abandonment with better manners. Style follows the task, whatever the person's seniority.

The rescue reflex practice

This is the failure the unit treats as central, though it is not a named model. The manager instinctively steps in with the solution as soon as someone struggles. It feels like help and it is faster today, and it teaches the person that they are not trusted to think. In an organisation it shows up as the manager of managers doing a manager's job, and at executive level as an organisation that has learned to wait for the executive's answer. Its provenance is experience, and the examinations use it because it is so easy to recognise.

The learning organisation practice

Peter M. Senge, The Fifth Discipline: The Art and Practice of the Learning Organization (1990) gave influential form to the idea that an organisation can be designed to learn, turning experience into shared capability instead of leaving it as local memory. In this unit it supplies the practice at executive scope: lessons from incidents that travel between teams, postmortem actions audited until they are done, slack funded for learning, and leadership reviews that take what was learned as seriously as what was shipped. It is graded as practice, and the book's systems-thinking claims are broader than what is used here.

Coaching the coaches practice

Again this is not a named model. It is the organisational-scope practice from PL-6 Leading through leaders, seen from the coaching side. Managers develop judgment when someone coaches their reasoning on real situations, which is what the judgment debrief does. The manager of managers should watch for the avoidance patterns of the managers they lead. A manager who cannot deliver a hard truth, or who asks to be told what to do, has a capability gap that will show up everywhere they go.

The question first

Whenever someone brings a problem, the manager responds first with a question: what have you considered, what would you do, what is stopping you? If an answer comes at all, it comes after the person has run out of their own thinking. This habit is what makes coaching the default and directing the exception.

The named exception

When the manager directs, they say that they are doing so: "I am going to make this call, because it is an emergency", or "because this is your first one". Naming it stops directing from becoming the default, and it tells the person that ownership will come back to them.

The wobble protocol

When delegated work is struggling, the manager lays out the options before acting. They can support (provide resources, remove a blocker), coach (ask questions that help the person see what they missed) or rescue (take the work over). Rescue is chosen only when being wrong would be costly and irreversible, and then it is done openly and with the reason given, as in PL-1 Delegation, ownership, and decision rights.

The judgment debrief

With a manager who reports to you, the regular one-on-one centres on a hard call they are facing or have just made: what they saw, what they weighed and what they chose. The manager of managers asks and holds back their own answer until the reasoning has run its course. When the manager says "just tell me what to do", they go through the trade-offs together instead.

The peer case discussion

Managers meet as peers to talk through real situations that one of them is facing, and coach each other with questions. It is the cheapest way to build a coaching culture. It only works if the manager of managers models it by asking for feedback in the room, being visibly coachable, and coaching where they might otherwise rule.

Learning loops, audited

At organisational scope the learning system itself gets checked. Do lessons from incidents cross team boundaries? Are postmortem actions closed? Is there slack to learn? Does the leadership review ask what was learned? A learning culture that exists only in policy dies at the first executive review with a flavour of blame, and one visible exception undoes a hundred training sessions.

At team scope the object is an engineer's judgment, developed in place of supplying answers. The manager coaches by default, accepts the slower path and directs deliberately. At organisational scope the object is the judgment of managers. The manager of managers coaches the coaches through judgment debriefs, treats a manager's avoidance patterns as the thing to develop, declines to hand down verdicts to a manager who asks for them, and builds the peer practice that turns a coaching culture into something real. At executive scope the object is the learning organisation. Reviews across the whole organisation learn instead of blaming, learning loops are built into how the organisation works and audited, and the coaching cascade runs through every level of leadership. The executive also recognises that an organisation which waits for their answer was taught to wait. The pattern is set out in How Judgment Scales; the managers being coached are the subject of PL-6 Leading through leaders.

• Defaults to coaching in developmental moments, with questions before answers. team
• Lets a person take a slower or different path and learn from it. team
• Directs only when the stakes or someone's inexperience require it, and names it as the exception. team
• Recognises the rescue reflex in themselves and chooses support or coaching instead.
• Coaches a strong engineer who does not mentor, document or lift others, and does not accept that technical strength exempts them. team
• Failure mode: rescuing at the first wobble. team
• Failure mode: being the source of every answer. team
• Failure mode: coaching through a real emergency that needed a call. team
• Failure mode: abandoning a true novice in the name of empowerment.
• Coaches a manager who gives only positive feedback on what their kindness is costing, with low-stakes practice and explicit backing through the discomfort. org
• Treats a manager's repeated avoidance of a hard conversation as the subject of the coaching, because it will recur everywhere. org
• Declines the trade when a manager says "just tell me what to do", and works through the trade-offs with them in place of issuing a verdict. org
• Coaches a manager who is too hands-off on the difference between empowering and abandoning: delegation with context, checkpoints and presence. org
• Builds the coaching culture through peer case discussions, managers observing and debriefing each other, and visible modelling from the head of the department. org
• Failure mode: handing answers to managers and calling it mentoring. org
• Failure mode: letting kindness that avoids conflict pass for people skills. org
• Failure mode: mandating a coaching culture while modelling command and control. org
• Changes reviews that default to blame across the organisation using every tool available: retraining how reviews run, leaders who understand safety in the rooms that matter, public reward for the honest review, and no visible exception left standing. exec
• Builds the learning loops into the organisation: lessons that travel between teams, actions audited until they are done, slack to learn, and "what did we learn?" treated as a first-class executive question. exec
• Runs the coaching cascade through every level of leadership, so that the organisation's culture teaches itself. exec
• Recognises that an organisation which brings decisions fully formed and waits for approval was taught to do so, and changes what the executive does. exec
• Failure mode: a learning culture that exists in policy and dies at the first executive review with a flavour of blame. exec
• Failure mode: lessons that never cross team boundaries. exec
• Failure mode: treating slack for learning as waste to be optimised away. exec

Speed versus development. The answer is quicker today, and the question builds someone who will not need to ask tomorrow. The tension comes up in every one-on-one, and a manager who always settles it in favour of speed ends up with a team that cannot decide.

Coaching versus direction. Coaching all the time abandons the novice, and directing all the time creates dependents. The resolution is situational judgment about the task, the person's experience of it and the stakes. The failure is choosing one mode by temperament.

Support versus rescue. From outside both look like help, and only support leaves the decision with the person. The dividing line is who decides at the end of the conversation, and the manager has to notice which side of it they are standing on.

Kindness versus growth. A manager who spares people any struggle is liked, and the people do not grow. A manager who lets them struggle for what it teaches can seem indifferent. The answer is to stay present through the struggle without ending it, and to explain why.

Policy versus exception. A learning culture can be written into policy, trained and measured, and a single visible review by a senior leader with a flavour of blame wipes it out. The exception sets the culture, not the rule, so the executive's job is to make sure the exception never happens.

A team manager has a capable engineer, eighteen months into the job, who brings every decision to them: which library to use, whether to split a pull request, how to answer a stakeholder's question, whether a design is ready for review. Each question takes the manager thirty seconds, the answers are good, and the engineer carries them out well. The manager has noticed that they are answering a dozen of these a day, and that the engineer's design documents no longer contain recommendations.

The easy path is to keep answering. The questions are quick, the answers are right, and it feels like being a helpful manager. This is the rescue reflex in its mildest and most corrosive form. The manager has become the engineer's judgment, and the engineer has learned that asking is the safe move.

The manager starts by changing their own behaviour. When the next question comes, they ask what the engineer would do and why, and then they wait. The first answers are tentative and hedged. The manager asks what would happen if they were on holiday, and the engineer comes up with a decision and a reason. The manager says "do that". In the weeks that follow they keep to the pattern, answering questions with questions. When the engineer's reasoning is sound the manager says so and nothing more. When it is not, the manager asks what the engineer has not considered, without supplying it. Design documents are now expected to end with a recommendation, and when the manager reviews them they ask about the reasoning behind the recommendation and leave the recommendation itself to the engineer.

The manager does two things deliberately. First, they tell the engineer what they are doing and why ("I have been answering questions you can answer, and I am going to stop, because I want your judgment, not mine, in this work"), so that the change is not taken as withdrawal. Second, they name the exceptions. Anything touching the payment path or a customer commitment should still come to the manager, and the manager will say when a decision falls into that category.

Three months on, the questions are down to two or three a week, and most are ones the manager wants to hear. The engineer has led a design the manager would not have chosen, and it worked. What the manager stopped doing was being helpful, because that helpfulness had been capping the engineer at the manager's own judgment.

• PL-1 Delegation, ownership, and decision rights: delegation, where the choice between coaching and rescue is made, and the discipline of not taking work back.
• PL-6 Leading through leaders: coaching the coaches, and the judgment debrief with a manager.
• PL-5 Career development and growth paths: coaching as the form growth takes when the aim is judgment.
• CC-1 Psychological safety and productive conflict: the safety that lets someone answer "what would you do?" honestly.
• DE-3 Reliability, incident response, and operational ownership: the blameless review as the central ritual of a learning organisation.

1. What does habitual rescuing teach a team?
   Answer

   That they are not trusted to think, that ownership can be taken back, and that asking is the safe move. It limits the team's capability to the manager's and creates dependents.
2. When is directing the right choice, and what is the discipline that keeps it from becoming the default?
   Answer

   In real emergencies, with true novices on a task, and where the stakes leave no room. The discipline is to name it out loud as the exception ("I'm making this call because…") so that ownership is seen to return afterwards.
3. What are the four questions of the GROW model, and what are they for?
   Answer

   Goal, Reality, Options and Will: what the person wants, where they are now, what they could do and what they will do. They give "ask before telling" a shape that a manager can hold on to in a one-on-one.
4. A manager who reports to you says "just tell me what to do". Why is answering them the worst available move? org
   Answer

   Handing verdicts to a manager makes them permanently dependent, and their team ends up run on your judgment at one remove. Work through the trade-offs together and coach the reasoning; decline the trade.
5. A manager gives only positive feedback to avoid conflict and their team's growth is stalling. What is the coaching? org
   Answer

   Coach them on what their kindness is costing, meaning the link between honest feedback and their team's development. They practise in low-stakes repetitions, with your explicit backing through the discomfort. The avoidance is itself the development need and should not be treated as a side issue.
6. What does it take to change blame-defaulting reviews across an organisation, and why does one visible exception undo it? exec
   Answer

   Retraining how reviews are run, putting leaders who understand safety in the rooms that matter, publicly rewarding the honest review that brought the ugly truth out, and leaving no visible exception standing. The exception sets the culture, and one senior review with a flavour of blame teaches the organisation what the real rule is.
7. What does an organisation that brings decisions fully formed and waits for approval tell the executive? exec
   Answer

   That it was taught to. The fix is for the executive to change what they do, asking questions in place of handing down rulings and pushing decisions down explicitly. Asking people to be more decisive will not fix it.

• John Whitmore, Coaching for Performance: GROWing People, Performance and Purpose (1992): the GROW model.
• Paul Hersey and Kenneth H. Blanchard, Management of Organizational Behavior: Utilizing Human Resources (1969): situational leadership; directing as what the novice needs.
• Peter M. Senge, The Fifth Discipline: The Art and Practice of the Learning Organization (1990): the learning organisation.