Mastering Interaction Review Meetings: A Practical Guide for Designers

What Is an Interaction Review Meeting

In many projects there are two types of interaction reviews: internal team reviews and full project‑team reviews. This article focuses on the latter, where after finalizing a design solution, the interaction designer gathers all stakeholders—including product, marketing, operations, visual design, development, and testing—to confirm the design.

Preparation Before the Meeting

Effective preparation outweighs the meeting itself. Key steps include:

Confirm the interaction plan with the product side before the meeting.

Verify feasibility with developers early to reduce on‑site objections.

Conduct internal reviews to gather professional feedback, especially for newcomers.

Prepare complete interaction documentation; avoid presenting unfinished drafts.

Notify participants at least one day in advance via email, attaching the design documents and clearly stating purpose, agenda, time, location, and attendees.

Reserve the meeting room, set up projector and computer, and arrive ten minutes early to test equipment.

Assign a meeting recorder.

Key Points During the Meeting

The designer leading the review should control the session by:

Briefly introducing the meeting’s purpose and content.

Presenting the solution clearly, highlighting priorities and distinguishing main points from details.

Maintaining direction and authority throughout.

Keeping the duration reasonable (typically 1–2 hours, depending on complexity).

Exuding confidence in the proposed design.

Common Challenges and How to Solve Them

Interaction reviews are not demand or technical reviews; product managers handle requirements, and technical leads handle technical issues. To overcome challenges:

Define design goals and scope at the start, limiting discussion to the meeting’s boundaries.

Address subjective feedback by providing rationales for design choices and persuading stakeholders.

Consider each participant’s concerns and respond constructively.

Keep the discussion focused; steer back if it drifts.

If an issue can’t be resolved on the spot, note it for post‑meeting follow‑up, seek mentor help if needed, and acknowledge any design shortcomings.

Incorporate useful feedback into the design.

Post‑Meeting Work

After the meeting, ensure the following:

Summarize meeting minutes and email them, assigning responsibilities clearly.

Update and redistribute the interaction design documents with any revisions.

Address lingering issues promptly, communicating with relevant parties and informing testers.

Continuously follow up on the overall development progress.

Conclusion

While practices may vary across companies, interaction review meetings are a crucial step in the project workflow. Conducting them smoothly, efficiently, and confidently requires preparation, clear communication, and ongoing improvement. Designers who face challenges in reviews can benefit from these guidelines.