topic : 3x3x3

1.1.1 - If You Can’t Name the User, You’re Guessing - Name the user definition: say who the user is, what starts the need and what result they are trying to reach.

1.1.2 - Describe the Pain Without Mentioning the Solution - Describe the pain statement: say who is affected, what happens right before the pain appears and what it costs the user or the team.

1.1.3 - The One-Line Promise That Keeps You Honest - Write the one-line promise: say who it is for, what result it creates and what it is deliberately not trying to do.

1.2.1 - Can You Explain This in 30 Seconds? - Explain the 30-second explanation: explain who it is for, what problem it fixes and what useful result appears without adding a second paragraph.

1.2.2 - What Does “Success” Mean for Version One? - Define the version one success definition: say what has to happen, how it will be measured and what number or threshold counts as enough.

1.2.3 - The Risks You’re Avoiding Naming - Name the named risk: say what might fail, who or what it would affect and what action will reduce the damage.

1.3.1 - The One Outcome That Makes This Worth Doing - Choose the main outcome: say what changes for the user, why that change matters and what signal will show it is real.

1.3.2 - What This Will Not Do (On Purpose) - Set the scope boundary: say what stays in, what stays out and why the cut protects the core path.

1.3.3 - Describe One Main Path - Then Ignore the Rest - Describe the main path: describe the user, what starts the flow and the exact steps that lead to the outcome.

2.1.1 - The Only Path Your Prototype Needs - Define the prototype path: say what the prototype is meant to teach, which path will test it and what signal counts as proof.

2.1.2 - Where the User First Feels Value - Find the first value moment: point to the moment the user first feels relief or progress and the step immediately before it.

2.1.3 - What This Build Is Meant to Teach You - Name the learning goal: say what you believe, what the build needs to answer and what signal will prove or weaken that belief.

2.2.1 - The Routine Work Checklist Nobody Talks About - Define the routine work checklist: say what repeats, who owns it and what done looks like each time.

2.2.2 - Buy vs Build Is a Strategy Choice - Make the buy versus build decision: say what the decision is about, why one side wins and which constraint makes the call.

2.2.3 - Understanding the Shape of the System - Map the system shape: say which part owns what, what each part depends on and where the important handoff happens.

2.3.1 - Where the Real Differentiation Actually Lives - Name the real differentiation: point to the advantage, show where the user feels it and say what should remain standard.

2.3.2 - Why Cutting Features Is a Design Skill in AI-Assisted Software Development - Choose the feature cut: say what stays central, what gets removed and why the product becomes stronger because of that cut.

2.3.3 - The One Metric That Proves This Works - Define the proof metric: say what the metric is, what user behavior creates it and what threshold counts as enough.

3.1.1 - Why Sharing Early Creates Learning - Plan the early sharing plan: say who will see it, what they will see and what question their reaction needs to answer.

3.1.2 - Ask for Signals, Not Opinions - Choose the decision signal: point to the behavior or result you need to see and explain what decision it will change.

3.1.3 - Decide in Advance What Would Change Your Mind - Set the decision threshold: say what evidence will trigger change, where it will come from and what action follows.

3.2.1 - The Difference Between Learning and Being Stuck - Name the learning signal: say what question is being answered, what signal will answer it and what decision comes next.

3.2.2 - Explain Your Decisions Before Asking for Review - Explain the review context: say what was decided, what trade-off it created and what question you want reviewers to answer.

3.2.3 - Iteration Should Increase Value - Check the iteration value test: say what changed, what user outcome it is meant to improve and what signal will show that it did.

3.3.1 - What “Ready” Actually Means - Define the readiness rule: say what has to be true, how it will be checked and who owns any remaining risk.

3.3.2 - Name the Risks Before Users Find Them - Name the launch risk: say what might break, what would trigger it and what response reduces the damage.

3.3.3 - Are You Comfortable Putting Your Name on This? - Set the ownership threshold: say what is still imperfect, what would happen if it failed and why shipping is still acceptable under those conditions.