7 Reasons Why Your Product Will Fail

7 Reasons Why Your Product Will Fail

Seven things your users think that will cause your product to fail

  1. “I don’t like it”
  2. “I don’t even want it”
  3. “I don’t even know how to use it”
  4. “I am happy with what I have”
  5. “I don’t want to pay for it”
  6. “No one else is using it”
  7. “I don’t trust it”

And what things you can do to over come this

Follow the deck to see where you can use techniques like:

  1. Rapid Prototyping
  2. Wire-Frames
  3. Reference Products (X of Y for Z)
  4. Gap Analysis
  5. USP Identification
  6. Product Definition
  7. Experience Design
  8. User Interface
  9. Habit Building
  10. Empathy Maps
  11. Product Migration
  12. Product Marketing
  13. Product Pricing
  14. User Research
  15. Business Models
  16. Go To Market
  17. Product Marketing
  18. Product Branding
  19. Product Support
  20. Product Reviews
  21. User Psychology

Sharing

SlideShare: https://www.slideshare.net/ddiinnxx/7-reasons-why-your-software-will-fail

SpeakerDeck: https://speakerdeck.com/ddiinnxx/7-reasons-why-your-software-will-fail


 

Five Buckets Model for Product Management

5-buckets-of-product-management

Inspired by The Five Competencies of User Experience Design by Steve Psomas,  ‘Five Buckets’ – Explained by Jonny Schneider and 5 Buckets of Business Analysis by Jiangmei Kang, I created a version for Product Management.

The 5 Buckets Model for Product Management

The Five Buckets is a model to describe the various capabilities of a Product Manager. This model list out important capabilities and suggests them to be competent in a subset of capabilities based on what their focus / interest is.

The 5 Capabilities of Product Managers (ProMa) identified are:

Five Buckets of Product Management

Influencing

  • Rallying opinions around the Product value
  • Active listening
  • Evangelism
  • Articulation of value
  • Connect Business, Users, Techies and be their advocate in Product decisions
  • Establish common language
  • Fill the communication gap
  • Stakeholder engagement
  • Problem solving
  • Decision making
  • Conflicts resolution
  • Jedi Mind Tricks
  • Elevator pitches
  • Quips, anecdotes, story telling
  • Personal leadership
  • CxO level conversations

Synthesis

  • Take inputs from various sources and synthesize them into coherent vision
  • Build Product Strategy
  • Product Design, Innovation, User Research keeping inputs and behaviors in mind
  • Work with Business Analysts, Experience Designers, Developers, stakeholders, contributors, builders, consumers, etc.

Prioritization

  • Roadmapping
  • Track and Manage the Delivery Progress
  • Manage and Prioritize the Product Backlog

Business Acumen

  • Sustainability of the business based on the product
  • Business case for ideas/product/innovations/incremental innovations
  • Pricing
  • Market scoping
  • Market research
  • Market size
  • Market opportunity
  • Product – Organization fit
  • Product – Market fit

Domain Knowledge

  • Ramp up at needed pace to get sufficient Domain Knowledge
  • SME or strong Design background or strong Development background

Some Key Thoughts

  • As with other versions, everyone has the combination of two or more capabilities. Nobody can be expert in all five areas.
  • Influencing is a basic and key competency for ProMa to be effective.
  • Prioritization (roadmapping, tracking, etc) and Synthesis (gather inputs and make sense of conflicting demands) are key day to day activities of a ProMa guided by right Business Acumen (business value of anything that crosses them).
  • For situations where Domain Knowledge is important, being an SME helps. Else, as a Generalist, ramping up to have sufficient knowledge of domain works.

Speaker Deck

Thanks to fellow ThoughtWorkers Sachin Sapre, Nagarjun Kandukuru, Kartik Narayanan, Vijayalakshmi K R, Kshama Tikmani and Manish Kumar for the feedbacks at various stages.