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

Why do people problems resist the fixes that work on everything else?

You have made your systems efficient. Inputs, outputs, bottlenecks removed. Then a disagreement between two colleagues, a stalled decision, a quiet resentment — and none of your tools apply. This is not a gap in your skill. It is a different kind of problem, and you have been solving the wrong one on purpose, because it was easier. Human friction cannot be optimized away because people are not variables you control. They have their own judgments, and those judgments will not align with your process no matter how well you design it. The work now is not a better system. It is you, choosing to ask instead of assume, to listen before you diagnose, to treat the friction as information rather than error. You are not alone in this — your pod faces the same wall. Use them. What one of you cannot see in a colleague, another will. This is precisely why you do not do this work alone.

◆ 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 concept (systems vs. people, judgment vs. optimization) is simple to state but hard to practice, so most of the value is in repeated, coached action with the pod.
How the two dials adapt to you →
What’s really going on

Because a person is not a process. You cannot flowchart a will that is not yours to command. The skill here is not optimization — it is judgment under uncertainty, practiced with others who see what you cannot. Stop trying to engineer people. Start building the habit of asking them.

🔒 What you’ll build togetherUnlock by starting
A moveName one human-factor problem you have been treating as a process problem. Say it plainly to your pod this week.
A moveBefore you propose a fix, ask the person involved one honest question and wait for the full answer.
A moveIn your next pod session, each person names a colleague whose behavior confuses them — and the group guesses three possible reasons before anyone diagnoses.
A moveChoose one recurring friction point. Do not solve it. Observe it for one week and report only what you saw.
A moveWhen you feel the urge to optimize a person, stop, and ask instead what they need that you have not offered.
PractiseName the Friction · a Pod of 4 · 30 min

What changes unlock by starting

  • You catch yourself trying to systemize a person, and stop.
  • You ask one real question before proposing one more fix.
  • Your pod names the same friction differently — and you see your blind spot.
  • You trade the comfort of control for the harder, truer work of understanding.

Related problems

The same struggle, seen by other coaches
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.