CRM Implementation Issue Log
This is a practical guide to building a issue log for a crm implementation project — a register of problems that have occurred and need resolving, adapted to the realities of deploying a customer relationship management system to improve sales and service.
What a Issue Log is
A issue log is a register of problems that have occurred and need resolving. For the full concept and how it works in general, see Issue Log. On a crm implementation project it plays the same role, tuned to this kind of work.
Why it matters for a CRM Implementation project
CRM Implementation projects live or die on deploying a customer relationship management system to improve sales and service. A well-built issue log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how crm implementation projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
CRM Implementation-specific considerations
Tailor the issue log to the risks that most often derail crm implementation projects:
- Poor data quality on migration
- Low user adoption
- Integration with existing tools
Example
On a real crm implementation project, the issue log would be shaped by deploying a customer relationship management system to improve sales and service. In particular, it should explicitly account for the project’s biggest risks — poor data quality on migration, low user adoption, integration with existing tools — rather than treating them as afterthoughts.