The no-typing week

The no-typing week is a seven-day experiment with one rule: capture every plan using only voice or screenshot, never the keyboard. You speak each event into Composed’s voice input, or screenshot the ones that already exist as images, and you let Apple’s Speech framework and Claude Vision do the structuring. The keyboard is off-limits for capture for seven days.

The point isn’t to prove voice beats typing. It’s to surface a number you’ve never seen: how many plans you were quietly dropping because typing them into a form wasn’t worth the ten seconds. People assume their capture rate is high because they remember the things they captured. The week makes the gap visible by removing the friction that was hiding it.

The rules

The rules are deliberately simple so the experiment is easy to actually run for seven days. There are three.

  • Capture by voice or screenshot only. When you remember a plan, speak it. When a plan arrives as an image — an itinerary, an invite, a texted schedule — screenshot it. No typing new events into a form.
  • Capture the moment you remember. Honor the 10-second rule from chapter 2.1. The experiment is about closing the gap between remembering and capturing, so capture while the thought is fresh, not “later.”
  • Editing is allowed. Fixing a misheard time or a wrong venue with one tap is fine — that’s reviewing the capture, not typing the event. The ban is on typing plans in, not on cleaning them up.

That’s the whole protocol. Seven days, voice or screenshot for everything new, fix-by-tap permitted.

What to track

Track three things, and track them lightly — a note in your phone is enough. The goal is awareness, not a spreadsheet.

First, how many things you captured this week versus a normal week. Most people are surprised it’s higher, because the small plans they used to skip now make it in. Second, how many captures landed right on the first try. This number climbs fast as your phrasing sharpens — by day three you’ll be saying the place out loud automatically. Third, the moments you reached for the keyboard out of habit and stopped yourself. Those reflexes are the friction you’re trying to notice; each one is a plan you might have dropped before.

The thing to measure isn’t whether voice is faster. It’s how many plans existed in your head this week that would never have survived the trip to a typed form.

What usually happens

What usually happens is that the first two days feel slightly awkward and the rest of the week feels obvious. Day one, you’ll catch yourself opening the keyboard and have to redirect to the mic — the habit is in your thumbs. By day three, the awkwardness is gone and you’re capturing things you’d normally have let slide: the “we should reschedule that” thought walking to the car, the recital date from the studio’s Instagram post, the dentist follow-up the receptionist mentioned at checkout.

The honest part: a few captures will miss, usually on one field, and you’ll fix them in a tap. A noisy room will trip the transcription once or twice. None of it is fatal, and the misses get rarer as your phrasing tightens. The Thursday you said “parent-teacher conference at 4 at Lincoln” without thinking about it — naming the school by reflex so the leave-by alert could do its job later — is the moment the method became a habit rather than an experiment.

What also happens is that the keyboard reflex weakens. By the end of the week, reaching for voice or screenshot stops feeling like a constraint and starts feeling like the faster path it always was.

After the week

After the week, keep the modes that earned their place and let go of the rule itself. The experiment was scaffolding; you don’t need a no-typing rule once voice and screenshot are your defaults. The keyboard comes back as the precision tool for edits and for the quiet rooms where speaking isn’t an option — exactly the type mode from chapter 2.1.

The result worth keeping is the higher capture rate. If the week showed you that more plans made it into a system you trust — including the small ones you used to drop — that’s the whole win, and it persists as long as the modes stay your first reach. The voice-to-calendar method is the phrasing that keeps voice reliable, and the voice input feature is where it lives.

Run it once. Pick a Monday, capture by voice and screenshot only through Sunday, and write down the three numbers. The experiment costs you nothing but a week of slight initial awkwardness, and it answers a question most people never think to ask: how much was I losing to the friction of typing? If you want to start before Monday, the voice-to-calendar hub is the fastest way in.

Next: Capture without judgment — capturing the things that feel too small, too obvious, or too embarrassing to write down.