Review the message and, where applicable, the implemented behaviour.
I have a sample. What would help me learn?
Choose whether this review concerns comprehension, usability, or implemented functionality, and prepare the matching comparison.
Lucas prepares a review with an editor and suitable volunteers. Looking at a storyboard is not the same as testing an automated system.
Lucas and every example here are prepared learning material, not a real case or an AI-generated result.
My test-and-improvement plan
- Define the question and level
Specify whether you are reviewing a concept, mock-up, or working function. Do not generalize from one level to another.
- Choose a reference
Use the approved fictional brief and a manual or existing output as comparison.
- Prepare reviewers and tasks
Invite suitable, willing reviewers. Define the task, permissions, and feedback to record. Working software stays in an appropriate test environment.
- Record observations
Document message comprehension, factual inconsistencies, access issues, and correction effort. For a working function, record actual input and output.
- Choose improvements
Prioritize changes, note remaining questions, and select a next decision. A favourable review is not automatic approval to publish or deploy.
What was actually tested?
People understand a storyboard. What does that establish?
Every option has an explanation. Open as many as you like — nothing is recorded or scored.
You have worked through Technology & Creative Industries.
Join Build your project to work on this with the people and programs behind it.