Leadership1 publisher3 min readPublished
Why Leaders Fail Under Pressure: It's the Environment, Not a Lack of Discipline
An Entrepreneur contributor argues leaders fail under pressure because their environment defaults them to habit, and prescribes protected time, decision frameworks and fewer inputs; each of those is paid for by somebody else in the organisation.
The Board Room · Leadership desk
What happened
- An Entrepreneur contributor column argues that leaders under pressure fail for want of an environment that supports deliberate thinking; it rejects lack of discipline or accountability as the cause.
- Its lens is Daniel Kahneman's Thinking, Fast and Slow, which describes a fast automatic system shaped by habit running in parallel with a slower deliberate and analytical one.
- The column names dashboards, Slack notifications, meeting requests, performance metrics and communication streams as the competitors for the attention reflective decisions need.
- Its prescription is to redesign the environment around decisions with protected time, decision frameworks and fewer inputs, and to stop leaning on willpower.
Compiled by The Board RoomSomething wrong?How this is made
Why it matters
- cost Protected time shifts the same amount of waiting onto the people who used to get same-day answers, and that side of the trade is rarely measured.
- decision If input volume and calendar access drive decision quality, improving it is a staffing and delegation call for the executive team. A private self-improvement project will not do it.
- precedent The diagnosis invites a follow-on claim inside companies: a rushed call is a defect in the operating calendar, and a performance review cannot fairly score it as character.
Protected time is a transfer. Nothing is saved. A senior leader's open calendar is the organisation's escalation buffer: anyone stuck can get an answer that day. Block the morning for deliberate work and the queue waits. Two of the three fixes the column prescribes, protected time and fewer inputs [2], are paid for by the people who were doing the interrupting.
The column's own formulation is that "Sustainable behavior change depends less on intensity and more on design" [11]. A decision framework agreed in calm conditions is a promise to overrule your later self, and the column is explicit that trying to change behaviour in the middle of chaos is usually too late [12]. The same pre-commitment removes latitude on the day the case in front of you is not the case the rule was written for. Most weeks that is worth it. The exception is the week the rule's author would have broken it, and nobody in the room has standing to.
A skeptic's version is short: environment language lets a leader who dodged a hard conversation cite the environment and escape being held to account. The column's first step answers that better than its framing does. It tells leaders to stop asking how to become a better leader and to ask instead "What situations repeatedly trigger reactive behavior?" and "What decisions do I consistently rush?" [10]. Those answers are checkable by the people who watched it happen, and the column supplies four candidate moments, among them reacting defensively during disagreement and avoiding difficult conversations until problems escalate [7][13].
The evidence behind the diagnosis is thinner than the diagnosis. Entrepreneur notes that "Opinions expressed by Entrepreneur contributors are their own" [9], and the support offered for the claim is the borrowed two-system account plus the observation that stress, fatigue, uncertainty and information overload hand control to the automatic system, which the column describes as energy conservation and refuses to call a leadership flaw [4]. It does not cite a study of leaders' decisions [14]. The column may still be right, but a board paper leaning on it is leaning on a framing, and the test has to come from the company's own record of rushed calls.
Anyone deciding this quarter should look at the division of labour. Naming the moments where your intention collapses is work a leader can do alone, in an afternoon. Reducing inputs means someone else decides what stops arriving in the leader's day, and protected time means their own request waits. The column puts the redesign with the leader who benefits from it: the ones who change successfully, it says, redesign how decisions happen instead of relying on motivation alone [8].
What to watch
- Any company publishing before-and-after evidence that protected decision time changed outcomes; a rearranged calendar on its own does not count.
- Whether executive teams give a named role ownership of input volume: dashboards, notifications and standing meeting requests.
- Whether a pre-committed decision framework survives its first real crisis, and who is allowed to record an override.