Startups and Product ManagementThe concept of Product Entropy                            Amarpreet Kalkat
WhyMost technology startups started by engineersInherent strengths in engineering, not as much     in product design or co...
Who Am ICo-founder @ Ciafo. Co-creator of Frrole & Travelomy   Have built 8+ internet products, 3 from scratchFrrole pseud...
#1Product Definition Fluid vs Concrete
#2Product Roadmap  Exist || !Exist
#3Product Thinking Input vs Output Effort vs Impact
#4       Goal Maximizing overall   business value,given the constraints
#5     StrategyProduct vs Brand vs     Execution
#6      ApproachPlaying to your strength
#7        FocusProduct you are building           vs  the solution you are         creating
#8    CatchNot planning for   execution
EntropyThermodynamics: A property used to determine the  energy not available for work in a thermodynamic  process.Statist...
Product EntropyThe unnecessary work done by           a user to accomplish his objectiveis the entropy of your product.
Thanks.@amarpreetkalkat   @frrole
The Cathedral And The Bazaar Rules1.    Every good work of software starts by scratching a developer’s personal itch.2.   ...
Upcoming SlideShare
Loading in...5
×

Startups & the Product Management Perspective

468

Published on

Engineers tend to start most of the technology startups. While this gives them an inherent advantage as far as engineering the product goes, it also tends to put them at a disadvantage when it comes to designing (non-technically) and commercializing the product.

This slide deck takes up the key concepts from PdM that apply to startup-mode products. This is not a case for having Product Managers onboard, 80% of the startups don’t need a dedicated PM.
Towards the end, it introduces the funky concept of Product Entropy.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
468
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Startups & the Product Management Perspective

  1. 1. Startups and Product ManagementThe concept of Product Entropy Amarpreet Kalkat
  2. 2. WhyMost technology startups started by engineersInherent strengths in engineering, not as much in product design or commercialization Does not apply to all engineers
  3. 3. Who Am ICo-founder @ Ciafo. Co-creator of Frrole & Travelomy Have built 8+ internet products, 3 from scratchFrrole pseudo-mentioned on WSJ, Forbes; TNW called Frrole top tweets better than Twitter top trends
  4. 4. #1Product Definition Fluid vs Concrete
  5. 5. #2Product Roadmap Exist || !Exist
  6. 6. #3Product Thinking Input vs Output Effort vs Impact
  7. 7. #4 Goal Maximizing overall business value,given the constraints
  8. 8. #5 StrategyProduct vs Brand vs Execution
  9. 9. #6 ApproachPlaying to your strength
  10. 10. #7 FocusProduct you are building vs the solution you are creating
  11. 11. #8 CatchNot planning for execution
  12. 12. EntropyThermodynamics: A property used to determine the energy not available for work in a thermodynamic process.Statistics: A measure of the disorder of a closed system.Information Theory: A measure of the uncertainty associated with a random variable.
  13. 13. Product EntropyThe unnecessary work done by a user to accomplish his objectiveis the entropy of your product.
  14. 14. Thanks.@amarpreetkalkat @frrole
  15. 15. The Cathedral And The Bazaar Rules1. Every good work of software starts by scratching a developer’s personal itch.2. Good programmers know what to write. Great ones know what to rewrite (and reuse).3. “Plan to throw one away; you will, anyhow.”4. If you have the right attitude, interesting problems will find you.5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.7. Release early. Release often. And listen to your customers.8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.9. Smart data structures and dumb code works a lot better than the other way around.10. If you treat your beta-testers as if they’re your most valuable resource, they will respond by becoming your most valuable resource.11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.12. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.13. “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.”14. Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.15. When writing gateway software of any kind, take pains to disturb the data stream as little as possible-and never throw away information unless the recipient forces you to!16. When your language is nowhere near Turing-complete, syntactic sugar can be your friend.17. A security system is only as secure as its secret. Beware of pseudo-secrets.18. To solve an interesting problem, start by finding a problem that is interesting to you.19. Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×