Put the approver in the first room

I have sat in the last meeting. The build is done. The demo works. Someone from risk is looking at a path they did not design and is being asked to bless a write they cannot undo. They say no. The room decides risk is the blocker.

They are not the blocker. They are late.

A write that can refund, send, post or publish needs four answers in writing before anyone builds: what may be drafted, what may be executed, what the approver sees, and how you undo it the same day. Those answers do not come from the engineers. They come from the person whose name is on the incident.

What changes when they are early

The path gets smaller. That is the point. A lot of “the model will handle it” dies in the first hour, which is cheaper than dying in the last one. The approver asks to see a diff, not a paragraph of confidence. Undo stops being a sequel and becomes a field on the same page as approve.

I run a room for this — risk, compliance, audit, finance — and I will not put them last. The thing they leave with is an approval design the accountable person would actually put their name to. If they will not sign it, we did not finish. We found out early.

The sentence I listen for

“We’ll bring risk in once it works.” That sentence means it will work in a demo and fail as a product. Bring them in while the work is still a blank gate. If you cannot fill the gate, you do not have a use case. You have a prototype looking for a signer.