Coaching versus directing

Coaching develops a person's judgment; directing gives them an answer. Both have a place, and managers over-rely on directing and on its most seductive form, rescuing — stepping in with the solution the moment someone struggles. Rescuing feels helpful and is faster today, and it teaches people that they cannot be trusted to think, caps the organisation's capability at the manager's, and manufactures dependents. The competency is the default of asking before telling, the tolerance of a slower or different path taken in the service of growth, and directing reserved for genuine emergencies, true novices and stakes that leave no room — named as the exception rather than slipped into as the habit. It matters because it is the mechanism by which a team becomes more capable than its manager, and because every other competency in this standard that involves developing someone — delegation, feedback, career growth, leading through leaders — runs 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 despite the policy, 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?" The questions develop the judgment; the answer replaces it.
2. Tolerate the slower path. A person who reaches a sound decision by a route the manager would not have taken has learned something the manager's answer would have prevented. The discomfort of watching is the price of growth.
3. Direct deliberately and name it. Genuine emergencies, true novices on a task, stakes that leave no room: directing is right, and it is said aloud as 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 is provisional. 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 a dependent. Walk the trade-offs together; refuse the trade.
6. Model it, or it does not spread. A coaching culture is built by leaders who ask for feedback publicly, coach visibly and are coachable — never by mandate from someone who commands.

Coaching has a large practitioner literature and thin experimental evidence in management settings; the unit grades its models as practice and borrows one from the leadership literature.

The GROW model practice

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

Situational leadership practice

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 coaching-versus-directing choice: directing for someone new to a task, coaching as competence grows, supporting, delegating. It is the reason "always coach" is as wrong as "always direct" — a true novice on a task needs direction, and coaching them is abandonment with better manners. Style tracks the task, not the person's seniority.

The rescue reflex practice

Not a named model but the failure this unit treats as central: the manager's instinct to step in with the solution the moment someone struggles, which feels like help, is faster today, and teaches the person that they cannot be trusted to think. Its organisational form is the manager of managers doing a manager's job, and its executive form is an organisation that has learned to wait for the executive's answer. Its provenance is experiential; its recognisability is why the examinations use it.

The learning organisation practice

The idea, given its influential form in Peter M. Senge, The Fifth Discipline: The Art and Practice of the Learning Organization (1990), that an organisation can be designed to learn — to convert experience into shared capability rather than local memory. For this unit its content is the executive-scope practice: incident learnings that travel between teams, postmortem actions audited to completion, slack funded for learning, and leadership reviews that ask what was learned with the same seriousness as what was shipped. Graded as practice; the book's systems-thinking claims are broader than what is used here.

Coaching the coaches practice

Not a named model but the organisational-scope practice from PL-6 Leading through leaders, stated here from the coaching side: managers' judgment is developed by coaching their reasoning on real situations — the judgment debrief — and the manager of managers' own avoidance patterns are the ones to watch, because a manager who cannot deliver hard truth, or who asks to be told what to do, has a capability gap that will repeat everywhere.

The question first

In any conversation where someone brings a problem, the manager's first response is a question — what have you considered, what would you do, what is stopping you — and the answer, if it comes at all, comes after the person has exhausted their own thinking. The habit is what makes coaching the default rather than the exception.

The named exception

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

The wobble protocol

When delegated work is struggling, the manager's options are listed before they act: support (resources, removing a blocker), coach (questions that help the person see what they missed), rescue (taking it over). Rescue is chosen only when the cost of being wrong is high and irreversible, and it is done explicitly, with the reason, as in PL-1 Delegation, ownership, and decision rights.

The judgment debrief

With a manager who reports to you, the recurring one-on-one is built around the hard call they face or just made: what they saw, what they weighed, what they chose. The manager of managers asks and does not answer until the reasoning is exhausted, and when the manager says "just tell me what to do", walks the trade-offs with them instead.

The peer case discussion

Managers meet as peers to discuss real situations one of them is facing, coaching one another with questions. It is the cheapest way to build a coaching culture, and it works only if the manager of managers models it: asks for feedback in the room, is visibly coachable, and coaches rather than rules.

Learning loops, audited

At organisational scope, the learning system is checked: do incident learnings 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 in policy dies in the first blame-flavoured executive review, and one visible exception undoes a hundred trainings.

At team scope the object is developing an engineer's judgment rather than supplying the answer, and the manager coaches by default, tolerates the slower path, and directs deliberately. At organisational scope the object is managers' judgment — coaching the coaches through judgment debriefs, treating a manager's avoidance patterns as the development need, refusing to issue verdicts to a manager who asks for them, and building the peer practice that makes a coaching culture real. At executive scope the object is the learning organisation: reviews that learn rather than blame across the whole organisation, learning loops institutionalised and audited, the coaching cascade running through every leadership level, and the recognition that an organisation which waits for the executive's answer has been taught to. The pattern is in How Judgment Scales; the managers being coached are PL-6 Leading through leaders.

• Defaults to coaching in developmental moments: questions before answers. team
• Lets a person take a slower or different path and learn from it. team
• Directs only when stakes or inexperience genuinely demand 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, rather than accepting that their technical strength exempts them. team
• Failure mode — rescuing at the first wobble. team
• Failure mode — being the source of all answers. 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 for the discomfort. org
• Treats a manager's repeated avoidance of a hard conversation as the coaching subject itself, because it will repeat everywhere. org
• Refuses the trade when a manager says "just tell me what to do": walks the trade-offs together rather than issuing the verdict. org
• Coaches a too-hands-off manager 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 top of the department. org
• Failure mode — issuing answers to managers and calling it mentoring. org
• Failure mode — letting conflict-avoidant kindness pass as people skills. org
• Failure mode — mandating a coaching culture while modelling command and control. org
• Changes blame-defaulting reviews across the organisation with the full toolkit: retraining how reviews run, safety-literate leaders in the rooms that matter, the honest review publicly rewarded, and no visible exception allowed to survive. exec
• Institutionalises the learning loops: learnings that travel between teams, actions audited to completion, slack to learn, "what did we learn?" as a first-class executive question. exec
• Runs the coaching cascade through every leadership level, so the organisation's culture teaches itself. exec
• Recognises an organisation that brings decisions fully formed and waits for approval as one that has been taught to, and changes what the executive does. exec
• Failure mode — a learning culture that exists in policy and dies in the first blame-flavoured executive review. exec
• Failure mode — lessons that never cross team boundaries. exec
• Failure mode — slack for learning treated as waste to optimise away. exec

Speed versus development. The answer is faster today and the question builds the person who will not need to ask tomorrow. The tension is real in every one-on-one, and the manager who always resolves it toward speed builds a team that cannot decide.

Coaching versus direction. Always coaching abandons the novice; always directing manufactures dependents. Situational judgment — the task, the person's experience with it, the stakes — is the resolution, and the failure is applying one mode by temperament.

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

Kindness versus growth. The manager who spares people struggle is liked and produces people who have not grown; the manager who tolerates struggle for its lessons can look indifferent. The resolution is to be present through the struggle without ending it, and to say why.

Policy versus exception. A learning culture can be written into policy, trained and measured, and one visible blame-flavoured review by a senior leader undoes all of it. The tension is that culture is set by the exception, not the rule, and the executive's job is to make sure the exception never happens.

A team's manager has an engineer, eighteen months in and capable, who brings every decision to them. Which library to use, whether to split a pull request, how to respond to a stakeholder's question, whether a design is ready for review. Each question takes the manager thirty seconds to answer, the answers are good, and the engineer executes them well. The manager has noticed that they are answering a dozen such questions a day and that the engineer's design documents have stopped containing recommendations.

The easy path is to keep answering; the questions are quick, the answers are right, and it feels like being a helpful manager. It 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 the safe move is to ask.

The manager changes their own behaviour first. The next time a question arrives, they ask what the engineer would do and why, and they wait. The first answers are tentative and hedged; the manager asks what would happen if they were on holiday, and the engineer produces a decision and a reason. The manager says "do that". Over the following weeks the pattern is held: questions get questions, and when the engineer's reasoning is sound the manager says so and nothing else, and when it is not the manager asks what the engineer has not considered rather than supplying it. The engineer's design documents are asked to end with a recommendation, and the manager's review of them asks about the recommendation's reasoning rather than replacing it.

Two things are done deliberately. The manager tells 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 read as withdrawal. And the manager names the exceptions: for anything touching the payment path or a customer commitment, the engineer should still bring the decision, and the manager will say so when it is one of those.

In three months the questions have fallen to two or three a week, most of them the ones the manager wants to hear, and the engineer has led a design the manager would not have chosen and that worked. What the manager does not do is keep being helpful, which was the thing that was capping the engineer at the manager's own judgment.

• PL-1 Delegation, ownership, and decision rights — delegation as the setting in which coaching versus rescue is decided; not taking work back.
• PL-6 Leading through leaders — coaching the coaches; the judgment debrief with a manager.
• PL-5 Career development and growth paths — coaching as the form growth takes when the goal is judgment.
• CC-1 Psychological safety and productive conflict — the safety that lets a person answer "what would you do?" honestly.
• DE-3 Reliability, incident response, and operational ownership — the blameless review as the learning organisation's central ritual.

1. What does habitual rescuing teach a team?
   Answer

   That they cannot be trusted to think, that ownership is provisional, and that the safe move is to ask. It caps the team's capability at the manager's and manufactures dependents.
2. When is directing the right choice, and what is the discipline that keeps it from becoming the default?
   Answer

   Genuine emergencies, true novices on a task, and stakes that leave no room. Naming it aloud as the exception — "I'm making this call because…" — so that ownership visibly returns afterward.
3. What are the four questions of the GROW model, and what are they for?
   Answer

   Goal, Reality, Options, Will — what the person wants, where they actually are, what they could do, what they will do. A shape for "ask before telling" that a manager can hold 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

   Because supplying verdicts to a manager manufactures a permanent dependent whose team is then run on your judgment at one remove. Walk the trade-offs together and coach the reasoning; refuse 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

   On what their kindness is costing — the link between honest feedback and their team's development — practised in low-stakes repetitions with your explicit backing for the discomfort. The avoidance is the development need, not a side note.
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, safety-literate leaders in the rooms that matter, the honest review that surfaced the ugly truth publicly rewarded, and no visible exception allowed to survive — because culture is set by the exception, and one blame-flavoured senior review 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 has been taught to. The fix is a change in what the executive does — questions instead of rulings, decisions pushed down explicitly — not a request that people be more decisive.

• 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 the novice's need.
• Peter M. Senge, The Fifth Discipline: The Art and Practice of the Learning Organization (1990) — the learning organisation.