Product glossary
The language of modern product teams.
Clear, citable definitions of the concepts, metrics and methodologies that run product orgs — written by the team building the product operating system. Filter by type; each term links to a full explainer.
-
Connected vs Consolidated Product Stack
A connected stack keeps specialist tools and joins their data on a shared spine; consolidation replaces them. Connection scales better because it follows the work, and because the thing worth consolidating was never the tool list. It was the record.
Read → -
Customer 360 (Account 360)
A Customer 360 is only genuine when revenue, usage, support, and in-progress work are joined at the data level — not when they are displayed in separate tabs that happen to share a customer name.
Read → -
Product Operating System
A product operating system replaces the stitching between tools, not the tools themselves. Customers, revenue, feedback and work sit on one record, so "who asked for this and what do they pay" is a field rather than an investigation.
Read → -
Product Spine
A spine is the third path between integrating tools and replacing them: one shared layer that every module reads and writes, so the customer, the revenue, the request and the task are the same record rather than four systems kept roughly in sync.
Read → -
Product-Led Growth (PLG)
Product-led growth lets the product itself acquire, activate, and expand users through self-serve onboarding — it scales by improving the product experience rather than by hiring more sales reps, and it fits products that deliver value to a single user fast.
Read → -
Product-Market Fit
Product-market fit is when a defined segment retains, refers, and pulls harder than you push — and you measure it with retention curves and the Sean Ellis 40% test, not vanity sign-ups.
Read → -
Single Source of Truth for Product
A single source of truth is not about owning fewer tools. It is about customer, revenue, feedback and work records being joined in one authoritative layer, so every decision in the room reads the same data instead of a personal export of it.
Read → -
Dual-Track Agile
Dual-track agile is two parallel tracks — discovery to validate what to build, delivery to build it well — owned by one team feeding one backlog, not two separate teams handing work over a wall.
Read → -
ICE Scoring
ICE ranks initiatives fast by multiplying Impact, Confidence and Ease. Confidence is the lever most teams waste: anchor it to real evidence and the score becomes a decision, leave it at gut feel and it becomes decoration.
Read → -
Jobs To Be Done (JTBD)
Jobs To Be Done shifts the unit of analysis from who the customer is to the progress they are trying to make, so teams build for real situations of need rather than idealized personas or feature lists.
Read → -
OKRs (Objectives and Key Results)
OKRs align teams by pairing one ambitious Objective with measurable Key Results — but they only work when Key Results track outcomes, not outputs, and grading stays decoupled from performance reviews.
Read → -
Opportunity Solution Tree
An opportunity solution tree turns a desired outcome into a branching map of customer opportunities, solutions, and experiments, so every build decision traces back to a real need and a measurable goal.
Read → -
Revenue-Weighted Prioritization
Revenue-weighted prioritization replaces a subjective impact score with the ARR of the accounts actually asking. It is one input rather than a veto on platform work, and it only functions when feedback, accounts and billing are the same record.
Read → -
RICE Scoring
RICE ranks unlike bets on one scale, and it is only as defensible as its inputs. Reach, Impact and Confidence are lookups against real usage, real outcomes and real customer evidence, not positions in an argument.
Read → -
RICE vs WSJF
RICE ranks by output potential over effort and suits discovery; WSJF ranks by economic cost of delay over duration and suits program sequencing. Pick by planning cadence, then spend your effort making the inputs real rather than switching frameworks.
Read → -
WSJF (Weighted Shortest Job First)
WSJF sequences by value per unit of time, making Cost of Delay an explicit part of every decision rather than a background assumption. Its honesty depends entirely on whether that Cost of Delay is measured or invented.
Read → -
Activation Rate
Activation rate measures how many new users reach a defined first-value moment inside a set window, and it is the highest-impact early signal in the funnel. Report the event and the window with the number, or the percentage means nothing.
Read → -
Net Revenue Retention (NRR)
NRR tracks how much recurring revenue a fixed cohort of existing customers generates over time — expansion minus contraction and churn — and crossing 100% is the line between a base that shrinks and one that compounds on its own.
Read → -
North Star Metric
A North Star Metric is the single leading indicator of delivered customer value that a whole team optimizes toward — not a revenue number, and never a vanity count like total signups.
Read → -
Build vs Buy Product Stack
Buy commodity tooling and reserve engineering for what differentiates the product. Then count integration debt honestly: five bought tools plus the connectors you wrote yourself is a build with a SaaS invoice on it.
Read → -
Continuous Discovery
Continuous discovery turns research from a periodic project into a weekly habit. It only compounds when the insight stays attached to the account that gave it and to the work it eventually produced.
Read → -
Feedback-to-Revenue
Feedback-to-revenue closes the loop between what customers ask for and what building it was worth, by keeping feedback, product work and revenue on one traceable chain. A vote count with no revenue behind it is noise wearing a number.
Read → -
Now-Next-Later Roadmap
A Now-Next-Later roadmap trades false date precision for honest confidence horizons — communicating sequence and intent around outcomes, so changing plans read as progress rather than missed deadlines.
Read → -
Product Analytics vs Web Analytics
Web analytics tells you how people find and browse your site; product analytics tells you whether users get lasting value from what you built — and product teams need both, joined at the user level, to make sound decisions.
Read →
Stop reading about it. Run it.
Every concept here is something AIOProductOS makes real on one shared spine — connectors included, no per-connector fee, flat plans from $199/mo, every module included. Every plan starts with a 14-day onboarding runway on your own data.
FAQ