Culture Is the Constraint: Why Technology Alone Doesn’t Deliver Outcomes

In 1974, the U.S. government mandated seatbelt interlocks in new cars, technology that prevented a vehicle from starting unless the driver buckled up. It functioned exactly as intended. It also failed almost immediately because consumers rejected it, dealers disabled it, and Congress repealed it within months. Not because the technology was flawed, but because people were not ready.

That pattern hasn’t changed. We continue to treat technology as the driver of transformation, when in reality technology enables, but culture determines outcomes.

Technology leaders don’t typically struggle with building or buying the right technology. The real challenge is getting meaningful adoption at scale and sustaining it. That gap exists because we often treat deployment as a technical event rather than a behavioral one.

Every significant technology initiative from ERP, AI, cybersecurity controls, anything generally with the ‘digital transformation’ narrative follows the same pattern, clear business case, technically sound solution, structured plan, yet adoption lags, fragments, or stalls.

We tend to troubleshoot the system. We should be diagnosing the culture.

What the Data Already Shows Us

You can see the same pattern play out repeatedly.

The printing press was around for years before it really changed society, and only took off when the social, economic, and institutional conditions were ready for it. The internet didn’t simply replace existing behavior; markets and users gradually shaped it to fit the way people already lived and worked. Nuclear energy has always been as much about trust and public perception as engineering. And, COVID vaccines reminded us that even a major scientific breakthrough doesn’t create impact on its own if people don’t trust it enough to adopt it.

Technology usually doesn’t break down because the tech is bad, it breaks down when people, habits, and motivations are unaccounted for.

Why This Matters Now as Much as it Ever Has

The pace of change feels, and often is, faster than any of us have seen. We’re not rolling out one solution at a time with adjustment periods in between.

Businesses and leaders are managing overlapping waves of transformation from AI and automation to cloud consolidations, digital operating models, and governance initiatives. Each of these carry significant behavior change, which along with simultaneous delivery needs, exceed the organization’s capacity to absorb them. 

When that happens, predictable risks emerge:

1. Selective Adoption – capabilities concentrate with early adopters while the broader organization lags
2. Operational Friction – workarounds, shadow IT, and inconsistent processes increase
3. Trust Degradation – employees disengage, and initiatives become compliance exercises rather than value drivers

At that point, technical debt becomes cultural debt. To gain sustained value from technology investments, the role of technology leaders extends beyond delivery into cultural integration.

That requires a shift in focus, starting with going from communication to narrative.

People may be introduced to systems, but they engage with the stories those systems tell about what they mean for them and for the company. If the dominant narrative around a technology is unclear, negative, or inconsistent, adoption will reflect that no matter how strong the implementation is.

Clarity comes from explaining what problem technology solves, who it helps, and what changes people should expect. Without that, people fill in the blanks and often default to skepticism.

Involving end users, business units, and impacted teams early doesn’t slow delivery, it reduces rework and increases adoption. It also surfaces edge cases and operational realities that don’t appear in design assumptions. The goal should be relevance, not consensus.

Trust Determines Adoption

Policies, controls, and standards are critical, but they don’t drive behavior on their own.

Trust in the intent behind the technology and the teams deploying it determines whether people use it as designed or work around it. That trust is built through:

• Transparency in decision-making

• Consistency in application

• Visible accountability

Enabling a broad form of company literacy, including decision transparency, what risks exist and how they are managed, to what tradeoffs are needed, provide necessary context that enables meaningful adoption.

Before scaling any initiative, it is worth testing five areas:

• Narrative – Do people understand why this matters?

• Trust – Do they believe in how and why it’s being implemented?

• Inclusion – Were the right stakeholders involved early enough to shape it?

• Friction – Where will resistance predictably occur?

• Integration – How does this become part of everyday work?

If those aren’t addressed explicitly, they will typically show up as delays, workarounds, or underperformance.

In the end, every technology investment is a bet on behavior change. The engineering problem is usually solvable. The human problem is where outcomes are won or lost.