DRI Canada Fall Symposium ยท November 12, 2026

What Your Dependency Map Isn't Showing You

Take the dependency challenge back to your team. Use the one-page worksheet to explore what could stop one critical service, and what you would need to recover it. Download the worksheet and session slides below.

Dependency challengeOne-page worksheet to use with your team Get the worksheet Session slidesWhat Your Dependency Map Isn't Showing You Get the slides

Run the challenge on one service

  1. Pick one critical business service and note its recovery time objective (RTO).
  2. Sketch its dependencies: technology, people, third parties, and the tools and access needed to recover it.
  3. Choose one dependency and assume it is unavailable. What stops? What degrades? What keeps working?
  4. Examine the recovery path. What must be available first? Does the backup depend on anything affected by the same failure, and can it carry the required load?
  5. Identify what could prevent recovery within the RTO. Record the assumptions you need to verify and who can verify them.

Start with what you know. Then set aside 90 minutes with the people who understand how the service runs and how it is recovered to work through the gaps.

I'm Denys Fiialko, founder of Stetora and creator of Failcast, a tool for mapping dependencies and simulating failures.

Did the exercise reveal a dependency or recovery assumption you hadn't considered? I'd like to hear what you found: denys@failcast.io