Change Management

Make it stick.

Change doesn’t usually fail at launch. It fails later, when the team hits friction, attention moves on, and the old way quietly returns. I build the practical support that helps people adopt new tools and ways of working, and I keep the follow-through alive long enough for it to become normal.

WHAT I DO

Deliverables that make the change specific, realistic, and sequenced.
  • Change strategy (how we’ll drive adoption and what “good” looks like)
  • Change roadmap (phases, milestones, and where people support is needed)
  • Stakeholder map (who’s impacted and what each group needs)
  • Impact assessment (what changes in the work, not just in the system)
  • Readiness check (where confidence is strong vs. where help is needed)
  • Integrated plan (communications, training, support, reinforcement working together)
  • Risks + resistance watchlist (likely pushback, root causes, and what we’ll do about it)
Deliverables that help leaders show up clearly and consistently.
  • Sponsor brief (what to say, when to show up, what to reinforce)
  • Leadership alignment notes (the decisions and messages we need locked)
  • Talking points + leader emails (written in a human voice, easy to deliver)
  • Town hall toolkit (storyline, FAQs, and how to handle the hard questions)
  • Leader 1:1 prompts (a simple structure for checking in with teams)
  • Manager cascade kit (how to translate the change into “what it means for us”)
  • FAQs (plain-language answers that hold up under pressure)
Deliverables that keep feedback flowing and build advocates across the org.
  • Change champion network setup (roles, expectations, coverage by site/function)
  • Champion toolkit (what to listen for, what to share back, how to help peers)
  • Office hours / Q&A structure (how support runs post-launch)
  • Community prompts (grounded in reality, not performative enthusiasm)
  • Feedback intake + triage (what gets escalated, what gets answered, what gets fixed)
  • Signal summaries (what people are asking, where they’re stuck, what’s changing next)
Deliverables that prevent the “post-launch dip” and make the new way easier than the old way.
  • Reinforcement plan (what happens week 1, week 3, week 6 so it doesn’t fade)
  • In-the-flow support (where help lives so it’s findable during real work)
  • Job aids + quick guides (short “how to do it” support for common tasks)
  • Hypercare communications (what’s new, what changed, what to do now)
  • Success stories (real examples that show “people like me can do this”)
  • Sustainment handoff (what moves from project mode to business-as-usual)
Deliverables that show what’s working and what to adjust next.
  • Adoption dashboard (simple view of usage + engagement signals)
  • Pulse checks (quick confidence/readiness questions that get answered)
  • Barrier log (top friction points and what we changed because of them)
  • Message and enablement iteration plan (what gets simplified, added, removed)
  • Leadership readouts (what’s landing, what isn’t, and the next move)
  • Lessons learned recap (what we’d repeat next time and what we’d never do again)

related use cases