topic : shape

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.

Where the Thinking Is - A rework based on what’s holding up in real builds and where the shape+build+launch thinking is right now.

If AI Is Your Guardrail, You’ve Already Lost - AI can move fast. But it won’t fix direction. If that part isn’t clear, speed just gets you to the wrong place quicker.

Multi-Sided Systems Blur Faster - The issue wasn’t that the user was vague. It was that there wasn’t just one.

A different set of eyes makes all the difference - A single suggestion from a fresh perspective can change everything.

vibeCoding is not AI-assisted coding (and confusing them costs you) - Same tools, opposite intent. The mistake is using vibeCoding habits on work that is actually AI-assisted coding, then wondering why it collapses in week three.