I spent twenty years discovering that the problem was almost never what people said it was.

I started as a software developer and architect, convinced — like almost everyone who comes from technology — that projects failed for technical reasons: fragile architecture, the wrong technology, poorly specified requirements. It took me a few years to see the pattern. The technology was almost always ready; what stalled was something else. People who hadn’t been brought along, processes nobody wanted to change, power nobody wanted to give up.

One scene sums it up. Early in my time at one of the Big Four, I worked on an RPA implementation at a major Brazilian food manufacturer. The technology was mature — nothing about it was experimental. The project stalled anyway: we designed a grand transformation when the context called for fast, incremental delivery, and bureaucracy and a volatile environment did the rest. The failure wasn’t in the robot. It was in the adoption strategy — and that lesson cost me enough that I never forgot it.

That is the thesis behind everything I think and write: technology only becomes value when it leaves the technical fiefdom and is absorbed by people and processes. The bottleneck is rarely in the code. It is in the organization that has to change for the code to be worth anything.

I built my career on that frontier — between technology, business, and people — at global consulting and technology firms, connecting worlds that rarely talk to each other: the large ecosystems (SAP, Oracle, the Big Four) and the organizations trying to extract value from them. In 2014, when Big Data was still a concept fresh out of a McKinsey report, I worked alongside data scientists unifying nationwide corporate registries and geolocation data to model purchase propensity — before the market had a name for it.

Along the way, I learned to separate two things that large projects treat as one: delivering the plan and transforming the organization. Milestones met on time and on budget are real merits — but they measure execution, not change. The disruption that matters demands strategic rethinking and cultural discomfort, and it rarely fits a schedule that has already tied every phase to a payment.

And it wasn’t just lived experience. I went on to study the question properly, in an MBA at FGV, one of Brazil’s leading business schools, expecting to run into problems of method or tooling. I interviewed senior executives at a major consultancy about why sound long-term relationship practices never took hold — and what surfaced, once again, was culture and governance: conflict aversion, lack of transparency, incentives that didn’t reward partnership. I stopped merely sensing the pattern and examined it with method.

Today my focus is AI adoption in the enterprise, and the same conviction applies — now with more force. AI is treated as a tooling problem when it is, above all, an adoption problem. Choosing between AI, analytics, or machine learning is the easy part. The hard part is getting the organization to understand that artificial intelligence is a means, not an end — and that using it seriously demands change in culture, process, and governance. That is where value is created or lost.

This blog is itself an exercise in the thesis. I didn’t write its code by hand — nor did I delegate judgment to the machine. I used AI the way I would use a senior consultant: I hired it, challenged it, and audited it. I defined the architecture I required — a flexible structure, code accessible in my own development environment, established tooling instead of reinvented wheels — rejected proposals that didn’t serve me, and reviewed what was delivered. That is the difference between adopting AI and merely using it. And that difference is exactly what I write about.

I keep studying to sustain that bridge: an MBA in Data Science, AI & Analytics (USP/ESALQ) and executive programs in AI Business Leadership, joining a technical origin to a broader view of organizational transformation. That origin is what lets me move with legitimacy between the language of business and the real architecture of solutions, without getting lost in either.

This space gathers what I think about transformation, technology, and the human side of change. Some of these essays are recent. Others I wrote nearly a decade ago, and they remain — unfortunately — current. Proof that the bottleneck was never technical after all.

— Waldemiro “Miro” Lustosa