The phone walk home is the most underused writing slot most people have. Twenty minutes, hands free, brain still warm from work. Voice into Claude correctly and you arrive at your door with half a doc already structured, not a wall of “um” you will never reopen.
What this covers
A repeatable phone-first workflow for turning loose voice input into shaped output: meeting recaps, doc drafts, post outlines, decision memos. The trick is not the transcription quality — it is what you tell Claude to do with the transcript the moment you stop talking.
Who this is for
Anyone whose best thinking happens while moving and worst thinking happens at a blank screen. PMs prepping standups, writers stuck on intros, founders crafting investor updates, ICs writing weekly notes. If your laptop draft of the same idea takes 90 minutes and your shower version takes 4, you are the target reader.
When to reach for it
Reach for it when you have an unstructured idea, a 10-25 minute walking window, and a doc shape in mind (recap, memo, post). Skip it for tasks that need exact figures, code, or careful citation — voice rushes you past the moments where precision matters.
Before you start
- Decide the output shape before you press record. “5-bullet status update” beats “thoughts on Q3.”
- Pick a place where you can talk semi-loudly without performing for strangers — voice gets stiff when you self-censor.
- Confirm the Claude mobile app has microphone permission and that you are on the model tier you actually trust for writing (not the free fallback).
- Have one anchor file open in a Project — last week’s update, the doc template, the meeting agenda — so the output inherits your real voice.
Step by step
- Open the Claude mobile app inside the Project that holds your template and voice samples. Voice without a Project gives you generic prose.
- Lead with the shape, not the content: “Take what I am about to say and turn it into a 6-bullet weekly update following the template in
update-template.md. Ignore filler words. Group related thoughts.” Speak that part first, then ramble. - Hold the voice button and just talk. Aim for 3-8 minutes. Anything past 10 and the front of your monologue gets compressed away.
- Stop recording and immediately send. Do not edit the transcript by hand on the phone — you will tidy “um” out for 20 minutes and lose the original momentum.
- Read Claude’s structured reply before you get home. If a bullet is wrong, reply with one voice message: “Bullet 3 is wrong — the launch slipped to Thursday, not Tuesday. Rewrite that bullet.” One correction at a time keeps the doc tight.
- When you get to a laptop, paste the output into the real surface (Notion, Google Doc, email). The phone chat was scratch space, not the deliverable.
First-run exercise
- Pick a recurring artifact you wrote on your laptop this week — a weekly update, a standup recap, a post intro. Time how long it took.
- Next time the same artifact is due, walk for 15 minutes and run this workflow instead. Save the output.
- Diff the two versions: which had more shape? More specifics? Fewer hedges?
- Note the gap. Most people find voice-first drafts are 70-80% as good in 30% of the time — that ratio is the whole reason to use this.
Quality check
- Does the output match the shape you asked for, or did Claude invent its own structure? If the latter, your opening shape instruction was too vague.
- Are the specific names, numbers, and dates accurate? Voice transcripts mis-hear proper nouns constantly.
- Did the synthesis flatten a nuance you actually care about? Voice + LLM both smooth toward the average.
How to reuse this workflow
- Save your three favorite opening shape instructions as a snippet on your phone. “Weekly update mode,” “post outline mode,” “decision memo mode” — paste, then talk.
- Keep an anchor file per output type inside the relevant Project so voice rambles always have a template to shape against.
- Log the artifacts you wrote this way in a small list — patterns appear after ~10 entries about when voice helps and when it hurts.
Recommended workflow
Walk home from the office → open the right Project on Claude mobile → speak the shape instruction first → ramble for 5-8 minutes → send → read structured reply at the next crosswalk → one voice correction if needed → paste final into your real doc tool when you sit down.
Common mistakes
- Recording for 20 minutes straight — the front half gets compressed beyond recognition.
- Skipping the opening shape instruction and hoping Claude guesses the format from context.
- Editing the raw transcript by hand on the phone instead of letting Claude restructure.
- Using voice for work that needs exact numbers — figures, dates, and citations get garbled.
- Trusting the first output for anything customer-facing without a laptop pass.
- Voice-ing into a fresh chat with no Project, then wondering why the tone is generic.
FAQ
- Will Claude show me the raw transcript?: Yes, but treat it as a backup. The structured output is the deliverable.
- What if I lose connection mid-walk?: The mobile app holds your input locally and sends when reconnected. Do not retry; you will double-send.
- Should I use Whisper or a dedicated transcription app instead?: Only if you need verbatim quotes. For shaped drafts, Claude’s built-in voice plus instructions wins on speed.
- Can I use this for sensitive client work?: Check your firm’s policy on voice data leaving the device. Many shops allow text chat but not voice.