Field note 08 5 min read
The hidden cost of approval by inbox
Approval by message feels flexible until volume, urgency, and accountability begin competing for attention.
OperationsAn inbox is excellent for conversation. It is a weak system of record for decisions that need ownership, deadlines, evidence, and a dependable next step.
The queue is invisible.
Nobody can see the full set of pending decisions, their age, or their impact. Requesters chase individually and leaders learn about delays only when something becomes urgent.
Create a decision record.
A dependable approval begins with a structured request, a named decision owner, the evidence required, and a due date. Conversation may still happen in email or chat, but the decision belongs to the record.
- One request with complete context.
- One current owner.
- A visible deadline and escalation route.
- A permanent decision history.
Keep the fast path honest.
Automation can route common approvals immediately while making exceptions explicit. The goal is not to remove governance; it is to make governance easier to follow and easier to inspect.
A decision should not disappear because a message moved below the fold.
