How to Pin Down Vague Design Feedback With Three Questions

When someone says "something's off about this," there are only three things worth asking before the call ends.

Which part are we talking about?
What would closer to right look like?
Is this a decision, or a reaction?

Ask those three and you stop the cycle where you interpret, revise, and hear "that's not really what I meant." Leave without them and no amount of careful note taking will save the next round. In a survey of 464 designers and directors, 84.9% said they find design revision requests burdensome, which tells you this is not a note-taking problem.

This article covers how to actually phrase those three questions, how to record a screen-share review so you can focus on asking them, and the decision list to send within ten minutes of the call.

(This is written for people receiving UI and visual design reviews. If you are looking for design review in the engineering sense, a formal gate where specifications are audited against requirements, this is not that article.)

Three questions that make vague feedback concrete

Most articles land on "clients should be more specific." True, and hard to apply. Clients say "something's off" precisely because articulating design is not their job, so asking them for better vocabulary rarely produces any.

Instead, the person receiving the feedback draws the specifics out with questions. The trick: never ask for vocabulary, always offer a choice.

Question 1: "Which part are we talking about?"

This locks down the scope.

"When you say heavy, do you mean this CTA block, or the overall impression from top to bottom?"

Ask as a two or three way choice. They will move their cursor to show you. Now the words are attached to a target again.

If you are recording, that cursor movement is preserved exactly as it happened.

Question 2: "What would closer to right look like?"

This draws out a reference point.

"Is there a site, or an earlier version, that feels closer to what you have in mind?"

Getting someone to define "trustworthy" is hard. Getting them to name one thing that feels close is easy. Their current site, a competitor, an earlier direction you showed them. Anything works.

Once one reference exists, you can talk in differences. "To move toward that, are we going wider on whitespace, or lighter on copy?" Again, a choice rather than a request for vocabulary.

Question 3: "Is this a decision, or a reaction?"

This one earns its keep.

"Should I treat that as something to change, or were you flagging it for awareness?"

In reviews, decisions, impressions and passing thoughts all arrive in the same tone of voice. Treating all of it as instructions inflates the work, and later someone says "I never asked for that."

Phrase it so nobody is on the defensive. Not "I need you to decide," but "should I treat that as something to change." Framed as moving forward, it never sounds like pushback.

You do not need all three every time. Use them when "something's off" appears.

Four habits for recording a review

To focus on questions, you have to let go of note taking. Recording is what makes that possible.

1. Record the window where the cursor lives

Capture the side that shows the pointing.

If they are sharing their screen and commenting, record that window. If you are sharing the design and they are directing, record your own screen. A recording without the pointing in it loses half its value.

Recording a single window rather than the whole screen also keeps notifications and other clients' work out of the frame.

2. Say something at the start

Mention the recording up front, leading with why.

"I don't want to lose any of the feedback, so I'm going to record just this window. It stays internal for my own work."

Purpose plus scope, in one sentence. That combination almost never gets pushback. For external reviews, see the FAQ below.

3. Say the timestamp out loud when feedback lands

This is your bookmark.

"Right, around here, got it."

Acknowledge out loud while noting the time, or simply repeat the point back a little clearly. The repetition marks the spot in the recording and confirms to the other person that you caught it. Two jobs, one sentence.

4. Read the decisions back before you end

Reserve the last two minutes to say out loud what was decided.

"So we're changing the CTA block spacing and the heading weight. Header color is on hold for now."

It aligns everyone in the moment, and it puts a summary of decisions at the end of the recording, which means nobody has to rewatch the whole thing later.

For recording reviews, try Qureco

A Mac screen recorder that covers per-window capture, no time limit and no watermark in its free tier. It captures the other person's voice with no virtual audio setup.

Download Qureco for Free

The decision list you send afterward

Skip this step and the recording becomes dead weight.

Do not hand over the raw recording. "The hour-long recording is in the folder, take a look" gets watched by nobody, including you.

Keep the recording as evidence and put only the decisions into text. Aim to send it within ten minutes of the review ending.

Five fields are enough.

[LP design review, Oct 2]

1. CTA block area
   Feedback: spacing reads as cramped
   Decision: increase vertical spacing to 24px
   Owner: Shirai / by Oct 6
   Recording: 08:40

2. Heading weight
   Feedback: overall tone is too assertive
   Decision: H2 from Bold to Medium
   Owner: Shirai / by Oct 6
   Recording: 15:12

3. Header color
   Feedback: wants to reconsider
   Decision: on hold (revisit next review)
   Owner: on hold
   Recording: 22:05

Three things make this work.

Separate "feedback" from "decision." What was said and what you will do are different things. Splitting them lets someone correct your interpretation early, while it is cheap
Write down what is on hold. Anything you decided not to act on comes back as "whatever happened to that" unless it is on the list
Include the timestamp. This is what turns the recording into a usable asset. When interpretations diverge, one minute of video settles it

Listing feedback with an owner, a due date and a status is the standard shape in formal design review practice too (what a design review is, Asana). For visual work, the fields end up the same.

To push those decisions into task management automatically, see turning meeting notes into Notion tasks.

Why the questions and the recording work together

Here is the mechanism behind the approach, starting from how rework happens.

Burdensome revision requests are the normal experience

In a survey of 464 designers and directors working in web production, run by STUDIO Inc. from April 3 to 10, 2024, 84.9% reported finding design revision requests burdensome: 38.6% said it happens often, 46.3% said sometimes (survey release).

The reasons given were that the intent behind the revision is unclear so extra clarification rounds are needed, that it is hard to tell which part the revision points at, and that opinions within the client's own organization do not line up. On top of that, 57.4% said "we have countermeasures, but the friction is still there" and 30.7% said "we have no countermeasures." A combined 88.1% have not solved it.

When nearly nine in ten have not solved something, it is not a personal shortfall in your interview skills. It is structural. Structural problems respond to systems, not to trying harder.

The words get separated from what they pointed at

"This part feels a bit heavy, doesn't it."

Write that down and you get "this part feels heavy." Everything "this part" was carrying vanishes in the transcription.

Spoken feedback is not made of words alone. Where their cursor was, how far the page was scrolled, which artboard was on screen. Those three things are what gave the words meaning.

Question 1 locks down the scope, and the recording preserves the cursor movement. Together they reconnect words to targets that would otherwise come apart.

Taking notes means not watching the screen

Reviews move quickly, and feedback arrives in bursts. While you write one point down, the next one lands, and then another. Writing and watching cannot happen at the same time.

What you end up with are fragments. "Spacing." "Color." "Stronger here." None of it means anything the next morning.

Handing the recording job to software is what frees your hands to ask. The recording is not the goal; it is the precondition for asking.

Figma comments capture only what was typed

Figma runs in the browser, so sharing a URL puts everyone in the same file and consolidates feedback in one place (using Figma as a reviewer, Classmethod). Cursor chat, audio chat and comments are all available.

That consolidation works well. For typed feedback, the problem is essentially solved.

The trouble is the asymmetry.

How the feedback arrived	Does it survive	Where it lives
Typed as a comment	Yes	Attached to the element in the design file
Typed in chat	Yes	Detached from what it referred to
Spoken during screen share	No	The listener's memory and notes

In practice most feedback arrives verbally, while someone is sharing their screen. The largest category is the one that survives least, and that gap is what the recording and the decision list close.

What to look for in a recording tool

If you are recording every review, the tool's characteristics start to matter.

Requirement	Why it matters
Per-window capture	Keeps notifications and other clients' work out of frame
No time limit	Reviews run long. Some free apps cut off at 5 or 30 minutes
No watermark	A watermark over the work makes color and spacing impossible to judge
Resolution options	1080p to review the design, 720p when it is only a record
Captures the other voice	Feedback comes out of their mouth. Microphone only records your own acknowledgments

That last requirement is the one that trips people up on macOS. The other person's voice comes out of your speakers as system audio, and capturing it traditionally meant setting up a virtual audio driver such as BlackHole. How to record internal audio on a Mac without BlackHole covers the ways around it.

Qureco is a Mac screen recorder that meets all five in its free tier.

Whole screen or a single window, picked from thumbnails so you never record the wrong thing
No virtual audio setup, with independent toggles for microphone and system audio
No time limit and no watermark. Exports as MP4 or MP3
Resolution options of 1080p, 720p, 480p and 360p

The Qureco recording screen, with independent toggles for microphone and system audio — Qureco official site

On the Pro plan, AI generates minutes from the recording, which gives you a first draft of the decision list.

Download Qureco for Free

One caveat: Qureco has no video editing features. Clipping a specific moment to share, or blurring something out, needs another tool. The workflow in this article keeps recordings as private evidence and sends text, so it does not come up, but the tool is not built for editing and distributing video. It is also macOS only.

Frequently asked questions

I find it awkward to ask about recording

Lead with the purpose and it gets easier. "So I don't lose any of the feedback" or "to cut down the back and forth" puts the benefit on their side. It only sounds like surveillance when the reason is missing. For internal reviews, ask once and then let it become how the team works.

Can I record a review with a client?

Get permission in advance, every time. Say that it stays internal and will not be shared. If they say no, do not record. The three questions and the read-back at the end still work without it. On the legal side, see is it legal to record a meeting.

I don't have time to rewatch recordings

Design the workflow so you never have to. In this approach, the recording exists so that when interpretations diverge, you watch one minute. That is why the decision list carries timestamps. Any workflow that requires watching the whole thing will not survive contact with a busy week.

Isn't Figma commenting enough?

For typed feedback, yes. What it does not cover is everything said aloud during screen share, which is where most feedback actually appears. Use both. Writing your decision list back into Figma as comments, attached to the elements, makes it easier to find later.

What about in-person reviews?

Without screen sharing, audio alone is enough. An audio-only recording on your Mac or a phone voice memo works. If the discussion moves to paper or a whiteboard, the pointing does not survive in audio, so the read-back at the end matters more. Recording in-person meetings on a Mac covers the setup.

Summary

When "something's off" appears, ask "which part," "what would closer look like," and "decision or reaction", always as a choice rather than a request for vocabulary
To keep your attention on asking, hand the recording job to software. Four habits: capture the window with the cursor, state your purpose at the start, mark timestamps out loud, read the decisions back before ending
Within ten minutes, send a decision list. Separate feedback from decision, name what is on hold, attach timestamps
Never hand over the raw recording. Send text, and keep the video as the one minute you watch when interpretations diverge
The approach works because spoken feedback separates the words from what they pointed at. "This part" lives in the cursor position, nowhere else
Figma consolidates typed feedback well, but spoken feedback is out of scope. The largest category survives the least

At your next review, try just one of the questions. Start with the third one, about decision versus reaction. It changes how much work you leave with.

Qureco Screen Recorder

Powerful screen recording app for Mac

Record meetings, let AI handle the notes, just read what arrives in Notion.
Try all features free for the first two weeks.

No Setup RequiredNo WatermarkAI Meeting NotesNotion Integration

Download for Free Learn More

The Qureco Screen Recorder app, showing a video call being captured with the screen and window picker below