Tools and Activities

Resource Hub · Implement · Evaluate · Adapt · Sustain

Change & Implementation Plan

Moving from a tested direction toward sustained practice

Implementation is another stage of learning, not the end of it. This plan helps teams coordinate action while continuing to monitor context, feedback, equity, fit, and emerging evidence.

Type: Tool / ProcessAdaptive implementationEvidence-linked review

Entries stay in the Brief working canvas when you change views. Use short, labeled notes or a partner to capture ideas. Print before leaving; reloading clears entries.

Complete meeting sequence

Brief working canvas

Change & Implementation Plan

Purpose: Coordinate a tested direction while keeping participation, evidence, adaptation, and review active.

Use this when: Learning supports broader use and the team needs cross-role coordination, resources, or approval.

Scope: Focused first pass: cover readiness and all 13 planning domains for the next implementation period. Verify commitments and extend the Full guide before a wider rollout.

Start with: Test records, affected perspectives, a provisional direction, and people with implementation knowledge and decision authority.

Time: 45–60 minutes for a prepared, near-term first pass; steps allocate 50. Allow 60–90 minutes or several sessions for a fuller plan and verified commitments. Review and implementation occur later. These are planning estimates; allow additional processing and participation time.

Participation: Think individually before discussion. Use bullets, a labeled diagram, or spoken ideas captured and checked by a partner. You may pass and return. Keep the required information and reasoning visible in your chosen format.

1. Decide whether to implement

7 minutes

Check what has been tested, who informed the decision, people affected, remaining uncertainty, and conditions for broader use. Choose Ready / Ready with conditions / Return to prototype or inquiry.

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Direction / evidence / source / limits · People affected / who informed this · Uncertainty / missing perspective · Readiness outcome / rationale / conditions · Intended change / for whom / why

2. Protect essentials and fit the context

7 minutes

Separate essential features from what can adapt. Name supports, difficulties, existing strengths, change depth, and central Conditions for Thriving.

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Essential features / why · Adaptable features / uncertainty · Context supports / barriers / assets · First-order / deeper change / rationale · Thriving conditions / differences across groups / what to monitor

3. Assign roles, influence, and resources

12 minutes

Keep affected people, implementation partners, knowledge holders, decision-makers, and coordinators distinguishable. State authority and how affected people continue shaping the work. Review time, people, expertise, relationships, infrastructure, funding/materials, and leadership/governance support.

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Position / person or group · Knowledge / responsibility / decision rights · Participation route / less influence and greater exposure · Power arrangement preserved or changed

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Support / available evidence · Missing or assumed support · Person able to commit / confirmation / conditions · Workload / access / burden correction

4. Coordinate the next actions and evidence

10 minutes

Choose only the next useful actions. Distinguish early implementation indicators, experience/learning indicators, and longer-term outcomes. Use time horizons that fit the work.

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Action / people involved / owner / due · Learning or accomplishment · Permission or dependency

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Early use / by whom / where / barriers — source · Experience / fit / equity / unintended effects — source · Longer-term meaningful outcome — source · Review interval / privacy / burden / uncertainty

5. Plan review and record adaptations

8 minutes now; revisit after action

Set a review before continuation becomes automatic. Include affected and operational knowledge in interpretation. Define signals for Continue / Expand / Narrow / Redesign / Pause / Stop. Begin the log now; fill effects after action.

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Review date / interpreters / decision authority · Working for whom / not working / evidence needed · Decision options / signals / next decision · Adaptation made or proposed / why / evidence or context · Observed effect or not yet known / owner

6. Make continuity accountable

6 minutes

State how roles, relationships, routines, and resources can endure beyond individuals, and what should stay adaptable. Share the plan and confirm the first review.

Keep the labels shown so related answers remain distinguishable. An explicit unknown is useful.

Include: Durable structure / shared capacity / backup · Purpose to preserve / features to adapt · Unconfirmed commitments / next verification · First action / owner / review / return route

Done when

Readiness is justified or a return route is assigned; essential and adaptable features, distinct roles, support gaps, next actions, three evidence horizons, an adaptation log, review rules, and continuity responsibilities are recorded.

One next move

Verify support and continuity commitments with the Change Leadership Support and Sustainability Map.

This preserves the local synthesis of implementation, adaptation, organizational learning, participatory design, and equity-centered change; it does not assert a validated implementation protocol. The brief is a Collaboratory presentation adaptation of this tool; its established sources and local contributions remain attributed in Optional support. CAST UDL Guidelines 3.0 informs the navigation and participation supports.

Optional support

Preparation, pacing, and participationPrepare the starting information and access supports; allow time for the activity and its follow-through.

Test records, affected perspectives, a provisional direction, and people with implementation knowledge and decision authority.

45–60 minutes for a prepared, near-term first pass; steps allocate 50. Allow 60–90 minutes or several sessions for a fuller plan and verified commitments. Review and implementation occur later.

Share purpose and prompts in advance when possible. Offer private preparation, accessible formats, and a recorder or partner. Plan how outputs will be returned, stored, and reviewed.

Sources, adaptations, and attributionReview the intellectual foundations, local contributions, and suggested citation.

Source and attribution

Implementation, adaptation, organizational learning, and equity-centered change

This plan synthesizes implementation-science attention to context, fit, core components, adaptation, implementation indicators, and sustainability with participatory design, developmental evaluation, organizational learning, and higher-education change practice.

The Resource Hub contributed this particular synthesis and planning structure. The underlying traditions and frameworks retain their established attribution.

Authorship, foundations, and suggested citation

Synthesized and developed by Jessica A. Leveto, Ph.D.

Intellectual foundations: Implementation science, developmental evaluation, participatory design, organizational learning, equity-centered implementation, and higher-education change practice.

Suggested citation: Leveto, Jessica A. 2026. “Change & Implementation Plan.” Sensemaking Collaboratory Resource Library. https://sensemakingcollaboratory.org/resources/tools/change-implementation-plan.