The leadership, accountability, and organizational readiness behind successful transformations.

Joint Insights from Emerson Human Capital and FS/4Ascend

Large-scale SAP transformations rarely begin with doubt.

• The platform is proven
• The roadmap is defined
• The system integrator is experienced
• The steering committee is active

And yet, many SAP S/4HANA programs miss timelines, erode confidence, strain budgets, and fall short of the value they promised.

When that happens, the instinct is predictable: blame complexity, scope, configuration, or SAP itself. That instinct is usually wrong.

As Florian Stursberg, Founder of FS/4Ascend, puts it, “SAP programs don’t fail because people aren’t capable or committed. They fail because accountability stops at workstream borders — and authority doesn’t extend across them.”

FS/4Ascend sees SAP failure where governance breaks down, where delivery discipline weakens, and where executive control proves thinner than the status reports suggest.

Emerson Human Capital sees the same failure from the organizational side: leadership behavior is inconsistent, readiness is overstated, communication is mistaken for change, and the business is asked to absorb more than it can realistically sustain.

The conclusion is the same: Technology isn’t usually the problem. Leadership and organizational readiness are.

We set SAP up to fail.

Most SAP programs do not fail suddenly. They fail gradually, then visibly.

The visible breakdown shows up late — in integration, testing, cutover, hypercare, or adoption. But the enabling conditions were usually approved much earlier.

Decision rights were left blurry to avoid friction. Business capacity was overestimated to preserve the timeline. Data ownership was treated as a downstream problem. Governance became a reporting routine instead of a control mechanism. Communication was allowed to masquerade as change management.

By the time the program looks unstable, it is usually behaving exactly as leadership designed it to behave.

This is why the strongest SAP programs are not just technically well-managed. They are governed with clarity, challenged with independence, and reinforced with serious organizational change discipline.

SAP isn’t an obstacle; it’s a mirror.

In other words, SAP does not create dysfunction. It exposes it.

• Weak decision rights? They show up in design drift
• Unclear data ownership? It surfaces during migration
• Overloaded teams? It becomes visible in testing compression
• Sponsor indecision? Turns into scope creep, delayed trade-offs, and expensive ambiguity

Florian notes, “Integration risk lives in the gaps. If no one owns the seams between workstreams, your program is exposed — no matter how green the plan looks.”

That point matters because the most dangerous SAP failures rarely begin inside a single workstream. They build in the seams between business and IT, between design and readiness, between executive intent and delivery reality.

For Emerson, the same pattern shows up on the people side. Founder Trish Emerson has long emphasized that transformation success hinges on leadership behavior. “Change doesn’t fail because employees resist it. It fails because leaders underestimate what it takes to prepare people to succeed.”

That is our shared insight. SAP forces clarity where ambiguity once survived. It demands structural discipline and behavioral discipline at the same time.

“Aligned” isn’t “owned.”

Many struggling programs share a familiar pattern: steering committees are active, slides are approved, risks are socialized, and dashboards still look reassuring.

But, when the trade-offs become expensive, when timelines tighten, when defects expose process weakness, and when the business needs clear direction, no single individual owns the outcome.

Florian explains, “Decision forums don’t equal decision ownership. When everyone agrees, accountability quietly disappears.”

A program is not governed because people meet. It is governed when leaders make decisions explicit, identify cross-stream accountabilities, and challenge the system integrator, the business, and each other before risk becomes irreversible.

That is also why independent oversight matters.  Firms like FS/4Ascend are positioned outside system-integrator incentives and implementation revenue models, which allows them to challenge assumptions, validate design and delivery decisions, and protect business outcomes even when those conversations are uncomfortable.

Organizational bandwidth is the real constraint.

Many SAP timelines are technically ambitious — and organizationally unrealistic.

Business leaders are expected to run operations, design future-state processes, cleanse data, execute testing, prepare teams, participate in training, support cutover, and still maintain business performance.

Florian says it directly. “It’s fantasy planning — timelines that only work if nothing slips, no one is out, and decisions happen instantly.”

From Emerson’s vantage point, this pressure shows up as adoption strain. Trish Emerson  emphasizes the human capacity problem. “You can’t layer transformation on top of an already maxed-out organization and expect performance to improve. Capacity is a leadership decision.”

That line should be taken literally. Capacity is not a project inconvenience. It is an executive choice. When leaders refuse to remove competing priorities, backfill critical roles, or protect SME time, they are not asking for resilience. They are approving failure on installment.

The constraint in most SAP programs is not configuration complexity. It is human bandwidth.

Communication is not change.

Many organizations equate communication with readiness. Town halls, emails, and executive updates might create visibility. They do not, by themselves, create adoption.

Rory McKenna, director of Emerson’s Change Management line of business, says, “Communication is the paint. It’s important — but it’s not the foundation.”