Zurück zum Blog

How to Dictate Release Notes From Verified Changes

Explain a software update by voice, then check the shipped behavior, affected users, and limitations against the release.

18. Nov. 2026Whisper One TeamWhisper One Team

You helped ship an update and can explain what changed, but the release notes are still an empty file. Start by saying what a user will notice. Then compare that explanation with the version that is actually going out. A feature you discussed last week might not be in this release.

This workflow uses a fictional room booking app. It assumes you have access to an approved list of shipped changes and someone who can confirm the behavior. Voice input helps write the explanation; it does not inspect your code or establish which changes reached production.

Pick the changes a user needs to know

Read the release list and group it by visible behavior. A fix for an unclear error message belongs in the notes if it changes how someone recovers. A dependency update might need a separate technical record rather than a paragraph in the public announcement. Follow your project's release policy for changes that require specific disclosure.

For each public item, find a concrete trigger. In the booking example, the trigger could be trying to reserve a room that someone else booked moments earlier. The updated behavior might keep the selected date visible and ask the person to choose another time. That is easier to explain than an internal ticket title such as “Handle booking conflicts.”

Speak the before and after in everyday words

Dictate one item into a draft, with the trigger, the result, and what the user can do next. For the fictional conflict fix:

When a room becomes unavailable before you confirm, the booking page keeps your selected date visible and asks you to choose another time.

Read it beside the shipped behavior. Does the date really remain selected, or is it only displayed in the message? Are all booking paths covered, or just the web form? Keep the statement as narrow as the evidence supports. If you have not confirmed one detail, mark it as a question for the release owner rather than smoothing it into a claim.

For a new option, add where to find it and whether it needs to be enabled. A reader should not have to search through settings to discover that the feature is still limited to a test group.

Check access and limits before polishing the prose

Verify the version, platform, rollout group, and any setup needed. If the change is available only in the desktop app, say so. If it will roll out gradually, distinguish the start of the rollout from access for everyone. Check whether the release owner has approved the wording before giving a date or promising that a bug is resolved.

Look for words such as “always,” “all,” and “instant.” They can make a narrow improvement sound broader than it is. You can usually replace them with the specific case you tested. Keep a known limitation near the feature it qualifies, so someone skimming the notes still sees it.

Copy version numbers, setting labels, and documentation links from their source after speaking the body. A spelling mistake in prose is distracting; an incorrect version or link can send someone to the wrong instructions.

Read the notes from the update page

Move the edited text into your release draft and read the headings alone. Can a person tell what matters to them? Put the important change first, then keep smaller fixes short. Check the documentation links and confirm that a screenshot, if you use one, shows the version being released.

Ask someone who did not write the code to explain the change back to you. If they hear a promise you cannot verify, adjust the note before publishing. To practice, download Whisper One for a supported Apple Silicon Mac and follow the first dictation guide. For a useful record of how the team chose the behavior, see the project decision log guide.