Tuesday, February 22, 2011

It’s not my problem

One of the major challenges of a project manager, or any manager, is determining is who owns the PROBLEM. By default, the PROBLEM is owned by the person with the biggest guilt complex (aka ME)…and not the person who can actually address the PROBLEM. No matter how hard the current PROBLEM owner tries to get others to help resolve the issue, the PROBLEM tends to bounce right back, as if it was attached like a paddleball. The end result: the PROBLEM is not effectively addressed and blame and future problems have a greater tendency to be associated with ME.

Ok, rant over, now some definitions:
  • The PROBLEM – anything that went wrong
  • ME – the Person who always seems to be working through the teams problems

Without trying to over-define everything, let’s just say that the PROBLEM is something that needs to be corrected, is understood enough to know who it should be assigned to and is of a severity enough that it needs to take priority. Any additional information is…well…nice to know.

An effective process would be:
  • Centralizing problem reporting – an excel sheet to some sophisticated bug tracker
  • Problem Triage – someone (ME) needs to determine how severe the issue is and WHO the PERSON is that is most associated with it and can resolve it
  • Assign (you need authority) to the PERSON
  • Follow up and make sure the problem gets attention and resolved

Seems simple, but if you ASSume people understand the process and will voluntarily follow it…well let’s just not ASSume, let’s communicate to the team and to management and let us ASSume that we have the authority to push the PROBLEM to the right PERSON….as difficult as assigning to the right person is, the actual resolution is based on the PERSON’s focus and attention to the PROBLEM. The easiest way I’ve found for this to happen is to send out a daily/weekly report of all active PROBLEMS, who they are assigned to and HOW LONG they’ve been out

standing. Peer pressure and Management pressure can then take it’s course.

4 comments:

  1. Great blog with some interesting insights, ill be followign this blog as i am currently enrolled in a project management classin college.

    ReplyDelete
  2. If an employer has to choose between a person of high technical caliber and someone with PMP as manager, he will definitely select the former. Life in the early days of liberalization was simpler For more information go through the following website www.knowledgewoods.in

    ReplyDelete
  3. If an employer has to choose between a person of high technical caliber and someone with PMP as manager, he will definitely select the former. Life in the early days of liberalization was simpler

    PMP certification

    ReplyDelete
  4. Hi Meade,

    I've always found that establishing an agreed issue log reporting process early in the project life cycle beneficial.

    This way you can be very clear about the magnitude of the current problem, the downstream impacts, who raised the problem, who is managing the problem to resolution.

    When the issue log is reported at your regular stakeholder, management and vendor updates, you can then direct the discussion to whether the person managing the problem is actually the person who has the authority to resolve the problem in a timely manner.

    ReplyDelete