When visiting clients to start a new project, it's interesting to find out that the stakeholders have been excluded from the planning or discovery sessions. If the stakeholder is not included, does that make it an IT project? Is there such thing as an IT project? What's the potential risk of NOT including stakeholders? What are the advantages of including stakeholders in the beginning stages? Do you want to eliminate process gaps, increase adoption, reduce anxiety, confusion, and frustration during your next project? Keep reading...
I am a BIG fan of the IT community. They bring a lot to the table:
But, they DO NOT establish business requirements. Stakeholders establish business requirements. For this reason, the BEST case scenario is to have stakeholders involved in the initial planning. At the end of the project, the stakeholders are the employees who use the new software, new hardware, and new processes. Stakeholders should be involved in the discovery sessions to communicate their needs, wants, and concerns. In addition, including them in the early stages gives them the opportunity to make suggestions.
Excluding stakeholders can create significant risk and possibly cause the project to take an unforeseen turn leading to:
We have known for decades that people who participate in decision-making that affects their work feel a higher degree of ownership and commitment to that work. We also know, where more people are involved in a joint process of common interest, the quality of output is higher. The same is true of strategic planning. High involvement in the process, by a variety of stakeholders, tends to generate better outcomes and a greater sense of ownership.
Have you ever wondered why people in the workplace resist change? Changes at work can be emotionally intense and create the following as a result:
Experts have noted that the experience of going through change at work can mimic that of people who are suffering from grief over the loss of a loved one. Because change can be so physically and emotionally draining, it often leads to burnout. As a change agent, you should try to mitigate as much of these feelings of grief as possible. Change is a process, not an event. Involving the stakeholders will relieve or eliminate some of the feelings that accompany the change process.
Engaging employees in the planning process itself helps build ownership within the organization. It’s nearly impossible to get where you want to go without a goal, a roadmap, and organizational commitment. Without a goal, you can’t align the organization to a common desired outcome. Without a roadmap, you have no idea what options are available to get there. And without commitment, you cannot ensure that your stakeholders will move in the direction you need to go. Building commitment through stakeholder engagement is an increasingly important element of the strategic planning process.
Greater understanding leads to greater ownership.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.