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

Why doesn't anyone notice the documentation I keep the team running on?

You keep the documentation. Everyone uses it. No one mentions it — until something breaks, and then they ask why it wasn't clearer. This is not unfair. It is simply how maintenance work gets noticed by people who are not trained to look for it. The invisibility is not a judgment on your worth. It is a fact about attention. Attention goes to fires, not to the walls that stop them. You cannot make your teammates notice. You can make sure they know. Stop confusing being essential with being seen. Those are different things. Only one of them is yours to arrange. Choose it.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The problem isn't a knowledge gap — it's inaction, so the page leans toward coaching, with just enough reframing to justify the shift.
How the two dials adapt to you →
What’s really going on

The work is invisible because it works. No one praises a bridge that never collapses. Your resentment is real. But no one will solve it by finally noticing you. You solve it by naming the work yourself, plainly, to the team. Choose to speak before you choose to resent the silence.

🔒 What you’ll build togetherUnlock by starting
A moveSend a short weekly note naming exactly what you fixed or clarified — not as a complaint, as a record.
A moveAt the next team meeting, say plainly: 'I updated X, here's why it matters.' Do not wait to be asked.
A moveAsk directly that this work count in your reviews. Do not assume anyone remembers to count it.
A moveWhen resentment rises, ask yourself: did I ask to be seen, or did I only expect it?
A moveTeach one teammate to maintain a piece of the documentation. This spreads both the visibility and the burden.
PractiseName the Invisible Work · a Pod of 4 · 30 min

What changes unlock by starting

  • You stop waiting for credit that was never coming unasked.
  • Your team starts seeing the documentation as work, not as weather.
  • Your resentment shrinks, because you acted instead of waiting.
  • The maintenance burden spreads, so you no longer carry it alone.

Related problems

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.