How to Decide When to Pivot a Project

Deciding when to pivot a project—changing its direction significantly—means pivoting when the evidence shows the current direction isn't working and a different one is genuinely more promising, rather than pivoting at the first difficulty or on a whim. Distinguishing a needed pivot from ordinary difficulty is what makes pivoting a sound decision rather than a reactive one.

Pivot based on real evidence, not first difficulty

Pivoting is a major decision, and it should be based on real evidence that the current direction isn't working—not on the first difficulty or a whim. Pivoting based on evidence means the decision to pivot rests on genuine evidence that the current direction won't work (the core isn't fun and can't be fixed, the concept doesn't hold up, the evidence shows the direction is fundamentally flawed)—as opposed to ordinary difficulty (the project is hard right now, but the direction is sound). This distinction is crucial because pivoting at the first difficulty (reacting to ordinary hard moments by changing direction) leads to never finishing anything (constantly pivoting away from sound directions that just got hard), while pivoting based on real evidence (genuine signs the direction won't work) is a sound response to a fundamentally flawed direction. Distinguishing real evidence that the direction won't work (the basis for a sound pivot) from ordinary difficulty (which persistence overcomes) is the key, because pivoting should respond to genuine evidence of a flawed direction, not to the ordinary difficulty that all projects have. Pivoting based on real evidence, not first difficulty—pivoting when the evidence shows the direction won't work, not at ordinary hard moments—is the foundation of a sound pivot decision, distinguishing a needed pivot from a reactive one.

A pivot needs a genuinely more promising direction. Beyond evidence that the current direction isn't working, a pivot needs a genuinely more promising alternative direction to pivot to. A genuinely more promising direction means the new direction you'd pivot to is genuinely more promising than the current one—a real reason to believe the new direction will work better, not just a different direction or a grass-is-greener impulse—because pivoting to a direction that isn't genuinely more promising just trades one struggling direction for another, without improving the project's prospects. A sound pivot requires both that the current direction isn't working (the evidence) and that a genuinely better direction exists (a real, more promising alternative), so the pivot improves the project's prospects rather than just changing direction. Without a genuinely more promising alternative, pivoting away from the current direction (even if it's not working) just abandons it without a better path, which may be worse than persisting or stopping. A pivot needing a genuinely more promising direction—a real, better alternative to pivot to—is what makes pivoting improve the project rather than just change it, ensuring the pivot is to something genuinely better. Combining pivoting based on real evidence, not first difficulty (pivoting when the direction genuinely won't work) with a pivot needing a genuinely more promising direction (a real, better alternative) is what makes a pivot decision sound—pivoting based on real evidence that the current direction won't work, to a genuinely more promising alternative, which improves the project's prospects. Deciding to pivot this way—based on real evidence and a genuinely better direction—is what makes pivoting a sound strategic decision that improves the project, rather than a reactive response to difficulty or a whim that just trades directions. Pivot based on real evidence that the current direction won't work and a genuinely more promising direction exists, distinguishing a needed pivot from ordinary difficulty, and pivoting becomes a sound decision that improves the project's prospects, rather than the reactive pivoting that abandons sound directions at the first difficulty or trades for a no-better alternative. A sound pivot responds to real evidence with a genuinely better direction, which is what makes it improve the project rather than just change it.

Default to the boring, robust choice

It's tempting to reach for the clever, novel, or technically impressive solution, but in production the boring choice — the well-understood approach, the proven pattern, the simple implementation — is usually the one that ships and keeps working. Cleverness has a way of becoming the bug you're debugging at 2am six months later.

Save your novelty budget for the things that actually make your game distinctive, and be conservative everywhere else. A game built on robust, unremarkable foundations is one you can keep building on, while one built on clever fragility is one that fights you the whole way.

Make the common case effortless

Most of what a player does, they do over and over, and most of what you build will be exercised in a handful of common situations far more than in the edge cases. Optimising the rare and neglecting the frequent is a reliable way to make a game that's technically complete and practically annoying.

So spend your polish where the volume is: the action repeated a thousand times, the menu opened constantly, the path every player walks. Making the common case smooth and satisfying does more for how the game feels than perfecting the corners almost nobody reaches.

Protect the thing that makes it special

Every game that connects has some core spark — a feeling, a mechanic, a tone — that's the real reason people love it, and that spark is fragile. In the rush to add content, fix problems, and respond to feedback, it's easy to sand away exactly the quality that made the game worth making in the first place.

Know what your spark is, and guard it. When a change threatens the thing that makes your game distinctive, that's the change to question hardest, because a game can survive plenty of rough edges but rarely survives losing its soul.

Why finishing beats perfecting

The hardest skill in indie development isn't any particular technique — it's finishing. Most games that never ship didn't fail on talent; they failed on scope, polished forever, or chased one more feature. The developers who build a real body of work are almost always the ones who got good at choosing something small enough to complete and then completing it.

That's worth keeping in mind here, because it's easy to let any one part of development expand to fill all your time. Decide what 'good enough to ship' looks like, protect that line, and treat the endless list of possible improvements as a backlog rather than a set of obligations.

Plan for the parts you can't see

Once a game leaves your machine, a lot of what happens to it becomes invisible by default. Players run it on hardware you don't own, hit problems you never reproduced, and most of them never tell you — they simply move on. The gap between 'it works for me' and 'it works for everyone' is where a surprising amount of churn quietly lives.

So plan to see what you otherwise couldn't. Watching real players, capturing the bugs and crashes they hit with the context to fix them, and paying attention to where they drop off all turn invisible problems into ones you can actually act on — which protects the reviews and retention everything else depends on.

Pivot a project when the evidence shows the current direction won't work and a genuinely more promising direction exists—not at the first difficulty or on a whim. Distinguish real evidence of a flawed direction from ordinary difficulty, and ensure the new direction is genuinely better, so pivoting improves the project rather than just changing it.