Blog

Notes on product decisions.

Prioritization, estimation, and decision records — the parts of choosing what to build that a framework alone does not cover.

Prioritization frameworks are the easy part. RICE fits on one line, and any team can learn to compute it in an afternoon. What the framework does not tell you is where the numbers come from, which of them you are quietly inventing, what to do when two scores land within the error bars of each other, or how to make a decision that survives the question “why didn't we build the other thing?” three months later.

That is what gets written about here: estimation, decision records, and the judgement that sits around a score rather than inside it. Mostly short, mostly opinionated, and grounded in the same model Tarazu itself runs on. If you want the framework mechanics first, start with the RICE guide.

The tie-break is the real decision

A four-point gap between two RICE scores usually isn't a gap at all. What to do when the framework correctly tells you it can't resolve the ranking any further.

Read →

What the number on the slider means

Tarazu uses shared score bands and recorded claims to explain a 1–100 input. The resulting index is a comparison aid, not a measurement or financial return.

Read →

A decision record isn't a changelog

Teams remember what they chose and forget why. What to write down at the moment of the call, and why the rejected options matter more than the chosen one.

Read →

Return to the notes behind your choices.

Free, and no account needed — guest mode runs entirely in your browser.