sayhushTo dictate actionable design feedback, describe the visible issue, explain its effect on the task, and suggest one next step. Keep preferences and questions separate from observed problems. The final organization and judgment remain yours.
Name the screen and the task
Feedback such as “this feels off” gives a designer little to test. Start with the screen, state and action: “On the empty-history screen, I am trying to find how to begin recording.” This gives the recipient a repeatable context. Avoid claiming that all users will behave like you unless you have evidence from actual research.
An original rough example
A rough draft might be: “The button looks lost and I think the heading is too big. I opened an empty history and couldn’t tell where to start. Maybe bring the shortcut closer to the empty-state text?” This is an illustrative draft, not a measured usability result. It contains one observation, a personal experience and a possible solution; those should remain distinct.
Make the feedback easier to evaluate
Manually edit to: “On the empty-history screen, I could not find the recording shortcut. Could we place the shortcut hint beside the empty-state explanation? Please check whether it is easy to notice at the smaller window size.” This gives the designer something to examine without treating your proposed layout as the only answer.
Anchor the comment to a real artifact
Include the screen name, version or link yourself. If a screenshot is useful, remove private account details first. Sayhush transcribes microphone speech; it does not inspect the design, attach a screenshot or know which frame you are reviewing. Saying “this button” is understandable to you in the moment but may be meaningless to the person reading later.
Separate several issues into several comments
Record one short comment per issue. After insertion, add the appropriate location and review the wording. If color, spacing and task flow are unrelated, splitting them helps the recipient respond individually. Use Pause to think through the impact before recording a request; Stop only when the comment is ready to insert.
Keep the tone precise
Replace blame with a description of the behavior you observed. Preserve uncertainty when you are making a suggestion. Before sending, check that the recipient can identify the screen and decide what to do next. Dictation can make feedback easier to capture, but it does not make a personal opinion a usability finding.