Designing approvals people actually follow
Visible steps, clear ownership, and no dead ends. Five patterns for approval flows that stick.
Arjun Mehta
An approval process only works if people use it. The fastest way to get bypassed is to make the official path slower than a quick message to a manager.
Five patterns that hold up
1. Make every step visible. People follow a process they can see. If a request shows exactly where it is and who has it, no one needs to ask for a status update.
2. Assign ownership, not a queue. "Pending approval" with no name attached is where requests die. Every open step should belong to a specific person.
3. Remove dead ends. A rejected request should always come with a clear next action — revise, escalate, or withdraw. Never just no.
4. Match the path to the risk. A small request shouldn't take the same five approvals as a large one. Route by amount, type, or site so routine work moves fast.
5. Keep an audit trail by default. When the record of who approved what is automatic, you don't have to reconstruct it later.
The test
A good approval flow passes one test: is the official path the easiest path? If it is, people follow it without being told. If it isn't, they'll route around it — and your audit trail goes with them.