The plan wasn't the problem
A planner gets handed out. A to-do list app gets recommended. A weekly routine gets drawn up together, everyone agrees it's sensible, and within a week it's abandoned. The usual conclusion is that the person "didn't stick with it," as though the strategy itself was sound and the failure was theirs alone.
Almost always, the strategy was only ever solving half the problem. It handled the task, write things down, follow these steps, but assumed the mental work of running the strategy itself was free. It isn't. That surrounding work has a name: Cognitive Admin, the noticing, deciding, sequencing, remembering, switching, monitoring, interpreting and anticipating that has to happen around a task before the task itself can even start.
By the end of this module you'll be able to name the eight components of Cognitive Admin, recognise which one is quietly sinking a strategy that "should" work, and redesign the strategy to remove that admin rather than demanding more willpower to carry it.
The work around the work
Most strategies are designed around the visible task: fill in the form, pack the bag, send the email. What they leave out is everything that has to happen before and during that task for it to actually get done: noticing it needs doing at all, deciding when and how, sequencing the steps in the right order, holding it in mind long enough to act, switching attention onto it from whatever came before, monitoring whether it's going to plan, interpreting what an instruction actually means in practice, and anticipating what might go wrong.
None of this shows up in the plan itself. A to-do list app handles remembering, it doesn't help with deciding what belongs on the list in the first place. A routine handles sequencing, it doesn't help with noticing that today's version needs to look different. This is why the same strategy can work well for one person and fail completely for another: the admin cost isn't the same for everyone, even when the task is identical.
The practical shift this module asks for: when a strategy fails, the first question shouldn't be "why didn't they follow it," it should be "which piece of admin did this quietly assume was free."
Four zones, one diagnostic question each
Starting: noticing & deciding
Realising something needs doing, and choosing when, how and in what order. A "just start it" instruction assumes this is instant. For many people it's the single most expensive part.
Holding: sequencing & remembering
Keeping the right steps in the right order in mind long enough to act on them. Tools that store information (lists, apps) help here, but only once the first zone is already done.
Doing: switching & monitoring
Moving attention onto the task and checking, while doing it, whether it's still going to plan. Interruptions cost more here than they look like they should, because re-entry itself is admin.
Translating: interpreting & anticipating
Working out what a vague instruction actually means in this specific case, and pre-empting what's likely to go wrong. "Use your judgement" is an instruction to do more of this zone, not less.
A useful habit: before recommending or judging a strategy, ask which of these four zones it actually handles, and which it silently hands back to the person. A strategy that only covers "holding" will reliably fail for someone whose cost sits in "starting," however well-designed it is.
Worked example: a colleague is given a beautifully organised shared task tracker and still misses deadlines. The tracker solves "holding," it stores every task clearly. But nobody is adding new tasks to it as they arise, that's "starting," the noticing-and-deciding zone, and it was never assigned to anyone. The fix isn't a better tracker, it's building a short daily or weekly moment where "what needs to go on here" gets asked out loud, because that's the zone actually failing, not the one the tool was built to fix.
Applying it in practice
Case 1 — A student is told to "just write a to-do list every morning." They agree it's a good idea, do it for three days, then stop, despite the list itself being well organised when they do write one.
What's most likely actually failing?
Case 2 — An employee is given a project-management app to "get more organised," but their output doesn't improve; tasks still get missed.
What's the most useful next diagnostic step?
Reflect before the assessment
Think of a strategy you've recommended, or been given, that looked sensible but didn't stick. Without naming anyone:
- Which of the four admin zones did it actually cover?
- Which zone did it quietly leave for the person to handle alone?
- What's one small change that would remove that admin instead of asking for more effort to carry it?
0 of 80 words written
This reflection isn't saved by the page. It stays on your screen only — copy and paste it somewhere safe (a note, your CPD log) before you move on if you'd like to keep it.
Check your understanding
6 questions. A score of 5/6 (83%) or higher unlocks your printable certificate. You can retake it as many times as you like.
Generate your printable certificate
Type your name exactly as you'd like it to appear. Your printable certificate is locked to this purchase — it can only be generated once per course.

This certifies that
has completed the CPD module
Cognitive Admin: Why Some Strategies Fail
Use your browser's Print (Ctrl/Cmd+P → Save as PDF) to save or print this printable certificate.