User Story
A short sentence describing a feature from the user's point of view. It follows the pattern: As a [user type], I want to [action], so that [benefit].
Acceptance Criteria
The specific conditions that must be true for a feature to be considered done. They remove ambiguity between what was built and what was wanted.
MVP
Minimum Viable Product. The smallest version of a feature or product that delivers real value and can be tested with real users.
Jobs To Be Done
A framework that asks what job a user is hiring a product to do. It focuses on the outcome they want, not the features they use to get there.
Product-Market Fit
The point where a product genuinely satisfies demand in a real market. Users come back, tell others, and would be upset if it disappeared.
North Star Metric
One metric that best captures the value your product delivers to users. Every team decision points back to moving this number.
Dogfooding
Using your own product internally before releasing it. It surfaces problems that real users would find, from people who have the power to fix them.
Feature Flag
A switch that turns a feature on or off without deploying new code. It lets you release to a small group first or roll back instantly if something breaks.
Onboarding Flow
The sequence of steps a new user takes when they first use a product. A good onboarding flow gets users to their first success as fast as possible.
Call To Action
A button, link, or prompt that tells the user exactly what to do next. It should be specific, direct, and impossible to miss.
User Flow
A diagram or description of every step a user takes to complete a specific task. It shows where they start, every decision they make, and where they end up.
Edge Case
A scenario that happens at the extreme limits of normal use. Edge cases break products that were only tested against the happy path.
Building toward a role? Browse career pathways that map terms to jobs.