Choose outcomes before tasks
Start the week by selecting a small number of outcomes that would make the week meaningfully successful. Then identify which projects and tasks support those outcomes.
This prevents a long task list from defining importance simply because it contains many items.
Place fixed commitments first
Add appointments, deadlines, travel, and other time constraints before assigning flexible work. The remaining space is your actual planning capacity, not the theoretical number of hours in the week.
Protect buffer around important external commitments.
Convert priorities into next actions
Every weekly priority should have at least one action that can be started immediately. If you cannot name the next action, the project still needs planning.
Keep the action small enough that starting does not require another planning session.
Use implementation cues
Connect an action to a situation: after the Monday team meeting, review the proposal; when the train ride starts, read the application requirements. Clear cues reduce the need to make the same decision repeatedly.
Calendar blocks can serve as strong cues when the task needs uninterrupted time.
Close the loop daily
At the end of the day, mark actual completions, move unfinished work deliberately, and record the next action for anything you are leaving midstream.
The weekly plan should change as reality changes. Review is not failure; it is the mechanism that keeps the plan current.
Keep fixed dates on the calendar, executable actions as tasks, and multi-step outcomes inside projects. Preserve source evidence whenever a date came from a document.
Plan capacity, not just priority
A priority list can still fail when it assumes more working time than the calendar actually contains. Estimate the usable blocks left after meetings, travel, recovery time, and routine responsibilities. Then choose work that fits that capacity.
When capacity is tight, reduce the number of active outcomes before shrinking every task into unrealistic fragments.
Create a weekly recovery rule
Decide in advance what happens when a day is disrupted. For example, move only the highest-priority unfinished action to the next protected block and return everything else to the weekly review queue. A recovery rule prevents one delay from causing repeated ad-hoc rescheduling.
The plan should remain easy to understand after changes, not merely preserve every original intention.