PG Canon · Chapter 06
Mistakes That Kill Startups
PG's list of the eighteen mistakes that kill startups reads less like trivia and more like a pattern-matched autopsy report. Most failures are one of these, in combination.
After this lesson
- Know the eighteen named failure modes, not just the vague ones
- Recognize which mistakes you're currently closest to
- Use the hardest-lessons essay to separate real problems from noise
Startups rarely die of one big mistake
They die of an accumulation of small, nameable mistakes — a shaky co-founder situation, a marginal niche, slowness to launch — each survivable alone but fatal in combination. Naming them makes them easier to catch early.
The 18 mistakes, condensed
- Single founder — no one to catch blind spots, share the load, or keep morale up
- Bad location — building where there's no density of users, talent, or peers
- Marginal niche — solving a real problem for almost no one
- Derivative idea — copying an existing company instead of starting from a real problem
- Obstinacy — refusing to change the idea even after the evidence says to
- Hiring bad programmers, and choosing the wrong platform — technical debt that compounds
- Slowness to launch, and launching too early — both stall learning, just in opposite directions
- Having no specific user in mind — designing for an imagined 'everyone'
- Raising too little money, and raising too much — both distort incentives and runway math
- Poor investor management, and sacrificing users to supposed profit
- Not wanting to get your hands dirty, and a half-hearted effort — the two faces of not really trying
Case
Case: the derivative idea in a marginal niche
A team clones a successful product's UI and pricing but targets a narrower, less painful slice of the same problem — both 'derivative idea' and 'marginal niche' at once.
Takeaway: Individually survivable mistakes compound. This team had two of the eighteen simultaneously and didn't notice until users declined to switch for a smaller improvement.
What 'Hardest Lessons' adds
Beyond the named mistakes, some lessons resist being taught in advance — how demoralizing rejection actually feels, how much real focus costs, how easily motion gets mistaken for progress. Read this essay when the eighteen-mistake checklist feels too clean for how it actually feels day to day.
Case
Case: three months of shipping, zero weeks of growth
A founder ships a visible redesign or new feature roughly every two weeks for three straight months — a new onboarding flow, a redesigned dashboard, a settings overhaul. The team feels enormously productive; the changelog is long. Weekly active users haven't moved the entire quarter.
Takeaway: None of the three months of work touched the one complaint that kept showing up in support tickets and churn surveys. Motion had been mistaken for progress — a distinctly 'hardest lessons' failure that no checklist item names directly, because it looks like diligence from the inside.
Which mistake are you closest to right now?
Be specific, not general.
Read the original
The 18 Mistakes That Kill StartupsThe named failure modes — use it as a checklist, not trivia.
This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.
Read the original
The Hardest Lessons for Startups to LearnThe lessons that resist being taught until you've felt them yourself.
This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.