Sample readout Illustrative

What an Executive Risk Scan readout looks like.

This sample shows the kind of evidence leaders receive at the end of a Risk Scan: where adoption is at risk, how aligned your leaders are, and the gap between how leaders see the program and what the evidence shows.

Sample excerpt, not a full report. This page shows a small selection of findings from an illustrative SAP S/4HANA program in the design phase. A full Executive Risk Scan report goes much further. The scores, quotes, and findings here are representative and are not drawn from any client.

Overall adoption risk

Elevated

Three of five conditions at or below 2.5 on the evidence

Sponsor strength

ModerateVisible at kickoff, quieter since

Leadership alignment

LowFunctional leaders describe the goal differently

Change capacity

StrainedTwo other initiatives land in the same quarter

Perception vs evidence

Leaders see a healthier program than the evidence shows.

Leadership & Purpose Workflow & Role Clarity Workforce Trust & Readiness Enablement & Support Measurement & Sustainment

Leadership view (interview ratings) Evidence-based score

Scores by condition

Where the gap is widest.

ConditionLeader viewEvidenceGap
Leadership & Purpose4.13.2−0.9
Workflow & Role Clarity3.62.4−1.2
Workforce Trust & Readiness3.42.7−0.7
Enablement & Support3.82.5−1.3
Measurement & Sustainment3.22.1−1.1

Scale of 1 to 5. The largest gaps, in Enablement & Support and Workflow & Role Clarity, are where leadership confidence is most likely to hide adoption risk.

Top adoption risks

Ranked by impact on value.

Each risk is rated on likelihood and impact, backed by evidence from leader interviews and program artifacts, and paired with owned actions and the sponsor decision needed to move it. Three of the risks from the sample register are shown here.

#RiskConditionLikelihoodImpactRatingAct by
R1People leaders cannot coach their teams through go-liveEnablement & SupportHighHighCritical8 weeks before go-live
R2Role changes are not reaching the people affectedWorkflow & Role ClarityHighMedium-highHighBefore UAT
R3No business owner for adoption after go-liveMeasurement & SustainmentMedium-highHighHighNext steering committee
R1

People leaders cannot coach their teams through go-live

Enablement & SupportLikelihood: HighImpact: HighCritical

What we found

  • Interviews: 6 of 8 leaders said people leaders will train the same week as their teams.
  • Training plan: people leaders are scheduled in the final training wave, with no early access.
  • Change plan: no manager toolkit, talking points, or coaching guide is planned.
  • Pattern: Enablement & Support shows the widest gap of any condition, with leaders rating it 3.8 and the evidence at 2.5.

"Our managers will be learning the screens the same week as their teams." Operations leader (illustrative)

Why it matters

About 140 people leaders support roughly 1,400 end users across six sites. When managers cannot answer basic questions, every issue goes to the help desk, hypercare volume spikes, and teams quietly rebuild old workarounds in the first month.

Leading indicator to watch

Share of people leaders who complete early access and a toolkit briefing six weeks before go-live. Target: 90 percent.

Recommended actionOwnerBy when
Move people leaders into an early training wave with sandbox accessTraining lead8 weeks before go-live
Issue a manager coaching guide, talking points, and an FAQ for the first two weeksChange lead6 weeks before go-live
Run weekly manager huddles at each site through hypercareSite operations directorsGo-live through day 30

Sponsor decision needed: approve backfill so people leaders can be released for one day of early training.

R2

Role changes are not reaching the people affected

Workflow & Role ClarityLikelihood: HighImpact: Medium-highHigh

What we found

  • Change impact assessment: describes process changes, but not what changes for each role.
  • Interviews: 5 of 8 leaders could not name the three roles that will change the most.
  • Decision log: 41 design decisions change approvals or handoffs, and none have been shared outside the project team.
  • Pattern: Workflow & Role Clarity scores 2.4 on the evidence, 1.2 points below how leaders rate it.

"We have changed approvals, but I am not sure anyone outside the project knows yet." Finance leader (illustrative)

Why it matters

The approval changes sit in procure-to-pay and month-end close. If people learn about them in training, gaps surface late in testing, shadow spreadsheets appear, and the first two closes after go-live are at risk of running late.

Leading indicator to watch

Share of the six most affected roles with a "what changes for me" summary reviewed by their manager before UAT. Target: all six.

Recommended actionOwnerBy when
Convert the change impact assessment into a role-level view for the six most affected rolesChange leadWithin 3 weeks
Have functional managers walk their teams through the role summariesFunctional leadsBefore UAT
Turn the decision log into a short monthly change bulletin for affected teamsPMOMonthly through go-live

Sponsor decision needed: make functional leads accountable for communicating role changes in their own areas.

R3

No business owner for adoption after go-live

Measurement & SustainmentLikelihood: Medium-highImpact: HighHigh

What we found

  • Program plan: the project team rolls off 30 days after go-live.
  • Benefits register: owned by finance, with no adoption measures attached.
  • Governance charter: no business owner is named for adoption after go-live.
  • Pattern: Measurement & Sustainment has the lowest evidence score of any condition, at 2.1.

"Once we go live, the project team moves on." Program leader (illustrative)

Why it matters

The benefits in the business case, such as lower inventory and a faster close, depend on people using the system as designed for months after go-live. Without an owner and measures, workarounds become permanent and no one sees the gap until the benefits fall short.

Leading indicator to watch

A named adoption owner and three agreed adoption measures, with baselines, approved at the next steering committee. Target: in place before go-live.

Recommended actionOwnerBy when
Name a business owner for adoption who stays accountable after the project team rolls offExecutive sponsorNext steering committee
Agree three to five adoption measures and capture baselinesAdoption owner and PMO4 weeks before go-live
Build a 90-day reinforcement plan with check-ins, refreshers, and recognitionChange leadBefore go-live

Sponsor decision needed: name the adoption owner and extend adoption reporting to 90 days after go-live.

What the full report includes

This page is a sample. The full report goes deeper.

The items below are highlights. This is not a complete list of deliverables.

  • A detailed assessment of all five adoption conditions, not just the highlights
  • The complete adoption risk register, with every risk rated, evidenced, and owned
  • Interview themes by stakeholder group
  • Full readings on sponsor strength, leadership alignment, and change capacity
  • The evidence behind each finding
  • An executive readout session with your sponsor and leadership team

Prioritized next moves

What to do in the next 30 days.

  1. Reset sponsor visibility: a short message from the sponsor at each remaining milestone.
  2. Align functional leaders on one plain-language case for change.
  3. Start manager preparation now, beginning with the sites that change the most.
  4. Name an adoption owner and draft the 90-day adoption measures.