In healthy organizations there are two types of people or groups that can stop a project. The first is the sponsor, client or steering group and the second is a expert group or individual who is charged with making sure the project is going in the right direction and is complying with policies, regulations and best practices.
When the sponsor, client or steering group stops the project it is usually stopped for good – "killed" or postponed until higher priority work is completed. When an expert, architecture group or other gatekeeper stops a project it is often not a kill or postponement. It is a pause during which the conditions that caused the stoppage are understood and cleared and the project set on course again.
Of course stopping a project is risky, particularly if you are not an executive or client. In some environments there is a process definition that allows for projects to be stopped by technical experts and project managers. In many of these there is an unwritten rule – never do it, even if it should be done. It's just too political; someone will hate you for it. In other environments, there is no provision in the process for anyone to stop a project. In either case, projects become like undying vampires sucking the blood form the organization.
Stop the LineIn quality manufacturing cultures workers can stop the assembly line when they see something wrong. In the Toyota Production System Jidoka is one of two main pillars. It means that people or machines can stop production lines in the event of problems such as equipment malfunction, quality issues, or late work. Jidoka helps prevent the passing of defects, helps identify and correct problem areas using localization and isolation, and makes it possible to "build" quality at the production process.
We need to apply this principle to project work.
Stopping a project for technical or quality reasons as opposed to business reasons a project does not mean killing it is a radical move since it means having project personnel stop work and thereby delay progress on the project. If they are full time the budget is affected; the meter is running.
Why would anyone want to do that? The answer is simple; to draw attention to something serious and make sure it is addressed quickly.
For example, in a technology based project a group responsible for making sure that security and other operational standards are met needs the power to get the project manager or others to deliver information and sit for technical reviews early in project life. Short of the ability to stop the project the review group often lacks the ability to get a resistant PM to cooperate or to take negative findings seriously.
How do we overcome the cultural and personal barriers to doing this? We make sure that everyone understands their responsibility to say something if they see something. We include appropriate gates in the project. We make sure that people are not afraid of repercussions if they take their responsibility to heart and actually pull the emergency stop chord.
Don't forget to leave your comments below.