Note 25 | Customers Hire Products to Get a Job Done
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.
Another central idea is Jobs to Be Done, discussed by Clayton Christensen in Competing Against Luck and advanced by Bob Moesta and Tony Ulwick. Customers do not simply buy products; they hire them to accomplish something. People want a hole, not a drill. That insight might produce a better drill—or a solution needing no drill at all.
Do not ask customers to design the product or name the product they want. Ask what problem they need solved, then keep asking why until you understand it. The answer may lead to a solution they never imagined. Establish the current job and why existing products or services fall short.
Aulet warns that people satisfied with their overall workflow rarely replace it merely because one product is better. Understand the complete process and fit into it, rather than expecting customers to reorganize everything around you.
FillBee wanted shoppers to visualize furniture in their homes in 3D. A good concept did not guarantee practical adoption. A rigorous use-case analysis identified measurement within research and planning as an improvement opportunity, then connected research, browsing, and purchase into one online flow. Two-sided markets need a Full Life Cycle Use Case for each side.
I trust teams that can explain whom or what customers currently hire, and why that solution disappoints, more than teams that open with feature lists.
Three actions: Express the core job as When…, I want to…, so I can…, in the Persona’s language rather than product jargon. List at least three existing alternatives and their failures or compromises. Follow each why down five levels to test whether you are solving a root problem rather than a casual feature request.
#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.
Sign in to comment, reply or like. Sign in / Sign up
Loading comments…