Collect examples, speak behavior and impact, then review.

Dictating Feedback and Performance notes starts with evidence, not adjectives. Before you open the note, collect two or three concrete examples from the recent period. For each one, write the date, the situation, what the person actually did, and what happened as a result. Use verbs you could observe from across the room, such as sent, asked, delayed, or rewrote. Leave out labels such as careless, brilliant, or difficult, because a label invites an argument about identity while an example invites a conversation about work. Two solid examples are worth more than a page of general impressions, and they are far easier to discuss.
Ask the person for their own account before you finalize the note. A short conversation often reveals context you did not see, such as a dependency that arrived late or a priority that changed midweek. Write down what they say in their own words, and mark which points you agree on and which remain open. If the conversation changes your view, change the note. Feedback written before the conversation and delivered afterward is not feedback; it is a verdict. The note should record a shared understanding, including the parts where you still disagree and what you will watch next. Write the notes before the meeting, not during it.
Separate what you observed from what you concluded. Observation sounds like the draft arrived on Thursday after the review. Interpretation sounds like the person does not care about deadlines. Both may be true, but only the first can be checked. Write the observation in one sentence, then write your interpretation in a separate line and label it as your reading. When you speak the note, share the observation first and ask whether your reading matches their intent. This habit keeps the note fair and makes it much harder for the reader to dismiss the whole message as opinion. Keep the note in draft until the conversation ends.
Put the evidence in a simple table before you dictate. Use five columns: date, situation, behavior, impact, and agreed action. Fill one row per example, and leave the action column empty until you have discussed it. A table forces you to notice when an example has no impact or when an action has no owner. It also shows whether your examples cluster around one theme or scatter across many, which changes how you open the note. Keep the table beside the draft while you speak, and read from it rather than from memory. The two lines stay separate in the final note. That separation is the whole method.
Speak each point in three parts: when the situation happened, what the behavior was, and what changed as a result. Then add the next step as a fourth part. For example: in the Tuesday review, the summary arrived after the meeting had started, which meant the group decided without the numbers, so next time send the summary the afternoon before. The pattern is situation, behavior, impact, request. It gives the reader a clear picture without turning the note into a character judgment, and it makes the requested change easy to accept or discuss. Four parts, one point, no detours. Say them in that order every time.
Use one example per point. Stacking three examples under one heading feels like a case file and puts the reader on the defensive. Choose the clearest example, state it once, and mention that it is part of a pattern only if you have the evidence. Replace always and never with specific counts or dates, because absolutes are easy to dispute and hard to prove. Name the behavior with a verb the person can repeat or stop. If you cannot describe the behavior in a sentence a colleague would recognize, the point is probably still an impression rather than an observation.
Describe the impact at the level where it actually landed. If a late draft delayed a decision, say which decision and for how long. If a clear summary helped a new colleague, say what the colleague was able to do. Do not inflate a small effect into a company-wide consequence, because the reader will know the difference and stop trusting the rest of the note. Distinguish actual impact from likely impact: this delayed the review by a day is different from this could delay future reviews. Keep the first, and offer the second as a concern rather than a fact.
End each point with a next step the person can own. Write it as a small, dated action: send the summary by four on the day before the review. Say what support you will provide, such as a template or a ten-minute check the first time. Then ask whether the action is realistic, and adjust it if the person proposes something better. A next step that the reader helped shape is far more likely to happen than one handed down. Record the agreed version in the note, with the date it will be reviewed. A next step without a date is a hope.
Do not bury a correction between two compliments. The sandwich makes the reader wait for the bad part and discounts the praise. Instead, separate the note into two clear sections: what worked and what needs to change. Give each section its own examples and its own level of detail. The reader can then take the praise at face value and focus on the correction without scanning for hidden criticism. This structure is more direct and, in practice, more respectful than a compliment used as a delivery mechanism. Two sections, two purposes, two sets of examples. The reader should never have to guess which is which.
Make praise as specific as correction. Instead of great job on the launch, say the launch checklist you built caught two missing approvals before they became delays. Name the behavior, the moment, and the effect. Specific praise tells the person what to repeat, which is the practical purpose of positive feedback. It also makes the note credible, because a reader who sees precise praise is more likely to trust the precise criticism that follows. Generic praise reads as politeness, and politeness is easy to discount. Praise that names the behavior can be repeated next quarter. Praise that names only the outcome cannot. Say what you saw, not how you felt.
Keep the correction on the work, not on the person. Describe the draft, the decision, or the handoff, and avoid labels that describe character. One clear correction is better than five small ones, especially in a written note that the reader will revisit. If several issues share a root cause, name the root once and give one example. If the issues are unrelated, choose the one with the largest impact and put the rest on a coaching list for later conversations. A note that tries to fix everything fixes nothing. Describe the work as a draft you both can edit. That framing keeps the tone calm.
Balance is not the same as equal time. If the honest weight of the note is mostly correction, say so, and do not manufacture praise to soften it. A reader can tell when the positive section exists only to cushion a blow. End with the priority: the one change that matters most before the next review. That sentence is what the person will remember, so make it specific, dated, and achievable. Everything before it is context; everything after it is follow-up. A note with one priority is easier to act on than a list. The rest can wait for the next review. Make the priority measurable.
Voiskey works at the system level, so you can write the note in the drafting app you already use. Press the shortcut, speak, and the text appears at the insertion point, with no export from a separate suite and no copy-paste. That matters for feedback, because the note belongs beside the examples and the calendar, not in a separate window that you have to reconcile later. Keep the evidence table open on one side and speak the note on the other. The evidence should sit within reach. A note written away from the evidence drifts into opinion. Keep both on one screen. If a sentence sounds wrong, click into it and speak the replacement. Keep the table visible while you speak.
Use Speak-Polish-Type-Edit and keep the deliberate language. Voiskey removes filler words, stutters, false starts, self-corrections, and grammar slips, which makes a spoken draft read like a considered note. It adapts punctuation, formatting, tone, and word choice to what you are trying to do, so a warm note of appreciation and a direct correction can come from the same voice. Deliberate phrases such as I want to be direct with you should be spoken as their own sentence, because the polish pass should not soften a choice you made on purpose. Say the deliberate phrase as a separate sentence. Speak the correction in the same calm voice as the praise.
Voiskey learns the names, jargon, acronyms, and spelling preferences you use, which helps when the note refers to projects, roles, and systems that recur across reviews. Correct a name once and later notes start closer to right. It supports more than one hundred languages and translation, so a colleague who works in another language can receive feedback in the language they read most comfortably. Check translated examples and role titles by eye, because a literal rendering can change the tone of a sensitive sentence. Spell the name the way the person writes it. A short glossary of role titles helps here. Keep it beside the evidence table. A human read-back is part of the routine.
Speed gives you time for the part that matters. Voiskey supports up to 220 words per minute, about five times faster than typing, so a full note takes a few minutes to speak and a few more to check. That margin goes into rereading the examples and testing the next step for realism, which is where feedback notes usually fail. Download Voiskey for Mac and Windows, keep the evidence table beside the keyboard, and the note becomes a short, careful task instead of a document you postpone until the review is due. A few minutes of checking protects a sensitive note.
Speak the note into the drafting app you already use. Voiskey places text at the insertion point, removes filler words and false starts, and adapts tone. Keep the evidence table beside the draft, speak each point as situation, behavior, impact, and next step, then check names and dates before sharing.
Voiskey learns the names, jargon, acronyms, and spelling preferences you use, so recurring project and role names stay consistent. It cannot verify an example, so read each date and name against your table. Correct a name once and later notes start closer to right.
Voiskey supports more than one hundred languages and translation, so you can speak the note in one language and produce a version a colleague reads more comfortably. Check translated examples and role titles by eye, because a literal rendering can change the tone of a sensitive sentence.
Voiskey supports up to 220 words per minute, about five times faster than typing. A short note takes a few minutes to speak, which leaves time to reread the examples and test whether the next step is realistic. Check the dates once more.

Download Voiskey for Mac and Windows and write careful feedback notes faster.
Use it across macOS, Windows, iOS, and Android