A 30-minute commute OS

The point of a commute routine is not to squeeze more output out of the day. It is to arrive with your priorities already decided, and to leave without carrying the day home unprocessed. Both are voice-only tasks. Here is a structure that fits thirty minutes each way.

Morning: decide, do not execute

• Minutes 0-5. Say the day out loud: what is on the calendar, what is actually due, what you are dreading. No tools required. This alone removes most of the morning fog.
• Minutes 5-15. Pick the one thing. Ask your assistant to argue with your choice — if the argument is convincing, change it. Then say the first concrete action for that one thing.
• Minutes 15-25. Prep the hardest conversation of the day. What is their position, what is your ask, where can you concede. Speak it, do not just think it.
• Minutes 25-30. Silence. Arrive settled rather than mid-sentence.

Evening: process, do not plan

• Minutes 0-10. Narrate what happened. What moved, what stalled, what surprised you. Capture as a structured note, not a rambling memo.
• Minutes 10-20. Loose ends. Every 'I owe someone a reply' becomes a spoken reminder. You are not answering anything, only making sure nothing is held in your head overnight.
• Minutes 20-30. Nothing work-related. This is a boundary, not a gap in the system.

Rules that keep it working

• Never plan in the evening. Evening planning produces anxiety and bad decisions; morning-you has better information anyway.
• One capture destination. If your voice notes land in three places you will trust none of them.
• Skip it when conditions are bad. Heavy rain, unfamiliar route, or a tired driver means the commute OS is off. It is a nice-to-have, not a commitment.

Run it for two weeks before judging it. The first few days feel awkward because talking to yourself in a car is awkward. By day ten it is the most reliable planning slot in the week, mostly because nothing else can be scheduled over it.