How Do I Get My Team to Start Thinking With Me?

A Story About the Difference Between Being Followed and Being Trusted

How Do I Get My Team to Start Thinking With Me?
A Story About the Difference Between Being Followed and Being Trusted

How Do I Get My Team to Start Thinking With Me? Usually the moment you stop being the person who has it all handled, and let them see the reasoning — and the doubt, and the once-that-went-wrong — behind how you lead. A team that only ever sees you certain will only ever wait for your certainty. What draws their thinking out is seeing yours, unfinished, in the open.

Let me tell you a story about a man who ran a flawless operation, and watched a room full of experienced people wait to be told what to think.

Daksh is a character I created — his situation will be familiar to anyone whose team follows them faultlessly and never quite arrives alongside them.

Followed, and Only Followed

Daksh was fifty-one, and chief engineer at a regional water utility.

He had come up through the plants — twenty-five years of pumps and mains and treatment works before he ran the whole engineering function. He knew the network the way you know a house you grew up in. When something failed at three in the morning, the phone that rang was his, and the answer he gave was the one the situation needed. His people knew it. The board knew it. In a sector where a bad day means a town without clean water, Daksh was the person you wanted holding it.

And his team followed him completely. They executed his decisions with precision. When he set a direction, they moved. When he solved a problem, they implemented the solution exactly as specified. By every operational measure, his was the best-run function in the utility.

What they never did was think with him.

Problems came up the chain to Daksh and solutions came back down. His engineers — many of them experienced, some of them nearly as seasoned as he was — brought him faults to fix rather than fixes to consider. They waited for his read before offering their own, and mostly didn’t offer their own at all. In meetings he’d lay out the plan and watch capable people write it down. Nobody argued. Nobody built on it. Nobody said the thing that would have made it better, though he knew, from the quality of the people in the room, that they had those things in them.

He’d come to accept it as the shape of technical leadership. He was the most experienced engineer in the building. Of course they deferred to him. That was the job working as it should.

What he hadn’t understood was that their deference wasn’t the job working. It was the ceiling on it — and he had built the ceiling himself, by being, for years, a man who was only ever certain in front of them.

The Meeting He Changed

The change came with a reorganisation, and a briefing he abandoned halfway through.

The utility was restructuring its engineering operations — merging teams, changing reporting lines, moving people between functions that had run separately for years. Some of it was sensible and some of it, Daksh privately thought, was risky. He’d been asked to bring his people through it, and he’d prepared the way he always did: the rationale, the new structure, the timeline, the reassurances. A clean briefing, delivered with authority.

He stood up in front of forty engineers and technicians, many of whom were quietly frightened about what the change meant for them, and started delivering it. And a few minutes in, watching the room brace the way a team braces when it’s being managed rather than talked to, he stopped.

He put the briefing down. And instead, he told them about the worst night of his career.

Fifteen years earlier, newly promoted and eager to prove himself, he’d made a call on a treatment process that he’d been warned about and overruled, because he was sure he knew better. He hadn’t. A fault he should have caught took a works offline, and for the better part of a day a stretch of the network was on the edge of losing supply. It was recoverable, and it was recovered, but he’d stood in the control room that night certain he’d finished his career, and more than that, certain he’d let down every person who depended on the thing working. What had saved it wasn’t him. It was a technician half his age who’d seen the problem coming, said so, been overruled, and then quietly built the workaround anyway — so that when Daksh’s decision failed, the recovery was already half in place.

“I’ve never forgotten that she was right and I wasn’t,” he told the room. “And that the reason we recovered is that she didn’t wait for me to be right. So I’m going to be honest with you about this restructure. Parts of it I believe in. Parts of it I don’t, and I’ve said so upstairs. And I’d rather work through it with you seeing exactly what I think than have you write down a version where I pretend I’m certain. Because I’ve been certain and wrong in this job, and it cost us.”

The room was quiet in a way his briefings never were. Then one of the senior engineers — a man who’d sat through a decade of Daksh’s meetings and rarely spoken in any of them — asked a real question. Not about job security. About whether one of the proposed team mergers would actually work operationally, and why he thought it wouldn’t.

They were in that room for two hours. Daksh spent most of it listening. By the end, his engineers had reshaped two parts of the plan — parts they’d have to live with — and flagged a risk in a third that he’d genuinely missed. The restructure went better than the ones in the functions around them. And it went better because the people delivering it had helped design it.

Why Experienced Teams Wait

Here is the mechanism, and it catches the most capable technical leaders hardest.

Certainty in a leader teaches a team to wait for it. When you are reliably right — and Daksh had been reliably right for twenty-five years — the rational thing for everyone around you to do is defer. Why would an engineer offer a tentative view to the person who always has the confident, correct one? Deferring isn’t reluctance; it’s a sensible response to a leader who has never visibly needed anyone else’s thinking. Every time you’re certain in front of your team, you quietly confirm that certainty is your department, and theirs is to carry it out.

This is why being more expert never fixes it. A more authoritative leader is a more certain one, and a more certain one gets a team that waits harder. Daksh’s competence wasn’t drawing his people’s thinking out — it was the exact thing keeping it in.

What changes it is showing them the unfinished part of your own thinking: the call you’re still weighing, the doubt you haven’t resolved, and above all the time your certainty was wrong and someone else’s tentative view was right. That last one is the key that turns the lock, because it tells a room that their half-formed thought might be the thing that saves the day — which is the only reason worth having to speak up.

You don’t get an experienced team thinking with you by being more obviously the expert. Daksh was the expert for twenty-five years. You get it by letting them see that your expertise has needed theirs before, and will again.

What Daksh Recognised

That evening, Daksh thought about the two hours he’d mostly spent listening, and found three things he’d never named.

The first was a success, though it hadn’t felt like leadership while it was happening — he’d barely led it, in the usual sense. But when he looked at what had actually changed, he saw it plainly. The moment he stopped being certain in front of his engineers was the moment they stopped waiting for his certainty. He’d told them about the worst night of his career, and the room had answered with the exact kind of thinking he’d wanted from them for years and never received. Every flawless briefing he’d ever delivered had produced silence. One honest admission had produced a better plan.

The second was a failure, and it was the twenty years of flawless briefings themselves. Nothing had ever gone wrong in them — that was precisely what had hidden the failure from him. No bad meeting, no poor decision, no engineer who’d let him down. Just years of experienced people, full of judgement he could see and never hear, deferring to a man who’d never given them a reason not to. He’d built the best-run function in the utility and the quietest one, and he’d taken the quiet as a sign of how well it ran.

The third was the passion underneath both, and it surprised him, because it wasn’t the engineering. It was the technician who’d been right when he was wrong, fifteen years ago — and the fact that he’d spent the years since promoting people exactly like her, people who saw things and said them, and then leading in a way that trained them not to. What he actually cared about, when he let himself look, was the engineer with the quiet correct instinct that saves a bad night. He’d been keeping those people silent for two decades while telling himself he valued them.

Three things. None of them about his competence, which had never been in question. All of them about the difference between a team that carries out your decisions and a team that helps you make them.

The Leader He Became

Daksh didn’t change how he ran the network. He changed what he let his engineers see of his own thinking.

He started bringing them problems he hadn’t solved yet, rather than solutions to implement. He said, out loud, when he wasn’t sure — and named the calls he was still weighing rather than presenting only the finished decision. When a newer engineer offered a tentative view, he stopped closing it down with the right answer and started asking them to follow it through.

And it moved, slowly and then not slowly. The experienced engineer who’d asked the first real question began raising others, in meetings, without being invited to — and other engineers started arguing with him, and the arguments made the work better. Within the year, faults were being caught and fixed further down the chain, before they ever reached Daksh’s desk, by people who no longer waited for his read to trust their own. His engineers had started bringing their judgement to each other, running decisions between themselves, catching each other’s blind spots the way that technician had once caught his. The network didn’t depend on him being the one who saw it first any more.

That was the change that mattered, and it was the one he hadn’t expected. He’d assumed leading better would mean sharper problems reaching him faster. Instead, fewer problems reached him at all — because the people around him had stopped waiting to be right and started being right together, out loud, without him. His job had quietly become a different one: not the engineer with the answer, but the one who’d made it safe for forty other engineers to have theirs.

Nothing about his expertise had changed. He was exactly as good an engineer as he’d always been.

He’d simply stopped being the only certain person in the room, and started being someone his team could think alongside — and then think without.

What Makes a Team Start Thinking With You: What Daksh’s Story Shows

Certainty in a leader teaches a team to wait. When you’re reliably right, deferring to you is the sensible thing for everyone around you to do. Daksh’s people stayed quiet because he’d never shown them their thinking was needed — not because anything was wrong between them.

Being more expert won’t change it. A more authoritative leader is a more certain one, and gets a team that waits harder. Daksh was the expert for twenty-five years. Expertise was never the missing thing.

Show them the unfinished part. The call you’re still weighing, the doubt you haven’t resolved. That’s the opening an experienced person climbs through, because it tells them there’s room for a view that isn’t yet fully formed.

Tell them the time your certainty was wrong. Daksh’s room came alive when he admitted the night a technician was right and he wasn’t. Your own overruled-and-mistaken moment, told honestly, is what tells a team their tentative view might be the one that matters.

Respect is not the same as trust. A team that respects your expertise carries out your decisions. A team that trusts you helps you make them. The first is earned by being right. The second is earned by being honest about the times you weren’t.

Your three stories hold the whole of it. A success that shows what happens when you lead as a person rather than an authority, a failure that shows what your certainty has quietly been costing, and a passion that shows who you actually came into this work to serve.

You Already Lead Well. That Was Never the Question

Everything Daksh needed was already there. He hadn’t been failing his team — he’d been leading them faultlessly and certainly, and certainly is what kept them waiting. The success that showed him what one honest admission could open. The failure that looked exactly like the best-run function in the building. The engineer, fifteen years ago, who’d been right when he was wrong — and every engineer like her he’d promoted and then silenced since.

Yours are there in the same way — in every experienced person you lead who has judgement you can see and have never heard, because you were always certain first.

Continue the Work

And if you want to go deeper — recognising your three stories and the experience inside each; telling them so people see how you think and what you’re leading for, rather than only what you can decide; and turning the same questions outward, to draw out the thinking of the people you lead — that is what my new Professional Self-Coaching resource is for. The thinking, the sequence, the questions and the frameworks a coach would bring to hours of one-to-one work, placed in your hands, to work through in your own space and time.

Get the Trust — Professional Self-Coaching for Leadership People Believe In. Tell the Three Stories That Turn Respect Into Trust, and Compliance Into Ownership. Prepare the Failure, Success and Passion Stories That Let People See How You Think, What You’ve Learnt, and What You’re Leading For

Work With Me: Individual WorkLife Coaching, Commissioned Learning Resources, Speaking Engagements and Organisational Partnerships. 

Support This Work: Your support makes a difference and helps me to continue creating resources that are accessible to everyone. Thank you. Carmel

Listen to the audio version here:  

Share These Learning Resources 

These resources are designed as short, effective learning experiences—for individuals managing their own development and companies supporting their people’s growth.

If you think this learning resource story would be helpful to others, share it forward.


Discover more from School of WorkLife

Subscribe to get the latest posts sent to your email.

Published by Carmel O' Reilly

I'm Carmel O'Reilly, founder of School of WorkLife. I use story-based learning — characters in real WorkLife scenarios — to help people develop their working lives, through Story Lessons, Guided Programmes, and Professional Self-Coaching resources, and the WorkLife Stories podcast. Irish, London-based, and endlessly drawn to a good story.