Product opportunity canvas
Align the user problem, business outcome, existing alternatives, evidence, and constraints before defining a roadmap.
Explore the full guidePractical guides / 04
Think clearly.
Build usefully.
Checklists and decision guides to help your team frame the opportunity before tools, timelines, and features take over.
Start with the right questions.
Each resource is designed for a working session. Use it with your team, note where answers differ, and turn uncertainty into explicit decisions.
Should this workflow use AI?
Evaluate repeatability, judgment, data, oversight, acceptable error, cost, and the simpler automation alternatives.
Explore the full guideSystems & data inventory
Identify sources, owners, access paths, sync direction, sensitive fields, failure impact, and recovery responsibility.
Explore the full guideA useful project brief
Give a delivery team enough context to ask better questions without writing a fifty-page requirements document.
Explore the full guideFour working checklists.
These are prompts, not pass-or-fail tests. The most valuable answers are often the ones your team cannot agree on yet.
Product opportunity
- Who experiences the problem most often?
- What do they do today instead?
- What measurable outcome should improve?
- What evidence shows the problem is worth solving?
- What must remain true even if the solution changes?
- What is the smallest useful test?
AI readiness
- Is the workflow frequent and costly enough?
- Which decisions require human judgment?
- What data is available, permitted, and representative?
- What errors are acceptable—and which are not?
- Where will review, correction, and audit happen?
- Would rules or conventional automation work better?
Integration map
- Which system is the source of truth?
- Who owns access and schema decisions?
- Which fields are sensitive or regulated?
- Does data move one way or both ways?
- What happens when sync is delayed or fails?
- Who monitors, retries, and resolves conflicts?
Project brief
- Business outcome and reason it matters now
- Primary users and critical workflow
- Current tools, workarounds, and friction
- Systems, data, and access dependencies
- Non-negotiable constraints or deadlines
- Decision-maker and people needed for input
Have the essentials?