Designing Speed Bumps To Protect Operations
Thoughtfully placing speed bumps within AI workflows re-engages human critical thinking. During a demo at Rising, Workday SVP & GM of Data Cloud Yasmeen Ahmad put this into practice. Building an autopilot agent to process signed offer letters for a new Malaysia office, she paused mid-build to add a step—a human review of any pay guarantees buried in the contract language. The agent went on to flag seven exceptions that a fully automated run would have missed.
That single, deliberate pause is exactly what researchers have been studying at scale. MIT Sloan teamed up with Accenture to test the idea inside real enterprise AI workflows and found that intentional check-ins can improve overall accuracy and reduce cognitive surrender.
Companies can apply similar tactics:
1. Problem formulation first: The agent drafts its plan, but won't run it. Before execution, employees write down what they expect to happen. No forecast of their own, no green light for the agent. An employee can't borrow a conclusion they haven't tried to reach themselves.
2. Hidden confidence scores: Grade it blind. The agent's certainty score—the number quietly nudging you to just approve it—stays locked until an employee makes their own call on the output. Only then does the agent show its hand, before the workflow moves to the next step.
3. Point-and-call verification: Literally, seriously, say it out loud before the agent executes. Japanese railway conductors point at the signal and call out its status before the train moves. Nuclear plant operators use the same trick before flipping a switch. Autonomous workflows need the same beat: a manual confirmation standing between a recommendation and an action.
4. Socratic AI coaching: The agent argues back instead of just acting. Before it moves from advising to doing, it raises counter-arguments and demands proof. In clinical decision support, diagnostic tools don't execute care—they force a mandatory deliberation between attending staff before orders can be signed. Slower, on purpose.
5. Quality-check honeypots: As agent oversight drops, QA tools must test the human in the loop. The system slips a deliberate error into the approval queue. Catching it proves the reviewer is paying attention. Missing it catches a rubber stamp in action.