Cupcakes vs. Skateboards: How to Scope a Smart MVP
1. The Pitfall of a Feature-Only MVP
When an MVP meant to quickly validate a hypothesis is reduced to a “barely working bundle of features,” the experience users actually feel becomes difficult to verify.
- Users experience convenience, trust, and delight within a flow, not in a list of features
- Minimum Viable Delight (MVD) is not a finishing-stage decoration, but the minimum level of experience that should remain even in an early product
- Small details shape the impression of a product and add differences that are difficult to replicate with features alone
2. The Layers of Experience Divided by the Kano Model
Because not every feature contributes to satisfaction in the same way, what to keep needs to be distinguished according to its nature.
- Basic features: elements that cause dissatisfaction if absent, but do not create great satisfaction even when present
- Performance features: elements whose satisfaction rises together as the quality or level of provision increases
- Delighters: elements that create positive emotions in unexpected moments
- Experiences like Duolingo’s mascot animation or Slack’s witty loading messages help memory, revisits, and word of mouth with little implementation
3. Cupcakes Rather Than Skateboards
Rather than first shipping only the skeleton of a feature and adding UX later, this is a way of designing a micro experience that is complete from start to finish even if the scope is small.
- A cupcake is smaller than a whole cake, but it fully contains the structure of taste, form, and satisfaction
- Even in MVP scoping, reduce the number of screens or features while preserving the core flow and emotional quality together
- The decision criterion is “which experience to leave complete” rather than “how much to remove”
4. Manage Delight with Priorities and Metrics
MVD does not remain at the level of sensory finishing; it can be connected to important customer touchpoints and validation metrics.
- Reduce friction first in flows that directly affect drop-off and customer lifetime value, such as onboarding, payment, and error recovery
- Verify the effect of small UX improvements through behavioral metrics such as task completion rate, drop-off rate, and revisit rate
- If you first place the hypotheses to validate and the core touchpoints rather than a feature list, it becomes easier for PMs, designers, and developers to align scope using the same criteria
