A crisis can make priorities feel obvious because many options disappear. That does not make crisis a good management system. The useful task is to create enough clarity for action without creating unnecessary alarm.
Reduce the decision surface
When a project stalls, list the decisions actually preventing progress. Some may be preferences that can remain open. Others may be essential dependencies. Choose the smallest decision that unlocks meaningful work.
A hypothetical emergency illustrates how quickly people can act when the objective is unmistakable. It does not prove that people work best under threat or that every delay is laziness.
Give the next step a boundary
Specify the output, owner and review time. “Send two viable directions by Thursday so we can choose one” is more actionable than repeatedly telling a team that the project is urgent.
Make the available resources and trade-offs explicit. A shortened deadline may require less scope or a different quality threshold, and someone needs authority to make that decision.
Keep escalation meaningful
If everything is urgent, the team loses a reliable way to distinguish a real incident. Agree on the conditions that justify interrupting planned work and the person responsible for calling that change.
Learn from the stall
After progress resumes, inspect why the work was blocked. Unclear ownership, missing input and too many parallel priorities are design problems. Solving them is more sustainable than recreating the emotional intensity that happened to move the work once.