Scope Creep (Death by "But What About...")
The Problem
Falling into the trap of endless possibilities and distractions. It's easier to list everything you could do than focus on what truly matters. The constant "but what about..." questions pile up: adding more metrics, covering more areas, adding data sources, real-time requirements, new AI ideas. Scope creep infects not just the solution you're building, but also the metrics you measure, the data in your warehouse, your strategy, and your personal and professional goals.
The Principle
Do less! Focus on fewer things and scale them further. Maximize the value of what you choose to do. Simplify to amplify. The next time you hear "but what about..." (or worse, say it yourself), be damn sure you want to add that nugget into what you're up to. Protect your scope like a product manager protects their roadmap—ruthlessly prioritize what creates the most value and say no to everything else.
3 Steps to Take Action
- 1
Write Down the Scope: Before starting anything, write exactly what's in scope and what's out of scope. Get stakeholder sign-off. Post it where everyone can see it.
- 2
Implement the "Scope Freeze": After requirements are signed, freeze scope for sprints/iterations. New ideas? Add to backlog for v2. Protect the current scope ruthlessly.
- 3
Track Scope Change Requests: Every time someone says "but what about...", log it. Review monthly: How many scope changes were requested? How many approved? If it's >20%, tighten discipline.
In Practice
A data science team started building a customer churn model. "But what about adding 50 more features?" "But what about predicting lifetime value too?" "But what about real-time scores?" Six months later, still no model in production. They reset: focused on 10 core features, basic batch predictions, single use case. Shipped in 3 weeks. Model prevented $2M in churn. Then they added features one at a time based on actual impact. Two years later, that focused v1 beat the "kitchen sink" approach they'd abandoned—and it was already generating value for 18 months while the bloated version would still be in development.
