<- leave the wiki or go home

A flexible and humane strategy for weekly planning

Tags: living

The Post-Effective Priority Queue is the name I came up with on the spot for a system I've been using for around two years now to schedule things I need to do over the course of a week. "Post-effective" implies here that, to a certain extent, it comes from Stephen Covey's ideology of "effectiveness" but tries to learn from its mistakes and move past them in a meaningful way.

Motivation

Todo lists

Todo lists are a very common tool to schedule tasks. All you have to do is break all your responsibilities into discrete tasks and cross them off your list as you complete them. You can order them by priority and/or complete them based on how much energy you have at a given moment.

Probably the biggest issue with todo lists is that they poorly represent how tasks should be distributed over time; instead, they tend to take on the form of a single fire hose of work. This is appropriate for some, but not all responsibilities.

Time-blocking

Time-blocking is when you designate "blocks", or whole periods of time to specific tasks. This can be done in conjunction with daily/weekly planning, though it would probably be unfeasible in monthly planning.

This is, in my opinion, the optimal scheduling strategy if you're optimizing for tasks completed and minimal time wasted. Realistically, though, this strategy has a number of problems:

However, time-blocking can help to contextualize tasks in a larger daily or weekly plan, which can be helpful with motivation.

Planning periods

Daily planning is ineffective for solving long-term problems. Monthly planning demands so much flexibility that most of your time planning things in advance will be wasted.

Certain self-proclaimed self-help gurus will tell you that weekly planning is a good compromise between these two extremes. I have found this to be mostly true in my personal experience. Some issues with it, however, include:

The Post-Effective Priority Queue

The Post-Effective Priority Queue (PEPQ) is a set of three priority queues that describes all the discrete tasks you want to accomplish over the course of a day. The first is designated for the morning, the second for the afternoon, and the third for the evening.

Each day is given its own PEPQ. At the beginning of the week, you list out everything you need to get done by considering where you are with your projects and revisiting deadlines, and then you assign each task to one of the three priority queues. How exactly you assign them is very personal, and it can take a while to figure out what works best for you.

When you start your day and you're ready to do work, you start with the top entry in the morning PQ, and move on until it's empty. Between completing each PQ, you should probably include some longer break, like eating lunch or supper.

If you don't complete all the items in your priority queue before you move on to the next unit of time, then you can quickly decide to reschedule them to tomorrow, or have all of the tasks roll over into the next PQ, depending on what makes more sense for the given tasks.

If several PQs start to pile up with unfinished work, then you need to take a step back and seriously reconsider how you're trying to schedule your work. It's possible you're either being overworked, or that you need to re-evaluate how you're prioritizing tasks.

Aside: wait, what's a priority queue exactly?

A priority queue is a data structure used quite a bit in software engineering. It's an ordered list of things, where their order is determined by some kind of "priority." When new items are put into the priority queue, they are inserted wherever their priority dictates they be. So, if you have three low-priority items in your priority queue and you add a high-priority item, then the new one is going to be next up in line. This is exactly how hospital emergency rooms order patients. In Canada, at least. Elsewhere, I get the feeling it has more to do with how much money you have.

In this context, we might choose to think of the priority as "how urgent they are," but in practice, what this priority actually represents is a lot more subtle and determined through lots of trial and error. Very, very generally, I think I might say that I usually order tasks by some combination of what kind of work they represent, how it'll make me feel to complete those tasks, and how well they would match how much energy I expect to have at a given point in the day.

How does the PEPQ compare to other strategies?

Here's how I believe the PEPQ improves upon or similarly fails like the other strategies listed above:

What do PEPQs handle poorly?

PEPQs don't do a very good job at representing work that doesn't break down into small, discrete tasks. Often I find I'll end up with things like "figure out what I need to do for X," or "spend some time doing Y." This mostly works, but these tasks are probably better suited for a different, parallel system.

Implementing PEPQs with software

To my knowledge, no applications support PEPQs both functionally and visually. You can recreate most of the functionality with a todo list app that supports assigning tasks due dates and priorities, and you can represent it pretty well visually with a weekly planner app, but few apps do both well in my opinion.

The way I do it is with a spread sheet. I typically create three spreadsheets a year: one for the winter, one for the summer, and one for the fall. Then, I create a new sheet for each week. The weekly sheet lists the days in the columns, and divides chunks of rows with different colours to represent the three priority queues. Then, as I complete tasks, style the cells with a strike through, which I've set up as a keyboard shortcut.