The project workaround is the interim solution that projects put in as a ‘quick-fix’ to address symptoms of project failure.
What is a project workaround?
The workaround is a set of activities that will alleviate the impact of the symptoms and will enable the ‘immediate’ problem to be overcome [temporarily].
If you are of the PMP camp then a workaround would be ‘a solution to an unidentified problem’.
Invariably the workarounds put in are not necessarily efficient or robust primarily due to the speed of the need for their implementation.
Workarounds are usually meant to be temporary which should be relied upon for a short time only.
Evolution of the workaround?
The workaround should be in place only until a more permanent resolution can be found.
Identify the cause or causes of the symptoms. A solution put in place that eradicates the causes and hence resolves the need for any workarounds.
Example of a workaround?
Imagine a leaking pipe. The symptom is the dripping water where the cause is the break in the pipe.
To this a workaround would be a bucket that catches the drips. It will resolve the immediate problem but it has a fixed life as the bucket will overflow.
The problem with Workarounds?
If you end up running with too many workarounds in place you run the risk of workarounds failing when you least need it.
This could cause bigger problems for you to address at a time not of your making
Always aim to reduce the number of workarounds you have to run with to reduce your risk of project failure workarounds causing your project to fail.
The solution to Project Workarounds?
Avoid workarounds being implemented by addressing the root cause. This will remove the symptoms from occurring.
The root cause is what is driving the failure demand and as such is a big draw on your precious project resources.
In the leaking pipe example, the cause of the break will be the root cause you want to address to stop it being able to happen again.
Read about Cause Capturing which is the next step in foiling project failures.
