Controlling Feature Bloat presented by Rishi Bhargava
Swiss Army Knife Approach <ul><li>Editor's Note:   </li></ul><ul><li>“ As anyone who has bought a cell phone over the last...
Demands on Product Management Implementation & Support Sales Customers Engineering Product Management
Other pressures on Product Management <ul><li>Competitive Matrix </li></ul><ul><li>Market Requirements </li></ul><ul><li>B...
Outcome: Lack of prioritization <ul><li>Product loaded with features </li></ul><ul><li>Half baked product </li></ul><ul><l...
Find your Way Out
Prioritize, Prioritize and Prioritize <ul><li>Learn to identify the real deal </li></ul><ul><ul><li>Get a macroscopic view...
Educate Technical Sales Team <ul><li>Focus on training the sales engineering team </li></ul><ul><li>Sales Engineering team...
Exceptions <ul><li>Make exceptions where you need to </li></ul><ul><ul><li>Competition Wins! </li></ul></ul><ul><ul><li>Bi...
Where to start? <ul><li>Organize all the feature requests in one repository </li></ul><ul><li>Identify the dimensions for ...
 
Upcoming SlideShare
Loading in...5
×

Controlling Feature Bloat Speaker Version

288

Published on

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

  • Be the first to like this

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

No notes for slide

Controlling Feature Bloat Speaker Version

  1. 2. Controlling Feature Bloat presented by Rishi Bhargava
  2. 3. Swiss Army Knife Approach <ul><li>Editor's Note: </li></ul><ul><li>“ As anyone who has bought a cell phone over the last couple of years can tell you, manufacturers love to cram as many capabilities into a product as possible—cell phones are now also cameras, music players, and game platforms. Why the rush toward &quot;feature bloat&quot;? Because consumers perceive value in this Swiss-Army-Knife approach and will pay for the added utility. The problem comes when the buyer actually starts to use the product. The increased complexity makes for a very unhappy consumer, who will look to return the product or look for another vendor in the future.” </li></ul>Feature Bloat: The Product Manager's Dilemma
  3. 4. Demands on Product Management Implementation & Support Sales Customers Engineering Product Management
  4. 5. Other pressures on Product Management <ul><li>Competitive Matrix </li></ul><ul><li>Market Requirements </li></ul><ul><li>Business Development </li></ul><ul><li>Resellers </li></ul>
  5. 6. Outcome: Lack of prioritization <ul><li>Product loaded with features </li></ul><ul><li>Half baked product </li></ul><ul><li>Confused sales team </li></ul><ul><li>Untrained implementation team </li></ul><ul><li>Failed implementations </li></ul><ul><li>and </li></ul><ul><li>unhappy customers! </li></ul>
  6. 7. Find your Way Out
  7. 8. Prioritize, Prioritize and Prioritize <ul><li>Learn to identify the real deal </li></ul><ul><ul><li>Get a macroscopic view of all deals </li></ul></ul><ul><ul><li>Understand the sales cycle in great depth </li></ul></ul><ul><li>Understand the deployment issues </li></ul><ul><ul><li>Work with deployment and support team to get input on top 3 product issues </li></ul></ul><ul><li>Where is the competitor beating you? </li></ul><ul><li>Identify long lead items </li></ul>
  8. 9. Educate Technical Sales Team <ul><li>Focus on training the sales engineering team </li></ul><ul><li>Sales Engineering team should know the state of the product </li></ul><ul><li>Gain confidence of the technical sales </li></ul><ul><ul><li>Expose your prioritization mechanism. </li></ul></ul><ul><ul><li>Share the internal roadmap </li></ul></ul><ul><li>Make them participate in prioritization </li></ul><ul><ul><li>Financial commitment from customers </li></ul></ul><ul><ul><li>Let them articulate the customer needs </li></ul></ul>
  9. 10. Exceptions <ul><li>Make exceptions where you need to </li></ul><ul><ul><li>Competition Wins! </li></ul></ul><ul><ul><li>Big Deals </li></ul></ul><ul><ul><li>Some other exceptions… </li></ul></ul><ul><li>Make people aware about the exceptions </li></ul>
  10. 11. Where to start? <ul><li>Organize all the feature requests in one repository </li></ul><ul><li>Identify the dimensions for prioritization </li></ul><ul><li>Communicate the priorities to whole company </li></ul><ul><li>Publish the roadmap for next 6 months </li></ul><ul><li>Set expectation that roadmap can change </li></ul><ul><li>Learn to say “No”. </li></ul>
  1. A particular slide catching your eye?

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

×