.png){kind=small}
PRODUCT OWNER WORKSPACE
Turn messy product context into an actionable starting point you own.
Review the context. Approve the Product Goal. Order user needs, and learn from the current integrated product.
PRODUCT CONTEXT
Give the Sensei reality to work with.
Choose how you want to begin.
IMPORT CONTEXT
BRING IN YOUR EXISTING CONTEXT
Paste notes, stickies, headings, shorthand, or other product context. Don't clean it up first.
SENSEI
These appear to describe one idea.
ORIGINAL IDEAS
Sensei suggested this wording. Edit it if needed; it is not customer evidence.
PRODUCT CONTEXT REVIEW
HERE'S THE PRODUCT CONTEXT I PULLED FROM YOUR CONTENT
Check the mapping and change anything that needs correcting.
PRODUCT GOAL
Your Product Goal
A concise desirable future state and the reasoning that makes its strategic hypothesis inspectable.
PRODUCT GOAL · Sensei assisted
The legacy Goal v1 is preserved unchanged. Any Goal v2 interpretation is a separate draft requiring new Product Owner approval.
Possible Product Goal adaptation · Sensei assisted
This proposal comes from representation wording. It has not changed the approved Product Goal and is not customer evidence.
EDIT PRODUCT GOAL
This Product Goal is approved and can drive downstream artifacts.
CHALLENGE THIS GOAL
One decision at a time.
WHAT YOU ALREADY SUPPLIED
Represent Product Goal
Optional ways to communicate the same approved goal. Edit the wording; use approved assets or leave their space empty.
ORDERED PRODUCT BACKLOG
Order the first plausible work and learning.
A starting hypothesis—not a complete specification of the future.
Preserved legacy work
PRELIMINARY DEFINITION OF DONE
Establish the initial shared quality bar.
One shared quality state for the Current Integrated Product (Scrum term: Increment). New Done work must meet this standard when integrated.
Refine only what may matter soon
Discuss roughly the top 3–5 items. Leave the rest deliberately incomplete.
A purpose for the upcoming Sprint
PO suggestions are proposals for discussion, not commitments or Sprint Backlog selection. During Sprint Planning the Scrum Team determines the Sprint Goal. Developers select the work and own task decomposition in their chosen tool.
Current Integrated Product and release
What should our MVP include?
Toyota Production System, Taiichi Ohno and Lean thinking are roots of waste reduction, flow and learning. Mary and Tom Poppendieck translated Lean principles into software development. The term Minimum Viable Product is generally credited to Frank Robinson, later popularized through Customer Development and Lean Startup, especially Steve Blank and Eric Ries.
Export product thinking
ForgeExportV1 is neutral input for future SWAT, Miro and Jira adapters. No external integration is invoked. The Product Backlog is globally ordered, not a To Do / Doing / Done board. Continuous support work may use a separate flow visualization.