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

Why Do New Threats Still Get Past Our Team?

You and your team can spot most threats before they land. The ones that get through aren't more dangerous — they're simply unfamiliar. You're hunting for patterns, and novelty has no pattern yet. This isn't a failure of effort. You're good at your work. But a team's shared instinct can become a shared blind spot. You all learned to see the same threats the same way, so you miss the same new ones together, at the same time. The work now isn't to watch harder. It's to change what you watch for, and to make each other responsible for naming what feels strange — even before anyone can explain why.

◆ 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 insight is short — pattern recognition explains the gap — but closing it takes sustained practice as a group, not more explanation.
How the two dials adapt to you →
What’s really going on

Your eyes are trained on threats you've already seen. A new one wears no familiar shape, so you look past it. The fix isn't sharper eyes — it's a different question. Stop asking 'have I seen this before?' Ask, together, 'what here doesn't fit anything we know?'

🔒 What you’ll build togetherUnlock by starting
A moveName the assumption behind your last catch: what did it look like that this new one doesn't?
A moveAssign one person each week to argue for the thing nobody flagged.
A moveAfter every miss, write down what didn't match any pattern you had. Keep a list of 'unlike,' not 'like.'
A moveIn review, ask 'what would fool us' before you ask 'what did we catch.' Rehearse the failure, not the win.
A movePick one signal this month that has no category yet. Decide together, out loud, how you'll treat it.
PractiseThe Unlike List · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team catches threats that don't resemble anything in your playbook.
  • You build a shared habit of naming unease before you can justify it.
  • Reviews shift from congratulating catches to hunting blind spots.
  • The team starts treating discomfort as data, not noise.
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.