Skip to main content

Course · IV — Action management

When the system breaks: how to restart

After a holiday, an illness, an overload or a missed week: a restart protocol, a grid to tell a system problem from an energy problem, and when to ask for help.

Full-course lesson IV — Action management

Preview

A productivity system always breaks eventually. A week of holidays, a cold that lingers, an urgent project that swallows everything: the task list fills up with things you will not do. The usual reflex is to rebuild everything in one evening. That is generally the worst option, because it repeats the effort that broke the system in the first place.

This lesson offers a different approach: a short restart protocol, a grid to tell whether the problem comes from the system or from your energy, and markers for when to talk to someone.

When the system breaks, your first impulse is to rebuild it entirely: a new tool, a new method, a new "clean" list. The problem is that this rebuild requires exactly the energy you are missing. You end up with a more beautiful system that is just as fragile.…

In the full lesson

  1. 1 The trap: rebuilding everything from zero
  2. 2 The restart protocol
  3. 3 System or energy: a simple grid
  4. 4 When to talk to someone
  5. 5 Put it into practice

The course opens soon

Sales are not open yet. Meanwhile, Module I is entirely free, and so is the 10 Windows settings guide.

Get notified when it opens

Leave your email: you will get the CMDglows newsletter, including the course opening announcement.

Already bought it? Open the full lesson

What the purchase unlocks

  • Every lesson in modules II to IX
  • Both the English and French versions
  • Reading in your private area, on desktop and mobile