Enterprise Software Product Changes

We send notifications about changes to the email of the target audience and pass the news through leads. At the same time, we update links in all instructions and prepare guides for users. The document should be written in simple language so that the search for an answer takes a minimum of time. Our guides are best suited in the FAQ format for simple processes and video recordings with step-by-step instructions for larger ones.

By nature, people want to maintain a state of balance for as long as possible, so the emergence of new processes in a team can cause resistance or misunderstanding. User Care specialists come to the rescue. They answer all questions, help to make changes to the system and resolve difficulties. Analysts make sure that User Care knows about all the updates, what works and how, and in each case they will help to figure it out.

So which is better: an application or an old-fashioned Excel spreadsheet? There is no correct answer. Companies have different needs at different stages of growth. Some of them will close ready-made Enterprise solutions, others will require special development. Or maybe there is no need to reinvent the wheel at all, and the ubiquitous Google Docs will cope with the task. Be critical of ideas, take into account the financial capabilities of the organization and, of course, automate everything that can be automated.

Adding a feature to a software product

It is important to carefully interview stakeholders to take into account the needs of all children. We had a case where we changed the form in the old system. We were named the people who use it, we interviewed them and found out that one of the features is no longer relevant. In the process of working on a completely different functionality, it turned out that this particular function is very necessary for another person, whose goals we did not know about. But everything worked out - we returned the feature for revision.

Of course, you can hammer nails with a microscope. But it's better to do the right thing. Feature N will reduce the time spent by certain employees by N hours per week - sounds cool. If we understand that the solution will improve the quality of work and the development of the feature is economically feasible, we submit the idea for approval. The final stage is the actual creation of the product. After that, we test the trial version, collect feedback from stakeholders and gradually launch the project.

In a large company, the Importance / Influence matrix is ​​suitable for collecting feedback. For each of the subsystems, we highlight the roles, key representatives and the level of influence of a certain system on them. So we see who needs to be interviewed, who needs to get approval, who just needs to be notified about the changes. All data is put on the map.