ESM only works when both the delivery and the governance hold.

Vendor-supplied project management is optimised against supplier scope and timelines. That's its job. Customer-side control is a different discipline. It represents the company's outcomes, constraints, and operational reality inside delivery, which the vendor PM isn't positioned to do. The two roles aren't in conflict. They're complementary, and programmes that have both typically deliver better outcomes.

A standard programme manager coordinates. Customer-side control intervenes. We own the pressure points that decide whether the platform becomes a business capability or a collection of custom patterns. That means pushing back on scope drift, challenging acceptance logic, aligning the CMDB to operational reality, and making risk visible before it becomes a go-live problem.

Yes. The Strategic Project Engagement is designed to work on new programmes and on programmes that have already drifted. The analysis phase establishes the current state of scope integrity, decision throughput, and delivery drift, and the control set gives leadership the tools to steer from wherever the programme is now. Stabilisation is a known pattern for us — particularly with ServiceNow programmes in prolonged hypercare.

The typical engagement runs over eight to ten weeks for the governance setup, analysis, and initiation package. The ongoing customer-side control presence continues for as long as the programme needs it. Most engagements run through to controlled go-live and into the early operational phase.

Yes. The customer-side control methodology is platform-agnostic. The governance structures, use case discipline, and CMDB alignment work applies regardless of whether the company is implementing ServiceNow, Jira Service Management, or another enterprise platform. Platform-specific expertise is applied where relevant, but the customer-side control model doesn't depend on it.