An atomic essay on Clayton Christensen, getting specific and GOOD ENOUGH products ๐
Clayton Christensen, the brilliant HBS innovation thinker & professor, was hired to analyze and improve fast food milkshakes ๐ฅค
At the time, the company didnโt know why the milkshakes were popular with consumers ๐โฃ๏ธ
After standing in line for days, watching consumers purchase these milkshakes, CC and his team realized that more than half of milkshake consumers were buying them early in the morning for their car commute ๐
They brought the milkshake mystery down to a single question: what was the โJob to be Doneโ by the milkshake for the customer, and how could they improve on that? ๐ฅค๐
The decisions that they made to optimize the product for this particular use case were VERY SPECIFIC (& not what they would have done for calorie-guzzling, post-workout consumers) ๐๏ธโโ๏ธ
As a side note, this is why we love analyzing customer use cases at @fcollective ๐
The milkshake consumers didnโt need the milkshake to be protein-packed or come in 100 different flavors.
They wanted something to break up the monotony of a long commute and easy grab-and-go payment options ๐ณ
When a startup is very specific about the Job to be Done, and Delight Factors for their customers, they can build GOOD ENOUGH in other feature areas.
If they donโt know, their product process will be diffuse instead of directed ๐
Learning WHY so you can focus on WHAT gives you more leverage than trying to ship EVERYTHING.
Welcome to the school of Good Enough ๐
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
Why aiming to control your own destiny can be a superpower for founders ๐ช๐ฝ
An atomic essay on moonshots & escape velocity ๐
Escape velocity in physics is the speed an object needs to reach to escape the earth's gravitational pull, and take off into space.
Investors sometimes talk about a startup reaching escape velocity, which is the speed and milestones the team needs to reach before they can start accelerating.
To more inclusive & interesting conversations in 2021 ๐ฅ
Here are 54 women I follow on @twitter and learn from everyday. I follow both men and women, and I learn from both. Please RT if you do too, and amplify their voices.
Applying software to highly regulated / intermediated industries like education and healthcare is so tricky.
When well-meaning technologists dive into these industries they slam into quite a few things. Human systems prove harder to hack.
A thread:
โ ๏ธ 1st problem: more than usual inertia around the status quo.
There are often multiple stakeholders who have fought to build distinct moats or for whom the status quo simply is profitable, and it distorts economic, productivity, and outcomes-based incentives.
โ ๏ธ 2nd problem: disconnect between users, stakeholders and payers.
Where normally, design principles teach us to find a deep stakeholder problem and solve it, here you can do that and still not find a payer for it (ever).
Sometimes it takes a few startups, raising several rounds of venture funding, and going through an acquisition process โ before founders understand some of the *unwritten dynamics in venture capital.*
#1: Raising more money does not automatically translate into building a more valuable startup.
Yโall will debate me fiercely on this one, but historically, this is true. Please see @epaleyโs definitive analysis on this here. techcrunch.com/2016/10/15/oveโฆ
#2: Growing into a high valuation is highly binary.
Like accelerating into a curve and hoping you make it... t he key proof point will be at your next round of funding, not this one.