The Same Question, Two Rooms

I have spent real time in two rooms that are not supposed to resemble each other. One is the early-stage startup, where a handful of people are trying to will something into existence with no resources and no guarantee anyone wants it. The other is the enterprise transformation, where a large organization with every resource is trying to change how tens of thousands of people work. By every obvious measure these are opposite situations. And yet, having sat in both, I kept noticing that the conversations rhymed. The same anxieties, the same failures, the same hard-won lessons, in rooms that share almost nothing on the surface. For a long time I treated that as a curiosity. I've come to think it's the most important thing I know about either one.

Why they look like different worlds

The surface differences are real, and they're what keep most people from seeing the overlap. A startup has no resources and nothing to lose; a transformation has enormous resources and a great deal to lose. One is measured in runway, the other in budget cycles. One fights to be noticed at all; the other fights the weight of its own history. They use different words, attract different people, and tell themselves they're playing entirely different games. A founder and a transformation leader, put in a room together, would each assume the other's job bears no resemblance to their own.

They'd be wrong, and the reason they'd be wrong is worth taking seriously.

The same problem underneath

Strip away the surface and both people are doing the identical thing: trying to make something new take hold among people who did not ask for it and have every reason to resist.

The founder is introducing a product to a market that is indifferent by default. The transformation leader is introducing a new way of working to an organization that is comfortable by default. In both cases the enemy is not a competitor and not the technology. It's inertia. The status quo, which is always free, always available, and always good enough in the eyes of the people you need to win over. Both are fighting the gravitational pull of the way things already are, and both discover that being obviously better on paper does almost nothing to overcome it.

Which means both are really doing the same work, the work that has nothing to do with the product or the initiative and everything to do with people. Understanding what people actually need, as opposed to what you assumed they need. Earning trust from people who are fine without you. Getting evidence before you bet everything. And changing behavior against resistance, which is the hardest thing in either room and the thing neither job is actually about on paper. The artifact, the product in one room and the transformation in the other, is just the vehicle. The real subject in both is human behavior change under uncertainty.

Why the overlap is more than coincidence

It would be easy to call this a nice parallel and move on. I don't think it's a parallel. I think it's the same problem wearing two costumes, and the reason is simple: both are fundamentally human problems, and the human layer does not care how big the room is.

A person decides whether to adopt a new tool, trust a new system, or change how they work for reasons that are remarkably consistent whether they're one of five people at a startup or one of twenty-five thousand at an enterprise. Do I trust this? Does it respect my judgment? Is my world better or just more disrupted? Did someone I believe stand behind it? Those questions are asked in both rooms, by the same human wiring, and the answers determine success in both. Scale changes the logistics. It does not change the fundamental unit, which is a person deciding whether to change. That's why the lessons transfer, and why someone who has genuinely learned one room has learned most of the other without realizing it. The constant across both is people. Everything else is a variable.

I'll resist re-arguing a related point I've made elsewhere, that the founder and the operator each learn things the other needs. This is the deeper reason that's true: the lessons transfer because the underlying problem was always the same one.

Why this is suddenly everyone's problem

For most of my career, this overlap was something you only saw if you'd happened to stand in both rooms. AI has changed that, and quickly, because AI is now forcing both rooms to confront the identical question at the same moment.

The startup using AI to build and the enterprise deploying AI at scale are both running headlong into the same wall, and it's the human one. Will people actually adopt this? Do they trust the machine's judgment, or resist it, or over-rely on it? Does the capability translate into changed behavior, or just into an impressive demo? These were always the decisive questions, but AI has made them unavoidable and simultaneous, because everyone is now building and deploying the same kind of system against the same kind of human response, regardless of the size of their room. The convergence I noticed slowly, over years, by accident of having worked both sides, is now arriving for everyone at once. The founder and the transformation leader are being handed the same problem, on the same timeline, by the same technology.

And the answer is the same in both rooms, too. It was never going to be found in the capability. It's found in the patient, unglamorous work of understanding people, earning their trust, and helping them change, which is the work both jobs were always secretly about.

Why I find this endlessly interesting

This is why the different parts of my work have never felt like separate careers to me. The research, the enterprise product leadership, the building: they look like three different things, and people are forever asking how they fit together. They fit together because they are three vantage points on a single question. What makes something new actually take hold among people, and why is that so much harder than it looks?

I study it formally because it's the question underneath my doctoral research. I live it operationally inside an enterprise. And I bet on it personally every time I build something. The startup and the transformation are not two different worlds I happen to move between. They're two rooms with the same question written on the wall, and I find that question endlessly interesting because it's the one that actually determines whether anything new succeeds, anywhere, at any scale. The technology will keep changing. The question won't.