Main idea

When a roadmap card sits in Now, its level of commitment is already stated by its position. Rewriting inside the card that it is committed, that it is a priority, that its horizon is the current quarter adds no information: it copies the column.

The card has to answer what the column does not say: why this topic deserves that place. For a committed topic — the value promise, the target, what is going to change, what is excluded, the metrics. For a candidate — what is left to settle and what would move it to commitment. For a topic kept visible — why it stays on display and why it is not a priority.

The opposite trap is bureaucratic and it feels like rigor: you add fields, statuses, tags, sub-categories, validation rules. The criterion that settles it is simple — if the information helps neither to decide, nor to understand, nor to communicate, it weighs things down without giving anything back.

Why it matters

It gives a writing rule that survives a change of tool: what the structure carries, the content does not repeat. It applies as is to a ticket filed in a status column, to a record placed in a folder, to a document dropped into a named workspace.

It also prevents the roadmap's most common drift: becoming a form nobody reads, where the effort of filling it in stands in for the quality of the thinking.

Nuances and limits

Redundancy is useful when the card travels outside its board — exported into a presentation, pasted into a message, read by someone without the overall view. The status then has to be repeated, but that is a distribution cost, not substantive information.

And the rule does not say how much writing is the right amount: it only says what is not part of it.

Open questions

• How do you tell, at the moment of adding a field, the one that will serve a decision from the one that will only reassure people about how serious the setup looks?