Talk, Don't Type: Why Your Best Prompts Are Spoken

3 days ago

5 min read

In a recent article, I made the case that the most useful prompts now run to several hundred lines and read more like a briefing for a new hire than a quick question. The first response I usually hear is a practical one: who has the time to write all of that? The instinct behind the question is understandable. When a busy executive sits down at the keyboard, the prompt tends to shrink to whatever can be typed before the next meeting, and the model is left to guess at everything that was left out.

The answer to that problem is surprisingly simple. Stop typing your prompts and start speaking them. Nearly every major AI tool now accepts voice input, and the habit of talking through a request for two or three minutes produces the kind of rich, detailed direction that most people would never take the time to write. For many leaders, it is the easiest way to get the benefits of the long prompt without the burden of writing one.

Why Speaking Makes Better Prompts

Most people speak about three times faster than they can type on a phone, roughly 150 words per minute compared with 40, so the same few minutes of dictation yields far more material than the same time spent typing (Ruan et al., 2018). Speech recognition has improved considerably since that study, and today’s tools turn spoken words into clean text with remarkably few errors.

The second advantage matters more. People explain things differently when they talk. Where a typed prompt tends to state the task and stop, a spoken one wanders in useful directions, picking up the background, the history, the concerns, and the small details that an experienced leader carries in their head but rarely writes down. Ask an executive to type a request for a board update and you may get one line. Ask the same person to talk it through and you will hear who sits on the board, which member always presses on cash flow, what went poorly last quarter, and what tone the CEO wants to strike. That second version is exactly the context a model needs to do excellent work.

The major AI developers say the same thing in their own guidance. Clear, detailed direction that explains the audience, the purpose, and what a good result looks like produces far better output than a short instruction (Anthropic, n.d.; OpenAI, n.d.). Speaking is simply the fastest way most people have of giving that detail.

There is also a third, quieter benefit: many leaders think best out loud. Talking a problem through to a model often clarifies the request in the speaker's own mind, and the model can then act on thinking that might never have made it onto the page.

How to Give a Spoken Briefing

Start by downloading the mobile app for whichever generative AI tool you already use, whether that is ChatGPT, Claude, Gemini, or something else. These tools offer their own microphone buttons on desktop and mobile alike, but your phone’s built-in dictation, which you can reach through the microphone icon on the keyboard, tends to produce the most reliable transcription and is worth using instead. Dictate on your phone, then pick up the conversation on your desktop when it is time to review the work.

Beyond adjusting to moving between your phone and your desktop, the hardest part is breaking the habit of short requests. A little structure helps, and the easiest approach is to talk to the model the way you would brief a capable new member of your team.

A good spoken briefing usually covers five things:

Who is involved. Tell the model what role to play, describe the audience and what they care about most, and fill in the background on your organization that a capable outsider would lack.
Why it matters. Explain the task and the decision or outcome it supports, since a model that understands the purpose makes better judgment calls than one following bare instructions.
What good looks like. Describe the voice, length, and format you want, and walk through a past example you were pleased with.
What to avoid, and why. Name the mistakes, sensitive topics, and unusual situations that have caused problems before, and explain the reasoning behind each so the model can apply it to cases you did not anticipate.
What you are unsure about. Acknowledge where your own knowledge runs out, ask the model to approach the work as a seasoned expert, and invite it to raise the risks, assumptions, and questions you may have overlooked.

Then close with one simple instruction: "Before you start, ask me any questions you need answered." This gives the model a chance to fill the gaps that even a thorough spoken briefing leaves behind.

Do not worry about speaking in polished sentences. Today's models are very good at finding the meaning in natural, rambling speech, including the false starts and the "actually, let me back up" moments. If a request is complex, you can even ask the model to first turn your spoken notes into a clean, organized brief, review that brief, and then have it begin the work. Leaders who find a briefing worth keeping can save it and reuse it, which over time builds the kind of prompt library I described in the earlier article.

A Few Sensible Cautions

Speaking a prompt calls for the same judgment as typing one, along with a few added habits. Be mindful of where you are. A detailed briefing about a client or a personnel matter should not be delivered in an airport lounge or a crowded coffee shop, where the people nearby can hear every word. Take the same care with what you share with the tool itself, since a spoken prompt reaches the model just as a typed one does. It also pays to glance at the transcript before you send it, because names, figures, and industry terms are where dictation most often slips.

Finally, remember that more words are only valuable when they carry useful information. The aim is to pass along the context that lives in your head and would otherwise never reach the model, which usually takes a few focused minutes rather than a long monologue. In TokenOps terms, a well-structured three-minute briefing that gets the work right the first time costs far less than a vague one-line request followed by four rounds of correction.

The Leadership Habit Behind It

Speaking is the most natural way most of us explain what we want and why, and dictating a prompt turns what would be a writing chore into a conversation. Try it once this week. Before your next call or on a walk between meetings, open your AI tool of choice, tap the microphone on your keyboard, and brief it the way you would brief a trusted colleague. The difference in what comes back is likely to change how you work with AI from then on.

References

Anthropic. (n.d.). Prompting best practices. Claude Platform Docs. https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices

OpenAI. (n.d.). Best practices for prompt engineering with the OpenAI API. OpenAI Help Center. https://help.openai.com/en/articles/6654000-best-practices-for-prompt-engineering-with-the-openai-api

Ruan, S., Wobbrock, J. O., Liou, K., Ng, A., & Landay, J. A. (2018). Comparing speech and keyboard text entry for short messages in two languages on touchscreen phones. Proceedings of the ACM on Interactive, Mobile, Wearable and Ubiquitous Technologies, 1(4), Article 159. https://doi.org/10.1145/3161187