Dictating Clear Instructions in Chat

A spoken method for step-by-step chat instructions that people can follow alone.

Voiskey Voiskey Team
WhatsApp DictationMessaging WorkflowDictating Clear Instructions

Frame the Task Before You Speak

Dictating Clear Instructions in chat starts with deciding what the reader must do first. Before you press the shortcut, write three items on a note: the goal, the starting point, and the condition that means the task is done. A goal such as set up the new till is too broad, while a goal such as connect the card reader to the counter tablet names a result you can see. Say the goal as an outcome, not as a topic. Then say where the reader starts, because an instruction that begins in the middle forces them to guess. The note takes a minute and prevents the most common failure: a confident message that leaves someone stuck at step one.

Name the reader and the place before the steps. An instruction for a new staff member differs from one for a colleague who has done the task ten times. Say who the instruction is for, and where they will perform it, such as at the front desk or on the loading dock. When you dictate, put that context in the opening line. A reader who knows the instruction was written for them pays closer attention and asks fewer clarifying questions. Check the draft for assumptions about tools, access, or background knowledge. Any assumption you cannot justify belongs in the message as an explicit prerequisite. Keep the prerequisite list to two items or fewer.

Write the first line as the action, not as a greeting. Chat threads are read on phones, and the first line decides whether the rest is read at all. A line such as three steps to reset the printer tells the reader what to expect. When you dictate, say the action line first, then the steps. Avoid openings that warm up slowly, such as I wanted to ask you to. Warmth belongs in the closing or in a separate message. A direct first line is not rude; it respects the reader's time and makes the instruction easier to find when they scroll back later. Save the greeting for people you know well.

Set the stopping point in advance. Every instruction needs a clear end, or the reader will keep going and change something you did not intend. Say what to do when the task is complete, such as reply with a photo of the screen or leave the device on the counter. If something goes wrong, say what to do first and who to contact second. When you dictate, speak these two branches as separate sentences. Then read the draft and check that a reader can tell the difference between done and not done. An instruction without an end state invites overwork and quiet errors. A single sentence for each branch is enough.

Sequence Steps in Spoken Order

Spoken instructions fail when the order is wrong. Before you speak, write the steps as a numbered list on paper, then read the list aloud once to hear where it jumps. Each step should begin with a verb and name one action. If a step contains the word and, check whether it is really two steps. When you dictate, ask for a numbered list and speak the numbers in order. Then compare the draft with your paper list. A missing number is easier to spot than a missing clause, which is why the numbered form is worth the extra request. Keep the list to seven steps or fewer.

Group the steps by place rather than by topic. If three actions happen at the same screen, keep them together, even if one is about a setting and another about a label. Readers move through space, and an instruction that sends them across the room and back wastes time. When you dictate, say the place before the group of steps. For example, say at the counter tablet, then list the three actions there. Check the draft for a step that returns to a place you already left. A place-based order is easier to follow and easier to check when something goes wrong. It also shortens the walk for a reader on their feet.

Put warnings before the action they affect, not after it. A warning that arrives after the step has already been taken is useless. When you dictate, say the caution first, then the step. For a device reset, say that the settings will clear, then say which button to hold. If the warning is long, move it into a short note above the steps and keep a one-line version in place. Check the draft to confirm that no caution appears after the action it was meant to prevent. Order is the difference between a warning and an apology. Mark the warning with a single word such as caution.

Add a check after each step that can fail silently. A step that produces no visible result, such as saving a setting, needs a confirmation: the screen changes, a light turns green, or a short message appears. When you dictate, ask for the check in the same step rather than as a separate line. Then read the draft and confirm that the reader knows what success looks like. Steps without checks produce instructions that seem complete but leave the reader unsure. A visible result is the cheapest form of quality control in a written procedure. Ask the reader to report the result before moving on.

Catch Ambiguity During Review

Review the draft for the words that make a step ambiguous. Pronouns are the main offenders: it, this, and that can point to two different objects in the same sentence. When you dictate, name the object instead of using a pronoun, and check the draft for any pronoun that has more than one candidate. The same applies to words such as normally and usually, which describe a habit rather than an instruction. Replace them with the exact case, such as when the light is red. A precise noun costs one extra word and removes the question that would have stopped the task. Read each step as if you had never seen the device.

Check every quantity and every label. A step that says press the third button is clear only if the buttons are counted from the same side the reader sees. When you dictate, say the side and the label together, such as the third button from the left, marked start. Check the draft for a number without a reference point. The same rule applies to time: say after two minutes rather than after a while. Quantities and labels are where a reader slows down, and a slow reader is a reader who may give up. Spell out units in full when the number matters.

Look for the step that assumes a previous step succeeded. A sequence such as open the menu, choose settings, then restart the device assumes that the menu opened and the setting exists. When you dictate, add a fallback for the step most likely to fail, such as if the menu does not open, close the app and try again. Then check that the fallback returns the reader to a known point rather than to the beginning. A good instruction anticipates one failure per procedure, not every possible failure, and it tells the reader where to resume. Two fallbacks are usually enough for a short procedure.

Ask a reviewer to mark the first place they would hesitate. Do not ask whether the instructions are clear, because almost everyone says yes. Ask them to read silently and point at the sentence where they would stop. Mark that sentence, then rewrite only that sentence and ask again. Repeat until the reviewer reaches the end without stopping. This method finds ambiguity faster than a general review, and it keeps you from rewriting parts that already work. The hesitation point is the exact place where the reader's context differs from yours. Fix one hesitation at a time so the test stays honest.

Test with the Person Doing the Task

Test the instructions with someone who actually performs the task, not with someone who wrote them. Give them the message with Voiskey's draft in the chat field, and ask them to follow it without asking you questions. Watch where they pause, what they reread, and which step they skip. Write those moments down as you observe them, not afterward. When they finish, ask them to describe the result in one sentence. If their description differs from the goal you wrote in the first step, the instruction needs work. A live test reveals more than a careful reread by the author.

Run the test twice with two different readers. One reader may know the device and fill gaps from experience, while a new reader will stop at the first missing detail. Choose one experienced and one new person when you can. Compare their hesitation points: the place where both stop is a real gap, and the place where only the new reader stops is a missing prerequisite. Fix the shared gap first, then decide whether the prerequisite belongs in the message or in a short training note. Two readers turn a vague impression into a ranked list of fixes. Keep the notes from both tests side by side.

Time the task without turning the test into a race. Record the start and end so you know whether the instruction is practical, but do not tell the reader that speed is being measured. A reader who feels timed will skip checks and hide confusion. After the test, ask one question about the part that took longest, and listen for the word because. The answer usually names the missing detail. If the reader needed a tool that was not mentioned, add the tool to the prerequisite line. A practical instruction fits the tools and the space the reader actually has. Add the time to your notes for the next revision.

Close the test with a short debrief and a decision. Ask the reader which step they would rewrite, and compare their answer with your own list. If the same step appears on both lists, fix it now. If the reader names a step you thought was clear, ask them to read it aloud and notice where their voice hesitates. Then revise the message in place, so the chat thread holds the improved version rather than a separate document. Record the date and the reader's role, and repeat the test when the procedure or the tools change. One revision is usually enough for a short procedure.

Standardize Repeated Instructions

Once an instruction works, turn it into a standard rather than rewriting it each time. Save the approved message with a short name, such as reset the card reader or close the counter. Voiskey places the draft at the insertion point, so the saved text can go straight into the thread where the reader expects it. Change only the fields that vary, such as a device number or a shift time. Keep the standard in one place that the whole team can reach, and note the date it was approved. A standard that nobody can find is not a standard; it is a personal note.

Write a short index for the standards so people can choose the right one. The index lists the task name, the reader it is written for, and the last review date. Group the entries by place, such as front desk, stockroom, and loading dock, because that is how staff search for them. When you dictate a new instruction, add its name to the index in the same session. Review the index every quarter and remove entries for tasks that no longer exist. A short index is the difference between a library people use and a folder people avoid. Keep the index to one page.

Train new people with the standard, not with a live explanation. Ask them to follow the saved instruction on their first day while you watch, and mark the step where they hesitate. If the standard is good, the hesitation will be about the device rather than the text. Update the standard when a device changes, and tell the team which version is current. When you dictate an update, say the version date at the top so old copies are easy to identify. Training from the written standard keeps the instruction honest, because every gap shows up in the first hour. It also gives you a record of what was taught.

Make the habit permanent with a download and a review date. Download Voiskey for the computers the team uses, set the shortcut where hands already rest, and keep the standards and the index in one shared place. Put a review on the calendar every quarter: read the three most-used instructions, follow them once, and fix anything that has drifted. Ask one person who did not write them to do the check. A standard that is reviewed stays useful, and a standard that is never reviewed quietly becomes wrong. The goal is instructions that a busy colleague can follow at the worst possible moment.

FAQ s

Press the shortcut in the message field, speak the steps in order, and ask for a numbered list. Voiskey adapts punctuation and formatting to the request, so the draft arrives as a readable list at the insertion point. You still check the order and the details before sending.

Speak each step with the object named, and ask for a numbered list. Voiskey removes filler words, stutters, false starts, and self-corrections while keeping your wording, so the draft is easier to scan. You still read each step once for pronouns that could point to two objects.

Voiskey learns names, jargon, acronyms, and spelling preferences. Say the term once during a practice instruction and correct the draft if it comes out wrong. The correction carries into later messages, which keeps repeated procedures consistent across the people who send them.

You speak the intent, Voiskey polishes wording, punctuation, and formatting, the text lands at the insertion point, and you edit only the details that matter. For instructions, check the step order, the warnings, and the end state before the reader receives them.

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 and send instructions people can follow.

Use it across macOS, Windows, iOS, and Android

Use it across