Ask a manager how they develop their people and most will describe advice: sharing experience, solving problems, showing the way. It feels like development. Mostly it manufactures dependence — and the alternative is a learnable discipline, not a personality change.
To coach your team rather than simply telling them what to do, hold conversations that make the other person do the thinking. Use a simple structure such as GROW — establish what they actually want, examine the reality, generate options before evaluating them, and agree a committed next step. Ask open questions and tolerate the silence in which thinking happens. Combine coaching with honest, specific feedback, use mentoring deliberately as a separate tool, and the payoff compounds into a team that grows capability instead of dependence.
There is a moment every manager knows. A team member arrives with a problem; you know the answer; you give it; they leave satisfied. Repeat this for a year and observe the result: a team that brings you everything, a calendar with no room in it, and people who are no more capable than when they joined — because the thinking has been done for them, reliably, on demand. The manager experiences this as being indispensable. It is actually the failure mode. Coaching is the alternative, and it is widely misunderstood as either therapy or a soft skill. It is neither. It is a structured way of holding a conversation so that the other person does the thinking — and it changes what a team is capable of.
The reason “be more coach-like” fails as advice is that under time pressure, everyone reverts to telling. What holds is structure. The recognised models — GROW is the best known — are essentially the same four moves: establish what the person actually wants from the situation (which is rarely what they opened with), examine what is really going on, generate options before evaluating them, and end with a committed next step. Ten minutes of that beats thirty minutes of advice, because the conclusion the person reached themselves is the one they will act on. The manager’s discipline is mostly restraint: the answer you are holding back is the space in which they think.
The engine of a coaching conversation is the question that makes someone stop and think rather than recite. “What have you already tried?” “What’s the real difficulty here, for you?” “What would you do if I were unavailable?” Open, short, and free of the manager’s hypothesis smuggled in (“have you considered…” is advice wearing a question’s clothing). Then the harder half: listening to understand rather than listening to respond, and tolerating the silence in which actual thinking happens. Most managers rescue people from that silence within three seconds. The ones who learn to wait discover their people knew more than either party assumed.
The answer you are holding back is the space in which they think.
Coaching without honest feedback collapses into pleasant vagueness. The combination that develops people is specific observation plus coaching question: here is what I saw, here is the effect it had — what was going on for you, and what would you do differently? Delivered soon, about behaviour rather than character, and with genuine curiosity about the answer, this is how performance conversations stop being annual ordeals and become the ordinary texture of working together.
Coaching draws out; mentoring pours in — experience, context, career navigation, doors opened. Teams need both, and confusion between them causes quiet damage: the mentor who only interrogates when guidance was needed, the coach who dispenses war stories when thinking was needed. The practical fix is contracting — agreeing explicitly what kind of help this relationship is for, what the boundaries are, and how you will both know it is working. Five minutes of contracting saves months of well-intentioned mismatch.
The compounding returns arrive when this stops being one manager’s style and becomes how the organisation develops people: managers coached on their coaching, mentoring schemes designed rather than left to chance, development conversations expected at every level, and talent grown by design instead of discovered by luck. Organisations that build this pipeline stop being surprised by succession questions — and their best people stay longer, because the surest way to retain someone ambitious is to be visibly invested in what they are becoming.
Coaching your team means developing people by helping them do their own thinking, rather than by supplying answers. It is widely misunderstood as either a therapeutic activity or a vague soft skill; it is neither. Coaching is a structured way of holding a conversation so that the other person reaches the conclusion, commits to the action, and builds the capability — because the answer someone works out themselves is the one they actually act on and remember. This is the precise opposite of the default managerial reflex, in which a team member brings a problem, the manager supplies the solution, and both leave satisfied while the team quietly grows more dependent and the manager’s calendar fills with problems only they can solve. Coaching trades the momentary efficiency of telling for the compounding return of capability.
A manager known for being endlessly available — the person everyone brought their problems to — was also, not coincidentally, drowning and unable to develop his people. The change began with a single substituted response. Instead of answering the next “what should I do about X?” with a solution, he asked, “what have you already considered?” and waited through the uncomfortable silence. The team member, who had expected to be handed an answer, thought for a moment and produced two reasonable options and a clear preference. The manager asked one more question — “what would you do if I were on leave?” — and the person effectively coached themselves to a decision. Multiplied across a team over months, that shift — from dispensing answers to asking questions and tolerating the silence — both freed the manager’s time and visibly grew the team’s capability. The restraint was the whole intervention: the answer he held back was the space in which they thought.
The returns from coaching compound when it stops being one manager’s personal style and becomes how the organisation develops people at every level. That requires deliberate structure rather than exhortation: managers who are themselves coached on their coaching, mentoring schemes that are designed rather than left to chance, development conversations that are expected and scheduled rather than improvised, and talent that is grown by intention rather than discovered by luck. Organisations that build this pipeline stop being blindsided by succession questions, because capability is being developed continuously rather than assumed. They also retain their most ambitious people longer, for a straightforward reason: the surest way to keep someone who wants to grow is to be visibly, structurally invested in what they are becoming — which a genuine coaching culture demonstrates in a way that no retention bonus can replicate.
Coaching draws out — it helps a person do their own thinking through structured questions. Mentoring pours in — experience, context and guidance. Teams need both, and the practical fix for confusion between them is contracting: agreeing explicitly what kind of help a relationship is for.
Use a simple structure such as GROW: establish what the person actually wants, examine what is really going on, generate options before evaluating them, and end with a committed next step. The manager's main discipline is restraint — the answer you hold back is the space in which they think.
Solving problems for people feels like help but manufactures dependence: the team brings you everything, your calendar fills, and no one grows because the thinking has been done for them. Coaching develops capability precisely because the person reaches the conclusion themselves — which is also the conclusion they will act on.