This article continues the series exploring the root causes of product failure. Even when you target the right users, and identify which of their problems are important to solve, you may still fail to solve the problems sufficiently.
Market Driven Competitive Advantage
Your strategy should be driven by the needs of the market. Becoming market-driven is critical to intentional product success. But it is not enough to understand your market. You have to sustain your understanding, and take advantage of it, competitively.
Flashback: This Week in the Past on Tyner Blain [Feb 9]
A look back at the best from this week in the past.
User Adoption ROI
You want your software to be used, not to sit on the shelf. You can’t achieve the ROI of your software if people don’t use it. And you can’t achieve the ROI of your software by forcing people to use it either. Some will fail to achieve the benefits, and […]
Don’t Make Your Products Too Simple
Joshua Ledwell wrote a short article expressing his perspective on designing software that is neither too simple nor too complex. He also links to some excellent other articles on the topic.
Product Life Cycle and the ROI of Agile Development
The product life cycle is a description of the presence or behavior of a product in the marketplace over time. The framework for description is a function of the sales volume of the product versus time. Over time, products are created and introduced, and sales grow, peak and decline. The product life cycle uses phases to describe these different periods in the life of a product. Understanding the product life cycle is also key to calculating the ROI of agile development.
Flashback: A Year Ago This Week on Tyner Blain [2006-02-10]
A look back at the best from a year ago
Prioritization With ROI and Utility
Prioritization with ROI is generally thought of as a quantitative analysis. For hard ROI, that is true. For soft ROI, it is anything but true. You have to make a prediction of the utility of the requirement or feature. That predicted utility is based on our expected utility, which is based on your past experiences. Your past experiences are reflected in remembered utility, which is a function of experienced utility. How can you know with certainty, and use that to prioritize requirements or features?
Flashback: A Year Ago This Week on Tyner Blain [2006-01-06]
A look back at the best from a year ago.