From strategy to use cases
You'll be able to Map current business processes to find where Copilot assistance creates the most impact.
Find the work, not the feature
Start from real processes. Where do people draft, summarise, search, prepare or rekey? Those are the spots where Copilot assistance shows up as measurable value.
Check what you know
Where should use cases come from?
Start from real tasks people do, not from features Copilot has.
Sources for this bite
The Scenario Library
You'll be able to Explain what Microsoft's Scenario Library offers and how to use it.
Don't start from a blank page
Microsoft's Scenario Library is an interactive catalogue of example Copilot outcomes and success measures by role and industry. Use it to seed your own use-case list and to borrow ready-made measures.
Check what you know
What does the Scenario Library provide?
Seed your use cases from the Scenario Library's role- and industry-based examples.
Sources for this bite
Prioritising use cases
You'll be able to Rank candidate use cases by value, feasibility and visibility.
Three lenses
- Value — how much measurable impact if it works?
- Feasibility — can people do it now, with current data and skills?
- Visibility — will a win be seen and copied by others?
Avoid the scatter
A short list of high-value, feasible, visible use cases beats a long list of maybes. Concentration is what makes value provable.
Check what you know
Which trio prioritises use cases?
Rank by value, feasibility and visibility — a short focused list beats a long one.
Sources for this bite
Choosing your first teams
You'll be able to Select first teams using Microsoft's guidance on whole teams in heavy-usage areas.
Whole teams, heavy users
Pick whole teams in areas of heavy Microsoft 365 usage, so people learn from each other. Scattered individuals don't reinforce each other and are hard to measure.
Check what you know
Who makes the best first cohort?
Start with whole teams who already live in Microsoft 365.
Sources for this bite
Day-in-the-life mapping
You'll be able to Build a role-based, day-in-the-life scenario that shows Copilot value in real work.
Show value in the real day
Walk a role through a normal day and mark the moments Copilot helps: the morning catch-up, the draft reply, the meeting recap, the report. Concrete beats abstract.
Check what you know
What does day-in-the-life mapping produce?
Map a role's real day to show exactly where Copilot earns its place.
Sources for this bite
Defining the pilot
You'll be able to Specify a pilot: duration, participants, use cases and how feedback is gathered.
Pilot spec
- Duration — long enough to form habits, short enough to learn fast.
- Participants — the first whole teams.
- Use cases — the prioritised short list.
- Feedback — how and when you'll gather it.
Check what you know
Which belongs in a pilot definition?
A pilot has four parts: duration, participants, use cases, feedback method.
Sources for this bite
Baselining value measures
You'll be able to Decide what 'impact' looks like and capture the baseline before the pilot starts.
Measure before you move
Decide what impact looks like for each use case and capture the 'before' now. Borrow success measures from the Scenario Library where they fit. Without a baseline you can describe the pilot, but not prove it.
Check what you know
When should you capture the baseline?
Define impact and capture the baseline before the pilot — proof depends on it.
Sources for this bite
Sources & notes
Everything here traces to Microsoft Learn, retrieved June 2026.
Microsoft Learn sources used in this stage
Accuracy flags
- The original taxonomy called 'Envision' a partner term. Microsoft's Phase 1 module is now titled 'Envision a successful adoption of Microsoft 365 Copilot'.