Our slide deck from Podcamp Toronto hosted on February 26, 2011. Presentation was 45 minutes with Q&A.
Shared our process on building a product successfully with constraints. Topics included:
* Getting started quickly
* Establishing structure
* Creating a team
* Defining the problem
* Planning an approach
* Executing a build
* Finding the minimum
* Acknowledging mistakes
* Launching a product
Learn more about this event at http://2011.podcamptoronto.com or #pcto2011.
Contact us anytime @skanwar, @drupeek or http://jetcooper.com.
Exploring the Future Potential of AI-Enabled Smartphone Processors
How to Build a Product in 99 Days (Podcamp Toronto)
1. How to Build a Product
in 99 Days"
February 26, 2011
Podcamp Toronto
@skanwar
@drupeek
2. - You
k
- Andrew Pee Whatever You Do
- Satish Kanwar"
Jet Cooper
Jet Cooper
Rocketr
Task Ave.
O
LeanCoffeeT
TEDxToronto
LeanCoffeeTO
3. Disclaimers"
Terms and conditions of what you learn.
• There are no best ways, just better ways
• Practice is greater than theory
• It never stops changing
19. Define the problem"
How to articulate what you’re doing.
• What’s really grinding your gears?
• What is the opportunity?
• What is the hypothesis?
• Who has this problem? Use cases
• What is my business model?
22. Plan an approach"
How to get your blueprint.
• There is no strategy, only a hypothesis
• Make more decisions, more often
• Create iterations, make pivots
23. Familiarity vs. Adaptation"
Agile vs. Waterfall (and back again).
• Does this feel right?
• Project planning does not equal project reacting
• Frequency of communication is paramount
25. Execute, execute, execute, execute, exec
How to actually build stuff.
• Customer development principles
• Design to test hypotheses faster
• Develop in what you know best
27. Product: “It has to achieve this”
Design: “OK, we can suggest this”
Dev: “Sure, but we should consider this”
Customer: “Got it. What do I do next?”"
29. Find the minimum"
How to ask yourself the right questions.
• Set the foundation first
• Add operations in the right order
• Callout each individual assumption
• Are you moving with or against the currents?
32. Acknowledge mistakes"
How to justify your pace.
• Fail fast, but minimize how far you fall
• Pick your battles according to expertise
• Saying “no” is okay. Saying “no, because” is better.
39. Get back to work"
How to keep spending time.
• Talk about the product
• Make asks of the customer
• Now it’s time for a strategy
40. For example, in 99 days…"
We completed a product at 15% of plan.
• We spent $9,917.56 to get to market
• We made 759 git commits over 99 days
• We had 3 heated debates about a feature being MVP
• We lost 30 days from using square pegs in round holes
• We did 7 iterations - 2 over 30 days, 5 over 7 days
• We made it here with a business model – March 7 rollout