Most managers believe their job is to have answers. Myles Downey believes their job is to ask better questions. The Enabling Manager makes the case that the highest-leverage thing a manager can do - for performance, for development, for retention - is to stop solving problems for people and start helping people solve their own.
This is not a book about being passive. Enabling is not abdicating. It is a discipline that requires more skill, more patience, and more self-awareness than directive management ever does. Downey's central argument is simple and discomfiting: most managers default to telling because it is faster, more comfortable, and feels more like leadership. It is rarely more effective.
Coaching as a leadership style has been discussed for decades, but it remains largely theoretical in most engineering and delivery organisations. Managers get promoted for technical competence and then discovered, often slowly and painfully, to be directive in every conversation. They solve problems, provide answers, assign work, and then wonder why their teams lack initiative.
Downey cuts through the noise. He is not asking managers to become full-time coaches. He is asking them to notice which conversations call for direction and which call for enabling - and to recognise that the ratio is usually inverted from what they assume. Most situations that feel like they need an answer actually need a question.
For engineering leaders, this has direct implications for delivery. Teams that have been enabled to think, decide, and adapt are faster, more resilient, and more engaged than teams waiting for instructions. The Enabling Manager is a practical guide to building that kind of team, one conversation at a time.
Downey introduces a simple model: a spectrum running from directive (you tell) through coaching (you ask) to non-directive (you listen). Most managers live at the directive end. The skill is not to permanently relocate to the non-directive end, but to consciously choose where on the spectrum to operate based on what the situation and the person actually need.
A junior engineer in a production incident needs direction. A senior engineer working through a strategic design problem needs questions. Most managers give both of them the same thing: the answer.
Before your next one-to-one, decide in advance: is this conversation primarily for your benefit (you need information, you need to direct) or for theirs (they need to think, grow, decide)? Let that intention shape how you open and run it.
Downey draws on Timothy Gallwey's "inner game" insight: performance is not just a function of skill and effort - it is also a function of what gets in the way. Anxiety, self-doubt, unhelpful beliefs, unclear purpose, lack of feedback - these are all forms of interference that reduce what people are capable of delivering.
The manager's leverage is not only in developing potential (through training, stretch assignments, feedback) but in reducing interference. The enabling manager asks: what is getting in the way of this person performing at their best? And then removes it.
In your next performance conversation, spend at least half the time exploring barriers rather than evaluating output. Ask "What's making this harder than it needs to be?" and listen without immediately offering solutions.
Downey is emphatic on one point: the quality of your attention shapes everything else. A manager who is distracted, mentally composing their response while someone is still talking, or checking messages during a conversation is not coaching. They are performing the theatre of coaching.
Real attention - genuine curiosity about what this person is thinking and experiencing - is transformative. It tells people they are valued, it surfaces information that would otherwise stay hidden, and it creates the psychological safety that makes honest conversation possible.
Run your next one-to-one with no laptop, no phone face-up, and no agenda you prepared in advance. Ask one open question and let the conversation go where the person needs it to go. Notice how different it feels - for them and for you.
The GROW model (Goal, Reality, Options, Will) is well known, but Downey uses it with precision. What most people miss is that GROW is not a script to run through - it is a framework for structuring enabling attention. The goal clarifies what we are actually trying to achieve in this conversation. Reality surfaces where we genuinely are. Options expand thinking. Will converts thinking into commitment.
Used mechanically, it produces stilted conversations. Used as a mental map - to notice where a conversation has stalled and why - it is extraordinarily useful.
The next time a direct report brings you a problem, instead of offering a solution, run a lightweight GROW: "What would a good outcome look like?" then "Where are you with it now?" then "What have you considered?" You will be surprised how often they arrive at a better answer than you would have given them.
Downey is careful to distinguish enabling management from coaching. Managers have accountability for outcomes. They have opinions. They have context that their reports sometimes lack. There are moments where direction is exactly right - where clarity and guidance are genuinely what the situation needs.
The discipline is not to abandon direction. It is to earn the right to direct by first enabling - so that when you do give a steer, it lands with authority rather than dependency.
Audit the last five significant conversations you had with direct reports. How many of them were you doing most of the talking? Where was the balance? Which of those conversations left the person more capable of handling the next similar situation? Let that inform how you run the next five.
The managers people remember and credit for their growth almost never gave them the answers. They asked the questions that made them find it themselves.
Directive management creates capable executors. Enabling management creates capable thinkers. Which one does your organisation actually need more of?
The most common failure mode in one-to-ones is the manager solving problems that the engineer was about to solve themselves - and calling it support.
If your team only performs when you are present, directing, and available, you haven't built a team. You've built a dependency.
Psychological safety is not created by saying "my door is always open." It is created by the quality of attention and response you give the moment someone walks through it.
Rewrite your one-to-one agenda as questions, not topics. Instead of "project update" write "What's the most important thing you want to make progress on this week?" The shift in framing changes who owns the conversation.
Practise non-directive listening in one conversation this week. No advice, no solutions, no stories about your own experience. Just questions and genuine attention. See what emerges.
Map your team against the interference model. For each person, ask: what are the top one or two things getting in the way of them performing at their best? How many of those things are within your power to address?
Run a GROW conversation on a real problem this week. Use it lightly - not as a checklist, but as a navigational map. Notice where the conversation gets stuck and what kind of question unlocks it.
Ask your team for feedback on your management style. Not a survey - a direct question in a one-to-one: "What's one thing I do that helps you most? What's one thing I do that gets in the way?" Then listen without defending.
"The manager's job is not to make people dependent on them. It is to make people capable of not needing them."
- Myles Downey