I have been involved in evaluating distracted driving programs for transportation workers. While working on the evaluations I developed an interesting way to understand how programs are acting and what they are doing. The method is based on a few principles, one set focusing on the nature of timelines and schedules, and the other on data collection.
Timelines and schedules
Timelines and schedules matter. These documents are constructed to meet a few objectives. They have to:
- Provide a reasonable plan whose tasks can be executed.
- Represent a reasonable correspondence between budget and work.
- Satisfy customers desires for when the work will be completed, and for how much.
In a sense there is a conflict between the first two objectives and the third, resulting in overly optimistic assessments of budgets and timelines. That’s the direction of the bias in our estimates. Continue reading “Timelines, Critical Incidents and Systems: A Nice Way to Understand Programs”