Sign in

The value creation queue

Findings turned into ranked work: what to fix first, what it is worth, and what happened to it.

Updated September 23, 2026
3 min read
results
analysis
features

An assessment tells you what is wrong. The queue is what you do about it.

Every finding the analysis produces also arrives as a recommendation: a piece of work with an owner's decision attached. The queue ranks them so the order is argued rather than assumed, and records what was decided so the next reader of the project can see it.

Where it lives

  • Per project — the Value creation tab, showing only that project's recommendations. This is where the work is done, alongside the evidence it came from.
  • Across every project — Value Creation in the sidebar, the same rows ranked together. Useful when one team is working several projects and needs the order across all of them.

Both read the same records. A status change in one is a status change in the other.

Return on effort

The ranking is a ratio, not a severity list: what the item is worth against what it costs to do. A high-impact finding that needs a year of platform work ranks below a medium one that needs a fortnight, because the second one will actually be finished.

Each row carries:

FieldWhat it says
Return on effortThe ranking figure — impact against effort
ImpactWhat is at stake if it stays as it is
LeverWhich part of the business it moves
Value thesisWhy it matters, in a sentence you could repeat to a board
Next stepThe first concrete action, not the whole program

Every status change needs a note

There are six states, and moving between them is a recorded decision:

  • Open — nobody has decided anything yet.
  • Planned — it is scheduled.
  • In progress — work has started.
  • Resolved — the work is done. This is a claim, and the next analysis run checks it against the evidence. Only a verified resolution counts toward progress, which is why marking something resolved is not the same as closing a ticket.
  • Accepted risk — the finding is fair and you are choosing to live with it.
  • Declined — the finding does not apply, with your reason.

The last two are deliberately not the same thing, and neither of them makes an item disappear. A dismissal without a stated reason is worse than no dismissal at all: six months later nobody can tell whether it was considered or missed.

If you share progress with an investor

Where an organization publishes to an investor, the queue is what the investor reads movement from — the items, their states, and the reasons attached to the ones that were declined. What each investor sees, and which projects it covers, is set on Administration → Investor sharing, never here.

Availability

The queue is part of the plans that include it. Where a plan does not, the tab explains what it does and the findings stay in the report.

Next

Was this article helpful?

Votes are read: an article that keeps failing gets rewritten.