Why CRM, ERP and project administration systems only create value when people change the way they work.
A new CRM platform is introduced, but salespeople continue keeping their own notes and spreadsheets. Salesforce is implemented, but managers still cannot rely on the pipeline data. A new project administration system goes live, but employees enter information too late or interpret the fields differently.
An ERP solution is installed, but teams continue working around it through email, Excel and informal agreements.
The technology works. The organisation has invested. Everyone has received instructions.
So why are the expected results still missing?
Because installing new technology is not the same as changing the way an organisation works.
The invisible gap between implementation and impact
Technology providers are very good at demonstrating what their solutions can do. They explain the functionality, calculate the efficiency gains and show how their technology can reduce costs, improve quality or accelerate processes.
The business case is convincing. The technology is tested. The implementation plan is ready.
And yet, the promised impact often fails to materialise. Not because the technology is inadequate, but because the organisation has underestimated the most important factor in any digital transformation: people.
Consider the implementation of a CRM system such as Salesforce.
Technically, the platform can provide a complete overview of customers, opportunities, activities, forecasts and commercial performance. But that value only emerges when salespeople consistently record the right information, managers use the system in their commercial conversations and teams trust the data enough to make decisions based on it.
If salespeople see CRM as an administrative burden, adoption will remain low. If managers request separate Excel reports, employees quickly learn that the new system is not really leading. If data definitions are unclear, every team will use the platform differently. If the system is not integrated into meetings, decisions and daily routines, it becomes an expensive database rather than a commercial management tool.
The same pattern can be seen in ERP implementations, project administration platforms, planning systems and digital collaboration tools. The system may be fully operational, while the organisation continues working in the old way.
Why technically successful implementations still fail
When the human side of implementation receives insufficient attention, predictable problems emerge:
- Employees continue using personal spreadsheets alongside the new system.
- Information is entered because it is mandatory, not because people see its value.
- Data is incomplete, inconsistent or outdated.
- Managers do not use the system during meetings and performance conversations.
- Old processes remain in place, creating duplicate work.
- Employees develop shortcuts to avoid the intended way of working.
- Frustration with the implementation becomes frustration with the technology.
Eventually, the organisation concludes that the system does not work. In reality, the system may function exactly as designed. What has not changed sufficiently is the behaviour around it.
From selling a product to delivering an outcome
For technology providers, this creates an important strategic challenge.
Customers are not ultimately buying Salesforce, an ERP platform or a project administration system. They are buying the improvement these systems are supposed to create:
- Better customer insight and more reliable sales forecasts
- Higher conversion and stronger commercial performance
- More efficient project delivery and resource planning
- Greater control over costs and margins
- More effective collaboration across departments
That means technology providers must look beyond product delivery. They must also consider what their customers need to turn technical functionality into daily organisational practice.
For one of our clients in the technology industry, PAWLIK developed an implementation programme that placed people at the heart of the digital transformation.
The central idea was simple: create a group of employees who would not merely use the new technology, but actively help the organisation adopt it. We called them Change Ambassadors.
Make sense
The first phase focused on creating understanding and commitment.
During a large kick-off event, the organisation explained the purpose of the transformation, the strategic ambition and the role of the new technology. The CIO shared the wider mission, while PAWLIK and the technology partner introduced the implementation programme.
Employees could apply proactively for the role of Change Ambassador. Applicants completed the PAWLIK Agile Leadership Basic Scan. This gave us insight into their natural strengths, development areas and potential contribution to the ambassador team.
The selection was therefore not based solely on technical expertise. We also looked for employees who could communicate, influence others, navigate resistance and help colleagues translate change into everyday practice.
Make it real
The second phase focused on developing the Change Ambassadors.
Based on the client’s objectives and the insights from the scan, we designed a blended development programme. It combined online preparation, practical face-to-face training and structured follow-up.
While the technology partner trained employees to work with the new solution, PAWLIK concentrated on the behavioural side of implementation.
- Create understanding among colleagues
- Recognise and address resistance
- Translate the transformation into practical workplace behaviour
- Support colleagues without taking over their responsibilities
- Give feedback and encourage adoption
- Act as a bridge between employees, leaders and the implementation team
By running the technical and behavioural development tracks in parallel, employees learned both how to use the technology and how to make it work within the organisation.
Make it happen
The third phase started when the technology entered the workplace. This is the point at which many implementation programmes end. We believe it is where the real transformation begins.
PAWLIK change experts were present during the first stages of implementation to support the Change Ambassadors and address leadership and adoption issues as they emerged.
We also introduced a trainer hotline for situations in which ambassadors needed immediate support. As their confidence and experience increased, this support was gradually reduced. Online inspiration, targeted reminders and personal coaching helped maintain momentum after the initial launch.
The impact after three months
Three months after implementation, we measured the results against previously agreed KPIs and compared them with implementations by the same technology partner without the PAWLIK programme.
The difference was clear.
- The new technology was used more frequently and more effectively.
- Employees reported higher satisfaction with the tool, their ability to use it and its contribution to their work.
- Performance improved on the KPIs defined by the technology provider.
- Employees experienced less uncertainty and anxiety about the transformation.
- Overall workplace satisfaction increased.
The technology had not changed. The way people were prepared, involved and supported had.
Digital transformation is behavioural transformation
A CRM system does not create customer focus.
A project administration platform does not create project discipline.
An ERP system does not create collaboration.
A planning tool does not create ownership.
Technology can enable these changes, but people and leaders must turn its possibilities into consistent behaviour.
For technology providers, this means that commercial excellence can no longer stop at selling, configuring and installing a great product. The real opportunity lies in taking responsibility for the outcome the customer wants to achieve.
That requires a shift:
- From product to solution
- From go-live to adoption
- From functionality to everyday behaviour
- From technical training to organisational change
- From delivering technology to making transformation work
Because the value of a system is not determined by what it can do.
It is determined by what people actually do with it.
