UX Design Coach

Which checkout screen did they mean? A better Figma design critique

Figma can place feedback beside a design. Use a delivery-and-payment example to check whether the note landed on the right frame and whether it warrants a change.

By Ashley Kays Rabbitt · November 18, 2026

“I need to see the total before I tap that.” If you heard those words during a checkout review, where would you leave the comment? Next to the price on the payment screen seems reasonable. Now imagine the speaker was pointing at “Continue” on the delivery screen. A designer could spend an afternoon polishing a price the shopper still wouldn’t see in time.

On November 9, Figma showed how its agent can use a linked transcript to place feedback alongside relevant designs. On November 12, Granola’s engineers described a discovery from building transcript search. An agent could find a meeting note and answer confidently while missing details that lived only in the conversation. Together, these reports suggest a test for design leads. Can another designer go from a canvas annotation back to the moment that justified it? Figma’s transcript annotation walkthrough · Granola’s transcript retrieval study.

Replay the comment with two frames in view

For a practice critique, name two frames Delivery · v3 and Payment · v3. Delivery shows a shipping choice and a Continue button. Payment shows the first complete total and a Place order button. Imagine that the shopper says the line above while Delivery is visible. A minute later, a teammate suggests making the total bolder on Payment. Both people talked about the total. They supplied different kinds of evidence.

A useful note on Delivery would read, “Shopper wanted the amount due before continuing from shipping selection. See the delivery segment at 02:10.” The timestamp and dialogue in this exercise are illustrative. The teammate’s idea belongs beside Payment as a proposed treatment. Writing it up as a second shopper complaint would manufacture agreement.

Give the agent a smaller job

In Figma’s agent chat, open Connectors, connect the service holding the approved critique notes, and provide the meeting link. Select or identify the frame versions from the session. Try this instruction with a transcript your team can share. Figma’s transcript annotation walkthrough.

Draft one annotation per distinct observation. Include the speaker’s role, a short excerpt and its location, and the frame version visible at that moment if the record establishes it. Put unclear references in a separate list. Leave the designs as they are.

Read the unclear list first. “That button” often makes sense to everybody who was in the room. If the recording, screenshot, or surrounding discussion can’t place it, ask the facilitator while the session is fresh. An unresolved note is cheaper than reopening the wrong design.

Turn one verified observation into a test

Duplicate Delivery. Put the order total below the shipping choices and update it when the shipping method changes. Give a participant one task. “Choose express shipping. Tell me what you expect to pay if you continue.” Record the amount they predict and when they found it. If they mistake the shipping fee for the total, you have a specific hierarchy problem to investigate.

At the end of the next critique, audit five annotations. Can a teammate recover the right frame, the underlying words, and the reason for the proposed change? When one fails, record which link went missing. Frame names fix a different problem from incomplete meeting notes. Knowing which failed will improve the next review more than a tidy wall of comments.