Back to blog

How to Dictate Design Feedback a Teammate Can Act On

Turn a spoken reaction into a review comment with a precise location, an observable problem, and a useful next step.

Nov 15, 2026Whisper One TeamWhisper One Team

You are reviewing a signup prototype and something feels off. You can explain the reaction in thirty seconds, but “make the screen clearer” will leave the designer guessing. Dictate the reaction while the prototype is still open, then edit the draft so the next person can find the issue and decide what to do with it.

Use a draft field you are allowed to use. For confidential designs, check your team's policy before speaking about them or sharing a screenshot. The example below describes a fictional community class registration form.

Pick one moment to comment on

Start by locating the friction. Open the screen, reproduce the moment, and write down the version or frame link. Mention the state as well as the screen name. “Registration, after choosing a Saturday session” tells someone much more than “registration page.” If the prototype has several versions, paste the specific reference into the draft after dictating.

Choose one problem per comment. If a layout issue hides a button and a separate label is confusing, make two comments. They may need different fixes. A single comment should have a clear answer to “where would I see this?” before it has a proposed solution.

A screen recording can help when the issue happens during a transition, but a still frame may be enough for a copy issue. Attach only what the reviewer needs and what your team allows you to share.

Say what happened before saying what should change

Describe the action you took and what appeared. Then explain what you expected and why. A rough spoken draft could be:

After I chose Saturday, the Continue button became active, but the selected time stayed below the fold. I expected to see which session I was about to confirm, because the two Saturday sessions have different start times.

Notice where the statement stops. It describes one reviewer's experience and gives the designer a way to check it. It does not assume every visitor will miss the time. If you only suspect a problem, call it a question: “I wonder whether someone on a short screen would notice the selected time before continuing.”

When your reaction is about a word such as “confirm,” paste the actual label from the design. The exact label matters more than getting its spelling right by voice.

Ask for an outcome the reviewer can check

Turn the observation into a request, without committing the team to your first solution. “Could the chosen time be visible before people continue?” gives the designer room to adjust the hierarchy. A possible solution can follow in a separate sentence. You might suggest repeating the time near the button, then ask whether the same information already appears somewhere suitable in the current layout.

If you are asking for a decision, name it. For example, “Can we decide whether a session change should clear the previously selected time?” If you are only making a suggestion, say so. Distinguishing those two lets the person receiving the feedback understand whether you are waiting on an answer.

Check the draft in the destination

Read the comment from the perspective of someone who has not heard your narration. Check the version, state, heading, and action. Remove anything that only makes sense while looking at your own cursor, such as “this part over here.” If the feedback has a condition, keep it with the request: the concern is about short viewports, for instance, so do not file it as a universal problem.

Paste the draft beside the relevant frame or into your team's issue tracker, then open the reference once more before posting. To practice, download Whisper One for a supported Apple Silicon Mac and follow the first dictation guide. If your feedback needs exact steps and environment details, use the guide to dictating a reproducible bug report for the next draft.