Dependencies and Sequencing · Product Fluency

Dependencies and Sequencing · 3 min

Situation

Every team is busy; the launch is still blocked.

Frontend is nearly finished, but the vendor has not approved API access. The data migration also depends on a schema decision nobody owns.

Progress within each team does not establish progress along the path to a usable release. Dependencies connect the schedule.

Mental model

Model work as a network.

Identify what must finish before another activity can begin. A critical path is the longest dependent chain that determines the earliest completion under the current plan.

Backend, frontend, design, legal review, vendors, data, and migration can all lie on that path. The bottleneck is not necessarily the largest engineering task.

Example

Move an uncertain external dependency early.

If vendor access takes an uncertain two to four weeks, request it before polishing the interface. A mock API can support parallel UI work, but real integration still needs validation.

Define a contract and realistic examples so parallel work does not diverge. Keep time for discovering mismatches when the real service arrives.

Failure case

Adding estimates as though everything is sequential.

Some tasks can run in parallel; others cannot. Simply summing every estimate can overstate duration, while treating all work as parallel can understate it.

Ask about shared people, review capacity, and integration work. One specialist needed by three tasks creates a resource constraint even if the tasks are logically independent.

PM decision

Make the dependency actionable.

For each important dependency, name the owner, needed-by date, expected output, uncertainty, and fallback. Escalate while options remain, not only after the deadline passes.

If a dependency slips, consider changing sequence, narrowing scope, using a temporary path, or changing the date. Explain which outcome each option preserves.

Remember this

Manage the path to value, not a list of busy teams.

A delivery plan should expose the dependent chain, uncertain handoffs, and alternatives. Progress is useful when it moves the release closer to a complete outcome.