Reopening a decision six months later
An old feature argument came back in a Thursday meeting. What was still in the six-month-old decision record, and what quietly wasn't.
Read →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 argument already happened before you opened the tool
Prioritization tools score a decision after it's already made, somewhere else entirely. That gap explains why reach gets faked and decision logs die.
Read →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
We normalized RICE to a continuous 1-100 scale because the math is right. A 2026 study on scale reliability told us what that scale was still missing.
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 →Let the model draft the score, not make the call
Where AI genuinely helps in prioritization, where it just launders a guess, and why the accountable step has to stay with a person who can be argued with.
Read →Reach is the number you're guessing at
Reach swings a RICE score harder than any other input and is the one teams most often invent. How to bound it honestly, and what to do when you can't.
Read →Stop relitigating the same decisions.
Free, and no account needed — guest mode runs entirely in your browser.