Skip to main content

The 7-step plan

Step One

Define the purpose

Pick one focus area before you ask anything: adoption barriers, prompt quality, time savings, or trust. Tell the team how feedback will be used; improvements, training, or escalation.

Pro tip: People give better feedback when they know it will lead to action.

Step Two

Use multiple lightweight channels

Don’t rely on surveys alone. Mix the methods below to capture both signal and story:

  • Micro feedback: 1 question, sent in Teams chat
  • Pulse surveys: 2–5 questions, using Viva Pulse or Microsoft Forms
  • Live discussion: standup or team meeting
  • Async feedback: dedicated Teams channel
  • 1:1s with power users and skeptics

Pro tip: Surveys give you trends, but qualitative comments are where insights live.

Step Three

Set a predictable cadence

  • Bi-weekly: 1-question micro feedback
  • Monthly: 5-minute pulse survey
  • Quarterly: 30-minute deep-dive or retro

Step Four

Ask sharp questions

Avoid generic “do you like it?” questions and instead focus on specific questions addressing key themes, like task-based usage, overall effectiveness, and enablement asks. Use the question bank on the next page to plan your prompts by theme.

Step Five

Capture and tag

Log feedback in a shared Loop doc or tracker. Tag every item by theme so patterns surface quickly:

  • Prompting
  • Accuracy
  • Time savings
  • Trust
  • Training gaps
  • Technical issues

Note frequency; one-off vs. recurring to separate noise from signal.

Step Six

Close the loop

Share a short “What we heard / What we did” recap with the team. Highlight 1–3 actions taken. Call out ideas implemented, and explain constraints when something can’t change yet.

Pro tip: Example: “You told us Copilot summaries were too long. We’ve added a short-prompt guide for summarization and will revisit this in two weeks.”

Step Seven

Feed insights upstream

  • Share trends with your adoption team
  • Escalate recurring product issues via official channels
  • Contribute insights to your Champion community

Sample question bank

Mix and match across themes. Rotate questions month to month, so champions don’t go on autopilot.

Adoption & Usage

  • What task did you actually use Copilot for this week?
  • Where did Copilot save you the most time?
  • Which scenario have you stopped using, and why?

Effectiveness

  • What worked better than expected?
  • Where did Copilot fall short or feel unreliable?
  • What’s one prompt worth stealing from you?

Trust & Confidence

  • Did you verify Copilot’s output? Why or why not?
  • What makes you hesitate to use Copilot?
  • What would make you comfortable using it on sensitive content?

Enablement

  • What would help you use Copilot more effectively?
  • What prompt or scenario should we document?
  • If we fixed one thing this month, what would lift your usage the most?

Skeptic-specific

  • What were you trying to accomplish when you decided not to use Copilot?
  • Where in your workflow would Copilot need to fit to be worth it?
  • Is the blocker trust, effort, or knowledge?
Microsoft 365 Copilot feedback guide for Champions