build

assemblebuy-vs-build

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

5 min read

build

assemblecommodity

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.

4 min read

build

prototypelearning

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

4 min read

build

prototypevalue

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

4 min read

build

prototypefocus

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

4 min read

shape

strategyuser-journey

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

4 min read

shape

strategyscope

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

4 min read

shape

strategyoutcomes

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

4 min read

shape

organiserisk

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

4 min read

shape

organisegoals

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

4 min read

shape

organiseclarity

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

4 min read

shape

problempromise

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

4 min read