I Stopped Typing for a Week. Here's What Actually Happened.

I set a simple rule for myself on a Monday morning: no typing except for passwords and code. Everything else, every email, every document, every Slack message, every note, had to be dictated. I gave myself seven days.

I expected to last about three.

Day One Was Humbling

The first thing I noticed was how many tiny things I typed without thinking. A quick reply to a message. A URL in a browser bar. A grocery item in a notes app. None of these feel like "typing" when you do them habitually, but they add up to a lot of keystrokes across a day.

I fumbled through most of Monday. Not because the transcription was bad, but because I kept defaulting to my keyboard before catching myself. My hands know the way. Breaking that habit took real attention.

By afternoon, though, something shifted. I had a long email to write, the kind I'd usually draft in stops and starts over twenty minutes. I just talked it out. It took four minutes. The draft needed minor cleanup, but the structure was there, and the tone was actually warmer than my typed emails tend to be.

The Middle of the Week Got Interesting

By Wednesday I stopped fighting it. I started treating every writing task as a conversation I was having with a future reader. That framing helped.

I dictated a 900-word article outline while walking around my apartment. I sent twelve emails before 9am without sitting down. My hands, which had been carrying low-grade tension that I'd stopped noticing, felt noticeably looser by midweek.

VoiceInk made the mechanics easy enough that I could stop thinking about the tool and focus on what I was saying. Press a key, talk, text appears. That simplicity matters more than I expected. Any extra step would have broken the rhythm.

I also found myself being less precious about first drafts. When you type, it's easy to stop and second-guess a sentence because your cursor is sitting right there, blinking at you. When you talk, momentum carries you forward. Editing is a separate act, and that separation turns out to be useful.

What Was Still Awkward

I won't oversell it. A few things stayed genuinely difficult.

Open-plan offices or shared spaces make dictation socially weird. I work from home, so this was minor for me, but it's a real limitation for people who don't have a private space.

Anything requiring precise formatting, technical strings, code snippets, was slower by voice. I broke my no-typing rule twice for code and felt fine about it. Voice input isn't trying to replace every possible input scenario.

And there's a learning curve to speaking for output rather than conversation. The first few days my sentences were fragmented, full of filler sounds, and hard to transcribe cleanly. By day five I was speaking in cleaner, more complete thoughts. That's a skill, and it develops fast.

What I Kept After the Week Ended

I didn't stay voice-only. But I kept more than I expected.

Long-form drafts: voice, always now. Emails over three sentences: voice. Meeting notes, thinking-out-loud documents, anything where I need to move fast: voice.

Short replies, code, anything structural: keyboard.

The split feels natural. My hands do less, my output is faster, and my wrists aren't complaining at 6pm the way they used to.

The experiment also revealed something I hadn't anticipated. Typing had become a way of slowing myself down, of feeling like I was being careful and deliberate. But a lot of that slowness was just mechanical drag, not careful thinking. Speaking forced me to commit to an idea and keep moving.

If you've been curious about voice input but haven't pushed yourself to actually rely on it, a week is long enough to find out what it can do for you. The awkward part passes faster than you'd think.