A/B Test
An A/B Test randomly assigns eligible people or items to versions. It compares a chosen measure to estimate cause and effect.
↗Product
Learn who needs help, what problem to solve, what success looks like, and what to try first.
01 / Atlas
All Product terms
Open a term for a simple meaning, an example, when to use it, how official it is, and its code name.
-
01 · More detail -
02 · Core Acceptance Criteria
Acceptance Criteria are results people can see and test. They say when a feature works well enough to accept.
↗ -
03 · More detail Conversion Funnel
A Conversion Funnel is a set of steps you can measure. It shows where people move forward or leave before reaching a goal.
↗ -
04 · More detail Feature Prioritization
Feature Prioritization is a steady way to order work by value, proof, cost, and risk.
↗ -
05 · More detail Gantt Chart
A Gantt Chart shows scheduled work as bars across time. It can show duration, dependencies, dates, owners, and progress.
↗ -
06 · More detail Jobs to Be Done
Jobs to Be Done describes the progress a person wants in a real situation. The product is the tool they choose for that job.
↗ -
07 · Core Key Performance Indicator
A Key Performance Indicator, or KPI, measures an important result over a set time. It must help someone make a decision.
↗ -
08 · Core Minimum Viable Product
A Minimum Viable Product (MVP) is the smallest complete product that tests the biggest value risk. Real users must be able to use it.
↗ -
09 · Core Onboarding Checklist
An onboarding checklist lists the first useful tasks for a new person. Clear status shows what is done and what comes next.
↗ -
10 · More detail Persona
A Persona is a research-based user type. It sums up goals, habits, and limits that appear again and again.
↗ -
11 · Core Problem Statement
A Problem Statement says who has a problem, when it happens, and why solving it matters.
↗ -
12 · Core Product Backlog
A Product Backlog is an ordered list of changing work. It can hold ideas, fixes, learning, and technical duties.
↗ -
13 · Core Product Goal
A Product Goal states the useful result a product should create for users or the business.
↗ -
14 · Core Product Requirements Document
A PRD records key choices for a product change. It covers the problem, users, goals, scope, limits, risks, and success proof.
↗ -
15 · More detail Product–Market Fit
Product–Market Fit means a clear market keeps choosing, valuing, and paying enough for the product.
↗ -
16 · More detail Retention
Retention is the share of a group that returns for useful activity after a set time.
↗ -
17 · More detail Roadmap
A Roadmap is an updated view of product goals, planned bets, and their order. It's not a promise of exact dates.
↗ -
18 · Core Scope
Scope marks what a project will deliver now and what it will leave out.
↗ -
19 · Core Target User
A Target User is the clear group whose needs and limits guide the first product choices.
↗ -
20 · Core Use Case
A Use Case shows how an actor reaches a goal with a system. It includes main, alternate, and failed paths.
↗ -
21 · Core User Flow
A User Flow maps the screens, choices, and replies on the way to a result.
↗ -
22 · Core User Story
A User Story is a short sentence. It names a user, a needed task, and why it helps.
↗