Choosing the next change means knowing what is ready for a decision, what is already underway, and what shipped without enough outcome evidence. The product’s Intents list brings those records together so the team can make that call from current information.
The input
Several intents for the same product, with objectives, review state, and whatever evidence or measurements are available. The list helps you find the records; it does not rank their business value for you.
The flow
1. Find the relevant work. Open Intents and use search or the Draft, In review, Approved, and Shipped filters. The list is ordered by recent updates, not priority.
2. Find decisions waiting on people. Use the action filter to locate intents needing review. Open the proposal to inspect the question, correction, or revision that needs attention. A lifecycle label and implementation authorization are separate records.
3. Compare value, dependencies, and cost. Read the objectives, evidence, scope, and recorded dependencies of the candidates. Agree what needs to happen first and what the team is postponing. Evidence count alone is not a priority score.
4. Check what earlier work achieved. For shipped intents, inspect the recorded outcome measurements. Use Awaiting outcome measurement to find missing follow-up. An AI implementation review does not establish that the user outcome improved.
5. Record the choice and review the proposal. Keep the reason for choosing this work with the intent. Resolve the remaining questions and approve the exact proposal revision before the coding agent implements it.
The output
A next-build decision with a reason the team can revisit, an agreed scope, and an approved proposal for the engineer. Work that still needs a decision or measurement stays visible.
Try it with three candidates
Open three intents competing for the next slot. Compare who benefits, what evidence supports the problem, which dependencies are available, and what you would postpone. Record the choice and its reason on the selected intent.
Related
Bring this workflow to your team.
Keep the evidence, decisions, and follow-up work together in your product.
Start with Pathmode