What I noticed the day I stopped fixing things in front of my team

What if leadership isn’t about finding the right answer? What if it’s about making it easier for the team to get to the work that matters?
A few years ago, I was in a meeting where a project had gone sideways. The client kept changing the outcome mid-stream — “I had an amazing idea last night!” He did this more than once. Timeline blown, budget spent, the kind of problem that makes a room go quiet and look at whoever’s in charge.
I had an answer. I could feel it forming before the person who dealt with the client even finished explaining what happened. Old habit — twenty-some years of being the guy who fixes things fast enough that people mistake speed for wisdom.
I didn’t say it. I asked a question instead: “What do you think we’re actually up against here?”
Ten uncomfortable seconds passed. My answer was still sitting right there, fully formed, easier to say than to hold. Then someone two levels below me — someone I would have talked over if I’d gone first — gave the best diagnosis of the problem I’d heard all week.
I’ve been chasing that ten seconds ever since.
The Leadership Style Nobody Taught Me a Name For
If you’ve sat through a leadership program, nodded at the right slide, and gone back to your desk exactly the same person — you already know the problem isn’t that nobody’s explained this well enough.
Most of us learn one model of leadership by osmosis, whether anyone ever says it out loud: the leader is the person with the answer. Good leaders have better answers, faster. You get promoted because you were right more often than everyone around you, and then one day you’re in charge of a room full of people, and the instinct that got you there — jump in, solve it, be right — is suddenly the thing standing in everyone else’s way.
I learned that the expensive way once — I led with my answer in a room that had a better one waiting, watched the room quietly fall in line behind it, and we spent two months building the wrong thing before anyone found the idea I’d talked over.
I don’t think the fix is a personality transplant. Plenty of decisive, sharp people are terrific at this once they see what’s being asked of them. The shift is smaller and stranger than it sounds: your job stops being “have the answer” and starts being “make it easier for the team to get to the work that matters” — sometimes that’s finding the right idea. Sometimes it’s clearing whatever’s in the way. Sometimes it’s just getting people what they need to move. Not softer. Not slower, most days. Just aimed somewhere else. And it turns out the idea is the easy part — the part that’s hard is staying with it once the meeting’s over and the old habit is right there again, cheaper than ever.
I’ve started calling this facilitative leadership when I have to call it something, but a good host at a dinner party is closer to what I mean — someone paying close enough attention to the room that the right conversation happens without forcing it.

What It Actually Looks Like
A directive leader walks into a stuck meeting and tells the room what to do. A facilitative leader walks in, names what success was supposed to look like, and then asks, “What’s actually stuck?” — and waits for the answer instead of filling the silence themselves.
A directive leader has one person talking 80% of the time, usually the most senior one. A facilitative leader notices that pattern and asks the quietest person in the room what they see, before anyone senior weighs in and anchors the conversation.
A directive leader avoids the hard conversation because naming it feels risky. A facilitative leader names it plainly — “I think there’s something we’re not saying; what is it?” — because they’ve decided the risk of silence is worse than the risk of the question.
None of that requires new vocabulary. It requires noticing your own instinct to jump in, and choosing, on purpose, not to — often enough that it stops being a choice and starts being how you lead.
Doesn’t This Fall Apart the Moment Things Get Urgent?
Fair question, and I get it all the time. People picture a leader who freezes the room to ask thoughtful questions while the server’s down and customers are furious. So let me be plain about where people take this too far.
In a real emergency, the answer to “what can I make easier” changes. The question doesn’t. Sometimes the most useful thing you can do for a room is tell it exactly what to do, right now, no discussion. Nobody in a genuine crisis wants a huddle. They want clear instructions and someone calling the shots. That’s still facilitative leadership, because it’s still built on the same question — what does this room really need from me right now to move well? The honest answer, in that moment, is just “clarity and speed” instead of “space and inquiry.”

When what the room needs is access to a resource, or an obstacle cleared, becoming the person who makes the call might be the most useful thing you have to offer — the same principle, just pointed at a different kind of easier. You’re not doing the work for the team; you’re making their work easier.
What separates a facilitative leader from a directive one isn’t that the facilitative leader never gives an order in a crisis. It’s two things that happen around that order.
First — they treat it as the exception, not the mode. A directive leader defaults to “tell people what to do” whether the stakes are an outage or which font goes on the slide deck. A facilitative leader can move into clear, fast direction when the moment calls for it, and doesn’t stay there once it’s passed.
Second — they come back for the debrief. A facilitative leader gathers the room within a day or two and asks the questions there wasn’t time for in the moment — what did we miss, what should the manual have said, who saw this coming and didn’t say anything. The directiveness that got everyone through the emergency doesn’t quietly become the leader’s permanent operating mode. It gets handed back.
I think about it like a pilot and a co-pilot. In clear air, a good captain runs an open cockpit — asks for the co-pilot’s read, welcomes a dissenting instrument reading, treats silence from the other seat as a bad sign. In severe turbulence, that same captain gives short, clear commands, and the co-pilot follows without a mid-storm debate. Nobody calls that captain a poor team player for taking control during the turbulence. The whole reason the crew trusts those commands is that the rest of the time, the captain listens.
That’s the piece I’d want you to leave with: facilitative leadership was never about giving up authority. It’s about knowing when and how to exercise it. The discipline isn’t in taking control during the storm. It’s in setting it back down once the storm’s over.
How to Actually Build This, Not Just Believe In It
Here’s the part almost every leadership article skips: understanding this idea and doing it under real pressure are two different skills. I can get a room to nod along with everything above in about ten minutes. Doing it once, in a workshop, with nothing on the line, doesn’t mean you’ll do it again next Tuesday, when there’s a real deadline and the old habit is sitting right there, faster and more comfortable.

You don’t unlearn a twenty-year habit in an afternoon. You unlearn it in the small moments after the afternoon, when nobody’s watching, and the old habit is right there, cheaper and easier than the new one. So, if you want this to change how you lead, don’t look for a better explanation of the idea. Look for reps. A few that have worked for me and the leaders I’ve watched try this:
Pick one meeting a week, on purpose. Not every meeting — one. Go in planning to hold your answer for ten seconds before you say it. That’s the whole assignment. See what happens in the silence.
Track your ratio for a day. Ask versus tell. Most people are stunned by the number once they count it. You don’t need to fix it yet. Just see it.
Hand off one thing you’d normally do yourself. Pick the task you default to because it’s faster to do it yourself. Give it to someone else this week, knowing it’ll be done worse the first few times. That’s the point.
Get someone to call it out. Ask a peer or a direct report to tell you, honestly, the next time you talk over someone or answer before they finish. You will not notice it in the moment — I never do. I asked a trusted colleague to ask, “Do you need a cookie?” when I did. It worked, but people started bringing me cookies every meeting.
Debrief the wins, not just the failures. After any high-pressure moment — even one that went fine — gather the room and ask what you missed. Most leaders only do this after something breaks. Do it after the ordinary weeks too.
None of these take a program. They take noticing, and then doing it again next week when it would be easier not to.
What I’d Ask You to Notice This Week
Pick one meeting. The next time you feel the answer forming before someone’s finished their sentence, hold it for ten seconds and ask what they think instead. See what happens in those ten seconds. It’s almost never nothing.
That’s the whole idea, honestly. The insight was never the hard part. Staying with it is — long after the meeting’s over and the room is just a room again.

John Losey has spent thirty years building leadership programs around one idea: less friction, more work.
© 2026 The IntoWisdom Group. This article is part of an ongoing series on facilitation and leadership.
(AI was used in this article for research, grammar, and feedback. All content is the work of the author. The author significantly edited any AI contributions. All images by Gemini and ChatGPT.)
This article first appeared on Medium.

