Design thinking for a CRM adoption challenge

Design thinking is a problem-solving approach that applies the principles of design to human behaviour. It’s relentlessly customer-centric, and it uses simple templates and maps to keep the focus on the people you’re solving for rather than the solution you happen to like.

The stages

1. Empathize - understand your customers. Observe and ask questions to learn what they actually want and need.
2. Define - name the problem. Identify the common challenges and what customers truly desire.
3. Ideate - generate ideas. Produce many possible solutions without chasing perfection.
4. Prototype - build a quick, rough version of the solution to test.
5. Test - put it in front of customers, gather feedback, adjust.
6. Implement - once the solution is validated, commit the resources to build it for real.

Example: low user adoption of a new CRM

Say Company XYZ rolls out a new CRM, and adoption among sales reps is poor. Design thinking gives you a way through:

• Empathize - sit with the reps. Where do they get frustrated? What slows them down?
• Define - pin down the root causes (too many clicks, unclear value, missing data) rather than blaming “resistance to change.”
• Ideate - brainstorm improvements: interface changes, automation, training, incentives.
• Prototype - mock up the interface changes quickly.
• Test - try them with a small group of reps and listen.
• Implement - roll out what worked, then keep iterating on feedback.

Conclusion

Design thinking is an incredibly simple yet remarkably effective technique. For CRM adoption especially - where the technology is rarely the real problem - a customer-centric, iterative approach beats a top-down mandate every time.