Team Design Review Workspace
Design a review workspace that keeps comments, versions, decisions, and ownership connected to the latest interface work.
The brief
Understand the problem
Background
Product teams review interface work across meetings, chat threads, and design files. When a frame changes, open comments lose context and decisions are difficult to distinguish from suggestions.
User context
Keiko is preparing a checkout update for engineering handoff. A researcher, content designer, and product manager must review it by Thursday, and several comments refer to an older version.
Product problem
The team needs focused review without covering the work in noise, while contributors need to know which version, decision, owner, and deadline applies.
Objective
Create review, comment, version comparison, and resolution states that produce a trustworthy record of what the team decided.
What to design
Define the experience
Required experience
- Open a review with scope, version, owners, and due date
- Leave anchored feedback with a clear intent
- Compare a changed area with earlier context
- Resolve feedback into a decision and prepare handoff
Screens and states
- Review overview
- Focused design review
- Version comparison
- Decision and resolution log
Core user flow
Follow the critical path
- 01
Keiko shares version 7 with three named reviewers
- 02
The content designer requests a label change on the delivery step
- 03
Keiko uploads version 8 and maps the comment to the updated control
- 04
The reviewer approves the change and the final wording enters the decision log
Product rules
Requirements and constraints
Requirements
- Keep review scope and latest version unmistakable
- Support comment types such as question, change request, and approval
- Show stale annotations without silently moving them
- Assign owners and due dates to unresolved decisions
- Preserve a readable history after comments are resolved
Constraints
- Guests may view only invited projects
- A resolved comment cannot be permanently removed from the audit record
- Dense annotation layers must remain navigable by keyboard
Reality check
States worth considering
Finish line
What to deliver
- Four desktop screens covering review through decision
- Interaction notes for stale comments, conflicts, and keyboard navigation
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Playfair Display & Source Sans Pro
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Playfair Display & Source Sans Pro
Clear interface writing gives people the confidence to understand what changed and decide what to do next.