How do you validate that your startup is solving a real problem for real customers? How to build a tight, cross-functional, disciplined team to develop and ship your MVP as quickly as possible? How do you deal with competitors, and turn competition into an advantage. This version was delivered at Product School on September 15, 2016.
3. About me…
17 years in tech startup industry.
Founded a consulting firm, ran it for a decade.
Early adopter of both Agile + Lean Startup.
Coaching enterprise product and tech teams.
Worked on 6 startups. Doing my 7th now.
Wrote book StartupPatterns.com - Release date: Sept. 30!
5. Product Market Fit
Solve a really painful problem for a real customer.
Do it as fast as humanly possible.
Make it difficult for anyone to catch up with you.
10. Persona Tips
Use paper and sharpies.
Always include a sketch.
Demographics should inform behaviors.
Behaviors should inform problems.
Don’t model real people.
12. Problem Interview Tips
Be nice and friendly.
You’re not selling something. Call it research.
Listen more than you talk.
Have someone else take notes for you.
Say, “tell me more about that” when you hear something interesting.
Count things to add up later.
13. Solution Interviews
Don’t combine with problem interviews.
Lowest fidelity solution first. Start with your voice, then paper, then maybe
software.
Don’t tell them how to use your solution. Observe and listen.
This is not your actual product. Don’t get caught up in the details.
Get their email address for later.
14. Solving the Right Problem
Understand the customer using personas. √
Conduct problem interviews. √
Conduct solution interviews. √
Iterate, as needed. √
16. Building Products Quickly
Define the work with user stories.
Visualize the work with a Kanban board or similar.
Teams should be cross-functional, dedicated, co-located.
Optimize for time with space, and vice versa.
32. Tip: Co-location results in casual, social behaviors that build trust.
Trust helps teams move faster.
Trust also helps reduce turnover.
33. Tip: Remote teams requires more communication.
More communication over distance results in slower feedback loops.
Slower feedback loops increase cycle time.
34. Building Products Quickly
Define the work with user stories. √
Visualize the work with a Kanban system. √
Use cross-functional, dedicated, co-located teams. √
Optimize time and space. √
36. Managing Competition
Don’t worry too much, or too little, about competition.
If there is no competition, you’re probably in trouble.
Competition helps you focus on what matters.
37. Worry Just Enough
Competition means there is business out there.
Don’t focus your strategy around what others do.
Segment! You can’t build everything for everyone.
38. Understand the Competition
Problem interviews should reveal how customers solve their problem now.
Some competitors are really partners. Integration can be a good strategy.
Only compete directly where it aligns with your vision.
39. Product Market Fit
Solve a really painful problem for a real customer. √
Do it as fast as humanly possible. √
Make it difficult for anyone to catch up with you. √