Enforcing Project Consistency Using Checklists

January 13, 2010 | Author: PM Hut | Filed under: Communications Management, Project Management Best Practices

Enforcing Project Consistency Using Checklists
By Zenkara

To bring some structure and consistency to projects (and business processes in general), audits or QA checks/gates are often performed to assess current practices and to enforce consistency. But in one of the great ironies, it is often necessary to not perform audits to measure compliance and instead use audits to understand current issues and build credibility. Simply leaping into measuring everything e.g. do we have at least 76% compliance, we need to first address the major problems.

To build trust and credibility with operational and project staff, we first need to provide support.

Using checklists as a basis for providing a tool to project staff is often a good start for improving. Not for people to actually tick off – though they can certainly do that if they want. We need to use checklists as a window into our (increasingly) complex business processes and methodologies.

Most methods are neither read nor understood. If you have a 400 page methodology, you can be pretty sure no one but the author and QA has read it – let alone understands it. Project staff want to get started right away and not get bogged down in what they see as theory. They’ll do what they need to get the job done.

By using a one page checklist we can start to gain some traction by:

  • Having a simple device (checklist) that shows what needs to be done at an absolute minimum – and isn’t that what many PMs want!
  • Using the checklist to ensure staff are focused on what needs to be done

So it actually works well both ways.

One thing though – don’t assess percentages too early (say within the first year) as you will experience a lot of pushback and resistance – and the checklists won’t get used and you’ll be back where you started.

Once everyone is using the checklists and you have some consistency in place (dare I say it, institutionalized) you can start to look at measures.

But in the mean time, just use a Red (Bad)/Amber(issues but manageable)/Green(OK) traffic light indicator.

If there are lots of good things happening, you might consider a gold/star. PMs always get blamed when things go bad, thanked when things go OK, but rarely thanked when things are well ahead.

So just write a few checklists to drive some change and see how it works. You might be surprised.

Zenkara focuses on streamlining and deploying business processes and quality systems and accelerating decision making through OODA (Observe, Orient, Decide, Act) and metrics systems. Zenkara is located in Brisbane, Australia.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

1 person has left a comment

I agree that checklists are a cheap, easy and pragmatic way to improve project consistency, and often under utilized.

You can further enhance the usage of checklists by including hyperlinks to boilerplate material or templates for any artifacts required to complete each item in the list. Since many PM’s often don’t know where to find such Best Practice materials (so end up creating their own and reinventing the wheel), this can often represent an additional step forward in productivity.

As with your caution about assessing metrics too soon, one should also allow the Best Practice material to initially be used as “voluntary” a starting point for PMs who are then free to modify them for their own needs. Only as maturity builds in the materials and PMs gain confidence that they are useful and relevant, should one start to enforce compliance to the material.

JohnD wrote on January 13, 2010 - 8:43 am | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories