---
summary: "Five-question checklist to evaluate every Orbit product change: requester clarity, approver context, supplier onboarding ownership, PO accuracy, and CS rollout visibility."
usage_mode: auto
sort_order: 0
tags:
  - product
  - policy
  - orbit
refs:
  - orbit-company-overview
  - sales-ops-cs-handoff-process
---

## Product Review Checklist

**Source:** Notion - Product & Customers, last edited 2026-05-07

---

## Policy

Every product change must be evaluated against all five questions before shipping. A "no" on any question is a blocker unless explicitly waived by the accountable lead with a written rationale.

## The Five Questions

| # | Question | What a "no" means |
|---|---|---|
| 1 | **Does a first-time requester know what to do next?** | The requester experience is unclear or requires prior knowledge not surfaced in the UI. |
| 2 | **Can an approver make a decision without missing context?** | The approver is missing information needed to approve or reject confidently. |
| 3 | **Is supplier onboarding assigned to a named person, not a queue?** | Supplier onboarding has no clear owner and will stall. |
| 4 | **Does the PO reflect the approved request?** | There is a mismatch between what was approved and what the PO captures. |
| 5 | **Can Customer Success detect a stuck rollout after week two?** | CS has no signal to identify customers who are not progressing past initial setup. |

## Usage

- Use this checklist in product reviews, design critiques, and pre-launch readiness checks.
- Questions 1–2 are requester/approver experience checks.
- Question 3 is a supplier onboarding ownership check.
- Question 4 is a PO accuracy check.
- Question 5 is a post-launch CS visibility check.

---

See also: [[orbit-company-overview]], [[orbit-product-design-principles]], [[sales-ops-cs-handoff-process]]
