Best Practices For Change Readiness

Most change initiatives don't fail because of the change that's happening, they fail because of how the change is communicated. I've watched brilliant restructurings collapse and transformative acquisitions unravel… Not because the plan was flawed, but because leaders were more focused on explaining the "what" and "why" than on how they were addressing the fears and concerns of the people on their team. People don't resist change because they don't understand it. They resist because they haven't been given a compelling story about their role in it. This is where the Venture Scape framework becomes invaluable. The framework maps your team's journey through five distinct stages of change: The Dream - When you envision something better and need to spark belief The Leap - When you commit to action and need to build confidence The Fight - When you face resistance and need to inspire bravery The Climb - When progress feels slow and you need to fuel endurance The Arrival - When you achieve success and need to honor the journey The key is knowing exactly where your team is in this journey and tailoring your communication accordingly. If you're announcing a merger during the Leap stage, don't deliver a message about endurance. Your team needs a moment of commitment–stories and symbols that anchor them in the decision and clarify the values that remain unchanged. You can’t know where your team is on this spectrum without talking to them. Don’t just guess. Have real conversations. Listen to their specific concerns. Then craft messages that speak directly to those fears while calling on their courage. Your job isn't just to announce change, but to walk beside your team and help your team understand what role they play in the story at each stage. #LeadershipCommunication #Illuminate

After multiple business and digital transformation journeys, one pattern keeps repeating. Technology rarely fails. Plans rarely fail. What fails is how change is absorbed once the program team steps away. Here are six lessons experience teaches—often the hard way: 1) Technology moves faster than people Systems can be implemented quickly. Ways of working don’t change at the same pace. I’ve seen teams technically enabled, yet still default to old habits because confidence and trust take time to build. 2) Progress comes from focus, not force The moments that moved the needle were never about pushing harder. They came from deliberately narrowing scope—fewer initiatives, clearer priorities, and protected execution bandwidth. 3) Decisions delayed cost more than decisions wrong Waiting for perfect alignment often created more cost than making a call and adjusting later. Momentum consistently favored teams that decided early and corrected fast. 4) Simplifying work creates more impact than adding tools The biggest gains didn’t come from new platforms alone, but from removing steps, handoffs, and unnecessary approvals before digitising the process. 5) Alignment matters more than intensity High energy without alignment led to friction. When business, IT, and operations agreed on outcomes and trade-offs, execution became smoother and resistance reduced naturally. 6) Clarity beats effort every time Clear ownership, clear success measures, and clear decision rights outperformed even the most hardworking teams operating in ambiguity. The real takeaway: Transformation is less about big launches—and more about what quietly changes in daily decisions and behaviors.

True progress in transformation relies less on sheer willpower and more on accurately identifying your current stage of readiness. Clinical observation reveals specific patterns. I often see people trying to force a habit before their mind is even willing to entertain it. They skip the vital groundwork and wonder why the behaviour does not stick. Real change happens in distinct stages. Recognising where you actually are prevents a lot of wasted effort. Here is the breakdown I use in practice. 1. Pre-Contemplation You are not intending to take action in the foreseeable future. You might be unaware that your behaviour is problematic or produces negative consequences. You likely feel that the cons of changing outweigh the pros. The task here is not action. It is awareness. Do not force a new gym routine. Instead, simply observe the friction points in your current day. Notice how you feel after certain choices. 2. Contemplation You are intending to change in the next six months. You are aware of the pros of changing, but are also acutely aware of the cons. This balance can produce profound ambivalence that keeps people stuck in this stage for long periods. The task here is analysis. Identify the barriers. What specifically is holding you back? Is it time? Energy? Fear of failure? Do not start the diet yet. Start solving the logic puzzle of your schedule first. 3. Preparation You are intending to take action in the immediate future, usually measured as the next month. You have typically taken some significant action in the past year. You have a plan of action, such as joining a health education class, consulting a counsellor, talking to your physician, buying a self-help book, or relying on a self-change approach. The task here is design. Set the environment. Clear the friction. Buy the walking shoes. clear the diary for better sleep. Make the default choice the healthy one. Most people fail because they try to jump straight to action while they are still in contemplation. They rely on motivation to bridge the gap. Motivation is unreliable. Structural readiness is not. If you find yourself stuck, stop pushing harder. Step back and ask which stage you are really in. The answer usually tells you exactly what to do next.

One of our clients—an international energy company—was undergoing a massive transformation, shifting from oil to e-mobility and sustainable fuels. The board’s mandate was clear: build a workforce ready for tomorrow’s challenges. During my first week, I visited a remote field site. Standing beside a team of engineers, I could sense their anxiety about unfamiliar technologies, stricter compliance audits, and the relentless pressure to deliver results. The old training modules? They barely scratched the surface of what these teams truly needed. We soon realized that off-the-shelf courses just weren’t enough. Understanding how people actually felt about new work processes was essential. I spent hours with field and office teams—listening, mapping out real pain points, and asking sometimes uncomfortable questions. How can we help our people make critical decisions on the ground? How do we build capability at scale, rather than just ticking compliance boxes? Once we gained that clarity, everything began to shift. Our team created an interactive learning journey—complete with role-based simulations, gamified crisis scenarios, and data-driven feedback loops. Each module put learners in the driver’s seat, dealing with real-life emergencies or optimizing EV infrastructure in realistic ways. It wasn’t all smooth sailing. Our first pilot exposed significant gaps—some learners felt overwhelmed, while others needed more hands-on support.We responded quickly by launching peer forums, field workshops, and targeted communications to bridge those divides. Within just 90 days, employees became noticeably more confident. Sites reported improved safety, efficiency, and even reduced downtime. This experience reinforced for me how real listening, strategic design, and a willingness to adapt can transform not just results, but the culture itself. I aim to make every learning initiative feel like a story worth living—for teams and for the business. #LearningAndDevelopment #EnergySector #Transformation #CriticalThinking #ProblemSolving #EVReady (Photo by <ahref="https://lnkd.in/gQWCp5Qf">Stockcake</a>)

The $3 million AI system sat unused for eight months. Perfect accuracy. Impressive speed. Zero adoption. I walked into that company to figure out what went wrong. Took me about an hour to see it: → Nobody told the operations team why they should trust a machine over their 15 years of experience → Nobody redesigned workflows around the new system → Nobody gave them a reason to change what was already working The executives thought they bought an AI solution. What they actually bought was expensive software that required massive organizational change and they skipped that part… This happens everywhere. I've seen it at Fortune 100 companies with unlimited budgets and at startups burning through their Series A. Same pattern. It's completely preventable. Before you spend a dollar on AI technology, answer three questions: → Can your team explain why this change matters to them personally? → Do your workflows support how the AI actually works? → Does your culture reward trying new approaches or punish deviating from the norm? If you can't answer those clearly, organizational readiness is your problem. Not the technology. The companies winning with AI figured this out early: → They spent months on change management before the first line of code → They redesigned workflows with input from people who'd actually use the system → They built trust before they built features Technology teams hate hearing this because it's not sexy. But organizational readiness determines whether your AI initiative transforms operations or becomes another failed pilot. Follow for the reality of AI implementation that nobody else talks about. Find out more at https://vist.ly/4gvpt #ai #aistrategy #leadership #aiimplementation #changemanagement #digitaltransformation #enterpriseai

Walking away from a change initiative: part 2. This is a summary of comments on my last post. The message from commenters is clear: walking away is not giving up—it’s about judgement, context & care for people. Many comments examine when & how to stop. Dan Rennie-Hale highlights governance, gateway reviews & culture so passion doesn’t eclipse reality & leaders can act when evidence says so. Paula Beattie links stopping well to psychological safety & early scoping of systemic & people issues. Marcella Bremer stresses understanding the starting culture so expectations match reality. Others describe the personal cost. Dr Penny Newman recalls being told to “never give up” & notes that persistence helps only when guided by data & emotions such as shame - there's no shame in stopping when costs outweigh benefits. David Wylie recounts the pain of pursuing a new service that never overcame structural resistance. Bree Katsamangos calls 2025 a "year of letting go" that opened new possibilities despite difficulty. Several reflect on system dynamics & power. Bob Bayles, MBA, MEd, FCPHR notes that perseverance is often rewarded long after it stops being responsible, especially when authority & incentives don’t match leaders’ risks. Andrew Williams connects this to adaptive leadership: knowing when the system isn’t ready or when we’ve become part of the problem. John-Paul Crofton-Biwer describes “zombie projects” that persist through mandate, not local will. Cognitive & cultural traps also emerge. Ish Ahmed links this to "sunk cost bias": continuing because of past effort rather than present value. Davina Jones recalls well‑meant but misplaced fixes like "yoga for burnout" instead of tackling root causes. Values & psychological safety run throughout. Stuart Miller & Gini Melesi warn of harm when leaders “spin” narratives that clash with stated values. Geraldine Johnston credit describes low self‑awareness & defensive leadership that turn change into reputation management. Rebecca Hewitt advocates external accountability to prevent slow drift from values. Some suggest alternatives to exit. Ivy Oandasan reframes walking away as shifting attention to more ready parts of the system. Audree F. reminds us some initiatives need new leaders, not closure. Philip Robinson emphasises breaking work into smaller pieces & engaging communities to learn & lead together. Finally, many call for learning from what stops. Elizabeth Bremner, BSc, MHA sees stopping as disciplined leadership that frees space for other work. Barbara Hercliffe urges documenting “what went well, would have been better if” to surface learning. Sharon Mickan, Emma Houghton & Helena Jackson note the timeliness of this reflection in health & care. Overall, walking away emerges as responsible change practice: evidence‑based, ethically aware, sensitive to power & readiness, grounded in values & learning‑focused. Thanks to all commenters.

Many organizations confuse project readiness with organizational readiness. They are not the same. A project can be technically ready. A solution can be fully tested. Training materials can be complete. Yet the organization may still be unprepared to adopt the change. Project readiness asks: "Is the solution ready?" Organizational readiness asks: "Are the people ready?" The distinction matters because employees do not adopt a transformation simply because it goes live. They adopt it when they understand it, trust it, and feel prepared to operate within it. The most successful transformations assess readiness long before deployment. They evaluate leadership commitment, stakeholder preparedness, change capacity, communication effectiveness, and organizational sentiment towards the proposed change initiatives. Readiness is not a milestone. It is a leadership discipline. And by the time resistance becomes visible, readiness gaps have often existed for months. Before asking whether the project is ready to launch, leaders should ask: Is the organization ready to succeed? #OrganizationalReadiness #Transformation #ChangeLeadership #ExecutiveLeadership #ChangeManagement #Leadership #TransformationStrategy

17 years. Hundreds of implementations. The successful ones all have one thing in common. The failures are missing the same thing. It's not the technology. It's not the training budget. It's not even the vendor. It's whether you have a PIER leading the change. 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 - They know the workflow 𝗜𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲 - They can actually move people to action 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 - They've done the job, not just studied it 𝗥𝗲𝘀𝗽𝗲𝗰𝘁 - The team trusts them Every successful change initiative I've seen has someone who checks all four boxes. Take away one? The whole structure collapses. I've seen companies assign brilliant IT people who've never worked the role... They can't answer the real-world questions. I've seen them assign process experts who have zero political capital. People smile, nod, and keep doing things the old way. Your vendor's customer success team can train all day long, but they can't hold your team accountable. Change needs an inside voice. Before you launch your next initiative - new CRM, sales methodology, whatever - ask one question: Who's your PIER? Because that person will determine your ROI more than any feature list ever will.

Every failed transformation has the same post-mortem. “Poor implementation.” It is the most expensive misdiagnosis in business. Implementation did not fail. The organization was never designed to absorb what it was handed. There is a difference between a capable organization and a ready one. Capability is what a system can do. Readiness is what a system is built to receive. Most organizations are extraordinarily capable. Almost none are structurally ready. The AI platform deployed in Q1 that became shelf software by Q3. The reorganization that produced the same outcomes with different titles. The strategy that was right, the investment that was real, the rollout that happened. And still. It did not take. Not because the thinking failed. Because the organization was never built to hold it. This is the pattern I have studied for three decades across complex operating environments. Innovation does not fail at the idea layer. It fails at the absorption layer. The structure between strategy and execution, the one no one designs on purpose, is the one that determines everything. I think of this as Adoption Architecture™. The discipline of building that structure intentionally. Not better change management. Not faster implementation. The organizational readiness to absorb, integrate, and sustain what is being built. The question every Board, founder, and investor should be asking before the next transformation investment is not: “Can we implement this?” It is: “Are we architecturally built to receive it?” Most are not. Most do not know it yet. #AdoptionArchitecture #Leadership #OrganizationalDesign

In my experience of working with organizations across Tata, Mahindra, and now through Ascen10X, I’ve observed one recurring challenge: 👉 There is no single “correct” path to transformation. 👉 But there is a wrong starting point for your context. And that makes all the difference! The Core Mistake Consultants Make: Most transformation efforts fail not because of poor execution…but because of poor entry-point selection. Consultants often: Apply a standard framework. Push a preferred methodology. Ignore organizational readiness Result? ❌ Resistance ❌ Superficial adoption ❌ No sustained impact The Reality: Multiple Entry Points Exist. A powerful insight from systems thinking is: Transformation is not linear—it is contextual and cyclical. There are multiple valid starting points depending on the organization’s reality: 1. Start with Vision (When organization is stable) Align leadership on future direction Build shared aspiration 👉 Works well when: No immediate crisis Reasonable internal trust exists 2. Start with Systems (For analytical cultures) Map processes, structures, and interdependencies Identify root causes 👉 Ideal for: Engineering / manufacturing setups Data-driven environments 3. Start with Team Alignment (When relationships are broken) Address trust deficits Enable dialogue 👉 Necessary when: Teams are misaligned Conflict is blocking progress 4. Start with Diagnosis (Most powerful but underused) Assess current reality deeply Use internal + external perspectives 👉 This is where tools like digital maturity assessments become critical (For example, evaluating CRM, operations, finance, AI readiness etc.) 5. Start from the Top (During crisis) Leadership drives change High urgency 👉 Works when: Financial / moral crisis exists 6. Start with Chronic Problems Solve visible pain points Build credibility 👉 Quick wins → Momentum 7. Start with Infrastructure / Processes Review systems like budgeting, planning, governance 👉 Useful for: Process-heavy organizations 8. Start with Quality / Excellence Initiatives TPM, TQM, Lean, Six Sigma 👉 Builds discipline + capability My Learning (After 30+ Years) The most successful transformations follow this sequence: 1. Diagnose deeply 2. Choose the right entry point 3. Build internal ownership 4. Create visible wins 5. Scale systematically ⚖️ A Critical Insight for Internal/ External consultants: You don’t transform organizations. You enable organizations to transform themselves. Please feel free to share your views. #Leadership #OrganizationalTransformation #BusinessExcellence #Consulting #DigitalTransformation #MSME #LeadershipDevelopment #ChangeManagement #SystemsThinking #Ascen10X