Cutting features feels like loss and looks like design - A 30 minute interactive Q&A on the design skill of subtracting features. Examples not tutorials. Places are limited to twenty.
build :: Making something concrete enough to learn from.
Why shipping every day is easier than once a month - A 30 minute interactive Q&A on splitting work into small regular chunks and deploying as often as you can. Examples not tutorials. Places are limited to twenty.
The unglamorous work nobody writes about is what actually ships things - A 30 minute interactive Q&A on the routine work that keeps builds moving. Examples not tutorials. Places are limited to twenty.
All the research, nothing to show for it - what if you could deliver this week? - You bought the books. Watched the tutorials. Spun up projects on three different stacks with two different AI coding tools. Investigated frameworks, compared hosting platforms, read threads from people who sound like they have it figured out.
Build is where the change touches running code. The goal isn't to finish; it's to prove the change is real, safe and reversible.
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.
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.
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.
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, 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.
2.2.3 - Understanding the Shape of the System Before You Change It - 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 in Your Build - 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 Most Builders Skip - 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 for Real Users - Define the proof metric: say what the metric is, what user behavior creates it and what threshold counts as enough.