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

Why do I have to keep fighting for users everyone else forgets?

You already know how to build it right. That was never the hard part. The hard part is doing it again, in a culture that treats it as optional, while you carry the weight of remembering for everyone who didn't. Notice what you're actually tired of. Not the work — the arguing. You've made yourself responsible for other people's priorities, and that is not yours to carry. Their indifference is not within your power. Your next commit is. So stop measuring your effort by whether you changed their minds. Measure it by whether the thing you built works for the person who needs it, regardless of who noticed.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The technical knowledge is already theirs; what they need is a sharper distinction between what's controllable and a concrete way to stop fighting battles that drain them.
How the two dials adapt to you →
What’s really going on

You do not need to win the fight. You need to stop treating it as a fight. Build accessibility into your own process before anyone asks — then the only person you're convincing is yourself, and that argument you can actually win. The weariness comes from demanding others care. Demand only that your own work does not depend on it.

🔒 What you’ll build togetherUnlock by starting
A moveBuild the accessibility check into your own workflow at the design stage, before anyone can ask you to skip it — make it structural, not optional.
A moveStop arguing for empathy. Say 'this is in the spec,' not 'this is the right thing to do.' Specs get approved. Feelings get debated.
A movePick one pattern or component this week and make it the accessible default for your whole team, not a special case you defend each time.
A moveWrite two short lists: what you control — your code, your reviews, your defaults — and what you don't — their budget, their timeline, their priorities. Stop spending energy on the second list.
A moveFind one person who already agrees with you and hand them a piece of this work. You do not have to be the only one who remembers.

What changes unlock by starting

  • You spend less energy convincing people and more energy building the thing itself.
  • Accessible patterns become the default in your work, not a request you repeat every project.
  • You stop carrying this alone because you've built allies, not just arguments.
  • The next project starts from a higher floor — because you set it there before anyone asked.

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.