Search

8 Tips for Managing Stakeholder Expectations

Why Stakeholder Management? One of the most critical aspects of project management is doing what’s necessary to develop and control relationships with all individuals that the project impacts. In this article, you will learn techniques for identifying stakeholders, analyzing their influence on the project, and developing strategies to communicate, set boundaries, and manage competing expectations. By successfully managing your stakeholders, you will be better able to keep a lid on scope creep, ensure project requirements are aligned, understand tolerance for risk, and mitigate issues that would otherwise delay the project. Good stakeholder management is a testimony to your influence in an organization, and a key component to a healthy project environment. As the project manager for a coveted account you are excited for the opportunity of a new project, but anxious for a good outcome. The team is assembled and you have every confidence that they will help you successfully meet and exceed the client’s expectations. You’ve been here before and you know that even the best laid plans can quickly go awry. When this happens you need to regain control fast before your team loses motivation. By properly managing the stakeholders’ expectations from the outset, the chances for a smoother journey are much greater. Here’s 8 tips for PMPs to help keep the stakeholders calm and reassured throughout the project, and also at the end, take a look at some great PDU courses for PMPs that can help you build your leadership and project management skills.   1. Identify who the stakeholders are. Obvious? Not always. Most projects will have numerous stakeholders and not necessarily just the most easily recognizable. The PMBOK® Guide defines a stakeholder as: a person, or organization, that is actively involved in the project, has interests that may be positively or negatively affected by the performance or completion of the project, and may exert influence over the project. That could include senior management in your own company. If the major influencers in your own company are not fully onboard, it could cause dissent in your team. You will then need to identify the other non-obvious stakeholders of this project. For example, who are the funders? They normally take a quiet back seat behind the movers and shakers, but if you haven’t considered their expectations you might lose an important influencer. Keep brainstorming for other quiet, but important stakeholders. 2. Identify the stakeholder’s preferred method of communication. By using the most effective manner of communication you will help ensure the stakeholder remains content. If you make the mistake of using the wrong method (or non-preferred method) it will cause frustration and lack of confidence. It will show you didn’t listen to their initial direction. 3. Keep stakeholders engaged throughout the process with timely updates. Ask the right questions, of the right people, at the beginning and throughout the project. 4. Accurately map expectations. Be crystal clear on the expectations from the stakeholder’s point of view. Ask them how they will measure success of the project. Inevitably you will discover conflicting definitions of success. Some will consider meeting the final deadline their number one priority. Another might consider end user functionality of the final product as most important. How do you manage these conflicts? One way would be to facilitate a meeting of all stakeholders (where practical) and help them come to mutually satisfying agreements. 5. Classify the level of communication for each stakeholder. Understand who requires hand holding and insists on receiving all details. Who prefers a basic, occasional overview? Who wants daily or weekly communication? 6. Identify which stakeholders will be advocates and which will be road blockers. Map your strategy accordingly. 7. Engage the stakeholders in decision making. Stroke their egos. You probably have already identified the best course of action, but present your findings in such a way that you leave room for the stakeholders to feel they have been involved in the process. 8. The manner in which the project is accomplished is vitally important, not just delivering on the required specs. Stakeholders will remember the overall mood of the entire process. Their measure of success is not just the finished product, but the way you attained the end goal.

8 Tips for Managing Stakeholder Expectations

4K
8 Tips for Managing Stakeholder Expectations
Why Stakeholder Management?

One of the most critical aspects of project management is doing what’s necessary to develop and control relationships with all individuals that the project impacts. In this article, you will learn techniques for identifying stakeholders, analyzing their influence on the project, and developing strategies to communicate, set boundaries, and manage competing expectations.

By successfully managing your stakeholders, you will be better able to keep a lid on scope creep, ensure project requirements are aligned, understand tolerance for risk, and mitigate issues that would otherwise delay the project. Good stakeholder management is a testimony to your influence in an organization, and a key component to a healthy project environment.

As the project manager for a coveted account you are excited for the opportunity of a new project, but anxious for a good outcome. The team is assembled and you have every confidence that they will help you successfully meet and exceed the client’s expectations.

You’ve been here before and you know that even the best laid plans can quickly go awry. When this happens you need to regain control fast before your team loses motivation.

By properly managing the stakeholders’ expectations from the outset, the chances for a smoother journey are much greater. Here’s 8 tips for PMPs to help keep the stakeholders calm and reassured throughout the project, and also at the end, take a look at some great PDU courses for PMPs that can help you build your leadership and project management skills.

 

1. Identify who the stakeholders are. Obvious? Not always. Most projects will have numerous stakeholders and not necessarily just the most easily recognizable. The PMBOK® Guide defines a stakeholder as: a person, or organization, that is actively involved in the project, has interests that may be positively or negatively affected by the performance or completion of the project, and may exert influence over the project. That could include senior management in your own company. If the major influencers in your own company are not fully onboard, it could cause dissent in your team.

You will then need to identify the other non-obvious stakeholders of this project. For example, who are the funders? They normally take a quiet back seat behind the movers and shakers, but if you haven’t considered their expectations you might lose an important influencer. Keep brainstorming for other quiet, but important stakeholders.

2. Identify the stakeholder’s preferred method of communication. By using the most effective manner of communication you will help ensure the stakeholder remains content. If you make the mistake of using the wrong method (or non-preferred method) it will cause frustration and lack of confidence. It will show you didn’t listen to their initial direction.

3. Keep stakeholders engaged throughout the process with timely updates. Ask the right questions, of the right people, at the beginning and throughout the project.

4. Accurately map expectations. Be crystal clear on the expectations from the stakeholder’s point of view. Ask them how they will measure success of the project. Inevitably you will discover conflicting definitions of success. Some will consider meeting the final deadline their number one priority. Another might consider end user functionality of the final product as most important. How do you manage these conflicts? One way would be to facilitate a meeting of all stakeholders (where practical) and help them come to mutually satisfying agreements.

5. Classify the level of communication for each stakeholder. Understand who requires hand holding and insists on receiving all details. Who prefers a basic, occasional overview? Who wants daily or weekly communication?

6. Identify which stakeholders will be advocates and which will be road blockers. Map your strategy accordingly.

7. Engage the stakeholders in decision making. Stroke their egos. You probably have already identified the best course of action, but present your findings in such a way that you leave room for the stakeholders to feel they have been involved in the process.

8. The manner in which the project is accomplished is vitally important, not just delivering on the required specs. Stakeholders will remember the overall mood of the entire process. Their measure of success is not just the finished product, but the way you attained the end goal.

KnowledgeHut

KnowledgeHut

Author

KnowledgeHut is an outcome-focused global ed-tech company. We help organizations and professionals unlock excellence through skills development. We offer training solutions under the people and process, data science, full-stack development, cybersecurity, future technologies and digital transformation verticals.
Website : https://www.knowledgehut.com

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Adaptive and Predictive Project Delivery - Challenges and Use Cases

Project managers should know how to strategize projects depending on the budget, client’s requirements, deadlines and specifications. Especially, in the software development projects managing the process with the right methodology and tools is significant in meeting your process goals.When it comes to choosing between adaptive and predictive project delivery, there has been a push towards adaptive (agile) methodologies over the more traditional predictive (waterfall) methodologies in the recent years. But the most common mistake is irrespective of the project requirements the project managers follow single project management strategy.In this e-book, we present an analysis by Dan S. Roman, an outcome-driven Senior Project Manager and Scrum Master. A champion of combining best practices to achieve results, Dan shares insights from over four decades of project management experience.The e-book is a report analysis on how the delivery approach, predictive or adaptive, can address some of the failure causes identified in the Chaos reports for enterprises to evaluate the best approach to choose between adaptive and predictive delivery for projects.Dan explains what the projects challenges are and how the right delivery approach can help. He quotes use cases on the approach and says what went well and what could have been different.In conclusion, to undertake these tasks Project managers must be aware of existing and emergent practices and gather deeper knowledge for the best suitable practices.
1544
Adaptive and Predictive Project Delivery - Chall...

Project managers should know how to strategize pro... Read More

Remove Your Mental Block, Open Up and Think in Terms of PMBOK’s Best Practices

Excerpt from the personal blog of KnowledgeHut Faculty – Satya Narayan Dash, PMP Aswin Krishnan H is a proud PMP today. His success is not only due to sound preparation, but also handling stress during the exam. He names it as the “smile” factor, as he has told below so uniquely. Aswin was part of my class in May, 2015. He is a very lively person and participates fully. In fact, I remember few instances where his enthusiastic participation were bringing surprised looks on some faces. In my view, enthusiasm is a great quality in any team member. But, unfortunately, it is highly underrated. I believe, enthusiasm is contagious and brings many into the fold of discussion. He called me after he was certified and I asked – “How does it feel to be a PMP?” He had a sense of happiness, relief and immense satisfaction. Below, he has outlined his experience in preparing for it, going through the PMP program and finally cracking the exam. Go on and read his experience.                                                               ************************************* Introductory – Why I decided on it and how I started? I was motivated to do PMP as part of my job and wanted to understand properly the Best Practices and how to use them with confidence in day to day activities as far as possible. Three of my friends were equally interested in doing Industry standard certification and when we began our search we had PRINCE 2 and PMP in our mind. Finally, we settled down with PMP which has huge demand in any industry. We then started our search for Training provider, found that it’s the Coach and his approach that help a lot in this kind of Certification, though online and word of mouth reviews we shortlisted Knowledge Hut. One of my friend had a successful experience in securing his PMP within a month after training with the Coach Mr. Satya Narayan Dash, He was really impressed by his practical approach, knowledge and personal commitment. He has previously attended PMP trainings from various centers but never could understand the concepts clearly, and failed in the exam miserably. He came from Chennai to do the course in Bangalore, just for the Coach. My PMP Training Experience: The training was very precise and covered all Knowledge Areas from the 5 Process Groups: Initiating, Planning, Executing, Monitoring and Controlling and Closing. Satya was very kind and use to share his personal experiences with certain problems which helped to see insights of approaches and reason why or what suits best based on the PMBOK Guide. He always helped us think about all the process and why each Input is given and what is the output of each process and why it is important, often in many of the companies we don’t practically use all the process or tools but the Coach’s insight in all tools and approaches was very helpful in understanding the Input, Tools and Techniques and Output (ITTO) for each Processes. We had classes on Weekends, the coach was very punctual and kept his timelines very strict. He was very happy to help even after the classes and he would stay back for us even if it was raining just to make sure that we get the idea of what is happening or why it is happening, He use to explain ‘Change Request’ or ‘Deliverable’ Flow by drawing pictures as it goes through each processes. These insights really helped in understanding the concept and the interrelationship between each process and ITTO. In the entire class there was fun, all were active and were participating which the coach always managed to make it interactive. Lot of things we need an actual physical person to explain to us rather than just going through hours and hours of Videos. I understood that having a real person standing in front of us will build that physiological effect, which will help me learn more and get motivated easily. My Own Study: I really wanted to complete the exam within 2 months after completing the class, but due to personal commitments it got extended to 4 months. Every-day I use to spend at the least 2-3 hours reading PMBOK 5th Edition, Rita Mulchay. This really solidified my understanding that was gained in the Classroom training.  In the last one or two months I use to keep on giving Mock Tests in the early mornings (4 -7 am) and then review them after coming back from work (7 – 8 pm), I kept on giving mock test from various places and was not be very subjective in selecting the source for exam. I felt that giving these mock tests really boosted my confidence and triggered to schedule the exam. While doing the mock tests most of the times I was in panic and I didn’t read all options and selected the wrong one. Rita Mulcahy’s recommendation helped. I read the options from D to A instead of A to D. This really increased my hit percentage. My PMP Exam Experience: I became a member, filled in my application, got my references and waited for a week to get it approved; luckily it was not selected for any audit. That was half way done, second challenge was to schedule the exam. I kept on giving mock tests until I had the confidence and was hitting 75-80% in mock tests. This triggered me to schedule an exam, at this time I just wanted it to get over at the earliest; luckily I found a date that was within 10 days and scheduled the exam on that day. I had formulated this strategy of completing 70 questions in an hour so I will be done within 3 hours at the max (200 questions) this I kept on applying while taking the mock tests and this strategy was quiet successful for me. On the Test day, I was faced with a flurry of Mathematical questions (20-25) from Question No#1 with all confusing stuffs and very wordy; I was very stressed, then I remember reading somewhere that even if you are stressed and if you manage to keep a smile on your face you can beat the stress. I applied the same and was able to get over the initial surprises in the exam. There were lots of situational questions, I was confused in lots of places; I marked them and kept on moving forward without worrying about the lengthy or wordy questions and kept on answering whichever I could. Finally, by the time I was done with 200 questions, it was like 2:30 hours; so I went back and selected all the unanswered and marked ones and slowly went through each one of them, now ‘smile’ factor worked and was able to easily and clearly read the questions and answer them. I completed all left outs within 45 minutes. Now I started reviewing again from beginning and just kept on speed reading questions and selected answers just to make sure that I did them correctly. The PMP really puts a toll on you with all sorts of Mathematical, Situational, and Tricky Questions, the initial impact of the questions is really intended to create stress, if you overcome that then you would be able to score very easily. During the exam I read the answers from D to A instead of A to D, I found this to be very helpful against panic answering due to stress. Suggestions for PMP Aspirants: – Dos Please read PMBOK at the least twice, it is very helpful and answer to PMBOK and not to your personal experiences. Please take any book like Rita or Andy Crowe or Head First and complete them once before kick starting the mock tests. Please keep a smile on your face, even though you are stressed, this will help relieve stress and get back to your senses while taking test, if you are in panic answering mode read the answers from D to A than from A to D this will improve your hit rate, these helped me. Please do take 10-15 mock tests before attempting the exam, this really helped me understand where I stand and what my weakness is and helped to motivate and improve. Real life PM experience helps a lot while answering these questions during the exam. – Don’ts Don’t waste time prolonging the exam, use your time wisely and complete it at the earliest. Having too many materials won’t help as you will be confused when to complete them, don’t get overburdened. Conclusion: After earning PMP I am much relived, I can see the fruits of hard work getting paid off. Whenever you say that you are PMP, there is a peer respect, because all of them know how much committed you need to be to earn this prestigious qualification. I now see what things at work do work and what not and how they are interrelated. PMP is not just a one-time process, you can apply this leanings in each every aspect of your life which you are doing unconsciously. Finally If I CAN DO IT ANY ONE CAN. You just need to remove the mental block and open up and think more in terms with best practices put forward by PMBOK, and your personal commitment. Brief Profile:  I am Aswin Krishnan H and am a Project Manager with Hewlett-Packard, India. I have 9 years of experience in Telecom, Retail and Security Domain with .NET Platform.                                                               ******************************   Aswin’s online PMP credential is available at PMI’s online credential registry. I am thankful to Aswin for sharing his journey in achieving the PMP certification. I believe it will help you – the PMP aspirant – to have your own. This article was originally published on managementyogi.blogspot.in
Remove Your Mental Block, Open Up and Think in Ter...

Excerpt from the personal blog of KnowledgeHut Fac... Read More

Identifying Project Stakeholders in the “Project Management Professional” Way

Project Management Professional (PMP) certification is an industry recognized qualification for the Project Managers. PMP is the market indicator of experience, knowledge and enhancement of skills, which are required to lead and direct the project. PMPs are the crucial part of every organization. PMP qualified Project Managers reach the potential to handle multiple projects and turn them into tangible outputs, minimizing the various project constraints. At the onset of the project, it is important to identify the formal authority for the project, in the form of Project Charter. That means, we need to identify the Project Stakeholders. Identifying project stakeholders at the very beginning of the project is critical to project success. This process is carried out before the end-to-end planning stage of the project. It is a two stage process which is carried out when the stakeholders are not content. If a step intended to satisfy the stakeholders is actually not serving its purpose, we can call it anything but project success. The following steps are mandatory to keep a project running successfully- Identifying the stakeholders Inspecting the relationship of each stakeholder with the project to establish their level of interest in the project. Anyone and everyone can be the stakeholder. It includes the people whose business interests are impacted by the project, who can dominate or steer the project, or have more expectations from the project. A stakeholder is not necessarily a sponsor or board member. He or she can also be a team member or the project manager. Every single member associated with the project can be a stakeholder. So you can identify the stakeholders by the source of information on the Stakeholders (Input), working on that information (using the tools) and on outcome. Input:  Project Charter– It not only refers to the documents specifying the rights of the Project Manager, but also provides a list of the key Stakeholders (comprises of the Sponsor, Senior Management, or Consulting Management). Procurement Documents: In addition to Charter, the Procurement Document is a great source to the third party stakeholders falling lower in hierarchy. Enterprise Environmental Factors– EEF indicates how the rules and regulations, human resources and structure of the Organization etc. affect the project. One of the factors can be input, to identify the key stakeholders which gives us insight on who has the power to influence the project. Organizational Process Assets– OPA is the repository which keeps information about the past project, improvement from past projects, procedures, policies and standards in an assembled manner, so as to act as a reference for future projects. Tools and Techniques:  Stakeholder Analysis– It consists of analyzing the information from the input of identifying Stakeholders, which will assist us to select the stakeholder who can influence the project positively. So we can start recording the role of an individual, their point of interest, their influence level against the list of all stakeholders. You should examine the expectations and interests of all the listed stakeholders in details. This may help identify more stakeholders. In addition to that, we can handle all the stakeholders’ concern and make plans to address them. That is one good way we can convert negative stakeholders to positive ones. Once we have the relevant details, we can use those to classify the stakeholders depending on their interests, influence, support and power. We can use tools like Resistor, Neutral and Advocate to categorize Stakeholders: Resistor is a negative stakeholder who is not supporting the project. Neutral stakeholder does not support the project. In this case, the project manager tries to convert their interests positively. Advocate is a stakeholder who completely supports the project and also provides ideas to overcome the barriers if any. Output:  Stakeholder Register- All the information accumulated in stakeholder analysis helps us in creating a Stakeholder Register. A register comprises of all  the information in tabular form, whose size depends on the project size. It is the duty of the project manager to identify the potential stakeholders and note them down in the table, so as to ensure project success. Project Stakeholder Register is depicted below: Stakeholder Management Strategy– Stakeholder management strategy is formulated to plan the actions for the entire course of the project management. This strategy is made to minimize the negative influences on the project.          As per PMBOK 5th Edition, the Stakeholder management strategy document includes the following: Key Stakeholder’s impact on the project Stakeholders’ level of participation as per stakeholder analysis Groups designated to each stakeholder Assessment of Impact Potential strategy for gathering Support Collecting source of information on the stakeholder as an input, and working on that data using tools can help us in finding the positive stakeholder to enhance the level for project success.
1772
Identifying Project Stakeholders in the “Pro...

Project Management Professional (PMP) certificatio... Read More

Useful links