Search blog, projects, service or people.

We are committed to transforming SAP projects into performing people through structured training and knowledge management. With SAP expertise since 2003, 36,000+ certifications delivered, and a proven methodology that ensures your Go Live is on time, on budget, and sustainably successful.

Zugang

Timeline and milestones

The project plan changes. The training plan follows.

The training timeline is tied to the phases of your project, aligned to the phases of SAP Activate®. Deadlines are tracked, sessions recalculated and risks scored. When the project slips, we adjust the training plan in minutes instead of days.

74 % of SAP projects take longer than planned, with an average delay of 6 to 8 weeks. When go-live moves, someone has to reschedule hundreds of training sessions while keeping dependencies and trainer availability in mind. By hand, that takes 40 to 60 hours. We do it in 15 minutes, and training stays in step with the project.

What we do

  • Training milestones are tied to the phases and gates of your project.
  • Deadlines are tracked automatically, with dependencies and lead times for every session.
  • When the project plan changes, we recalculate the entire training plan in minutes.
  • Risks are scored continuously: too little time, trainer bottlenecks, knowledge that fades before go-live.

How we work

Every session is linked to your project's master plan, with explicit rules such as “Module 2 training after CRP2, at least 3 weeks before go-live”. Lead times for preparation and invitations calculate themselves, and buffers absorb small deviations.

When the project plan changes, and it will, we carry the new dates through the entire training plan in one go. Dependencies are recalculated, conflicts come with a suggested solution, trainer availability is re-checked, and the messages to everyone involved are ready as drafts. What takes more than 40 hours by hand is done in 15 minutes.

Scoring runs alongside. It shows where there is too little time between two milestones and where trainers overlap. It also shows where training happens too early and knowledge fades before go-live, and where it gets too tight. Colors show at a glance where someone needs to look.

Dependencies

What has to happen before what is fixed. No wrong sequence, no cascading delays.

Rescheduling in one go

A change to the project plan runs through the entire training plan, with conflicts and solutions.

Seeing risks early

Continuous scoring with warnings for compression, conflicts and readiness gaps.

Frequently asked questions

We take the milestones from your project plan, from the tools your PMO already uses. They become anchors for training. When the project plan changes, we update the training plan accordingly.

Every delay is recalculated, even several in a row. All earlier versions are kept, so you can see how the plan evolved, for lessons learned and for the conversation with leadership.

Yes. What happens if go-live moves from March 15 to April 30? You compare trainer demand, readiness and risks of the options and take a decision to the steering committee.

Ideally in the Prepare phase of SAP Activate, when the project plan is taking shape. Then training milestones can still shape the master plan. We can also join mid-project and bring order to training that is already running.

Is your project explaining a lot right now?
Let's talk.

Together we look at which parts of the toolkit help your project.