The Problem to Product Workflow
A structured 10-step workflow I use to move from unclear product problems to product strategy, MVP scope, execution-ready documentation, prototype direction, launch planning, and learning review.
This page gives the abstracted version of the system: the steps I follow, the artifacts I create, and the frameworks I use to make product decisions visible.
What the Workflow Produces
Four working outputs come out of any project that runs through the system, regardless of domain or stage.
Product Clarity
A defined problem, user, segment, job, and why-now context that everyone can point to.
Product Decisions
Documented strategy, opportunity hypothesis, success metric, and visible trade-offs.
Execution Readiness
PRDs, user stories, acceptance criteria, scenarios, and prototype direction a team can build from.
Learning Evidence
Launch monitoring, post-launch reviews, PMF checkpoints, and the next decision, recorded honestly.
The Questions I Answer Before, During, and After Building
Every step exists to answer a specific product question. The map below shows which question belongs where.
| Stage | Product Question | Workflow Step |
|---|---|---|
| Problem | What real user problem are we solving, and why now? | S01 · Problem Discovery |
| User | Who exactly is this for, and which segment are we deliberately not solving for? | S02 · User & Segment |
| Context | How do users solve this today, and what are the alternatives, substitutes, and constraints? | S03 · Context & Market |
| Strategy | What is the product bet, the opportunity hypothesis, and the success metric? | S04 · Strategy & Hypothesis |
| Risk | Is this feasible across business, technical, operational, and ethical dimensions? | S05 · Feasibility & Risk |
| Scope | What is the smallest useful version, and what are the visible trade-offs? | S06 · MVP Scoping |
| Experience | How does the user actually accomplish the job, including edge cases and error states? | S07 · Experience Design |
| Documentation | Can a team build this from the document, end to end? | S08 · Product Documentation |
| Launch | How do we ship it, monitor it, and capture feedback? | S09 · Execution & Launch |
| Learning | What did we learn, and what is the next decision: iterate, pivot, pause, or sunset? | S10 · Learning Review |
Step-by-Step
Open any step to see its purpose, decision focus, frameworks, artifacts, and how it shows up inside a case study.
Artifact Library
The concrete documents and outputs the workflow produces, grouped by stage. Click a tab to switch.
Framework Index
The frameworks I lean on, grouped by the product decision they support.
How This Becomes a Case Study
Each case study section maps directly back to the workflow step that produced it.
| Case Study Section | Workflow Source |
|---|---|
| Problem Snapshot | S01 · Problem Discovery |
| User & Segment | S02 · User & Segment |
| Research & Assumptions | S01, S02, S03 |
| Product Strategy | S03, S04 |
| Risk & Feasibility | S05 · Feasibility & Risk |
| MVP Scope & Trade-offs | S06 · MVP Scoping |
| User Flow & UX | S07 · Experience Design |
| Documentation Excerpts | S08 · Product Documentation |
| Execution Plan | S09 · Execution & Launch |
| Launch & Monitoring | S09 · Execution & Launch |
| Learning & Next Decision | S10 · Learning Review |
| "How I Worked" Note | Tool support disclosure across all steps |
How I Label Evidence
Every project gets an honest evidence label. The label tells you what stage the proof is at, not how impressive the headline sounds.
How I Use AI-Led Development in the Workflow
AI-led development supports the workflow at specific points: research synthesis, documentation drafts, UI exploration, prototype scaffolding, internal tools, and technical probes. It speeds up the parts that benefit from speed.
Final product judgment stays human-led. Problem framing, user understanding, scope decisions, trade-off calls, prioritization, and learning reviews are reasoned through and signed off by me, not by a tool. AI-generated material is treated as a draft that needs review, testing, and clear disclosure.
See the Workflow Applied
The system is most useful when you can see it inside real projects. Each case study runs through these same 10 steps with explicit evidence levels and trade-offs.