More often than not, you will have limited or less resources than you would want. Be it more developers or budget to experiment or anything else, it will be less than what you would ideally want. In such a case, one should focus on below 3 aspects: [1] Ruthless prioritization Spend good amount of time in prioritization. If you are able to prioritize right, half the battle is already won. [2] Play by the strengths When you have limited resources, focus on the right allocation. Play by the strengths of each person in the team. [3] Innovative out-of-the-box solutions As it is said, "Necessity is the mother of invention", likewise, such situations forces you to think hard and innovatively. Come up with unique solutions to your problems.

Effective resource allocation for high priority requests allows you to get the maximum value out of the limited resources you have at your disposal. It improves team well-being & morale in tough times. To achieve this one must undertake the below measures: 1. Notify stakeholders & set clear expectations on the focus areas. Prioritize based on factors like impact, strategic alignment, effort required, resource availability & strengths 2. Identify automation areas during the development phase like QA automations, effective code repository and documentation. Prioritize automations for long term gains 3. Make sure to monitor resource allocation & make adjustments if required. Refine priorities based on customer feedback and blockers

Go for high/moderate business impact + high/moderate feasibility. A critical thought here is that this approach over a consistent basis would neglect the craft and creativity associated with PM. But here’s the thing - with limited resources, the outcomes often have to obey the above framework- then it is the skill of the product manager to deliver such features in a creative manner.

The feature that focusses on the unique experience or the main problem solving feature is the one which I should prioritize as it is more important to solve a problem first and if you did that well after that everything comes up like UI/UX and some more simple features that help us in retention and to give the user more reason to used our application.

When resources are limited, prioritize feature requests based on three key criteria: impact, alignment, and effort. First, assess the potential impact on customer satisfaction, growth, or revenue. Prioritize features that solve critical pain points or offer significant value to users. Second, ensure alignment with the product vision and business goals to avoid distractions. Finally, evaluate the effort required in terms of time, complexity, and resources. Features with high impact, strategic alignment, and low effort should take priority for the best return on investment.