# Own, Not Rent: Why Change Can't Be Outsourced **Author:** Alexey Krivitsky **Date:** 2026-07-10 **Reading time:** 4 min **Category:** Org Design **Tags:** org-design, change-management, transformation, 10x-org, leadership **Canonical:** https://krivitsky.com/post/10xorg-p1-own-not-rent --- **TL;DR:** Buy-in is permission to proceed, not ownership. A change you hand off is a change that gets handed back. The first principle from 10X ORG: own, not rent. This kicks off a Friday series — one principle from *10X ORG* each week, the ideas that make an organization ten times more effective, not ten percent. We start with the one everything else rests on. ## The six weeks that got erased Years ago I made an expensive consulting mistake. Expensive not in money — in learning. A Hamburg startup had hit its first real scaling pains. I studied the system, saw what was wrong, and pitched a vision of change to the CEO. He gave me the green light and left to raise the next investment round. I had a six-week window, and I used it. I formed a guiding coalition — the CTO, the CPO, product managers, engineers. Together we reshaped the place. What had been a set of isolated teams, each guarding its own slice of the product, became a **team-of-teams**: small groups with a shared purpose, working toward outcomes instead of tickets. People were in the room while it happened. They argued, adjusted, and made it theirs. Most of them loved it. One moment stays with me. A machine-learning engineer had spent months alone in a one-person department, tuning algorithms nobody used. In the new setup he joined a full-stack team, and the web developers there were hungry to learn what he knew. At a product review he grinned and said, "OMG, the brain I've been developing all these months actually works." It did. And the bigger brain — the team-of-teams — had started working too. Then the CEO came back. He looked around and didn't recognize his own company. He asked a few questions, heard the loudest voices of the unhappy minority, and flipped it all back. Overnight, six weeks of progress were gone. ## The blessing was not ownership So what was my mistake? I secured executive buy-in. I had the blessing. Isn't that the thing you're supposed to get? Apparently not. **Buy-in is permission to proceed. It is not ownership.** The CEO had handed the change to me the way you hand a problem to a contractor — *you deal with it* — and a change you've handed off is a change you can hand back. He rented it. And rented things get returned. Craig Larman once put it sharply: call it a "process change" and you'll get management support, at best; call it "a deep change to the organizational design" and you'll get their involvement. The distance between support and involvement is the whole game. Which is the principle — the first one in the book, because everything else leans on it: **own, not rent.** ## Rented ideas draw resistance; owned ones draw care Organizations rent change all the time. They buy the polished slide deck, roll out the popular framework, install the target operating model — and then discover the people inside don't believe in any of it. The ideas aren't necessarily bad. They were just imported before anyone inside understood the problem they were meant to solve. **Rented ideas get treated as someone else's responsibility**: best as bought, not to be questioned, adapted, or improved. And people can tell when they're being changed rather than changing. That is what resistance actually is — not stubbornness about a new process, but a reaction to being *acted upon*. Under pressure to show improvement, they comply on the surface and send up green status reports while little shifts underneath, and the gap between the reports and the reality widens by the day. Ownership does the opposite. When people help discover the need for change and shape what "better" looks like, it stops being extra work handed down from above and becomes their own insight. People protect what they own — they defend it when things get hard, adapt it when reality moves, keep it alive in a hundred small daily decisions. **10X performance can't be installed from outside. It grows from the inside out.** ## Change with people, not to them The clearest counter-example I know is [Poster](/post/case-study-poster-pos-org-topologies), a Ukrainian SaaS company. Its CEO didn't hire anyone to transform it. He gave his people 90 days to learn the fundamentals of systems thinking and organizational design, then turned them loose on their own system. They studied it, iterated on the org blueprint, and co-created a future state they actually wanted. It looked slower than a top-down rollout. It was. But speed without ownership doesn't stick — and this stuck. The proof came later. When COVID hit, and then the full-scale invasion, Poster didn't have to redesign under fire. Its teams already held the mandate to adapt and refocus on whatever mattered most. That adaptive capacity is what carried the company back to profitability within a year. Nobody had to defend the change; it was theirs from the start. This is also why I've grown wary of the phrase "transformation project." A project has a start date, an end date, and a neat block diagram. Organizational change has none of those cleanly — it is slow, human, and unpredictable, and treating it like a machine to be reassembled only teaches everyone to make the change look good on paper instead of real. I've written before about why [transformation exists only in retrospect](/post/agile-transformation-televised), and why [AI amplifies whatever organization you already have](/post/redesign-for-ai-why-transformation-requires-organization-design) rather than fixing it. ## Own, not rent — in the age of AI The same trap is being reset right now, in AI costume. A vendor sells you an "AI operating model," you buy a few thousand agent seats, someone rebrands the PMO as the "AI orchestration layer" — and you've rented your AI transformation exactly the way that Hamburg CEO rented his. New labels, the old structure underneath. The uncomfortable part is that AI doesn't fix a rented organization; it amplifies whatever one you already have. Bolt agents onto fragmented ownership and narrow mandates and you don't get a better org — you get [the old traffic jam, faster](/post/the-ferrari-trap). DORA's 2025 research puts numbers on it: hand AI to a struggling team and stability actually drops. The dysfunction was already there. The tools just found it sooner. Which is why the AI-era version of this principle is the line I keep coming back to on the book tour: first design, then AI. AI is a lever, not fairy dust — it accelerates a direction you've already chosen and owned, and it can't choose one for you. The organizations that will actually absorb agents are the ones that already own their adaptive capacity, the way Poster did: teams with the mandate to study their own system and reshape it. A top-down AI rollout onto a rented structure just teaches people to fake AI adoption the way they once faked agile. Own the redesign first, then let the agents in. ## The one that everything rests on If there is a single reason change fails to produce lasting performance, this is it: it was rented, not owned. The conditions for deep, durable change are simple to name and hard to live — shared direction from the top, and real ownership of the problem by the people closest to the work. Own, not rent. That's principle one. Eight more Fridays to go. If you want the whole argument — the stories, the map, and the eight principles that follow — *10X ORG* is [on Amazon](https://www.amazon.com/10X-ORG-Topologies-Elevating-Performance/dp/9083670406), a bestseller in Management Strategy and several other categories, in Kindle, paperback, and hardcover. Happy Friday, all.