The roadmap is often where the disagreement becomes visible

A team asks for prioritisation help. The roadmap is crowded, every item has a sponsor, and nobody can explain what should move. It is tempting to reach for a scoring model.

But the score is rarely the missing ingredient. The team has not agreed which decision it is making, which evidence deserves to change that decision, or who can make the trade-off.

An illustrative example

Imagine a product group preparing a detailed weekly portfolio view. Leaders can see more work than before, but decisions still move slowly. Each team brings different evidence. Some ask for approval, others ask for advice, and several simply report status.

One useful move could be smaller than a dashboard rebuild: define the decision expected from the review, make the owner visible, and ask every team to name the signal that would change its current bet.

A roadmap becomes useful when it protects a choice—not when it records every request.

A practical decision brief

Before changing the roadmap, write six lines:

  1. The customer or business change we are trying to create.
  2. The belief behind this bet.
  3. The strongest new evidence.
  4. The decision needed now.
  5. The owner of that decision.
  6. The signal that would make us stop or change course.

If those lines are unclear, another prioritisation score will add precision without adding judgment.

What this does not mean

Roadmaps are not useless, and every decision does not need an elaborate memo. The point is narrower: a roadmap cannot resolve an unnamed strategic disagreement. It can only display its consequences.

Evidence note

This sample uses an imagined situation to demonstrate a way of thinking. It is not an account of Malav’s client work and does not claim a measured outcome.