Atarim for UX/UI Designers: Managing Design Reviews and Iterations

The work of iterating is not the redesign. It is reconciling six comments from four people across three channels, working out which ones contradict each other, and establishing whether the note about the header applied to this round or the last one. Atarim removes most of that by attaching feedback to the design and the version it was given on.

Feedback lands on the design itself, on the version it was left on.

The work of iterating is not the redesign. It is reconciling six comments from four people across three channels, working out which ones contradict each other, and establishing whether the note about the header applied to this round or the last one.

Atarim removes most of that by attaching feedback to the design and the version it was given on. This guide is about being the person receiving and acting on that feedback, rather than the person running the review.

Getting Your Work In

Uploads are capped at 20 MB and 20 files per batch, so a large set needs splitting before you start.

Instructions:

Uploading several related files at once groups them into a collection, which suits a set of screens better than adding them one by one.

Iterating in Versions

Versions are what stop round three inheriting round two’s comments. Feedback stays attached to the version it was left on, which means your revision history doubles as a record of why each change happened.

Instructions:

Two constraints are worth knowing. The last remaining version cannot be deleted, and version actions are permission-gated — without the right permission you see You do not have permission to create new versions rather than a silent failure.

What You Can Do from the Info Bar

Designs can also be dragged in the grid to reorder them, which is quicker than moving one position at a time when sequencing screens for a walkthrough.

Signalling Where a Design Is

Status is set from the Design Status control in the bottom bar, with the tooltip “change status for the current design in view”. It applies to whichever design you are looking at.

Reading the Feedback You Get

Reviewers click the part of the design they mean and type. Each comment becomes a task pinned to that point, on that version. When a design has no feedback yet, the sidebar prompts reviewers to click any part of the design to leave their feedback.

Responding and Handing Work Back

Each piece of feedback is a task with a status and a priority. Statuses run Open, In Progress, Pending Review, and Complete; priorities run Low, Medium, High, and Critical.

You can annotate your reply as well as your reviewers can annotate theirs. The comment box carries an annotation control that opens a window headed Annotate screenshot, with arrow, rectangle, circle, pen, and text tools, plus Undo, Redo, and Fit to Screen.

Working Through a Round

By round three the list is long. The designs sidebar carries filters built for this.

Talking to Your Team, Not the Client

Comments and tasks can be marked internal, which hides them from guests and clients. This is where you raise that a request breaks the grid, or that something will cost more than it is worth — on the design, without it landing in the client’s review.

Getting an AI Opinion Before the Review

Atarim’s AI team can review a built page before your human reviewers see it. Two members matter most to a designer.

Reviews are started from a page in the collaboration view. At least one agent must be enabled, and only one review runs at a time. Findings come back in the Review tab in the sidebar, grouped by the viewport they were found in; selecting one takes you to it on the page.

Benefits for a Designer

Fewer rounds is the compounding benefit. See Reducing Feedback Cycles With Visual Collaboration

Example Use Cases

Known Limitations

FAQs

Common issues

• “You do not have permission to create new versions” — your role on this project does not carry version rights. Ask an administrator.
• The version delete option is unavailable — it is the last remaining version. Delete the design instead if that is what you want.
• A Figma import brought in the whole page — no frame was selected when the URL was copied. Select it and import again.
• Upload failed — check the batch against the 20 MB and 20 file limits and that the file type is supported.
• You cannot see the Design Status control — page approvals are not on your plan, or your role does not carry the status permissions.
• A brand new design already shows as In Progress — no status has been set. The badge falls back to In Progress.
• Feedback landed on an old version — the reviewer was viewing it. Check the version selector before the next round opens.
• Reviewers cannot open the design — it has not been shared with them yet.
• Internal tasks are locked — not on your plan. Do not assume a comment is hidden from the client.
• The designs view is cramped — the browser is narrower than recommended. Widen the window.

Conclusion

Add versions rather than new designs, set Needs Review instead of messaging someone, name conflicts instead of quietly picking a side, and let the client close their own requests. The context arrives free — the discipline is in how you respond to it.

Understanding how the review is being run makes it easier to work with. Explore Atarim For Design Leads