A request for a new field, screen or automated step is often the start of a conversation. Before changing the setup, it helps to understand the work behind the request.
1. What is the team trying to do?
Choose a real task and walk through it with the people doing the work. Include the emails, spreadsheets and conversations around Microsoft Dynamics. These steps can explain why a seemingly small task takes so long.
2. Where does it get difficult?
Look for repeated entry, missing information, unclear ownership and steps people have to work around. Ask the team to show examples. This gives the change a specific problem to solve.
3. What would a better result look like?
Agree on what should improve. For a customer service team, that might mean less time assigning cases or fewer steps to find the information needed to answer a customer. Keep the intended result clear enough to check afterwards.
4. What needs to change?
Consider the process, the application configuration and the way people use it. Explain the options and the work involved. A clear view of all three helps the business decide what is worth doing.
5. How will the team test it?
Use real tasks to test the change with the people who will use it. Check the result against the problem you started with. Explain the new setup and record anything that still needs attention.
This is how Mason Pete approaches practical Microsoft Dynamics improvements: understand the work, agree on the change and check it with the team.