Podcast: Play in new window | Download
Subscribe (Free) More
A bad week in your productivity system is like a multi-car accident on the highway, where one thing goes wrong and the damage quickly compounds far beyond the original problem.
It often takes only one point of failure—like stopping file organization or email responses—for everything else to begin cascading behind it.
That is why a good productivity system should not merely help you when things are going well. It should be built to survive when things are not.
In an actual driving emergency, your goal is not to hit the car in front of you head on. If you can, you swerve. You soften the blow. You try to create a glancing impact instead of a direct collision. The same is true in your productivity life. When a bad week begins, the goal is not perfection. The goal is to reduce the downstream damage.
One way to do that is with kinder self-speak. Another is to have reset points built into the week. I have spoken before about the Day Reset (69) as one way to interrupt the slide and reorient yourself. More broadly, resilience in a productivity system comes from having small checks and recovery points throughout the system so that one failure does not become five.
For me, the GTD Weekly Review is one example of that kind of resilience (116, 117). But even if you are not doing a full Weekly Review, you can still build in checkpoints every few days. Review your calendar. Look at your sent email folder. Check your downloads folder on your work computer. Review your browser or download history. These are small touchpoints, but they help you see where things may be drifting before the week gets away from you.
So perhaps the question to ask is this: what does a bad week look like for you? And what checkpoints would help you gradually steer away from it? Usually, it is not one big heroic act that saves the week. It is a handful of small corrective behaviors that keep the system from spiraling.
Build your system not just for your best weeks, but for your worst ones too.