When to pause
Is this moment asking for automatic approval?
Not every decision requires a hold. The threshold is whether speed, pressure, or habit is closing the gap between influence and response before judgment can return. When the source of the impulse is unclear, the default should be inspection, not release.
Evidence and suggestion
What is being suggested, and what is actually known?
A recommendation, an AI output, an urgent request — these are not facts. They are inputs carrying authority claims. Separate what is being proposed from what can be verified. Fluency is not accuracy. Urgency is not necessity. Agreement in a group is not truth.
Authority and responsibility
Who is asking, and who carries the consequence?
The person or system making a recommendation may not carry the cost of the decision. An AI does not live with the outcome. A platform does not own the regret. A manager may share the consequence but not the full weight. Before approving, clarify whether the authority to decide still sits with the person who will absorb the result.
Reversible and irreversible decisions
Can this decision be walked back?
Some actions can be revised, corrected, or undone at low cost. Others commit resources, relationships, or reputation irreversibly. The more irreversible the decision, the stronger the case for holding, inspecting the source, and returning approval to its owner before action.
Who carries the consequence
If this goes wrong, who absorbs the cost?
A decision made under pressure often separates the decider from the bearer. The person who clicks may not be the person who suffers. Before approving, name who will live with the result — and whether that person is present in the decision.
Verify, delay, or refuse
Is approval the only option?
Approval is not binary. You may proceed, but you may also revise the action before release, verify the facts before committing, delay until more is known, or refuse passage entirely. The right to approve includes the right to set conditions, and the right to withhold.