Pressure is one thing. Feeling trapped is another.
A deadline can focus a team. A deadline nobody is allowed to question can teach the same team to hide problems until the last possible moment. Then everyone acts surprised at the surprise they spent three weeks making impossible to report.
Reading Sheryl Sandberg and Adam Grant's Option B got me thinking about a simple leadership tool: the panic button.
The button changes the situation
There is a long experimental history behind the question of control, including Glass, Singer, and Friedman's 1969 study of adaptation to environmental noise. The useful distinction for this post is between facing an unpleasant demand and believing you have no way to affect it.
Picture two versions of the same task. In one, the noise continues and you have no recourse. In the other, you know how to stop and ask for help. Even before you use that option, the situation means something different.
I am using the panic button as a workplace design principle, not claiming a precise blood-pressure effect or a guaranteed productivity gain. The practical question is: does the team have a credible way to change course when the work becomes unmanageable?
Three buttons worth installing
1. “Call me when this goes red”
Tell people what counts as an urgent escalation, whom to contact, and what help they can expect. A production incident, a blocked decision, an unsafe release: name the cases.
Then answer when they call. “My door is always open” is not a support mechanism if walking through it gets you interrogated about why you failed.
2. The deadline can be discussed
Not every date can move. But scope, staffing, sequencing, and risk can often be discussed before the date arrives. Make it clear which decisions the team can change and which need escalation.
The button is not “ignore the deadline.” It is “bring the evidence early, and we will decide what gives.”
3. We can stop the experiment
Agree that an unsuccessful approach can be stopped without treating its proposer as the failure. What did we learn? What assumption broke? Is the next attempt worth its cost?
Otherwise people keep feeding a project because admitting it is hungry has become more dangerous than letting it eat the quarter.
A button has to work when pressed
Low usage is not the goal. A button nobody presses might mean things are fine. It might mean nobody trusts it.
Watch what happens to the first person who asks for help. That response teaches the team more than the announcement. And if the button is used constantly, investigate the workload and system around it; an emergency route cannot be the entire operating model.
The promise is small: when trouble arrives, you will have somewhere to go and a decision we can revisit. Keeping that promise is the leadership part.
A small modeling detour
I also built a Bayesian simulation inspired by Option B. It explores assumptions using synthetic trajectories; it does not estimate how real people recover. The equations are there for anyone who wants to inspect the toy world.
Have a good weekend. And answer the button.
Related Posts
Ignore the Feathers
Every team has more good ideas than capacity. The hard part is selection — learning to see past the costly signals, prestigious credentials, and compelling narratives to focus on what improves the outcome.
Modeling Resilience: A Computational Exploration of Option B
A Bayesian simulation inspired by Option B: how to make assumptions about recovery explicit, inspect their consequences, and distinguish parameter recovery from evidence about people.