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

Why can I build a team but not see what's broken?

You can run a team. You assign, you motivate, you follow up, and it works — for a while. Then something breaks again, in a slightly different shape, and you reach for the same tool: find the weak person, coach them, replace them. The problem returns anyway. That is the signal you keep missing. Here is the honest reading. You are good at managing people. You are not yet good at reading the system they stand in. A team is a fish, but dysfunction is the water — the incentives, the unclear ownership, the broken handoffs, the meeting where no decision is ever actually made. You keep examining the fish. This is learnable. Not through more willpower, and not by trying harder to motivate people who are already doing their best inside a bad structure. You learn it by asking a different question before you act: if I swapped this person out, would the same failure happen again? If the answer is yes, you have found the water, not the fish.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
Half of this is a concept you have never been taught — how to see a system instead of a person — and half is a habit you build only by practicing it on your own team.
How the two dials adapt to you →
What’s really going on

You are watching people when you should be watching the system around them. The late report, the dropped handoff, the burned-out star performer — these are not character flaws. They are what the structure produces. Stop diagnosing the person. Start diagnosing the path the work travels before it reaches them.

🔒 What you’ll build togetherUnlock by starting
A movePick one recurring failure. Write the name of the person you blame, then cross it out and write the rule, incentive, or handoff that let it happen.
A moveFor one week, log every complaint by where it happened — which meeting, which approval step, which handoff — not by who was involved.
A moveBefore you coach anyone, ask: would a different person, in this same seat, fail the same way? If yes, coach the seat, not the person.
A moveTrace one task from start to finish. Find the exact point where no one actually owns the decision. That point is your dysfunction.
A moveDescribe the broken system to someone above you using zero names. If you cannot do it without naming a person, you have not found the system yet.

What changes unlock by starting

  • You can name the structural cause of a repeated failure instead of the person attached to it.
  • You stop replacing people and watching the same problem return in a new seat.
  • You can raise a dysfunction to leadership without it sounding like you are blaming someone.
  • You build the habit of checking the system first, every time, before you judge the person in it.
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.