Talk it through with Aurelius
LibraryAureliusThe problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why do hidden supplier risks still catch me off guard?

You built a process. You check the risk boxes. And still, something breaks that was never on your list. That is not bad luck. It is a blind spot, and blind spots can be named. Here is why it happens. Your assessment looks at the supplier standing in front of you. It does not look at what that supplier depends on — the one factory, the one software tool, the one person who knows how the process actually works. Those things stay invisible until they fail. The fix is not a smarter spreadsheet. It is a habit. Ask what this depends on. Then ask again, one layer past where you'd normally stop.

◆ 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 know how to assess risk; what's missing is the discipline to dig one layer deeper, so this page leans toward action over theory.
How the two dials adapt to you →
What’s really going on

You are not missing risk because you are careless. You stop asking questions at the first visible layer. Every supplier depends on other suppliers, tools, and people you never named. Choose to ask one more question than feels necessary, every time, and write down what you find.

🔒 What you’ll build togetherUnlock by starting
A moveAsk each key supplier directly: what single thing, if it failed, would stop you from delivering to me? Write down their answer.
A moveMap one layer past your own vendor list — your supplier's supplier, their key tool, their one indispensable person.
A moveFor your three most critical suppliers, ask what happens if their backup plan also fails.
A moveBuild a short list: if this breaks, who do I call in the next hour? Test that list before you need it.
A moveReview this list every quarter, not only after something breaks.

What changes unlock by starting

  • You stop being surprised by failures you could have named in advance.
  • You have a written list of real dependencies, not assumed ones.
  • You know exactly who to call within the hour when something breaks.
  • Your risk process reaches one layer deeper than it did before.
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.