There is a particular conversation that happens in project post-mortems with remarkable consistency. Someone identifies the thing that went wrong, traces it back to its origin, and the room goes quiet for a moment because everyone realizes that the origin was visible months earlier. It was not hidden. It was not unpredictable. It was simply not treated with the urgency it deserved because at the time it did not feel like the most pressing thing on the list.
That origin is almost always a dependency.
What a Dependency Actually Is
A dependency is any condition that must be true before something else in the project can proceed. Some dependencies are obvious and operational. You cannot move into the space until the lease is signed. You cannot ship the product until the packaging is ready. You cannot launch the website until the developer has finished building it.
These are the dependencies that make it onto the project plan. They are sequenced, tracked, and managed. When they slip they are noticed.
The dependencies that cause the most damage are a different kind. They are the relationships, approvals, regulatory clearances, and external commitments that sit at the foundation of the project's entire logic. They are not tasks. They are preconditions. And because they do not look like tasks they rarely get the same disciplined attention.
The supplier relationship that the entire production model depends on. The key hire whose expertise is central to the delivery model. The regulatory approval whose timeline is outside the owner's control. The anchor client whose commitment would validate the business case for everything that follows.
Each of these is a dependency. Each of them has a lead time. And each of them, if it fails to materialize on schedule, has the potential to delay or derail not just one milestone but every milestone that follows it.
The Question Worth Asking Right Now
For whatever project you are currently planning or executing, there is a question worth sitting with honestly.
If one thing failed to come through — one relationship, one approval, one commitment from an external party — which one would do the most damage to the project's timeline and viability?
That thing is your critical dependency. It is the one that deserves the earliest attention, the most proactive management, and the clearest contingency thinking.
The owners who identify it early and treat it accordingly tend to find that it is manageable. The ones who identify it late tend to find that it was the thing that determined the outcome.
Name it before it names you.