Published July 30, 2026 · Hoopi team
Nobody is worried about a bad draft
When teams hesitate to delegate, the fear is almost never a mediocre document. It is the email that went to the customer, the record that got overwritten, the payment that went out, the thing that cannot be pulled back.
Every one of those is an irreversible action. And irreversible actions are a small, enumerable set — sends, writes, deletes, payments, publishes. Gate that set, and the entire remaining surface becomes safe to hand over without thinking about it.
Cheap to reverse means cheap to try
Once the failure mode is 'a draft I did not like', the cost of delegating a new kind of task drops to almost nothing. People start handing over work speculatively, which is exactly the behaviour that finds the valuable use cases.
The organizations we see delegating the widest range of work are the ones whose admins spent an afternoon early on mapping approval rules to their existing delegation of authority. That afternoon buys a year of not having the conversation again.
Loosen deliberately, not by drift
Approval rules should get looser over time, but as a decision rather than by neglect. A useful pattern: after a standing job has run correctly for a month, review the log and drop the approval on the actions that were approved unmodified every single time.
That is a five-minute review that compounds, and it keeps the remaining gates meaningful. Gates that fire on everything get clicked through, which is worse than not having them.
Want to try this on your own worst task?