The Delayed-Good, Bad-Forever Quality Rule
A delayed game is eventually good; a bad game is bad forever.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 75%
Shigeru Miyamoto's famous design principle argues that shipping deadlines should bend to quality, not the reverse: a late product can still become great once it's finished, but a rushed, poor-quality product carries that reputation forever because, unlike software patched post-launch on other platforms, Nintendo historically does not meaningfully rework games after release. This principle functioned as a decision rule for delaying titles (and consoles) until they met an internal bar, prioritizing long-term brand equity over short-term revenue or competitive timing. It explains both major Nintendo successes (delayed but excellent titles) and a real failure mode: without a check on what 'good' means, teams can convince themselves a delayed product will 'eventually' be good and polish indefinitely without truly fixing what's broken.
Origin
Extracted from Acquired
Core principles
- 01Tie launch timing to a quality bar, not a calendar date
- 02Assume you cannot fix a bad reputation post-launch
- 03Protect long-term brand equity over short-term revenue timing
- 04Recognize this rule can become an excuse for endless polishing if not paired with real criteria for 'good'
How to run it
- 1
Define what 'good' means before you start
Set explicit, non-negotiable quality criteria for the product so 'delay until good' has a real finish line instead of becoming indefinite polishing.
Watch out Without clear criteria, teams can convince themselves any delay is justified indefinitely.
- 2
Give the team authority to slip the date
Empower creative/product leadership to move the ship date when quality criteria aren't met, insulating the decision from short-term sales or investor pressure.
Pro tip This requires a leader willing to visibly back the delay decision publicly.
- 3
Treat launch as (mostly) final
Because you're not planning to substantially patch or live-service the product after release, invest the extra time pre-launch rather than assuming problems can be fixed later.
Watch out This philosophy conflicts with live-service/games-as-a-service models where post-launch iteration is expected and valued.
- 4
Weigh brand equity against competitive timing
Accept the risk of a competitor's first-mover advantage in exchange for protecting the long-term reputation of the franchise or platform.
In the wild
Zelda: Breath of the Wild was originally intended as a Wii U exclusive but was delayed and ultimately launched simultaneously with the Switch.
→ The game is widely regarded by industry insiders as one of the best-designed titles ever made and achieved a rare one-to-one console attach rate, anchoring the Switch's early success.
Common mistakes
Mistaking 'eventually good' for guaranteed good
Critics note Nintendo sometimes assumes every one of its franchise entries is automatically excellent, when in practice quality still varies release to release.
Ignoring the live-service alternative
Rivals improve mediocre launches significantly post-release; refusing to do this can leave a flawed launch title permanently underdeveloped.
Is it for you?
Not ideal for
Live-service or fast-iteration software products where post-launch patching is expected and cheap.
From the transcript
“a delayed game is eventually good. A bad game is bad forever.”
From the episode
Nintendo: The Console Wars