Description
A moderated, courtroom-style meeting where expert inspectors present evidence of usability problems and the design team may rebut each one.
Formal usability inspection adapts software code inspection to interfaces. A moderator acting as judge runs a meeting in which the interface is presented and inspectors argue its merits and weaknesses; design-team members may contest the evidence for each alleged problem, and the moderator rules on whether it stands. In the inspection tradition, roles are defined (moderator, inspectors, recorder, owner), inspectors prepare individually with checklists or heuristics before a logging meeting, and agreed problems are followed up and verified as fixed. Shneiderman and colleagues note it is educational for novice designers and managers, who see problems argued in the open, but it takes longer to prepare and needs more people than other reviews. Reviewers should note problems rather than design solutions and respect the team's investment.
Attributes
- Discipline
- Usability & Evaluation
- Loss type
- Extinct
- Stage
- Design, Evaluation
- Data
- Analytical / expert
- Effort
- Days
Steps
- Appoint a moderator, expert inspectors, a recorder and design-team representatives.
- Circulate the interface, scenarios and any heuristics or guidelines in advance; inspectors prepare problem lists individually.
- In the meeting, present the interface and each alleged problem with its evidence.
- Allow the design team to rebut; the moderator rules on whether each problem stands.
- Record agreed problems with severity and owner, and note disputed items.
- Follow up to verify fixes.
Sources
- Designing the User Interface (Shneiderman et al., 2018)
Also known as
- Courtroom-style usability inspection
- Adversarial design review
Categories
- User Research
- Usability & Evaluation