Health, Education & Government
›
HR & Talent
›
Workforce Transformation
Change Management
People decisions with significant organizational, financial, and cultural stakes.
Prosci
McKinsey
Kotter International
Accenture
Inside this journey
-
Pre-Discovery
Align sponsors, decision roles, and constraints before detailed diagnosis.
-
Stakeholder Alignment
Confirm executive sponsors, decision roles, timeline, and what ‘good’ looks like for each stakeholder.
Alignment Questions
Where This Conversation Begins
- Briefly describe the transformation you’re accountable for: scope, primary objective, and the trigger that started it (ERP, merger, shared-services, etc.).
- What is your target go-live or milestone timeline?
- Which role or person is the named executive sponsor today?
- Approximately how many people will the change touch (users, approvers, managers)?
- What single outcome would make this program feel unquestionably successful to you?
Is Sponsorship Actually Holding—or Just Performing?
- If I told you executive attention typically drops three weeks after kickoff, what makes you confident that won’t happen here?
- Who are the decision roles that must sign off at each major milestone (sponsor, approver, procurement, legal, IT change board)?
- Which sponsor behaviors are currently visible—are they actively removing obstacles, visibly advocating, or delegating to others?
- How has sponsorship behaved on recent transformations—did they stay engaged, or drift away? Tell a specific example.
- What formal governance or escalation path exists if a sponsor or steering committee signal wanes?
- Which of these would be the fastest lever to re-energize sponsorship if attention fades?
What Actually Happens Day-to-Day (Where Work Lives)
- When people must complete the new process under pressure, how often do they default back to the old way?
- Describe the current end-to-end process for a typical user task that will change—who touches it, systems involved, and handoffs.
- Where have you observed the most frequent failure modes today (data gaps, approvals missed, system errors, inconsistent role clarity)?
- How often do these failures materially impact business outcomes (cost, time-to-complete, compliance)?
- Who currently enforces the existing process—role/title—and how do they do it?
- Do you track any baseline metrics tied to current behavior (completion rates, error rates, time-to-task)? If so, what are the recent values?
The Invisible Blockers (Who Quietly Benefits From ‘How It Is’)
- Who in the organization has a clear incentive to keep the old way, even if leadership says change is desired?
- Where have you seen passive resistance show up before—delayed adoption, selective compliance, or informal workarounds? Provide a concrete example.
- How do middle managers feel about the new workflows—threatened, neutral, curious, supportive, or bypassed?
- Are there pockets (locations, teams, or levels) where cultural resistance is higher? Where and why?
- What informal power players or peer influencers would we need onside to shift norms quickly?
- Have you measured employee sentiment or readiness yet (pulse, survey, interviews)? If yes, what was the headline finding?
If Adoption Were Real (What Success Actually Feels Like)
- If we returned three months after go-live and adoption had stuck, what would you see, hear, and measure differently?
- Which measurable signals would prove behavioral adoption (choose all that apply)?
- What threshold would you set for ‘acceptable adoption’ at 30, 60, and 90 days (for example: 70% of users completing tasks via new system)?
- Whose perception of success matters most—finance (ROI), sponsors (strategic alignment), managers (ease of work), or frontline users (daily usability)? Rank your top two.
- What acceptance criteria would make you comfortable signing off at key milestones (pilot acceptance, staged rollouts, full go-live)?
- If adoption lags but KPIs improve in other areas, how should trade-offs be evaluated?
Experience the Solution—Not Just See It
- Imagine a complex, high-pressure scenario where the new process must succeed—what would be the single worst outcome and why?
- Which real-world scenarios should we rehearse with users to validate solution fit (month-end close, incident recovery, urgent approvals, high-volume transactions)?
- How do you prefer training and enablement to be delivered for champions and middle managers?
- What responsibilities should the champion network hold vs. the program team (escalation, coaching, local adoption metrics)?
- Which acceptance scenarios must be simulated and signed off before we consider wide deployment?
- What success stories or internal proof points would most convince skeptical managers to change behaviors?
What Would Make This Break (and How We Stop It)
- What is the single silent risk that, if unaddressed, would create a permanent adoption dip?
- How robust is your data and access readiness—are there known gaps that would block go-live?
- Which of these failure modes concerns you most: sponsor drift, manager resistance, data issues, or frontline rejection?
- What pre-deployment controls would you require to reduce risk (pilot with rollback plan, freeze periods, executive checkpoints)?
- Who would own real-time rapid response at go-live (title/role), and who is the escalation point if they can’t resolve an emerging resistance pattern?
- How long are you willing to provide intensified launch support before shifting to BAU sustainment?
Ready, Set, Decide—Practical Next Moves
- If we left this conversation without naming a concrete owner for adoption outcomes, how likely is the program to stall in your view?
- Which pilot scope would give you the fastest, least risky signal of adoption readiness?
- Which three immediate actions would you prioritize this month to increase odds of adoption success?
- What level of effort and time can your program team commit to champion activation and go-live rapid response?
- What would you like us to deliver first—a readiness assessment, sponsor alignment session, or champion pilot plan?
- Who else should join the next meeting to make decisions (names or roles), and when is the earliest you can commit to that session?
-
Current State Mapping
Document today’s processes, failure modes, resistance hot spots, and adoption baselines.
Current State
Tell Me About Today — Quick Tour
- In one sentence, how would you summarize how work actually gets done today where this change will land?
- Which parts of the organization will be affected? (select all that apply)
- Which core systems and tools are involved today? (select all that apply)
- Approximately how many users will be expected to adopt the new ways of working?
- What recent event or trigger made this change urgent?
Where Do Things Break When It Matters?
- What recurring failure have leaders learned to 'live with'—and why hasn’t anyone fixed it yet?
- Describe a recent critical incident where process failure caused a visible business impact. What happened and who noticed first?
- How frequently do you see handoff or approval failures that require rework?
- Which failure modes should we instrument from day one? (pick up to 4)
- When these failures occur, how do they typically surface—customer complaints, missed SLAs, finance reconciliations, executive escalation, or quietly in team chat?
- Who is formally responsible for resolving these failure modes today?
Who Really Decides and Who Quietly Resists?
- Which single role or group, if quietly opposed, could stop adoption cold even with executive buy-in?
- Map the sponsors and decision-makers involved (select all that apply)
- Which informal influencers or networks matter most to adoption (e.g., union reps, high-performing sites, local champions)?
- How engaged are executive sponsors right now on a 1–5 scale?
- Which groups have already raised clear objections, requested carve-outs, or asked for delay?
- How confident are you that middle managers will prioritize the new process over legacy workarounds?
How Do People Actually Work — Not How You Wrote It Down?
- What's one routine workaround people use today that would embarrass a sponsor if they saw it?
- Walk me through a day-in-the-life for two archetypal users who will be most affected (titles or roles).
- Which process steps are most commonly bypassed or manual? (select all that apply)
- When questions about the process arise, how long does it typically take for a definitive answer to reach the frontline?
- What guidance, job aids, or training do people actually use today—if any?
- How does it feel on the frontline when a process change lands—excited, anxious, skeptical, overburdened, or something else?
When Change Has Failed, What Did It Look Like?
- Think back to the last major change that underdelivered—what was the single human reason it failed?
- How did adoption evolve in that program—did you see a 'honeymoon' then a dip, a flat line, or steady improvement?
- Which early warning signals were missed or misinterpreted in that program?
- How were lessons from that failure captured and used (or ignored) afterward?
- What sunk-cost behaviors kept teams reverting to the old way despite evidence it wasn't working?
What Would Adoption Success Feel Like Day-to-Day?
- If adoption were irreversible, how would a frontline manager's day change in practical terms?
- List three measurable behaviors you would expect to see at 30, 90, and 180 days post-go-live.
- Which KPIs matter most for this program? (select up to 4)
- What would executives publicly celebrate as proof the change worked?
- What trade-offs are you willing to accept to secure adoption (e.g., slower rollout, narrower scope, extra budget for coaching)?
Signals, Metrics, and What You're Actually Watching
- Are the metrics you track encouraging the right behavior or are they creating perverse incentives?
- Which primary adoption and performance metrics do you currently monitor? (select all that apply)
- Which of those are baseline metrics vs. target metrics (briefly identify baseline and target where known)?
- How often are adoption metrics reviewed and who attends those reviews?
- What tools or dashboards currently capture adoption signals (select all that apply)?
Barriers You’re Pretending Are Solved
- What organizational truth are you quietly hoping won’t be tested during rollout?
- Rate readiness across these dimensions: people, process, data, technology, governance.
- Where are the largest capability gaps (e.g., manager coaching, data quality, operational capacity)?
- What political or cultural dynamics could derail adoption if not actively managed?
- Who is likely to push for exceptions or carve-outs and why?
Small Tests That Could Prove or Break This
- What would you rather learn now in a focused pilot than discover by surprise at go-live?
- Which micro-processes or user cohorts could we pilot that would give the most predictive signal? (select all that apply)
- What success criteria would make a pilot meaningful to your executive team?
- How much time and budget could realistically be allocated to a rapid pilot or readiness sprint?
- Who would need to be involved from your side to run a meaningful pilot (roles, not names)?
Next Steps: Where We Start to Close the Gap
- If you could guarantee one outcome by go-live, what must it be?
- Which stakeholders need immediate alignment to de-risk the program in the next 30 days? (select all that apply)
- What would be the single most valuable deliverable from a 4–6 week readiness sprint (pick one)?
- How would you prefer a change advisor to work with you on this: embedded in the program, advisory/check-ins, or a blended model?
- Who will be the primary point of contact by role/title for urgent decisions during readiness work?
- Given everything we've covered, how ready are you to run a focused readiness assessment now?
-
-
Outcome Discovery
Define target adoption outcomes, measurable success signals, and the risks that must be mitigated.
Discovery Questions
Putting Adoption on the Table
- What is the single change your transformation must deliver to be widely called a success?
- Who will notice success first—select the groups most likely to celebrate an early win
- When you picture people doing their jobs after the change, what specific behaviors are you expecting to see day-to-day?
- How concerned are you that a post-go-live adoption dip could become a permanent drag on ROI?
- Tell us about one recent change initiative where adoption stalled—what happened and when did you first notice the issue?
If Leaders Lose Interest, Who Pays the Price?
- What would it cost the program if your executive sponsors’ attention faded three weeks after rollout?
- Which sponsor roles are most at risk of diverting attention, and why might they pull back?
- How would sponsor disengagement typically show up in decisions about scope, budget, or escalation?
- Have you already seen early signs of waning sponsorship (missed meetings, delayed approvals, delegated decisions)?
- If you answered yes, briefly describe the clearest example and its timing.
- What formal or informal escalation path exists to re-engage sponsors quickly?
Where Resistance Hides
- Who in your organization would secretly be relieved if this change quietly failed—and why?
- Which middle-manager behaviors most often preserve the status quo in your environment?
- In recent pilots or UAT, which tasks or scenarios produced the most pushback or workarounds?
- How do frontline teams usually signal resistance—overt complaints, silence, workarounds, or selective compliance?
- Are there subcultures, geographies, or functions that act as amplifiers of resistance? Name them and why they resist.
- If passive resistance is left alone, how long do you think it will persist?
What 'Good' Looks Like—In Real, Measurable Ways
- If we had to name three measurable behaviors that prove adoption is happening (not just awareness), what would they be?
- Which of the following types of signals can your team reliably capture today?
- For 30, 60, and 90 days post-launch, what target would convince you the program is on track (give one measurable target per milestone)?
- Which leading indicator would you want alerted on before go-live—so we can intervene early?
- Which single signal, if observed, should trigger an immediate corrective action?
What Could Break the Outcomes
- If one risk materializes between pilot and 60 days post-go-live, which single risk would most likely cause the adoption targets to fail?
- Which of these risks are currently present in your program?
- For the highest-risk item you selected, explain what makes it likely and any near-term triggers.
- What risk controls are already in place (governance, playbooks, champion time, budgets)? Select all that apply.
- What authority and access do we need from your team to execute rapid interventions when we surface a failing adoption signal?
- Who should be our internal go-to for emergency interventions (name and role)?
The Minimum Changes That Deliver Value
- What's the smallest set of behavior changes that would unlock the majority of the program's expected value?
- Which process steps, if reliably followed, would most reduce rework or defects?
- What training, scripts, or tools have you tried before—what specifically worked and what didn’t?
- Which managerial actions would most accelerate uptake (pick the top two)?
- If we had four weeks of focused pre-go-live effort, what one thing would you insist we prioritize?
Who Needs to Be Bought In—and How They Show It
- Which stakeholders must visibly change their behavior so the rest of the organization follows?
- For each stakeholder group you selected, what visible actions would demonstrate genuine commitment?
- What existing incentives or consequences might work against those visible commitments?
- Do you currently have named champions? Choose the closest description and, if applicable, list names below.
- If you have or plan champions, briefly list names/roles and current level of engagement.
- How quickly can managers be mobilized to enforce and coach new behaviors after go-live?
How We'll Measure Our Way to Confidence
- Would you accept early course corrections based on leading indicators even if that temporarily changes rollout sequencing or feature scope?
- Which analytics sources can we access to measure adoption?
- How often do you want adoption status updates and who are the essential recipients?
- Who should receive the dashboard updates (names/roles)?
- What acceptance criteria should program leadership use to sign off on 'adoption readiness' prior to go-live?
- If metrics indicate elevated risk, which decision-maker(s) can authorize a pause or remediation?
Communications That Move People
- What’s the most common change message your organization has heard that failed to change behavior—and why do you think it failed?
- Which channels carry the most credibility for different audiences (pick all that apply)?
- How do your managers prefer to receive coaching materials—scripts, short playbooks, live facilitation, or digital tools?
- Which framing resonates most with employees here—efficiency gains, reduced errors, job security, career opportunity, or customer impact?
- What would make the initial post-launch communication feel urgent, credible, and different from past communications?
Next Steps: Shared Commitments to Protect Outcomes
- What concrete decisions must be made now to make adoption non-negotiable?
- Which of the following commitments are you ready to make today? Select all that apply.
- Who will be accountable for monitoring the adoption dashboard and initiating corrective actions (name/role)?
- What cadence would you prefer for integrated readiness and risk reviews with our team?
- What outcome at 90 days would justify transitioning responsibility to business-as-usual (name 2–3 measurable criteria)?
-
Solution Experience
Walk through how the change will deliver outcomes in the customer’s context using real scenarios and failure modes.
Experience Meetings
- Current-State & Consequence Confirmation
- End-to-End Scenario Solution Experience
- Failure-Mode Simulation & Champion Response Workshop
- Acceptance Criteria & Evidence Mapping (Proof of Future State)
- Executive Validation & Commitment (Solution Experience Summary)
- Identified data gaps and an owner-driven plan to fill them before pilot.
- A single, stakeholder-approved one-sentence current state; no vague language.
- A quantified consequence statement (dollars, time, risk) agreed by business owners.
- Introductions and meeting objective
- Prep a short follow-up session to re-run the scenario after gaps are resolved.
- Objectives and rules for simulation
- Validate that champions and managers can detect and execute the first-line response to key failure modes.
- Confirm escalation paths and decision owners when first-line responses fail.
- Agree monitoring thresholds and who is responsible for alerts.
- Capture playbook edits required to close response gaps.
- Update response playbooks with steps and owner names based on simulation outcomes.
- Configure monitoring alerts and route to named owners; verify test messages.
- Schedule a follow-up tabletop within two weeks to validate playbook updates.
- Recap approved future-state outcomes and scenarios
- A completed acceptance criteria matrix tying each outcome to measurable evidence and a named owner.
- Clear go/no-go thresholds and decision rules for pilot and rollout.
- A single, stakeholder-approved one-sentence future state (outcome-focused).
- Produce and distribute the acceptance criteria matrix (metric, data source, owner, threshold).
- Assign owners to data collection tasks and schedule initial metric baselining.
- Document contingency triggers and responsible escalation contacts.
- One-sentence recap: current state, consequence, future state
- Obtain executive endorsement that the Solution Experience proves the future state and warrants proceeding.
- Secure commitments for resources, sponsor engagement cadence, and escalation pathways.
- Set the timeline and owners for pilot readiness and acceptance gating.
- Capture executive sign-off on the acceptance criteria and pilot scope.
- Assign executive sponsor cadence (meeting frequency, success reports) and document escalation contacts.
- Schedule the pilot readiness checkpoint and circulate agenda and required artifacts.
- Agreement on which real scenarios and failure modes will be used for the Solution Experience.
- Customer to confirm or update the one-sentence current state in writing.
- Customer to provide or validate the data sources and metrics used for consequence quantification.
- Facilitator to finalize the approved future-state sentence and circulate to attendees.
- Facilitator to collect and confirm the specific scenarios and failure-mode examples for the walkthrough.
- Brief recap of confirmed preconditions
- Stakeholders confirm that the demonstrated sequence directly delivers the agreed future-state outcome.
- Each demonstrated step is explicitly tied to and accepted as mitigating a named failure mode.
- Identify any gaps requiring design or operational changes before pilot or build.
- Agree on evidence types and data that will prove the success signals in practice.
- Document and assign ownership for any gaps discovered during the walkthrough.
- Produce a one-page scenario-to-signal mapping that ties every step to measurable success signals.
- One-sentence current state confirmation
- High-level scenario proof summary
- Review prioritized failure modes and detection signals
- Select scenario(s) and success signal(s)
- List success signals and required evidence types
- Quantify the consequence
- Map each signal to metric, data source, frequency, and owner
- Acceptance criteria and go/no-go summary
- Stepwise scenario walkthrough (Diagnosis -> Proof -> Validation)
- Simulation round 1 — frontline rejection scenario
- One-sentence future state definition
- Simulation round 2 — middle-manager workaround
- Decision and commitments
- Define acceptance thresholds and go/no-go rules
- Tiebacks to failure modes
- Risk carve-outs and contingency criteria
- Debrief: timing, effectiveness, and lessons
- Validation checkpoints and stakeholder confirmation
- Next steps and timeline to pilot readiness
- Preconditions checklist and artifact review
- Agree monitoring thresholds and alert routing
-
Solution Scope
Define change deliverables, champion network responsibilities, training scope, and measurable acceptance criteria.
Scope Configuration
- Deliver executive sponsor coaching sessions
- Run manager resistance-handling workshops
- Deliver role-based end-user training
- Facilitate process walk-through and simulation labs
- Activate change champion network workshops
- Deploy on-site go-live hypercare support
- Operate adoption helpdesk (on-site or remote)
- Create and distribute launch communications pack
- Run train-the-trainer sessions
- Deliver role-based quick-reference job aids
- Facilitate cross-functional integration workshops
- Moderate steering-committee and sponsor briefings
Scope Questions
Deliver executive sponsor coaching sessions
- How many executive sponsors or sponsor proxies need one-to-one coaching?
- What is the current level of sponsor engagement?
- Which topics should coaching prioritize?
- Preferred coaching format?
- How frequently should coaching sessions occur during the program?
- Are there specific decision gates or meetings where sponsors must be prepared (e.g., budget sign-off, cutover)? Please list.
- Language or time-zone constraints for coaching sessions?
Run manager resistance-handling workshops
- How many manager participants across levels (frontline, middle, senior) will attend?
- Which manager tiers should be included?
- What are the common resistance patterns observed or anticipated?
- Preferred workshop format and duration?
- Do you want practical role-plays and scripted scenarios included?
- Are managers expected to own specific adoption KPIs after the workshops? If yes, which ones?
- Will attendance be mandatory and tracked by HR or program governance?
Deliver role-based end-user training
- Which user roles need training (select all that apply)?
- How many end users in scope by role (approx.)?
- What training modalities are required?
- Are there existing training materials we should reuse or adapt?
- Required languages and accessibility needs for training?
- What are success/acceptance criteria for end-user training (e.g., pass rate, completion %)?
- When must training be completed relative to go-live?
Facilitate process walk-through and simulation labs
- Which business processes should be covered in walk-throughs and simulations?
- How many scenario variants and failure modes should be simulated?
- Do you have a sandbox/test environment available for realistic simulations?
- Who should participate in simulation labs?
- Preferred format for simulations?
- What measures will indicate a successful simulation (e.g., error rate, time-to-complete)?
- Are there specific systems integrations or data conditions to replicate?
Activate change champion network workshops
- How many champions do you expect to activate and in which geographies/functions?
- What selection criteria will be used for champions?
- Which responsibilities should champions own?
- Preferred cadence for champion workshops and check-ins?
- Do you want champions certified or issued role descriptors and KPIs?
- Should workshops include practical toolkits (talk-tracks, FAQs, escalation templates)?
- Are there incentives or recognition programs to maintain champion engagement post-launch?
Deploy on-site go-live hypercare support
- Which locations require on-site hypercare coverage?
- Duration of on-site hypercare required?
- What hours should hypercare cover?
- What support roles are required on-site (e.g., process lead, trainer, IT resolver)?
- What are the escalation paths and SLA targets for hypercare issues?
- Estimated peak daily support volume (tickets/incidents) at go-live?
- Are on-site staff required to perform coaching/manager interventions, or strictly technical support?
Operate adoption helpdesk (on-site or remote)
- Which support channels should the helpdesk operate on?
- Required helpdesk operating hours and time-zone coverage?
- Target SLAs for first response and resolution?
- Should the helpdesk be staffed by business-process experts, technical support, or both?
- What ticketing or ITSM system will the helpdesk integrate with?
- Do you require multilingual support and if so which languages?
- What reporting and escalation cadence do you want from the helpdesk (daily dashboards, weekly summaries)?
Create and distribute launch communications pack
- Which audiences must be addressed by launch communications?
- Which channels should be used for launch communications?
- Do you require templated assets (emails, slides, FAQs, manager talking points)?
- Will communications require translations or localization?
- Who must approve communications and what is the approval SLA?
- How will communications effectiveness be measured (open rates, attendance, survey feedback)?
- Are there regulatory or compliance constraints on communications content?
Run train-the-trainer sessions
- How many trainers need to be trained and where are they located?
- What prior training experience do nominated trainers have?
- Preferred format for train-the-trainer?
- Should trainers receive assessment/certification and refresher plans?
-
Mutual Commit
Confirm commercial terms, governance, milestone acceptance criteria, and escalation paths tied to adoption outcomes.
Agreement Modules
- Statement of Work (SOW)
- Commercial Terms & Pricing
- Payment Schedule & Invoicing
- Acceptance Criteria & Milestone Sign-Offs
- Governance & Steering Committee Charter
- Adoption Outcomes & Success Metrics Agreement
- Escalation & Dispute Resolution Path
- Change Control & Change Order Agreement
- Champion Network Commitment
- Service Level Agreement (SLA) & Support
- Data Processing & Security Annex (DPA/Security)
- Roles, Responsibilities & RACI
- Termination, Renewal & Liability Terms
-
Deployment
Operationalize rollout with readiness checks, champion activation, and validation.
-
Pre-Deployment Readiness
Verify data, access, manager engagement, champion readiness, and risk controls before execution.
Readiness Questions
Opening: Quick Snapshot of Your Program
- Briefly, which type of transformation are we preparing for?
- What’s the target go-live window (month and year) and how fixed is that date?
- How many people will be in scope for the initial launch (approximate)?
- Who is the executive sponsor and what is their stated priority for this program?
- Which program outcomes are non-negotiable for leadership (select up to three)?
Are We Mistaking Visibility for Commitment?
- When sponsors show up for steering meetings, what concrete evidence do you get that they're still committed after launch?
- How often do sponsors directly engage with frontline teams or managers about the change?
- Give an example of a time a sponsor's attention noticeably shifted—what happened and how did the program respond?
- Which signals would make you confident a sponsor will sustain attention through the adoption dip?
- If sponsor attention wanes, what are the fastest ways you've seen to re-engage them?
Where the Work Really Happens: Teams, Managers, and Real Resistance
- Which layer of the organization typically decides to stick with the old way—frontline users, middle managers, or leadership—and why do you think that happens here?
- Who are the three groups most likely to slow or block adoption in week 1–8 after go-live?
- How were middle managers involved in design and testing—were they consulted, informed, or largely bypassed?
- Tell us about a specific manager or team that resisted change previously—what did they do, and what was the impact?
- Which incentives or accountabilities exist today that might reward keeping the status quo?
What Keeps You Up at Night?
- If this program fails to achieve adoption at expected levels, what is the single worst business consequence you fear?
- How would that consequence show up in metrics your executives care about (be specific—names and thresholds if possible)?
- How tolerant is the Board/C-suite for a period of adoption underperformance before corrective actions are required?
- What early indicators would you monitor to detect that the program is drifting toward that worst-case?
- Which stakeholder(s) would you need to brief immediately if those indicators start trending poorly?
If Adoption Were Non-Negotiable: What Success Looks Like
- Imagine adoption is hitting targets three months after go-live—what specific behaviors are people doing differently?
- Which measurable success signals would prove the change is real (choose up to three)?
- What acceptance criteria do business owners expect before they 'sign off' on a successful deployment?
- How will you prioritize competing success measures (e.g., speed vs. accuracy vs. cost)?
- Who will own the ongoing measurement of those signals after our engagement ends?
What Would a True Change Partner Actually Do Differently?
- Why do you think communications + training alone have not delivered sustainable adoption in your past programs?
- If a partner could surface resistance 3–4 weeks before go-live, what would you want them to do with that insight?
- Which working model do you prefer for a partner on-site lead: embedded full-time, periodic advisory, or virtual with frequent check-ins?
- What evidence or references would convince you this partner can re-engage disengaged sponsors and managers?
Ready, Set, Stop — Pre-Deployment Practicalities
- What data and system access must be validated before we run final dress rehearsals (pick all that apply)?
- Which managers have committed to attending go-live simulations and coaching sessions?
- Who are your nominated champions today and how confident are you in their readiness (select one)?
- What contingency controls are you prepared to use if a critical process fails on day 1 (select all that apply)?
- Which single technical or access issue would be most likely to delay execution if unresolved at cutover?
Small Tests, Big Signals: Early Warning and Rapid Response
- What pattern of early behavior would make you suspend roll‑forward and address adoption risk first?
- How will we collect real-time adoption signals—automatic telemetry, manager checkpoints, champion reports, or a mix?
- Who has the authority to call a rapid response and reallocate resources during the first 30 days post-launch?
- Describe one recent example where rapid intervention saved a deployment—what signal triggered action and what was done?
- What cadence for status and signals reporting feels right in the first two weeks after go‑live?
Commitments, Next Steps, and What We’ll Own Together
- Of the areas we've discussed, which three would you prioritize for immediate attention (pick up to three)?
- Who is the final decision-maker for approving an external change partner and the pilot scope?
- Realistically, how quickly can you mobilize a pilot readiness window with your core stakeholders?
- What would success look like at the end of a 4–6 week readiness engagement with us?
- Is there anything we haven't asked that you worry will trip up adoption and you'd like us to know right now?
-
Champion Activation & Enablement
Mobilize and train change champions and middle managers, finalize playbooks, and simulate resistance handling.
-
Go-Live Support & Rapid Response
Provide intensive launch support, monitor adoption signals in real time, and intervene on emerging resistance.
-
Validation & Transition to Sustainment
Verify adoption metrics against success signals, document lessons, and transition ownership to BAU.
Validation Questions
Quick Frame: Where Are We Right Now?
- What is the program name, primary objective, and planned go-live date?
- Which of these best describes your program’s current phase?
- How many end-users and manager-level users are in scope for adoption tracking?
- Who on your team will be our primary contact for validating adoption metrics and coordinating BAU handover?
- What existing change artifacts (adoption metrics dashboard, playbooks, lessons log) already exist and where are they stored?
If We Measured Adoption Today, Would It Tell the Whole Story?
- When you look at your current adoption metrics, what one headline would you expect to see?
- Which behaviors have you defined as 'adopted'—and are those tracked as usage, task completion, or outcomes?
- How confident are you in the accuracy of the data feeding your adoption signals?
- If a metric shows a 20% drop week-over-week, how do you want us to interpret that signal—temporary noise, localized resistance, or systemic adoption failure?
- Which dashboards or tools do we need access to for independent verification (e.g., LMS reports, system logs, service desk tickets)? List system names and access owners.
Where Is Resistance Still Quietly Winning?
- Which group feels most likely to quietly revert to old ways if not actively supported?
- What are the top three reasons these groups might resist or revert (e.g., unclear value, workload, system gaps, incentives)?
- Where have you seen the earliest signs of resistance—support tickets, missed transactions, informal feedback, or performance dips?
- How long have these resistance patterns been visible, and what attempts have been made to address them?
- If we had to name one 'resistance hot spot' to prioritize for an immediate intervention, what would it be and why?
What Would ‘Sustained Success’ Actually Feel Like?
- What specific behaviors or outcomes would make you say this program is sustainably successful 6 months after go-live?
- Which quantitative thresholds would you accept as proof (choose all that apply)?
- Which qualitative signals would convince you (examples: manager testimonials, frontline stories, fewer workarounds)?
- How should short-term stabilization (first 30–90 days) be balanced against longer-term behavior change (3–12 months)?
- Who needs to feel these wins most urgently (executive sponsors, program directors, CFO, operations), and how will they signal satisfaction?
Who Will Own This When Our Team Steps Back?
- If we handed off documentation and dashboards tomorrow, who in BAU would be responsible for daily monitoring and issue escalation?
- Do you have named BAU roles with explicit acceptance criteria for adoption (examples: 'Support Lead will triage within 24 hrs', 'Managers will review adoption weekly')?
- What training, playbooks, or governance artifacts must be completed before handover? Select all that apply.
- How much budget and FTE headcount will BAU commit to sustainment activities (choose ranges)?
- What would make you decide not to hand this to BAU and instead extend a specialized adoption support period?
What Lessons Do We Need to Capture Before They Fade?
- Which recent decisions or adaptations during rollout produced unexpectedly good or bad results that must be documented?
- How do you currently capture lessons—retros, ticket notes, senior reviews, or not at all?
- Which stakeholders should contribute to the lessons log (e.g., frontline reps, support, product owners, regional managers)?
- How soon should we schedule a lessons capture session to ensure actionable items are recorded and owners assigned?
- What format would make lessons most usable for BAU—short playbook updates, recorded case studies, or prioritized action lists?
Are Your People, Data, and Tools Ready to Stay Vigilant?
- Do you have direct access to the raw data streams needed for ongoing adoption monitoring (yes/no and list sources)?
- Which monitoring cadence do you prefer post-handover (daily alerts, weekly summaries, monthly business reviews)?
- What automated alerts or guardrails do you currently have to prevent a small issue becoming systemic?
- Which training and coaching rhythms must continue after handover (e.g., new-hire training, manager refreshers, quarterly simulations)?
- Who will be the escalation point if adoption metrics trend downward—name, role, and expected response SLAs?
Small Bets That Prove the System or Protect Value
- If we proposed a 2–4 week micro-pilot to validate a sustainment mechanism, what problem would you most want it to prove it can solve?
- Which pilot levers could we realistically test quickly—targeted coaching, incentive changes, automation fixes, or adjusted reporting?
- What success criteria would make the pilot a clear 'go/no-go' for scale?
- Who needs to be at the table to run the pilot and commit to follow-through (roles and time commitment)?
- How quickly could you authorize a pilot of this kind and where would the funding come from?
Final Check: What Commitment Will Make the Transition Stick?
- What are the non-negotiable acceptance criteria you need to see before we formally transition ownership to BAU?
- Who will sign the handover acceptance—name, title, and the metrics they will review?
- What is your preferred timeline for a formal handover workshop and go/no-go decision?
- What ongoing advisory relationship would you value after handover (periodic check-ins, on-call support, quarterly reviews)?
- If we could leave you with one ready-to-use artifact that increases the chance of sustainment the most, which would you pick?
-
-
Success
Review outcomes against agreed signals and maintain a shared channel for issues and continuous improvements.
Success Reviews
- Success Signal Review (Weekly - Early Sustainment)
- Issue Triage & Rapid Response (Ad-hoc)
- Continuous Improvement Backlog & Prioritization (Monthly)
- Sustainment Governance & BAU Handover
- Lessons Learned & Adoption Insights Workshop (Quarterly)
Issues & Enhancements
- Opening & Objectives
- If consequence exceeds escalation threshold, notify sponsor and trigger governance meeting.
- Incident Summary & Impact
- Contain the immediate impact and limit business exposure.
- Agree a prioritized remediation plan with clear owners and milestones.
- Ensure transparent, timely communication via the shared channel and sponsor alerts.
- Assigned owner to implement containment fix and post status updates to the shared channel every reporting interval.
- Technical lead to deliver a preliminary root-cause evidence package within 24 hours.
- Communications owner to publish a stakeholder update and escalate to sponsors if SLA breached.
- Backlog Review Snapshot
- Convert observed adoption gaps into a prioritized, resourced backlog tied to outcome improvement.
- Ensure owners and timelines are set so progress is observable and reported in the shared channel.
- Align on documentation/training updates needed to sustain improvements.
- Product/Change owner to schedule top 3 backlog items into execution sprints with clear milestones.
- Change lead to assign playbook and training updates to authors and set delivery dates.
- Ops lead to update the public roadmap and backlog status in the shared channel.
- Handover Summary
- Complete formal transfer of ownership and responsibilities to BAU teams.
- Ensure monitoring, reporting, and escalation mechanisms are in place and understood.
- Confirm documentation and shared channel access are finalized for ongoing issue management.
- BAU lead to confirm access and ownership in the shared channel and accept governance responsibilities.
- Operations to publish final runbooks and monitoring playbooks to the shared knowledge repository.
- Schedule the BAU health-check at the agreed cadence and invite sponsors/champions.
- Workshop Framing & Desired Outcomes
- Harvest and validate lessons learned that materially affect adoption outcomes.
- Design and prioritize a set of experiments or improvements tied to measurable signals.
- Assign owners and clear success criteria and commit to publishing results via the shared channel.
- Research lead to publish the workshop report with prioritized experiments and owners to the shared channel within 5 business days.
- Assigned experiment owners to define baseline, success signal and measurement plan before pilot start.
- Communications to prepare a short 'wins & learnings' brief for sponsors to maintain engagement.
- Establish whether current outcomes meet the agreed success signals and thresholds.
- Decide and assign immediate corrective actions for any off-target signals.
- Ensure all decisions and issues are captured in the shared channel for traceability.
- Owner(s) to execute agreed corrective actions and report progress in the shared channel within 48 hours.
- Ops lead to update the dashboard with latest data and annotate any manual adjustments.
- Recap of Agreed Success Signals
- Quantitative Trends Review
- Priority & Risk Assessment
- KPI/SLA Monitoring & Reporting
- Map Items to Success Signals & Outcomes
- Adoption Dashboard Review
- Immediate Containment Actions
- Prioritization Using Criteria
- Qualitative Insights from Champions & Users
- Governance & Escalation Paths
- Champion & Manager Sustainment Plan
- Resource & Timeline Allocation
- Variance & Consequence Assessment
- Synthesize Patterns & Root Causes
- Rapid Root Cause Triangulation
- Root-Cause Snapshot
- Ideation & Prioritization of Experiments
- Intervention Plan & Resourcing
- Update Playbooks & Training Needs
- Documentation, Runbooks & Access
- Intervention Options & Decisions
- Publish Roadmap & Channel Maintenance Rules
- Sign-off & Next Review Date
- Communications & Stakeholder Notifications
- Commit Owners, Success Criteria & Reporting