Skip to main content
Bring your challenges. Leave with possibilities. Save your seat for ESPC Microsoft 365 and AI Conference!
Register now

Move beyond activity reporting

After a Champion-led activation, it’s easy to focus your reporting on what happened: how many people attended, how many prompts were shared, or how much feedback came in. Those details matter, but they don’t necessarily tell you what changed or what you should do next.

That’s where a one-slide impact readout comes in. Rather than simply summarizing the activity, it connects what you set out to accomplish with the strongest evidence you have so far. Just as importantly, it acknowledges what the evidence doesn’t tell you.

A clear impact readout
answers five questions:

  1. What did we intend to do? The outcome or behavior the effort was meant to support.
  2. What’s the strongest evidence? The signal that most clearly shows progress.
  3. Where is the evidence limited? What the evidence doesn‘t yet prove.
  4. What can we reasonably conclude? The most credible interpretation.
  5. What do we recommend and why? Whether to continue, change, scale, or stop the activation.

Gather your evidence

You don’t need perfect data to evaluate whether an activation is showing promise, but you do need enough information to connect the activity to the outcome it was designed to support.

Before building your readout, bring together the information and evidence you already have:

InputConsiderations
Intended outcomeThe behavior, workflow, confidence shift, or business result the activation was meant to support
Session detailsWhat you ran, who it was for, and when it happened
Available metricsParticipation, completion, repeat use, satisfaction, or other relevant usage signals
Examples of storiesConcrete ways employees applied the workflow or used Copilot differently
Feedback or blockersWhat helped, what didn’t, and what support employees still need

You may not have every input, and that’s okay. Rather than filling every evidence gap, focus on what the evidence you do have can reasonably tell you.

1. Start with the intended outcome

Return to what the activation was meant to change. Ideally, it identifies the behavior, workflow, confidence shift, or business result you hoped to influence. If the original outcome was broad, clarify the change it was intended to support before evaluating the evidence. For example, your intended outcome might have been:

Four teams will use Microsoft Copilot to create clearer, more consistent stakeholder updates from project inputs.

This gives you something specific to evaluate. You’re not only asking whether people attended a workshop, but whether the workshop helped teams practice a useful workflow and produce better updates.

Compare that with an activity-focused statement:

We hosted a stakeholder update workshop.

That tells you what happened, but not what you hoped would change. Connecting the activity to its intended outcome gives the evidence context.

2. Turn evidence into a credible conclusion

Once you’ve reviewed the intended outcome, you can evaluate the evidence. That might include metrics, examples, stories, feedback, or blockers. No single signal tells the whole story. The goal is to identify what most clearly indicates progress, what remains uncertain, and what you can reasonably conclude from both.

A simple structure keeps that interpretation grounded:

Readout elementQuestion to answerExample
Strongest evidenceWhat most clearly indicates progress?Faster updates, clearer summaries, more consistency
Important limitationWhat does the evidence not yet show?Small pilot group, repeat use not yet measured
Reasonable conclusionWhat can you credibly claim based on the evidence?Practical value observed, but business impact not yet confirmed

The limitation is just as important as the positive evidence. It keeps the conclusion credible and gives decision-makers the context they need to understand both what happened and what still needs to be tested.

Use language that reflects the strength of your evidence:

If you have…You can say…
Participation or completion data“The activity reached…” or “Employees completed…”
Feedback or satisfaction signals“Feedback indicates…” or “Employees reported…”
Examples of work outputs“Examples show…” or “Teams applied Copilot to…”
Early repeat-use signals“Early signs suggest…”
Limited or incomplete data“The evidence does not yet show…” or “More evidence is needed to understand…”

Be cautious about making causal claims. Avoid saying the activation “created business impact” unless the evidence supports that conclusion. In many cases, an early signal is enough to inform a useful next step.

3. Decide what to do next

An impact readout shouldn’t just summarize activity. It should present evidence to help you make a decision.

Your decision will generally fall into one of four categories:

DecisionUse whenExample next step
ContinueEarly signals are positive, but you need more evidence before expanding.Run the workshop with another team and measure repeat use.
ChangeThe activation reached people, but feedback or blockers show that the approach needs adjustment.Update the scenario, audience, support model, or facilitation approach.
ScaleEvidence shows a repeatable workflow or practice that other teams can use.Package the example and expand to similar teams.
StopThe activation didn’t produce useful signals, solve the intended problem, or justify more investment.Retire the activity and try one that better fits the need.

In the stakeholder update example, the recommendation might be:

Continue for one more cycle with another team and measure whether participants reuse the workflow over time.

That recommendation matches the strength of the evidence. The activation showed early value, but there isn’t enough evidence yet to support scaling broadly.

4. Build your impact readout

Now, bring all the pieces together into a five-line impact readout:

Readout lineSample statement
We intended to:Help four teams use Copilot to create clearer, more consistent stakeholder updates from project inputs.
The strongest evidence is:Four teams completed the workshop and guided practice. Feedback indicates employees created updates faster, and several teams shared clearer, more consistent examples.
The evidence is limited by:The evidence comes from a small number of teams, and repeat use hasn’t yet been measured.
We can reasonably conclude:Early signals suggest the workflow has practical value, but the evidence doesn’t yet demonstrate sustained adoption or broader business impact.
We recommend:Continue for one more cycle with another team and measure whether participants reuse the workflow over time.

You can use the completed readout slide in a status update, leadership review, Champion community discussion, or planning conversation.

Microsoft Copilot logo

Use Cowork to choose and plan your activation

Once you've narrowed your options, use Copilot or Cowork to help you choose an activation and turn it into a simple plan.

Example prompt

Create a one-slide impact readout from the following five statements. Make it concise, credible, and appropriate for an adoption or leadership update. Do not overstate the impact. Include the intended outcome, strongest evidence, important limitation, reasonable conclusion, and recommended next step.

We intended to: [outcome]
The strongest evidence is: [evidence]
The evidence is limited by: [limitation]
We can reasonably conclude: [conclusion]
We recommend: [continue, change, scale, or stop + your reason]

Discover more resources for Champions

Find practical guidance, tools, and prompts to help you drive Copilot adoption and engage your team.

Explore resources
Drive value with Microsoft 365 user enablement tools
Microsoft Frontier Tour