Public transport is generally one of the more notorious services for running late, we are all used to waiting for buses, trains, and planes.
There can be a number of reasons why services run late – mechanical trouble, unexpected demand, or incorrect timetabling. While fingers are often pointed at operators, this is not always the case. The Greater Wellington Regional Council has recently adjusted some of its bus timetables to Wellington’s northern suburbs, in some cases making journeys 23 minutes longer.
Programming accuracy and delays to completion are also a common feature of a number of construction and technology projects. There are often difficulties understanding the effect that particular delays will have on projects and anticipating ways to reduce the delays and manage project stakeholders.
To a large extent this relies on the accuracy of information from everyone involved in a project. There has to be accurate information and an environment that supports open discussion. The adjustment made in Wellington is a good example of where accurate information has been used to adjust expectations. While the Council may have wanted to maintain the old timetable, clearly the journey simply takes too long.
Developing an environment of open, real-time reporting for projects could go a long way to reducing disputes that most projects face. There can be significant debate about how best to create that relationship – particularly whether a carrot or stick is better.
What do you think?