In most mid-market companies, responsibility is abundant. Accountability is rare. Every process has an owner. Every project has a team. Every decision has multiple people involved. And when the process fails, the project delays, or the decision produces a bad outcome, the search for accountability reveals that responsibility was distributed so broadly that no single individual can be identified as the person who should have prevented the failure.
The procurement manager approved the vendor. The quality team inspected the delivery. The project manager scheduled the timeline. The finance team released the payment. The operations head oversaw the process. Five people were responsible. Nobody was accountable.
This is not a personality problem. It is an architectural problem. The organisation's decision-rights structure, escalation paths, approval hierarchies and reporting relationships are designed in a way that distributes responsibility without concentrating accountability. Everyone is involved. Nobody owns the outcome.
The Three Dimensions of Accountability Architecture
1. Decision rights
Who has the authority to make each significant decision? In many organisations, the answer is ambiguous. A pricing decision may require input from sales (market feedback), finance (margin analysis), product (positioning) and the founder (final approval). Four functions contribute. But which function owns the decision? If the pricing proves wrong, which function is accountable for the outcome?
In most companies, the answer is: the founder, who approved it. This is not accountability. It is escalation. The founder cannot be meaningfully accountable for every decision they approve, because they approve dozens of decisions daily on the basis of information others prepared. The accountability should rest with the function that prepared the recommendation and the analysis that supported it.
2. Ownership vs involvement
Every process involves multiple people. Ownership means one person is responsible for the outcome and has the authority to direct the process toward that outcome. Involvement means everyone else who contributes.
When ownership is undefined, involvement substitutes. Everyone is "involved" in the process. Nobody "owns" it. The process runs by consensus, coordination and informal negotiation rather than by authority and accountability.
The consequence: when the process succeeds, credit is shared. When it fails, blame is diffused. The organisation cannot learn from failure because it cannot identify where the failure originated.
3. Escalation vs delegation
In an accountability architecture, decisions are delegated downward with clear authority and ownership. The person making the decision is accountable for the outcome. Escalation occurs only when the decision exceeds the delegate's authority or when exceptional circumstances require senior judgment.
In a responsibility-without-accountability architecture, decisions are escalated upward by deault. The person closest to the information passes the decision to someone with more authority, who passes it to someone with more authority, until the decision reaches a level where the decision-maker has authority but not information. The decision is made on the basis of a summary rather than evidence. And when the outcome is poor, the person who made the decision (the senior executive) was working with incomplete information, while the person who had the information (the junior staff) did not have the authority.
Building the Accountability Architecture
In Northrop Management Private Limited's governance and organisational advisory work, accountability architecture is designed through a four-step process.
Step 1: Map every significant recurring decision. Pricing changes. Procurement approvals. Credit decisions. Hiring. Customer escalations. Capital expenditure. Product changes. Compliance responses.
Step 2: Assign a single owner for each decision. Not a committee. Not a shared responsibility. One person whose role includes the authority to make the decision and the accountability for the outcome. The owner may consult others. They may seek input. But the decision and the accountability rest with one individual.
Step 3: Define the decision rights. For each decision, specify: what the owner can decide independently (within defined parameters), what requires escalation (above defined thresholds or in exceptional circumstances), and what information the owner must have before deciding.
Step 4: Build the feedback loop. For each decision type, track outcomes. Did the pricing decision improve margins? Did the procurement decision deliver quality and value? Did the hiring decision produce a productive employee? The feedback loop connects accountability to evidence: the owner is accountable not just for making the decision but for the outcome it produced.
The Northrop Management Maturity Index (NMMI) captures accountability as one of its seven dimensions. A company that scores poorly on accountability, where decisions are made by committee, where ownership is unclear, where escalation substitutes for delegation, will also score poorly on decision velocity, operational quality and governance effectiveness, because each of these depends on clear accountability to function.
Ashish Chaudhary, frames the organisational design principle directly: "Accountability is not a personality trait. It is an architecture. An organisation that designs clear decision rights, assigns single owners and tracks outcomes will produce accountability naturally. An organisation that distributes responsibility without concentrating ownership will produce meetings, escalation and blame. The difference is not culture. It is design."
Questions for the Boardroom
- For each of our ten most frequent high-value decisions, can we name the single individual who is accountable for the outcome?
- How many of our decisions are made by committee, and is that structure producing better outcomes or slower outcomes?
- When a process fails, can we identify within 24 hours the person who was accountable for preventing the failure, or does the search for accountability reveal that responsibility was shared so broadly that nobody owns it?
- Are our escalation paths designed for exceptional circumstances, or have they become the default decision-making mechanism?
- Do we track decision outcomes by owner, so that the quality of each person's decision-making is visible over time?
Closing Implication
Accountability is the connective tissue between decisions and outcomes. Without it, an organisation can make decisions without learning from them, approve strategies without owning their execution, and distribute blame without concentrating improvement.
The fix is not exhortation. It is architecture: clear decision rights, single ownership, defined parameters, escalation only for exceptions, and a feedback loop that connects each decision to its outcome. An organisation that builds this architecture will produce accountability as a structural output. An organisation that does not will produce everything except accountability, regardless of how often leadership talks about it.
