Chasing Sunsets

Lifestyle

A simple productivity system that survives a bad week

By C.S. · 12 min read ·

A green meadow with wildflowers and a wooden fence under a pink sunset, with a crescent moon and birds in a V. AI-generated artwork.

Disclosed AI-generated artwork.

Every productivity system works in the demo. Color-coded calendar, five priorities, a morning routine, a review every Friday. It works right up to the week when the kid gets sick, the boss moves the deadline, you sleep four hours, and the whole thing falls over by Tuesday lunch. Then you do not have a system. You have a pile of guilt with tabs.

This is a system for that week. It is small on purpose. It has five parts, they fit on one sheet of paper, and every part has a version you can do when you are running on nothing. If you can hold to it on a bad week, the good weeks take care of themselves.

Look at how most systems are built. They assume a stable morning, a full block of focused time, and enough energy left at 5 p.m. to review and re-plan. Those are the conditions of a good week. When they disappear, the system does not bend. It snaps, and because it snaps all at once, the natural response is to abandon it and go back to reacting.

There is a second problem. Long lists. A list of twelve tasks is not a plan, it is an inventory, and an inventory does not tell you what to do at 2:40 p.m. when you have twenty minutes and a headache. So you pick the easiest item, or you scroll, or you re-read the list. Psychologists call the pull of unfinished tasks the Zeigarnik effect: open loops keep nagging. What quiets the nagging is not finishing everything. It is having a concrete plan for the open item (Masicampo & Baumeister, 2011). A plan you can actually follow on a bad day is worth more than an ambitious one you follow only on the good ones.

The third problem is interruptions. You do not get an uninterrupted day. A well-known field study of knowledge workers found people switched tasks roughly every three minutes, and that after a real interruption it took on average more than twenty minutes to get back to the original work (Mark, Gonzalez & Harris, 2005; Mark, Gudith & Klocke, 2008). A system that needs four clean hours to work is a system that will not work most days. Build for the interruptions instead of hoping they stop.

The whole system on one page

Here it is in full: one thing, three items, blocks with slack, a parking lot, a shutdown. Five parts. The rest of this article explains each one and what to do with it when the week goes wrong. At the end there is a free printable that puts all five on a single sheet, because the system should be on your desk, not in a tab.

Step 1: The one thing

Before the day starts, or the night before, answer one question: if I only get one thing done today, what should it be?

Not the most urgent. Not the easiest. The one that, done, means the day was not wasted. Some days that is a piece of real work. Some days it is a phone call you have been avoiding. Some days it is a doctor’s appointment. It does not have to be impressive. It has to be the right one.

Write it at the top of the page, on its own, and try to do it first, before the day gets its hands on you. If first is impossible, at least protect a block for it. The point is that when the afternoon dissolves, and it will, the day already counted.

This is the part of the system that survives anything. You can be sick, sad, traveling, or drowning in other people’s emergencies and still do one thing. When you look back at a bad week and see five one-things done, that is not a bad week anymore. That is a week you got through with something to show.

Step 2: Three, not ten

Under the one thing, write two more. That is the day’s list: three items. Not five, not the seven that would make a nice week, three.

Three is not a magic number, but it is roughly the number of meaningful things a person actually completes in a normal working day once you subtract meetings, messages, and the general friction of being alive. Write ten, finish three, and you go home feeling seventy percent behind. Write three, finish three, and you go home done. Same work. Very different Tuesday night.

There is an old story about a consultant named Ivy Lee telling a steel executive to write down his six most important tasks each evening and work them in order the next day. Whether the story happened the way it is told is not the point. The method is sound and it has been re-invented under a dozen names since. Ours is shorter because most of us are not running a steel company, and because a shorter list survives a bad week better.

Everything that does not make the three goes in the parking lot, not on the list. That is a rule, not a suggestion. The moment the list grows past three, it stops being a plan.

Step 3: Blocks, with one already lost

Do not schedule your day by the hour. Schedule it in blocks: three or four chunks of roughly ninety minutes to two hours. Give each block a job. The one thing gets the first block if it can. Meetings and messages get their own block, so they stop leaking into all the others.

Then do the thing almost nobody does: plan for one of those blocks to disappear. Something will come up. A call, a fire, a person at your desk. If your plan needs every block, one interruption breaks the whole day. If your plan needs all but one, the interruption just lands in the block you had already written off.

People are reliably bad at guessing how long things take, and they do it in one direction. Kahneman and Tversky called it the planning fallacy in 1979 and it has held up in every study since. You will not fix this by trying harder. You fix it structurally, by leaving room. A day with slack is not a lazy day. It is an honest one.

Between blocks, take five minutes that is not a screen. Stand up, get water, look out a window. The block system only works if the blocks have edges.

Step 4: The parking lot

Everything that is not today goes in one place. One. A notebook page, a single note on your phone, the back of the planner. Not your head, not seven sticky notes, not the inbox.

The parking lot is where the other nine tasks live. It is also where ideas go when they arrive in the middle of a block, and where worries go when they show up at 11 p.m. The rule is simple: if it is in the parking lot, you are allowed to stop thinking about it. That permission is the whole point. David Allen built an entire method around this idea in Getting Things Done, and the core of it is right: a mind that trusts its capture system is a mind that can focus.

You do not have to organize the parking lot. Do not add tags, priorities, or colors. It is a holding pen, not a database. Once a week you will look at it and pull out the next few one-things. That is all the processing it needs.

For what it is worth, I kept a digital task manager for years and switched to a single ruled notebook the winter a project went sideways and I stopped opening the app. The notebook was slower, uglier, and always on the desk. That last part turned out to be what mattered.

Step 5: The five-minute shutdown

At the end of the working day, before you close the laptop or leave the desk, spend five minutes doing four things:

  1. Cross off what got done. Look at it for a second.
  2. Move anything unfinished to the parking lot or to tomorrow. Not both.
  3. Write tomorrow’s one thing at the top of a fresh page.
  4. Say, out loud or in your head, some version of “done for today.”

This sounds like a small thing. It is the second most important part of the system after the one thing. The shutdown is how you stop carrying work home in your head. The unfinished-task research is clear on this: once there is a written plan for the open loop, the loop goes quiet (Masicampo & Baumeister, 2011). Cal Newport made the shutdown ritual a centerpiece of Deep Work for the same reason. You are not being precious. You are giving your brain a receipt.

It also means tomorrow starts already decided. You do not walk in and spend the first forty minutes deciding what matters. It is on the page. You begin.

The bad-week version

Here is what makes this different from every system that has failed you: it has an official minimum, and the minimum is not a failure state.

On a bad day, the system is: the one thing, and the shutdown. That is it. No three, no blocks, no parking lot review. Pick the one thing, do it when you can, take five minutes at the end to write tomorrow’s, and stop.

On a bad week, do the bad-day version five times. Five one-things and five shutdowns. When the week is over, you will have five real things done and a plan for Monday, which is more than most people get out of a good week with a broken system.

The reason to write the minimum down is so you do not have to negotiate it when you are tired. Tired brains negotiate badly. They either demand the full system and give up, or they abandon everything. A pre-decided floor removes the negotiation. This is the same idea that makes a habit survive: never miss twice, and make the tiny version count.

If the bad week is turning into a bad month, that is a different problem and this system is not the fix. Sleep, food, people, and sometimes help from someone trained for it come first. The Help page has real numbers by country.

The weekly reset

Once a week, fifteen minutes, ideally at the same time so it becomes automatic. Sunday evening or Monday morning both work. Do three things:

  1. Read the parking lot. Cross out anything that is dead. Do not feel bad about the dead ones.
  2. Pull out the three to five items that should become this week’s one-things.
  3. Look at the calendar for the week and mark the days that are already going to be bad. Plan the minimum version for those days in advance.

That is the whole review. If you want to add a line about what went well, add it. If you skip the reset one week, nothing collapses. Do it the next week.

Mistakes that look like the system failing

The one thing is too big. If it does not fit in one block, it is a project, not a one-thing. Pick the next step of it instead.

The list is creeping. Three became four became six. Go back to three. Put the rest in the parking lot where they belong.

Skipping the shutdown because the day was bad. The bad days are exactly when the shutdown matters most. Two minutes. Write tomorrow’s one thing. Stop.

Using the parking lot as a to-do list. It is not. Nothing in it is due. If you read it every morning and feel behind, you are using it wrong. Read it once a week.

Trying to make it pretty. Apps, templates, and color codes are how people procrastinate on the actual system. A ruled page and a pen will do. The printable below is deliberately plain.

The free one-page planner

Everything above fits on one sheet: the one thing, three items, four blocks with one marked as likely lost, a parking lot, the shutdown checklist, and the bad-day minimum printed at the bottom so you do not have to remember it.

Download the one-page planner (PDF, free)

Print a stack. No email address, no sign-up, nothing to unlock. It is a US Letter page and prints fine on A4. If you want it as a phone wallpaper or a different layout, say so and I will make one.

Sources

  • Masicampo, E. J., & Baumeister, R. F. (2011). Consider it done! Plan making can eliminate the cognitive effects of unfulfilled goals. Journal of Personality and Social Psychology, 101(4), 667–683.
  • Mark, G., Gonzalez, V. M., & Harris, J. (2005). No task left behind? Examining the nature of fragmented work. Proceedings of CHI 2005, 321–330.
  • Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of CHI 2008, 107–110.
  • Kahneman, D., & Tversky, A. (1979). Intuitive prediction: Biases and corrective procedures. TIMS Studies in Management Science, 12, 313–327.
  • Allen, D. (2001). Getting Things Done. Viking.
  • Newport, C. (2016). Deep Work. Grand Central.

Newsletter

One email a week, when there is something worth sending

A new article, a quote, a free wallpaper. No spam, no selling your address. Leave any time.