.png)
Decentralizing Decision Making on a Team: What Changes When Decisions Leave One Person's Head
- Lindsay Sheldrake
- Jul 10
- 6 min read
Welcome to Diary of a Leader: Real Stories, Leadership Lessons, and Personal Growth
There's a moment that happens, sometimes months into working with a leadership team, that I've come to recognize immediately.
Someone on the team makes a call that, a few months earlier, would have gone straight to the founder. Not a small decision. A real one. And they don't mention it as a big deal. They just mention it, in passing, the way you'd mention something completely ordinary.
The founder usually notices before I have to point it out.
Something has changed. Not just in how fast the decision got made, but in how the whole team is operating.
Welcome back to Diary of a Leader, where we explore what is really happening beneath leadership, growth, and the structures meant to support both.
This week is about what actually changes on a team once decisions stop living inside one person's head. And why decentralizing decision making on a team is less about trust and more about design.
Where Decisions Usually Live in a Growing Business
In most founder-led businesses, this is not a deliberate design. It's just how things end up.
The founder has the most context. They've been there the longest, seen the most situations, carry the clearest picture of what the business is trying to become. So naturally, decisions gravitate toward them.
At a small size, this works fine. The founder is close enough to everything that being the decision-maker doesn't create much friction.
As the business grows, the gravity stays the same even though the conditions that made it work have changed. Decisions still travel to the founder, but now there are more of them, coming from more people, about situations the founder has less direct context on than they used to.
The team isn't choosing to defer. They're following the path that's always existed. Nobody decided this is how it should work. It's just how it's always worked.
What Happens to a Team When This Doesn't Change
When decision-making stays centralized past the point where it should, a few predictable things start to happen.
Response time slows down, not because anyone is being slow, but because every meaningful decision now waits in a queue behind the founder's attention.
Team members start to anticipate what the founder would want, rather than developing their own judgment about what the situation actually requires. This looks like alignment. It's often something closer to guessing.
And quietly, capability stops developing. Not because people aren't capable, but because the system never asks them to exercise judgment. Decisions get made for them, by default, simply because the path of least resistance runs through the founder's inbox.
None of this is dramatic. It rarely feels like a crisis. It just feels like business as usual, which is exactly what makes it hard to notice from inside it.
What Actually Changes When Decisions Move
When decision rights genuinely shift, and this only works when it's intentional, not accidental, the change shows up in a few specific ways.
Response Time Changes First
This is usually the most visible shift. Decisions that used to wait days now happen in hours, sometimes minutes, because the person closest to the situation is also the person empowered to act on it.
This isn't just about speed for its own sake. It changes what the team is capable of responding to in real time, particularly with clients and situations that don't wait politely for a founder's calendar to open up.
Judgment Starts Developing for Real
When people are actually making decisions, not just executing ones handed to them, something different starts happening to their thinking.
They start considering tradeoffs. They start developing a feel for the business's priorities, not because they were told what those priorities are, but because they've had to apply them directly to real situations.
This is the part that surprises founders most. The judgment was often already there. It just never had anywhere to go.
The Founder's Role Genuinely Shifts
This is the change founders feel most personally.
When the team can make sound decisions without the founder's constant involvement, the founder's attention becomes available for something else. Not because they've stopped caring about the details, but because the details no longer require their direct hand on every one.
What replaces that involvement varies. For some founders, it's strategic work that's been waiting. For others, it's simply the ability to take a real week off without their phone becoming a second job.
Team Ownership Starts to Feel Different
There's a subtle shift in how people talk about their work once decisions genuinely belong to them.
Language changes from "I think we should" to "I decided." Accountability becomes easier to locate, because it's clear who actually made the call. And counterintuitively, people often become more careful with decisions once those decisions are truly theirs, not less.
Why Decentralizing Decision Making on a Team Doesn't Happen on Its Own
If the upside is this clear, why doesn't it happen naturally as businesses grow?
Because decision rights rarely get redesigned. They just accumulate, by default, around whoever has historically made the call. Without a deliberate shift, that pattern continues indefinitely, regardless of how much the business or the team around the founder has grown.
Moving decisions intentionally requires the founder to get specific about what actually needs their judgment and what doesn't. It requires the team to be told, clearly, what's now theirs to decide, not left to infer it from whether the founder happens to push back.
This is structural work, not a mindset shift. Hoping the team will "step up" rarely changes anything if the underlying decision rights were never actually redefined.
The Question Worth Asking
Most founders, sensing this problem, ask:
Why doesn't my team make more decisions on their own?
The more useful question is:
Which decisions have I never actually told my team belong to them?
Almost always, the answer reveals that the team isn't avoiding ownership. They were simply never formally given it.
Reflection Questions
Which decisions currently route through you that genuinely don't require your specific judgment?
What would need to be true for your team to make those decisions confidently without you?
Where have you assumed your team should "just know" what's theirs to decide?
What would change about your week if three of your most common decisions moved permanently off your plate?
Wrapping Up: Decisions Are a System, Not a Personality Trait
It's tempting to think of decision-making capacity as something people either have or don't.
In practice, it's much more often a question of whether the system around them ever asked them to use it.
Teams don't usually need more confidence to make decisions. They need decisions that have actually been handed to them, clearly enough that there's no ambiguity about whose call it is.
That shift, made deliberately, changes more than just speed. It changes what the whole team becomes capable of.
Frequently Asked Questions
How do you know if decision-making is too centralized in your business? Common signs include decisions routinely waiting on the founder regardless of how small they are, a team that frequently asks "what would you do" rather than proposing their own answer, and response times that consistently lag behind what the business actually needs. If most meaningful decisions still pass through one person, the system is centralized by default, even if no one designed it that way.
What's the difference between delegating tasks and delegating decisions? Delegating tasks means handing off execution while the underlying judgment still belongs to someone else. Delegating decisions means the authority to choose, not just to act, has genuinely moved. A team can be very busy executing tasks while still being entirely dependent on the founder for every meaningful decision.
How do you start decentralizing decisions without losing control of important outcomes? Start by clearly identifying which decisions genuinely require founder-level judgment and which don't. Communicate the boundary explicitly rather than leaving the team to infer it. Decisions can move incrementally, starting with lower-risk areas, while still maintaining visibility through regular check-ins rather than requiring approval on every call.
Continue Reading
If this resonated, these posts go deeper:
Stay tuned for more real-world reflections on leadership, operational clarity, and purposeful growth in the next installment of Diary of a Leader.
