Comment from Kevin to yesterday’s post Mine to Keep.

Comment:
I am interested in how you made the connection between due date and time span. Just because a deliverable is required later in the process, does not necessarily mean that it has a longer time span or involves more strategic thinking.

For example, when building a machine or facility, the design (site layout, engineering drawings etc.) are needed first while the finishes (paint, tile etc) could be required last. Yet it may take years of coordinating stakeholders, engineers and architects to develop the design vs. a few months of focus groups etc for the finishes. In this scenario, I would rather handle the design and delegate the finishes.

Therefore, it would seem as though the “what by when” might be a bit simplified and that we should rather focus on “what and how long” in order to differentiate between the due date and the time span.

Response:
Thanks for the distinction. Time Span is measured from the starting time for the task and indicates the time during which discretionary decisions are made to achieve the goal. Your example of the construction project is correct. Due date, as the measurement for Time Span, only works when the start time for everything is NOW. You are correct in measuring the Time Span from when the tasks are actually assigned, though the due date may be late in the overall construction process.