How to Turn a Stagnant Interaction Checklist into a Practical Design Tool

Value and Goal of the Interaction Checklist

Interaction designers are familiar with self‑checklists, but many end up unused. In our team the original checklist sat idle like a product with no users. To avoid that, I spent a weekend iterating the checklist, focusing on its purpose and value.

Checklist value:

Helps designers review their work comprehensively, catching gaps in scenarios and details.

Visualizes designers' blind spots, reinforcing memory of product structure, user scenarios, and interaction details.

Ultimate goal: designers no longer rely on the checklist; it becomes an internal mental aid, with the paper form only serving as a transitional tool.

Problems of Checklist 1.0

The original version suffered from three main issues:

Long access path: stored as an Excel file, opening it required multiple steps, increasing friction.

Poor reading experience: disorganized structure made it hard to grasp at a glance; mixed horizontal and vertical layouts forced scrolling.

Out‑of‑date content: because nobody used it, updates lagged, and maintaining four separate documents for each platform was cumbersome.

Establishing Checklist 2.0

After identifying the problems, I focused on two improvement dimensions: document format and content structure.

Document format – from online to offline: I printed the checklist on a single A4 page so designers can grab it instantly, annotate, and avoid the time‑consuming search process.

Content structure – a Mario‑style layout: To make the many checklist items memorable, I mapped them onto three parts of a classic Mario game scene: background environment, game path, and player character.

The three templates derived from this metaphor are:

Environment: hardware, software, and email environments.

Process Path: entry points, pages & controls, forward/back actions, and prompts.

User Operations: gestures, mouse, keyboard, and other inputs (e.g., Touch Bar, voice).

Each template is further broken down; for example, the process path aligns game start/end with entry/result, level pages with UI controls, and character movement with next/previous actions.

Usage Scenarios and Summary

To ensure adoption, the new checklist should be printed, shared via a short PPT, and introduced to the team.

Typical scenarios include:

After design reviews: capture newly discovered issues, mark them on the checklist, and later sync updates to the digital version.

After design completion: use the checklist to verify interaction scenarios and details before final hand‑off.

New‑hire training: mentors can explain product structure and terminology using the checklist’s keywords, accelerating onboarding.

In summary, a well‑designed checklist should be easy to access, readable, and regularly updated. By iterating its format and structure—and aligning it with familiar visual metaphors—designers can move toward the ideal state of “no checklist in hand, checklist in mind.”