If you are not embarrassed by the first version of your product, you’ve launched too late.
The Idea That Came from Failure
In 1997, Reid Hoffman founded SocialNet, an early social-networking idea that allowed people to create profiles, connect with friends, and share updates. The concept was ahead of its time, but the company failed.
The problem was not necessarily the idea. Hoffman spent too long trying to make the product ready before releasing it. By the time it reached the market, conditions had changed, users had moved on, and the window of opportunity had narrowed.
That experience taught him a principle he later applied to LinkedIn:
If you are not embarrassed by your first release, you launched too late.
LinkedIn’s Imperfect First Day
When Hoffman and his co-founders launched LinkedIn in 2003, the product was extremely simple. It had no sophisticated news feed, recommendation engine, or polished profile experience. Users could upload a photo, write a short introduction, and connect with other professionals.
The first version was not impressive—and that was precisely its value. By releasing early, the team could observe real users, collect real feedback, and improve based on evidence rather than internal assumptions.
LinkedIn gradually developed from a basic professional networking site into a global platform used by hundreds of millions of people. In 2016, Microsoft acquired LinkedIn for $26.2 billion.
Speed of Learning Beats Perfection of Planning
Hoffman later systematized this way of working through the idea of Blitzscaling: in conditions of uncertainty, organizations may need to prioritize speed over efficiency.
This does not mean acting recklessly. It means recognizing that a fast feedback loop can be more valuable than a flawless plan built without sufficient contact with reality.
The most important management skill is not making a perfect decision when everything is known. It is making a responsible decision when information is incomplete—and then correcting course quickly.
Three Lessons for Managers
1. Perfection Is the Enemy of Speed
Waiting until every detail is polished can cause a team to miss the moment when action matters most. A useful first version creates learning; an endlessly revised draft creates only delay.
2. Embarrassment Is the Price of Feedback
An imperfect release can feel uncomfortable, but it gives a team access to real-world information. That information is often more valuable than another round of internal debate.
3. Speed Is a Strategy
In uncertain environments, moving quickly is not merely an operational preference. It can be a competitive advantage. Teams that learn, measure, and adapt faster can outpace teams that plan carefully but act slowly.
A Question for Today
Is there something you are postponing because it is not ready yet? Perhaps the better approach is to release a smaller first version, learn from the response, and improve it one step at a time.
The goal is not to celebrate poor quality. The goal is to avoid confusing perfection with progress.
References
- Hoffman, Reid, and Chris Yeh. Blitzscaling: The Lightning-Fast Path to Building Massively Valuable Companies. Currency, 2018.
- LinkedIn. “About LinkedIn.” Corporate history and company background.
- Microsoft. “Microsoft to Acquire LinkedIn.” Press release, 2016.