Move from evidence-backed priorities to a usable roadmap

In Discovery → Direction, each view answers a different question: Active work shows what the team has started shaping now; Priorities is the saved, editable plan for what should be considered next; and Analysis is the latest complete analysis, including proposals, rankings, uncovered demand, evidence quality, and gaps.

Analysis proposes changes; it does not silently rewrite the team plan. Review proposed additions and removals in Priorities before moving work into Active work.

Choose the relevant product scope. A product view and No product are ordered queues; All products is a grouped overview.

Compare the evidence, affected customers, goals, expected impact, effort, dependencies, and unanswered questions for each candidate. Use analysis to explore tradeoffs, then save the team’s choice in Priorities.

Missing evidence is a gap to investigate. A model score is not approval. When a priority moves to Active work, Zentrik preserves the decision context behind that move.

Promote an idea when the team is ready to manage it as committed product work. Before promotion, confirm:

1. The customer or business problem is explicit.
2. Source evidence and the relevant opportunity remain linked.
3. The intended users and product area are known.
4. Scope boundaries and material constraints are visible.
5. A success check exists.
6. Open questions are accepted, assigned, or resolved.

The initiative becomes the home for the committed problem, scope, artifacts, tasks, decisions, and delivery context. Preserve the trace back to discovery instead of recreating the rationale in an unrelated brief.

From the initiative, review the brief, draft stories and acceptance checks, split tasks, and record dependencies. Review generated scope, estimates, and dates with the people responsible for the work.

On Schedule, use Plan timeline to place tasks within their cycles. Other initiatives’ tasks appear for context and cannot be edited there. A task stays within its assigned cycle.

Follow Documents and delivery for artifacts and external handoffs, and Schedule work on the roadmap for timeline controls.

Use Now / Next / Later to communicate sequence, Timeline for dates, or capacity and impact views to compare team load and goals.

Review the effect of changes before sharing a commitment. Record externally fixed dates as constraints. A roadmap date does not establish that work shipped or achieved an outcome.

Revisit priorities and the roadmap when:

• new evidence changes the severity or reach of a problem
• a study invalidates or narrows an idea
• effort, dependency, or capacity assumptions change
• a committed initiative is paused, replaced, or completed
• delivery status changes downstream
• an outcome creates new evidence for the next decision

Return work to priority review when it is no longer active. Do not preserve its old rank automatically; reconsider it against the current cohort.

Check that each committed initiative has an owner, problem, scope, success check, and dependencies. The roadmap should show the agreed sequence or dates, with a reason to revisit the plan when evidence or capacity changes.