55EXPERIENCE

Approval Experience & End-User UX

Human-in-the-loop works only when the human knows exactly what they are approving.

Priority: P0
Phase: MVP
Primary owner: Product Design / Workflow
Status: Blueprint

Objective

Approvers may not be security experts. The approval experience must translate technical agent behavior into business consequence while preventing accidental authorization of a different or broader action.

What to build

Clear identity: agent, owner, initiating person/system.
Plain-language action summary plus exact technical details on demand.
Business context: customer/vendor, amount, destination, record count or environment.
Risk explanation and matched policy.
Approve, reject, request changes, escalate or open investigation.

Implementation decisions

Bind approval to exact parameters or an approved bounded range.
Show whether action is reversible.
Use mobile-friendly responsive approval cards.
Require stronger authentication for critical approvals.

Definition of done

Approver can understand consequences without opening another system.
Changing protected parameters invalidates prior approval.
Decision and reason become part of permanent evidence.

Success metrics

Median approval time
Rejection rate
Parameter-change invalidations
Escalation rate

HUMAN CONTROL

Human-in-the-loop works only when the human knows exactly what they are approving.