ADKAR Model for WFM Transformation

From WFM Labs

ADKAR Model for WFM Transformation applies Prosci's individual change management framework to workforce management transformation. While Kotter's model addresses organizational-level change and the Change Curve addresses emotional response, ADKAR provides the diagnostic precision to understand why a specific person or group isn't changing — and what to do about it.

Overview

ADKAR was developed by Jeff Hiatt, founder of Prosci, and published in ADKAR: A Model for Change in Business, Government, and Our Community (2006). The model is built on a simple but powerful premise: organizational change only happens when individuals change, and individuals change through five sequential elements:

  1. Awareness — Understanding why the change is needed
  2. Desire — Personal motivation to participate in the change
  3. Knowledge — Knowing how to change (what to do)
  4. Ability — Demonstrated capability to implement the change
  5. Reinforcement — Factors that sustain the change over time

The elements are sequential. You cannot create desire in someone who isn't aware of the need. You cannot build ability in someone who lacks knowledge. And you cannot sustain change without reinforcement. When a WFM transformation stalls, ADKAR helps identify the barrier point — the specific element where individuals are stuck.

This diagnostic precision is what makes ADKAR indispensable for WFM transformation. When an analyst won't use the new forecasting platform, the response depends entirely on which element is the barrier. Is it awareness? ("I didn't know we were changing.") Desire? ("I know, but I don't want to.") Knowledge? ("I want to, but I don't know how.") Ability? ("I know how in theory, but I can't actually do it.") Reinforcement? ("I used it for a week, but nobody noticed and the old way is easier.")

Each barrier demands a different intervention. Treating a desire problem with training (knowledge intervention) wastes time and money. Treating an ability problem with more communication (awareness intervention) frustrates everyone.

The Five Elements Applied to WFM

A — Awareness

Definition: Understanding why the change is necessary, what's changing, and what happens if the organization doesn't change.

WFM questions that test awareness:

  • Do stakeholders understand the current maturity level and what it costs the organization?
  • Can they articulate why the current state is unsustainable?
  • Do they know what will change specifically — tools, processes, roles, metrics?
  • Do they understand the timeline and what's expected of them?

Common awareness gaps in WFM:

  • Analysts who don't understand the strategic rationale — they see a tool change, not a maturity transition
  • Supervisors who weren't included in communication — they hear about changes from their teams rather than from leadership
  • Agents who experience schedule changes without understanding why — they attribute changes to "management doesn't care" rather than "we're optimizing for better outcomes"
  • Executives who don't understand the maturity model — they see a "WFM project" rather than a multi-year transformation

How to build awareness:

  • Present the cost of current state in financial terms: "Current forecast accuracy costs us $X annually in overstaffing"
  • Show the competitive gap using industry benchmarks and peer comparison
  • Make it personal for each audience: analysts hear about professional development opportunities; supervisors hear about improved tools; agents hear about better schedule quality; executives hear about ROI
  • Use multiple channels: Town halls, team meetings, one-on-ones, written communications, dashboards
  • Repeat: Prosci research shows people need to hear the change message 5-7 times through multiple channels before awareness registers

Awareness failure mode: The WFM leader communicates the change once, in a team meeting, using WFM jargon, to WFM analysts — and assumes the entire organization is now aware. Supervisors, agents, operations managers, and executives remain uninformed.

D — Desire

Definition: Personal motivation and choice to participate in and support the change.

WFM questions that test desire:

  • Do people WANT to change, or are they merely compliant?
  • Can individuals articulate what's in it for them personally?
  • Are people volunteering for transformation activities or being assigned?
  • Is there active advocacy, or just passive acquiescence?

Common desire barriers in WFM:

  • The spreadsheet expert: An analyst who built their career and reputation on mastering the current forecasting methodology. The change threatens their expert status. They are aware of the change but have no desire to participate because it reduces their value.
  • The autonomous supervisor: A supervisor who values their ability to override schedules and make real-time decisions. Integrated WFM with rules-based scheduling reduces their autonomy. They understand the rationale but don't want to give up control.
  • The burned-out agent: An agent who has lived through three "schedule improvement" initiatives that all failed. They are deeply aware that change is happening and deeply skeptical that it will matter.
  • The political resistor: A manager whose headcount or budget is threatened by WFM optimization. They understand the change perfectly and oppose it because it reduces their organizational power.

How to build desire:

  • WIIFM (What's In It For Me): Explicitly address what each person gains from the change:
    • Analysts: "You'll spend 80% of your time on analysis instead of data preparation. You'll learn probabilistic methods that make you more marketable. You'll have tools that match your ambition."
    • Supervisors: "You'll have real-time visibility you've never had. You'll spend less time on schedule adjustments and more time coaching your team. Your performance metrics will improve."
    • Agents: "You'll have more schedule flexibility, better preference matching, and easier shift swaps. Your feedback will directly influence scheduling decisions."
    • Executives: "You'll have predictive workforce analytics, reduced labor costs, and the ability to model scenarios before committing resources."
  • Address the loss directly: Don't pretend nothing is being lost. "I know you built the current forecast process from scratch. That expertise transfers — and the new platform will let you apply it at a level that wasn't possible before."
  • Peer influence: People are more influenced by peers than by leadership. When one respected analyst embraces the change, others follow.
  • Consequences of non-participation: This must be handled carefully, but organizational change requires organizational alignment. "The new methodology is how we'll operate. If this isn't the direction you want your career to go, we should have an honest conversation about that."

Desire is the most common barrier point in WFM transformation. Prosci's research across industries shows desire as the most frequent barrier, and WFM is no exception. The specific pattern: experienced WFM professionals who are fully aware of the change and knowledgeable about the new methods, but who don't want to give up the tools and processes they've mastered. This isn't irrational — it's a reasonable response to a threat to professional identity. It requires empathy, patience, and persistence.

K — Knowledge

Definition: Information, training, and education on how to change — what to do differently and how to do it.

WFM questions that test knowledge:

  • Do people know how to use the new tools?
  • Do they understand the new processes and their role in them?
  • Can they articulate the new methodology and why it works?
  • Do they know where to get help when they're stuck?

Common knowledge gaps in WFM:

  • Platform knowledge: How to use the new WFM software — navigation, configuration, workflow execution
  • Methodology knowledge: The analytical foundations of the new approach (e.g., probabilistic vs. deterministic forecasting, optimization vs. heuristic scheduling)
  • Process knowledge: The new workflows — who does what, when, with what inputs and outputs
  • Integration knowledge: How the pieces fit together — how a forecast change flows through to scheduling, how real-time data feeds back to planning

How to build knowledge:

  • Role-based training: Analysts need deep platform and methodology training (40-80 hours). Supervisors need workflow and dashboard training (16-24 hours). Agents need self-service portal training (2-4 hours). Executives need dashboard and reporting orientation (2-4 hours).
  • Just-in-time delivery: Don't train people on features they won't use for three months. Train on what they need now, and deliver additional training as new capabilities are activated.
  • Multiple modalities: Classroom training for core concepts. Video tutorials for platform navigation. Quick reference guides for daily workflows. Peer mentoring for contextual questions. Office hours for troubleshooting.
  • Test understanding: Don't assume training equals knowledge. Assess comprehension through practical exercises, scenario-based assessments, and observation.

Knowledge failure mode: Three days of vendor-led platform training, delivered two weeks before go-live, covering every feature in the platform regardless of role or sequence. Result: information overload, rapid forgetting, and zero practical capability when go-live arrives.

A — Ability

Definition: Demonstrated capability to perform the new behaviors and implement the change in practice.

WFM questions that test ability:

  • Can people actually DO the new process, not just describe it?
  • Are they producing work at acceptable quality using the new methods?
  • Can they handle exceptions and edge cases, not just the standard workflow?
  • Are they performing at or approaching their previous productivity levels?

The critical distinction — Knowledge vs. Ability:

Knowledge is intellectual understanding. Ability is demonstrated performance. A WFM analyst can attend 40 hours of training on probabilistic forecasting (knowledge) and still be unable to produce a probabilistic forecast that's accurate enough for production use (ability). The gap between knowledge and ability is practice — and most WFM transformations don't allocate enough time for it.

Common ability gaps in WFM:

  • The trained-but-struggling analyst: Completed all training, passed all assessments, but takes three times as long to produce a forecast and the quality is inconsistent. Needs practice, not more training.
  • The aware-but-overwhelmed supervisor: Understands the new dashboard but freezes when real-time events require rapid response using unfamiliar tools. Needs simulated practice with coaching.
  • The knowledgeable-but-slow agent: Knows how to use the new self-service portal but takes 10 minutes for a task that should take 2. Needs repetition and time.

How to build ability:

  • Practice time: Build dedicated practice periods into the implementation plan. Analysts need 2-4 weeks of supervised practice before they're expected to produce production-quality work.
  • Reduced workload: During the ability-building period, reduce non-essential demands. If analysts are expected to learn the new system while maintaining full production in the old system, neither gets done well.
  • Coaching, not training: Ability is built through coaching — observing someone do the work and providing real-time feedback. This requires experienced practitioners (internal experts or external consultants) who can sit alongside analysts during their first production forecasts.
  • Safe-to-fail environment: Create a sandbox environment where analysts can make mistakes without production consequences. Run parallel forecasts (old and new method) during the transition so the new method can be validated without risk.
  • Progressive complexity: Start with the simplest use case and build. First forecast: one queue, one channel, one week horizon. Then add complexity incrementally.

Ability is the second most common barrier point in WFM transformation — and the most expensive to fix because it requires the most time and hands-on support. Organizations that budget for training but not for ability-building consistently underinvest in the most critical phase.

R — Reinforcement

Definition: Factors that sustain the change and prevent reversion to the old way.

WFM questions that test reinforcement:

  • Are new behaviors being measured and rewarded?
  • Is the old way still accessible? (If so, people will use it under pressure.)
  • Are there consequences for reverting to old methods?
  • Is leadership visibly using and referencing the new processes and metrics?
  • Do onboarding and ongoing training reflect the new way?

Common reinforcement failures in WFM:

  • The available escape hatch: The old WFM platform is still accessible "just in case." Under deadline pressure, analysts revert to the tool they know.
  • Misaligned metrics: The organization is measuring WFM performance using the old metrics — which the old methods were optimized for. New methods look worse by old measures.
  • Invisible adoption: Nobody tracks whether people are actually using the new processes. Compliance is assumed rather than verified.
  • Leadership reversion: Under executive pressure, leaders revert to asking for the old reports in the old format. If leadership doesn't use the new outputs, nobody will produce them.
  • Onboarding gap: New hires are taught the old way by colleagues who haven't fully transitioned, perpetuating legacy practices.

How to build reinforcement:

  • Remove the old way: Decommission the legacy platform. Delete the shadow spreadsheets. Remove old report templates from shared drives. This is uncomfortable but necessary — every available escape hatch will be used.
  • Align metrics: Update KPIs, scorecards, and performance reviews to reflect the new way of working. If you're moving to probabilistic forecasting, measure probabilistic accuracy — not the old single-point metrics.
  • Visible recognition: Publicly acknowledge people who have embraced the new way. "Sarah's team was the first to produce a full probabilistic staffing plan using the new methodology. Here are the results."
  • Accountability: After a reasonable transition period, the new way is the expected way. Continued use of old methods is a performance issue, not a preference.
  • Continuous improvement cycles: Monthly process reviews, quarterly capability assessments. The transformation doesn't end — it evolves into continuous improvement.
  • Update all documentation: SOPs, training materials, onboarding guides, quick reference cards — all must reflect the current way of working.

The ADKAR Assessment

The most practical application of ADKAR is the barrier assessment — a diagnostic that identifies where each individual or group is stuck.

How to Conduct an ADKAR Assessment

For each stakeholder group, rate each element on a 1-5 scale:

Element Question Rating Scale
Awareness "I understand why we need to change our WFM processes" 1 (strongly disagree) to 5 (strongly agree)
Desire "I want to participate in this change" 1 to 5
Knowledge "I know what to do differently and how to do it" 1 to 5
Ability "I can perform the new processes at an acceptable level" 1 to 5
Reinforcement "The organization supports and rewards the new way" 1 to 5

Interpretation: The barrier point is the first element scoring below 3. Because ADKAR is sequential, addressing elements after the barrier point is ineffective. An analyst who scores Awareness=5, Desire=2, Knowledge=4, Ability=3, Reinforcement=2 has a Desire barrier — all the training in the world (Knowledge) won't matter until the desire barrier is resolved.

Common WFM ADKAR Patterns

Pattern 1: The Uninformed Organization Awareness=2, Desire=2, Knowledge=1, Ability=1, Reinforcement=1 Diagnosis: Communication hasn't happened or hasn't landed. Start with awareness before anything else.

Pattern 2: The Informed but Unwilling Awareness=4, Desire=2, Knowledge=3, Ability=2, Reinforcement=1 Diagnosis: People understand the change and may even know how to do it, but don't want to. This is the most common WFM pattern. Address desire through WIIFM, peer influence, and honest conversation about the future.

Pattern 3: The Willing but Unable Awareness=4, Desire=4, Knowledge=4, Ability=2, Reinforcement=2 Diagnosis: People are on board and trained, but can't perform at the required level. This is a practice and coaching problem. Invest in hands-on ability building.

Pattern 4: The Unsustained Change Awareness=4, Desire=4, Knowledge=4, Ability=4, Reinforcement=2 Diagnosis: The change happened but is eroding. Old methods are creeping back in. Reinforcement is failing — check for available escape hatches, misaligned metrics, and leadership reversion.

ADKAR by WFM Role

Role Typical Barrier Point Most Effective Intervention
WFM Analysts Desire (don't want to give up mastered tools) WIIFM focused on professional growth, peer influence from early adopters
Supervisors Ability (trained but can't perform under pressure) Simulated practice, coaching during live operations
Agents Awareness (don't understand why schedule changed) Targeted communication through supervisors, self-service portal demos
Operations Managers Desire (change reduces control/authority) Reframe role as strategic rather than tactical, executive alignment
IT Staff Knowledge (unfamiliar with WFM domain) WFM-specific orientation, paired work with WFM analysts
Executives Awareness (don't understand maturity model) Maturity assessment presentation, peer benchmarking, ROI model

Maturity Model Position

ADKAR applies at every maturity transition, but the dominant barrier point shifts:

  • Level 1→2 (Reactive → Foundational): Primary barrier is Knowledge — people need to learn basic WFM discipline and tools
  • Level 2→3 (Foundational → Integrated): Primary barrier is Desire — analysts and supervisors must give up autonomy for integration
  • Level 3→4 (Integrated → Optimized): Primary barrier is Ability — the jump to probabilistic/optimization methods requires deep practice
  • Level 4→5 (Optimized → Adaptive): Primary barrier is Desire — people must accept reduced direct control as AI systems expand

See Also

References

  • Hiatt, J.M. (2006). ADKAR: A Model for Change in Business, Government, and Our Community. Prosci Learning Center.
  • Prosci (2018). Best Practices in Change Management (10th edition). Prosci Inc.
  • Prosci (2020). "The Prosci ADKAR Model." Prosci Research Hub.
  • Creasey, T. (2018). "The Correlation Between Change Management and Project Success." Prosci Research.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=ADKAR_Model_for_WFM_Transformation&oldid=2280"