Everything I Don't Have to Click
The biggest advantage of talking to AI isn’t how fast I can talk. It’s everything I don’t have to click. I don’t have to open the right app, find a record, click into the right box, type the update, save it, then copy the information somewhere else. I can explain what needs to happen and review the result. As of this November, I haven’t typed an email in roughly two months. That doesn’t mean I stopped writing them. I still decide what they need to say. I talk through the situation, read the draft, make changes and approve the send. Our company texting works this way too. I explain what I want to communicate, review the message and decide when it should go. The words still need to sound like me. The customer still needs a useful answer. I’m just not typing that answer into a box myself. Talking is only part of it There is a difference in how quickly we can get words out. A large typing study found that volunteers averaged about 52 words per minute copying sentences on a keyboard. A speech-comprehension study described approximately 130 to 190 words per minute as an average speaking range. Those aren’t equivalent tests. One measured typing; the other tested comprehension at different speech rates. They involved different people and tasks, and neither measured the time it takes to run a business workflow. They don’t prove that talking makes me three times more productive. For me, talking makes it easier to get the messy version out. I can explain the situation, change my mind halfway through and say, “Actually, not that. Do this instead.” I don’t have to turn every thought into a perfectly structured request before I start. But if the result is just a paragraph I have to copy and paste into another app, I’ve only changed the first step. The more useful change is connecting that conversation to the tools where the work happens. The work can actually move I use this across four websites. I might notice a broken layout, want to change some wording or have an idea for an article. I explain the change. It gets prepared for review and tested where appropriate. I decide what should go live. I’m still responsible for what the site says and whether the change is right. I just don’t have to find every file or navigate every editing screen myself. The same idea applies to our crew and vehicle board. I can ask to move a driver, change an assignment or mark a van as back from the shop. These are updates to our operating tools, not just suggestions in a chat window. The board already has hard and soft conflict checks built into it. If a change creates a scheduling problem, those existing checks can flag it for review. The assistant isn’t making up the operating rules as it goes. Those rules were there before I asked for the change. That distinction matters. A spoken request is another way into the system. It isn’t a reason to bypass the checks that make the system useful. The setup underneath matters People sometimes call this a company brain. I think of it more concretely: the records, operating rules and tools have to be connected well enough that an assistant can understand the request and act on the right thing. It needs to know which driver, which vehicle and which trip I’m talking about. It needs current information, not a guess based on an old conversation. It needs permission to make the particular change, and it needs to stop when it doesn’t have enough information or authority. Without that foundation, voice is mostly dictation. With it, I can direct work without doing all the navigation between the decision and the update. What if AI makes a mistake? It will. People make mistakes too. That doesn’t excuse either one. It makes the checks more important. Permissions limit what can change. The scheduling rules check for conflicts. I review important decisions and outgoing messages. If something is unclear, I want it brought back to me, not quietly filled in with a plausible answer. Those guardrails matter whether a person clicks the button or asks an assistant to do it. They don’t guarantee that every mistake gets caught. I still have to pay attention. Sometimes the assistant gets something wrong, needs more context or can’t complete a step. Sometimes I decide it’s quicker to do it myself. This isn’t an automatic business running in the background while I stop thinking about it. It feels more like working with an executive assistant who can use some of my software. I explain the outcome, make the decisions and check the work. The assistant handles more of the steps between them. I’m still running the business. I’m just spending less time finding the right screen and typing into it.