Module 1

Foundations

Define product stage, user need, scope, acceptance criteria, and launch readiness.

101 minutes across 10 published lessons

Loading progress…

Lessons in This Module

Lesson 1
Prototype, MVP, and Production Product
Understand the purpose, limits, and risk profile of prototypes, MVPs, and production products.
Open Lesson
Lesson 2
Start with the User’s Problem
A user problem is a specific obstacle, cost, delay, or unmet need experienced by an identifiable group in a real situation. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 3
Find the Core Workflow
The core workflow is the shortest complete sequence through which the intended user receives the product's central value. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 4
Features, Requirements, and Assumptions
A feature is a product capability, a requirement states a condition it must satisfy, and an assumption is an unproven belief behind the plan. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 5
Writing Useful Acceptance Criteria
Acceptance criteria are observable conditions used to decide whether a workflow or requirement has been completed correctly. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 6
Reducing Scope Without Removing Value
Scope reduction removes secondary users, variations, integrations, or automation while preserving the product's smallest useful outcome. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 7
Estimating Technical Complexity
Technical complexity is the uncertainty and coordination created by rules, integrations, data, permissions, scale, and operational consequences. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 8
When an MVP Is Ready to Launch
An MVP is ready to launch when its core workflow works for the intended users and its remaining risks are understood, owned, and proportionate. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 9
When Vibe Coding Is No Longer Enough
Vibe coding becomes insufficient when the product's consequences exceed the team's ability to review, test, operate, and explain the generated system. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson
Lesson 10
Preparing an MVP Build Brief
An MVP build brief is a decision record describing the user, problem, core workflow, rules, boundaries, acceptance criteria, and operating expectations. Learn the founder decision, practical evidence, and warning signs that matter.
Open Lesson

Lessons in This Module

Lesson 1

Prototype, MVP, and Production Product

Understand the purpose, limits, and risk profile of prototypes, MVPs, and production products.

Open Lesson

Lesson 2

Start with the User’s Problem

A user problem is a specific obstacle, cost, delay, or unmet need experienced by an identifiable group in a real situation. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 3

Find the Core Workflow

The core workflow is the shortest complete sequence through which the intended user receives the product's central value. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 4

Features, Requirements, and Assumptions

A feature is a product capability, a requirement states a condition it must satisfy, and an assumption is an unproven belief behind the plan. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 5

Writing Useful Acceptance Criteria

Acceptance criteria are observable conditions used to decide whether a workflow or requirement has been completed correctly. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 6

Reducing Scope Without Removing Value

Scope reduction removes secondary users, variations, integrations, or automation while preserving the product's smallest useful outcome. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 7

Estimating Technical Complexity

Technical complexity is the uncertainty and coordination created by rules, integrations, data, permissions, scale, and operational consequences. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 8

When an MVP Is Ready to Launch

An MVP is ready to launch when its core workflow works for the intended users and its remaining risks are understood, owned, and proportionate. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 9

When Vibe Coding Is No Longer Enough

Vibe coding becomes insufficient when the product's consequences exceed the team's ability to review, test, operate, and explain the generated system. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson

Lesson 10

Preparing an MVP Build Brief

An MVP build brief is a decision record describing the user, problem, core workflow, rules, boundaries, acceptance criteria, and operating expectations. Learn the founder decision, practical evidence, and warning signs that matter.

Open Lesson