Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why does the maintenance side of cleaning still confuse us?

You know how to clean. That part is not the problem. What confuses you is the rest of it — who restocks, who checks what, how often, and what happens when someone forgets. That is not a cleaning skill. That is an organizing skill, and no one taught it to you. Right now the system lives in someone's head, or in several heads that don't agree. That works until it doesn't — until the person who remembers is sick, or busy, or gone. Then the whole thing falls apart and it looks like laziness, when really it was never built to survive without one person's memory. You do not need to become more organized people by nature. You need a document, a short one, that any of you could read and know exactly what to do. Build that, and the confusion ends. Don't build it, and you will keep having the same argument about whose fault it was.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The team needs a clear method for turning tasks into a system, but the real block is avoidance and diffusion of responsibility, which coaching must confront directly.
How the two dials adapt to you →
What’s really going on

Confusion here is not a lack of skill. It means no one wrote the system down. The fix is not to try harder — it is to build a list, name an owner for each task, and write it where everyone can see it. Choose to do that this week, together.

🔒 What you’ll build togetherUnlock by starting
A moveSit down together and list every task that repeats — not just 'clean,' but restock, inspect, order, schedule, check.
A movePut one name next to each task. Not 'we.' One person.
A moveWrite the whole thing down in a place everyone can see, not in anyone's memory.
A movePick one day a week to check what broke, and fix the system — not the person.
A moveWhen a task gets missed, ask what in the system failed before you ask who failed.
PractiseMap the System · a Pod of 4 · 30 min

What changes unlock by starting

  • A written list exists that any team member could follow without asking questions
  • Each task has one clear owner instead of vague shared responsibility
  • Fewer arguments about who should have done what
  • The team catches breakdowns in a weekly check instead of after something fails
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.