It was eleven o’clock at night when you made the decision.

You’d been turning it over for weeks, but that night, sitting in front of the laptop with the third coffee of the evening, it suddenly became clear. The path forward was obvious. You sent the email, signed the contract, made the offer, killed the project — whatever it was, you committed.

By Friday, you were unwinding it. The information you’d been sure was complete had a gap. The thing you’d been certain about had a counter-factor you hadn’t considered. The clarity you felt at eleven o’clock was a story your brain had assembled out of incomplete data, and you’d believed it because you needed to.

This is why founders make bad decisions when stressed, and it isn’t a willpower problem. It’s a feature of how the brain works. Your operator OS is built to produce confident narratives out of partial information, and the more stressed it is, the more confident the narrative gets. The story feels true because the story has to feel true. That’s the whole point of the system.

And until you understand what’s running, you’ll keep believing the stories you tell yourself at eleven o’clock.

What Happens to Your Decision-Making at 11pm

I work with founders who can tell me exactly when their worst decisions happened. Almost universally, it’s late at night, on the back end of a long week, after a hard conversation, or in the aftermath of a setback. The state matters more than the substance.

The decision feels lucid in the moment. That’s the part that always trips operators up afterward — they don’t remember being confused or hasty. They remember being clear. They remember the clarity feeling like wisdom.

What they don’t remember is what their brain was actually doing. It wasn’t analyzing the situation in front of them. It was constructing a story that made the situation feel resolved, so the nervous system could come down.

The cost of an unresolved, ambiguous situation to a stressed nervous system is enormous. The brain runs hot when probabilities are uncertain, when outcomes are pending, when there’s no clear answer. It evolved to resolve ambiguity quickly — because in an ancestral environment, ambiguity meant unseen threat. The faster the brain could collapse the uncertainty into a definite answer, the faster the system could relax.

That’s the bug that becomes a problem in modern business. Your situation isn’t ambiguous because there’s a tiger in the grass. It’s ambiguous because you genuinely don’t have enough information yet. The right move is to wait, gather more data, or sit with the discomfort of not knowing. But your stressed brain doesn’t tolerate that well — and so it does what it’s built to do. It builds a story out of what’s in front of it, calls the story complete, and lets you act on it.

This pattern has a name in cognitive science, and it explains more about why founders make bad decisions when stressed than any productivity framework can.

What Cognitive Science Calls “WYSIATI”

Daniel Kahneman called this pattern WYSIATI — “What You See Is All There Is.” He won a Nobel Prize for the body of work this idea came from, and most founders have never heard of it.

WYSIATI describes how the brain treats the information immediately available to it as if it were the complete picture. Your mind doesn’t natively acknowledge what’s missing. It builds the most coherent story it can with what’s in front of it, and then it gives you a feeling of confidence that scales with the story’s coherence — not with the story’s accuracy.

This is critical to understand: your confidence in a decision is your confidence in the story your brain assembled, not your confidence in the underlying reality.

A coherent story made of partial information will feel just as confident as a coherent story made of complete information. Your nervous system can’t tell the difference. The signal it’s reading isn’t “do I have enough data,” it’s “does this story hang together.” If the story hangs together, the system relaxes. If it doesn’t, the system stays activated.

This is why founders can be deeply, viscerally certain about decisions that turn out to be wrong. They weren’t lying to themselves. They weren’t being overconfident as a character flaw. Their brain delivered a story that felt complete, the confidence that accompanies a complete story showed up, and they acted on it.

And here’s the part that makes this dangerous for operators specifically: this whole process gets worse under stress.

How Stress Hijacks the Story-Maker

The brain has two systems for processing information. Kahneman called them System 1 and System 2. System 1 is fast, automatic, pattern-matching — it runs your default reactions. System 2 is slow, deliberate, analytical — it does the careful thinking. Under normal conditions, both systems contribute to a decision. System 1 produces a quick read, System 2 checks it against the actual data, and the two negotiate.

Under stress, this changes. Researchers call the shift “Stress Induced Deliberation-to-Intuition” — SIDI for short. When the system is under load, resources get pulled from the prefrontal cortex (where System 2 lives) and reallocated to threat response. System 2 effectively goes offline. System 1 takes over.

System 1 is brilliant at fast pattern-matching, but it’s built on WYSIATI. It works with what’s in front of it. It doesn’t check for what’s missing. It doesn’t slow down to question its own outputs. And when System 2 isn’t there to verify, System 1’s stories run unchecked.

This is what’s happening at eleven o’clock when the decision feels clear. The clarity isn’t a sign that you’ve figured it out. It’s a sign that System 2 has gone offline, that your brain is operating in fast-pattern-matching mode, and that the story it just produced is the only story it can see. Which feels, from the inside, exactly like wisdom.

This is what’s happening at the OS layer. The conscious mind — the Software layer — interprets the experience as deliberate thought. The reality is that the deliberate thinking system has been temporarily benched, and the automated story-maker is running the show alone.

Why Founders Make Bad Decisions When Stressed — And What It Costs Them

Most people’s decisions don’t compound the way founder decisions do. A bad call by a salaried employee is mostly contained. A bad call by an operator — about pricing, hiring, partnerships, product direction, capital allocation — ripples through the entire business for months or years.

Founders also make a higher density of high-stakes, high-ambiguity decisions per week than almost anyone else. Most of those decisions happen on top of a baseline of accumulated stress that never fully clears. Which means the conditions for WYSIATI to produce a bad call are present most of the time.

Here’s the math you don’t want to do but should. If even 15% of your significant decisions are made when System 2 is offline — at night, after a hard week, in the aftermath of a setback — and those decisions are operating on stories that feel complete but aren’t, the cumulative cost over a decade is staggering. It’s the hire you didn’t need to make. The customer you fired who you should have kept. The product line you launched that should have waited a quarter. The pricing move you made based on a competitor’s behavior that turned out not to mean what you thought it meant.

None of those decisions felt rushed in the moment. They felt clear. That’s the trap.

And the cost isn’t just the individual bad decisions. It’s the compounding loss of credibility — with yourself, and with the team that watches you reverse calls every few months. Founders who can’t trust their own decision-making at scale develop a wariness about deciding at all, which becomes its own form of dysfunction. They start over-consulting. They start asking everyone. They build the kind of decision-making process that protects them from themselves but slows everything down.

The real fix isn’t avoiding decisions when stressed. It’s recognizing what state you’re in, and adjusting the decision process accordingly.

How to Stop Making Bad Decisions Under Stress

You can’t will yourself into System 2 when System 2 is offline. That’s the trap most founders fall into — they tell themselves to “think harder” or “be more careful,” and they’re using the part of the brain that’s compromised to fix the part of the brain that’s compromised.

The work is structural, not effortful. Three practices change the underlying pattern.

Name your state before you decide. Before any significant decision, ask: What state am I in right now? Are you tired, hungry, fresh, after a fight, after a win, late at night, mid-morning, two coffees deep? Just naming the state — out loud, in writing, anywhere outside your own head — recruits the prefrontal cortex back into the conversation. You don’t have to change the state to benefit from naming it. The act of observation alone partially reverses the SIDI shift. Most founders never do this because the state feels like background noise. It’s not background. It’s the operating environment for the decision you’re about to make.

Run the pre-mortem against the decision you’re about to make. Before you commit, write down: If this decision turns out to be wrong six months from now, what would I have been missing? This is the structural workaround for WYSIATI. You’re forcing yourself to imagine the gap that you can’t naturally see — the information not in front of you that the System 1 story-maker has rendered invisible. You won’t catch everything, but you’ll catch some of it. And the catches will be the difference between the decisions you reverse and the ones you don’t.

Build a 24-hour wait on anything reversible. If a decision can wait twenty-four hours, make it wait. The state you’re in at eleven o’clock will not be the state you’re in at noon the next day. If the decision still looks clear after sleep, food, and System 2 coming back online, you’ve reduced your WYSIATI risk substantially. If it doesn’t still look clear, you just dodged a bad call. The cost of the wait is almost always smaller than the cost of the wrong call.

These are slow practices. They don’t feel like a productivity gain in the moment. They feel like friction. The compounding effect, though, is the difference between an operator whose decisions improve year over year and one whose decisions oscillate with their state.

The Story Becomes Visible

Back to eleven o’clock and the decision that felt so clear.

The next time it happens — and it will — you’ll notice the clarity arrive. The certainty. The feeling that you finally see it. Instead of acting on the feeling, you can name it for what it is: the System 1 story-maker delivering a coherent narrative built from whatever happens to be in front of you at this hour, in this state, on this much sleep.

The story isn’t necessarily wrong. But the confidence is borrowed from coherence, not from completeness. And until you’ve checked which one is doing the work, you don’t know whether you’ve understood the situation or just resolved it.

This is the harder version of operating, and it’s the one most founders never build. The operators who do build it have a quality that’s hard to name from the outside — a kind of steadiness across states, where the decisions they make at eleven o’clock look about the same as the decisions they make at noon. That’s not luck. That’s the system, working on purpose.

You can build it. It just doesn’t come from working harder.