Procurement & S2P · People and adoption
Procurement Change Management: 10 Best Practices for Lasting Adoption
Help employees and suppliers adopt the new way of working, resolve the barriers they encounter and sustain it after the project ends.
At a glance
Look beyond attendance
- Understand the change for each audienceIdentify the task, impact and practical barrier.
- Check behaviour in real workUse evidence of successful process use, not attendance alone.
- Keep ownership after launchAgree support, handover and ongoing review.
On this page
Start with the behaviour
Procurement change management connects design to daily work
Procurement change management helps the people affected by a new process, policy or system understand, practise and sustain the behaviours it requires. It includes internal teams and suppliers, and starts while the change is being designed.
A trained requester may still send purchases by email if the new form cannot handle an urgent case. A registered supplier may still submit invoices through the old channel. Neither problem is solved by counting completed training sessions.
Define adoption as the intended behaviour in eligible real work: the right route is used, the task succeeds and required controls are followed. Then check operational results, such as rework, waiting time and service reliability. High usage can coexist with a difficult process.
This guide develops the people and adoption side of our procurement transformation best practices. That article covers the broader delivery foundations, including supplier data, process design, policies and guidance. The practices below build on those foundations; they do not replace agreed controls or exception routes.
Best practice 01 of 10
1. Give sponsors visible decisions and actions
A sponsor needs to do more than announce the programme. Agree which business outcome they support, what they can decide and which conflicts require their intervention. Name a change lead to coordinate adoption work and business managers who will reinforce it locally.
Ask managers to allocate time for user testing, training and launch support, with cover for operational work. A procurement lead cannot make finance or legal capacity available simply by putting their names on a plan.
Put it into practice: maintain a sponsor action log covering unresolved decisions, resources, manager briefings and escalation. For example, if two functions disagree about who handles rejected requests, obtain a decision and update the process before communicating it.
Best practice 02 of 10
2. Map the change from each audience’s point of view
Describe what people do today, what they will do differently and what becomes harder or easier. Include requesters, approvers, buyers, AP, legal, IT support and supplier contacts where affected. Segment by task and impact, not only department.
An approver may need to review requests in a different queue; a supplier may need new invoice details; AP may need to classify exceptions differently. Record access, language, accessibility, time-zone and workload needs alongside the process change.
Put it into practice: create a change-impact register with the audience, current and future task, likely barrier, action owner and validation method. Test assumptions with people doing the work. Use the example below as a starting point.
Best practice 03 of 10
3. Involve users before the design is treated as finished
Ask representative users to walk through normal transactions and awkward exceptions. Include occasional users and people outside the project team, rather than relying entirely on confident champions.
Use an approved test environment and realistic scenarios. Check the full hand-off: can a requester submit enough information, can the approver make the decision, and can operations complete the next step? Separate a usability problem from a missing policy decision or a technical defect.
Put it into practice: record the scenario, observation, issue owner, decision and retest evidence. Tell participants what changed following their feedback and explain decisions where a request cannot be adopted. Business acceptance should reflect working scenarios, not workshop attendance.
Best practice 04 of 10
4. Investigate resistance before choosing the response
Reluctance can expose a genuine problem: extra effort, unclear authority, unreliable access, an unhandled exception or fear of losing control. Ask for a recent example and observe the task before assuming someone needs another message or training session.
Match the response to the cause. Clarify an uncertain role; fix a demonstrated defect; agree operational cover for a capacity problem; explain a required control and its approved exception route. Escalate unresolved policy or resource conflicts to the accountable owner.
Put it into practice: keep a concern-and-response log with evidence, action, owner and feedback date. Check whether the barrier was removed. Avoid labelling a whole team “resistant” when only a few views have been heard.
Best practice 05 of 10
5. Give each audience a clear next action
Every communication should explain why the change matters, who is affected, what they must do, when it applies and where to find help. Managers need enough detail to answer questions about responsibilities and exceptions.
Communicate against confirmed milestones. If a process decision changes, update the guidance before asking people to act. Use one maintained source for instructions, with suitable formats and language support. For suppliers, validate the contact and track failed delivery or unanswered requests.
Put it into practice: maintain a schedule with audience, required action, channel, trigger or date, sender, owner and follow-up. An email sent or opened is communication evidence; completion of the requested task needs separate validation.
Best practice 06 of 10
6. Train for the work and check demonstrated ability
Build training around role-specific tasks, controls and exceptions. A requester needs to raise a valid request; an approver needs to decide within their authority; an AP colleague needs to investigate an exception. Include how to obtain help when the normal route fails.
Offer realistic practice, short reference guides and suitable sessions or recordings. Ask participants to complete a task without the trainer doing it for them. Record errors and support needs, then adapt the guidance or design.
Put it into practice: use a training matrix covering audience, task, format, access prerequisites, task demonstration and follow-up. Attendance establishes participation. A successful demonstration indicates readiness in that scenario; sustained adoption still needs evidence from real work.
Best practice 07 of 10
7. Support suppliers through their first successful transaction
Keep the existing supplier-readiness disciplines: agreed scope, validated contacts, reliable records and a controlled tracker. Tailor support to the supplier’s intended channel and transaction needs. Do not assume registration alone means they can transact.
Confirm that the supplier can access current guidance, understands the required information and knows how to raise a problem. Where appropriate, support an initial transaction and verify that it reaches the next team successfully. Use the agreed process for suppliers who need an alternative route.
Put it into practice: track contact validation, registration where required, task readiness, first successful eligible transaction, open barriers and the next owner action. Distinguish inactive suppliers with no transaction due from active suppliers struggling to adopt.
Best practice 08 of 10
8. Separate activity, readiness, adoption and results
Use four distinct questions: did people take part; can they perform the task; do they use the process in real work; and is the operation improving? The answer to one does not establish the next.- Activity: attendance or guidance distributed, with the intended audience defined.
- Readiness: successful task demonstrations, access confirmed and critical barriers addressed.
- Adoption: eligible work completed through the intended route, with controls followed and approved exceptions recorded separately.
- Operational results: rework, exception causes, elapsed time, backlog and service quality over comparable periods.
The procurement reporting guide explains how to define measures, validate source records and assign reporting ownership.
Best practice 09 of 10
9. Plan launch support and evidence-based exit criteria
Hypercare provides increased support after go-live. Plan the people, issue priorities, reporting route and escalation before launch. Include process and system expertise so a user is not passed between teams without an owner.
Review issues at a frequency proportionate to launch conditions. Identify whether repeated questions indicate unclear guidance, a defect, a missing decision or a capacity constraint. Fix the cause and communicate the response.
Put it into practice: agree exit criteria with the receiving operational owner: critical issues resolved or controlled, acceptable service performance, usable guidance, known residual risks and sufficient support capacity. Time elapsed alone should not end hypercare. Record owners and review dates for outstanding items.
Best practice 10 of 10
10. Make sustained adoption part of normal management
Name who maintains the process, system configuration, supplier guidance, training and adoption measures after the project team leaves. Keep improvement decisions within the established approval and change-control arrangements. Build new-joiner and refresher support into normal operations. Review process use after relevant demand peaks, staff changes or system updates. Use transaction evidence and user feedback to identify workarounds returning or instructions becoming outdated. Put it into practice: hand over a maintained improvement backlog, documentation, support routes and review calendar to named owners. Agree how each change will be approved, communicated and checked afterwards. Close an action when evidence shows the problem has improved, not simply when a new guide has been issued.Use the procurement operating model guide to define process owners, decision rights and hand-offs that sustain these responsibilities.
Practical client experience
Three examples of the work behind adoption
These published cases show specific delivery activities that support readiness and sustained use. Their outcomes are evidence about those engagements, not benchmarks or guaranteed adoption rates for another organisation.
Client example
Supplier relationships: engagement and training
At a UK company in a regulated sector, Denova’s embedded Supplier Relationship Manager mapped processes, established a single communication contact and engaged stakeholders who were cautious about a more formal supplier-management approach.
The case reports 42 or more suppliers trained, supported by training packs and onboarding sessions. It illustrates practical engagement and supplier preparation. The training total alone does not establish a measured rate of sustained supplier adoption.
Read the published account of the issues, support and reported outcomes.
Client example
Esker: connect training to implementation readiness
A global enterprise’s Esker programme had been delayed for four years before Denova’s involvement. An embedded consultant mapped procurement and AP processes, introduced structured SIT and UAT, coordinated defect resolution, supported the Oracle integration and trained business users.
The case reports a live environment and a documented process framework used by eight entities. Its lesson is the combination of working processes, testing, cross-functional coordination and user readiness. The preceding four-year delay is not Denova’s delivery duration.
Read the published account of the issues, support and reported outcomes.
Client example
Zip: documentation and ownership sustain the change
The Zip case describes unclear system ownership, undocumented processes and manual workarounds. Denova’s consultant gathered user pain points, documented workflows and production changes, improved configuration and transferred knowledge.
The account explicitly says formal metrics were not in place. It supports the value of documentation and ongoing ownership, without providing a quantified adoption improvement. Keep those responsibilities in the operational handover.
Read the published account of the issues, support and reported outcomes.
Copy and adapt
An illustrative change-impact and adoption-plan example
Fictional scenario: one business unit introduces a guided purchase-request form and an agreed invoice channel using its existing systems. Scope, controls and exception routes have been approved. The examples below are planning aids, not Denova client findings, service commitments or universal targets.
Use one record per affected audience and task. Assign interventions against actual readiness gates and the dates in your delivery plan; do not infer a fixed rollout sequence from this example.
Illustrative plan · Requesters
Raise a complete purchase request
Current → future and impact: Requests currently arrive by email. The new form requires a business owner, cost centre and justification. Occasional users must learn both the fields and the approved urgent-request route.
Barrier and intervention: Users are unsure which cost centre applies. Procurement and finance agree field guidance; representative users test a routine request and an urgent exception; managers reinforce the route.
Owners: Change lead coordinates the activity; the procurement process owner accepts the guidance; local managers arrange practice time.
Readiness, adoption and results evidence: Record attendance separately. Test independent task completion before release. After launch, review eligible requests using the form and the reasons for returns. Compare rework with the baseline; a form submission alone is not successful adoption.
Illustrative plan · Suppliers
Send an invoice through the intended channel
Current → future and impact: In-scope suppliers previously email invoices to several contacts. They need the agreed channel, required references and support instructions. Some contacts may be outdated.
Barrier and intervention: Validate contacts and scope, provide current instructions, offer targeted support and check the first eligible invoice where appropriate. Maintain an approved alternative route for legitimate exceptions.
Owners: Supplier enablement lead owns follow-up; AP confirms successful receipt and exception handling; the supplier’s contact completes its tasks.
Readiness, adoption and results evidence: Track failed contacts, readiness and first successful transaction. Measure eligible invoices successfully received through the intended channel, with clear exclusions. Track avoidable invoice returns and open support issues separately.
Illustrative plan · Operations and support
Resolve issues and maintain guidance
Current → future and impact: Questions previously depend on project-team contacts. A named operational team will triage issues, route decisions and maintain approved instructions.
Barrier and intervention: Rehearse cross-team incidents and an absent key colleague; check access and cover; agree knowledge transfer, issue priorities and escalation.
Owners: Service owner accepts the handover; process and system owners retain their decisions; named support roles maintain the knowledge base.
Readiness, adoption and results evidence: Use observed incident handling and unresolved issue age. Exit hypercare only when agreed performance, ownership, residual-risk and capacity conditions are met; set a review date for remaining actions.
Use the same record for each audience
Copyable change-impact and adoption-plan template
CHANGE AND AUDIENCE
Business outcome and change in scope: ___
Audience, task and affected population: ___
Current behaviour → required future behaviour: ___
Impact — roles, effort, access, controls and support: ___
Evidence source and assumptions to validate: ___
BARRIERS AND ACTIONS
Concern or barrier; evidence and business consequence: ___
Design / process / access / capacity / knowledge response: ___
User involvement and feedback to close: ___
Communication — action, channel, sender and follow-up: ___
Training — practice task, format and demonstration: ___
Supplier-specific support where relevant: ___
Action owner, decision owner, dependency and due date: ___
VALIDATION AND OWNERSHIP
Readiness evidence and acceptance owner: ___
Adoption measure — eligible population, numerator and denominator: ___
Operational result and comparable baseline: ___
Data source, limitations, target or trigger and review date: ___
Approved exceptions and unresolved barriers: ___
Hypercare escalation and agreed exit evidence: ___
Ongoing owner, deputy and improvement-review cadence: ___
Use the plan in reviews to decide what needs action: a corrected process, access fix, clearer instruction, more practice or a sponsor decision. Avoid treating every adoption gap as a training problem.
Keep its milestones aligned with the procurement transformation roadmap. Continue to use the existing Best Practices guide for the supplier-data, policy and operational foundations supporting this work.
Practical support