Skip to main content

    Adoption bottleneck

    Plan how an improvement could spread.

    Understand the evidence, local context and support each team needs before extending a change.

    Worked planning example. Figures below are illustrative, not verified ALIRA client results. Review the approach with your team before use.

    Test this idea free

    First plan free. No credit card.

    The Reality

    • .Ward A tested the idea. Results are good.
    • .Ward B says "we'll try it when we have time"
    • .Ward C got distracted by another project
    • .Six months later, still only Ward A is using it
    • .The evidence exists. The spread just... stalled.

    What Works

    • Map the actual blockers to adoption
    • Assign one spread lead (not a committee)
    • Test removal of each blocker on one ward
    • Then roll out simplified version across trust
    • Adoption across four wards in 8 weeks
    Spread roadmap

    How to spread this

    Plan

    Interview Ward B, C, D staff: why haven't you adopted Ward A's change? List every blocker (training, time, equipment, process conflict, trust, clarity).

    Do

    Assign a spread lead. Test removal of top three blockers on Ward B. Simplify, don't enforce.

    Study

    Did removing blockers make Ward B adoption easier? What took longer than expected? Ask staff: is it now something you'd use?

    Act

    If blockers are removed and Ward B is using it, roll out to C and D using the simplified version. Stop expecting people to adopt the original.

    One trust did this. Service lead identified five adoption blockers. Tested solutions on Ward B over two weeks. Then rolled out simplified version to Wards C and D. Six weeks later, all four wards using it. The change didn't get harder. The spread plan did.

    The thing that works in one ward often doesn't spread because you're asking other wards to solve your problems the same way you did. Instead, let them solve it their way. Remove the blocker, not the method.

    Why this works when spread usually fails

    You're measuring the actual blocker

    Most spread stalls because you don't know why. Is it training? Time? Trust? You can't remove a blocker you haven't named.

    One lead, not a committee

    Committees slow adoption. One person with authority to simplify and test removes friction every day, not every six weeks.

    You're testing spread, not forcing it

    Test on one ward first. Let them fail safely. Then roll out what works. You're not spreading the original idea. You're spreading what actually sticks.

    Ready to spread your idea?

    Map your blockers. Test removal. See adoption across your wards in 8 weeks instead of 6 months.

    Create Your Spread Plan Free