Sound AdviceThe other day I had some time on my hands so I decided to do a little clean up of the data drives on my computer system. That was a bold decision. Not just because of the number of files I have — numbering in the tens of thousands — but also how many of those files seem to exist multiple times, not to mention also in multiple progressive revisions.
So be it. But instead, I came across a couple of thoughtful pieces that I saved and now feel it is worth while showing them as one of my Musings. The first piece is by email from Kiron Bondale circa July 2014 who writes: What are the characteristics of your ideal project sponsor? From Manager's Choice By Bec Morse
Business Transformation Consultant; Project Management Trainer and Speaker; Capability Builder Kiron Bondale, PMP, PMI-RMP
Senior Project Portfolio & Change Management Professional
responds:
Here are a few snippets of advice to your sponsor to get the discussion thread rolling
(in no particular order):
- Please respect role boundaries with your PM and don't micromanage or undermine the PM's role,
- Demonstrates true commitment to project success (not just being involved!)
- Please ensure you have sufficient influence and authority to effectively support the project and
- Act as a highly visible champion and spokesperson for the project's benefits & outcomes to the team and to key stakeholders.
- Please have the funding required to ensure the project's survival to completion, and
- Act in an appropriate, responsive fashion when risks, issues, actions & decisions are brought to your attention
Advice to the project manager and team members: 15 tips on good email etiquette
The second piece I found is by Denise Dudley from Work It! Get In, Get Noticed, Get Promoted (Skill Path Publications). It appears to be from around June 2017.
- Reply in 24 hours or less.
- Begin with a salutation.
- Introduce yourself.
- Show the topic in the subject line.
- Avoid joking or sarcasm.
- Make sure grammar, spelling, and everything else are perfect.
- Don't use text lingo.
- Avoid all caps.
- Be careful what you write.
- Close with a sign-off.
- Take 5 to review your message before hitting "send".
- Don't overuse "Reply All".
- Keep it short.
- Don't send negative messages via email.
- Keep a thread.
Yes, I know this is pretty well standard stuff. However, in my experience, in most exchanges or threads whether associated with a project or some discussion forum, only about a half of these recommendations are actually heeded. What a pity! But there are occasions when all of these "requirements" are particularly important. That is, as project manager or team leader you have to straighten out an issue that is either sensitive or personal, or both. In which case — DON'T HIT THE SEND BUTTON.
Save your missive overnight and re-read it in the morning. Then you will know what it feels like to receive such a message. Fix or smooth as necessary to make your message more likely to be accepted as good advice rather than being rejected out of hand as arrogant, or rude, or both. If the message passes that test, and it is still needed, go right ahead and hit the SEND button. Now you can get it out of your mind and move on to the next project challenge. 
| 
