Implementation and change

How do we make it work? Staying with you through the build and after go-live, until your team runs the platform and the old routes are switched off.

During the build

Procurement Code acts as your design authority through the build, making sure the policy, process and ownership decisions are made when the build needs them.

When it helps

You've chosen a platform and the build is about to start.

What you get

  • Policy, process and ownership decisions made when the build needs them
  • Decisions your team owns
  • A team ready to run the platform from go-live

After go-live

Adoption is checked against the baselines agreed at the start. Sponsors in each function stay involved, so the old routes are switched off rather than left running alongside.

When it helps

The platform is live, but people still use the old routes.

What you get

  • Adoption measured against the baselines
  • The old routes switched off
  • A team that runs the platform without outside help

In my last in-house role I led an orchestration rollout that went live in 18 markets on the same day.

Change runs through all of it

It starts in the first session and runs until the old routes are switched off.

The other functions

When a platform takes on checks legal, finance and information security used to do by hand, Procurement Code helps each function agree what it now owns.

Your procurement team

The shift is from processing requests to designing how the process behaves. Procurement Code runs a change impact assessment for each group and plans how each one moves to the new way of working.

Governance

A steering group across legal, finance, technology and procurement makes decisions in the order the build needs them.

Not sure which of these fits?

Tell me what you're weighing up and we can work out which of these would help.

Talk it through

Send a short note about the decision in front of you. I reply personally within a working day.

Get in touch