Lives Designed Like Bad Games (And How to Fix the Level Design)
Game designers have known for 30 years how to make people voluntarily attempt hard things, fail, and try again. Most self-improvement advice ignores everything they've learned.
In this article3 sections
Game designers spend careers solving a problem that behavioral scientists have been wrestling with for decades: how do you get someone to voluntarily attempt something difficult, fail, and then choose to try again?
The gaming industry generates over $180 billion per year from the answer to that question. Billions of hours of human attention are voluntarily directed at challenging tasks that produce no material reward. People stay up until 2am trying to beat a difficult level they’ve attempted thirty times. They restart from scratch after losing hours of progress and feel motivated to do so.
Then they close the laptop and fail to do their morning workout for the third day running.
The difference isn’t motivation. It’s design.
What Games Get Right That Habits Get Wrong
In 1990, Mihaly Csikszentmihalyi published his foundational research on “flow,” the psychological state of optimal experience that emerges when skill level and challenge level are in balance. Too easy, and attention wanders. Too hard, and anxiety overrides engagement. The sweet spot — where difficulty slightly exceeds current skill — is where sustained voluntary effort happens.
Good game designers have internalized this as craft. A well-designed game doesn’t start at full difficulty. It opens with a tutorial level: a structured entry point where core mechanics are learned through low-stakes repetition. Failure in the tutorial is cheap, the consequence is minimal, and the feedback is specific enough to teach. By the time the game gets hard, you understand the rules well enough to work through the difficulty rather than being baffled by it.
Most habits are designed like terrible games. They skip the tutorial. They start at maximum difficulty. They provide no feedback until failure, and failure carries full cost with no respawn.
Consider a common scenario: someone decides to wake up at 5:30am to work on a side project before their workday starts. Day one: they get up, they’re exhausted, they sit in front of the project for 90 minutes in a state of cognitive fog that produces nothing usable, and they go to work feeling worse than before. Day three: they don’t get up. Day seven: the habit is dead and they’re blaming themselves.
What happened? The level was immediately at maximum difficulty. There was no tutorial. There was no feedback mechanism between “got up” and “produced meaningful work.” There was no respawn (the missed day feels like a game over rather than a level restart with full health). And the win condition was undefined enough that success or failure can’t actually be determined in real time.
The game was broken before it started.
The Four Design Failures
1. No win condition.
Every playable game has a clearly defined state of victory. You rescue the character. You reach the score. You clear the level. The player can, at any moment, determine whether they’re winning or losing, and how far from winning they currently are.
Most habits have no equivalent. “Get healthy” is not a win condition. “Be more productive” is not a win condition. “Finally do the thing I’ve been putting off” is the most unplayable game imaginable: no defined endpoint, no scoring, no way to know if you’re ahead or behind.
The values calendar approach is a step toward win condition definition, but most people stop short of being specific enough. The game designer’s question is: at 5pm today, how will I know whether today was a win? If you can’t answer that in 10 seconds, the game isn’t designed yet.
2. Wrong difficulty curve.
Every competently designed game adjusts difficulty dynamically based on player performance. In some games, this is explicit: “adaptive difficulty” systems that track failure rates and reduce enemy health or slow projectile speeds when a player is struggling.
Habits typically work in reverse. The first week is hardest: new behavior, unfamiliar context, no positive feedback yet from results. The motivation is highest but the capability is lowest. When the habit would be getting easier (around week six to eight, as automaticity begins), the person has often already quit.
A well-designed habit would have its steepest challenge after the initial enthusiasm has provided scaffolding, not before. This means starting with a deliberately degraded version of the target behavior: the minimum viable game, not the full thing. Not “wake up at 5:30 and work for 90 minutes,” but “wake up 20 minutes earlier than usual and spend 15 minutes on a low-stakes version of the project.” Tutorial level.
3. No respawn.
In almost every well-designed game, losing is not game over. You respawn, usually near the point of failure, with your accumulated upgrades intact, and you try again. The cost of failure is time, not progress.
Most people treat a single missed day in a new habit as evidence that the game is over. They don’t respawn. They restart from the beginning (the classic “I’ll start again next Monday”) or they don’t restart at all. The week-three kill zone kills so many habits specifically because it’s the moment when this design failure meets peak difficulty: the novelty is gone, the automaticity hasn’t arrived, and one bad day feels conclusive.
A well-designed habit has explicit respawn mechanics: a defined protocol for what happens after a missed day or a bad week. Not a punishment. Not a consequence that erases progress. A restart from the nearest checkpoint, with whatever was earned still in inventory.
4. Invisible feedback loops.
Games provide near-constant feedback: health bars, score counters, sound effects, visual confirmation that actions produced effects. A player knows within seconds whether their approach is working.
Most habits have feedback loops measured in months. You can’t tell if the morning workout is “working” until weeks in. In the absence of real-time feedback, the brain defaults to estimating based on effort and discomfort, and effort and discomfort feel bad, which signals “this might not be worth it” rather than “this is the challenge zone where progress happens.”
Building short-loop feedback into habits changes this. A streak counter is a feedback loop. A brief written note at the end of a session is a feedback loop. A shared accountability structure where someone else knows whether you showed up is a feedback loop with social dimensions that the brain processes differently from private self-tracking.
Redesigning the Game
The game designer’s approach to behavior change doesn’t require new motivation. It requires better level design.
Define the win condition for today, not the year. What specific, checkable thing would need to be true at 5pm for today to count as a win? Write it down in the morning. Check it at 5pm.
Start easier than feels necessary. The tutorial level should feel slightly embarrassing in its simplicity. If it doesn’t, it’s too hard.
Build an explicit respawn protocol. Decide now what happens when you miss a day: a specific reduced action, one person told, and a restart. The respawn has a known form before you need it.
Create a feedback loop that fires within 24 hours. Whether that’s a streak counter, a brief log, or a person who knows whether you showed up, the brain needs signal faster than monthly outcomes provide.
The motivational problem you think you have is often a design problem. Games solved this decades ago. The mechanics — tutorial level, clear win conditions, respawn protocol, short feedback loops — aren’t proprietary. They’re available to apply to any behavior you’re trying to build.
DontSnooze runs on these exact mechanics: a daily proof of completion (feedback loop), a streak counter (win condition), a social challenge structure (multiplayer), and consequences for missing that don’t end the game (respawn). Not because it’s trying to gamify your life, but because these are the structures that make voluntary sustained effort possible in any domain.
The level is hard. But the design doesn’t have to be broken.