Approval buttons look small. They are not. They encode authority, risk, and accountability in one click.
Bad approval flows ask a human to bless work they cannot inspect. “Approve deployment.” Which diff? Which environment? Which tests passed? Which customers are affected? If the approver has to open three tabs and ask two people, the product did not design approval. It outsourced anxiety.
Approval needs context
Every approval screen should answer:
- What changed?
- Why now?
- What evidence says this is safe?
- What happens if I say no?
The last question is the one most systems forget. A real approval flow has a useful rejection path. Otherwise approve becomes the only button that moves work forward, and the human becomes decorative.
This matters more with agents. An agent can prepare work faster than a human can review it. That makes the approval surface the bottleneck and the control plane.
Design the approval button like it matters. It does.