Designing readable states in multi-step approvals

Approvals fail quietly when operators cannot answer three questions in under ten seconds: who is next, what is blocked, and which rule fired. We bias toward typographic hierarchy instead of icon stacks because language survives printing and screen recordings regulators request. In Daejeon workshops we watched managers rehearse incident stories. The teams that kept approval consoles longest wrote short rationales inline, not in separate tickets. That habit shaped how we structure evidence chips and immutable notes in the Ops Console pattern. We still avoid promising instant consensus. Dense interfaces need training budgets. The honest trade-off—more text upfront, fewer Monday surprises—is the one service orgs audit successfully.