Every developer knows the pain: 47 project folders collecting dust, each one a monument to good intentions and poor execution. Research shows the average developer maintains 3.7 unfinished side projects with completion rates hovering at a dismal 15-20%. The problem isn't your lack of time, motivation, or skill—it's that you've never learned to negotiate with yourself about what "done" actually means.

The Kill List Framework is a structured approach to murdering your darling ideas before they murder your project's chances of completion. This talk cuts through the perfectionism and scope creep that silently kill more projects than all technical debt combined, providing a battle-tested system for shipping real products instead of maintaining eternal works-in-progress.

Drawing from lessons learned shipping 6+ projects in the last few years—many embarrassingly simple but all actually completed—this session provides a practical, no-nonsense approach to transforming your project graveyard into a shipped portfolio. You'll leave with actionable frameworks you can implement immediately, including a 30-day sprint structure, energy management strategies, and a systematic approach to defining "done" before writing a single line of code.
This isn't motivational fluff—it's applied violence for project survival.

Key Takeaways :

The Kill List Framework - A structured 4-tier categorization system (MUST/SHOULD/COULD/WON'T-HAVE) to ruthlessly prioritize features and prevent scope creep with maximum 3 must-have features for MVP.

The Done Contract - How to define completion before coding begins, creating explicit boundaries that transform endless projects into shippable products within 30 days.

48-Hour Recovery Protocol - A systematic approach to breaking project inertia before it becomes permanent, including specific actions for technical blockers, burnout, and distraction.

30-Day Sprint Structure - Week-by-week breakdown: setup + core feature (Week 1), remaining features (Week 2), integration (Week 3), and launch sequence (Week 4) with feature negotiation strategies
The Boring Tech Principle - Why using familiar, proven technology ships faster than learning cutting-edge frameworks, and when to separate learning projects from shipping projects.

Energy Management over Time Management - How to map high-energy tasks (architecture, debugging) to peak hours and low-energy tasks (documentation, planning) to off-hours for 3x productivity gains.

Two-File Start Strategy - Defeating analysis paralysis by beginning with minimal structure (just index.html + app.js) instead of spending days on perfect architecture that you'll inevitably reorganize.

The Kill List Framework: A Developer's Guide to Actually Finishing Side Projects

Most developers maintain 3.7 unfinished projects with 15-20% completion rates. The problem isn't time or skill—it's never learning to negotiate with yourself about what "done" means. This talk provides a battle-tested system for shipping real products by ruthlessly prioritizing features and killing perfectionism before it kills your project.

Learn 7 actionable frameworks: (1) Kill List—4-tier feature prioritization with max 3 must-haves for MVP, (2) Done Contract—define completion before coding, (3) 48-Hour Recovery Protocol—break inertia before it's permanent, (4) 30-Day Sprint Structure—weekly breakdown from setup to launch, (5) Boring Tech Principle—familiar tools ship faster than shiny frameworks, (6) Energy Management—map tasks to peak/off hours for 3x productivity, (7) Two-File Start—defeat analysis paralysis with minimal structure.

Walk away with templates, a 7-day quick-start challenge, and frameworks to transform your project graveyard into a shipped portfolio. No motivational fluff—just applied violence for project survival.

Target: Junior-mid and maybe senior developers with 2+ unfinished projects who want to ship, not polish eternally.