The manager-as-coach approach asks managers to build their team's ability to find answers instead of supplying the answers themselves. It fails for two reasons. Managers drift back into directing without noticing. And when they do coach, they often coach the wrong problem, because nobody taught them to read what was actually happening first.
Coaching technique matters. Good questions matter. The GROW model, popularized by John Whitmore, has helped a generation of managers structure a coaching conversation. But technique is the second half of the skill.
Three modes, one default
Managers move between three modes with a team, often several times in one meeting:
- Directing. You have the answer or the authority, and you're transmitting it. Necessary when stakes are high and time is short. A problem when it becomes the default.
- Managing. Tracking progress, removing obstacles, keeping the work moving. Real work, focused on output.
- Coaching. Building the team's ability to find answers. Watching, diagnosing, intervening at the level of behavior instead of task.
Most managers believe they're coaching more than they are. Some are policing: watching closely and applying pressure, which produces compliance rather than capability. Some are babysitting: keeping everyone organized and out of trouble, which produces dependency.
Here's the test. If your team functions better when you're not in the room, you're coaching. If it functions better because you're always in the room, you're doing something else.
Coaching the wrong problem
Even real coaching fails when it's aimed at the wrong thing. I learned this coaching a leadership team at Nike that wouldn't move. I threw every intervention I had at them and coached harder. The resistance I was coaching against turned out to be scar tissue from leaders who had prescribed and left, plus a team with no shared picture of what it was building. My coaching was fine. It was aimed at nothing.
That's the gap in most manager-as-coach programs. They teach the coaching conversation. They don't teach the read that tells you what the conversation should be about.
What coaching actually depends on
The Read Lab is built on a decade of Coaching Metaskills delivery. It rests on four disciplines, practiced in order and then used together:
- Self-awareness. Knowing your own default and catching it before it fires. A manager carrying anxiety they haven't named will read caution as resistance.
- Observation. Seeing what's actually happening in the team, separate from the story you've attached to it.
- Diagnosis. Holding more than one explanation for what's driving it, and treating your first read as a hypothesis.
- Intervention. Choosing the smallest move that fits the moment, then watching what it does.
When it takes hold, you can hear it in how managers describe their own practice. At American Family Insurance, one leader we trained described how she reads a team that's stuck: "Why are they spinning? Do they seem distracted? Are they hungry? Is this person feeling well?" Another put the whole discipline in one line: "Listen and Observe to see where they are and what they need before jumping in."
That's coaching that starts in the right place.
If you're building a manager-as-coach program
- Teach the read before the coaching model. Managers need to know what they're coaching before they decide how.
- Name the modes. Managers who can name directing, managing and coaching can catch themselves switching.
- Practice on live teams with observation. Coaching is learned by doing it while someone watches and gives feedback.
- Measure independence. The goal is a team that needs the manager less, not more.
This sits at the center of Diagnostic Leadership: reading what's actually happening before deciding what to do. The Read Lab builds it in three days of observed practice.