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.

This guide is about being the person receiving and acting on that feedback, rather than the person running the review.

Getting Your Work In

You can upload up to 20 designs at a time, so a large set needs splitting before you start.

Instructions:

1. Open the project that should hold the design and go to Designs in the sidebar. If you need a new design project first, select Add new on the Projects screen and choose Upload designs or PDFs or Connect to Figma.
2. Select Add design. The upload window opens, headed Upload Design.
3. Drag your files in, or select Upload Files. You can add up to 20 designs at a time, and success confirms with Design added to your project.
4. Or paste a link into Drop a Figma URL Here. Select a frame in Figma before copying the URL to import that design; with no frame selected, the full page is pulled in.

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:

1. Open the design and find the info bar above it.
2. Select Create new version and upload the revised file. The window is headed Add Version, described as useful for comparing different versions of the same design.
3. Use the version selector to move between versions and see what changed.

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.

Signaling 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.

• This Design / All Designs — narrow to what is in front of you, or see the whole project.
• Assigned To Me — cut to what is yours.
• Show Complete Tasks — bring closed work back when auditing a round.
• Show Internal Tasks — include or exclude the team-only conversation.
• Sort by priority, status, date, or unread first.
• Search across tasks and comments as you type.

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. Navi and Pixel matter most to a designer, and the others cover copy, SEO and QA.

Start a page review with Review at the top of the sidebar in the collaboration view. At least one agent must be enabled, and only one review runs at a time. Findings come back in the Tasks tab, as subtasks under the review, grouped by the section of the page they were found in, and selecting one takes you to it on the page. The designs view has no review button yet. To review an uploaded design, ask the AI in a chat to run one.

Benefits for a Designer

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

Example Use Cases

Known Limitations

• The last version of a design cannot be deleted. Delete the design itself if you need it gone.
• Uploads are capped at 20 designs per batch.
• Draft cannot be selected from the status control, although the badge can appear.
• The status control depends on page approvals being in your plan, and on your role.
• Version and design actions are permission-gated, so you may not be able to create or delete versions.
• Figma import depends on frame selection — with none selected, the full page is imported.
• Page reviews start from the collaboration view. The designs view has no review button yet, so ask the AI in a chat to review an uploaded design. Only one review runs at a time.
• Internal tasks and attachments depend on your plan.

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 is 20 files or fewer, and that each file’s size and type are supported.
• Design Status shows a lock, or a status is missing — page approvals are not on your plan, or your role does not carry that status permission.
• 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.
• Screen size too small — design projects need a browser window at least 1024 pixels wide. 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