The approval bottleneck
The bottleneck moved to the approver.
One team is all agents: a product manager, a developer and a tester. A person approves their ticket batches from a phone.
The agents produce work faster than one person can read it. So the slow step is no longer writing code. It is the person deciding what ships.
Something else went missing too. A human team argues: "this ticket is vague", "this touches billing", "why now?" Agents tend to agree with each other. That friction used to catch mistakes before the approver ever saw them.
The goal is not to remove the approver. It is to put the arguing back, so the approver only reads the few tickets that still need a person.
- Who waits
- The whole agent team
- What's missing
- Pushback before approval
- Target
- Only the top two or three tickets reach a person
- Design
- Pushback Reviewer