Expectations R' Us
From the pmStudent Blog
by Josh Nankivel
Ranting and raving about project management and systems engineering.
Recent Posts
The Problem with Project Management
The Problem with Project Management
The Problem with Project Management
LinkedIn Recommendations Are Easy
The Catch-22 of Project Management Certification and Experience
Categories
Agile,
Career Development,
Certification,
Change Management,
Communications Management,
Cost Management,
Documentation,
Earned Value Management,
Education,
Integration and Test,
Kanban,
Leadership,
Lean,
Lessons Learned,
Methodology,
Misc,
Multitasking,
New Project,
Operations,
Planning,
PMP,
Productivity,
Professional Development,
Project Estimation,
Project Leadership,
Quality,
Requirements Management,
Risk Management,
Schedule Management,
Scope Management,
Software,
Systems Thinking,
Tools,
Video,
Work Breakdown Structures (WBS)
Date

image by DailyPic via Flickr
When it comes to communicating with your project stakeholders, setting appropriate expectations and following through is king.
I was reminded of this important fact recently.
My Blunder
With four systems, I have a lot of key stakeholders. I had not properly communicated with one of those key stakeholders. At least, I should have done better.
I met with her this week and disovered she had specific worries about the system's useability that had not previously been uncovered. Had I been more dilligent, I could have easily addressed those concerns over a year ago. I came to this program after the design phase was complete, so I wasn't involved with eliciting requirements initially or working on system design.
I Was Lucky
I was able to address the concerns on the spot, but I was lucky. For other stakeholders, holding reservations like this for a long period of time could easily span resentment and cynicism toward the project.
The truth is, many people will avoid a conversation if they expect it might be unpleasant. Most of the time it isn't a conscious decision, but a heightened ability to rationalize behavior that avoids the confrontation.
I became aware of the fact I hadn't done enough to communicate with this stakeholder a few months ago. The opinions of my team made me think she would be very difficult to deal with, because everyone thought she'd want some functionality that our design just won't allow. So I rationalized that I really had to have my ducks in a row before I even attempted to speak with her. I had to justify the design all over again, and be sure I had talking points to respond to any objection.
Lesson Learned
In short, I wasted a lot of time and effort due to an imagined fear. It turned out she was very receptive to our design, she just didn't fully understand it and how she would be able to interact with the system.
If I had done a better job of communicating all along, her expectations as a stakeholder would have been clear to me and my team. In response, I could have ensured her expectations were set correctly and met.
I think it's important to acknowledge times like these when we fail to meet our own expectations. It's theraputic and educational. Here's another lessoned learned for the books.
Will you share a communication or setting expectations blunder in the comments? That way I don't feel so stupid. :-)
Posted on: October 14, 2011 06:05 PM |
Permalink
Comments (4)
Please login or join to subscribe to this item
Wai Mun Koo
PMO Director| Intergraph PP&M
Singapore, Singapore
Well, it can turn out their way too. There are stakeholders who are really demanding and if you are not well prepared, they will just shunt you off immediately and will not want to discuss further with you as they will think that it is a total waste of time.
There are also other type of stakeholders who make lots of noise because they have no clue what is going on and the details of the project, but once being briefed and educated, they will regain the confidence in the project. Usually, people develop fear and negative unnecessarily when they are kept in the dark. Others may just feel their voices not heard (perhaps not being given due attention and respect) if you have not taken their ideas and requests into consideration.
Yet there are also another type of stakeholders who will be so nice in front of you and very cooperative. But once you turn your back, they will transform into another beast totally and start cursing and swearing behind you on your project as if the project is killing them.
Monthly stakeholders meeting is a must! and one to one communication with key stakeholder that has the most interest in the project on weekly basis.
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
Good points everyone. All great things to keep in mind.
You're definitely not stupid!
On more than one occasion I have missed one or more stakeholders from a project communication, and that's normally the wrong person and the wrong moment.
Honesty is normally the best policy in these situations and I've always found people to understnd that your (mostly) human.
Please Login/Register to leave a comment.
|
Disbelief in magic can force a poor soul into believing in government and business.
- Tom Robbins
|