01 / The queue
Where is approval time actually being lost?
Measure the queue before redesigning it. For two weeks, record each approval request, its requester, the decision type, the amount or exposure, the time submitted, the time answered, and the consequence of delay. Group repeated requests. Ten small procurement approvals may be one missing spending rule. A single delayed contract may be an information problem because the reviewer was never given its term, obligations or alternatives.
Distinguish a permission request from an advice request. A team member may ask the founder to choose because the boundary is unclear, because the founder has previously reversed decisions, or because they want a second opinion. Only the first two require approval-system changes. An advice conversation can remain useful without transferring ownership back to the founder.
02 / Approval matrix
What should an approval matrix contain?
Build the matrix around categories and thresholds the team can apply. State the owner, the maximum exposure, the information needed, and the escalation route. A threshold can be monetary, but it can also concern customer harm, legal commitments, access to sensitive data or a promise that cannot easily be reversed. Keep the matrix short enough to use during real work. Attach a link to the relevant policy, not a folder of unread documents.
Avoid a rule saying every decision above a certain amount requires the founder personally. A named finance lead or board process may already be the right approver. Follow the company's legal documents and actual governance arrangements. The sample below is an operating design, not legal advice or a prescribed rupee threshold.
| Decision | Normal owner | Escalate when |
|---|---|---|
| Routine customer remedy | Customer lead | Outside agreed refund or reputation limits |
| Supplier choice within approved specification | Operations lead | Exclusivity, term or exposure exceeds the mandate |
| New debt, equity or material legal commitment | Named governance approver | Always, before commitment |
| Small reversible experiment | Project owner | It touches protected data or regulated claims |
03 / Decision packet
What information lets an approver answer once?
Require a brief decision packet for reserved matters: recommendation, alternatives, expected benefit, downside, cost or commitment, deadline, and what happens if the decision is deferred. The approver should be able to say yes, no, or 'return with this missing fact.' Without a standard packet, founders receive a stream of messages that must be reconstructed into a decision.
Set an expected response window for each category and a backup approver where governance permits one. If a customer promise expires in four hours, an approval route that meets once a week is not a route. Where no lawful substitute exists, change the promise or prepare the decision earlier. Silence must not be treated as approval for high-risk commitments.
- Recommendation and named decision owner
- Two credible alternatives, including doing nothing
- Cash, customer, legal and reputation exposure
- Evidence known and uncertainty remaining
- Deadline, default action and review date
04 / Feedback loop
How can approvals become lighter without losing control?
Review the queue monthly. Track median wait time, requests that exceeded the service window, decisions sent to the wrong approver, and cases that had to be reopened. Read a sample of decisions made below the approval threshold. If errors recur, improve the mandate or training rather than sending every routine choice upward again.
Tell the team when a rule changes and why. When a founder reverses a decision that was inside the owner's mandate, either identify a missed constraint or acknowledge that the mandate needs revision. Quiet reversals train people to seek permission even when the written policy says they can decide.