Just because you failed to consider it explicitly, doesn't mean it won't tank your process.[^1] When designing a system, building a process, or planning a project implementation you typically need to [[RAID Log|identify dependencies]] - those things which your endeavor _depend on_ to be successful. These are the **known dependencies** of your process, aka their _explicit_ dependencies. In 100% of cases, given enough creativity, there are inevitably _implicit_ or _unstated_ dependencies that could tank your process. Each of these do, in a very real sense, add to your process's dependency chain, and [[Dependency Chains are the Victim of Statistics]]. # Rube Goldberg Example ![[Pasted image 20250302141420.png]] Known system dependencies _(treating each section as a whole)_: - Dominos 1, Ball track, Dominos 2, Light button ![[Pasted image 20250302144710.png]] **Implicit** system dependencies: - Transition _between_ each section ![[Pasted image 20250302181508.png]] This doesn't even consider implicit dependencies of the subcomponents themselves, such as the the chance you fail to place a domino where you intended it to be, which could happen any domino inside the subcomponents. # Handling The key[^2] is striking the right [[Balance]] of considering factors that may affect your process and not concerning yourself with those that are sufficiently unlikely to result in failure. You inevitably **have** to accept some risk that _something_ not factored into your analysis could affect results. This is the "_the building gets hit by a meteor_" contingency. It always could happen, factoring it into any practical [[Pre-mortem]] wouldn't result in any practical benefit. Accept it. You have to draw the line somewhere for your analysis. [[Data, Information, Knowledge, Wisdom Pyramid|wisdom]] is knowing when to draw the line where. Sometimes it's okay to consider the trajectory of a spherical chicken in a vacuum. **** ## Source - self ## Related [^1]: I'm using the term "process" for the sake of simplicity, but every time the word "process" is used you could instead substitute any of: System, design, project, service, etc. [^2]: as with so many things