ProductOSDocs
Sign in

PM Academy

PM Glossary

Every product-management term ProductOS uses, defined in one line each, plus why it matters when you're building solo.

You don't need a PM title to do product management, you need the vocabulary. This page defines every term ProductOS puts in front of you, in one line each, with the founder's reason to care.

These are the same definitions the in-app info dots and the PM Coach use, rendered from one registry: when a definition improves, it improves everywhere at once.

The Golden Thread

Golden Thread
The traceable line from a user complaint to a measured result: feedback → themes → features → initiatives → releases → outcomes.
Why it matters: It's the difference between “I build what's loud” and being able to show why every line of code exists.
Where it lives: /golden-thread
Feedback
One raw signal from one user: a request, complaint, or bug, captured before it evaporates.
Why it matters: Your gut is one data point; feedback is everyone else's. Capture it the moment it lands or lose it.
Where it lives: /feedback
Theme
A cluster of related feedback that reveals a pattern.
Why it matters: Ten people asking for “export” isn't ten problems, it's one. Themes stop you fixing symptoms one ticket at a time.
Where it lives: /themes
Feature
A specific capability you build to address a theme.
Why it matters: The unit you actually ship. Tying it back to a theme keeps you honest about who asked for it.
Where it lives: /features
Initiative
A strategic bet that groups features toward one outcome, with a hypothesis.
Why it matters: Stops feature-factory mode, you state what you expect to change, not just what you'll build.
Where it lives: /initiatives
Release
The bundle of work that ships together, with a version and a date.
Why it matters: Shipping becomes a discrete event you can announce, measure, and roll back, not a vague “it's live.”
Where it lives: /releases
Outcome
The measured result after shipping: did the metric move?
Why it matters: Building is the easy half. Outcomes tell you whether the bet paid off, and what to do next.
Where it lives: /outcomes

Craft

Discovery vs. Delivery
Discovery is deciding what's worth building; delivery is building it well.
Why it matters: Founders over-index on delivery and skip discovery, then build the wrong thing fast.
Where it lives: /feedback
Prioritization
Deciding what to do next when you can't do everything.
Why it matters: There's one of you. Choosing wrong for a month costs a month you don't get back.
Where it lives: /features
RICE
A scoring model: Reach × Impact × Confidence ÷ Effort.
Why it matters: A cheap way to argue with yourself objectively instead of chasing the shiniest idea.
Where it lives: /features
Effort / Impact
Rough sizing of cost (xs–xl) against value, often drawn as a 2×2.
Why it matters: High impact, low effort is where a solo founder lives. This names the quadrant.
Where it lives: /features
Roadmap
The sequenced plan of what's coming: usually Now, Next, Later.
Why it matters: Your promise to yourself and customers about order. Replaces the 40-tab browser.
Where it lives: /roadmap

People & money

Persona
A named archetype of a user, with goals and pain points.
Why it matters: Forces “who is this for?” before you build, and stops you building for yourself by accident.
Where it lives: /personas
Account
A customer organization, with ARR, health score, and churn risk.
Why it matters: In B2B, ten users at one account isn't ten accounts. An account is revenue at stake.
Where it lives: /accounts
ARR
Annual Recurring Revenue, the yearly value of your subscriptions.
Why it matters: The number you and investors actually track. It ties product work to money.
Where it lives: /accounts
Churn
The rate at which customers leave.
Why it matters: You can't out-acquire a leaky bucket. Churn quietly kills early SaaS.
Where it lives: /accounts

Strategy

Vision
The long-term world you're trying to create.
Why it matters: Your north star when every option looks reasonable. Cuts decisions in half.
Where it lives: /strategy/vision
Mission
What you do today, for whom, to move toward the vision.
Why it matters: The vision is the destination; the mission is the vehicle.
Where it lives: /strategy/vision
OKRs
Objectives say what you want; Key Results say how you'll measure progress.
Why it matters: Turns “grow the business” into three numbers you can check on a Friday.
Where it lives: /strategy/okrs
SWOT
Strengths, Weaknesses, Opportunities, Threats: a snapshot of where you stand.
Why it matters: A 20-minute honesty exercise that surfaces what you're avoiding.
Where it lives: /strategy/swot
Positioning
The category you claim and who you're the obvious choice for.
Why it matters: “For X who need Y, we are the Z that…”, if you can't fill it in, neither can your customer.
Where it lives: /strategy/positioning
Pricing
How you package and charge for value.
Why it matters: The fastest lever on revenue, and the one founders touch least.
Where it lives: /strategy/pricing

Intelligence

Competitor
Another option your buyer is considering, including doing nothing.
Why it matters: You're never compared in a vacuum. Knowing the alternative sharpens your pitch.
Where it lives: /intelligence/competitors
Battle card
A one-pager on how to win against a specific competitor.
Why it matters: When a prospect says “but X does Z,” you need the answer ready, not next week.
Where it lives: /sales/battle-cards

Go-to-market

Go-to-market (GTM)
How a thing reaches and convinces customers: launch, message, channel.
Why it matters: A great feature nobody hears about is a tree falling in a forest. GTM is the second half of shipping.
Where it lives: /gtm/launches
Messaging
The words that translate a feature into a benefit a buyer feels.
Why it matters: “We added webhooks” vs. “connect to anything in 5 minutes.” Same feature, different sale.
Where it lives: /gtm/messaging
Channel
A path to reach customers: content, paid, community, partners.
Why it matters: You can't do all ten. Naming them forces you to pick one or two and go deep.
Where it lives: /gtm/channels

Statuses

Discovery (status)
Still validating the problem and sketching the solution, not committed to build.
Why it matters: Cheap to kill, expensive to skip. Time here saves a build you'd regret.
Under review (status)
Captured and being evaluated, no decision yet.
Why it matters: An explicit triage state keeps the inbox honest, nothing rots unread.
Planned (status)
Committed to build, not yet started.
Why it matters: The difference between a backlog and a wish list.
In progress (status)
Work in flight right now.
Why it matters: If too much sits here at once, nothing ships.
Shipped (status)
Live for users.
Why it matters: The question changes from “will it work?” to “did it?”, go check the outcome.
Won't do (status)
A deliberate, recorded no.
Why it matters: Saying no out loud beats letting tickets rot politely.
At risk (status)
Tracking behind plan badly enough that the target date is in danger.
Why it matters: An early flare, not a failure. Raising it now is what makes the date save-able.

Last reviewed 2026-09-22