Have you ever heard a stakeholder on your project say, “I’m completing the template you guys asked me to complete?” Or maybe you’ve heard, “I’m completing the steps in your process.” Do you know what’s wrong with both of those sentences? They didn’t say “our;” they said “your.”
Sometimes we think we’ve done a good job of rolling out great project and change management best practices. We feel like they really “get it,” and then they throw this “you” and “your” stuff at us. Watch out: The minute you aren’t looking, “your” process is going to fall apart. Why? Because it’s your process. It should never, ever be your process.
The key to sustainability in project and change management best practices is ownership—their ownership, not yours.
Many times, leaders will put one person in charge of creating best practices for the organizations. OK, so that in and of itself is not an issue. What that person does next is what will determine ultimate success or failure of the implementation of these practices.
When you are tagged as “the one” to put all this stuff in place, it’s important to remember that you are accountable, but that doesn’t mean it needs to be a one-person show. You must get others involved and find a way to give them a stake in the outcome of the effort. If you don’t, you run the risk of a few things happening:
- They make you out to be the “bad guy,” trying to “make” them change the way they have “always done things.”
- They ignore you.
- They only behave when you are watching.
- When you are off to another assignment, the whole thing falls apart.
- Your leadership starts to wonder if you can handle this effort or sees you as ineffective.
- …and many others.
Instilling Better Ownership
So, how do you avoid these issues? You make it their process from the beginning.
Although you are the one charged with making the changes, it doesn’t mean that you must do it in your tiny workspace huddled over your computer by yourself. Get out there and engage others. You don’t necessarily know what will work best in the organization (and if you think you do, you are probably wrong, at least partially). Start pulling together stakeholders to listen before talking. Ask questions about what’s working for them and where they have pain points. That discovery process will help you do a few things:
- Engage them in the process, making it “our” instead of “your” process
- Help them feel heard and understood
- Develop a more robust solution that incorporates the real world they are working in
- Give you a chance to tie their desires and pain points to the process you want to roll out
- Give them a chance to be a part of the solution development (FYI, this is how you build early adopters and change champions.)
- Ensure the process becomes ingrained in the way they operate, as valued and engaged stakeholders
- Show your leadership team that you are a leader—not just a doer—and you can engage others successfully to implement change (Watch out world—here comes that bigger assignment!)
- … and many others
And If You Still Need More Convincing…
This way also helps you share the workload with others. You can engage a group of stakeholders in the process of interviewing others to get their input, gathering examples of things that work, developing prototype processes or templates and tools, and ultimately make the process of rollout much easier because it’s a team of people that are all early adopters doing it with you.
The moral of the story with creating any change is to do the change with them instead of to them to ensure that it becomes theirs and not yours.