Reflections on Adapting to Change in Projects

When I started working in SAP 25 years ago, I thought change management just meant telling people when we go live. Draft a few emails. Put together a timeline. Send out a cutover checklist. That was it. Back then, I thought change was about communication. Now I know better. After being part of so many SAP projects, here’s what I’ve come to believe: The real challenge isn’t configuring SAP. It’s helping people feel safe enough to change with it. Because behind every transaction is a human habit. Behind every process is someone’s comfort zone. Behind every workshop is someone silently thinking: “Will I be able to keep up with this?” Change management isn’t about getting users to accept SAP. It’s about understanding what they’re afraid of losing — and designing the journey so they don’t have to lose it all at once. The best SAP projects don’t force change. They inspire it. They meet users where they are. They guide them patiently to where they need to be. They create space for transformation — not just implementation. If you asked me the most critical success factor for SAP today? It’s not scope control. Not testing. Not training. It’s how well we support the people who need to live in the system every day. 💬 What’s one thing you do to help users truly adapt during an SAP project? #SAP #SAPS4HANA #ChangeManagement #ERPTransformation #SAPConsulting #DigitalLeadership #OrganizationalChange #ASARDigital #UserAdoption #HumanCenteredDesign

I still can’t believe how many Controls Engineers out there won’t even write their code prior to commissioning… let alone test it.   I mean, I can empathize with how demoralizing it is to arrive onsite, with beautiful code in hand, ready to conquer the world - only for the scope to completely change as you walk through the door… I’ve been there myself, more times than I can count.   What I cannot support is the attitude of, “It’s going to change anyway, so why bother?” This mindset is an unhealthy mix of arrogance, apathy, and dejection, often built upon decades of experience with poor, even nonexistent, project management.   Rather than succumb to this defeated state, what can we do?   --- Focus on What We Can Control Scope changes are inevitable, but the effort we put into preparation is completely in our control. Writing and testing our code beforehand might not prevent changes, but it gives us a solid foundation to adapt quickly. Pivoting from a structured starting point is far easier than scrambling to build one under pressure.   --- Expect Change, but Plan for Quality We know things will change - that’s a given. But planning for change doesn’t mean sacrificing quality. Modular, reusable code and simulation environments only make the modifications easier and help ensure that we are delivering value, even though the ever-evolving requirements.   --- Shift Our Mindset This isn’t about writing "perfect" code - it’s about respect for our clients, end users, and craft. Starting with, “Why bother?” sets the stage for mediocrity. Starting with, “How can we be better prepared?” creates opportunities for growth.   --- Fight for Change Blaming poor project management, unclear scopes, or rushed deadlines is easy… but it doesn’t solve our problems. Instead, take charge. If the calls aren’t happening, organize them. Push for reviews with the operators, management, and maintenance teams to uncover potential changes earlier.   Get ahead of the shifts instead of reacting to them. Advocate for what matters: detailed scopes, realistic timelines, and access to simulation environments. Speak up in kickoff meetings, ask thoughtful questions, and document everything. Fighting for change isn’t about pointing fingers - it’s about stepping up to create the structure and clarity our clients deserve. So, while we’ve all been burned by poor planning or surprise changes, it’s how we respond defines us.   How do you balance preparation with the unpredictability of commissioning?   #Automation #Engineering #ContinuousImprovement #ProjectManagement

Project Chaos 5 Key Takeaways 1. Embrace Chaos: Project chaos is inevitable. Embrace it as an opportunity to learn and grow rather than viewing it as a failure. 2. Adaptability is Key: When plans go awry, the ability to adapt and find alternative solutions determines the ultimate success of a project. 3. Cultivate Resilience: Whether it's tight budgets, missed timelines, or limited resources, resilience will keep you and your team motivated to overcome any obstacles that arise. 4. Learn from Failures: Mistakes and setbacks should be perceived as learning opportunities. Use these instances to refine your strategies and processes. 5. Lead Through Uncertainty: Great leadership is defined by guiding your team effectively through adversity. Remember, it's your response to chaos that shapes you as a leader. =============== During my time as a Project Manager at a start-up, I experienced the essence of project chaos firsthand. We were tasked with launching a new software product within a tight deadline. Our meticulous plan seemed flawless. However, halfway through, one of our key developers fell ill, throwing a wrench into our timeline. In the face of this adversity, rather than succumbing to panic, we embraced the chaos. We shifted roles, redistributed tasks, and even learned new coding languages to keep our project on track. The experience was challenging, but it forced us to be resourceful and adaptive. Another instance that redefined my perspective on failure was a project that went over budget due to unforeseen market fluctuations. Instead of viewing this as a setback, we took it as a learning opportunity, revising our budget estimation process and incorporating buffers to accommodate such variables in the future. These experiences made me realize that chaos is not an obstacle but an opportunity to grow. It has shaped me into a more resilient leader who can adapt to changing situations and guide my team through adversity. So, remember: When a project goes awry, don't panic. Embrace the chaos, adapt, and let it mold you into a more effective leader. ❗How Can I Help You? I'm Justin, a PhD and PMP holder with 21 years of project management experience, mentoring Fortune 500 teams. I've trained 4,000+ professionals, and now I focus on helping project managers in swiftly advancing their skills to enhance their career trajectories, surpass competitors, and evolve their project skills into becoming highly desirable leaders. 👇 Join my upcoming cohort for using ChatGPT for Project Management! lnkd.in/dmA-dNjS #business #management #projectmanagement #innovation #operationsmanagement