Where Decisions Don’t Need to Be Made

Decision quality improves when decision volume drops

Decision Movement

In our previous article, we looked at stuck decisions—the ones that remain partially open, revisited without closure, accumulating in the system. If you recognized your organization there, you're likely asking: What does the alternative look like? How do organizations actually move decisions?

The answer isn't revolutionary. It's not about hiring better people or implementing more processes. Across Indian organizations of different sizes and sectors, there's a clear pattern in places where decisions move: decisions are made where the information is, boundaries are clear, and those boundaries are actually protected. Here's what that looks like in practice.

Decision Movement

In organizations where decisions move, there's a consistent pattern: the decision-maker is as close as possible to where the work happens. Not where the authority sits, but where the information is.

In these organizations, there's usually something clear and written. Not a thick policy document, but something accessible: 'Regional sales teams can adjust pricing within X percent without checking with corporate. Product teams own feature prioritization. Team leads can approve purchases under Y amount without escalation.' The specificity matters. Without it, people guess. And when they guess wrong, they stop trying.

What makes this different from theory is that these aren't suggestions—they're boundaries that are actually protected and respected. A sales manager in the field adjusts regional pricing, and no one second-guesses it. A product team decides on a feature timeline, and it doesn't get revisited because the founder has a different idea. A team lead approves a tool budget because they've been told: This is yours to own. That clarity changes behaviour.

Distinction

Organizations that move decisions well share another pattern: they've made conscious choices about what escalates and what doesn't. This distinction isn't arbitrary. It's based on impact and irreversibility.

What stays local: Operating decisions with reversible consequences. A team decides on their sprint schedule and standup format. A manager decides which projects get which resources. A customer-facing region decides how aggressively to pursue a new customer segment. These decisions should be made by the people closest to the work.

What goes up: Strategic decisions with company-wide implications and irreversible consequences. Entering a new market. Changing organizational structure. Major hiring freezes. Decisions about core values or mission. These are rare. When they're not, escalation becomes the default.

The problem in many organizations isn't the categories themselves. It's the absence of categories. Everything feels potentially critical. So everything escalates. A manager uncertain about whether to approve a team member's training program waits for the founder's input. A product team hesitates on a feature scope question. The conversation that should take 20 minutes takes 20 days.

Role of Leaders

In organizations where decisions flow, leaders do something counterintuitive: they make fewer decisions, but they make the critical ones more deliberately. The difference isn't about ignoring important choices. It's about being explicit about which ones matter and why.

This involves explicit conversations with direct reports. A manager sits down and discusses: 'Here's what you own completely—you decide, you own the outcome. Here's what requires my input because it affects the team or our strategy. Here's where we definitely need the founder's thinking, and here's why.' Not once a year in performance reviews. Regularly. With specificity.

This distinction matters because without it, everything becomes ambiguous. Is this a 'tell the founder' decision or a 'decide and inform' decision? Founders don't know what to expect. Teams don't know what will be questioned. So the safe move is to escalate. The result looks like founder bottlenecks—not because the founder is hoarding decisions, but because no one knows which ones need their input.

Clear boundaries usually solve 90% of this. 'This decision affects how we hire and retain people—founder input expected.' 'This one is about which features we build this quarter—team owns it, founder sees it.' People know the difference between 'escalate for thinking' and 'ask permission.' Founders aren't surprised. Teams aren't waiting.

The leader's job changes. Instead of being the person who makes all decisions, they become the person who protects the decision structure from erosion. When a decision goes wrong, they don't pull authority back. They coach the person to avoid the misstep next time. They reinforce: This is your territory to own. We trust it until trust is broken—not after.

In organizations where decisions move, HR Business Partner (HRBP) plays a specific role: as the thinking partner who helps leaders clarify boundaries. One of their roles should be to help identify which decisions genuinely need founder input and which ones have become escalated out of habit or otherwise – ‘is it because the founder genuinely needs to weigh in, or because no one's confident in the decision being made locally?' Such conversations facilitate clarity for managers and their teams about decision authority.

The difference is subtle but critical. In one case, HR manages the decision structure. In the other, HR helps the organization build one.

Chaos:

Organizations where decisions stall often share predictable patterns.

• Undefined boundaries. No one knows what they own, so everything gets discussed in meetings with increasing levels of seniority.

• Authority without accountability. People have decision rights, but no one tracks the outcome or learns from mistakes. So caution replaces confidence.

• Inconsistent application of boundaries. The founder overrides decisions sometimes, respects them other times. With no clear pattern, people stop trusting the boundaries.

Everything becomes uncertain, and when everything is uncertain, everything escalates.

Structure:

In organizations where decisions move, you see specific structures in place:

• A decision authority matrix. Not necessarily fancy. Often just a document that maps decision types to decision-makers. It's created with teams, not imposed from above.

•  Spending authority by role. A clear ceiling on budget decisions at each level. You don't ask permission for decisions under your level; you execute and report.

•  Escalation protocols defined in advance. If a decision lands on your desk that should have been made elsewhere, you send it back. 'This is your decision to make. Here's my thinking to inform you.'

• 'Role card' conversations. Each person knows, explicitly, what they decide, what they influence, what's decided for them, and what they're informed about. Not inferred. Spoken.

•  Outcome tracking tied to decisions. Not blame—learning. When a decision doesn't work out, the focus is: What did we learn? What would you do differently? Not: Why did you make this mistake?

This pattern exists already. Not everywhere, but in pockets - led by leaders / managers who understand that empowering decisions is faster than controlling them.

What distinguishes these pockets isn't access to better resources or smarter people. It's clarity. Decision architecture. Boundaries that feel safe enough to move within.

When decisions move, it's because someone has said: This is yours to decide. These are the boundaries. This is what success looks like. And then: It's protected until conditions change.

The question isn’t how to make people decide faster. It’s how to design systems where fewer decisions are needed—and the rest move to where they belong.