« Managing Project Scope
Agile and the PMO Working Together »

How to Prepare for a Project Sponsor Meeting

February 5, 2010 | Author: PM Hut | Filed under: Communications Management

How to Prepare for a Project Sponsor Meeting
By Zenkara

Sponsors are critical to almost all projects. They’re the people who get budgets approved, they’re the ones who provide the energy and impetus for getting the business ready for the project.

Yet Project Managers often seem to treat them like they’re a pain in the backside and are really just a distraction from the real project work. When we meet with sponsors, we’ll often take along a project progress/status report and run through it with then during the meeting. If we don’t have much to report, we’ll often wordsmith the report to make it look like there’s real action happening. These types of status reports often don’t have many quantitative measures and are a talkfest rather than a real progress report.

However, when you treat the sponsor meeting as the opportunity that they are, you’ll find more engagement and more success in your projects.

Remember that sponsors themselves usually report to someone (or a board, executive team etc) so it’s in their interest to know what is truly happening.

Treat each sponsor meeting as if you were selling them the project/product and you’ll soon see a revitalizing of the business.

Prepare for the meeting by gathering not just the progress report but also what is not contained in the progress report.

Info on the team, the environment, customer politics, project performance enables a much broader picture of what is happening and more of what sponsors really want to know.

They can always read a status report to get the % schedule complete, budget expended, risks identified. But some PMs exclaim “but we need to explain the report to the sponsor”. That really just indicates a poorly written report.

Motivated sponsors as just as interested in what is not in the report and most importantly if their expectations are still being met. They also want to make sure they are aware of any surprises as soon as they crop up – rather than being informed at the end of the month.

An important job of the PM is managing expectations – particularly those of the customer and of the sponsor. By getting to know their concerns before the meeting, you can begin to anticipate what questions they’ll ask during the meeting1.

Of course if you don’t get anything from them, either:

  1. they’re priorities are elsewhere and you have got to get back under their noses for a successful outcome – “not in their lot, oft forgot” or,
  2. they’re completely happy with progress (less likely)

When you can anticipate their needs and come prepared with answers, you build confidence in their project and your progress.

Not to sound like a cliche, but help them help you…

Here’s a project sponsor pre-meeting checklist (MS Word document).

1Emails you get throughout the week from the sponsor are a good indicator of their concerns – read between the lines.

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

This entry was posted on Friday, February 5th, 2010 and is filed under Communications Management. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

1 person has left a comment

Hi Zenkara - this is a very good post. What are your thoughts on other actual steps a PM can take?

Laura Bamberg wrote on February 8, 2010 - 4:01 pm | 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