"Speed and learning are inseparable.
Pressure does something predictable: it narrows attention. In a rollback decision with incomplete telemetry, that narrowing turns into a demand for certainty you cannot honestly provide.
If you do not write the decision, you do not avoid it—you postpone it until the worst moment. You see it in temporary mitigations that become default behavior by repetition, when execution interprets the boundary differently than you meant. If you cannot describe the boundary simply, the boundary will not survive escalation and reorgs. A single written sentence can remove more noise than another meeting, because it stops the renegotiation loop.
Name the non-goal and the boundary that defends it so the work stays shippable under pressure. That is what makes execution calmer. Make the decision legible to the next person who inherits it.