By the end of this lesson you can
- Show how you validated designs in a case study.
- Report outcomes honestly, including partial or unknown results.
- Connect outcomes back to the original problem.
The idea
Outcomes answer the question every reviewer has: did it work? Show both how you tested and what changed.
Validation
Briefly describe usability tests, A/B tests, pilots or feedback sessions. Say what you tested, with whom, and what you changed as a result.
Outcomes
- Quantitative: completion rates, conversion, time on task, support calls, error rates.
- Qualitative: user quotes, stakeholder feedback, observed behaviour.
- Organisational: a pattern adopted by other teams, a process improved, a decision made.
When you lack hard numbers
Many projects never ship, or ship after you leave. Be honest: report test results, the metrics the team planned to track, or what you would measure. "Task success rose from 3 of 6 to 6 of 6 participants in the second round of testing" is a valid outcome.
Link back
Connect outcomes to the problem you set up at the start. If the problem was abandonment at photo upload, report what happened to abandonment.
Why it matters in real projects
Outcomes turn a case study from "here is what I made" into "here is the difference I made". They show you care about impact rather than output. Honest reporting, including uncertain or partial results, builds credibility, while inflated or vague claims are easily spotted by experienced reviewers and can damage trust in the whole portfolio.
A realistic example
A case study about a parking permit service ends: "In two rounds of testing with 12 residents, task completion rose from 7 of 12 to 12 of 12. After launch, phone enquiries about permits fell by about a third over two months. One thing we did not fix: residents with more than one car still found renewals confusing, which the team has planned for the next phase."
The result is specific, linked to the original problem and honest about what remains.
Step by step
Summarise testing
Write what you tested, with whom and what changed.
Collect outcomes
Gather numbers, quotes and organisational effects.
Check accuracy
Make sure every figure is real and attributable.
Handle gaps
If results are unknown, say what was planned or would be measured.
Link to the problem
Show how outcomes address the original problem.
Note what remains
Mention unsolved issues honestly.
Common mistakes
Mistake Inflated or invented numbers.
Instead Report only real, checkable outcomes.
Mistake Outcomes unrelated to the problem.
Instead Link results back to the problem statement.
Mistake Leaving outcomes out because the project did not ship.
Instead Report test results and planned measures.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 30 min
Outcomes section
Write the testing and outcomes section for a case study.
Steps
- Summarise how you validated the design.
- List quantitative, qualitative and organisational outcomes.
- Link each to the original problem.
- Add one honest note about what remains.
Deliverable
A testing and outcomes section.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Show how you validated the design.
- Report quantitative, qualitative and organisational outcomes.
- Be honest when results are partial.
- Link outcomes back to the problem.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Usability testing 101 (opens in a new tab)Nielsen Norman Group
- Measuring success (opens in a new tab)GOV.UK Service Manual
Your notes
Marking complete updates your course and roadmap progress.