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

Why do the hard cases still beat me when easy ones don't?

You can plan for most patients now. That is real progress — do not dismiss it. But you already know the easy ones were never the test. The complex cases are. Here is what is happening. You learned a plan that works for the common case, and you run it automatically. When the case doesn't fit, you run the same plan harder. More effort, same method. It still doesn't land. This is not a sign you lack talent. It is a sign you have one tool. The work now is not to try harder at the tool you have. It is to build a habit: notice when the tool doesn't fit, and stop before you force it.

◆ 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
You already have the facts; what's missing is the habit of catching yourself mid-plan and switching approach, which is built through practice, not instruction.
How the two dials adapt to you →
What’s really going on

The resistant cases are not failures of skill — they prove your method only covers what's simple. You built one process for the common case and run it everywhere. Build a second process for what doesn't fit: slow down, name the difference, and work from there.

🔒 What you’ll build togetherUnlock by starting
A moveBefore planning the next hard case, write three ways it differs from the ones you solve easily.
A moveName the assumption you made before you even looked closely — then test whether it's true.
A moveSet a hard stop: if your first plan doesn't fit in ten minutes, call it a different kind of case and start fresh.
A moveKeep a running list of your last five resistant cases. Look for what they share — that's your real curriculum.
A moveWhen a case beats you, write the exact point your plan broke — not 'it was hard,' the precise moment.

What changes unlock by starting

  • You stop treating resistant cases as failures of effort and start treating them as a different category.
  • You build a second process — not a harder version of the first — for cases that don't fit the pattern.
  • You catch yourself forcing the standard plan onto an unusual case earlier each time.
  • You keep a working record of what actually makes a case resistant, instead of guessing from instinct.
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.