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

Why does our team stall on problems that cross disciplines?

You built real skill. You can take separate systems and make them work together. That is no small thing. But now a problem shows up that doesn't live inside one discipline. It bleeds across your team's boundaries. No one owns it fully. Your group, trained to solve things cleanly, starts grabbing for answers before anyone has named what kind of problem this actually is. That is the trap. Not a skill gap. A naming gap. Here you will learn to spot an unnamed problem, and you will practice naming one — together — before you try to solve it.

◆ 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 team needs a little framework to recognize an unnamed problem, but the real change comes from repeated practice naming one together.
How the two dials adapt to you →
What’s really going on

You are not failing at skill. You are reaching for a solution before your team agrees on what kind of problem you are holding. Emergent problems cross the lines your disciplines were built to defend. Stop solving. Choose, together, to name the problem's shape first — that is the actual work.

🔒 What you’ll build togetherUnlock by starting
A moveWhen a problem crosses disciplines, stop the group and ask what kind of problem this is before anyone asks how to solve it.
A moveWrite the problem on one shared page before a single solution gets proposed.
A moveHave one person argue the problem from each discipline's view, then find where those views conflict.
A moveSet a 10-minute timer. Name the problem's shape fully before anyone speaks a fix.
A moveAfter you act, go back and ask whether you named the right problem at all.
PractiseName the Problem First · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team catches itself reaching for solutions too early — and stops.
  • You build a shared habit of naming a problem before attacking it.
  • Cross-discipline problems start to feel like a known shape, not chaos.
  • You waste fewer cycles solving the wrong problem well.

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.