Stop dictating sentences. Start dictating thoughts.
Voice tools get interesting when people stop trying to sound like software.
We have been trained by interfaces
Most software quietly teaches us how it wants us to behave. Forms want complete answers. Search boxes want the right keywords. Writing tools want sentences that are already half-finished before we begin. Even dictation often asks us to speak as if we are reading a document out loud.
But that is not how thinking usually arrives. A real thought can start with a half-sentence, pick up context halfway through, change direction, borrow a word from another language, and only become clear after we have heard ourselves say it. None of that is a failure of communication. It is communication in motion.
When we began shaping Lungoor Voice, this became one of the most important behavioural questions for us: should people learn to dictate better, or should the product learn to understand people better? We chose the second.
Speech is not messy. It is unfinished.
Calling natural speech 'messy' can be useful shorthand, but I don’t think the person speaking is the problem. Spoken thought is often simply unfinished. We use filler while we decide what comes next. We repeat a word because we are holding onto an idea. We say 'actually' because we changed our mind. We switch language because one phrase arrives faster in another vocabulary.
A useful voice product should recognise the difference between noise and intent. Removing an 'umm' is easy. Removing the sentence that contained the point is not. Reformatting a rambled update is useful. Making the speaker sound like a completely different person is not.
That line matters. The job is not to make everyone sound polished in exactly the same way. The job is to reduce the friction between what someone meant and what they need to send, save or act on.
Good voice software should not reward people for becoming better dictation machines. It should reward them for being human.
The clean draft is the first moment of trust
The first output after someone speaks matters more than almost any feature list. If I talk for twenty seconds and the product gives me something I recognise as mine, just clearer, I begin to trust it. If I have to repair the tone, restore missing context, or undo overconfident rewriting, the product has created a second job.
This is why I like the idea of a clean draft rather than a perfect draft. 'Perfect' suggests the system has the final word. A clean draft leaves the user in charge. It should remove obvious friction, give the thought structure, and still feel like something the person could have written on a good day.
That is also why selection and styles matter. Sometimes the thought is right but the room changes. A quick internal update, a client email, and a formal note can carry the same meaning while needing very different delivery. The user should be able to change that delivery without rebuilding the thought from scratch.
Voice-first does not mean voice-only
There is another behaviour we have to respect: not everyone wants to speak all the time. Sometimes you are in a shared room. Sometimes the thought is easier to type. Sometimes you already have a paragraph and only want help reshaping it.
For us, voice-first means voice can be the fastest route into the work when it helps. It does not mean forcing a microphone into every moment. The same system should support a rough spoken thought, selected text, a style change, or a simple command such as 'make this shorter' or 'turn this into bullets.'
The important part is continuity. You should not have to leave the place where the work is happening, explain yourself to another tool, copy the result back, and then recover your context.
The product test I keep coming back to
Behavioural design is often about tiny moments rather than dramatic features. Does the user hesitate before pressing the shortcut? Do they trust the output enough to send it? Do they understand what changed? Do they feel more capable after using the tool, or more dependent on an opaque system?
The best version of Lungoor, for me, is not one where people admire the AI. It is one where they barely notice the machinery. They remember the thought they had, not the process required to format it.
Try this yourself: say the thought the way it arrives, pauses, corrections and all. Then compare the raw version with the clean draft. The goal is not to sound more like Lungoor. The goal is for Lungoor to sound more like you.
Select a rough draft, choose a style, and compare what changed, and what stayed yours.
Try Lungoor Voice