Cognitive & Pluralistic Walkthrough Notes

Cognitive Walkthrough

  • Used to evaluate learnability: How easy it is to use a system the first time it's encountered.
  • The evaluator acts as a new user (without involving actual users).
  • Evaluator completes tasks from user stories to assess the interface from a new user's perspective.
  • Evaluators can be team members, UX specialists, product owners, clients, engineers, or stakeholders.
  • Evaluators consider user personas, including their skills and experience.
  • A set of prescribed questions are used to identify interface problems.
  • It's important to consider usability and potential difficulties new users might face.
  • Notes are taken regarding potential changes.
  • This method may be slightly biased and not as effective as methods involving actual users.

Questions to Ask During a Cognitive Walkthrough

  • Will users try to achieve the right result (the overall task goal)?
  • Will users notice that the correct action is available?
  • Is the action easily visible and findable?
  • Is the right affordance provided?
  • Will users associate the correct action with the result they're trying to achieve?
  • Consider metrics like missed clicks.
  • Is the label correct and does it afford the right information?
  • Does the icon have the right mapping that users expect and understand?
  • After the action is performed, will users see that progress is made?
  • System should give feedback to show progress, such as progress indicators.
  • Example: Steps like cart, delivery details, payment, and success.

Pluralistic Usability Walkthrough

  • Similar to cognitive walkthrough but involves a group.
  • Includes a facilitator and participants, including users.
  • All participants assume the role of a user and consider personas.
  • Benefits:
    • Involves users.
    • Can be done early.
    • Discovers different perspectives.
    • Addresses design and usability with experts and users.
  • Limitations:
    • More appropriate for a linear system.
    • Requires a good facilitator.
    • Scheduling can be difficult.
    • Slow due to team discussion at each step.