Product
Product: build the right thing, not just more.
Scope creep, a release that keeps slipping, an MVP that grew into a product. The hardest part of early product work is deciding what not to build. This is where I help founders cut scope back to what actually matters.
- The MVP keeps growing.
- Development is taking too long.
- Not sure which feature comes first.
- App or website for the first version?
- Which metrics actually matter?
Start here
Targeted starting points for this area.
Frameworks for this area
How big should my MVP be?
Most MVPs are at least three times larger than necessary. A decision framework for founders deciding what belongs in v1 and what can wait.
What belongs in version one?
Version one exists to learn. Not to impress. A decision framework for founders deciding what makes the first launch and what waits for version two.
Which feature comes first?
Most roadmap discussions are actually prioritisation problems. A decision framework for founders deciding which feature creates customer value first, and which ones can wait.
Should this be an app?
Many founders assume they need an app. Most actually need a mobile-friendly website. A decision framework for founders weighing native, web and hybrid delivery.
React Native or native?
Cross-platform React Native and Expo ship one codebase across iOS and Android; fully native delivers platform-best UX and deep device access. A decision framework for founders choosing between them.
Which metrics actually matter?
Many founders measure activity. Few measure progress. A decision framework for founders deciding which metrics drive decisions and which ones just fill dashboards.
When to go live
Most startups launch too late. Perfection delays learning. A decision framework for founders deciding whether the product is ready for real customers.
Do you really need to build all of this?
Most MVPs are much larger than they need to be. The faster you learn, the faster you discover what matters.