The Digital Wisdom Collective™
Your S/4HANA Program Has a Gap Nobody Owns
Between what the business needs and what the program delivers sits a blind spot that belongs to no one — where intent, process reality, and system decisions quietly drift apart. By the time it's visible, it's already expensive. The Canary is an independent signal layer that makes that misalignment visible while it's still reversible.
Most programs already contain some critical misalignment — it just becomes visible within weeks.
Book a Clarity Call
Miners carried a canary because it sensed what they couldn't - turning an invisible threat into a warning while there was still time to act.
The Canary plays that role for an S/4HANA program. It surfaces drift while it's still cheap to correct — because the value was never in fixing the mine. It was in the warning.
Every S/4HANA Program
The Only Question Is Whether You See It Early - or Pay for It Later
What Creates the Risk
Every S/4HANA program creates misalignment. The partner is accountable for delivery. The business owns the demand — what it actually needs the system to do. But the space between Demand and Delivery, where intent turns into design decisions, belongs to no one.
Change management, where it exists at all, works on adoption further downstream — and many programs don't have a defined change function at all. That's the point: this gap opens whether or not change management is in place. It isn't a maturity problem you can staff your way out of. It's structural.
What The Canary Does
The Canary sits alongside your implementation partner as an independent signal layer, making visible where alignment is breaking down across business, process, and system, while it is still reversible.
Built by Barbara Wittmann, who has worked inside ERP programs at every level, from SAP's Office of the CEO to global implementations.
Most programs don't fail because people make bad decisions. They fail because people make decisions without seeing the same reality.
The Pattern
Every S/4HANA Program Has the Same Blind Spot
The gap doesn't announce itself. It shows up in four recurring patterns — each one quiet at first, each one expensive by the time it's visible.
1
Business Intent Drifts
The original business case said one thing. Six months in, the program is solving a different problem and nobody noticed the shift.
2
Process Reality Gets Overwritten
The implementation follows best-practice templates. But the actual workflows, the ones people rely on, were never mapped. The system goes live. The workarounds multiply.
3
Decisions Happen Without Shared Context
Steering committees approve milestones. But the CIO, process owners, and implementation partner are each operating from a different picture of reality.
4
Risk Surfaces Too Late
By the time misalignment becomes visible, it is already embedded in configuration, training, and go-live timelines. Fixing it costs multiples of what preventing it would have.
The Pattern
Everyone Signed Off on the Same Goal. Almost No One Wants the Same Thing.
On paper the goal is simple — a new system — and everyone committed to it. But underneath that one written sentence sit goals that were never reconciled:
  • The project lead needs to deliver on time and on budget.
  • One business owner finally wants the requirement they've been denied for ten years.
  • Another wants to protect the process that is their competitive edge.
  • The implementation partner needs to stay inside the quoted price and timeline.
Every one of these is legitimate. None of them is wrong. And almost none of them are ever said out loud — which is exactly how the drift starts.
The Context
The 2027 Deadline Is Compressing Every Decision
SAP's end-of-maintenance deadline has created a market-wide rush. Companies are committing to S/4HANA programs under time pressure, often before their organization is ready to absorb the change. Implementation partners are at capacity. Internal teams are stretched. And the decisions being made now will lock in operating models for the next decade.
Partners at Capacity
Implementation resources are stretched across a compressed market. Your program may not get their best attention at every inflection point.
Internal Teams Are Stretched
The people who know how the business actually operates are being asked to run it while redesigning it. Something gives — and it is usually alignment.
Decisions That Lock In a Decade
What gets configured now defines how your organization operates through the 2030s. Speed without alignment is a compounding liability.
The companies that navigate this well will not be the ones who moved fastest. They will be the ones who maintained alignment while moving fast.
And the 2030 extended-maintenance option isn't the escape it looks like — it costs a premium, freezes your system, and the consultant market tightens exactly as everyone waits. Moving deliberately now beats moving under pressure later.
The decisions being made now are harder to reverse later, even when they turn out to be wrong.
What Changes
With Signal vs. Without Signal
Without an Independent Signal Layer
  • Misalignment becomes visible after it is already embedded
  • Decisions are made with partial or conflicting reality
  • The middle layer absorbs tension without a voice
  • Issues escalate late, often during testing or go-live
  • Corrections are expensive, political, and slow
With an Independent Signal Layer
  • Misalignment becomes visible while it is still reversible
  • Decisions are made with shared context across layers
  • The execution layer has a structured voice
  • Tensions surface early, before they harden into the system
  • Adjustments happen in motion, not after failure
This is the difference between reacting to problems and seeing them while they are still preventable.
The difference is not capability. It is visibility at the moment it still matters.
In most programs, these fault lines already exist, they're just not visible yet. The first step is not fixing them. It's seeing them clearly. Late misalignment doesn't just cost money, it costs control of the program.
How It Works
An Independent Signal Layer - Because No One Else Owns It
Two Entry Paths
Prevention or Correction - The Structure Is the Same
Early-Phase Alignment
When: At the beginning of the program
Focus: Prevent drift before it emerges
Establish shared orientation across stakeholders. Align business intent, process thinking, and system direction. Surface early assumptions and potential fault lines before they harden.
Mid-Stream Realignment
When: Once the program is already underway
Focus: Restore clarity under active system pressure
Identify where alignment has diverged. Surface hidden tensions and decision gaps. Recreate shared orientation across teams and partners while the program is still in motion.

Most companies engage once misalignment becomes visible. The ones who engage early avoid that situation entirely.
One Client. Two Perspectives.
C-Level
"Working with Barbara is always on point. She simplifies complexity without losing it, connects the dots, and brings in perspectives that strengthen my communication with the leadership team and the board. She also helps me see where adjustments are needed — in both leadership and execution."
— CIO, Global Multichannel Retailer
Execution Layer
"Barbara has supported us across every major project over the past five years. She is a trusted resource to listen, reflect, and connect the dots for those of us in execution — and acts as a neutral layer with partners when needed. She gives us a voice that is heard at the C-level."
— Director PMO, same organization
The Engagement
Two Levels of Engagement. One Continuous Signal Layer.
The value is not in driving decisions, but in making visible what emerges between intent and execution.
1
CIO Sparring
A confidential, bi-weekly space for the CIO or program sponsor to pressure-test decisions, navigate partner dynamics, and think through what cannot be said in a steering committee.
When I was in the seat of interim CIO, I realized what a lonely place that was. Everyone wanted to talk to me, but they all wanted to sell me software or services. What I needed was simply someone who could hash out issues with me and give me another set of eyes. Being in the weeds and in charge of IT is taxing. I can be that person who helps.
This is where strategic clarity is formed, before decisions cascade into the program.
2
Signal Lab
Concentrated at the start, light thereafter. The engagement opens with 4–6 weeks on-site — building the shared picture, establishing the relationships with the 5–8 key players, and surfacing the first fault lines while everyone is in the room. Once that foundation is set, the rhythm shifts: most of the work happens remotely, through the people closest to the program, with one on-site day a month to work the signal face-to-face. Not a fixed agenda — a flexible interface to where misalignment is emerging.
3
Monthly Signal & Alignment Summary
A written briefing delivered between Signal Labs. Early warning signals across the program. Emerging misalignments. A clear, non-political perspective on risks and tensions. Not a status report, a signal report.
4
Orientation Maps + Alignment Pulse
Living visual maps maintaining shared orientation across business intent, process reality, system landscape, and organizational dynamics, plus a monthly pulse showing where alignment is holding, weakening, or breaking down.
Signal Lab
A Structured Voice for Where Misalignment Actually Forms
Signal Lab works with a focused group of 5–8 key players — the people closest to where decisions are made and reality is experienced. In larger programs, it is not about reaching everyone. It is about reaching the right nodes of the system.
The format is adaptive, based on where signal is needed:
  • 1:1 conversations
  • Small group sessions
  • Targeted deep-dives into specific tensions or decisions
After the on-site start, the footprint is deliberately light — but light means precise, not absent. The signal keeps flowing between visits through the 5–8 people closest to where decisions are made; the monthly on-site day is where it gets worked, not where it's first noticed.
A Space Where
  • Assumptions get challenged
  • Tensions surface without politics
  • Different realities become visible
  • Decisions can be re-examined before they harden into system design
The Canary does not drive outcomes. It makes visible what the program cannot see from the inside.
In most cases, the first Signal Lab already surfaces tensions and misalignments that were previously felt, but not named.
Value
The Math Is Simple - and It's Not Small
S/4HANA programs typically run $5M–$30M+ for mid-market and upper mid-market companies — placing them in the category McKinsey and the University of Oxford studied across 5,400+ large IT projects (those above $15M). On average, those programs ran 45% over budget and delivered 56% less value than predicted, and the leading causes were not technical but unclear objectives, shifting requirements, and unaligned teams. Misalignment, not technology, is what makes them expensive.
Source: McKinsey & Company with the University of Oxford, 'Delivering large-scale IT projects on time, on budget, and on value' (2012).
$2–4M
Rework Cost
On a $10M program — caused by misalignment, not technology
$4–8M
Rework Cost
On a $20M program — embedded before it becomes visible
45%
Over Budget
Average cost overrun on large IT programs — driven by misalignment, not technology.

The Canary engagement runs at a fraction of total program budget. On a $10M program, that is the difference between a $200K signal layer and a $2–4M rework bill. The cost is not in discovering misalignment, it's in discovering it too late.
The Canary doesn't prevent the rework itself — it makes the rework preventable, by surfacing misalignment early enough for the program and the implementation partner to correct it before it hardens into the system.
Engagement Model
How It Works in Practice
Phase 1 includes both CIO Sparring and Signal Lab, establishing visibility, trust, and pattern recognition. Phase 2 continues Signal Lab as the program evolves through go-live and stabilization.
Phase 1 - Alignment
6 Months · Structured advisory engagement, billed monthly. Opens with 4–6 weeks on-site to build the shared picture and the relationships it runs on, then settles into a primarily remote rhythm with monthly on-site presence. Establishes visibility, trust, and pattern recognition. Alignment emerges over time — it cannot be rushed.
Phase 2 - Ongoing Coherence
12–24+ Months (Optional) · For the duration of the program. Maintains signal as the system evolves. Supports sustained decision quality through go-live and stabilization.

From the first on-site sessions, we build a single, shared view of how the organization actually operates across business intent, process flow, and system design — what I call an Operational Reality Mapping. It's not documentation. It's a decision-relevant map that makes visible where the layers connect and where they don't. For most organizations, this is the first time these layers appear in one frame, and the first fault lines surface in the conversation itself.
What This Is Not
Not a Project Role. Not a Delivery Function. Not Change Management.
A signal layer that makes alignment — and misalignment — visible while the system is still being built. Independent. Neutral. Designed for precision: maximum signal from the few nodes that matter, not maximum hours on site.
Not Embedded
Not part of the project team. Maintains independence and neutrality throughout.
Not Competing
Does not compete with your implementation partner, your project lead, or you. It sits alongside all of them and makes each one look good by surfacing problems while they're still cheap to fix.
Not an Informant
Not the board's spy, and not a reporting line on your people. CIO conversations stay confidential; the Signal Lab exists to give the execution layer a voice upward — not to watch them from above.
Not Heavy
Focused where misalignment actually forms. No heavy reports, no trying to reach everyone.
Misalignment is rarely the surprise. The timing of when you see it is.
At a Glance
Engagement Snapshot
CIO Sparring
  • Cadence: Bi-weekly, confidential (remote)
  • Who: CIO / Program Sponsor
  • Deliverable: Strategic clarity
  • Phase 1: 6 months
  • Phase 2: As needed
Signal Lab
  • Start: 4–6 weeks on-site to establish the shared picture
  • Then: primarily remote, with ~1 on-site day per month
  • Who: 5–8 key players
  • Deliverable: Signal & Alignment Summary
  • Phase 1: 6 months
  • Phase 2: 12–24 months
Investment: a fraction of total program budget
Ready to Add an Early Warning System to Your S/4HANA Program?
Barbara Wittmann
Founder, Digital Wisdom Collective™
  • Started at SAP in the early 2000s in the Office of the CEO, working on initiatives by Hasso Plattner, including early work with what became design thinking and agile collaboration models
  • 20+ years inside ERP and transformation programs, not as an observer, but as an operator who has sat in the lonely interim CIO seat
  • Named inventor on multiple SAP patents, and built a solution that was absorbed into the SAP Standard Portfolio — she helped build the product her clients are now migrating to, not just consult on it.
  • Has seen the full hierarchy of ERP programs, from executive decision-making to day-to-day system reality, understanding firsthand how taxing it is to be in charge of IT
  • Known for stepping into stalled programs, identifying what is actually broken, and finding the thread others missed
  • As interim CIO, found roughly 30% of an eight-figure IT budget hidden in the existing landscape and turned it into the business case for a greenfield S/4HANA approach.
  • Trained coach and facilitator, recovering consultant and accidental technologist
  • Founded the Digital Wisdom Collective to strengthen an organization's ability to help itself, building the human infrastructure required for technology to work
One Conversation. No Pitch.
30 minutes to see where your program may already be drifting and what that will cost you if it stays invisible. You leave with clarity. We find out if there's a fit.
© 2026 Digital Wisdom Collective™ · All rights reserved · www.digitalwisdom.co