Ambiguity kills Projects (the 1st Law)

Not so clear
Ambiguity is the enemy of project success. Its one of the first things I instruct new project managers on. I call it the First Law in project management.
Its not hard to find ambiguity in projects. Look closely at the objectives, the requirements, the scope definition and the schedule. Are they each as clear and as accurate as they can be? Most importantly, do we know what “done” really looks like? This is crucial. (Glen Alleman’s prolific and consistently excellent blog at Herding Cats has a host of outstanding posts on this – check it out). Each ambiguity is a potential source of conflict, rework and failure.
Clarity Checks
The antidote to ambiguity is clarity – here are a few items that must be on the ‘Clarity Checklist’:
- Are deliverables defined with clear boundaries?
- Are there detailed and explicit descriptions of inclusions and exclusions?
- Are completion and acceptance criteria clearly stated for each deliverable?
- Do we know what “done” looks like for each deliverable?
- Are tasks defined at an appropriate level of detail?
- Are most tasks in the range of 4-40 hours of duration? (a useful guide for most projects)
- Are task outputs tangible?
- Have the outputs been agreed upon by their owners and dependents?
- Is progress tracked at task level?
- Is evidence of progress validated before being reported upward?
Leaving ambiguity unchecked simply increases project risk. The pursuit of clarity isn’t always popular because it makes people have to think ahead a little harder. But its necessary. So put on your flak jacket and go on a mission – seek out ambiguity and destroy it… before it does some damage.
(See all 5 Laws summarized in The 5 Laws of Effective Project Management)