You've been thinking about this for years. That's a problem.

Mindset · 6 min read

The clients who come to me with the clearest vision are usually the hardest to work with on scope. Not because they're difficult people. Because they've had years to think about every detail. Every feature. Every edge case. Every "what if." They've built the entire app in their head, and by the time they sit down with me, it's a fully-formed product with fifty screens and three user types.

That's not a starting point for an MVP. That's a roadmap for version five. And the gap between what they've imagined and what we should actually build first is where most of the tension in the design process lives.

Why long ideas get bloated

When you've been thinking about something for a long time, you keep adding to it. You see a competitor and think "mine should do that too." You read an article and think "that feature would be perfect." You're in the shower and think "what if users could also..." Every new thought gets added to the pile. Nothing ever gets removed. The idea only grows.

By the time you're ready to build, the idea doesn't feel optional. Every feature feels essential because you've spent so long justifying it in your head. You've imagined users relying on it. You've thought about how it connects to everything else. Cutting it feels like amputating a limb, not removing a feature.

But here's what I've learned from every project I've worked on: the features you've been thinking about the longest are often the ones your users care about the least. Because you've been thinking about features. Your users are thinking about problems. They don't care about your feature list. They care about whether the app does the one thing they downloaded it for.

The emotional weight of cutting

Scope conversations with long-term thinkers are emotional. I'm not exaggerating. I've sat in meetings where cutting a feature felt like a personal loss to the client. They've lived with this idea. They've told their partner about it at dinner. They've imagined the moment a user discovers this feature and thinks "this is brilliant." Removing it feels like giving up on a piece of themselves.

I get it. I really do. But the truth is, you haven't lost that feature. You've deferred it. And if you're serious about this product, you'll build it eventually. But not yet. Not until the core works. Not until people are using it. Not until you have data that tells you whether the feature you've been dreaming about is the feature your users actually want.

Phase two is not a graveyard. It's a holding pen for good ideas that need more time, more budget, and more evidence.

How to let go without losing the plot

First, write everything down. Every feature, every idea, every late-night brainwave. Get it out of your head and into a document. Not so you can build it all. So you can see it all at once and start making decisions about what's first.

Second, separate the problem from the feature. For every item on that list, ask: "What problem does this solve?" If the answer is vague, it's not ready. If the answer is clear, ask the next question: "Is this problem urgent enough that the app fails without solving it?" If yes, it's in the MVP. If no, it waits.

Third, trust the process. I know that sounds like something a yoga instructor would say. But the MVP approach has been validated by every successful product company in existence. None of them shipped version five first. They shipped version one, learned from it, and built from there. Your years of thinking aren't wasted. They're banked. You'll use all of it. Just not all at once.

Sources
The Lean Startup (Eric Ries) - Building iteratively based on validated learning rather than upfront planning.
Fix Time and Budget, Flex Scope (Basecamp) - Constraints drive better product decisions.

Related blog posts:

Self-funding your app →

When your family thinks you're wasting money →

What if nobody downloads it? →