The Quickest Mind in the Room: Choosing When to Advise and When to Coach
Photo: Tom Poole, CC BY-SA 2.0, via Wikimedia Commons
Most managers who answer quickly are not acting from vanity. They are trying to keep work moving, reduce risk and spare their team unnecessary uncertainty. In lean UK teams with fixed delivery dates, that instinct is understandable. The difficulty is not the occasional direct answer. It is the pattern in which the most experienced person in the room becomes the only person expected to think.
The hidden trade-off in a fast answer
An immediate answer has obvious advantages. It saves time, limits exposure and is often correct. But repeated across weeks and months, it teaches the team that escalation is rewarded and that half-formed proposals are acceptable. The manager becomes a queue rather than a coach. Decisions still get made, yet the range of decisions the team is trusted to make becomes narrower.
The aim is not to make managers slower or to introduce uncertainty for its own sake. It is to make the team more capable at the same pace. That requires distinguishing between a genuine need for direction and a habit of supplying it.
A three-step check before you respond
Before answering, run a short mental check. It need take no more than a few seconds.
- Is the matter time-critical, high-risk or outside the person’s authority? If so, advise. Safety, legal, compliance, reputational and irreversible spending decisions are not coaching experiments.
- Does the person have enough context to form a view? A new starter may need an answer with an explanation. An experienced colleague may need a question and a boundary.
- What is the cost of a wrong call? If it is low and reversible, let the person decide and review afterwards. If it is high, guide the decision rather than merely observing it.
The output should be one of three responses: advise, coach or defer. Deferring does not mean avoiding the issue. It means setting a time and a format for a decision, usually with a recommendation attached.
Scripts that set expectations
Managers often avoid coaching because it can feel like a quiz. The remedy is to state your intention plainly.
When advising: ‘I am going to give you a direct answer this time because the client deadline is today. The reason is X. For the next similar decision, I would like you to bring me two options and your recommendation.’
When coaching: ‘I have a view, but before I share it, what have you considered so far? … Which option would you be willing to test first?’
When deferring: ‘This does not need a decision today. Bring me a one-page recommendation by Tuesday and I will challenge it, not replace it.’
These lines do several things at once. They respect the pressure the person is under, they preserve the manager’s accountability and they make the next conversation more useful.
When advice is the professional choice
There is no virtue in withholding an answer when the situation clearly calls for one. If a supplier contract contains an unusual liability clause, a customer complaint risks breaching a regulatory requirement, or a team member is about to make an irreversible commitment, advise. The skill lies in giving the answer with the reasoning attached.
A useful habit is to pair the instruction with the principle behind it: ‘Approve the extension, because the penalty for late delivery is greater than the cost of the additional week. The principle is that we protect the client relationship where the financial exposure is disproportionate.’ That turns an instruction into a reusable judgement.
When coaching earns its place
Coaching is most valuable when the person has enough context to reason, the stakes are manageable and the issue is likely to recur. It should be focused rather than open-ended. Two or three questions are usually sufficient: ‘What would you do if I were unavailable?’ ‘What would make you confident enough to proceed?’ ‘What is the smallest reversible step?’
Then stop. Agree the action, the review point and what would cause the decision to be escalated. Coaching is not therapy, and it should not be used to delay a decision that the team needs today.
Building judgement without slowing delivery
Judgement grows through repetition with feedback, not through occasional heroic conversations. A few light structures can help.
Ask for recommendations rather than problems in one-to-ones. A simple format works well: situation, options, recommendation, risk. It takes five minutes to prepare and saves twenty minutes of discussion.
Add a proposal-first item to team meetings. The first five minutes should be for proposed decisions, not a tour of unresolved issues. This does not stop people raising concerns; it changes the starting point.
Review decisions after the event. A short conversation about what was expected, what happened and what should change next time is more valuable than a lengthy post-mortem. For recurring decisions, capture the principles in a one-page playbook so that the answer is available without the manager being present.
A short experiment for December
As teams enter December planning and appraisal season, choose one recurring request that currently lands on your desk. For two weeks, note whether you advised, coached or deferred. At the end, identify the questions you answered most often. Turn the top three into either a coaching conversation or a written principle.
The test is not whether you gave fewer answers. It is whether the team began to bring better questions and firmer recommendations. The quickest mind in the room is an asset. It becomes a liability only when it is the only mind expected to work.
