In our earlier article From Fashion to Function: Is CRM Adoption Driven by Hype or Real Business Value? We explored the journey of Customer Relationship Management from trend to necessity. While the popularity of CRM systems is undeniable, the real question has shifted from:
“Should we implement a CRM?”
to
“How do we implement CRM successfully?”
This article delves into that “how.” Specifically, we explore the complex, often underestimated domains involved in CRM implementation, from the orchestration of project management, through the nuanced challenges posed by stakeholders and users, to the final, pivotal measure of success: the impact on customers. At the end of the day, CRM is not about software, it is about relationships.
The CRM Implementation Landscape
CRM adoption today is almost universal in today’s growing businesses. Yet, despite widespread enthusiasm, a significant percentage of CRM projects fail to deliver anticipated results. Why? The issue rarely lies in the technology itself, as most modern CRM platforms offer robust features and scalability. A mistaken choice can always happen, when the tech solution is chosen in lack of a strategic planning.
The real problem lies in implementation. CRM is unique among IT projects because it touches nearly every department and it is in fact more about processes that impact the customer experience. CRM isn't just about digitising processes, it’s about transforming how people work, communicate, make decisions, while it should enable a more customer-centric approach than a resource-centric one. Prioritising customer needs, expectations and overall the experience. The success of CRM thus hinges not on purchase, but on its strategic execution.
Recent discussions have reignited debates about the value of Project Management, particularly in the IT industry. Notably, Tom Gilb asserts:
We acknowledge this criticism, yet argue that the real problem lies not in the concept of project management itself, but in how professional standards are (or aren’t) upheld—an issue common to many professions. When project management is executed with genuine professionalism, anchored in clarity, stakeholder value, and effective delivery, it remains a powerful driver of value creation.
Too often, critiques from some in the Agile community are directed at the role of project manager, rather than at poor execution or outdated practices. We suggest that the conversation should focus on raising the standard of project management, not abandoning the discipline altogether. Properly practiced, PM is not dead; it is an essential, value-creating function for clients and organisations alike.
CRM projects are inherently multidisciplinary, cutting across technologies, departments, and organisational culture. Unlike traditional IT projects that are bounded by strict system parameters, CRM demands flexibility and responsiveness to how people work. It should mirror the real processes, but also enable new envisioning and a substantial enhancement of how people work.
Successful CRM rollouts require:
Integrated timelines, balancing quick deliverables with a long-term roadmap
Effective resource orchestration, often combining internal subject-matter experts with external consultants and delivery partners.
Strong Interdepartmental coordination, among several conflicting goals and agendas and shared accountability
Outsourcing CRM project management to a certified PMP adds significant value. Today’s PMP credential is far more than “waterfall”: in its latest evolution, PMI has embedded deep Agile and hybrid delivery expertise as a core component of contemporary certification. Additionally, PMPs often undertake specialised Agile training, such as PMI’s own Agile Certified Practitioner (PMI-ACP), further reinforcing their ability to manage complex, fast-evolving business requirements, injecting external objectivity, rigorous governance, and experience across diverse verticals. When such a professional joins executive delivery teams, they serve as a dedicated change agent, bringing not only structure and governance, but also the agility and flexibility needed for successful CRM transformation
Project management is not merely a logistical necessity in IT, whilst it can be a primary value driver. Well-executed project governance ensures:
Budgets are respected and justified by ROI
Objectives are clearly aligned with business strategy
Risks, such as employee resistance or poor data migration, are flagged early and proactively addressed
Outsourced PMP project managers excel here, they’re trained to navigate high-stakes environments through proven internationally recognised methodologies (such as PMBOK and PRINCE2) and extensive Agile training. Thanks to updates to the PMP syllabus and certifications like the PMI-ACP - AgilePM, these professionals can shift between traditional, Agile, or hybrid approaches, tailored to context. As internal diplomats they succeed in bridging the gap between C-level and sales force: rally executives, users, and IT around a shared vision, turning business strategy into real-world outcomes
Product Owner is a strategic necessity in CRM, a preeminent solution enabler. A well executed Ownership of Solution may smooth choices over:
Features and Functions
Objectives and Deliverables
Stakeholders diverging agendas
A Product Owner has responsibility for the effectiveness of the overall solution, leading according to the organisation’s strategic commitment to the planned “Relationship Marketing”.
Use a phased rollout: Begin with high-impact departments then iterate.
Be Agile: define the budget and the timing, then adapt the scope.
Create a governance framework: Define decision rights, approval paths, and escalation channels.
Communicate continuously: Frequent touchpoints, cross-functional teams, then stakeholder continuous updates and engagement seeking are paramount.
Implementing a CRM affects, and is affected by:
Sales: Seeks better pipeline visibility
Marketing: Needs connectivity for customer segmentation and campaigns
Customer Service: Requires access to previous interactions
IT: Manages integrations, data security, and support
Leadership: Demands strategic outcomes like improved customer retention
These groups do not always share the same priorities. A well-planned stakeholder map is essential.
Stakeholders represent one of the major complexity in projects:
Resistance to change: Sales people may perceive a control purpose
Inertia: “We’ve always done it this way” is an evergreen among major roadblock in adopting anything.
Misaligned expectations: Managers and operators often change opinion on requirements and do not even clarify them properly.
User adoption can break your CRM project. Here’s how to achieve it:
Design for the functions: Users will adapt workflow accordingly
Deliver it: provide users instruction on the ready made system.
Let them learn alone: People will figure it out just using it.
Plan improvements quickly: Don’t wait for suggestions
If you do just the opposite you will engage your people.
At its core, CRM is designed to strengthen customer relationships. But without a clear customer-centric strategy, systems risk becoming an expensive Rolodex. Some relevant points of a customer-focused CRM implementation are:
Enhance personalised engagement
Provide consistent experiences across touchpoints
Enable proactive service through interactions
Empower decision-making by fresh, reliable data
Allow more time for direct actions
To determine whether the CRM delivers customer value, consider:
The trend of Net Promoter Score: are clients any happier?
The time of Sales Process Cycle
Trend of Retention and Repeat Business
Using a “before-and-after” analysis can make improvements easier to quantify and communicate.
Bad data: Inconsistent or unreliable data lead to frustration and lack of confidence in the CRM
Over-automation: IT people may be keen to exceed with automations, the right balance should be planned.
Siloing systems: Without integrations operators may get frustrated in data replication
System first: processes and features should enable more time for thinking and focusing on more valuable tasks: Customer-Centricity.
Executive sponsorship is non-negotiable
Without top-down support, projects lose momentum or get derailed by departmental politics.Change must be managed, not avoided
Change management should run in parallel to project timelines.CRM is an evolution
Expect multiple phases and evolving goals as the business grows and adapts.
CRM implementations are intricate, multi-faceted endeavors, weaving together technological advancements, human capital, and strategic foresight. While the CRM systems themselves inherently offer immense potential for organizational transformation and improved customer relations, their true value is unlocked not by their mere presence, but by the
meticulous quality of their execution,
the profound depth of stakeholder engagement,
the unwavering rigor of project management,
and, crucially, an unyielding focus on tangible customer outcomes.
These four pillars collectively form the bedrock upon which successful CRM adoption and sustained, impactful results are built. Considering that ultimately, the true success of a CRM implementation should not be solely measured by internal metrics such as team adoption rates or system proficiency. While these operational efficiencies are certainly beneficial, the paramount indicator of a successful CRM deployment lies in how effectively the entire company adapts to and fulfills the evolving needs of its end-customers. And in how they perceive their own experience in the interaction (relationship) with the brand:
We can say that a truly impactful CRM implementation extends well beyond streamlining internal processes; it fundamentally transforms the organization's approach to customer relationships.
This involves understanding customer preferences, anticipating patterns, and delivering personalized, consistent experiences across all touchpoints. Therefore, the ultimate benchmark for a CRM's efficacy is its demonstrable impact on the brand customers’ satisfaction, loyalty and, consequently, long-term business growth.
Select a project manager and a team that can really impact the project
Focus on gathering requirements before deciding anything.
Map and consult all stakeholders to select and plan features
Choose phased implementation to allow iterative learning
Link CRM metrics directly to customer experience KPIs
Invest in change management and user training from day one
Focus: The customer is not a data point, they are the ultimate reason why.
If you enjoy reading about the topic, I’d be happy to share more by subscribing to this newsletter.
No posts

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.