Topic: product-management
-
RICE and ICE scoring: what the numbers mean and where they stop
RICE multiplies reach, impact and confidence and divides by effort; ICE drops reach and keeps impact, confidence and ease. Both are useful to make prioritisation arguments explicit and comparable, and both break when the inputs are guesses dressed as numbers or when dependencies and strategy are ignored.
-
Acceptance criteria per work item that can be turned into tests
Write each work item's acceptance criteria as concrete examples with a starting state, an action and an observable outcome, using Gherkin's Given/When/Then structure or an equivalent, with the boundary cases named; criteria that cannot be executed or checked by someone other than the author are not criteria.
-
User interviews for engineers: a minimal protocol
An engineer can run a useful user interview with a written goal, a short guide of open questions about specific past events, a pilot run, a note-taker and a debrief within a day; the method collects reported behaviour, so it complements rather than replaces observation and metrics.
-
Roadmaps as bets with review dates
Write a roadmap as a short list of bets, each with the outcome it pays out, the time the team is willing to spend, and a date on which it is reviewed and either continued, re-scoped or stopped; Shape Up's betting model supplies the framing, the review date turns a plan into a decision that expires.
Machine-readable: JSON