21
GetBadges Lean Startup by Example Justyna Wojtczak Krzysztof Hasiński

GetBadges - Lean Startup - Agile Poznań

Embed Size (px)

Citation preview

Page 1: GetBadges - Lean Startup - Agile Poznań

GetBadges Lean Startup by Example

Justyna Wojtczak Krzysztof Hasiński

Page 2: GetBadges - Lean Startup - Agile Poznań

What is…

Page 3: GetBadges - Lean Startup - Agile Poznań

What is GetBadges?

Page 4: GetBadges - Lean Startup - Agile Poznań

What is GetBadges?• 2014 - Badges for OpenSource tools

• 2015 - Gamification for programmers

• 2015 - Gamification Platform for IT teams

• 2016 - Game for IT Teams

• 2016 - Motivation platform for teams

• 2017 - ?

Page 5: GetBadges - Lean Startup - Agile Poznań

What is Lean Startup?

Page 6: GetBadges - Lean Startup - Agile Poznań

What is Lean Startup?

A temporary organization formed to search for a repeatable and scalable business model.

Page 7: GetBadges - Lean Startup - Agile Poznań

What is Lean Startup?

Page 8: GetBadges - Lean Startup - Agile Poznań

Lean Startup

Page 9: GetBadges - Lean Startup - Agile Poznań

So you’re a startup

Page 10: GetBadges - Lean Startup - Agile Poznań

GetBadges v0

• Badges

• Redmine + GitLab (Espeo’s infrastructure)

• Leaderboard

Page 11: GetBadges - Lean Startup - Agile Poznań

Fat startup

Page 12: GetBadges - Lean Startup - Agile Poznań

GetBadges v0

• Started at a hackathon…6 months to deliver

• Aimed at friends

• No market validation

Page 13: GetBadges - Lean Startup - Agile Poznań

Lean Canvas

• Looks for problem/solution

• Not focused on customer segments

• …or money flow

Page 14: GetBadges - Lean Startup - Agile Poznań

GetBadges v0

• Solves no real problem

• Has no real customers

• Not an MVP (no value)

Page 15: GetBadges - Lean Startup - Agile Poznań

GetBadges + Lean Canvas

• Done waaaaay too late

• Shows potential problem/solution fits

• Extracts unique value (game algorithm, integrations)

Page 16: GetBadges - Lean Startup - Agile Poznań

Experiments and Pivoting

• Experiment one - go around CEOs of software houses and find what problems do they have

• Result one - no problems at all, they’re doing great

• Lesson learnt - software houses are liars

• Pivot - none, ask developers

Page 17: GetBadges - Lean Startup - Agile Poznań

Experiments and Pivoting• Experiment two - go around devs of software

houses and find what problems do they have

• Result one - boring projects, problems with cooperation

• Lesson learnt - a simple game can make their work more enjoyable…for a week or so

• Pivot - prepare some predefined badges and arrange them into a game (with progress)

Page 18: GetBadges - Lean Startup - Agile Poznań

Experiments and Pivoting

• Experiment three - will somebody pay for our product?

• Result one - yes, but not for very long

• Lesson learnt - improve longevity, next time implement payments sooner

• Pivot - none, it works

Page 19: GetBadges - Lean Startup - Agile Poznań

Experiments and Pivoting

• Experiment four - can we get more software houses onboard?

• Result four - no, software houses are too tricky

• Lesson learnt - change customer profile

• Pivot - target product based companies

Page 20: GetBadges - Lean Startup - Agile Poznań

Experiments and Pivoting

• Experiment five - can we upsell or lower the churn?

• Result five - no, the game is not long enough

• Lesson learnt - if you want to make a game have a game designer

• Pivot - implement a game instead of just badges

Page 21: GetBadges - Lean Startup - Agile Poznań

GetBadges

• We’re not a poster child of lean startup

• But it helped us a lot

• When in doubt do this: