feature-creep_thumb25255B1325255D

Too Many Bells and Whistles Will Not Sell a Product

Too Many Bells and Whistles Will Not Sell a Product

Too Many Bells and Whistles Will Not Sell a Product
Technical entrepreneurs love to compare the number of features in their product to competitors, and they love to keep adding features -- just because they can. Unfortunately, this approach often turns off mainstream customers, who find the result hard to use. Even worse, this “feature creep” often makes the final product late to market, sluggish and more expensive than competition.
“Focus” is the key to success in a startup, and a minimum viable product (MVP) that does a few things better than anyone else will get more attention quicker from your market. From that base, you can then iterate more effectively, based on customer feedback, to add additional features that really expand the market. Early adopters, who love to count features, are not your major market.
As a former developer, experienced technical entrepreneur, and an advisor to many startups, I recommend that every technical startup adopt and live by some strict strategic and organizational rules to counteract the urge and risks of feature creep. These include:
Separate requirements gathering from product implementation. Every startup team needs a “product owner” role who is not an engineer or coder to collect from customers, prioritize and document required features. Then developers size the implementation alternatives, and startup executives draw a line based on vision, costs and funding.
Define and enforce role and decision authorities. Developers should get the last word on implementation, sizing and duration alternatives. Marketing and product owner negotiate the minimum viable product level based on competition and customer expectations. Financial executives set staffing budgets and monitor spending.
Communicate and commit to a formal development process. With agile and other incremental development processes, schedule and track the allowable time boxes -- one to four weeks -- per cycle.;

Read Also:
Optimizing Project Staffing to Improve Profitability with Cortana Intelligence


Chief Analytics Officer Spring 2017

2
May
2017
Chief Analytics Officer Spring 2017

15% off with code MP15

Read Also:
Data Could Be the Next Tech Hot Button for Regulators

Big Data and Analytics for Healthcare Philadelphia

17
May
2017
Big Data and Analytics for Healthcare Philadelphia

$200 off with code DATA200

Read Also:
The land grab for farm data

SMX London

23
May
2017
SMX London

10% off with code 7WDATASMX

Read Also:
6 Leadership Behaviors Drive Continuous Innovation

Data Science Congress 2017

5
Jun
2017
Data Science Congress 2017

20% off with code 7wdata_DSC2017

Read Also:
Big Data or Not Big Data: What is question?

AI Paris

6
Jun
2017
AI Paris

20% off with code AIP17-7WDATA-20

Read Also:
Artificial intelligence swarms Silicon Valley on wings and wheels

Leave a Reply

Your email address will not be published. Required fields are marked *