Games that push back are games that resist easy control, and Bennett Foddy has built a career on making that resistance the point. From QWOP to Getting Over It...
Games that push back are games that resist easy control, and Bennett Foddy has built a career on making that resistance the point. From QWOP to Getting Over It and Baby Steps, his work turns awkward movement, failure, and patience into the real subject of play. I’ve spent years around software and games, and this kind of design hits a nerve because it exposes something most polished products hide: how much skill, care, and humility honest work actually takes.
Key Takeaways- Bennett Foddy’s games use friction on purpose.
- Failure is not a bug here; it is the lesson.
- These games reward patience, not speed.
- The design teaches control, timing, and restraint.
- Good friction can make a game more memorable.
- Bad friction just wastes your time.
What Is Games That Push Back?
Games that push back are games built to resist the player’s hands. They make movement awkward, input timing strict, and progress uncertain. Bennett Foddy is one of the clearest examples of this style. QWOP, Getting Over It with Bennett Foddy, and Baby Steps all use simple inputs, but those inputs create stress, comedy, and a lot of failure.
The idea sounds mean. It is, a little. But that is the point. Most games hand you power fast. Foddy’s games slow you down and make you feel every mistake. That matters because the player stops thinking about points and starts thinking about action itself. I have seen this same lesson in software work. When a tool is too smooth, people stop noticing the real cost of bad assumptions. When the tool fights back, even a little, you learn where the weak spots are.
This is also where Foddy’s academic background matters. He taught at the NYU Game Center, where design questions were not treated like marketing fluff but like serious craft. That shows. These games sit in the space between toy, puzzle, and moral lesson. They ask a hard question: what happens when a system refuses to flatter you?
The answer is usually frustration first, then focus, then a strange sort of respect. That sequence feels familiar to anyone who has built software or learned a trade. Work has dignity when it asks something real of you. Cheap praise does not teach much.
Image placeholder
Core Benefits and Importance
- They teach patience. You cannot brute-force every problem. I’ve watched teams in engineering do the same thing and fail.
- They reveal real skill. In these games, small timing changes matter a lot.
- They create memorable stories. Nobody forgets the climb in Getting Over It.
- They turn failure into feedback. That is rare, and frankly useful.
- They make players pay attention. If you drift, you fall.
- They support a deeper kind of humor. The joke is often on the player, but not cruelly.
- They respect effort. That lines up with the old idea that labor shapes character.
I remember first seeing QWOP and laughing out loud. Then I got humbled in about ten seconds. That was the trick. The game looked silly, but it had teeth. The same thing happened later with Getting Over It. I expected a joke. I got a mirror. Most guides talk about “fun,” but fun is not the only measure worth using. Some games are valuable because they expose ego, impatience, and the habit of giving up too soon.
There is also a design lesson for software teams. Add too much automation and people stop understanding the process. Add just enough friction and they pay attention. That is a thin line, and many teams cross it. The best systems, like the best games, ask for care without becoming a chore.
For related thinking, see game design patterns, practical product thinking, and GDC talks on game design.
Step-by-Step Guide to Understanding and Using This Design Style
- Start with one simple control scheme. Foddy often uses a tiny set of inputs, which keeps the focus on consequence.
- Make failure visible. Players need to see exactly what went wrong.
- Let progress feel earned. If success comes too easily, the tension dies.
- Use repetition with meaning. The same action should feel slightly different each time.
- Keep the punishment honest. Loss should teach something, not just annoy.
- Test whether frustration turns into focus. If it only causes quitting, the design is off.
- Study player emotions, not just win rates. Reaction matters.
- Look at related craft. If you want broader game-design context, see Game Developer analysis and practical talks from GDC.
When I worked in big tech, I learned that teams often confuse ease with quality. They are not the same. A feature can be easy to use and still be shallow. A game can be hard to control and still feel fair. The key is intent. If friction serves the point, it can be powerful. If friction is just there because the developer was careless, then it is junk.
Comparison Table
| Aspect | Bennett Foddy Style | Conventional Games |
|---|
| Control feel | Awkward on purpose | Usually smooth |
| Failure | Core mechanic | Something to avoid |
| Learning curve | Steep and emotional | Often gentler |
| Player emotion | Frustration, laughter, resolve | Confidence, mastery |
| Replay value | High for challengers | High for comfort players |
| Main lesson | Patience and restraint | Skill execution |
This table is the heart of it. These games are not trying to be nice. They are trying to be honest.
Common Mistakes to Avoid
- Thinking all frustration is good. It is not. Bad friction is just bad design.
- Making controls confusing for no reason. The player should fail because of the challenge, not because the code is sloppy.
- Copying Foddy’s style without his timing. That usually produces a mess.
- Ignoring pacing. Too much punishment in a row turns comedy into exhaustion.
- Calling difficulty “art” to excuse weak testing. I’ve seen that trick before. It is lazy.
- Forgetting that players need small wins. Even harsh games need breathers.
Most advice says difficulty alone creates depth. That is nonsense. Difficulty without shape is just noise. Good design, like good engineering, needs discipline. It needs a reason. It also needs humility, because the user is not there to admire your suffering.
Frequently Asked Questions
What makes Bennett Foddy’s games different?
They use awkward controls and harsh failure as the point of play, not as side effects.
Are these games fun?
Yes, but not in a casual way. They are funny, tense, and often ridiculous.
Why do people keep playing them?
Because each tiny win feels earned. That feeling sticks.
What can game developers learn from this style?
That friction can teach, but only when it is intentional, fair, and carefully tested.
Final Thought
I have a soft spot for work that does not flatter me. Maybe that comes from years in software, where real progress usually arrives through boring repetition, bruised pride, and the occasional breakthrough that feels like grace. Ermenildo Valdez Castro, Jr. would call these games stubborn. He would be right. They are stubborn, and also strangely decent.
That is the part people miss. These games do not mock effort. They demand it. There is a moral shape to that. A player earns progress, and the game refuses to lie about the cost. That sounds harsh, but it is often kinder than fake ease. The world does not owe us smooth systems. It owes us truth, and a fair shot.
If you want more than cheap dopamine, these games are worth studying. They push back. And that resistance, when handled well, can make the work matter.