Communication: 'this roadmap is directional — not a commitment to dates', 'we're de-scoping X to protect Y'
0 / 5 completed
1 / 5
A product manager explains to a new engineer: "We use OKRs to align the team. Each Objective is a qualitative statement of what we want to achieve. Each Key Result is a measurable outcome that tells us whether we got there. We set a confidence score from 0.0 to 1.0 — right now this KR is at 0.4, which means we think there's a 40% chance we'll hit it." What is the difference between an Objective and a Key Result in OKRs?
Objective: a qualitative, inspiring statement of what you want to achieve. It answers "where are we going?" Examples: "Make our API the most reliable in the industry", "Become the go-to data platform for mid-market companies." Key Result: a specific, measurable outcome that signals whether you reached the Objective. Must be a result, not a task. Example KR: "Reduce API p99 latency from 800ms to 200ms." Bad KR (task): "Deploy the new caching layer." OKR vocabulary: Confidence score — a probability (0.0–1.0) of hitting the KR by end of period. 0.5 = on track; <0.3 = at risk; >0.7 = sandbagging. Committed OKR — expected to be achieved 100%; failure is a problem. Aspirational OKR (stretch goal) — 70% achievement = success; designed to push beyond comfort. OKR check-in — weekly or bi-weekly update of confidence scores and progress. KR owner — individual accountable for tracking and moving the KR. In conversation: "Our confidence on the latency KR dropped to 0.3 — we need to escalate the infrastructure blocker."
2 / 5
An engineering manager presents at a quarterly planning: "Our roadmap this quarter has three horizons. Horizon 1 is committed work — shipped features we're supporting and optimising. Horizon 2 is the bets we're actively building. Horizon 3 is exploratory — prototypes we might or might not productise. I want to be clear: the Horizon 3 items are directional, not commitments." What does directional mean in roadmap vocabulary?
Directional: indicates intent and likely direction without constituting a firm commitment. The opposite is committed — work that will be delivered. Roadmap vocabulary: Now/Next/Later — a three-horizon roadmap format. "Now" = committed, in-progress; "Next" = prioritised, likely next; "Later" = directional, exploratory. Horizon 1/2/3 — strategic time horizons: H1 = optimise existing business (0–12 months); H2 = build new growth (12–36 months); H3 = explore future options (3–5 years). Theme-based roadmap — organises work around customer outcomes/themes rather than specific features; avoids over-committing to implementation details. Feature freeze — a deadline after which no new features are added to the release scope. Descope — removing a feature from a release to protect the deadline. In conversation: "The Horizon 3 items help stakeholders understand where we might go — but they're not on the delivery plan."
3 / 5
A senior PM explains prioritisation to the team: "We're using RICE to rank these features. RICE stands for Reach, Impact, Confidence, and Effort. Feature A has Reach=500 users/quarter, Impact=3, Confidence=80%, Effort=2 person-weeks — so its RICE score is 500 × 3 × 0.8 / 2 = 600. Feature B scores 240. We're doing Feature A first." What does Confidence represent in the RICE scoring framework?
RICE score = (Reach × Impact × Confidence) / Effort. RICE vocabulary: Reach — how many users/customers will this affect per period? (people/quarter). Impact — how much does it move the needle per user? (scale: 0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive). Confidence — how certain are you about the Reach and Impact estimates? (100% = high evidence; 80% = medium; 50% = low). Acts as a discount factor for uncertainty. Effort — total person-weeks/months of work. Other prioritisation frameworks: MoSCoW — Must have (non-negotiable), Should have (important), Could have (nice-to-have), Won't have (explicitly out of scope). WSJF (Weighted Shortest Job First) — used in SAFe: Cost of Delay / Job Duration. Prioritises fast-to-deliver items with high cost of delay. Value vs. effort matrix — 2×2 quadrant. "Quick wins" (high value, low effort) first. In conversation: "The confidence score is only 50% because we haven't user-tested the assumption yet — we should validate before committing to Horizon 2."
4 / 5
During backlog grooming, a tech lead says: "This epic is too big to put on the roadmap as a single item — let's break it into initiatives. The first initiative is the foundation: authentication and data model. The second is the user-facing features. Each initiative should have a clear milestone we can point to. We can use the milestone as a forcing function for the quarterly review." How do epic, initiative, and milestone relate in planning vocabulary?
Planning hierarchy (most common interpretation): Initiative — a large strategic bet or programme of work aligned to a business goal. May span multiple quarters. Example: "Launch self-serve analytics." Epic — a large body of work within an initiative, typically 2–8 weeks. Contains multiple user stories. Example: "Build the query builder." User story — a small, user-centred slice of work delivered in 1–5 days. Milestone — a key checkpoint marking meaningful, demonstrable progress. Not a feature — a state: "users can query their own data." Vocabulary: Backlog grooming / refinement — the process of reviewing, estimating, and prioritising backlog items. Sprint goal — a single, clear objective for a sprint that the team commits to. Forcing function — an event or constraint that compels action. Example: a quarterly review as a deadline for reaching a milestone. In conversation: "The milestone is 'users can log in and see their dashboard' — that's what we're committing to for the quarterly demo."
5 / 5
A product director explains to stakeholders why a feature is being delayed: "We're de-scoping the reporting module from Q3. I know that's disappointing, but the core payments flow has to be right first — it's blocking 200 customers. We're re-prioritising based on what moves our north star metric most. The reporting module is still on the roadmap for Q4 — it's not cancelled." What does de-scope mean in a roadmap context?
De-scope: to remove an item from the current delivery commitment — a release, sprint, or quarter. It is not cancellation. The item typically moves to a future period or the backlog. Roadmap communication vocabulary: De-scope — "we're removing X from this release." Reprioritise — "X is now more important than Y; Y moves down." Stretch goal — "if we finish early, we'll tackle this bonus item." Committed vs. aspirational — committed = will be done; aspirational = best-case scenario. North star metric — the single metric that best captures the core value the product delivers to users. Everything is measured against its impact on the north star. Backlog — the ordered list of all remaining work. Ice box — ideas deprioritised indefinitely, not actively groomed. Phrases: "We're de-scoping to protect the Q3 launch date." "This feature is de-prioritised, not cancelled." "We'll revisit in the next quarterly planning cycle."