Most project managers approach task dependencies as causal. For example, the printing of a brochure cannot happen before the design of the brochure is approved. Likewise, the design of the brochure cannot be approved before final layouts are distributed to project leaders. In a tightly woven, traditional project, each task relies on a previous task’s completion before it can begin.
However, in today’s distributed work environment, many organizations can leverage the power of multiple locations, outsourced labor and highly productive team members to take on multi-threaded projects. In this kind of example, the layout of a brochure can be designed using placeholder text at the same time that copy is being written. Project managers working in this kind of environment can use charts or spreadsheets to break out tasks and chains that can be performed independently of each other, reducing the number of dependencies within a project. This method of planning substantially lessens the risk that an entire project can become delayed due to a single missed deadline.
Tom Olzak explores the benefits of detailed task dependency mapping in his article, “How to Effectively Review the Structure and Sequence of Your Project Tasks.”