Why Culture Determines Whether Change Delivers Value

“It sounds like you don’t trust the other team to use the new system and process and do a good job.”

Organizations achieve value from AI not simply through adoption, but through cultures that foster trust, learning, accountability, and employee involvement. 

A recent Prosci® report, “Closing the Gap Between AI Use and Business Value,” finds AI adoption is increasing but adoption alone does not equate to achieving the intended business value. Organizations with “open mindsets,” rather than “cautious” ones, report stronger outcomes. Open-minded organizations trust AI, welcome employee input, and give employees autonomy in choosing AI tools, resulting in more helpful solutions. Cautious organizations do the opposite, often resulting in less helpful AI. Prosci’s® solution? Ensure AI fits the work, manage risk through appropriate safeguards, make decisions transparently, and enable experimentation and learning. 

I say the same dynamics that influence AI adoption also influence virtually every process or technology transformation initiative. Mindset reflects the culture of the organization or group. Culture influences if a change is embraced or resisted – regardless of what the change is. And ensuring employees are involved in the solution, understand risk and business value, and can experiment is good change management practice. 

Observation 

Me: “It sounds like you don’t trust the other team to use the new system and process and do a good job.”

Leader: “To be honest, no I don’t. What if they don’t update the system properly or on time? They haven’t communicated well and made errors in the past. What if they don’t manage the cases properly and cause delays?”

For this case, leadership supported the change – the existing state was ineffective and error-prone, and it was agreed the specific task will shift to another group. The teams were engaged in the design of the technology, process, and role changes. So, what was really going on here? Was this actually about trust, or about something else?

Some practices existed simply because they always had and no one had challenged the status quo. Most of the concerns and “what ifs” were based on one-off cases rather than day-to-day reality. The team was focused on the exceptions rather than the norm, which dragged down the entire process. The teams were also focused on individual completion and error rates and not on process performance or client value. 

When probed further, it seemed I hit another issue: accountability. Shifting the work from one group to another and designing the change with transparency meant what went unreported before would now be visible. These two teams would be equally accountable to deliver efficient and accurate client service. 

Success would no longer be defined by completion and error rates alone; the client experience now mattered. Yet the culture remained focused on error finding, and a bit of cover-your-ass (CYA), which shifted attention away from outcomes and seeing things holistically.

Resistance to change was not only about trust in technology or process and but also transparency and accountability. 

What helped? Together revisiting what the teams co-designed and who the work was for – the clients they serve. The groups, including leadership, required coaching on client and service-focused design. Success was no longer about how many cases an individual was doing (or getting wrong) but how efficient and helpful the client experience was – an outcome senior leadership was expecting to achieve. They needed to shift from a fault-finding culture to a continuous improvement and service-oriented one.

Trust and accountability for the new process were developed through a deeper understanding of team dynamics and culture. 

Trust the Process

When implementing digital or process change in an organization it is common to hear that the project must develop trustin the system or process. This task usually falls to organizational change management, assuming they are engaged in the change. Unfortunately, they are often asked to step in once all design decisions are made, user testing is underway, and an implementation date is set. It is no wonder that “lack of trust” is often cited as a key finding in failed change initiatives. 

What does “trust the process or technology” mean or look like? Just because an individual or team is trained and uses the new process or technology does not mean they have confidence in it. Meaning they do not necessarily utilize or embrace the change to achieve the intended business value. 

Trust

There are two sides to trust, the person/group doing the judging and the person/group, statement, or thing being judged. A judgement is based on the standards applied and how these standards are constructed. An individual or team can naively trust something and be ill-informed. Take the Theranos scandal for example. Investors, board members, and pharmacies blindly trusted Elizabeth Holmes’ claims about her blood-testing technology. Start-up culture and hype created the environment for a grand deception.

Individuals can also mistrust due to groupthink or group allegiance – blindly adopting distrust for something because their leader or group does. Consider the comment, “I don’t trust them to do the right thing.” Followed by, “Have you talked to them about why they make those mistakes?” The answer, “No. It’s always been like that according to my boss.” 

In both examples above, the judgement standards applied by the group went untested.

We also see these trust dynamics playing out across society today, as increasingly polarized groups are influenced by misinformation spread through social media.

Trust and Organizational Change

Building trust in a change and ensuring it adds value begins with inquiry: understanding its implications and identifying the support individuals and groups need to adopt it effectively. However, asking can result in information a leader does not want to hear or worse, silence (which is falsely interpreted as acceptance). This is especially true if the environment is already laden with failed change initiatives, low employee engagement, and limited transparency. Although difficult, this situation can be overcome with an investment in people. 

In a highly engaged learning environment, individuals more readily accept change, trusting their concerns will be heard and addressed – even though the outcome may not be what they want to hear, they are given the opportunity to discuss the change and work through the implications. If employees are not worried about losing their jobs for speaking up, they may offer ideas that propel change. A recent example of successful human-centred change is Ikea’s adoption of AI tools.

A few things to consider when addressing trust in organizational change:

  • Involve change management at the onset of change initiatives. (Do I really need to say this?) 
  • An organizational change requires skilled individuals who understand organizational culture – and don’t just follow established change frameworks or checklists. 
  • Ensure the change team has the skills to engage and coach team members and leaders. Ensure the leaders also have the skills to coach team members and negotiate with other leaders.
  • Understand the two sides of trust. Determine what must be questioned and be open to the findings. Ask why, a lot! (See my previous post about this.)
  • Understand how the culture is influenced by what is measured (accountability!). Like begets like. Albeit not all leaders or organizations care all that much about culture or employees. So be it, the data shows how this negatively impacts the bottom line. 

Organizations often think trust in a system or process happens once everyone is trained or is something employees must develop after the change is implemented. In reality, trust is created during design through transparency, involvement, learning, and accountability. 

Trust goes both ways, between employees and leaders.