Interpreting Your Results

Scores Tell You Where. Findings Tell You Why.

You have category scores, findings, and severity levels. Now what?This lesson explains how to read your results and communicate them clearly.

What the Scores Tell You

Excellent: Maintain, don't break

Good: Minor polish only

Mixed: Needs attention

Poor: Prioritize fixes

Critical: Fix before release

Look for Patterns

Multiple low scores across categories signals systemic UX problems. One category very low while the rest are fine means an isolated gap with a focused fix. Many containment flags means a governance review is needed. Low Control combined with low Trust scores suggests agent autonomy is too high.

Scores Are a Snapshot, Not a Verdict

A 2 Star score doesn't mean "bad product." It means "this area needs work." Audits inform improvement, not judgment.

Prioritizing What to Fix

Fix CRITICAL findings first, then categories scoring or, then clusters of flags, then MAJOR findings. MINOR issues can wait until time allows.Don't fix everything at once. Focus on what harms users most.

Communicating Results

need evidence, exact behaviors, and reproduction steps.Use the Report Template to structure your output.

Communicating Results

Executives - need overall health, critical risks, and top 3 priorities.
Product teams - need category scores, specific findings, and recommendations.
Engineers - need evidence, exact behaviors, and reproduction steps.

Good Audits

A good audit delivers clear category health, prioritized findings with CRITICAL first, actionable recommendations, and evidence for every claim.Your value isn't the score — it's telling teams where risk lives and what to fix first.

Interpreting Your Results

You must be logged in to access this course

Foundation

Agent Experience Assessment

Task Scenario Library

Failure Patterns

Real Audit Example

Downloads & Templates