Lean Startup
A practical step-by-step guide to lean startup, including preparation, instructions, common issues, tips, and next steps.
Lean Startup
This guide explains how to approach lean startup, including the preparation, practical steps, common mistakes, and final checks that help you finish with confidence.
Before You Start
Step-by-Step Instructions
Quick Reference
Common Problems When You Lean Startup
Fix: Many people get caught up trying to make their MVP perfect with lots of features. This delays launch and means you spend more time and money before getting feedback. The fix is to ruthlessly cut features until you have only the absolute core function that tests your main hypothesis. If you can test your idea with a simple survey or a mock-up, do that instead of building a whole app.
Fix: It's natural to want your idea to succeed, but ignoring negative feedback is a recipe for failure. Actively seek out critical comments. Ask open-ended questions like "What problems did you have?" or "If you could change one thing, what would it be?" Be ready to hear things you don't like and treat them as valuable insights, not criticisms.
Fix: This is a common trap where creators keep building and perfecting without ever launching. The Lean Startup is all about quickly moving to "Measure" and "Learn." Set strict deadlines for your MVP build. For example, tell yourself you will launch in two weeks, no matter what. This forces you to focus on only the essential elements.
Fix: This is one of the hardest decisions. A good rule of thumb is to set clear metrics or goals before you launch your MVP. For instance, "I expect 10% of visitors to sign up." If your results consistently fall far short of your goals after several small adjustments, it's a strong sign that you might need to pivot. A pivot means changing a core assumption, not just tweaking a colour.
Fix: While measuring is vital, you can spend too much time dissecting every piece of data. The goal is "validated learning" – learning that helps you make a decision. After collecting feedback, look for the clearest patterns and insights that point towards a change or a clear next step. Don't wait for perfect data; aim for "good enough" to inform your next small step.
Advanced Tips for Lean Startup
- A/B Testing: Once your MVP has some users, try offering two different versions of a feature (A and B) to different groups of users at the same time. This helps you see which version performs better based on real data, giving you clear insights into what customers prefer.
- User Interview Techniques: Instead of just asking "Do you like this?", learn to ask open-ended questions about past behaviours. For example, "Tell me about the last time you tried to solve [problem your product solves]." This often reveals deeper needs and pain points than asking about future intentions.
- Focus on Vanity Metrics vs. Actionable Metrics: Avoid "vanity metrics" like total website visitors if they don't tell you anything about customer behaviour. Instead, focus on "actionable metrics" – numbers that directly relate to your hypothesis and inform your next steps, such as conversion rates (how many visitors complete a desired action) or retention rates (how many customers keep coming back).
- Concierge MVP: Sometimes, your MVP can be providing the service manually yourself before you build any tech. For example, if you're building an AI tool, your concierge MVP might be you doing the AI's job manually behind the scenes, processing requests from customers and sending back results. This allows you to learn exactly what's needed before investing in complex software.
- Story Mapping: Before building any new feature, use "story mapping" to visualise the entire user journey and prioritise what absolutely needs to be in your MVP. This technique helps ensure everyone understands the core purpose of the product and avoids scope creep.
- Hypothesis-Driven Development: Frame every new feature or change as a clear hypothesis. "We believe [this feature] will help [these users] achieve [this outcome]." Then, design specific ways to measure if that outcome is achieved after you launch the feature.
Lean Startup FAQ
What exactly is a "pivot" in Lean Startup?
A pivot is a structured change in strategy designed to test a new fundamental hypothesis about the product, business model, or growth engine. It's not a complete restart, but a shift in direction based on validated learning that your current approach isn't working as expected. Examples include changing your target customer group, the core problem you solve, or how you make money.
Is the Lean Startup method only for tech companies?
No, absolutely not! While it became popular in the tech world, the principles of build-measure-learn, MVPs, and validated learning can be applied to any new business, product, or even project within an existing organisation. It's a mindset for reducing waste and increasing the chances of success by getting customer feedback early.
How small can an MVP be?
An MVP can be extremely small. It could be a simple landing page describing your idea to see if people sign up for more info. It could be a survey to gauge interest, a hand-drawn mock-up, a prototype built from cardboard, or even a video explaining your concept. The key is that it's just enough to test your riskiest assumption.
What if customers don't know what they want?
Customers often can't tell you exactly what new product they want. However, they are excellent at telling you about the problems they face, the frustrations they experience, and what they dislike about existing solutions. The Lean Startup approach focuses on understanding these problems through observation and conversation, and then testing solutions to see if they truly alleviate those pain points, rather than asking for specific feature requests.
How long should each Build-Measure-Learn cycle take?
The shorter, the better. Many successful Lean Startup practitioners aim for cycles lasting anywhere from a few days to a couple of weeks. The goal is rapid iteration and learning. Long cycles mean slower learning and greater risk. Short cycles encourage you to keep your MVPs truly minimum.
Final Checklist for Lean Startup
- Have you clearly defined the problem your idea solves?
- Do you have a testable hypothesis about how your idea will solve that problem?
- Is your MVP the absolute smallest version needed to test your core hypothesis?
- Have you launched your MVP to real customers?
- Are you actively collecting both quantitative (numbers) and qualitative (opinions) data?
- Have you analysed the data and honestly assessed if your hypothesis was correct?
- Have you made a clear decision to either "persevere" (continue) or "pivot" (change direction)?
- Are you ready to repeat the Build-Measure-Learn cycle based on what you've learned?
- Are you open to significantly changing your original idea if the feedback demands it?
