October 21, 2010 – Communicating what Matters

Several of the brain dump entries from February center around “Communicating what Matters.” This shouldn’t be a surprise. Some have estimated that 80% of project management is communication. Others claim that 63% of all statistics are made up on the spur of the moment.

The mark of an excellent project manager is communicating the right amount to the right people in the right format at the right time: making it matter.

The Right Amount

We’ve all sat through long winded, slide enhanced meetings that completely fill the4-hour morning time slot and spill over into lunch. If you are like me, you grasped the concept, impact and expectations of the topic within the first 20 minutes, but have to endure the remaining torture. In truth, I probably delivered some of those presentations.

The purpose of any communication is to allow the audience to make informed decisions (#2 on February’s list). This is true whether you are sending an email or presenting at an executive meeting. Give them all the information they need; leave nothing important out. Summarize the content and focus on the pertinent information. You will want to have any supporting evidence or content available, but wait until they ask before inundating them with it.

Additional suggestions:

• If asked to produce a report, verify the content and detail needed before starting.
• At the start of a meeting, lay out your direction and ask if where you are headed is where they expected to end up.
• Reread your emails from the perspective of the receiver. Is it organized logically? Is your main point summarized within the first two sentences? Are you being too wordy?

The Right People

Have you ever been to a meeting and thought, “Why in the world did they invite me to another one of these?”

Or what about speaking with someone for an hour only to have them say, “I’m not the person you need to talk with. You need to speak to Joe Smith in Accounting.” Why couldn’t they have informed me of that in the first 5 minutes?!?

One critical communication point is the “To:” list on your email. Check it twice before hitting send. Make sure you have only the intended audience copied. Avoid hitting “reply to all” unless you mean it or remove unnecessary names.

Make sure you have the right individual. In the Orange County chapter of PMI there is an individual named Tom Cumming. Because we are both active in the chapter, we are constantly receiving emails intended for the other individual. Making that mistake wouldn’t be too bad, but if one “Joe Smith” is the CEO and the other is the guy in accounting you wanted to contact, be careful.

Additional suggestions:

• Mailing lists are essential. Setting one up for each project will save time when sending out communications. Then make sure to maintain it as people join and leave the team.
• If you are not getting feedback on emails or people are not showing for your meetings, verify that they are receiving your communications.
• When in doubt, ask. A simple phone call saying, “I’m trying to reach the individual in charge of…” can save a lot of explaining later.

The Right Format

This became strikingly clear to me on one particular project. I failed to deliver the project’s schedule and status in a format consumable by my client. The direction of the project was on track to meet our schedule. We were well within budget. The scope was being honed appropriately.

However, because it wasn’t delivered in the format that was expected, I missed the mark. Once it was sorted out, things progressed much smoother.

If you are new to the department or company, ask others to point you in the right direction. If there is a PMO, there is usually a template. Don’t reinvent what already exists.

Additional suggestions:

• If there are several versions of a regular communication (ex. Status Report, Resource Request, Charter, etc.) in use, look to standardize it. Consistency will save time for you in creating it and for the recipient in reviewing it.
• Templates need to be reviewed and revised regularly to make sure they are meeting the needs of the intended audience.
• If there is a meeting, report, or template that is no longer needed get rid of it.

Presenting the right amount of information to the right people in the right format will at least you stand a chance of “Communicating What Matters.”

October 27, 2008 – Back to the Basic: Communication – How

Once, in the midst of a long distance relationship I had the grand idea of sending a Western Union Telegram to my girlfriend. From my vast knowledge of telegrams, based solely on movies and TV, I knew that every time you put a period they say "STOP" to indicate the end of the sentence. I envisioned a hand delivered envelop with the words “Don’t STOP loving me and I won’t STOP loving you” on Western Union paper. I think they took my $20 and placed a phone call instead that incoherently said "Don't loving me and I won't loving you."

Telegrams were a great way to express you feelings in the 1800’s but by the 1980’s it was out dated. Sometimes you know what to say and when to say it but fail to be heard because of how you choose to say it.

How to be Heard. When deciding how to get your message out, you need to consider both the method and content.

The method does matter. There are the normal methods:

• Phone. Great for quick answers and to give initial direction. Not so good for detailed instructions or approvals.
• Voice Mail. Excellent for letting people know you called and for playing phone tag. Don’t rely on it to guarantee the message was conveyed or that action will be taken.
• Instant Messaging. Good tool to exchange ideas and verify progress.
• Email. Reliable for giving more detailed instructions and receiving approval. Not very personal and can lead to chaos when everyone replies to everyone else.
• Teleconference. When your team is half way around the world, email doesn’t cut it. It can take 2 days to convey a message. Scheduling a teleconference can clarify the conversation quickly.
• Webex / GoToMeeting. Web meeting tools that allow you to share your desktop information make it possible for you to run your business from practically anywhere.
• Get out of your seat. The personal touch allows you to observe the non-verbal aspects of communication like body language, eye contact, gestures and facial expressions. When other methods fail, it may be worth the trip down the hall or across the world.
• Video Conference. The next best thing to being there. Setting up a web cam on both ends of the world can be relatively cheap and net big benefits.

Sometimes you have to think beyond the normal to get your message across.

• Go Big. The company I work for owns a plotter for printing poster size images. Some statements need to be loud. Skywriting might be a little much.
• Websites / SharePoint. A central location for communicating project updates is a great means to keep the team, management, end users and other key stakeholder informed.
• Hand Written. In an age of electronic everything, sometimes the best communication is a hand written note. It can be a card of encouragement, a sticky note of thanks or a message on the whiteboard.

Content clarifies. Here are some simple things that will help get you heard clearer.

• Check the Spelling. I recently received a high glossy postcard from my insurance company. They spelled the word “their” wrong…twice. It doesn’t instill a large amount of confidence in the company.
• Reread it for clarity. Some sentences make their own nonsense…like this one. Often I review what I think is brilliant writing and find it muddled.
• Shorten it. As you reread, look for simpler, more concise ways to communicate your thoughts.

In the end, you need to merge the What, When and How to get your message across.

By the way, that long distance relationship? We just passed our 19th wedding anniversary.

September 8, 2008 – Back to the Basic: The Troubling Triangle

In our quest to return to the basic of project management we have already tackled the stakeholders. Next we take on the triple constraint in the form of a triangle. The concept of a triangle to represent the Scope, Schedule and Cost of a project is actually quite ingenious. Adding more scope dictates an increase in the schedule, cost or both. Reducing the cost or timeline for the project requires less scope. Each part is dependent on the other two.

The trouble is that management thinks of these three items as completely independent of each other; like 3 line segments lying as distinctly separated as the bones in my daughter’s x-ray from last week’s edition.

Scope. The scope of your project includes the full extent of what is agreed to, both verbally and in writing. In reality scope is never fully defined until all of the requirements are vetted, but from the minute you take ownership it is our responsibility is to ferret out promises and commitments made. This is especially evident in the consulting world. Account Representatives (aka Salesmen) are notorious for making promises and not letting the project manager in on the secret. Take your list of Stakeholders and find out their expectations.

The resulting wish list is not your scope. Like pruning a Bonsai tree you need to cut that back to something you can realistically deliver in the timeframe and cost provided. Remember, you can’t set one line segment of your triangle without impacting the other two.

Cost. Auto salesmen get a bad rep, justifiably so in many cases. But you can take a page out of their play book. When asked how much it will cost to deliver the scope, ask how much they are looking to spend. If they only have enough for a used, beat up Yugo, don’t try to sell them a Lamborghini.

When giving an estimate, put it in terms of what will be delivered. Never give a quote without documenting your assumptions; the “here’s what I was thinking…” piece. Placing the cost into context forces the discussion of scope.

Schedule. Timing is always an issue. On one project our directive was to go live in August. Backing up from that date gave us July for Testing and Implementation, June for Development, May for Design and April for Requirements. It would be tight, but do-able. At the end of May “in production” was clarified to mean the day after 4 weeks of parallel testing in the production environment. Changing the move to production, even if we weren’t “live” would have been impossible without changing the scope and adding more resources (increasing the cost).

Find out what the date is and the significance of it. If it is a hard date you have already set one of the legs in the triangle.

As you establish the three legs of your triangle, it is management’s job to stretch the scope side while reducing the length of the cost and schedule sides. How can you effectively push back without a career shortening screaming match?

Go gourmet on them. Most CIOs, VPs and Senior Managers enjoy their share of fine food. The higher end restaurants produce amazing dinners that take longer to serve and cost quite a bit more than your local fast food joint. Even our cafeteria at work has a sign that says, “Good food takes time. Thank you for your patience.”

Build a reputation on speaking straight and not padding estimates. It is your responsibility to present the facts, back them up with evidence and state your case clearly. It is their job to make decisions.

September 1, 2008 – Back to the Basic: Stakeholders

On July 17, 1999 I was sitting in an emergency room waiting for x-rays to confirm something obvious. My six year old daughter had broken her left arm just above the elbow.

On the television a worse parental nightmare was unfolding for the Kennedy family. The night before, John F. Kennedy Jr.’s plane had crashed off Martha’s Vineyard, MA (USA) and the news was covering the ongoing search. It was determined that the likely cause of the accident was spatial disorientation, a confusion of the brain that completely destroys your perceptions. The sky that night was dark, and a haze hid the horizon. Without visual references the brain can misinterpret signals from your inner ear.

Pilots with this condition have been known to fly upside down while believing they are right side up. Instead of climbing steeply they may in fact be heading straight for the ground. Only by relying on their instrument panel can they pull through it.

In the midst of a project, when changes are dogging you and deadlines are due, it is easy to loose sight of reference points, forget the basics and start running on adrenaline and pure luck. If your instincts are solid you may be able to fly by the seat of your pants for some distance. However, even the best project mangers can succumb to project disorientation. Fortunately it is neither fatal nor as tragic as JFK Jr’s death.

This series is entitled “Back to the Basics” and is intended to remind us that projects fail day by day, usually when we loose sight of simple things.

Stakeholders.
Project success begins by identifying and understanding who your key stakeholders are. If you can’t identify the players and which side they are on, you stand little chance of satisfying their needs and landing the project without incident.

Identification. Several stakeholders jump out immediately: the sponsor, end users and your team. But a stakeholder is an individual or group that is either impacted by the development process or the end product of your project

In 1988, New York State attempted to put a low level radioactive waste dump in Allegany County. Although not involved in the construction or ultimate use of the facility, the people of the county were key stakeholders. Their “Bump The Dump” campaign successfully blocked the project and in 1992 the US Supreme Court amended the federal law that required states to store radioactive waste within their own borders.

Create a list of the people and groups impacted by your project. Include hidden ones like:
Current users of what you are getting rid of or replacing (system, building, facility, software, highway, forest)
External suppliers, users or supports. Whole communities are impacted by factory shutdowns, megastore constructions or radioactive dumps. On a much smaller scale, the company supplying data or using your information will have impacts, too.
Support Teams. Call center reps, operational support and disaster recovery are impacted by system changes.

Motivation. Once you have identified them, you need to understand their position. Some will be strong supporters of the project. Others my loose their jobs or need to be retrained as a result of it. For each stakeholder determine and document how the project will impact them.

What pressures are they under? Your director’s bonus may be based on you spending the entire budget. Regulatory or legal requirements may impose strict timeframes. CEO commitments to shareholders may have been made.

Recognition. Return to your list throughout the project. In addition to documenting new stakeholders, begin to put specific names beside each one. This will help you think through whom you are dealing with and begin to plan your approach to dealing with them.

Communication. From the beginning of the project you need to keep the stakeholders informed. You don’t need to have all the answers and in some cases you won’t be able to divulge all of the information, but an open line of communication will alleviate fear and uncertainty.

Unspoken and unaddressed concerns will exist for something as big as potential layoffs or as seemingly small as a new time entry logon screen. Create a forum and an atmosphere conducive to asking question and providing feedback.

The ultimate success of you project depends on you identifying the right stakeholders and satisfying their requirements while sustaining minimal damage from the opposing viewpoints. It is easy to become disoriented by the loudest stakeholder or the one holding the cash, but by identifying them and their agendas you can pull out of a dive before you crash.

NOTE: For an interesting twist on Stakeholder Management, visit the article “The End of Fairy Tale Beginnings” at www.computerworld.com