Adding a feature always involves some research, which is part of the process. But what's really important is understanding the business impact it will have. I begin by evaluating the cost-effectiveness and the potential Full-Time Equivalent (FTE) savings each feature request could save us. Then, I think about how well it supports our business goals and I prioritize those that deliver the highest value with the least resource investment. I discuss the findings with the leadership team to make sure we're all on the same page before sharing the decisions with the stakeholders.

What is it that needs researching? New features should be prioritised by the impact they have on the user and the benefits they bring. It's important to split out the research needed into two groups: research to understand the impact on the user and research to understand how to build the new feature. Once you've prioritised the user, the priorities should be clear for how you find the solution.

When projects experience multiple new innovation FEATURE requests, they are more likely suited for the AGILE project management methodology -- where prototyping & continuous improvement are advantageous. During planning stages & initial research it is difficult to think of everything initially. Alternatively, maybe analysis & research were not fully done & expectation gaps will emerge. Key points of evaluation & resolution for newly expressed enhancements might include * What is RCA for these new features? * Are they new creative innovations or things missed in planning phase? * Do they impact the final project milestones? * Should we do them now or later? * Which FEATURES do most stakeholders prefer most? * Is there ROI in doing now?

Create solutions that people want to use—not just systems you want them to use. In my experience, solutions built without genuine user input rarely gain meaningful adoption. When designing systems, tools, or processes, involving users early and frequently is essential. Their insights should drive feature prioritization, ensuring that what we build truly meets their needs and aligns with their workflows.

Welcoming various feature requests along with research often takes one to make hasty decisions to meet the deliverables. One can opt to Analyse Impact, Prioritise and Research for the item list. Analyse Impact: Involves initial research to estimate the impact it would have on business, system and end user. Prioritise: Rank as per the system requirements and/or dependent modules. Research: Perform various system and user related research mapped alongside evaluation metrics from KPIs.