topic : avoiding overbuild
Keeping the build small on purpose so it can ship and be learned from.
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.
Published 3 months ago 4 min read build2.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.
Published 3 months ago 4 min read build2.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.
Published 3 months ago 4 min read launch3.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.
Published 3 months ago 4 min read build eventCutting scope without cutting value · vibe2value workshop · Thu 19 February 2026 - Scope and value are not the same list.
1 min read build eventRefactoring when you should be shipping · vibe2value workshop · Thu 12 March 2026 - A refactor is a feature with a worse return.
1 min read