Dictating Team Updates from the Gmail Compose Window

Turn a weekly update into a clear, skimmable note.

Voiskey Voiskey Team
Gmail DictationChrome ExtensionDictating Team Updates

Gather Facts Before You Open Compose

Dictating Team Updates from the compose window works only when the facts are already gathered. Open a note first and write the three things a reader needs: what changed, what it means for them, and what happens next. Pull the dates, owners, and numbers from their source rather than from memory. A weekly update built from memory drifts toward generalities, and generalities are what make people stop reading. Spend five minutes on the note, then open the compose window. The order matters, because a blank window invites you to start talking before you know what you need to say. Keep the note short.

List the sources beside each fact so you can check them later without hunting. A short reference such as the project tracker or the last status note is enough. If two sources disagree, resolve the conflict before you dictate; a dictated update that contains a contradiction is harder to repair than a written one, because the flow of the paragraph makes the error look intentional. Mark anything you cannot verify and decide whether to leave it out. An update with fewer, verified facts is more useful than a longer one with soft claims. Write the reference beside the fact rather than in a separate list.

Decide who the update is for and what they already know. A team that lived through the week needs different detail from a manager who saw only the summary. Write the audience at the top of the note and choose the three facts that matter most to them. If the audience is mixed, lead with the item that affects the most people and put the rest in order of impact. The same facts can support a short update or a long one; the audience decides which. If the audience is unclear, ask one reader what they need before you write.

Set a time limit for the note and for the dictation. Ten minutes of preparation and five minutes of speaking is enough for most weekly updates. A time limit prevents the update from becoming a writing project and keeps the focus on decisions rather than prose. If the facts are not ready within the limit, send a short note saying when the full update will arrive. A reliable short update beats a late comprehensive one, and the team learns to trust the rhythm. A dependable rhythm is easier to plan around than an occasional long update. Keep the rhythm predictable.

Structure the Update as Bullets

Structure the update before you speak the first sentence. Choose a simple shape: a one-line summary, three to five bullets, and a closing line with owners and dates. Say the shape out loud once, then dictate into it. A spoken update without a shape tends to arrive as one long paragraph, and a long paragraph hides the decisions inside it. The shape also makes the voice easier to control, because each bullet is a short unit you can finish before moving to the next. Write the shape at the top of the note so the dictation has a visible frame.

Keep each bullet to one idea and one owner. If a bullet needs two owners, it is two bullets. If a bullet needs a date, put the date in the same sentence rather than at the end of the update. Voiskey adapts punctuation and formatting, so spoken list markers can become ordered text, but the discipline of one idea per bullet is yours. Read each bullet after you speak it and ask whether a skimmer could act on it without reading the rest of the message. A bullet that needs a second sentence is usually two bullets. Split it in two.

Put the most important bullet first. Readers skim from the top, and many stop after the first two items. The first bullet should answer the question the audience is most likely to ask, even if the work behind it finished last. Order by impact rather than by chronology. A chronological update reads like a diary, while an impact-ordered update reads like a decision brief. The same facts, arranged differently, produce very different responses. If the first bullet feels weak, the real headline is probably lower down and needs to move up. Move the headline up before you dictate the rest.

Close with a short block for owners and dates. List who is doing what and when the next checkpoint falls. This block is easy to scan and easy to quote in a meeting. Keep it separate from the bullets so it does not get buried. If an owner is missing, write unassigned rather than leaving the item blank; a visible gap invites a decision, while a blank line hides one. A clean closing block turns the update into something the team can actually track. Keep the block in the same place every week so readers know where to look. Keep it fixed.

Speak for the Skimmer

Assume the reader will skim. Put the conclusion in the first line and the supporting detail after it. Use short sentences and concrete nouns. Name the system, the team, and the date rather than saying the usual people or sometime next week. A skimmer should be able to read the first line of each bullet and still understand the state of the work. If that is not true, the bullet is doing too much and should be split. Write the first line of each bullet as a complete claim rather than a topic label. Then read all first lines on their own.

Speak in complete thoughts rather than fragments. Voice input handles full sentences better than a string of disconnected phrases, and full sentences are easier to edit later. If you catch yourself starting a thought and abandoning it, stop, take a breath, and say the thought again from the beginning. Voiskey removes false starts, but a clean second attempt is still faster than a paragraph that needs reconstruction. The edit step is for judgment, not for reassembling broken syntax. A second attempt costs a few seconds and saves the edit pass a difficult repair. Keep the wording plain, direct, and short.

Avoid jargon that only the speaker understands. Every team has shorthand, and shorthand is useful until it reaches someone outside the group. Write the expansion the first time a term appears, then use the short form. If the audience is mixed, keep the expansion in every bullet. A skimmer who has to decode an acronym will skip the rest of the line. Plain language is not a downgrade; it is what makes the update usable by more people. Ask a colleague outside the team to read one update and mark anything they had to decode. Fix anything they had to decode.

Read the update once at skimming speed before you send it. Cover everything except the first line of each bullet and see whether the message still makes sense. If it does, the structure is working. If it does not, move the key fact into the first line and push the detail down. This test takes under a minute and catches the most common failure of dictated updates: important information buried in the middle of a long sentence. If the covered version fails, move the one fact that matters into the first line and try again. Then read it again at speed.

Proof Numbers and Owners

Numbers and owners are where dictated updates fail most often. Read every number against its source before you send. Check the unit, the date, and the rounding. A spoken number can arrive as a different number when the phrasing is ambiguous, so say amounts in full and pause between groups of digits. Mark each number in the draft and tick it off against the note. This is a mechanical check, and mechanical checks are the ones that catch errors when you are in a hurry. Keep the source note open beside the draft during the whole check. Do it before you edit.

Check every name against the note as well. A misheard name in an update is more damaging than a misheard adjective, because it sends credit or blame to the wrong person. Use the form the person uses at work, and keep it consistent across the update. Voiskey learns names, jargon, acronyms, and spelling preferences, so a correction you make once helps future updates. Fix the name in the field immediately rather than after the paragraph is finished. Add any corrected name to your vocabulary note so the next update starts from the right form. Keep that note open during the check.

Confirm that every action has an owner and every owner has an action. Read the closing block and the bullets together, because ownership often drifts between them. If a bullet describes work but no one is named, add unassigned and raise it in the next team conversation. An update that lists work without owners looks complete and is not. The check takes a minute and prevents the most common follow-up question: who is doing this? Write unassigned in capitals so it is impossible to miss during the final read. Read the closing block aloud once more to catch it.

Run the proof pass in a fixed order: numbers, names, dates, owners. A fixed order prevents you from checking the first item twice and skipping the last. Read the update once in that order, then read it once for sense. Do not merge the two passes, because the mechanical check and the comprehension check use different attention. When both passes are clean, send the update. The routine is short enough to repeat every week, which is what makes it reliable. When the order becomes automatic, the check takes less time than reading the update once. Time the pass once to confirm it.

Reuse the Format Next Week

Save the shape of a good update so next week starts from a template rather than a blank window. Keep the one-line summary, the bullet block, and the owner-and-date closing in a note you can copy. Do not copy last week's content; copy the structure. A template removes the small decisions about format and lets you spend the time on facts. It also keeps the update recognizable from week to week, which helps readers find what they need without rereading the whole message. A template that is easy to copy is more likely to be used on a busy Monday.

Keep a short list of the terms your team uses and the forms of names you have verified. Add to it whenever a correction appears. Over a month, the list becomes a small style guide that makes dictated updates faster and more consistent. Share it with anyone who writes the update in your place, so the voice does not change when the author does. A shared list is more useful than a personal habit, because it survives holidays and handoffs. A shared list also gives a new writer a starting point that is better than a blank page. Share it widely.

If you write the update on more than one machine, download Voiskey on each computer you use and keep the shortcut and the template in the same place. A different setup on a second machine is enough to break the weekly rhythm. Install it, run one practice update, and confirm that the shape survives the move. Then add the machine to your Monday routine. Consistency across machines is what makes the format feel like a habit rather than a project. Write the location of the template in the same note as the shortcut so both are easy to find. Write it down.

Review the format quarterly and change one thing at a time. If readers consistently ask the same question after the update, the format is missing a field. Add it, use it for a month, and check whether the question stops. If a section is never read, remove it. The goal is a format that earns its space, not one that grows because it is easy to add a heading. A lean format is easier to dictate and easier to skim. Ask one reader each quarter which section they use most and which they skip. Change only what the answers support.

FAQ s

One shortcut starts dictation and the text lands at the insertion point, so you speak the update in the field where it will be sent. Voiskey removes filler words and stutters and adapts formatting, which keeps the first draft close to the final note.

Voiskey adapts punctuation and formatting to what you are trying to do, so you can speak updates as ordered points and review the structure in the edit step. Keep each point to one idea, then confirm the breaks before sending from the compose window.

Check names, dates, numbers, and owners in the edit step, because the app types what you say and does not verify facts. Read the update once as a skimmer would, then confirm that every bullet has an owner and a next step.

Voiskey learns names, jargon, acronyms, and spelling preferences, so repeated terms become reliable after correction. Numbers still need a human check in the edit step. Keep the same term and format each week, and fix errors in the field as they appear.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows to dictate a skimmable team update every week.

Use it across macOS, Windows, iOS, and Android

Use it across