Use this concept as a question to test the decision, not as a label for a person.
Open →Decision situation
Product prioritization
Review roadmap choices without letting the loudest request, recent event or prior investment define value.
Signals to notice
Reasons to slow down and check.
- One customer story dominates the discussion.
- A feature stays high priority because much work is already invested.
- Success criteria are being added after the preferred option is chosen.
Questions before action
Make the missing evidence visible.
- What outcome are we optimizing before comparing features?
- Would we fund the next step if no work had already been spent?
- What broader evidence competes with the vivid request?
Relevant lenses
Concepts that may help you test the reasoning.
Practical moves
Do something different, not only notice a label.
Evaluate the next step using future cost and value rather than resources already spent.
Open →Compare a vivid case with the broader frequency or distribution that should inform the judgment.
Open →Fix the comparison dimensions before a preferred option makes the criteria move.
Open →Skill to develop
Decision making under uncertainty
You can make a decision without pretending uncertainty has disappeared.
Practice this situation
Choose a useful first move.
One large customer describes a painful workflow problem. The roadmap discussion treats that story as proof that most users need the same feature.
Skill: Decision making under uncertaintyOpen scenario →A feature has consumed eight months of work. New research shows limited demand, but the team argues that stopping would waste the investment.
Skill: Decision making under uncertaintyOpen scenario →