Featured

4 Top Reasons Why Stakeholder Engagement Matters

Your customer is responsible making sure the right people are involved in the project.  After all, they are paying for the work.  Right? 

WRONG!    

 The project manager is responsible for ensuring project success which goes beyond simply following instructions.  This means, the PM is ultimately responsible for ensuring the appropriate players are involved throughout the project to minimize project risks and ensure project acceptance.    

In some organizations, this may be a challenge, but the rewards are well worth the effort.  Here are 4 of the top reasons why strong stakeholder engagement helps ensure project success. 

  1.  Avoid surprises

Too often, project teams find out about requirements well into a project resulting in rework and/or project delays.   Failure to address these “surprises” cam result in low project acceptance   and lack of confidence in the quality of the project results.  Researchers found that missed requirements were a factor in more than 1 out of 3 project failures. 

Project teams can avoid these “surprises” by engaging all groups that feel they have input or are impacted by the project to be involved throughout the project lifecycle. Create advocates

2. Create Advocates

If a stakeholder is kept informed and consulted throughout the project process, they feel they are part of the team and own the project results.  They are unlikely to criticize or speak badly about the project results.  Project teams can use this tendency to create a network of advocates in interested groups. 

This approach was used successfully by a leading motorcycle manufacturer interested in developing a web bases system to provide dealers with sales leads obtained through magazine inserts and motorcycle shows.  The project team involved several well-respected dealer representatives to actively participate in the project including requirements definition and validation.

 These dealer representatives were able to help “sell” the new solution to other dealers because they were integral in designing the solution and felt pride in what the team delivered. 

3. Improve Project Quality

Project teams cannot possibly know everything about the business impact of every project they take on.  Fortunately, they have subject matter experts that they can call on for their expertise and their knowledge of the organization.

 Engaged stakeholders have “skin in the game”.  They have supported the project and feel responsible for the project results.  Because they have a sense of ownership and are responsible to their business groups, they are going to make sure all requirements are defined,  any issues are addressed and the project results are thoroughly  tested before it turned over to the business unit. 

4. Simplify Project Acceptance

Stakeholder engagement results in better requirements definition,

high quality results and user advocates.   Project acceptance becomes an administrative formality.  There is no question that the project deliverables meet the business requirements and project scope since all impacted groups were involved throughout the entire project.  They were consulted, kept them informed and understand any design decisions.  Of course, they will accept the results! 

Involving added stakeholder groups in the project does increase complexity and communications.  However, it is well worth the added effort and will directly contribute to your project/s success.   

Featured

Project Stakeholder Management 101

John was at a loss. He had been working with the team for months to implement the new sales processes.  Days before go-live, the Customer Service vice-president announced he would not allow the project to move forward.  What went wrong?  

As Project manager, John had ensured he had good sponsor support, had gotten buy-in from all the impacted departments and communicated cutover plans repeatedly.  What more could he have done? 

In hindsight, the problem became clear. Although the team had agreement on the new processes from each impacted department, they had not addressed the concerns and needs of all impacted stakeholders.  There were within Customer Service who had serious concerns which had not been shared with the team.    

John’s experience is not that unusual.  Many project managers have made the costly mistake of thinking participation meant that the groups impacted by their project were engaged and in support of the project goals.    Fortunately, we have the knowledge and have the tools to minimize this risk in our projects.   This approach, commonly called Project Stakeholder Management, helps us ensure that all interested parties are actively involved and their relevant interests are addressed.    

What is Project Stakeholder Management?  

Project Stakeholder Management is a set of processes used to ensure that all groups and individuals who will be impacted by a project are identified and their concerns are appropriately addressed. 

Who are Project Stakeholders?   

Stakeholders are groups or individuals who will be impacted by the project or who have interest in the project outcome. 

Stakeholders may be internal or external.  Internal customers are members of the team or the business.  This would include:

  • the project requestor
  • groups/individuals   that will use the project results
  • groups/individuals that will need to change their processes because of the project
  • managers and executives
  • the project team
  • Subject matter experts

External stakeholders are outside of the business but will be impacted or have an interest in the project outcome.  Example include:

  • news agencies
  • government or regulatory organizations
  • vendors
  • partners
  • distributors
  • customers

This list of stakeholders is not comprehensive, but it is a good representation of the types of individuals and groups who may need to be engaged in a project.

A word of warning, project teams may feel some of true stakeholders have no reason to be involved and be tempted to ignore them in order to move the project forward more quickly.    If the interested group feels they should be considered and are not engaged, they can raise last minute objections and delay the entire effort. 

What are the Steps of the Project Stakeholder Management Process? 

Different authors will name the related processes and process steps with their own names, but the overall process is the same no matter what you call each step.   For our purposes, let’s use the processes as defined in the Project Management Book of Knowledge, (PMBOK).  The PMBOK identifies four Project Stakeholder Management processes

  1. Identify Stakeholders – identifying WHO are the stakeholders that needs to be involved in the project.  This includes people or groups who will be impacted, need to provide input, and/ or are interested in the results.     
  2. Plan Stakeholder Engagement – Developing and documenting HOW project stakeholders will be involved in the project. 
  3. Manage Stakeholder Engagement – WORKING THE PLAN.  This step involves working with the stakeholder and providing all necessary information to address their concerns and meet their needs. 
  4. Monitor Stakeholder Engagement – Routinely assessing stakeholder relationships and adjusting approach, as necessary. 

We will discuss each of these processes in more detail in future posts.