? Start by categorizing feature requests based on impact and urgency. ?? ? Prioritize requests that align with long-term business goals. ?? ? Balance high-profile client requests with the needs of regular users to maintain overall user satisfaction. ?? ? Consider the potential benefits of each request for a broader audience. ?? ? Communicate with high-profile clients about timelines and explain your prioritization process. ??? ? Involve the team in decision-making to ensure fair prioritization. ?? ? Use data to evaluate the value each request brings to the product. ?? ? Keep both clients and users informed on progress and decisions. ??

Do not add any feature unless it solves meaningful problem for majority of your customer base Request from high profile customer could add high tech debt to your platform Access weight of problem before action Every request is important, understand what can be acted first and what can be parked for later

In my experience, start by evaluating the potential long-term impact of the feature for all users. High-profile clients may push urgency, but it’s crucial to assess whether the request aligns with broader product goals. Always consider resource availability and ensure that every decision supports both immediate needs and future scalability.

A high-profile client request must be balanced with a regular client's demands. It requires a strategic approach to how to prioritize these requests, that is, to start by categorizing them according to their potential impact by how much it is aligned to the business goals of the firm and the value for the users. Allow both types of users to sit down with you to give their feedback and understand your needs. Then create a transparent scoring system through objective evaluation based on criteria such as urgency, resource availability, long-term benefits, and more. Maintain stakeholders whose priorities and decisions are communicated regularly.

I would like to tackle this using below approach 1. Weigh both feature requests with respect to Strategic theme / Current state / User base / segmentation / financial impact / effort and opportunity cost 2. Get collaborative / diverse perspective from all stakeholders. 3. Evaluate how each request aligns with overall product strategy, operating model, health and wealth of product in terms of long-term goals. 4. Be ruthless, empathetic as well as practical in prioritization in both request. 5. Transparently communicate trade off, scoped out or delay in serving the deferred request maintaining rapport and futuristic relationship.