Good one, my perspective would be 1. First I will have a discussion with customer to understand their requirement completely. I would ask questions like why they need this feature asap, how is it impacting their business & their clients. 2. I would also verify how are they using our product currently and if by chance they have failed to explore the full potential that might serve their current problem, I would also ask them the data that they are tracking to ensure they have exhausted the options and have this entire discussion along with the sales team as well. 3. I would overlook the current roadmap what are we doing in next 4 months and the impact of it and do an analysis of the available resources, cost involved, business impact and convey to my stakeholders in case im going to continue serving the customer's need pushing other developments efforts beside.

Thank you for the video. Here are a few more points that can also be considered: If we need to inform the customer that it cannot be done, 1. and if there are no alternative workarounds, we can explain them the current agreed features as per the plan 2. Provide a potential timeline if we are planning it(requested feature) in future 3. Make them aware of upcoming features It is also possible that upcoming features might eliminate their need in the first place and give them an idea on how are we tackling the critical items first If we need to consider the feature, 1. The engineering team can be divided into two parts 2. Some members can work on it in the next sprint, while a few 'good-to-have' features can be swapped that will have minimum/no impact 3. Inform all the stakeholders if any impact might happen to the current high-priority items making sure everyone is aligned

one can also consider if the feature can help other clients, maybe include it in future roadmap and give that visibility to the client instead of outrightly saying a complete no, or try to see if an MVP version of the feature is possible to be made in the current sprint/roadmap by deprioritizing something else

@tryexponent

Жыл бұрын

Hi Shambhavi! That can definitely be a viable course of action depending on what the request is and how in line it is with your product's objectives. Great suggestion!

Overall a very good answer. I missed one item. For a large and strategic customer it is nearly always the case that one would want to offer some form of alternative. The worst case, in the scenario where there are simply no other decent options, is the ability to talk about future review in the longer term roadmap and then asking for additional detail. In practice, it should be very very rare that the answer of "no" is delivered for this type of scenario.

Great problem statement

How to start as a product manager

My question is .. why there is no discussion about the time needed for implementation . If we have enough time and it is important to customers, we can reprioritize and implement this.

@tryexponent

Жыл бұрын

Hey Naidu! You are right that implementation time does factor into evaluating the new advocated feature. However, the concept of having "enough time" is a bit misleading. When you spend time building this feature, you are spending time away from advancing your roadmap... unless your team allocates a certain number of hours a week to work on things not on your roadmap. Would love to hear your thoughts on this!

Too many YOU KNOWS