10 Practical Prompt Patterns for Copilot in Teams and Facilitator
Excerpt: Users often know that Copilot exists, but they do not know what to
ask. A small prompt library makes adoption much easier.
What a user can achieve
·
Use repeatable prompts for
meetings, chats, channels, and recaps.
·
Teach users to include scope,
role, and output format.
·
Create team-specific prompts
for common workflows.
Step-by-step guide
1. Start with the result you want: summary,
decision log, risk list, action plan, or email draft.
2. Add scope: this meeting, this thread, last 24
hours, or the current agenda item.
3. Add audience: project manager, support lead,
executive sponsor, or customer team.
4. Add format: table, bullets, short email,
decision record, or task list.
5. Save useful prompts in your team guidance or
use Microsoft prompt resources where available.
How it works in practice
The best
Copilot prompts are not long. They are specific. A simple pattern is: task plus
context plus format plus quality rule. Example: "Summarize this meeting
for a project sponsor in five bullets and separate decisions from
opinions." For Facilitator, prompts should support the group, not only one
person. Example: "Track agenda progress and warn us when a decision is
still missing." For Teams chat, ask for a time range and topic. Example:
"Summarize yesterday's discussion about the migration issue." For governance,
add a review rule: "Mark anything uncertain as needs verification."
Teams can build a shared prompt library for recurring meetings, support
handovers, incident reviews, and customer workshops.
|
Copy-paste prompt: Use this structure:
My role is [role]. Analyze [meeting/chat/channel]. Focus on [topic]. Return
[format]. Mark uncertain items as needs verification. |
Comments
Post a Comment