How to Make a Weekly Priority List

- Choose outcomes only after seeing available capacity
- Map the week before naming the winners
- Gather tasks in one temporary list
- Select three layers, not one ranking
- Write priorities as finish lines
- Put each priority on the calendar
- Use a daily pull, not a daily rewrite
- Review the week without grading your character
Choose outcomes only after seeing available capacity
Make a weekly priority list by placing fixed commitments and essential maintenance on the calendar first, estimating the work blocks that remain, and choosing no more major outcomes than those blocks can support. Write each priority as a result, give it a next action and scheduled block, then keep other tasks on a separate backlog.
A list of thirty “priorities” is not ambitious. It is a normal task list wearing a fake mustache.
Map the week before naming the winners
Open the calendar and add existing meetings, appointments, travel, care, classes, deadlines, and personal commitments. Then reserve realistic time for email, preparation, administration, meals, transitions, and recovery. Those activities use capacity whether or not the planner finds them aesthetically inspiring.
Mark the blocks in which focused work is actually possible. Note differences in energy, location, tools, and interruptions. A sixty-minute block on a quiet morning is not identical to sixty minutes between calls, and planning becomes saner as soon as the boxes stop pretending otherwise.
For more capacity-first planning, visit Workable Weeks.
Gather tasks in one temporary list
Collect open work from notes, email flags, project systems, messages, and memory. Do not organize while gathering. Include follow-ups, maintenance, and decisions—not merely large visible deliverables.
For each item, ask:
- What happens if this waits one week?
- Is another person blocked?
- Does it move an important project or only maintain one?
- Is the deadline real, current, and owned by someone?
- What is the smallest complete result?
- What information or permission is missing?
Remove duplicates and obsolete items. Delegate only when responsibility, authority, context, and timing are clear; forwarding a vague task is not delegation so much as relocating weather.
Select three layers, not one ranking
Use three layers:
Commitments: work that must happen because of a real deadline, consequence, or promise.
Progress: one or two meaningful outcomes that advance important work.
Maintenance: recurring actions that keep systems, relationships, health, and life operating.
This prevents maintenance from masquerading as all available progress and prevents exciting progress from quietly eating payroll, medicine pickup, or the meeting preparation that keeps Thursday civilized.
If the commitments already fill the week's work blocks, the honest priority decision is renegotiation. Do not add a progress goal merely so the page looks visionary.
Write priorities as finish lines
“Website” is not a weekly outcome. “Approve the homepage copy and send the final assets to development” is. A useful priority contains a verb, an object, and a visible done state.
Add its first action:
- open the latest copy and list unresolved comments;
- request the missing sales figures;
- outline the first three sections;
- book the inspection; or
- choose between the two documented options.
Estimate with humility and include revision, communication, setup, and waiting. When uncertainty is high, schedule a discovery block whose result is a better estimate or decision—not a fantasy promise that the entire project will emerge by lunch.
Put each priority on the calendar
Assign a work block to every chosen outcome. If no suitable block exists, it is not a plan for this week. Move it to the backlog, reduce its scope, or renegotiate another commitment.
Add buffer around fragile days and before external deadlines. Keep a small list of low-energy or short tasks for gaps, but do not pack every gap in advance. Capacity held for interruption is doing a job even when no interruption arrives.
The guide to resetting after an unproductive week shows how to communicate slipped work and diagnose why a previous plan failed.
Use a daily pull, not a daily rewrite
At the end of each day, check progress and pull the next action from the weekly list. Adjust blocks when new facts appear, but preserve the distinction between chosen outcomes and incoming requests.
For a new task, ask what it displaces. If the answer is “nothing,” inspect the calendar again; the task may have discovered a rare pocket of imaginary time.
Limit the daily list to what can fit around scheduled work and maintenance. Carrying ten items forward every evening adds copying, not capacity.
Review the week without grading your character
At week's end, mark each outcome complete, continuing, cancelled, or renegotiated. Note why estimates missed and which interruptions repeated. Write the next action for continuing work before closing the review.
Use the pattern to improve one planning assumption: meeting recovery, dependency timing, work-block length, routine load, or the number of concurrent priorities. A useful weekly list is not the one with the most crossed-out lines. It is the one that made tradeoffs visible early enough to choose them.