Change Management at the Project Level

Change management's purpose is clear: to ensure that changes deliver intended results and outcomes by addressing one of the most critical elements of successful change, the people side of change.

Employee adoption and usage are the bridge between a great solution and ultimate results. In practice, change management plays out on several different levels within the organization.

• Enterprise level – an organizational capability and competency
• Project level – a benefit-realization and value-creation measure applied on particular initiatives
• Individual level – an approach for enabling one person to change successfully

The Goal of Change Management at the
Project Level

Change management at the project level is about ensuring that a project achieves its intended results and outcomes by supporting the individual transitions required by that project. When you install a new technology, employees must adopt and use it to deliver value. When you implement a new process, employees must adopt and use it to deliver value. Project-level change management provides the specific strategies, plans, actions and steps that focus on impacted employees and work in alignment with a project deployment.

Change management, at the project level, can be applied on any project or initiative that impacts how employees do their jobs. Some changes impact hundreds of employees while others impact thousands. Changes can be driven by external factors, internal factors or some combination of both. Changes can impact processes, systems, tools, organization structures or job roles (or any combination thereof). But if a change requires employees to do their jobs differently (by exhibiting new behaviors, following new processes, using new tools), then there is a role for project-level change management.

From the project perspective, change management is the set of activities (the processes and the tools) applied to a particular project or initiative to drive adoption and usage. But, is that how you would tell a project team what change management is?

What is Change Management at the
Project Level?

As change management practitioners, it is important that we understand what change management is and, more importantly, how we present what change management is to the project teams we work with.

We could begin with a technical definition:

Change management is the application of a structured process and set of tools to manage the people side of change to achieve a desired outcome.

–Prosci's formal definition of change management

While this is accurate, it may not be the most effective way to describe what change management is if our goal is to build commitment and support for change management. Think about the definition above compared to these:

Change management is a…

• Benefit-realization tool
• Way to ensure achievement of results and outcomes
• Approach for driving greater ROI
• Vehicle for optimizing adoption and usage
• Tool for avoiding excessive project cost
• Approach for mitigating project risk

While these statements don't tell you exactly what change management is, each conveys what change management is in the context of what our audiences (project managers and senior leaders) care about and what concerns them: benefit realization, results, outcomes, ROI, adoption, usage, cost and risk.

So, to answer to the question, "What is change management at the project level?" we need to know who we are speaking to. To the project managers and senior leaders we are working to engage, change management is a solution to a problem they are experiencing (such as projects not delivering intended results and outcomes). When defining change management to a change management practitioner, change management is the structured approach for creating a strategy to drive employee adoption and usage, so  projects achieve intended results and outcomes.

Applying Change Management at the Project Level

While the best definition of change management might vary depending on the audience, benchmarking research indicates some fairly straightforward steps for applying change management at the project level. Here are four tips for getting started on applying change management:

1. Apply a structured methodology

Over the last decade, the discipline of change management has evolved and matured. The "soft and fuzzy" side of change is now addressed with rigor, structure, process and tools. Using a structured methodology helps you be direct and targeted and helps you avoid missing key considerations.

2. Customize and scale your approach

In change management, one size does not fit all. The change management strategy and plans for an incremental change impacting 50 employees will look very different than the plans for a radical transformation impacting 5,000 employees. You can follow a similar change management process, but the resulting outputs must be scaled and customized based on the change itself and those being impacted. 

3. Dedicate (or find) a resource 

If no one is assigned to change management, chances are it won't get done. Prosci's research shows a direct correlation between having a dedicated resource and change management effectiveness. A dedicated resource provides focus and a single point of contact. The resource can be someone on the team or someone supporting the team, but there needs to be someone focusing on change management.

4. Work in collaboration with the project team 

Change management cannot be applied at the project level in a vacuum without engagement from the project team. Clearly articulate the relationship between the project team and change management resources. Define the roles and responsibilities. Work deliberately to create a partnership with a singular goal in mind—delivering the intended results and outcomes of the project.

Apply Change Management to Organizational Projects and Initiatives

At the project level, change management is a benefit-realization and value-creation measure applied on particular initiatives. It is a structured approach to create customized and scaled strategies and plans to drive employee adoption and usage. It is a way to ensure that a project achieves intended benefits and outcomes, realizes ROI, mitigates costs and risks ,and creates value. It is a way to ensure that projects and initiatives are more successful.