Article Archives
Article Categories
Articles
Three Must-Read Tips to Make Your Change Efforts More Sustainable
by Cassandra Worthy
Originally posted on July 21, 2024 on projectmanagement.com
As a project management professional, you’ve undoubtedly faced the frustration of seeing your change efforts spark initial enthusiasm, only to watch results gradually drift back to the status quo. It feels like you’re constantly pushing and pushing, with progress slipping away the moment you ease up. Sound familiar? Let’s explore how to make your change efforts stick for the long haul.
Key takeaways
- Define beliefs or thoughts required to sustain the change
- Define the actions those thoughts manifest and role-model them
- Never underestimate the power of consistency
Sustained Change Happens Through Sustained Beliefs
To achieve lasting change, we must focus on the beliefs that underpin our actions. When people truly believe in the necessity and benefits of change, their actions will reflect those beliefs consistently, even in your absence. Here are three tips to help your next change initiative become stickier.
Three "Sticky" Tips to Help You Sustain Change Adoption
Sticky Tip #1: Define Beliefs or Thoughts Required to Sustain the Change
Start by identifying the core beliefs necessary to support the change. These beliefs should tie into your organization’s existing value system to ensure they resonate deeply.
For example, if you’re implementing new software aimed at boosting efficiency, nurture the belief that “this software will enable higher efficiency.” Provide concrete evidence to back this up—share case studies, success stories from other departments, and data showing time saved or errors reduced.
Sticky Tip #2: Define the Actions Those Thoughts Manifest and Role-Model Them
Beliefs drive actions. Once you’ve defined the necessary beliefs, outline the specific actions that will manifest from these thoughts. Then, role-model these actions consistently.
If the belief is that new software increases efficiency, the actions might include regularly using the software, sharing tips on how to use it effectively, and celebrating small wins achieved through its use.
Example: As a leader, demonstrate your commitment by using the software yourself and sharing your experiences. Encourage team members to do the same and highlight their successes in team meetings.
Sticky Tip #3: Never Underestimate the Power of Consistency
Consistency is crucial in moving from transition to steady-state. It’s not enough to push for change initially; you must reinforce the new behaviors until they become the norm. Brands build their identity through consistent messaging and actions—your change efforts should follow the same principle.
Example: Think of a brand like Coca-Cola, which consistently reinforces its message of happiness and refreshment through every touchpoint. Similarly, ensure that every communication, action, and decision aligns with the new way of working. Over time, this consistency will solidify the change in your organization’s culture.
Conclusion
Making change stick requires more than just initial enthusiasm—it demands a strategic focus on sustaining the beliefs that drive new behaviors. By defining and nurturing the necessary beliefs, role-modeling the resulting actions, and maintaining unwavering consistency, you can transform fleeting wins into lasting success.
Remember, sustained change happens through sustained beliefs. Let’s make your change efforts stickier and more impactful.
By following these tips, you can enhance the longevity and effectiveness of your change initiatives, ensuring that your hard work leads to lasting improvements within your organization.
Pit Happens: 7 Ways to Navigate Out of Project Despair
Is your project showing signs of trouble and slippage? As the project manager, ensure you are the one steady at the stick so you can help everyone navigate through the “pit.”
Key Takeaways
- Watch for the warning signs
- Right-size the communication
- Keep talking
- Avoid being “love bombed”
- Stay focused
- Be specific with changes
- Don’t go back to the well too often
By Lonnie Pacelli/article originally appeared on ProjectManagement.com
Note: Lonnie is an Accenture/Microsoft veteran with four decades of learnings under his belt. He frequently writes and speaks on leadership, project management, work/life balance, and disability inclusion. Reach him at [email protected]
It was one of my earlier projects as a project manager.
I spent a lot of time planning the work out, calculating the critical path through the project, and getting everything ticked and tied prior to kickoff. The kickoff meeting went well with the exec sponsors. I set high expectations on my ability to deliver. The team was largely silent during the kickoff meeting, letting me do my thing.
The first few weeks in, I reported that we were on schedule and budget, and within scope; we were on our way to a stellar delivery.
At week four, a few of the tasks started slipping. “No problem, we can make it up,” I thought to myself. I reported that we were still on schedule.
The next few weeks saw more slippage, and some team members began expressing concern about our ability to meet dates. I reported that things were still okay, and we were working through a couple of minor issues.
After a couple more weeks, the concerns continued to crescendo, and one of the exec sponsors caught wind that there might be some problems on the project. He set up a meeting with me and some of my leads to deep-dive on what was going on. It was one of my most uncomfortable meetings at that point in my young career. I was the last one in the room to acknowledge there were problems.
The exec sponsor then talked with my manager and told him the project needed more seasoned leadership. A more senior project manager was assigned to the project, with my role being relegated to project administration under her leadership.
This experience burned an indelible mark in my psyche.
On my next project, my execution was very different. When I saw there were problems, I immediately pointed out that issues existed and the project was in trouble. My communication was frequent, voluminous, and broad. By golly, I wanted to make sure everyone knew we were in deep yogurt.
Again, an exec sponsor did a deep-dive with me and the team. I thought for sure I was going to be commended for raising the flag early.
I was replaced.
“What the &*%*#?” I thought after being benched.
I decided to seek out some advice from a more seasoned PM. This was a difficult thing for me to do because I was prideful and thought it was weak to seek out advice. Nonetheless, I swallowed my pride and had a talk with him.
It was a brutal and humbling discussion, but one that I needed to hear. I thought more about what happened on the two projects, the common threads, and what I could have done differently. It was then that I recognized that both projects hit a pit of despair, where things seemed to start off well—then started going south.
In the first project, I was in pit-of-despair denial, thinking the problems would somehow fix themselves. In the second, I was in pit-of-despair overreaction—that my job was to tell anyone who would listen that we were in trouble. Both were the wrong reactions.
I learned an important lesson: You can’t completely avoid pits of despair, but you can throttle how you manage through them.
I’ve seen the pit-of-despair phenomenon repeat itself many times with other project managers in my career, where things start off (according to the PM) great, then trouble happens, then the drama comes when the PM can’t work his or her way out of the pit.
Even with the best planning and risk mitigation techniques, sometimes pit happens. It’s unavoidable. It’s how the PM responds to the pit that is of paramount importance.
The bottom line is that the team, execs and other stakeholders want to know that the PM is in control and acting unemotionally, based on facts and data.
It’s like one of my favorite analogies experiencing turbulence on a plane: The captain talks in calm, reassuring tones, but also doesn’t hide the fact that turbulence is on the way. The captain’s job is to be realistic, focused and calm. It’s that same demeanor that the team, execs and other stakeholders want (and need) to see in the PM.
When I have seen other PMs (or myself) managing a project heading toward the pit, here’s how I’ve seen the most success in navigating out it:
- Don’t ignore the warning signs. Manage problems as either risks or issues with clear desired resolution; dates the resolution needs to occur; and the owner of the resolution.
- Right-size the communication. Don’t keep it to yourself, hoping it will go away; and don’t cry wolf. Articulate the problem, what’s being done about it and where help is needed, if any.
- Keep talking. At the end of each communication, let your audience know when the next communication will occur. Then follow through.
- Avoid being “love bombed.” Jittery execs, trying to help, can suck up a PM’s time with custom briefings and extraneous communications. Control the narrative through structured touchpoints and ensure the execs are getting what they need.
- Be focused, not nervous. This is a pet peeve of mine. Once I was running a high visibility project. After a status meeting, the general manager asked me if I was nervous. I said, “You pay me to be focused, not nervous.” “That’s a great response,” he said. Never say “I’m nervous” as a PM. Replace it with “I’m focused.”
- Be specific when a scope/schedule/budget plan of record needs to change. Sometimes navigating out of the pit means a plan of record change. Be clear and objective on what needs to happen and who needs to sign off on it.
- Limit the number of times you go back to the well. When a plan of record needs to change, ensure you are being as comprehensive and realistic about the rest of the project as you can in your ask. I’ve found that going back to the well with a plan of record change more than once significantly reduces others’ confidence in your ability to deliver. Plan of record asks should be realistic, not aspirational.
I’ve been through the pit of despair as a PM, consultant, team member, and exec stakeholder plenty of times. It’s uncomfortable, to say the least, for everyone involved. Ensure you are the one steady at the stick so you can help everyone navigate through the pit. Others depend on you.