Dr. Wallace's Favorite Mental Models

The Yerkes-Dodson Law

Why a little pressure sharpens your work, and a little more wrecks it — and why the tipping point depends entirely on how hard the task is.

Psychology Performance under pressure Workload design ~6 min read
⛰️

The 30-second version

Performance rises as pressure, stress, or excitement (arousal) rises — but only to a point. Push past that point and performance falls, often sharply. The peak isn't fixed: on easy or well-practiced tasks you can handle a lot of pressure before it hurts you; on hard or unfamiliar tasks, the peak arrives early, and a seemingly moderate amount of stress is already too much. Most pressure-related failures aren't a motivation problem. They're a mismatch between how much arousal a task can actually absorb and how much it's being handed.

Inverted-U curve Task difficulty shifts the peak Named 1908

Mental Model Compass

A quick gut-check before you reach for this model.

Reach for it when…

  • You're deciding how much deadline pressure, stakes, or urgency to apply to a specific task or person.
  • Performance dropped right when stakes went up (a pitch, an exam, a live demo, a big game).
  • You're designing a role, shift, or environment and need to calibrate stress on purpose, not by accident.
  • Someone performs beautifully in practice and falls apart live, or vice versa.

Skip it when…

  • The real constraint is raw working-memory overload from too much information at once — that's Cognitive Load Theory, not arousal.
  • The issue is running out of decisions late in a long day, not stress intensity — that's Decision Fatigue.
  • Someone is dealing with chronic burnout, clinical anxiety, or a diagnosed condition. This model describes momentary task performance, not a substitute for medical or mental-health support.
  • You're tempted to use it to justify manufacturing stress on your team as a management style "because pressure helps." That is exactly the over-application researchers warn against (see Common Mistakes).

How it works, one layer at a time

In 1908, psychologists Robert Yerkes and John Dodson ran mice through a simple maze, giving them small electric shocks of varying strength to motivate faster, more accurate runs. Mild shocks improved performance. Strong shocks made it worse. The relationship wasn't a straight line — it was a curve that rose, peaked, and fell. Decades later, that curve is still the reference point for how arousal and performance relate in humans.

Plot arousal (calm → wired) on one axis and performance (poor → excellent) on the other, and you get a bell-shaped curve. Too little arousal: you're under-aroused, under-motivated, sluggish, or bored — performance is weak. Moderate arousal: you're alert, focused, engaged — performance peaks. Too much arousal: attention narrows, working memory degrades, fine motor control and judgment suffer — performance collapses, sometimes fast.

This is the half of the law that actually makes it useful. For simple, well-rehearsed, or physical tasks, the peak sits far to the right — you can pile on quite a lot of adrenaline before it hurts, and extra arousal can even help (think of a sprinter or a weightlifter under a roaring crowd). For complex, unfamiliar, or judgment-heavy tasks, the peak sits far to the left — a surprisingly small amount of pressure is already past the summit, because the task needs spare working-memory capacity and calm attention that high arousal consumes first.

Try the simulator below — the same stress level is a helpful nudge for one kind of task and a performance killer for another.

A widely cited 2007 review (Lupien et al.) found that stress-hormone levels do track an inverted-U relationship with memory performance, lending real biological weight to the original behavioral finding. But researchers are candid that the exact mechanism isn't fully pinned down, and competing frameworks — flow psychology, reversal theory — argue the relationship between arousal and performance is more textured than one clean curve, especially for how arousal is *interpreted* (threat vs. challenge) rather than just how intense it is. Treat the inverted-U as a strong rule of thumb for calibrating pressure, not a precise formula.

Interactive: move the peak

Pick a task type, then drag the arousal slider and watch where performance actually peaks.

Loading…

Four domains, same curve

SettingUnder-arousedSweet spotOver-aroused
Sales pitch / live demoFlat delivery, no energy, loses the roomAlert, crisp, reads the room, handles questions wellTalks too fast, forgets key points, over-explains out of nerves
Surgery / high-stakes procedureComplacent, misses small cues, slow to reactFocused, steady hands, calm scanning for problemsTunnel vision, hands shake, decision quality drops under time pressure
Competitive sportSluggish, un-motivated, "flat" game"In the zone" — fast, loose, confidentChoking — overthinking routine plays, muscle tension, panic
Exam / certification testCareless errors from boredom or low stakesSharp recall, good pacing, catches own mistakesBlanking, re-reading the same question, running out the clock
Customer support under SLA pressureSlow resolution, little urgencyEfficient triage, clear communicationRushed troubleshooting, missed root cause, reopened tickets
Software incident responseLow urgency, slow to escalate a real outageClear-headed triage, calm comms to stakeholdersPanicked rollback decisions, tunnel-visioned on one hypothesis

Common mistakes

✕
Assuming more pressure is always more output. That's only true on the left half of the curve, on simple tasks. Past the peak, more pressure actively destroys performance.
✕
Applying one pressure level to every task on a team. The same deadline intensity that sharpens a routine, well-rehearsed task can tank a genuinely novel or judgment-heavy one happening at the same time.
✕
Treating "stress helps" as a license to manufacture artificial urgency. This is the exact over-application researchers caution against — the model describes a real relationship, not a mandate to pressure-test people as a management habit.
✕
Confusing challenge with threat. Arousal interpreted as an exciting challenge tends to help longer than arousal interpreted as a threat to your identity or job security, even at the same physiological intensity. Framing matters as much as intensity.
✕
Ignoring practice as a lever. Rehearsal moves a task from "complex" toward "simple" on this curve — it's often cheaper to raise someone's skill than to manage their stress.

When not to use it

Don't reach for this model when the problem is chronic rather than momentary — ongoing burnout, sustained overwork, or a mental-health condition need a different kind of response entirely, not a tighter arousal dial. Don't use it to retrofit a justification for a high-pressure culture after the fact. And don't use it as your only lens on a performance problem — skill gaps, unclear instructions, bad incentives, or plain exhaustion can all look like "wrong arousal level" without actually being one.

Related models in this series

Worked application: redesigning a high-stakes product demo

A team kept blowing investor demos despite flawless rehearsals. Here's how calibrating arousal — instead of just "telling people to stay calm" — actually fixed it.

  1. Name the task type honestly. A live investor demo with Q&A is a complex, partly-novel task (you can't script the questions) — not a simple, rehearsed one. That alone explained why the usual pep talk ("get fired up!") was making things worse, not better.
  2. Separate the sub-tasks by difficulty. The scripted walkthrough is simple and rehearsed — high arousal there was fine, even energizing. The unscripted Q&A is complex — it needed a lower, calmer arousal state to protect working memory for improvising answers.
  3. Changed the pre-demo ritual. Instead of a single hype-up huddle right before going on, the team did the hype huddle earlier (to fuel energy for the scripted part) and added a short, deliberate calming routine (slow breathing, a 2-minute silent review of likely hard questions) immediately before Q&A specifically.
  4. Reframed the stakes from threat to challenge. Leadership stopped saying "this funding round depends on this," which reads as threat, and started saying "this is the best audience we'll get to pressure-test the pitch," which reads as challenge — same stakes, different interpretation.
  5. Practiced the actual difficulty, not a watered-down version. Rehearsals started including a hostile-questioner role-play, which moved the Q&A segment itself from "complex and novel" toward "complex but rehearsed" — raising the arousal level the team could handle before performance dropped.
  6. Measured the right thing afterward. Instead of just asking "how did it feel," they reviewed which specific moments performance dipped, and checked whether those moments lined up with an arousal spike (a hard question, a technical glitch) — confirming the model was the right lens, not just a plausible-sounding story.

Result: the scripted segment stayed energetic, the Q&A got noticeably calmer and sharper, and the team stopped treating "nerves" as a single, undifferentiated problem to be willed away.

Try It Yourself: build your own calibration prompt

Describe a real situation. This builds a ready-to-use prompt you can hand to any AI assistant (or think through yourself) to diagnose where you're sitting on the curve.

Save this as a reusable skill

A portable reference you can hand to any AI assistant, or keep for yourself, so this model is one copy-paste away whenever you need it.

Preview

Apply to My Problem

Describe what you're dealing with, and get a tailored prompt that applies the Yerkes-Dodson Law directly to it.