What's an MVP (and What to Cut)
You've got a notebook full of ideas for what your app should do. Here's the hard truth that will save you weeks: you don't build all that yet. You build the smallest piece that proves the whole thing is worth it.
An MVP — Minimum Viable Product — is the smallest version that actually delivers your core value. "Viable" is the key word: it has to genuinely help someone, not just be a half-finished sketch. Think one sharp knife, not a whole crowded kitchen drawer.
Find the ONE thing
Every idea has a beating heart — the single job it absolutely must do. A scheduling app must let someone book a time. A check-in tool must let a client log how their week went. Everything else is decoration.
Ask yourself: if it only did one thing, what would make it still worth using? That's your MVP. Write it in a single sentence. If you can't, keep cutting until you can.
What to cut for version 1
Almost everything. For v1, be ruthless and cut:
- Logins and accounts — until you've proven people want the thing
- Settings and customization — pick one sensible default
- The "nice to have" list — every "wouldn't it be cool if..." waits
- Polish — pretty comes after useful
You're not deleting these ideas. You're parking them on a "later" list where they're safe.
One big exception: cut polish, not protection. If your app touches personal data or takes payments, then logins and basic security aren't "nice to have" — they belong in v1. The moment real people trust you with their info or their card, you owe them a locked front door. So cut features, cut frills, cut customization — but never cut the protection that keeps people's data safe.
Why small beats big
A small thing you can actually use this week teaches you more than a perfect plan you stare at for a month. Real people touching a real tool tell you what's wrong faster than any amount of thinking. Shipping small isn't lowering your standards — it's how you find out what's actually worth your standards.
The feature creep trap
Feature creep is when "just one more thing" quietly turns a two-week build into a six-month swamp. It feels productive. It isn't. Every feature you add before launch is a bet you're making without proof — and one more place something can break. When you catch yourself saying "while we're at it...", stop. Park it.
▶️ Try this
Take your app idea and write its core value in one sentence: "This lets [who] do [the one thing]." Then list three features you're tempted to include — and move all three to a "later" list. That sentence is your MVP. Everything else can wait.