"A failure to decide is often disguised as a request for more data.
In a release that is halfway out and already being noticed, the room keeps asking for one more datapoint, as if it will remove responsibility. Meanwhile the calendar keeps committing you.
If you do not write the decision, you do not avoid it—you postpone it until the worst moment. You see it in a ship/hold call with incomplete data, when execution interprets the boundary differently than you meant. Make the signal observable, not philosophical, so you can act without debating intentions. Keep it calm, concrete, and small; the goal is a move you can repeat, not a speech you can admire.
Write one sentence that commits the team: next step, non-step, and reopen signal. That is what makes execution calmer. Let others hold you to it.