A practical routine for dictating a clear, warm new-hire announcement

Introducing a New Team member is a small message with an outsized effect on how the group receives the person. Before writing, list the audiences who need the news and what each one must do with it. The immediate team needs the start date, the role, and the first project. Cross-functional partners need the name, the scope of the role, and the best way to make contact. External contacts need only the parts the new colleague has agreed to share. Write these three audiences on one page and mark the facts that differ between them. One announcement rarely fits all three, and a message that tries to serve everyone usually gives each reader too little of what they need.
Decide who should send the message and who should be copied. A manager usually makes the internal announcement, while a colleague may handle partner introductions with a shorter note. Confirm the new colleague's preferred name, pronouns, title, and start date directly with them, in writing, before you draft. Ask whether they want their previous employer named, and ask which project they are willing to mention first. Record these answers on the same page as the audience list. This preparation prevents the common failure where an announcement is warm in tone but wrong on a detail the new colleague cares about, which is hard to correct after the whole group has read it.
Set a send window and a reply path. Announcements land best on a normal working day when the team is likely to read messages, not late on a Friday or during a holiday stretch. Decide whether replies should go to the sender, to the new colleague, or to a separate welcome thread, and say so in the note. Give the new colleague a chance to read the draft before it goes out, even if the change is minor. Note who will update the team directory and the distribution list after the message is sent. A short checklist with owner and date for each follow-up keeps the announcement from becoming the only place the new person exists.
A reliable announcement has five parts: the news, the person, the role, the first contribution, and the welcome. Put the name and role in the first two lines so a reader who skims still learns the essential fact. Follow with two or three sentences about relevant background, chosen for this team rather than copied from a resume. Name the first project or area of responsibility, because it tells colleagues where to bring questions. Close with a concrete way to welcome the person, such as a short introductory call in their first week. Keep the whole message under two hundred words; longer announcements bury the request to say hello.
Prepare the facts on a single sheet before you speak. You need the full name, preferred name, title, team, start date, location or working arrangement, one or two background highlights, and the first assignment if it is confirmed. Add the names of anyone who interviewed the person or advocated for the hire, because those details make the welcome specific. Mark which facts are public and which should stay out of a broad distribution. Confirm spelling and pronunciation with the new colleague, especially for names that are unfamiliar to the group. This sheet becomes the source for both the spoken draft and the final review, so errors surface before the message reaches a wide audience.
Choose a structure that matches the team's culture without imitating it blindly. A formal group may expect a short professional note with the reporting line stated; a small product team may prefer a warmer message that mentions a shared interest. Either way, keep the essential facts in the same order and vary only the framing. If the team uses a standard subject pattern, follow it so the announcement is easy to find later. Ask a colleague who joined recently which details helped them most in their first week, and use that answer to decide what to include. The structure should make the message predictable for readers while leaving room for one genuine, specific sentence about the person.
Settle the subject line, the recipient list, and the timing before you write the body. A useful subject names the new colleague and the role, so the message can be found weeks later. Build the recipient list from the audience map and check it against the team directory. Decide whether the announcement goes to one group or several lists, and whether external contacts receive a different version. Schedule the send for a time when the new colleague will be available to answer early replies. These three decisions turn a draft into a plan, and they prevent the last-minute question about who was left off the message.
Dictate the announcement in a conversational voice, as if you were telling a colleague across a desk. Say the name and role first, then the background, then the first project, then the welcome. Speaking the message lets you hear whether the tone sounds like the team or like a press release. Voiskey types at the insertion point in the message field, removes filler words and false starts, and adapts punctuation and formatting to the shape of the note. Pause between the five parts so the structure survives transcription. If a sentence comes out tangled, finish the thought and fix it in the edit rather than restarting the recording, since repeated restarts produce fragments that are harder to repair.
Speak names and titles with extra care. Say the new colleague's preferred name, the team name, and the first project out loud and check how each appears in the draft. When a name is unfamiliar to the transcription, speak it slowly once, correct the spelling in the text, and repeat it in the next sentence so the correction settles. Do the same for product names and internal acronyms the team uses every day. Voiskey learns names, jargon, acronyms, and spelling preferences, which matters when you announce several hires in a quarter. Keep the fact sheet visible during the spoken run so your eyes confirm what the draft should contain.
After the spoken pass, read the message once as a new colleague would. Does the first paragraph tell them who this person is and why they matter to the team? Does the middle give a reason to reach out? Does the close make the next action obvious? Cut any sentence that only repeats the job title in different words. Check the pronouns, since a spoken draft can shift between them when the speaker is thinking aloud. Confirm the start date and the reporting line against your fact sheet. Then read it as a recipient who is scanning: the name, the role, and the welcome should still be visible after a five-second glance.
Edit the announcement for three readers at once: the team, the new colleague, and anyone who receives it by forward. For the team, verify that the role and the first project are clear. For the new colleague, verify that nothing was shared beyond what they approved, including their previous employer and their location. For the forward reader, make sure the message still makes sense without the surrounding thread, so spell out the team name instead of relying on a shorthand the group uses internally. A short accuracy pass over names, titles, dates, and links prevents the most common follow-up questions. Keep the approved version and the sent version together for reference.
Tone should reflect the team and the occasion without overpromising. A welcome message is not a performance review, so avoid claims about how the person will transform the group. Describe what they will work on and how colleagues can help. If the team is remote or spread across offices, add a practical detail such as the hours they usually keep or the channel where they answer questions. When the team includes readers in several countries, speak the announcement in the language the group uses and use translation for a second version if needed; Voiskey supports more than one hundred languages and translation. Keep both versions consistent on names and dates.
Build a short review loop before the message goes out. Send the draft to the new colleague and to one teammate who knows the audience. Ask each reviewer for one factual check and one clarity check rather than general comments. Apply the changes, then read the result aloud to catch anything that no longer flows after the edits. If the announcement includes an attachment or a link, confirm that it opens for someone outside the immediate team. Note the final version and the date so the next announcement can reuse the structure that worked. This loop adds a few minutes and removes the ambiguity that generates replies before the new person has even started.
The practical way to run this workflow is to dictate the announcement where you will send it. Download Voiskey for macOS or Windows, open the message window, press the shortcut, and speak the five parts from your fact sheet. The text lands in the field you are already using, so you can compare it with the approved facts without switching applications. Because the tool works at the system level, the same approach covers an email announcement, a chat post, and a short note to a partner. Speak one practice version, edit it, and keep the edits as a reference for the next new colleague who joins.
Treat the announcement as a reusable ritual rather than a one-off message. Save the structure, the audience list, and the five-part skeleton in a note the team can find. After each hire, record which details readers asked about, such as parking, equipment, or the first-week schedule, and add them to the checklist. Keep a separate paragraph for external partners, because their version needs less internal context. Assign an owner for the announcement and a backup, so a busy week does not delay the welcome. Over several hires, this ritual produces a message that is faster to write, more consistent, and easier for the new colleague to trust.
Review outcomes instead of relying on impressions. Note how quickly teammates respond to the welcome request and which questions arrive in the first week. If the same question appears three times, the announcement is missing a detail. Update the skeleton rather than answering individually each time. Keep the new colleague's preferred name and title current in the directory and in the saved template. When the team changes its tools or its working arrangement, revise the practical paragraph in the announcement. A short review after each hire keeps the ritual accurate as the team evolves, and it gives the next sender a better starting point. Store the revision date beside the template so nobody uses an outdated version.
Keep the speaking setup consistent across the team. Voiskey is available for macOS and Windows, so download it on the machine you use for announcements and keep the fact sheet in a shared note. When several managers send welcomes, agree on the five-part order and the tone so the messages feel like one team. A shared vocabulary of team names, project names, and acronyms helps every sender produce a draft that needs fewer corrections. Before the next hire, speak a practice announcement with the current template and time it; if it takes longer than a few minutes, simplify the skeleton. The goal is a warm, accurate note sent on the right day without a scramble.
Write the name, role, start date, first project, and welcome as five cues on a fact sheet. Open the announcement window, press the shortcut, and speak the cues in order. Voiskey types the text where you are writing and removes filler, so you can edit a clean draft and check the facts before sending.
Include the preferred name, title, team, start date, one or two relevant background points, the first project, and a concrete way to welcome the person. Confirm every name and date with the new colleague before you speak the draft, and leave out anything they have not approved for a broad audience.
Yes. Voiskey adapts punctuation, formatting, tone, and phrasing to what you are trying to do. Say whether the note is for a formal group or a small product team, and speak the version that fits. Then review the result for names and dates before the announcement goes to the wider group.
Voiskey learns names, jargon, acronyms, and spelling preferences as you correct them. Say an unusual name slowly once, fix the spelling in the draft, and the next message starts closer to correct. Still compare the final text with the fact sheet, because a learned spelling can differ from the one a new colleague prefers.

Download Voiskey for Mac and Windows and turn the facts about a new hire into a warm, accurate announcement.
Use it across macOS, Windows, iOS, and Android