Catalogue › Copilot Adoption

CopilotForge - Copilot Adoption

Use it in Copilot Cowork: download the Copilot Adoption plugin for Copilot Cowork and upload it under Customize > Plugins > Upload plugin. How to install.

Design and run organisation-wide or business-unit Microsoft AI adoption programmes, from readiness and scenarios through launch, reinforcement and measurement.

Layer: adoption
Lead role: Adoption Lead
Plugin name: copilotforge-copilot-adoption

Skill Status Lifecycle Description

adoption-measurement draft Discover, Measure, Improve Defines how Copilot adoption is measured across usage, capability, behaviour change and business outcomes, with baselines set before launch, team or role-level reporting above a minimum group size, and feedback loops that change the programme. Use when setting adoption measures, when a sponsor asks whether Copilot is working, or when someone proposes tracking individual usage.

adoption-readiness draft Discover, Mobilise Assesses whether an organisation or business unit is ready to adopt Microsoft Copilot across sponsorship, licences assigned versus used, IT-led technical enablement, data and permissions hygiene, approved-use guidance, support and communications, and records the gaps to close before launch. Use when licences have been bought or are about to be, before a launch date is fixed, or when early use has stalled.

adoption-reinforcement draft Launch, Measure, Improve Runs the always-on reinforcement cycle for Copilot after launch - a calendar of nudges and refreshers, scenario refreshes, manager follow-up prompts, re-engagement of teams whose use has faded and refreshers when Copilot changes - triggered by team-level signals, never individual tracking. Use when launch is over and use is plateauing, when teams drift back to old habits, or when a Copilot change must reach existing users.

adoption-support-model draft Mobilise, Launch, Improve Designs the user support model for Copilot - self-help, Champions as first-line peer guidance, office hours, the IT service desk, admin escalation to Microsoft, the security route for suspected data exposure and the intake route for ideas - with triage categories, capacity and a feedback loop. Use when Copilot is about to launch, when Champions or the service desk are overwhelmed, or when nobody knows where Copilot questions go.

audience-segmentation draft Discover, Envision, Mobilise Builds the adoption audience model for a Copilot programme by grouping the workforce on work pattern, Copilot access, device and shift constraints, information sensitivity and change impact, using aggregate HR and IT data, then sizing each audience and setting how it is reached, onboarded and supported. Use when one message is going to everyone, when waves need defining, or before personas and scenarios are chosen.

copilot-onboarding draft Enable, Launch Designs the onboarding experience each newly licensed or enabled Copilot user receives - access confirmed before the welcome, approved-use guidance in plain words, a first session on starting scenarios, first-week tasks and where to get help - as a repeatable flow for launch waves, new joiners and people changing role. Use when access is being switched on, when new joiners get Copilot with no guidance, or when onboarding was a one-off launch.

executive-enablement draft Mobilise, Enable, Launch Enables executives to use Copilot in their own work and lead its adoption visibly - private or small-group sessions on their real tasks, support for executive assistants and chiefs of staff, care with sensitive leadership content, and the visible behaviours that give others permission to experiment. Use when leaders hold licences but rarely use them, before a launch where executives go first, or when leaders' messages about AI ring hollow.

frontline-enablement draft Envision, Enable, Launch Enables frontline and deskless workers to adopt AI safely - confirming with IT and the licensing route which experience and device each frontline audience can use, choosing a few shift-relevant scenarios, teaching in huddles and on mobile within paid time, involving supervisors and employee representatives, and adapting support and Champions. Use when frontline teams join a rollout, were left out of one, or found desk-based training useless.

launch-plan draft Mobilise, Enable, Launch Plans a phased Copilot launch with onboarding by persona, executive and manager enablement, reinforcement through office hours and Champions, a support model and a feedback loop that keeps improving the programme. Use when readiness gaps are known and a rollout needs sequencing, when a big-bang launch is being proposed, or when a launch happened but nothing followed it.

role-based-adoption draft Enable, Launch, Scale Designs an adoption journey for each priority role - first scenarios, guided practice on real work, team routines and later extension to Cowork tasks or agents - with role-specific onboarding, manager expectations, peer support, milestones and team-level success signals. Use when a role group needs more than generic onboarding, when a sponsor names priority roles, or when a role's use has stayed shallow.

scenario-discovery draft Discover, Envision, Enable Segments the workforce into personas such as desk, hybrid and frontline workers, discovers role-based Copilot scenarios with business owners, prioritises them by value and frequency, and builds a scenario catalogue with prompt patterns that users can verify. Use when planning what people will actually do with Copilot, when usage is generic and shallow, or when a new team or role joins the rollout.

Skill	Status	Lifecycle	Description
`adoption-measurement`	draft	Discover, Measure, Improve	Defines how Copilot adoption is measured across usage, capability, behaviour change and business outcomes, with baselines set before launch, team or role-level reporting above a minimum group size, and feedback loops that change the programme. Use when setting adoption measures, when a sponsor asks whether Copilot is working, or when someone proposes tracking individual usage.
`adoption-readiness`	draft	Discover, Mobilise	Assesses whether an organisation or business unit is ready to adopt Microsoft Copilot across sponsorship, licences assigned versus used, IT-led technical enablement, data and permissions hygiene, approved-use guidance, support and communications, and records the gaps to close before launch. Use when licences have been bought or are about to be, before a launch date is fixed, or when early use has stalled.
`adoption-reinforcement`	draft	Launch, Measure, Improve	Runs the always-on reinforcement cycle for Copilot after launch - a calendar of nudges and refreshers, scenario refreshes, manager follow-up prompts, re-engagement of teams whose use has faded and refreshers when Copilot changes - triggered by team-level signals, never individual tracking. Use when launch is over and use is plateauing, when teams drift back to old habits, or when a Copilot change must reach existing users.
`adoption-support-model`	draft	Mobilise, Launch, Improve	Designs the user support model for Copilot - self-help, Champions as first-line peer guidance, office hours, the IT service desk, admin escalation to Microsoft, the security route for suspected data exposure and the intake route for ideas - with triage categories, capacity and a feedback loop. Use when Copilot is about to launch, when Champions or the service desk are overwhelmed, or when nobody knows where Copilot questions go.
`audience-segmentation`	draft	Discover, Envision, Mobilise	Builds the adoption audience model for a Copilot programme by grouping the workforce on work pattern, Copilot access, device and shift constraints, information sensitivity and change impact, using aggregate HR and IT data, then sizing each audience and setting how it is reached, onboarded and supported. Use when one message is going to everyone, when waves need defining, or before personas and scenarios are chosen.
`copilot-onboarding`	draft	Enable, Launch	Designs the onboarding experience each newly licensed or enabled Copilot user receives - access confirmed before the welcome, approved-use guidance in plain words, a first session on starting scenarios, first-week tasks and where to get help - as a repeatable flow for launch waves, new joiners and people changing role. Use when access is being switched on, when new joiners get Copilot with no guidance, or when onboarding was a one-off launch.
`executive-enablement`	draft	Mobilise, Enable, Launch	Enables executives to use Copilot in their own work and lead its adoption visibly - private or small-group sessions on their real tasks, support for executive assistants and chiefs of staff, care with sensitive leadership content, and the visible behaviours that give others permission to experiment. Use when leaders hold licences but rarely use them, before a launch where executives go first, or when leaders' messages about AI ring hollow.
`frontline-enablement`	draft	Envision, Enable, Launch	Enables frontline and deskless workers to adopt AI safely - confirming with IT and the licensing route which experience and device each frontline audience can use, choosing a few shift-relevant scenarios, teaching in huddles and on mobile within paid time, involving supervisors and employee representatives, and adapting support and Champions. Use when frontline teams join a rollout, were left out of one, or found desk-based training useless.
`launch-plan`	draft	Mobilise, Enable, Launch	Plans a phased Copilot launch with onboarding by persona, executive and manager enablement, reinforcement through office hours and Champions, a support model and a feedback loop that keeps improving the programme. Use when readiness gaps are known and a rollout needs sequencing, when a big-bang launch is being proposed, or when a launch happened but nothing followed it.
`role-based-adoption`	draft	Enable, Launch, Scale	Designs an adoption journey for each priority role - first scenarios, guided practice on real work, team routines and later extension to Cowork tasks or agents - with role-specific onboarding, manager expectations, peer support, milestones and team-level success signals. Use when a role group needs more than generic onboarding, when a sponsor names priority roles, or when a role's use has stayed shallow.
`scenario-discovery`	draft	Discover, Envision, Enable	Segments the workforce into personas such as desk, hybrid and frontline workers, discovers role-based Copilot scenarios with business owners, prioritises them by value and frequency, and builds a scenario catalogue with prompt patterns that users can verify. Use when planning what people will actually do with Copilot, when usage is generic and shallow, or when a new team or role joins the rollout.

Credit

Created by Simon Foote as part of CopilotForge. Content is licensed under CC BY 4.0; keep the credit in each skill's license and authors fields when you share or adapt it. See NOTICE.md in the repository.