Insight February 24, 2025 7 min read

Try saying your next AI prompt out loud.

Speaking can make it easier to include your thoughts and context. Review the resulting text before sending it to ChatGPT, Claude, Gemini or another tool.

You’re having conversations now, not writing documents

AI chat lets you explain your question in full sentences. Relevant context, nuance and specific goals can help the tool answer the question you meant to ask.

When you use ChatGPT, Claude, or Gemini, you’re not filling in a form. You’re talking to an intelligence that gets better the more you give it. Tell it your constraints, your preferences, your background, your goal — and it responds with something tailored and useful. Give it a terse, stripped-down command, and you get a generic answer you could have found on the first page of Google.

The entire “prompt engineering” industry exists because people discovered this asymmetry: more context in, better answers out. But there’s a problem. The tool most people use to input their prompts — a keyboard — is actively working against them.

Typing makes you say less than you mean

Watch what happens when someone types a prompt into ChatGPT. They have a rich, complex question in their head. Maybe they want help planning a trip, debugging a piece of code, or drafting an email to a difficult client. The thought in their head is full of context — constraints, background, nuance, preferences.

Then they start typing. And something happens. The prompt shrinks. The context disappears. They strip it down to the minimum because typing is slow, effortful, and every additional sentence costs time and energy. The keyboard imposes a tax on every word, and your brain unconsciously pays that tax by saying less.

The result looks something like this:

“Copenhagen trip ideas”

That’s what they typed. Here’s what they were actually thinking:

“I’m planning a trip to Copenhagen in June with my family. We have two kids under 10 who get bored easily. We love food — especially local restaurants, not tourist places. My wife is into architecture and design. We’re staying for five days and we don’t want to exhaust ourselves with a packed schedule. What would you recommend?”

The first can produce a generic list. The second gives the tool details about the children, interests and pace it can use when suggesting an itinerary.

Typing suppresses context. Not because you don’t have the context. Because typing makes it too costly to include.

Speaking unlocks the full prompt

Now imagine the same person speaks their prompt instead of typing it. Something different happens. They don’t strip anything out. They don’t self-edit for brevity. They just … talk.

“So we’re going to Copenhagen in June, the whole family, two kids — they’re seven and four. We really love food, like actual local places, not the tourist stuff on Nyhavn. My wife is super into architecture and Scandinavian design. We have five days and we don’t want to overdo it — what would you suggest?”

That’s the same person with the same question. The difference is the input method. When you speak, you naturally elaborate. You add asides. You provide background. You explain the why behind the question, not just the question itself. This isn’t a decision you make consciously. It’s how speech works. Talking is effortless in a way that typing simply is not, and your brain takes advantage of that effortlessness by giving more.

Try both methods on your own prompts and see which makes it easier to include useful context.

AI models are context machines

This matters enormously because of how large language models actually work. ChatGPT, Claude, Gemini — they don’t think. They predict. They generate the most probable continuation of the text you gave them. And the more specific your input, the more specific and useful their output.

This is not a minor effect. The difference between a vague prompt and a detailed one can be the difference between a useless response and a genuinely brilliant one. AI researchers and power users know this. It’s why the best AI prompts read almost like conversations — full of context, constraints, examples, and clarifications.

Here’s the irony: the way most people naturally speak to another human is almost exactly the prompt structure that AI models respond best to. You give background. You explain constraints. You describe what you’ve already tried. You say what good looks like. You do this automatically when you talk. You stop doing it when you type.

Voice input doesn’t just give you more words. It gives you the right kind of words — the kind that AI models use to generate better, more targeted, more useful responses.

The flow state problem

There’s another dimension to this beyond word count. When you type a complex prompt, you’re doing two things simultaneously: formulating your thought and mechanically transcribing it. These processes compete for the same cognitive resources.

While drafting a prompt about marketing strategy, you might stop to correct a typo and forget a constraint you meant to add.

This happens constantly. Every typo, every autocorrect fight, every moment of hunting for a special character — these are micro-interruptions that fragment the thought you’re building. The prompt you submit is not the prompt you meant to write. It’s the prompt that survived the obstacle course of typing.

Speaking lets you draft in one pass and edit afterwards. Review the transcript before sending, especially names, numbers and specialist terms.

A useful prompt describes what you need. Choose the input method that helps you do that.

The Nordic language tax

If you write in multiple languages, you may find voice input convenient when switching languages or using a small keyboard.

Consider the Danish word “købsaftale.” How you type ø on iPhone depends on your selected keyboard. Some keyboards offer variants when you hold a key, while the Danish keyboard has dedicated characters.

Characters such as ø, æ, å, ä and ö, along with autocorrect settings, can affect typing if the keyboard does not match your language.

Try saying “købsaftale” and check how it comes out. Choose the language you are speaking and review the text before sending.

What this looks like in practice

Here are some examples of adding useful context to a prompt you speak:

  • Brainstorming. Instead of typing “marketing ideas for SaaS,” you say: “I’m running a B2B SaaS product in the Nordics, our average deal size is around 30,000 kroner, our current pipeline is mostly from LinkedIn but we’re seeing diminishing returns — what are some unconventional channels we should test?”
  • Writing assistance. Instead of “write a professional email,” you say: “I need to reply to a client who’s upset about a delayed delivery. I want to be apologetic but not groveling, and I need to propose a concrete solution — we can offer a 15% discount or expedited shipping on their next order.”
  • Code debugging. Instead of pasting an error and typing “fix this,” you say: “This function is supposed to filter an array of user objects by subscription status, but it’s returning an empty array even when I know there are active subscriptions in the data. I think the issue might be in how I’m comparing the date fields.”
  • Research. Instead of “explain quantum computing,” you say: “I’m a software developer with no physics background. Explain quantum computing in a way that focuses on the practical implications for cryptography — I need to understand whether my company should start thinking about post-quantum encryption.”

The useful difference in each example is the added context. You can provide that with either input method.

The right tool for the AI era

The keyboard was designed for an era when text input meant writing documents — letters, memos, reports. Precision mattered. Speed didn’t. And the person you were writing to was human, capable of inferring context you left out.

In an AI conversation you can start with a short prompt or give more detail upfront. Choose based on what the tool needs to know.

The keyboard is an interface from a different era, optimized for a different kind of communication. Voice is the natural interface for the conversational, context-rich, high-frequency interactions that define AI usage.

This is why Aivo can insert dictated text into compatible fields on iPhone and Mac. Use the Aivo keyboard on iPhone or the app shortcut on Mac. Select your language, speak your prompt and review the result. Transcription can vary.

You don’t need to change which AI you use. You don’t need to learn prompt engineering frameworks or memorize templates. You just need to remove the bottleneck between your thought and the AI’s input field. Speak the thought. Let the AI hear all of it — the context, the constraints, the nuance, the background that you would have cut if you had to type it.

The bottleneck was never the AI

People spend enormous energy trying to get better answers from AI. They read prompt engineering guides. They experiment with different phrasings. They iterate through multiple attempts to coax the model into understanding what they want.

Most of the time, the AI understood fine. The problem was upstream. The prompt was impoverished — not because the person didn’t know what to ask, but because typing compressed a rich thought into a sparse command. The keyboard ate the context. The AI never saw it.

Try saying a prompt out loud and compare it with the typed version. Check which draft better expresses the task.

Speak your draft, review the text and send it when it is ready.

Talk to your AI, not type to it

Try Aivo free in compatible text fields on iPhone and Mac.