The Manager Who Stopped Having All the Answers
Marcus had a reputation, and he'd earned it: whatever the problem, he had an answer, usually within thirty seconds of hearing it described. His team liked this about him, mostly. It was also, without anyone quite naming it, the reason so few of them tried to solve anything themselves anymore.
The Manager Everyone Went To
It's a specific kind of competence that becomes its own trap. Marcus was fast, sharp, almost always right. Bringing him a problem got it solved efficiently — faster, usually, than working through it as a team. So people brought him everything. A vendor issue. A disagreement between two teammates. A question that, six months earlier, someone would have figured out on their own.
He didn't create this pattern on purpose. He just never noticed it forming.
What Always Having the Answer Actually Costs
The cost doesn't show up in any single decision. It shows up over time, in a team that has quietly stopped exercising a muscle they used to use. Ask someone on Marcus's team to make a judgment call without checking with him first, and the hesitation was visible — not because they weren't capable, but because they'd learned, gradually, that their job was to escalate, not decide.
The Meeting Where Something Different Happened
A scheduling conflict landed in his inbox — the kind of thing he'd normally resolve in a sentence. He opened his mouth to answer, and then, for reasons he couldn't fully explain afterward, didn't.
"What would you do?" he asked the person who'd brought it to him instead.
The pause that followed was longer and more uncomfortable than he expected. But an answer came — a reasonable one, maybe not exactly what he would have said, but workable. He said so. And then he stopped himself from adding the improvement he could already see.
What the Team Did With the Space
It didn't transform overnight. The first few times, people still glanced at Marcus mid-sentence, waiting for him to jump in. He mostly didn't. Within a few weeks, fewer questions were arriving at his desk pre-packaged as problems only he could solve. More of them were arriving already half-solved, framed as "here's what I'm thinking — does this seem right?"
He hadn't gotten worse at his job. He'd just stopped doing parts of everyone else's.
In the final article of this series: a team, six weeks later, describing in their own words what actually changed.