Monday, June 11, 2007

Now a Word From Our Sponsor

TO: Team Members

FROM: Sponsor

You have been selected to participate on the new [project name] team led by John. The team will meet once per week. The activities performed by this team will include:

  • Defining the project requirements for each decision gate.
  • Committing a closed plan to deliver project scope on [x date].
  • Sponsoring change requests to modify product plans based on significant changes to the committed baseline.
  • Communicating project status for your deliverables with the project manager to confirm that we have alignment of the piece parts.
  • Highlighting project risks in a timely fashion.

You have been selected to participate on this team because you have the knowledge and experience to make important contributions to this initiative. If for any reason you feel that you will not be a productive representative on this team, just let Eddie know.

Regards,
Cornelius Vanderbilt

__________________________________________

Here are the important elements of this letter:

1. Communicates meeting frequency
2. Defines activities
3. Sets expectations
4. Establishes referential authority


Moments after this letter was sent, it became readily apparent that some members of the team never agreed to support your project. How often do you hear, “I don’t have the time for this, go away?” Yes, this letter will trigger an avalanche of resistance from employees who never signed up for the assignment. That’s the beauty of using this letter, since it flushes out resistance early in the process so that you can deal with it.

If a team member’s workload is constrained, then become an advocate for that team member and ask his/her manager to reprioritize that person’s work. Functional managers and sponsors who tell the employee to “just do it” are your worst enemy. You should never be the source of a major work/life balance issue in your team and you shouldn’t have to beg and cajole resources to help. Use your sponsor to help resolve these resource issues.

No comments: