The Courage to Kill — Killing Well Becomes the Next Resource

A killing decision isn't resource recovery — it's asset accumulation.

What a maker who lost 5 years learned

I know someone who spent 5 hours a week and 50,000 KRW a month on a zombie project for 5 years. Features stopped getting added, users stayed under 10. Revenue evaporated through product fees. He kept muttering "someday." Because he was told not giving up was a virtue.

In the end, 600,000 KRW didn't vanish quietly — it disappeared with his eyes open. And the real pain was this: this project consumed the time and money he could have spent attempting a second MVP. Dead projects keep eating life even after they die.

What a zombie project looks like

A zombie project is a business that's dead but pretending to be alive.

When you finished your first MVP after Season 1, you assumed: "Within 3 months I'll know clearly whether this succeeds or fails." Reality differs. That signal stays blurry. 100 users a month, 110 next. Paid users 3 to 5. Is this growth or stagnation?

5 traits of a zombie project

• Growth curve is flat. First month 100, still 110–120
• No or minimal revenue. Monthly fees 30,000 KRW
• Active users declining. 100 signups, 5 active
• Nothing being learned. No feedback, no direction, no reason for failure
• No personal motivation left. Maintained only as "I have to"

If all 5 are true, it's not a project, it's an installment payment. A silent obligation to pay every month. Korean startup angels call this "zombie ventures" — companies chasing government grants and existing only on paper.

Persevere vs zombie: not "direction" but "acceleration"

You learned Persevere conditions in Season 1: don't stop if data is positive. But "positive" is fuzzy. Is 10 users a month "positive"? Positive for one or two months then flat?

What matters is "acceleration," not "direction."

A legitimately Persevere-worthy project gets more output per unit effort over time. What took 100 users of effort in month 1 takes 50 users of effort in month 3. Or 5 paid users in month 1 becomes 20 paid users in month 3 with the same effort. That's the real growth signal.

Zombie projects: input rises but output stays. 5 hours got you 10 people; 3 months later, 5 hours still gets you 10. Worse: doubling time barely holds the previous level.

Many makers think: "I'll put more in. Stopping now wastes everything so far." That's the sunk-cost fallacy. Humans are 2x more sensitive to avoiding loss than gaining gain.

The "just a little more" trap, sunk cost's real name

The most insidious whisper of zombie projects is "just a little more."

• "This month will be different. I added a new feature."
• "Try again next week. The marketing strategy changes."
• "Until this winter. When the season hits, it'll change."

These whispers aren't lies. The possibility exists. There are projects that took off after 6 months, and services that went viral after 3 years. The problem is you have no way to tell whether you are that project.

Park is exactly in that situation. 6 months stuck at 5 paid. 2 hours invested per month. 2 hours "feels manageable." But 6 months × 2h/month = 12 hours. Four other ideas are stuck in Notion, and one of them could have been validated in 1 month.

Action to escape the zombie: a 3-month deadline + external check

The most reliable way to diagnose a zombie project is to set "clear milestones."

What state should your project be in 3 months from now?

• Users 100 → 150
• Or monthly paid 5 → 10
• Or you must prove via analysis that "this problem can't be solved"

If you have none of these, that's not Persevere — that's "continuing to exist."

Strongest zombie diagnostic: external check

3 months from now, on a set date, ask these three people:

1. Is this project really valuable?
2. Given the current growth rate, what will 6 months from now look like?
3. If this project didn't exist, what would you do with that time?

Their honest answers are more trustworthy than your rationalizations. They have no sunk cost.

Zombie diagnostic checklist

If 3 or more apply, seriously consider Kill.

• Flat growth curve last 3 months (±10%)
• Output hasn't moved relative to monthly time invested
• Active user share ≤20% (relative to signups)
• Paid conversion ≤0.5% or revenue < invested cost
• No feedback or unclear direction
• Maintained only because "I have to"
• Continuing fatigue exceeds the regret of killing
• Other projects you want to try are blocked by this one

3 Korean zombie retrospectives

Case 1. Notion organizer tool (2 years, then Kill)

"I spent 300,000 KRW/month — hosting, banners, ads. But signups never crossed 50. 2 years in I realized: this isn't what people want. If I'd spent that time elsewhere, my monthly revenue would be 5x today."

Case 2. Team collaboration SaaS (3 years flat, then Pivot)

"Originally for developer teams, no user growth. But I couldn't quit — I had 10,000 lines of code. 3 years in, customer interviews revealed devs wanted Slack integration, not our tool. We pivoted to a completely different customer. I didn't Kill, but 3 years of sunk cost delayed the Pivot."

Case 3. Community platform (to a hobby)

"Cut ad spend, minimized server cost. Now 100,000 KRW/month. 30 users. No revenue. I keep it alive because this community is the only place my online friends gather. But this isn't Persevere — it's a hobby. Once I drew that line, peace came."

Quick Kill decision table

3+ YES → consider Kill.

Wrapping up

Kill decided, assets organized. Two choices remain. Pivot or Persevere. Kill is hardest; for the same reason Pivot isn't easy.

Next post: "the exact Pivot point." What to change and what to keep.

Previous: Signal vs Noise, Revisited
Next: The Exact Pivot Point — the craft of swapping hypotheses

About the characters (Seoyeon Park, Junho Lee)
Characters in this series are fictional personas created by Fail School. Sunk-cost fallacy, Pieter Levels, Doeon Kwon's Disquiet retro and other citations are real.

Minchul Kim, CEO of Freeive, Fail School