Note 26 | Do Not Build Yet. Draw Something You Can Discuss.

These are Robin Shen’s original reading notes and commentary, written in his own words after reading Bill Aulet’s Disciplined Entrepreneurship: 24 Steps to a Successful Startup. They are not the original book, excerpts from it, or an official publication. Methods and concepts from the book are attributed to Bill Aulet; other sources are identified where stated. For reference only; not investment advice.

English translation of Robin’s Chinese reading notes and commentary. Passages are paraphrased, not verified verbatim quotations from the original English edition.

Aulet deliberately waits until chapter 12 before asking you to depict the product. Teams that build too early often fall in love with their creation and stop listening. Here, produce only a High-Level Product Specification: a picture, storyboard, or brochure for discussion with teammates and prospects. This is not development. Love solving the problem well, not the product itself.

The IKEA effect explains why making something can create irrational attachment. Delaying development preserves an inquiry mindset rather than a pitching mindset. Explore strengths and weaknesses with customers instead of selling. Aulet also describes spiral innovation: the first version need not be right. If even 10% is useful, keep that portion and iterate. A concrete visual starts the learning cycle.

A good specification is visual, benefit-led rather than feature-led, high-level, targeted to the initial customer, and flexible enough to invite changes. Emphasize the Persona’s first priority. Listening requires willingness to change. Altaeros’s illustration of an airborne wind turbine exposed internal disagreements before aligning the team and supporting research. Sensable’s eventual digital-clay product differed substantially from its original concept. The specification still worked because it started the conversation.

A founder claiming openness after locking the engineering schedule may have already closed the door halfway. Start with a drawing you can change before writing code you cannot easily undo.

Three actions: This week, create one hardware visual or a three-to-five-screen software storyboard without scheduling development. Replace technical jargon with benefits tied to the Persona’s top three priorities. Review it in inquiry mode with two target customers, record three requested changes, and align the team’s interpretation before meeting them.

#DisciplinedEntrepreneurship

These are reading notes and reflections based on my personal understanding. I recommend reading them alongside the original book for the full context.

Comments

What do you think? Share your experience or questions.

Loading comments…