As asked
A business wants to adopt a new CRM. How would you run a gap analysis to decide what needs to change?
Sample answer outline
Define the desired future state in measurable terms, document the current state honestly, then list the gaps across people, process, data, and technology. For each gap, assess size, effort, and priority, and recommend whether to configure, customise, change the process, or accept the gap. A strong answer ends with a prioritised roadmap rather than an undifferentiated list, and flags gaps that are cheaper to solve by changing the process than the system.
Expect these follow-ups
- How do you decide when to change a process instead of customising the software?
- How do you quantify the size of a gap so leadership can prioritise it?
- What is the risk of customising a packaged CRM heavily?