Webinars

When Your SAP Programme Hits Turbulence — What to Do in the next 20 Days

brian.lavery@limelight.consulting (Brian Lavery) — Fri, 05 Jun 2026 09:37:24 GMT

When Your SAP Programme Hits Turbulence — What to Do in the next 20 Days

At some point in most large SAP programmes, something happens that changes the conversation at board level. A deadline is missed. A stage gate fails. A budget is challenged. Confidence drops. From that moment, everything the programme team does is viewed through a different lens.

The question is not whether that moment is serious. It is. The question is what you do in the 20 days that follow — because those 20 days determine whether the programme recovers or compounds.

6 Change Challenges

jayne.mather@limelight.consulting (Jayne Mather) — Tue, 05 May 2026 18:11:04 GMT

6 Change Challenges

Visibility drops. Alignment frays. Saturation builds. Most teams only name these problems after they have already stalled the programme.

7 Deadly Data Sins

graham.stewart@limelight.consulting (Graham Stewart) — Tue, 05 May 2026 17:58:40 GMT

The 7 Deadly Data Sins

Data is the most underestimated workstream on every S/4HANA programme. By the time most teams realise that, it is already causing delays.

Programme Transformation: The Need for Speed

brian.lavery@limelight.consulting (Brian Lavery) — Tue, 05 May 2026 17:39:20 GMT

Your board wants it delivered faster. Your SI wants more governance. Something has to give — but it doesn't have to be control.

Every S/4HANA programme is under pressure to move faster than ever. The risk is that speed and governance get treated as opposites. They are not — but getting the balance wrong in either direction kills programmes. This webinar is a practical conversation about where the line is, and how to stay on the right side of it.

Composable Architecture

gordon.kelly@limelight.consulting (Gordon Kelly) — Tue, 05 May 2026 16:51:36 GMT

Composable architecture: strategic advantage or expensive distraction?

Every SAP landscape conversation now includes composable architecture. But before you adopt it, you need to understand what it actually means for your programme, your integration strategy, and your ability to govern a more complex technology estate.