How to challenge an approval without removing control.

The Problem

Approvals are the most common source of Flow Time delay. A piece of work sits on a manager's desk for three days waiting for a signature. When you suggest removing the approval, the immediate reaction is fear: "If I don't review it, mistakes will go to the client."

What to Look For

Most approvals are low-trust mechanisms masking a lack of clear rules. The manager is acting as a human rule-engine.

Key Principle

Removing an approval does not require removing control. It requires changing the mechanism of control from proactive gatekeeping to boundary conditions.

One Small Thing to Try

Instead of requiring approval on every item, establish Decision Boundaries.

1. Define the Safe Zone: "Any quote under $10,000 that maintains a 40% margin can be sent directly to the client without review."
2. Define the Exception: "Only quotes over $10,000, or with margins below 40%, require my approval."
3. Shift to Audit: Instead of reviewing before sending, the manager reviews a random 10% of sent quotes after the fact to ensure quality.

Questions to Ask

• In the last 100 times I approved this, how many times did I actually change it? (If the answer is less than 5%, the approval is performative).
• What is the actual risk if this goes out with an error? Can we survive it?
• Am I approving this to add value, or just to feel in control?

What to Measure

Measure the reduction in Flow Time for the items that now fall within the Safe Zone.

What Not to Damage

Do not remove approvals on irreversible, existential risks (e.g., signing a massive lease, changing core compliance). Remove approvals on high-frequency, reversible, low-risk actions.

What to Do Next

Identify the most frequent approval you perform each week. Write the rule that would allow your team to make that decision 80% of the time without you.