A colleague notices that the delivery date in a proposal does not match the planning sheet. The proposal is ready to send. Sales is waiting. The founder is unavailable. Does the colleague pause it, send a warning or assume somebody else has checked?
Growing organisations need an answer before that moment arrives. Responsibility for spotting a problem means little if the person who spots it cannot prevent the next action.
A useful example from manufacturing
Toyota describes this explicitly in its Toyota Production System. Under jidoka, equipment can stop when it detects an abnormality, and an operator can stop the line by pulling a stop cord. The problem becomes visible so someone can respond.
That is a concrete arrangement between detection and action. The person closest to the work has a way to interrupt it. Applying that principle to office work requires some design: what counts as a reason to pause, what gets paused and who takes responsibility next?
Make the pause specific
In the proposal example, the team could agree that an unconfirmed delivery date holds the proposal before sending. Drafting can continue. Other proposals can move. The delivery owner checks capacity and confirms or changes the date.
This is an illustrative application, not a Toyota case. Its value is the boundary: a specific uncertainty stops a specific commitment. Nobody needs to freeze the whole business or obtain the founder’s permission to raise the issue.
Write the condition in language people can recognise. “Escalate significant concerns” leaves each colleague to interpret significance under pressure. “Hold any proposal whose delivery date has no capacity confirmation” gives them something they can check.
Then name the person who resolves it, a backup and the expected response time. If nobody responds, the commitment stays on hold and the backup receives the case. Silence should have an agreed meaning.
Decide who can restart
Permission to pause and permission to restart can sit with different people. A salesperson may spot the mismatch. The delivery owner has the information and authority to confirm capacity. A commercial owner may need to approve changed terms.
Keep a short record of the source, the affected proposal version, the reason for holding it and the final decision. Record who authorised release. If the proposal changes afterwards, check whether the confirmation still covers it.
The same questions apply when AI prepares the proposal. A tool might flag a missing confirmation or prevent sending when a required field is empty. An authorised person still needs to resolve an uncertain delivery promise. Decide what happens if the check is unavailable before relying on it.
Learn from the interruptions
A pause creates useful information. Repeated holds for missing capacity data suggest a problem earlier in the workflow. Repeated unnecessary holds suggest that the condition needs refining. Review both, including how long resolution takes and whether errors still reach customers.
In a Blueprint, I would make these permissions and handoffs explicit. During Build, I would test them with ordinary cases and exceptions. Stewardship keeps checking whether the arrangement still fits as the team and its tools change.
Source checked 26 October 2026: Toyota Motor Corporation, Toyota Production System. The office workflow recommendations are my application of the principle.