Forums

Hey Team,

I need some clarification.

According to Mike and Mark's recommendations a task (which is part of a project) should be reported as YES (completed) or NO (not completed) before any other information is shared by the direct, correct?

And, when communicating the status of a project as a whole the RED = missed task deadlines / project in danger, AMBER = missed some task deadlines / project not in danger, and GREEN = no missed deadlines / no future delays expected / project not in danger, should be used, correct?

I was trying to communicate these recommendations to my boss and got confused (looked a little embarassed I am sure) when I realized that I was saying both tasks and the overall project were both reported on using the RED/AMBER/GREEN system.

THanks for all your wonderful support of the years.

 

MICHAEL BOYKO

buhlerar's picture

Not that significant of a distinction.  I don't know if it matters so much whether tasks are reported yes/no vs. red/amber/green.  In practice, the "task" being reported on may be a 6-week activity so red/amber/green would make sense if it's work in process.  The only time it's a clear yes/no is if it's done or it's late, in which case you could just report as green or red (no amber if it's done or late).  Someone in charge of the project (who is chairing the meeting, for example) may have to attend another meeting where he or she is reporting on the status of the overall project, but in each of these meetings you could safely go exclusively with red/amber/green reporting.

I didn't get the sense from M&M that you have to make a distinction for tasks vs. projects.  The point is, you lead with status, not a story.

gearhead86's picture
Licensee BadgeTraining Badge

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

MicrosoftInternetExplorer4

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}

Michael,

BUHLERAR hit the nail on the head.   It’s Bottom Line Up Front (BLUF) repackaged.

Providing the status first allows the audience to put the rest of the conversation in context.  The status provides a framework that they can build the picture around.

In addition, the R/A/G ratings can guide the discussion.  It's always great to celebrate the small victories (i.e., finishing a task on time, budget and within scope), but the managers are going to be more interested in discussion the yellow and red categories to understand the risk and your mitigation strategies.

I'm not a fan of the YES/NO system -- projects and tasks are rarely black and white.

You can use either system to report status, either at the project level or at the task level.  It's really a matter of company policy -- or personal preference if there's no formal guidance.

Bill

MichaelBoyko's picture

Thank you for your insights. I want to be able to bring good project management to our firm - and I can't do that with out you guys! THANKS!

Merry Christmas / Happy Hollidays

- Michael