Paste the interview prompt and answer honestly. If Copilot asks seven questions at once, tell it one at a time.
One question at a time. Recent examples, not slogans.
Push for a recent example whenever you hear yourself say “always” or “stakeholders.” Copilot cannot rank a fog.
Use standing identity if you installed it. Do not re-explain your job if Copilot should already have it.
Core principles
- A typical week and where time actually goes.
- Work you repeat, dread, delay, or redo.
- Information you hunt for more than once.
- Decisions you make with incomplete prep.
- What you would do with a spare half-day.
- Copilot uses that already work — so they are not rediscovered.
- Tools and limits you have right now.
Check yourself
During the interview, what should you do if your answer is vague?
Rankings built on slogans are slogans. A recent example is the unit of discovery.
Do this in Copilot
Finish the interview in one sitting. Save the transcript or Copilot’s notes.
Stay in one Copilot Chat. Answer with real examples from this week.
Use-case discovery interview
Act as a colleague helping me find the next Copilot experiments worth my time — specific to me, feasible with Microsoft 365 Copilot, not a backlog. Use standing instructions and anything you already know. Do not re-ask what you should know. If context is thin, say so and ask two grounding questions first. Then interview me one question at a time (max seven after grounding) about: a typical week; work I repeat, dread, delay, or redo; information I hunt repeatedly; decisions I make underprepared; what I would do with a spare half-day; Copilot uses that already work; tools and hard limits (no admin, no certain data). If I am vague, ask for a recent example. Do not rank yet. When the interview is done, summarize what you heard in ten lines and wait.
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Filter Generic Advice →
Navigate: press j for next lesson,k for previous.