A thirty-minute spoken ritual that turns a messy week into a short plan.

Voice Routines for Weekly planning start with a clean input set, because a plan built on memory alone repeats last week's omissions. Open four things before you speak: the list of open commitments, your calendar for the coming week, the messages that need a decision, and the project list you actually maintain. Skim each one and mark only the items that require action in the next five workdays. Close everything else. Put the marked items in a single document under three headings: must finish, must start, and must decide. The gathering step should take ten minutes and produce a short list, not a second inbox. A narrow input set keeps the spoken plan specific.
Convert each marked item into a line that names the deliverable and the owner. A line such as finish the pricing comparison by Tuesday is usable; a line such as think about pricing is not. If an item has no owner, write your name or the name of the person who must act. If it has no date, decide whether it belongs this week at all. Move unscheduled items to a later list instead of letting them blur the plan. Read the list aloud once and remove anything you cannot explain in one sentence. A weekly plan earns its keep by being short enough to remember and specific enough to start.
Look for conflicts before you schedule anything. Two deliverables due on the same morning, a meeting that blocks the only focus block, or a dependency on someone who is away can all turn a reasonable plan into a scramble. Write each conflict beside the affected line and decide which item moves. Do not solve every conflict during the planning pass; mark the ones that need a conversation and schedule that conversation. The goal of this step is to surface collisions early, while there is still room to move. A conflict noticed on Monday is a scheduling choice; the same conflict noticed on Thursday is an emergency.
Set a thirty-minute limit for the whole ritual and divide it into gathering, speaking, and confirming. Use a timer for the first month. If gathering takes longer than ten minutes, the input set is too broad; if speaking takes longer than ten, the list is too long. Stop at the limit and carry the remainder to a short follow-up later in the day. A weekly plan that consumes an afternoon is a project, not a routine. Keep the timer visible and write the actual duration on the planning card. The duration is the first measure of whether the ritual is sustainable.
Speak the week in five fixed slots, one for each workday, rather than as an unordered list. For each day, say the one outcome that would make the day worthwhile, then the two tasks that support it. Keep the outcome concrete and the tasks small enough to finish or hand off. If a day has no clear outcome, say so and mark it as a buffer or a meeting-heavy day. A fixed slot makes the plan easy to review and easy to adjust when something slips. It also prevents the common failure where every task is assigned to Monday and the rest of the week becomes a backlog.
Place the most demanding work in the slot where you actually have energy, not where the template says it belongs. If your mornings are interrupted, put the deep task in the afternoon and the shallow tasks in the morning. Say the reason aloud so the plan records why a slot looks unusual. When a day is already full of meetings, reduce the outcome to a single small deliverable rather than pretending the day is open. The spoken plan should describe the week you will actually have, not the week you wish you had. Realism is more useful than symmetry. Write the reason beside the slot so the choice is visible at a glance.
Keep two fixed anchors in every slot: a start time and a stopping condition. The start time protects the task from being crowded out; the stopping condition tells you when to stop even if the task is not perfect. Say both aloud as part of the plan, for example draft the section from nine to ten thirty and stop when the outline is complete. Without a stopping condition, a single task can absorb the whole day and push the rest of the plan aside. Write the anchors on the planning card and copy them into the document you check each morning.
Leave one slot deliberately open for the work that always appears. Every week brings an unexpected request, and a plan with no room for it breaks on the first surprise. Say the open slot aloud and name the kind of work it is likely to absorb, such as urgent reviews or a colleague's question. When the week ends without a surprise, use the slot for a task that has been waiting. Do not fill the open slot during planning just because it looks empty; its value is its availability. A plan with slack survives contact with a real week. Review the open slot on Thursday and decide whether to use or protect it.
Choose no more than three priorities for the week and state each one as a commitment rather than an intention. A commitment names the result, the date, and the person who will receive it. For example, send the revised budget to the finance owner by Wednesday afternoon. Say the three commitments at the start of the spoken plan, before the daily slots, so the days can be arranged around them. If a priority cannot be expressed as a commitment, it is probably a theme rather than a task. Themes are useful for direction, but they do not tell you what to do on Tuesday morning.
For each commitment, say what you will stop doing to make room. A week has a fixed capacity, and adding a priority without removing something is a plan to work late. Name the task you will defer, shorten, or hand to someone else. If nothing can be removed, reduce the scope of the commitment until something can. Write the trade on the card beside the commitment. A visible trade makes the plan honest and gives you a defensible answer when a new request arrives. Keep the trade on the same line as the commitment so it cannot be forgotten. Commitments without trades are wishes with a deadline attached.
Check each commitment against the inputs you gathered. If the commitment depends on a document, a person, or an approval, say when that dependency will be available. If it will not be available before the deadline, change the deadline or change the commitment. Do not plan to chase a dependency on the same day the result is due. Write the dependency beside the commitment with a date. A commitment that assumes everything arrives on time is fragile; one that names its dependencies can be adjusted before it fails. If a dependency has no date, treat the commitment as unplanned until it does.
Read the three commitments aloud at the end of the planning pass and ask whether you would defend them in front of the people who receive the results. If the answer is no, reduce the number or rewrite the weakest one. Keep the final list to three lines and put it at the top of the document you check each morning. The daily slots support these lines, not the other way around. When a new request arrives during the week, test it against the three commitments before accepting it. A short list is easier to defend than a long one.
Move the plan into the tools you already use before the planning pass ends. Put the three commitments at the top of your task list, copy the daily outcomes into your calendar, and add the dependencies to the relevant project note. Do not create a new system for the plan; the cost of maintaining a second system is usually higher than the benefit. If a tool cannot hold a detail, put the detail in the planning document and link to it. The plan is confirmed when you can find each commitment from the place you normally start your day. If that takes more than a minute, the plan is not finished.
Check that the calendar and the task list agree. A task scheduled on a day with no available time is a plan that will slip. Read each daily outcome against the meetings already on the calendar and move the task or shorten it. If a meeting changed after you planned, update both places before you close the pass. Write the date of the confirmation beside the plan. The check is boring and takes five minutes, but it prevents the most common weekly planning failure: a good list that never meets an available hour. Move a task to a day with real capacity rather than extending its estimate.
Confirm the people side of the plan as well. If a commitment depends on a colleague, send a short message that names the result and the date, and ask them to confirm. If a meeting needs an agenda, add it now rather than the night before. If a decision needs an owner, name the owner in the note. The plan is not real until the people involved know what they are expected to do. Keep the messages short and specific; a confirmation is not a status report. Record which confirmations are still missing. Add the unanswered confirmations to the top of the next day's list.
Keep the plan in one place and one format for the whole week. When something changes, update the plan rather than starting a new note. If a change is large, write a single line explaining what moved and why. At the end of the week, the plan and its changes become the input for the review. A plan that is edited in place is easier to compare than a collection of daily notes. Consistency of format is what makes the Friday review take fifteen minutes instead of an hour. Name the file with the week and the year so versions sort in order.
Review the week against the three commitments, not against the length of the task list. For each commitment, mark delivered, partly delivered, or missed, and write one sentence about the cause. Compare the daily outcomes with what actually happened and note where the plan was unrealistic. Keep the review to fifteen minutes and write it in the same document as the plan. A short review that happens every week is more useful than a thorough one that happens once a quarter. The comparison is the evidence you use to plan the next week more accurately. Write the review in the plan itself so the next gathering step sees it.
Identify the single biggest planning error and the single biggest planning win. The error might be an underestimated task, a missing dependency, or a day with no slack. The win might be a commitment that finished early or a slot that absorbed a surprise well. Write both in one sentence each and add them to the planning card. Do not list five errors; one clear lesson is easier to apply. If the same error appears three weeks in a row, change the template rather than trying harder. Repeated errors are a design signal, not a discipline problem. Keep the lesson short enough to read before the next planning pass.
Archive the week and prepare the next input set. Move unfinished items to the next planning document with a note about why they remain open. Close the tabs and documents you no longer need, and keep only the sources for the next commitment. If a colleague will cover part of the week, give them the commitments, the dependencies, and the confirmations that are still missing. A clean archive makes the next gathering step faster and prevents an old task from reappearing without context. Give each carried item a new date or remove it from the list. A clean archive is part of the planning work, not an afterthought.
When you want to try the same planning ritual on another machine, download Voiskey for Mac or Windows and keep the planning card identical. Voiskey turns speech into text at the insertion point in the app you are already using, so the commitments land in the same kind of document you use now. Run one planning pass and compare the duration with your usual time. Keep the format stable for a month before changing it. A routine that survives a change of machine is one you can rely on during travel or a hardware swap. Record the duration and any differences in the planning card.
Gather four inputs first: open commitments, the coming week's calendar, messages that need a decision, and your project list. Mark only what needs action in five workdays, then speak the week in five daily slots. Voiskey places the text at your insertion point, so keep each slot to one outcome and two supporting tasks.
Dictate the items that require a decision or a deliverable in the next five workdays, each with an owner and a date. Add the conflicts you can see between deadlines, meetings, and dependencies. Leave background material out; the pass should start from a short, specific list rather than a full project archive.
Limit the week to three commitments, each naming a result, a date, and a recipient. State what you will defer or shorten to make room. Check every dependency and confirm the people involved before the pass ends. Put the three lines at the top of the document you check each morning.
Mark each commitment delivered, partly delivered, or missed, and write one sentence about the cause. Name the biggest planning error and the biggest win, then add both to your planning card. Move unfinished items into next week with a note, and archive the week before you gather the next input set.

Download Voiskey for Mac and Windows and run one thirty-minute weekly planning pass.
Use it across macOS, Windows, iOS, and Android