MVP Design Hacks
A successful startup/product company needs to master the art of validating early product ideas quickly and effectively. Whether you are building a product, service or a new feature, the two most important questions to find out early are:
- are we solving the right problem?
- if yes, how do we pitch the idea to the target customer to generate a favourable action?
During this session, we'll focus on various safe-fail experimentation techniques used by Lean Startups for quickly identifying and validating the customer's value hypothesis, without having to build the real product. You will leave this session equipped with various MVP design techniques, that will allow you to rapidly discover a viable product/service that delights your customers, without spending a lot of time and effort.
Traditionally, entrepreneurs believed that the only way to test their product/service hypothesis was to build the best-in-class product/service in that category, launch it, and then pray. Most often, products/services fail, not because they cannot be built or delivered. But because, they lack the market-fitment and customer appeal.
To avoid these risks, these days startups are focusing on building a "Minimum Viable Product" (MVP), a product that includes just enough core features to allow useful feedback from early adopters. This reduces the time to market and allows the company to build subsequent customer-driven versions of the product. Hence mitigating the likelihood of wasting time on features that nobody wants. MVPs are typically deployed to a subset of customers, such as early adopters that are more forgiving, more likely to give valuable feedback.
However the problem with MVPs is that companies still spend too much time building stuff and very little time learning. Don't forget the purpose of MVP is validated learning NOT building. This session will give you ideas on how to quickly formulate and test your value and growth hypothesis in a scientific framework using extremely cheap MVP techniques collectively referred to as MVP Design Hacks.
Outline/Structure of the Tutorial
- Quick examples of how 2 companies (startup and an established enterprise) had to find the right market fit the hard way.
- Need for MVP and how its is different from Design Thinking Flow
- Quick example of how others have hacked their MVPs and achieved their validated learning for a fraction of the cost
- Some examples from Edventure Labs (an Tech-Ed startup) - From Vision to 6 Pivots - Our journey and learning
- Introducing the big picture - "Vision - Strategy - Hypothesis - Safe-Fail Experiment - Validated Learning Cycle"
- Simon Sinek's Golden Circle (How great leaders inspire action) and how you can design MVPs to discover the "Why"
- Redefine MVP & understand that you don't have to build even a mini-version of your product to validate your hypothesis
- Learn how to maximise your validated learning for minimum investment
- Understand the importance of Safe-Fail Experiments and a few ideas on how to design them
- Learn the "Vision - Strategy - Hypothesis - Safe-Fail Experiment - Validated Learning" Cycle
- Understand how MVPs can be designed to discover the "Why" (based on Simon Sinek's Golden Circle)
Product Owners, Product Managers, Sr. Management, Startup Founders
schedule Submitted 5 years ago
People who liked this proposal, also liked:
Rajat Talwar - Pains and Gains of being a Full Stack DeveloperRajat TalwarFull Stack Dev at confengine.com / Co-founder poolmyride.comXnsio
schedule 5 years agoSold Out!
As the industry is shifting towards an Agile (Continuous Delivery) style for developing products and services, (whether startups or large established organisation), everyone today has to thrive by innovating and adapting to the latest trends in technology. They have to keep themselves ahead in the race to delight customers. Full stack developers are key players in experimenting and delivering value consistently using varied tools and technologies throughout the stack.
In this session I'll be share my journey of how I became a full-stack developer. Hopefully this will help others understand how they can target and plan to gradually become a full stack developer in their respective teams.
Also I'll highlight the following topics:
- What is the importance of a full stack dev?
- What tools/resources/languages in my experience work best for full stack developers?
- Downsides of being a full stack developer!