#change-management

#change-management

The pace of change in the workplace is relentless, especially when it comes to navigating AI transformation. I've spent my career helping organizations adapt, and I can say this with certainty: the real difference between teams that thrive and those that stall isn't the toolset-it's how effectively they manage change. And the urgency to get it right has never been greater. Without the right change management, investing in new technology is not going to give you the results you seek. Leaders need to think deeply about how work gets done, how teams collaborate, and how value is created from new tools.

There's just one problem, though: While many know how to declare an initiative, far fewer understand what it takes to carry the project through the friction of daily workflows. What separates those rare successes from the long list of initiatives that fade into half-measures is not only leadership and resourcing, but also the way organizations adapt, measure, and learn as they go.

My first experience with technology adoption for a law firm was probably in 1993. I was attending a partner meeting for a top Am Law firm to demonstrate the first version of Lexis on Microsoft Windows. My pitch was strong enough to get a partner to grab the mouse and try for himself. The problem was that he had never used a computer before. When the partner grabbed the mouse, he accidentally highlighted half the screen. Embarrassed, he walked away without saying a word.

When you think about growing your business, it's natural to picture new customers, more sales, and bigger teams. But growth today looks a little different than you might be used to because it also involves making sure your people can work effectively with the systems you put in place. That balance is what makes the difference between growth that feels sustainable and growth that leaves everyone stretched.

The execs kick things off: Why are we here? What will this achieve? Then the consultants descend. Let the process mapping begin. Swim lanes. Handoff points. Decision makers. Stakeholders. RACI charts. Today is all about people and process. The message is clear: fix the people side first - because until you do, no technology will save you. No more silos. No more pain points. Content, data and insights delivered on time and on spec.

Organizations can achieve a threefold improvement in project outcomes simply by applying some degree of change management, according to a recent study from Prosci.

Changes from the C-suite often land as abstract ideas that feel disconnected from the reality on the ground. It's up to team leaders to help people see what it means for them.

Gary Chapman created the love languages model to address romantic partners' miscommunication in expressing love, leading to insights in relational dynamics.

COOs perceive law firm partners as the primary barrier to change, indicating that partners disregard the improvement recommendations put forth by their COOs.

People who are presented with the risk of losing a current position or status are far more likely to engage with the task at hand, motivated by the fear of failure.

As the leader, it is not your job to have all the answers, only to facilitate your team in finding them. Actively engage your employees in the problem-solving and change-planning processes.

Engineers often overlook the human and organizational dimensions of software migrations, misjudging them solely as technical projects while these elements significantly affect outcomes.

The challenge in developing or updating a website isn't just stakeholder management-it's change management.

During SAP Sapphire, Maura Hameroff clarified that "Rise with SAP" and "Grow with SAP" are support programs aimed at assisting customers in their ERP journey.

Using organizational psychology helps ensure the success of change management projects by emphasizing skills like curiosity, empathy, and systems thinking to aid transitions.

Growth is painful. Change is painful. But nothing is as painful as staying stuck where you do not belong.

"Microsoft has suffered a run of backend changes affecting functionality recently, leading to multiple outages. We need to enhance our detection and response to similar events."