MVP and Product Design Basics

What This Is

This guide helps you turn a big project idea into a small, buildable first version (an MVP).

MVP means Minimum Viable Product:

  • Minimum: smallest useful version
  • Viable: actually works for a real user
  • Product: solves one clear problem

Why This Matters

Most student projects fail because the idea is too big, not because the student is not capable.

A good MVP helps you:

  • start quickly
  • finish something real
  • learn faster from feedback
  • avoid wasting time on extra features too early

Core Concepts

1) Ideation

Ideation means generating project ideas and selecting one worth building now.

A strong idea usually has:

  • a clear user
  • a clear problem
  • a clear first outcome

Quick filter:

  • Do I care about this problem?
  • Can I explain it in one sentence?
  • Can I build a useful first version in 1-2 weeks?

2) Elevator Pitch

An elevator pitch is a short 2-3 sentence description of your idea.

Template:

I am building [product] for [user] who struggles with [problem]. My MVP helps them [outcome] by [core approach].

Example (sports):

I am building a shot-tracker for high school basketball players who forget what shots they practiced. My MVP helps them log daily shot attempts and see simple weekly totals.

Example (non-sports):

I am building a homework planner for students who feel overwhelmed by large assignments. My MVP helps them break tasks into daily steps with due-date reminders.

3) User Stories

User stories keep features focused on user value.

Template:

As a <type of user>, I want <action>, so that <benefit>.

Examples:

  • As a student athlete, I want to log my workouts, so that I can see consistency over time.
  • As a student, I want to split a project into small tasks, so that I stop procrastinating.

Tip:

  • If a feature cannot be written as a user story, it may be too vague.

4) MVP Scope

Your MVP should solve one core problem, not every possible problem.

Use this scope split:

  • Must Have: required for MVP to be useful
  • Nice to Have: useful later, not required now
  • Not Now: explicitly out of scope

Example:

Project: Study Planner

  • Must Have:
    • add assignment
    • set due date
    • show daily task list
  • Nice to Have:
    • color themes
    • calendar sync
  • Not Now:
    • mobile app
    • group collaboration

5) Success Criteria

Success criteria are checks that prove your MVP works.

Good criteria are specific and testable.

Examples:

  • "Given a new assignment, user can save it without errors."
  • "App shows tasks due today in one view."
  • "User can mark a task complete and it stays completed after refresh."

Step-by-Step: Define Your MVP

  1. Write your project idea in one sentence.
  2. Define one target user.
  3. Define one main problem.
  4. Write 3-5 user stories.
  5. Select 3-5 must-have features only.
  6. Write a "Not Now" list.
  7. Add 3-5 success criteria.

If it still feels too big, remove one feature and test again.

Examples: Big Idea vs MVP

Example A: Sports Recruiting Platform

  • Big idea:
    • profiles, messaging, highlights, coach dashboard, analytics
  • MVP:
    • athlete creates profile
    • uploads one highlight link
    • exports shareable profile page

Example B: AI Recipe App

  • Big idea:
    • meal plans, shopping lists, nutrition tracking, social sharing
  • MVP:
    • user enters ingredients
    • app returns one recipe suggestion
    • user saves favorite recipe

Example C: Study Companion

  • Big idea:
    • planning, flashcards, AI tutor, reminders, analytics
  • MVP:
    • user adds assignment
    • app breaks into subtasks
    • app shows "today's plan"

Common Mistakes to Avoid

  • Building for "everyone" (no clear user)
  • Writing vague goals ("make it cool")
  • Choosing too many must-have features
  • Skipping "Not Now" list
  • No testable success criteria

Quick Copy/Paste Worksheet

## Elevator Pitch

I am building ...

## Target User

...

## Main Problem

...

## User Stories

- As a ..., I want ..., so that ...
- As a ..., I want ..., so that ...
- As a ..., I want ..., so that ...

## Must-Have Features

- ...
- ...
- ...

## Not Now

- ...
- ...

## Success Criteria

- ...
- ...
- ...

If you can explain your MVP in plain language, with clear user stories and clear success checks, you are ready to build.