change-management

Produce a behavioral evidence checklist showing what done looks like at the role level. Measures readiness through observable task execution, not training attendance or self-reported confidence.

Produce a structured escalation package for a champion who has surfaced an adoption risk or structural design issue. Triages the issue by category and routes it to the correct response — information clarification, adoption risk mitigation, or sponsor-level structural decision.

Produce a role-based communications strategy and message architecture for a transformation. Run this command once the structural decisions behind the communication are confirmed.

Produce a live decision register tied to the change impact log, with training and readiness dependency tracking. Run this command when functional decisions are open and go-live dependencies need to be mapped.

Produce a dependency map showing which upstream conditions must be in place before training, readiness, and go-live activities can proceed. Run this command when the engagement has multiple open dependencies and a go-live date under pressure.

Produce an engagement close document confirming that the change management program has met the conditions necessary to transition from implementation into sustainment. Run this command at engagement close or when a sponsor asks whether the transformation is ready to stand on its own.

Produce a go-live readiness checklist with structural condition verification. Run this command during the final two weeks before go-live.

Produce a structured change governance decision gate model for the change program of a transformation program. Run /ocm:governance-gates to establish formal SteerCo checkpoints that connect transformation milestones, leadership approvals, and readiness metrics into a single governance architecture.

Produce a change impact assessment with structural risk identification. Run this command when scoping an engagement or when the transformation scope changes.

Produce a dated T-minus milestone schedule anchored to the program's governance gates, change program workplan phases, and readiness dashboard staging targets. Run /ocm:milestone-timeline to generate a single dated artifact connecting all three layers of transformation management into a schedule a practitioner can hand directly to a PMO or sponsor.

Produce a quantitative readiness tracking dashboard for the change program of a transformation program. Run /ocm:readiness-dashboard on a weekly cadence to measure and report adoption readiness to executive sponsors, PMO, and program leadership.

Produce a Day One Readiness Map with go/no-go criteria. Run this command four to six weeks before go-live and update it as the date approaches.

Produce a resistance analysis with category-specific intervention design. Run this command when resistance patterns are visible or anticipated.

Export your practitioner profile, artifact status, and key decisions as a portable block you can paste into a new session. Run this when your session is getting long or before closing a session you plan to continue later.

Produce a sponsor activation brief with a structural decision register. Run this command at engagement kickoff or when sponsor engagement needs to be reset.

Produce a stakeholder and sponsor analysis with structural authority assessment. Run this command at the start of any engagement or when the sponsor landscape changes.

Start here. Run /ocm:start to orient to the plugin, identify where you are in the engagement, and set up your practitioner profile so every subsequent command uses your context automatically.

Produce a structural readiness profile and assess whether the conditions for structural work are present in this engagement. Run this command when you have hit the change program's limit and need to assess whether the sponsor readiness exists to go further.

Produce a role-based training strategy with the Tomorrow Test applied throughout. Run this command once the future state process and role definitions are confirmed.

Produce a structured change program work plan organized across three phases — days 1-30, days 30-90, and days 90 and beyond. Run /ocm:workplan when scoping a new engagement or getting a late-starting program back on track.

Activates when the conversation involves change impact assessment, risk identification, mitigation planning, resistance analysis, or questions about what will be hardest about this change and for whom. Trigger phrases include "change impact", "impact assessment", "who is affected", "risk assessment", "resistance", "what could go wrong", "mitigation", "impact analysis", "who will push back", "what are the risks".

Activates automatically when the conversation involves organizational change, transformation, system implementation, digital adoption, or any discussion of how to get people to work differently. Trigger phrases include "change management", "transformation", "implementation", "adoption", "go-live", "rollout", "change program", "why isn't this working", "resistance", "people side of change".

Activates when the conversation involves communications planning, message development, announcement drafting, change narrative, sender strategy, or questions about how to communicate a change to affected audiences. Trigger phrases include "communications plan", "messaging", "announcement", "what do we tell people", "change narrative", "comms strategy", "how do we communicate this", "email to employees", "town hall", "cascading communications".

Activates when the conversation involves readiness assessment, go-live planning, Day One preparation, risk identification, go/no-go decisions, or questions about whether an organization is prepared to launch. Trigger phrases include "readiness assessment", "go/no-go", "Day One readiness", "are we ready", "readiness map", "go-live risk", "launch readiness", "cutover", "readiness checklist", "who decides if we go live".

Activates when the conversation involves stakeholder analysis, sponsor identification, influence mapping, change impact assessment, coalition building, or questions about who needs to be involved in a transformation. Trigger phrases include "stakeholder map", "who are the stakeholders", "sponsor", "who has authority", "who needs to be on board", "influence", "coalition", "change champion", "who should be in the room".

Activates when the conversation involves post-go-live planning, sustainment strategy, adoption monitoring, value realization, or questions about whether the change will stick after the consulting team leaves. Trigger phrases include "sustainment", "post go-live", "adoption monitoring", "value realization", "will this stick", "what happens after we leave", "30 60 90 day plan", "change agent network", "sustainment plan", "adoption metrics".

Activates when the conversation involves training strategy, learning design, curriculum development, competency assessment, readiness validation, or questions about how to prepare people to work in a new system or process. Trigger phrases include "training plan", "training strategy", "learning design", "curriculum", "competency", "readiness validation", "who needs training", "training needs analysis", "Tomorrow Test", "day one readiness".

Notion workspace — used for live tracking artifacts. Writes decision registers, dependency maps, behavioral evidence checklists, and champion escalation logs to the engagement workspace database.

SharePoint document library — used for deliverable storage. Saves stakeholder maps, communications plans, training plans, readiness maps, and go-live checklists to the engagement folder.

Microsoft Teams — used for program team notifications. Posts escalation flags, training blocker alerts, and go/no-go status updates to the engagement channel.