Decision Making Framework for Founders India: The Decision Rights Matrix

The most practical decision making framework for founders in India is not a prioritisation tool or a time management matrix. It is a system that answers one specific question — which decisions should the founder own, which should be delegated, and precisely where that line sits at each stage of a business's growth.

Most founders never build this system. Instead, they operate on instinct — involving themselves in the decisions that feel important, delegating the ones that feel safe, and gradually accumulating a growing queue of approvals, sign-offs, and consultations that slow the business down without the founder ever consciously choosing that outcome.

The result is what Adherio calls decision latency: the gap between when a decision needs to be made and when it actually gets made. In a manufacturer in South India that Adherio worked with — ₹20–50 crore revenue, decade-long operating history, capable leadership team — average decision latency had reached approximately ten days. Not because decisions were complex. Because the organisation had never defined who was authorised to make what, and so everything defaulted to the founder.

After twelve weeks of engagement, average decision latency had fallen to four days. The founder had not become less involved in important decisions. Rather, they had become appropriately involved — present where their judgment genuinely changed the outcome, absent where it did not.

This article presents the framework that made that shift possible.

---

Why Decision Rights Break Down as Businesses Scale

Understanding how to fix a decision rights problem requires first understanding why it develops in the way that it does.

In a business's early years, centralised founder decision-making is rational. The founder has the most complete picture of the business — its strategy, its clients, its capabilities, its constraints. Routing decisions through them is efficient because they can make fast, well-informed calls without lengthy context-setting. Furthermore, at small team sizes, the coordination cost of distributed decision-making often exceeds the benefit.

However, two things change as the business grows past ₹10–15 crore. First, the volume of decisions multiplies — more products, more clients, more functions, more geographies, more people generating more issues that require resolution. Second, the founder's ability to hold complete context across all functions simultaneously begins to degrade. As a result, the centralised model that once produced fast, well-informed decisions begins producing slow, partially-informed ones.

The problem is compounded by organisational behaviour. Teams that have been conditioned to route decisions upward continue to do so even when they are theoretically capable of deciding independently. Waiting for the founder becomes culturally embedded — not because team members are incapable, but because the system has never explicitly authorised them to act without approval. Consequently, even when the founder tries to delegate, the organisation does not absorb that delegation cleanly.

The fix requires more than a willingness to let go. It requires a structural change: a documented architecture that defines, with precision, who can make what class of decision, at what financial or strategic threshold, and under what conditions escalation is required.

The Decision Rights Matrix: How It Works

The Decision Rights Matrix is a framework that categorises every significant decision a business faces across two dimensions: the domain it belongs to, and the level at which it should be authorised.

The Four Decision Domains

Every operating decision in a founder-led business falls into one of four domains.

The Three Authorisation Levels

Within each domain, decisions are allocated across three authorisation levels.

Building the Matrix: A Practical Walkthrough

The Decision Rights Matrix is not a theoretical document. It is a working tool — built specifically for your business, at your current scale, reflecting your actual decision landscape. Here is how to construct it.

1 Step 1: Map Your Current Decision Inventory

Before allocating authority, you need to understand what decisions the business is actually making. Spend one week logging every decision that is escalated to the founder — including the ones that probably should not be. The output of this exercise is almost always clarifying. Founders consistently discover that a large proportion of their escalations involve decisions that a capable function head should be authorised to make independently.

In the manufacturing engagement mentioned above, this mapping exercise revealed that approximately 60% of decisions reaching the founder involved operational and lower-tier commercial calls — scheduling changes, vendor reorders, routine client approvals — that had been escalating upward purely because the system had never explicitly authorised anyone else to resolve them.

2 Step 2: Define Financial and Strategic Thresholds

For each domain, establish the thresholds that determine which authorisation level applies. Financial thresholds are the most straightforward to define.

For a business at ₹20–50 crore revenue, a workable starting structure might look like this: operational expenditure below ₹2 lakh sits at Level 1; between ₹2 lakh and ₹10 lakh at Level 2; above ₹10 lakh at Level 3. Commercial commitments below ₹5 lakh in annual contract value sit at Level 1; between ₹5 lakh and ₹25 lakh at Level 2; above ₹25 lakh at Level 3.

These thresholds are not universal. They should reflect your business's specific cost structure, risk tolerance, and the seniority and capability of your leadership team. The principle, however, is consistent: the threshold should be set at the point where the financial or strategic consequence of a wrong decision justifies the cost of involving a more senior decision-maker.

3 Step 3: Assign Explicit Ownership

For each decision class and authorisation level, name the role — not the person, but the role — that holds authority. This is important because named-person authority is fragile. If authority sits with a specific individual rather than a defined role, it evaporates when that individual leaves, is promoted, or is on leave.

Role-based authority, by contrast, is durable. It attaches to the position, transfers with it, and creates a structural norm that outlasts any particular person holding the role.

4 Step 4: Define Escalation Logic

Escalation is not a failure of the decision rights system — it is a feature of it. Some decisions genuinely require elevation because they are ambiguous, cross-functional, or consequential beyond what the current authority level should absorb alone.

However, escalation must have defined logic. Specifically, every person in the business should know: under what conditions do I escalate, to whom, within what timeframe, and with what information prepared in advance. Without this logic, escalation becomes the path of least resistance — used not because a decision genuinely requires senior involvement, but because it is easier than deciding.

In the D2C brand that Adherio worked with — scaling from ₹40 crore toward ₹100 crore — a significant proportion of cross-functional escalations were occurring not because decisions were genuinely ambiguous, but because role boundaries were unclear and team members were uncertain who had authority over decisions that sat at the intersection of two functions. Clarifying role charters and escalation pathways eliminated the majority of these escalations within weeks.

What the Matrix Looks Like at Different Scales

One of the most common mistakes founders make when building a decision rights architecture is treating it as a static document. In reality, the matrix should evolve as the business scales — because the appropriate distribution of authority at ₹10 crore is different from what is appropriate at ₹50 crore.

• At ₹5–15 crore, the matrix is relatively flat. The founder appropriately holds authority across a wide range of commercial and strategic decisions. Level 1 authority is primarily operational. The primary value of the matrix at this stage is making implicit decision-making explicit — so that the few things the founder has delegated are genuinely embedded rather than perpetually re-centralised.
• At ₹15–40 crore, the matrix needs to expand significantly at Level 2. A growing leadership team should be absorbing the majority of commercial decisions below defined thresholds and all operational decisions above routine. The founder's Level 3 authority should be narrowing deliberately — focused on strategic direction, significant capital commitments, and senior hiring.
• At ₹40 crore+, the matrix should be operating as a genuine governance architecture. Level 1 and Level 2 decisions should be flowing through structured forums — weekly operating reviews, monthly commercial reviews — rather than individual approvals. The founder's involvement should be almost entirely at the strategic level, with operational and commercial governance running through the leadership team.

The Outcome Metric: Decision Latency

The single most useful measure of whether a decision rights architecture is functioning is decision latency — the time between when a decision needs to be made and when it is actually made and communicated.

High decision latency is not primarily a symptom of slow people or poor judgment. It is a symptom of unclear authority. When people do not know whether they are authorised to decide, they wait. When escalation pathways are ambiguous, decisions queue. When the founder is the default authority for everything above routine, their attention becomes the binding constraint on the business's operating speed.

In the manufacturing engagement above, the fall in average decision latency from ten days to four days — achieved without any change in personnel or reporting structure — was entirely a function of clarifying who could decide what. The decisions did not become simpler. The people making them did not become more capable. The system around those decisions became clear for the first time, and the business moved accordingly.

For a ₹20–50 crore business, six days of recovered decision latency across hundreds of annual decisions represents a material improvement in operating velocity. More importantly, it represents the beginning of a business that can move at institutional speed rather than founder speed — which is the prerequisite for everything that follows.

A Final Note on Founder Psychology

No article on decision rights would be honest without acknowledging the psychological dimension of this work.

Founders who have built significant businesses through their own judgment develop, understandably, a strong prior that their involvement in decisions produces better outcomes than their absence. In many cases, that prior is accurate. Founder judgment is often genuinely superior — built from years of pattern recognition, market intuition, and hard-won operational knowledge.

However, the relevant question is not whether the founder makes better decisions than their team. It is whether the cost of routing all significant decisions through the founder — in time, in speed, in opportunity cost, in team capability development — is worth the quality premium that centralisation provides.

At a certain scale, it almost never is. Not because founders stop being valuable, but because the value of founder judgment is best deployed at the strategic level — where it is truly irreplaceable — rather than distributed across hundreds of operational and commercial calls where a well-designed system can produce equivalent outcomes at a fraction of the cost.

Building a decision rights architecture is not an act of stepping back from the business. It is an act of directing your attention toward the decisions where it matters most. That is not delegation as abdication. That is delegation as strategy.