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

Why can't I get my team to fix tech debt, not just ship?

You see the rot before anyone else does. That is your skill. But seeing it is not the same as proving it, and until you prove it, your warning sounds like preference against their urgency. This is not a fight about code. It is a fight about what gets trusted — your judgment, or the feature deadline everyone already feels in their bones. You will not win that fight with a better explanation. You win it with a number someone else already believes. You do not control the roadmap. You do not control whether leadership listens. You do control what you bring into the room, and whether your team names the cost together instead of leaving it to you alone.

◆ 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 team already understands the technical reality; what's missing is the discipline to turn it into a shared, measurable case — that's mostly practiced behavior, not new information
How the two dials adapt to you →
What’s really going on

You are not losing a technical argument. You are losing because you bring opinion where others expect cost. Stop saying 'tech debt.' Name what it already breaks — hours lost, bugs shipped, work redone — and bring one fix, not a list. Choose the smallest cut that pays back fastest.

🔒 What you’ll build togetherUnlock by starting
A moveTrack the cost of the debt for two weeks — hours lost to bugs, delays, or rework it caused. Write the number down.
A moveBring one fix, not a list. Name the smallest change that pays back the fastest.
A moveAttach the fix to a feature already approved. Say: we fix this while we build that.
A moveAsk the team, out loud, what breaks next quarter if nothing changes. Make the cost shared, not yours alone.
A moveSet a fixed slice of every sprint for debt work, so it stops being a fight you must win each time.
PractiseCost Ledger · a Pod of 4 · 30 min

What changes unlock by starting

  • The team argues from a shared number, not your opinion
  • Leaders see the cost in terms they already track — time, bugs, delay
  • Fewer repeat debates about the same debt every planning cycle
  • A standing block of time protected for debt, agreed once instead of fought for each sprint
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.