Project and change management

Full accountability for your SAP programme: planning, steering, stakeholders and risks. And change management that brings the organisation along instead of running it over.

SAP projects are rarely pure IT projects. They change workflows, responsibilities and habits across the whole organisation. A project manager who only maintains the schedule therefore falls short: the role is to drive decisions, keep dependencies in view and listen to the departments.

We lead SAP projects and programmes with clear accountability: a realistic plan, an honest status, clean escalation. And we take care of the side that gets shortchanged in many projects: the people who will work with the system after go-live.

Why clients get in touch

The project needs a new leaderThe current project manager is leaving, the programme keeps running, and the handover has to work within weeks.
The status is unclearThe reports are green, the gut feeling is not. An assessment should show where the project really stands.
The departments are not on boardThe system is almost ready, but the organisation is not. Training and communication are running late.
The cut-over is approachingThe go-live date is set, the runbook is missing, and nobody has planned a dress rehearsal.

Scope

What we take on

Individual roles or full accountability, depending on the programme.

Project management

Accountability for planning, budget, dates and quality, with transparent reporting to your boards.

Programme steering

Keeping several workstreams in step: dependencies, resources and the interfaces between them.

Stakeholder management

Management, departments and IT rarely speak the same language. We translate and keep everyone on the same page.

Risk management

Naming, assessing and treating risks early, before they turn into slipped dates.

Change management

Involving those affected early, building up key users and organising training, so the new system is actually adopted.

Cut-over management

Runbook, dress rehearsal and a go-live weekend where every step is rehearsed.

How we work

How we run projects

Step 1

Mandate and setup

Goals, scope, governance and a plan that fits the organisation rather than the textbook.
Step 2

Steering

Progress, budget and risks in rhythm, with a status that shows the situation as it is.
Step 3

Change and enablement

Communication, key user development and training alongside the build, not just before go-live.
Step 4

Cut-over and handover

Runbook, dress rehearsal, go-live and an orderly handover to the line organisation.

What you get

What our leadership looks like

An honest status

A status report that shows green when things are green. And red when they are red, while there is still time to react.

The organisation in view

A system the departments embrace is worth more than a perfect project plan.

Experience from many programmes

More than three decades of project practice in SAP programmes, from mid-sized companies to international rollouts.

Questions

Frequently asked

Do you also take over running projects?

Yes. It starts with a short assessment: where the project really stands, what the biggest risks are, what the next three months need. Then you decide how to continue.

Classic, hybrid or agile?

Whatever fits the organisation and the programme. An SAP implementation with a fixed go-live date needs different instruments than continuous development. We work with both and mix where it makes sense.

How much change management does an SAP project need?

More than most plans allow for. Anyone who starts thinking about the users at integration testing will hardly catch up. Communication and key user development belong in the plan from day one.

Contact

Does your programme need leadership or a second pair of eyes?

Tell us where your project stands. An assessment quickly shows what it needs.

Discuss your project