Any product/project development has a set of features that has to be developed at the end of the day. It is important to have the list/set of features however it isn’t a priority to prioritize them. This is a mistake that a lot of Business Analyst and Product Managers run into… for simple reason because its risk free. At the end one can blame it to the customer since the customer was the one who wanted the features.
One needs to understand what features need to be added to a product to meet customer needs by not prioritizing the features but to have a much broader view. One needs to know the underlying customer needs to the business model to the product road map to the go-to-market strategy. The ultimate goal for a product manager or business analyst should be Return on Investment.
Unfortunately, it is all too easy for product managers and business analyst today to fall into feature-focused development mode, especially for web applications and those developed using Agile methods.
A simple exercise can prevent help one break a trap. Ask yourself the age old and basic questions repeated time and again
- What is the purpose?
- What problem does it solve?
- Who is my target Customer/Persona?
- What are the alternatives to solve this problem?
- How important it is to solve this problem?
- Does this support the product strategy and roadmap?
It is easy and tempting to prioritize features and get the work done with a few extensions to your deadline; however it is important to identify the right feature to have a better Return on Investment.
No comments:
Post a Comment