Culture and Mindset Are Not the Same Problem, and Transformation Fails in the Gap Between Them

Digital transformation is usually framed as a technology program with a culture workstream attached. That framing misses where most programs stall: in the gap between an organization’s culture, which changes slowly, and the mindset the new way of working requires, which has to change quickly. Closing that gap is a design task for the CIO, not a communications exercise.

The prevailing view treats culture as the soft side of transformation, something to be managed once the platform decisions are made. That view explains why change-management budgets exist. It does not explain why programs with sound technology and committed sponsors still stall. I would argue that culture and mindset are distinct, that they pull in different directions during a transformation, and that the CIO sits at the point where that tension becomes visible.

Two different things that get treated as one

Culture is the set of beliefs and practices an organization has accumulated over time: how decisions are made, what is rewarded, what is tolerated. It is deeply ingrained and changes slowly, even as new technologies arrive.

Mindset is the orientation people bring to new work: openness to change, attention to the customer, willingness to experiment and take calculated risks. A digital mindset is dynamic. It develops through exposure to new tools, processes and results.

The two matter differently. Culture determines what an organization will sustain. Mindset determines what it will try. A transformation needs both, and they are rarely aligned at the start.

Executives already recognize the weight of the first. In PwC’s Global Culture Survey 2021, 66% of senior executives (C-suite and board members) said culture is more important than strategy or operations to an organization’s success (PwC, 2021).

Where the gap shows up

The disconnect is easiest to see between technical teams and the rest of the organization. Technical teams tend to prioritize iteration and efficiency. Functions rooted in established practice tend to prioritize stability and predictability, which they have long been rewarded for. Neither is wrong. But when a transformation asks both to work in the same way, the difference surfaces as friction, delay and quiet workarounds.

The mechanism runs like this:

1. A transformation introduces tools and processes that assume a digital mindset.
2. The surrounding culture still rewards stability and penalizes visible failure.
3. People who experiment are exposed; people who wait are protected.
4. Initiatives fragment into pilots that never become how work is done.
5. The organization concludes that “the culture resisted”, when the culture did exactly what it was built to do.

What the CIO can actually change

The CIO cannot change culture by declaration. What the CIO can change are the conditions under which mindset and culture meet.

• Shared practice across functions. Extending agile ways of working beyond IT gives the organization a common language and a common rhythm. McKinsey’s work on culture for a digital age makes a similar point: the culture has to perform across the organization, not only inside its digital teams (McKinsey).
• Protected experimentation. A “fail fast, learn faster” approach only works if failure inside agreed limits is not penalized. McKinsey’s research on organizational transformations found that completely new initiatives succeeded 64% of the time, against 31% for repeats of past ones (McKinsey).
• Change programs tied to how decisions are made. Leadership training, communication and engagement matter, but only when they change what is measured and rewarded.

What follows

The practical implication is to treat culture and mindset as two separate design problems with one owner. Culture is shaped through incentives, decision rights and what leaders tolerate. Mindset is shaped through exposure, practice and visible results. A transformation that works on only one will produce either enthusiasm without staying power or stability without change.

Technology is not a support function, and neither is the work of making it stick. Where would your organization punish the behavior your transformation depends on?