If Every Decision Leads Back to You, That’s Not Leadership. That’s Dependency
Megan first noticed the pattern on a Tuesday morning, although if she was honest, it had been happening for months.
She was walking into her third meeting of the day when Jordan, one of her directors, caught her outside the conference room.
“Do you have thirty seconds?” he asked.
Megan glanced at her watch. She did not have thirty seconds.
But she liked Jordan. He was capable, thoughtful, and usually brief.
“What’s up?”
“We’re trying to decide whether to delay the client rollout by two weeks. There’s a quality issue in one part of the process, but the team thinks we can manage it with extra support.”
Megan asked two questions, heard the shape of the issue, and made the call.
“Delay it,” she said. “If the support plan depends on heroics, it’s not a plan. Tell the client today, own the delay, and give them the revised path.”
Jordan nodded, relieved.
“Got it. That helps.”
And it had helped.
That was the problem.
Megan walked into her meeting feeling useful, decisive, and faintly uneasy.
By noon, two more people had asked for her judgment.
One wanted to know whether to push back on a finance request.
Another wanted her read on a staffing tradeoff.
By 4:00, her chief of staff had dropped a note into chat:
“You’ve been pulled into eight decisions today that were not technically yours.”
Megan stared at the message.
Eight.
She leaned back in her chair and let herself feel the weight of it.
Her team was not incompetent. That would have been easier to name.
They were smart. Experienced. Hardworking.
And still, too many roads led back to her.
The next morning, Megan brought it up with Claire, an executive coach she met with twice a month.
“I think my team has gotten too dependent on me,” Megan said.
Claire did not look surprised.
“What makes you say that?”
“They keep coming to me for decisions they should be able to make.”
“Are they avoiding ownership?”
Megan paused.
That answer would have been convenient.
“I don’t think so,” she said. “Most of them care a lot. They don’t want to make the wrong call.”
Claire nodded.
“So they come to you.”
“Yes.”
“And you answer.”
Megan smiled, but not happily.
“Yes.”
“Quickly?”
“Usually.”
“Clearly?”
“Usually.”
“Accurately?”
Megan sighed. “Often.”
Claire let that sit for a moment.
“Then from their perspective, the system is working.”
Megan looked up.
“That’s the part I don’t like.”
“It may be working for the decision,” Claire said. “But it’s not working for their judgment.”
Megan knew what she meant immediately.
Every time someone brought her a messy question, Megan cleaned it up. She saw the risk, named the priority, made the tradeoff, and sent them back with clarity.
The work moved.
The team felt supported.
The decision was usually better.
But something else was happening underneath.
Her leaders were learning that the safest way to make a hard call was to bring it to Megan first.
Not because they were weak.
Because Megan had trained them well.
Claire asked, “What do you think they’ve learned from you?”
Megan crossed her arms.
“That I’m available?”
“Yes.”
“That I care about quality?”
“Yes.”
“That I have high standards?”
“Maybe,” Claire said. “Or maybe they’ve learned that your standards live in your head.”
That landed.
Megan thought about Jordan from the day before. He had not asked, “Here’s the standard we’re using. Does this decision meet it?”
He had asked, in effect, “What do you think?”
And she had told him.
Claire continued.
“There’s a version of this that becomes learned dependence. People stop trusting their own decision process because the real approval mechanism is you.”
Megan winced slightly.
“Learned dependence.”
“I’m not saying you created helplessness on purpose,” Claire said. “This is common with strong leaders. Especially the ones who are fast, caring, and right a lot.”
“That sounds suspiciously like a compliment before a correction.”
“It is.”
Megan laughed.
Then she got quiet.
Because she could see it now.
She had thought she was building a high-performing team by being responsive.
But in some cases, she had been building a team that waited.
Waited for her read.
Waited for her approval.
Waited for her to turn ambiguity into certainty.
And the more she did it, the more natural it became for everyone.
That afternoon, Megan tried something different.
Jordan came to her again, this time with a vendor issue.
“The team’s split,” he said. “One group wants to keep pushing the vendor because switching would slow us down. Another thinks we’re absorbing too much risk.”
Megan felt the answer rise immediately.
It was almost physical.
She could see the path. She could make the call. She could save them twenty minutes.
Instead, she asked, “What standard are you using to decide?”
Jordan blinked.
“What do you mean?”
“I mean, what matters most in this decision?”
“Speed and risk.”
“That’s two things. Which one wins if they conflict?”
Jordan hesitated.
Megan waited.
A month earlier, she would have filled the silence.
Finally, Jordan said, “Risk, I think. The timeline matters, but if the vendor misses again, the downstream impact is bigger than the delay from switching.”
“Good,” Megan said. “What threshold would tell you the risk is no longer acceptable?”
Jordan looked down at his notes.
“If they can’t give us a confirmed recovery plan by Friday, with named owners and dates, we move.”
“And what would make you escalate it to me?”
“If the switch affects the enterprise client timeline or creates a budget issue above our approved range.”
Megan nodded.
“Then you don’t need my answer. You have the decision filter.”
Jordan smiled a little.
“That was annoying.”
“I know.”
“But useful.”
“Also yes.”
For the next few weeks, Megan kept practicing.
When someone asked, “What should we do?” she asked, “What are you optimizing for?”
When someone asked, “Do you agree?” she asked, “What would make this a good decision?”
When someone said, “I wanted to get your take,” she asked, “What’s your recommendation, and what principle is behind it?”
At first, the team found it uncomfortable.
So did Megan.
The old way was faster.
The old way made her feel valuable.
The old way gave everyone a clean little hit of certainty.
But the old way also kept too much judgment centralized in one person.
So Megan began naming the standards more explicitly.
In a leadership meeting, she drew four columns on a whiteboard.
Principles.
Priorities.
Thresholds.
Examples.
“These are the things I’ve been carrying around in my head,” she told the group. “That’s on me. If you have to keep asking me what good looks like, I haven’t made the standard clear enough.”
The room got quiet.
She started with principles.
“We protect client trust over internal convenience.”
“We do not solve recurring problems with recurring heroics.”
“We make the owner of the work visible, especially when decisions are cross-functional.”
Then priorities.
“This quarter, reliability beats speed when the two are in conflict.”
“Director time should go toward system issues, not repeated exception management.”
“Escalation should happen when the decision changes risk, budget, timing, or strategic commitments.”
Then thresholds.
“If the impact is contained within your function and under the approved budget, make the call.”
“If it affects another leader’s commitments, align with them before deciding.”
“If it changes the client promise, bring the recommendation forward, not just the problem.”
Then examples.
She walked through three recent decisions, including Jordan’s client rollout.
Not to critique them.
To show the thinking.
“In this case, the issue was not simply whether the team could work harder,” she said. “The real question was whether the plan depended on extraordinary effort to meet a normal commitment. That violates our standard. If the plan only works when people overextend, the plan is not strong enough.”
Jordan nodded slowly.
“I wish I’d had that sentence two weeks ago.”
Megan smiled.
“Exactly.”
Something shifted after that meeting.
Not dramatically.
Not overnight.
But noticeably.
People still came to Megan, but the quality of the conversations changed.
They stopped bringing raw uncertainty and started bringing framed judgment.
Instead of, “What should we do?” she heard:
“Here’s the tradeoff we’re making.”
“Here’s the threshold we think applies.”
“Here’s where we think this needs escalation.”
“Here’s the principle we used, but we want to pressure-test the risk.”
The decisions were not always perfect.
But they were stronger.
More importantly, they were less dependent.
One Friday afternoon, Megan watched Jordan lead a tense discussion between Operations and Sales. The old Jordan would have looked toward her when the conversation got complicated.
This time, he didn’t.
He said, “Let’s come back to the standard. We said reliability beats speed when client trust is at stake. So the question is not, ‘Can we force this through?’ The question is, ‘Can we deliver it without creating risk we’ll have to explain later?’”
Megan sat quietly.
No one looked at her.
No one needed to.
For a moment, she felt the strange discomfort of becoming less central.
Then she felt something better.
Leverage.
After the meeting, Claire asked her how things were changing.
Megan thought for a while before answering.
“I used to think my value was in having the answer,” she said. “Now I think my value is in making the answer less dependent on me.”
Claire nodded.
“That’s senior leadership.”
Megan looked out the window.
“It’s harder than answering.”
“Yes.”
“And slower at first.”
“Yes.”
“But it’s cleaner.”
“How so?”
Megan smiled.
“Because now I can tell the difference between a team that needs my judgment and a team that needs access to the standards behind my judgment.”
That became the line she repeated to herself.
When she felt the urge to rescue a decision.
When someone brought her a problem they were capable of thinking through.
When speed tempted her back into old habits.
A senior leader’s job is not to be the answer key.
It is to raise the quality of thinking around them.
That does not mean withholding help.
It means giving the kind of help that builds capacity.
Sometimes that is an answer.
But more often, it is a principle.
A priority.
A threshold.
An example.
A better question.
A clearer bar.
Because the more senior the role, the less scalable it is to have every important decision pass through one capable person’s mind.
The real work is to make judgment transferable.
To turn instinct into standards.
To turn standards into shared decision quality.
And to build a team that does not just know what the leader would decide.
They understand how strong decisions are made.
**********
If this article describes what you’re navigating in your work or leadership, you can schedule a conversation with me. We’ll look at what’s happening, what may be keeping it in place, and whether coaching would be the right support.
