Somewhere in my first year as an engineering manager, someone on my team said something I never forgot. "You stopped telling me what to do and started asking me what I thought." I hadn't noticed the shift happening. I only noticed it once she named it.
I'd swapped one word in my own head, quietly, without a ceremony. Manager became coach. It changed almost everything about how I led.
The Word Does the Work
"Manager" implies control. You manage inventory. You manage a budget. You manage risk. The word carries an assumption baked in: something needs to be contained, directed, kept in line.
"Coach" implies something else entirely. A coach studies you, adjusts to you, pushes you toward a version of yourself you couldn't reach alone. Nobody has ever said "my coach controlled me into becoming a better athlete."
I didn't choose to write about this by accident. Garry Ridge, the former CEO of WD-40, built an entire leadership philosophy around this exact swap: from manager to coach, a job title change reshaping everything underneath it. I came across his framing while researching this post, and it crystallized something I'd been circling for years without the right language for it.
What the Research Says
I went looking for evidence this isn't only a nice metaphor, and Gallup has spent years measuring exactly this shift.
Their research studied 49,495 business units and 1.2 million employees and found only about two in ten managers instinctively coach rather than boss. The rest default to directing tasks instead of developing people, even when they'd describe themselves as supportive leaders.
The performance gap this creates is not small. Gallup found managers trained in coaching and people development see up to 18% higher engagement among their teams, a rise of 20% to 28% in other manager performance metrics, and 21% to 28% less turnover on their teams. Employees who get daily feedback from a manager are three times more likely to be engaged than those who hear from their manager once a year. Employees whose manager involves them in setting goals are nearly four times more likely to be engaged than employees left out of it.
None of these numbers measure a personality trait. They measure a behavior, and behavior follows the mental model you're operating from. Boss thinks control. Coach thinks development. Those two mental models produce different daily choices, and different daily choices compound into wildly different outcomes over a year.
What Changes When You Say "Coach" Instead
The words we use for a role tend to set the boundaries of what we think the role allows.
When I thought of myself as a manager, my job was to remove obstacles, assign work, and keep the team on schedule. Useful things, all of them, and not enough on their own. When I started thinking of myself as a coach, my job expanded to include the harder, slower work: figuring out what each person on my team wanted to get better at, and building their week around it instead of only around my deadlines.
Coaching changes how you run a one-on-one. A boss opens with status updates. A coach opens with "what's the hardest part of your week been." Coaching changes how you give feedback. A boss corrects the outcome. A coach asks what the person noticed about their own process, and lets them find the fix before offering one. Coaching changes how you handle a mistake. A boss assigns blame and moves on. A coach treats the mistake as the most useful data the team will get all quarter.
None of this is soft. Gallup's own numbers on stress show managers experience 27% higher stress than individual contributors, and coaching a struggling employee through a real problem takes more energy than issuing a directive. Coaching is the harder job wearing the softer name.
The Part I Got Wrong for Years
Early in my career I thought coaching meant being gentle. I confused the word with being nice, with avoiding hard conversations, with letting standards slide so nobody felt bad.
I had it backward. The best coach I ever had in the Army held a much higher bar than any boss I'd worked under, and he held it by asking harder questions, not by softening them. He never told me the answer when I was capable of finding it myself. This was uncomfortable in the moment and valuable for years afterward. Coaching isn't the absence of a standard. It's a different route to reaching one, built on questions instead of orders.
I carried this lesson into every leadership role since, through engineering teams and into HR work, and I still catch myself slipping back into "manager mode" when I'm tired or under pressure. The pull toward directing instead of developing never fully goes away. You get faster, over time, at noticing when you've slipped back into it.
It Spreads Past the One-on-One
Once I started noticing the manager-versus-coach split in myself, I started noticing it everywhere else in the organizations I worked in.
Job postings still describe "managing a team of five" as though headcount were the achievement. Performance review templates still ask "did this person meet their objectives" instead of "did this person grow." Promotion criteria still reward whoever kept the most projects on schedule, rather than whoever built the most capable people underneath them. The language of control runs through the whole system, not only through individual leaders trying their best inside it.
This matters because leaders don't operate in a vacuum. A manager trying to coach inside a system built to reward control gets pulled backward constantly. I've watched genuinely coaching-minded leaders revert to boss behavior the moment a deadline got tight, not because they forgot their principles, but because every incentive around them pointed toward control right then. Changing your own language is the starting point. Changing what your organization measures and rewards is the part sustaining it.
I saw this play out clearly during my own move from engineering leadership into HR-focused work. Engineering had spent years measuring velocity and deadlines. Fixing how leaders showed up for their people meant fixing what got measured first, not only what got said in a one-on-one.
Try the Swap for a Week
You don't need a title change to test this. You need a week of noticing your own language.
Count how many times you tell someone what to do versus how many times you ask them what they think should happen next. Notice whether your one-on-ones open with your priorities or theirs. Watch what happens to a mistake on your team: does it become a lesson the person owns, or a correction you hand down.
The word on your business card likely says "manager." Nobody is stopping you from acting like a coach anyway. My own team member noticed the shift in me before I'd noticed it in myself, and this is usually how you'll know it's working too. Not because you announced a new leadership philosophy, but because someone on your team quietly starts trusting you with harder problems than they used to bring you.
What would change on your team this week if you asked one more question before giving one more instruction?