System dependencies
See which processes and activities rely on particular applications.
Understand the work around the system before you replace it.
Talk to the people who use it, follow the work around it and uncover the manual steps, dependencies and workarounds the new system will need to support.
The system is not always the problem.
A frustrating system does not always need replacing.
A frustrating system can be part of the problem without being the whole problem. Follow the work around it before deciding what the replacement needs to fix.
See technology through the work it supports.
Manual workarounds
Find where people compensate for technology.
Duplicate entry
Identify where people enter the same information multiple times.
Shared systems
Understand where different teams depend on the same application.
Upstream and downstream
See what happens before and after a system-supported activity.
Change impact
Understand what replacing a system could affect elsewhere.
Considering a CRM, ERP, practice-management or other core system change?
Start with the work that depends on it.