Weekly Planner System: Three Priorities and a Friday Review

My week as a test manager is other people's problems arriving in no particular order: a supplier's build that fails on Monday, a defect nobody can reproduce, a steering committee that wants the report a day early. A plan that assumes none of that will happen is dead by Tuesday, and I have seen enough colour-coded hour-by-hour calendars die that way to stop making them. The alternative, opening the laptop and letting the inbox set the week, is worse. The thing with the real deadline never reaches the top of the pile until it is late.

What works for me is smaller than either. Twenty minutes on Monday morning to pick three things, a calendar that is 40% empty on purpose, five minutes each morning, and ten minutes on Friday to see what actually happened. The tooling is a weekly planner, a Pomodoro timer for the blocks, and whatever calendar you already have.

Monday, twenty minutes: three priorities, each with a day

Sunday evening if you prefer. I do it on Monday before the first meeting. The point is that it happens before the week starts pulling.

Three minutes: last week. What got finished, what carried over, what surprised you. This is calibration. After a few weeks you know how much a week of yours actually holds, and it is less than you think.

Five minutes: this week's three priorities. Three, not ten. The things that, if they are the only things you finish, make the week a success: the test report that goes to the steering committee, the entry criteria the supplier has to sign, the defect list that has to be triaged before the next build. If everything looks urgent, ask which one would cost the most if it slipped a week. That one is first.

Five minutes: a day for each. Not the only day you touch it, but the day it gets its block. Put the hardest one on Tuesday or Wednesday, before anything has gone wrong.

Two minutes: the fixed points. Meetings, deadlines, the release calendar. If Tuesday is wall-to-wall meetings, the hard priority moves to Wednesday.

The output is three lines with a day next to each and the fixed points underneath. It fits on an index card, and it should, because anything longer will not be read on Thursday.

Block 60% of the calendar and leave the rest empty

Time blocking means the calendar shows what you intend to do, not only who you intend to meet. The mistake is filling it. A calendar with every hour taken breaks the first time a meeting overruns, and in a week with suppliers in it something always overruns.

Block 60% and leave 40% open. For an eight-hour day that is about five hours in blocks (two or three for the priorities, plus the meetings) and three hours for email, small tasks, questions from the team and whatever arrives.

Make the priority blocks long. Thirty minutes is not a block; by the time the context is loaded it is over. Ninety minutes is the minimum for anything that needs thought. Inside the block, the Pomodoro timer at 25 minutes on and 5 off keeps me out of the inbox, which is the real threat to a block, not the meeting.

Defend the block the way you would defend a meeting with your most senior stakeholder. Someone asks for that slot, you offer another. Let it get overwritten three times and you stop believing the calendar, and then the whole thing is decoration.

Five minutes each morning, before the inbox

The weekly plan sets the direction. The morning check keeps you on it. Before email, before the chat client:

1. Look at today. Which meetings, which fixed points, how much open time is left.
2. Pick one to three tasks from the weekly priorities. Specific ones. Not work on the report, but write the defect summary section of the report.
3. Decide what goes first. The hardest one gets the first block, while the day is still clean.

Three decisions, five minutes. The rest of the day is execution, and when one task ends the next is already chosen, which is the part that matters. Deciding what to do next at 15:00 with three people waiting is how the small urgent thing wins over the large important one.

I tick the tasks off in the weekly planner as they go. The ticks are the raw data for the Friday review, and it is surprising how much of a week you have forgotten by Friday without them.

Interruptions: two questions and a note

The plan is not a contract. It is the thing that tells you what you dropped when something else arrived.

When something arrives, two questions:

1. Is it more important than what I am doing now? Yes: switch. No: write it down and go back.
2. Does it have to happen today? Yes: decide what it replaces on today's list. No: it goes on tomorrow or later in the week.

The writing down is the important part. An interruption is expensive because it sits in your head next to the task you were on. Five words on the list and it leaves your head.

When the whole week is gone, not one day but all of it (a production incident, a release date moved, a personal emergency), take five minutes and plan the remaining days from scratch. Three days will not hold five days of priorities. Move some to next week and say so to whoever is waiting for them.

The four kinds of interruption and what I do with each:

• Urgent and important: the supplier's build is broken and the test window closes tonight. Switch now.
• Important, not urgent: a tester wants a second opinion on a test design. Block 30 minutes tomorrow.
• Urgent, not important: five people want a quick reply. One 20-minute batch, not five separate breaks.
• Neither: the forwarded article. Weekend, or never.

Friday, ten minutes: the review is what makes it work

Without the review you plan every week in a vacuum and repeat the same mistake. Ten minutes at the end of Friday:

What got done. Read the ticks. Most people undercount their week because Monday and Tuesday are gone by Friday.

What did not, and why. This is data, not guilt. A task that has carried over three weeks running is telling you something: it is not important (delete it), it is too big (split it), or it is blocked (go and unblock it). In defect terms, a ticket that stays open for three weeks is never waiting on nothing.

What you learned. You planned too much, a kind of work took twice as long as you thought, mornings are better for writing and afternoons for meetings. One line, and it changes Monday's plan.

What is already on Monday. Seeing the steering committee on Friday afternoon means you do not meet it cold on Monday morning.

The one number I would track is completed priorities over planned priorities. Three out of five every week means the plan is too big or the estimates are wrong, and both are fixable. Aim for 80%, and adjust the planning rather than the effort until you get there.

The template is ten lines, and it stays ten lines

The best tool is the one you will still be using in March. Paper works for some people and a screen for others, and switching every month in search of the perfect one is itself the problem. Pick one and give it three months.

For a digital setup this is all of it:

• Tasks: the weekly planner, in the browser, nothing uploaded. A project management tool for one person's week is more tool than week.
• Focus: the Pomodoro timer. Counting the focused hours in a day is sobering the first time.
• Calendar: whatever you already have.

The template:

` Week of [date]

Priorities: 1. [Top priority], target day 2. [Priority 2], target day 3. [Priority 3], target day

Fixed points: - [Meetings, deadlines]

From last week: - [What worked] - [What to change] `

Ten lines, fifteen minutes on Monday. It beats most elaborate systems for one reason: you will still fill it in during week twelve.

The pull is always toward more. A column for energy levels, a colour per project, a scoring model. Resist it. A system that works at ten lines does not work better at fifty, and the review is for changing what you do, not for adding fields.

FAQ

What about weeks where the calendar is not mine?

Meeting-heavy weeks get smaller priorities: three 30-minute tasks that fit between meetings instead of one that needs a clear afternoon and never gets it. Lower the ambition to the time that exists. A finished small thing beats an unstarted large one.

Should the weekend be planned?

Only if you want it to be. A light list (two personal things and one thing you enjoy) suits some people; for others a planned weekend is not a weekend. I would try each for a month and keep whichever you stuck with.

My job is reactive: support, on-call, service desk.

Plan the calm hours only. If there are two quiet hours a day, one priority task goes in them. For the rest, the planning goes into checklists and templates that make each reactive task faster, because you cannot plan when the tickets arrive but you can plan how you handle them.

How long before it feels normal?

Three or four weeks, and the Friday review is what carries it there. It is the moment you see that planning the week changed the week. Skip the review and the Monday session starts to feel like paperwork, and within a month it stops.