I Stopped Typing for a Week. Here Is What Happened.

It started as a productivity experiment and became something stranger. For seven days, I used voice input for everything I could: emails, Slack messages, notes, article drafts, even commit messages. I typed only when I had no other option. Here is what I found.

Day One Was Humbling

The first morning was rough. I sat down to reply to an email and realized I had no idea how to speak a professional message out loud without sounding like I was leaving a voicemail. I kept starting sentences, stopping, starting again. The transcript looked like I had never written an email before.

By the afternoon, something shifted. I stopped trying to dictate the way I would type and started just talking through what I needed to say. The emails got better. Not perfect, but better.

Slack Was Surprisingly Easy

I expected Slack to be painful. Short messages feel like they should just be typed. But because they are short, the cost of imperfection is low. I would speak a message, glance at it, fix one word if needed, and send it. The whole thing took less time than typing, even accounting for the occasional correction.

By day two, I was sending Slack messages faster than before. The casualness of voice matched the casualness of Slack in a way that worked.

Long-Form Writing Changed Character

This was the part I did not expect. When I dictated article drafts, they came out differently than when I typed them. More direct. More example-heavy. The sentences were longer on average but somehow easier to read, probably because they followed the rhythm of actual speech.

I used VoiceInk for most of this, pressing a key to start, speaking a paragraph or two, then moving on. Because it runs locally on my Mac, there was no delay between speaking and seeing the text. That matters more than I thought it would. Even a one-second lag breaks the flow.

The drafts needed editing, as all first drafts do. But they needed less restructuring than my typed drafts usually do. The logic was already there because I had talked through it in real time.

The Unexpected Problem: Private Spaces

Two situations stopped me cold. Cafes, where I felt self-conscious speaking full sentences out loud, and phone calls, where switching to voice input mid-conversation felt strange. These are real limits of voice-first workflows. They are not dealbreakers, but they are genuine friction points.

I developed a workaround for cafes: I would draft in a quiet corner or step outside. It added a small logistical cost but also, oddly, forced me to batch my writing into longer focused sessions rather than scattered bursts.

My Hands Noticed the Difference

By day three, I realized my right hand was not aching at the end of the day the way it usually does. I have mild RSI from years of heavy typing, and the afternoon stiffness is normal enough that I had stopped registering it as a problem. Without the typing load, it mostly disappeared.

This alone made the week worth it.

What I Kept After the Week Ended

I did not go fully voice-first permanently. Typing is still faster for short bursts of structured text, code, and anything requiring precise formatting. But I kept dictation for three things: first drafts, long emails, and any writing session where I am trying to think something through rather than just record something I already know.

The week changed my default. I used to reach for the keyboard automatically. Now I ask, for a half-second, whether speaking would be better. Often it is.

If you have been curious about dictation but assumed it was only for people with accessibility needs or very specific workflows, one week is enough to find out whether it fits how you actually work. The experiment costs nothing except a little awkwardness on day one.