How can you update an information system for changing user needs?

Very true hence business analysis and documentation are the key.one more observation is the changing technology landscape . Technofunctional analysis of the requirements is the need of the hour

In my opinion, the above materials describe exactly the best method of making changes in the IS system, but I will say the order of their implementation more precisely. You must first talk to the end user and understand her information needs and the access she needs. After that, check the current status of the system and identify the things that need access and changes. Then, the desired accesses and related changes are checked with the rules of the organization and if allowed, the changes are applied.

Changing users need always create opportunity for building new systems or enhance the current one. It is always crucial to understand the current situation to assess the need, gaps and current enterprise architecture to enhance or replace the IS. In case the current team has existing team has big gap to assess the situation, leveraging Process Mining tools can be good option to understand current systems capabilities, gap with user and market needs. Most of the users are comfortable with current systems but as per new need there is possibilities to rewrite the systems based on new process designs and compliance.

It is very important to have clearly defined Objectives and requirements to achieve the required outcomes. Objectives could be based on change in business models, technology advancements and process change. Its always important to define the Objective to fulfill the future state and build the requirements around them. These are very helpful to analyze build vs Buy decision, customization or change with the best practices.Also its critical to have non functional (User & data volume, channels etc) with make sure it works with volume after complition.

Recently interacted with one CXO who passionately explained about his new solutions to custom develop in 9+ months and that will be ready soon for UAT. Co-incidently I have worked with one customer to implement a product in 3 months having similar functionalities. In fact after few weeks, same CXO reached out to us and given the contract to implement same product for his organization, due to significant delays, gap in requirement, changes in the market situation. It is critical to have clear scope & timelines when going for custom development. It is very important to have Show & Tell, Power User Reviews during Design and development to make sure there are no suprises during UAT and product / solution is developed as expected.