Notes · Restart & resilience
Most productivity systems work when energy is high. The one that decides whether a system stays alive is the bad week. Here is how to design for that week specifically.
You know which week we mean.
Maybe you were ill. Maybe a relative needed something. Maybe the work itself caved in. Maybe nothing dramatic at all — just a week where your energy did not arrive and the days passed without much progress on anything.
That week is the week your productivity system either survives or quietly dies. If you have used many productivity tools over the years, you can probably trace each abandonment back to one specific bad week.
This article is about building a system for that week. Most productivity writing is implicitly about good weeks — assumed energy, assumed focus, assumed clarity. The bad week is the test most systems fail. It is also, in many ways, the more important design constraint.
A good week supports its own system. You feel productive; you open the app; the app reflects your productivity back at you; the loop is virtuous.
A bad week breaks the loop in a specific way. You feel low; you open the app; the app shows you the gap between what you said you would do and what you actually did; you close the app; you do not open it again for several days. By the time you come back, the gap has widened. The visible inventory of unfinished items is larger than it was. The first thing you see is, effectively, here is how far behind you got.
This is why so many productivity tools have a quiet adoption curve — strong start, fast decline. The strong start is the optimistic version of yourself. The fast decline begins the first time the tool punishes you for being human.
If a system cannot survive the user's worst week, it is not really a system. It is a fair-weather tool dressed up as one. The work is to find or build the system that holds when nothing else is holding.
There are three properties that distinguish bad-week-survivable systems from fair-weather ones.
This is the central design property. When you come back to the system after a few days away, what greets you matters enormously.
If the first thing you see is a long list of overdue items, the system has just confirmed your worst fear about the missed week. You will close it and come back even later.
If the first thing you see is the work you have already built — the garden, the journal, the done-list — the system shows you context first. The unfinished work is still there, but it is not the headline. The headline is here is what you have done so far this year. You can navigate to the unfinished items deliberately, but you are not greeted by them.
This sounds like a small UX choice. It is the biggest factor in whether a productivity tool survives long-term use.
Alice Boyes in Psychology Today makes a related point about overwhelm in general: when we are mentally depleted, our brains default to fight, flight, or freeze responses — and freezing is what looking at a long list usually produces.1 A system that primes the freeze response, every time the user opens it after a bad day, is not going to be used.
In a bad-week-survivable system, missed items are present but not aggressive.
No red. No badge counts. No notifications that climb. No "overdue" labels in shouting type. Items that did not get done last week just sit there, available when you are ready to look at them, invisible until then.
This is not the same as hiding them. A system that hid overdue items would make you more anxious — you would not trust it. The right design is to show them but not amplify them.
In practical terms: the difference between a productivity tool that uses red colour for overdue and one that uses the same neutral colour for all items is the difference between a tool that feels stressful to open on a tired day and one that does not.
Most popular productivity apps send push notifications when you stop using them. Your streak is at risk. You have not opened the app in 3 days. Make today the day. These are designed by growth teams, with the best intentions and the wrong assumption: that users disengage because they need a nudge.
In reality, users disengage during bad weeks because they need space. A push notification, in that moment, reads as a small criticism. Several push notifications in a row read as harassment.
A bad-week-survivable system does not chase you. When you are not using it, it is patient. When you come back, it is calm. The implicit promise is: I will be here when you are ready, and I will not behave as though your absence was a betrayal.
It is a small philosophical position, expressed through notification settings. The position turns out to make the difference between abandonment and durability.
When the bad week is happening, the right move is not to do more. It is to reduce what the system asks of you to the smallest, kindest minimum.
Three reductions that help:
The instinct on a bad day is to fix the system, to add structure, to over-plan. That instinct is wrong. The bad day wants less of the system, not more.
A specific scenario: it is Monday morning. The previous week was bad. The system is in disarray.
What you should not do is open the task manager and try to clean it up. That is a salvage operation dressed up as productivity, and it will eat your morning energy without producing any forward motion.
What you should do, in this order:
Total time spent reckoning with the bad week: 10 minutes. Total time spent doing the work that matters most: the next two hours.
You will come back to the unfinished items later. Maybe tomorrow. Maybe at the end of the week. They will not get worse for being unattended for a day. Your week will, however, get visibly better for spending its first two hours on the important thing rather than on the cleanup thing.
This is essentially what Oliver Burkeman has called the non-strategy — a quiet acceptance that you cannot do all of it, and a deliberate choice of the few things you will do anyway.2
Oasa was built around this exact problem.
The Zen Garden does not shrink when you stop tending it. If you come back after a difficult fortnight, the Garden you had built before the fortnight is still there, in the same state. The Seeds that did not get tended sit quietly. There is no red. There is no badge climbing. There is no notification telling you that you broke anything.
The first thing you see when you reopen Oasa, after any length of time, is the Garden you have built. The unfinished work is one tap away, but it is not in your face.
This is a design choice that costs us nothing and gives users a real, ongoing thing: the ability to come back without dread.
If you would like to see the Garden in its various stages — from a small patch of soil to a more flourishing place — the Zen Garden page is the calmest page on our site, and probably the right next stop after this article.
Read next:
A. Boyes, "5 Quick Solutions When You're Overwhelmed by Your To-Do List", Psychology Today, 2022-03-14. https://www.psychologytoday.com/us/blog/in-practice/202203/4-quick-solutions-when-youre-overwhelmed-your-do-list ↩
O. Burkeman, Four Thousand Weeks: Time Management for Mortals, 2021. https://www.oliverburkeman.com/fourthousandweeks ↩
A quieter productivity practice
Oasa turns focused work into a Garden that grows over time and never shrinks. The Zen Garden page walks through what each stage looks like.
