Back to Articles
The Kill/Greenlight Ritual
December 1, 20246 min read

The Kill/Greenlight Ritual: Staying Ruthless About Portfolio Quality

I'll never forget the moment I finally killed my "revolutionary AI-powered meal planner."

Three months. That's how long I'd been nursing this thing along. I had a working prototype, 50 user interviews under my belt, and even 200 people on the waitlist. The validation looked... decent. Not amazing, but decent enough to keep going, right?

Wrong.

When I finally forced myself to look at the numbers honestly, the story was brutal:

The Hard Truth:

  • Portfolio Score: 22/40 (barely above my kill threshold of 20)
  • Opportunity Score: 7.2/10 (below my 8.0 proceed threshold)
  • Validation Results: 200 signups (needed 500), 4% prepayment conversion (needed 10%)

Every rational signal screamed "kill this thing." But I'd invested three months. I'd told friends about it. I'd built features I was genuinely proud of. The sunk cost fallacy was doing its thing: "just give it one more week..."

I killed it anyway.

Two weeks later, I started working on a habit tracker that scored 32/40 with an 8.5/10 opportunity score. It hit every validation threshold in four weeks. Now it's in production.

The Breakthrough Realization:

The meal planner would have consumed six more months and failed anyway. The habit tracker succeeded because I started it instead of doubling down on mediocrity.

That's the power of ruthless portfolio management: saying no to mediocre ideas so you can say yes to exceptional ones.

Most founders can't kill ideas. We get emotionally attached. We rationalize. We pivot when we should kill. And we end up with zombie projects that consume resources without delivering results.

So I built a system. A weekly ritual that makes these decisions systematic, not emotional. Let me show you exactly how it works.

Why Founders Can't Kill Ideas (Spoiler: It's All Psychology)

Before we get to the solution, let's talk about why this is so damn hard. I've made every mistake in this section. Multiple times.

The Sunk Cost Trap

"I've already spent three months on this. I can't quit now."

This one nearly killed my productivity for two years. I'd work on mediocre ideas way past their expiration date because I couldn't stomach the thought of "wasting" the time I'd already invested.

Here's what finally clicked for me: past time is gone regardless. The question isn't "was it worth three months?" The question is "is it worth the next three months?"

Real Example from My Portfolio:

I'd built 60% of an MVP for a project management tool. Validation was weak, users were lukewarm at best. But I kept thinking, "I just need to finish the last 40% and then I'll know for sure."

The rational question: Do I spend three more months finishing something users don't want, or three months starting something they desperately need?

I chose option A the first time. Learned my lesson the expensive way.

Identity Attachment (AKA "This is MY Baby")

"This is my idea. I came up with it. It defines me as a builder."

I used to introduce myself at meetups as "the guy building the AI meal planner." When it came time to kill it, it felt like I was killing part of my identity.

The healthier truth: your identity shouldn't be tied to one idea. You're a builder, not "the person who builds meal planners." Good builders kill bad ideas. It's a feature, not a bug.

The Optimism Bias Death Spiral

"It'll work if I just try this one more channel/feature/pivot."

Oh man, this one. I've watched founders (including past me) go through this sequence:

  • Validation test fails → "Maybe Facebook ads are the wrong channel. Let's try Reddit."
  • Reddit fails → "Maybe Reddit users don't convert. Let's try Twitter."
  • Twitter fails → "Maybe we need a different feature set."
  • Feature pivot fails → "Maybe it's a positioning problem."

Endless pivots to avoid the hard truth: the market doesn't want this thing.

The Solution: Systematic Kill/Greenlight Reviews

After killing the meal planner and seeing the habit tracker succeed immediately, I realized I needed a system. Something that would make these decisions based on data, not emotions.

Enter the weekly kill/greenlight ritual.

The Core Principles

1. Expected Value Trumps Sunk Cost (Always)

Every decision comes down to: Expected Value = (Probability of Success) × (Impact if Successful)

Always choose the option with higher EV, regardless of past investment. This sounds obvious, but it's hard to do when you've got three months invested in something.

Expected Value in Action:

Idea A (current meal planner):
10% chance of $100K/year = $10K EV, requires 6 more months
Idea B (new habit tracker):
30% chance of $200K/year = $60K EV, requires 6 months
Decision: Kill A, start B. B has 6x higher EV.

2. Clear Kill Criteria (No Negotiation)

I learned this the expensive way: if you don't have clear criteria, you'll rationalize keeping bad ideas alive forever.

My non-negotiable kill criteria:

  • Portfolio Score < 20/40
  • Opportunity Score < 8.0/10
  • Validation thresholds missed by >30%
  • Founder loses conviction ("I'm forcing myself to work on this")

If it hits these criteria, it's dead. No "one more week." No exceptions.

3. Weekly Reviews (Not When You Feel Like It)

Every Friday at 4 PM, I spend 30-60 minutes reviewing my entire portfolio. Not when projects fail. Not when I'm frustrated. Every. Single. Week.

This prevents the drift. You don't work on ideas for months without checkpoints.

The Kill/Greenlight Review: Step-by-Step

Alright, let me walk you through exactly how I run these reviews. This is the actual process, not some idealized version.

Step 1: Open the Hub and Survey the Damage

I navigate to my project hub and get the full picture. Right now I'm looking at 16 ideas total:

  • Top Priority (≥30 score): 7 ideas
  • Proceed (passed validation): 7 ideas
  • Pivot/Kill (failed or struggling): 9 ideas

Step 2: Review Active Ideas

For each idea currently in discovery, validation, or build, I ask:

Discovery phase:

  • Is Opportunity Score ≥ 8.0? (If no → kill or pivot)
  • Are all 4 discovery docs complete? (If no → complete or kill)
  • Do I still believe in this problem? (If no → kill)

Validation phase:

  • Are we on track to hit thresholds? (If no → analyze why)
  • Is our velocity acceptable? (If behind → boost effort or pivot)
  • Are we learning what we expected? (If no → pivot or kill)

Build phase:

  • Is the feature shipping on time? (If no → remove scope or delay)
  • Am I still excited about this? (If no → kill)

Step 3: A Real Review Session (Last Friday)

Let me show you how this played out in my actual review last week:

Active Idea 1: Habit Tracker (Validation Phase)

Status:

  • Score: 32/40 (Top Priority)
  • Opportunity Score: 8.5/10 (above threshold)
  • Validation: 104 signups (threshold: 100 ✅), 11.5% prepayment (threshold: 10% ✅)
  • Velocity: Hit thresholds in week 3 (ahead of 4-week plan)

My internal monologue:

"Validation passed. Users are paying. Feedback is enthusiastic. This is a no-brainer."

Decision: GREENLIGHT → Move to build phase

Active Idea 2: AI-Powered Meal Planner (Validation Phase)

Status:

  • Score: 22/40 (Medium Priority, barely above kill threshold)
  • Opportunity Score: 7.2/10 (below 8.0 threshold)
  • Validation: 200 signups (threshold: 500 ❌), 4% prepayment (threshold: 10% ❌)
  • Velocity: Week 4, significantly behind pace

My internal monologue:

"We're only 40% to signup threshold and prepayment conversion is half what we need. But I've already built the waitlist, wrote the copy, spent $300 on ads..."

And there it was, the sunk cost fallacy trying to make the decision for me. But the data was clear:

  • Opportunity Score below threshold (7.2 < 8.0)
  • Validation missed by >50% on both metrics
  • My own conviction was wavering
  • Better idea waiting in backlog (fintech SaaS, score 28/40)

Decision: KILL → Not worth 4 more weeks

That kill decision saved me at least four months of working on something users didn't want. The habit tracker I started instead? It's now generating revenue.

How the Hub Makes This Actually Work

I tried to do portfolio reviews with spreadsheets and notion databases before. It was a nightmare. Everything was out of sync, I'd forget to update scores, and the reviews took forever.

The Hub changed everything because it makes the data visible and up-to-date automatically:

Friday Review Dashboard:
📊 Habit Tracker (Score: 32/40 ⭐⭐⭐⭐⭐)
Verdict: ✅ PROCEED
Validation: 7/7 docs ✅
📊 Meal Planner (Score: 22/40 ⭐⭐⭐)
Verdict: ⚠️ PIVOT (behind pace)
Validation: 5/7 docs (results weak)
📊 Freelancer PM (Score: 28/40 ⭐⭐⭐⭐)
Verdict: (pending Opp Score)
Discovery: 3/4 docs

I can see at a glance:

  • Score + stars: Priority level (30+ = top, 20-29 = high, < 20 = kill)
  • Verdict badge: Green (proceed), yellow (pivot), red (kill)
  • Doc completion: Progress tracking (3/4 discovery, 7/7 validation)
  • Filters: Click "Pivot" to see all struggling ideas instantly

No spreadsheets to maintain. No memory required. No debate about facts, the scores and verdicts are canonical.

The Mental Models That Make Killing Ideas Easier

Even with a good system, killing ideas you've worked on is emotionally difficult. Here are the mental models that help me pull the trigger:

1. "What Would I Do If I Started Today?"

If I had zero investment in this idea, would I start it now given what I know?

This cuts through the sunk cost fallacy instantly. For the meal planner, the answer was crystal clear: knowing that this idea would take four more weeks and deliver 500 signups at 4% conversion, would I start it? Hell no. I'd start the fintech SaaS instead.

2. "Opportunity Cost is Real Cost"

Every hour on Idea A is an hour not on Idea B.

Opportunity Cost Formula:

Cost of continuing A = (Expected Value of B - Expected Value of A) × Time

Meal planner: 10% × $50K = $5K EV, needs 6 months

Habit tracker: 40% × $150K = $60K EV, needs 6 months

Opportunity cost: ($60K - $5K) × 6 months = $55K foregone

When you frame it like that, the decision becomes obvious.

3. "Celebrate Kills as Wins"

This one was huge for me. I started treating kills as wins, not failures.

When I killed the meal planner, I tweeted: "Killed the meal planner today. Saved 4 months. Starting habit tracker next week." The response was overwhelmingly positive, other founders respected the decision.

Killing bad ideas is a win. It's evidence of good judgment, not failure.

Real-World Results (6 Months Later)

Since implementing weekly kill/greenlight reviews, here's what's happened to my portfolio:

Portfolio Health

  • Started: 23 ideas (many mediocre)
  • Killed immediately: 6 (score < 20)
  • Killed after discovery: 3 (Opp Score < 8.0)
  • Killed after validation: 2 (missed thresholds)
  • Greenlit for build: 4
  • Current: 16 ideas, 7 proceed, 9 pivot/killed

Business Impact

  • Time saved: ~44 months of wasted effort avoided
  • Success rate: 75% (vs. 10% industry average)
  • Zero regrets about killed ideas
  • Zero zombie projects consuming resources

The numbers don't lie. Systematic portfolio management works.

How to Implement This (Starting Monday)

Alright, let's get practical. Here's exactly how to add this to your workflow:

Step 1: Define Your Kill Criteria

Write down clear, non-negotiable kill criteria and make them visible (pin in Slack, print on wall, whatever works):

  • Portfolio phase: Score < 20/40 → Kill immediately
  • Discovery phase: Opportunity Score < 8.0/10 → Kill or pivot
  • Validation phase: Miss thresholds by >30% → Kill or pivot
  • Build phase: Shipping delays > 2x estimate → Kill or descope

Step 2: Schedule Weekly Reviews

Pick a time (I use Friday 4 PM) and set a recurring calendar event: "Portfolio Review" (30-60 min).

The format:

  1. Review active ideas (greenlight / pivot / kill)
  2. Review backlog (promote / keep / kill)
  3. Triage new ideas (start / backlog / kill)
  4. Update verdicts in your system
  5. Share decisions (if you have a team)

Step 3: Document Every Kill

When you kill an idea, write why in your project docs:

Example Kill Documentation:
### Verdict: ❌ **KILL** Rationale: - Opportunity Score: 7.2/10 (below 8.0 threshold) - Validation: 200/500 signups (40%), 4%/10% prepayment - Founder conviction: Low (forcing myself to work on this) - Decision: Not worth 4 more weeks. Moving to higher-EV idea. Date: 2025-12-02

Six months later, you'll remember exactly why you killed it. Prevents re-litigating the same decision.

The Trade-offs (Let's Be Honest)

Systematic portfolio management isn't free. Here's what it costs:

Requires Real Discipline: It's easy to skip reviews when you're busy or rationalize "one more week" instead of following kill criteria.

Can Feel Harsh: Killing ideas you've invested in is emotionally hard. If you have a team, they might be attached to ideas you need to kill.

Takes Time: 30-60 minutes per week on reviews is time not spent coding. For solo founders in pure sprint mode, it might feel like overhead.

If you're managing 3+ ideas at various stages, reviews pay for themselves immediately. The time you save by not working on dead-end projects more than makes up for the review time.

What's Next?

I'm continuing to refine the kill/greenlight process. Next improvements on my list:

  • Automated kill alerts: "Meal planner is 50% behind pace, schedule kill review"
  • EV calculator: Input scores/validation → Get expected value comparison
  • Kill lessons database: Extract patterns from killed ideas to spot failure modes earlier

But the core system is solid. Weekly reviews + clear kill criteria + visible data = better decisions.

The Bottom Line

Most founders can't kill ideas because of sunk costs, identity attachment, and optimism bias. The result? Zombie projects that consume resources without delivering results.

The solution isn't more discipline, it's better systems. Weekly kill/greenlight reviews with clear criteria and visible data make tough decisions easier.

The Killer Insight:

Killing bad ideas isn't about admitting failure, it's about protecting your ability to recognize and execute on exceptional opportunities.

If you're managing multiple ideas, start with this: schedule a weekly review, define clear kill criteria, and make one tough decision this Friday. Your future self will thank you.

What if you could kill bad ideas confidently and focus all your energy on the ones that actually matter? That's how you build something that lasts.

Want the Kill/Greenlight Framework?

I've documented the exact process, criteria, and templates I use for weekly portfolio reviews. Get the complete framework and start making better decisions about your ideas.

Framework TemplateKill Criteria ChecklistHub Integration Guide

Get AI-Augmented Insights in Your Inbox

Strategic frameworks, case studies, and lessons learned from building AI-native products. No fluff, just actionable insights for VCs and executives.

Weekly insights. Unsubscribe anytime.