Martec's Law: The Management Problem You Can't Fix, Only Manage

There's a graph I keep coming back to. On one axis, the quantity of change. On the other, time. Plot technology on it and you get an exponential curve — computing power, platforms, networks, all compounding on each other, all accelerating. Plot your organization on the same graph and you get something much flatter. A logarithmic curve. People, structures, processes, incentives, culture — all of it evolves slowly, and the bigger the organization, the slower it gets.

This isn't a leadership failure. It's not because your CTO didn't read the right framework or your CEO isn't visionary enough. It's a human limit. And it has a name: Martec's Law.

Technology changes exponentially. Organizations change logarithmically.

That's it. That's the whole law, and it's arguably the most important management problem of the century, because it means something uncomfortable: organizations cannot sustainably change faster than that logarithmic curve allows. You can change more slowly. You can refuse to change at all. But you cannot outrun technology. Nobody can.

So the real question isn't "how do we keep up?" You won't. The real question is: what do you do about the gap?

Most organizations don't choose a response. They just react — adding tools, launching initiatives, chasing whatever the market did last quarter — and end up defaulting into the worst possible position. Here are the four actual strategies, in order of how deliberate they require you to be.

1. Accept Permanent Change — and Choose Your Battles

The first move is admitting you will never be caught up. That's not defeat, it's the new normal. Once you accept that, the question shifts from "how do we catch up" to "what actually matters here."

That means making explicit choices:

• Which capabilities genuinely differentiate us from competitors?
• Which technology domains deserve continuous, real investment?
• Where can we deliberately choose stability over novelty?

Discipline starts by putting energy where it compounds — not wherever the loudest fire is currently burning.

2. Relentlessly Limit Technology Choice

Unconstrained choice is the fastest route to complexity. Every extra technology, platform, language, integration pattern, or tool you allow into the organization adds cost, risk, and cognitive load — and it adds it forever, not just once.

Smart organizations are strict, almost boringly strict, about what's allowed in. Not because new things are bad, but because every yes is a permanent tax on everyone who comes after.

3. Increase the Organization's Ability to Absorb Change

You will never match technology's exponential curve. But you can improve your own metabolism. Lean and agile ways of working, short feedback loops, decentralized execution within clear constraints — these don't make your organization faster than technology. They make it faster than it currently is, which is the only lever you actually control.

4. Occasionally Reset the System Deliberately

Incremental improvement has limits. Sometimes the accumulated debt — technical, structural, cultural — is too large for small adjustments to fix. Smart organizations occasionally step back and ask the hard question: should we tear this down and rebuild it properly, on purpose, rather than let entropy decide for us?

The Default Nobody Chooses

Here's the uncomfortable part. Most organizations don't pick any of these four strategies. They drift into a fifth, unofficial mode: reacting to everything, absorbing nothing, and calling the resulting chaos "transformation." New tools get added because a vendor pitched well. New processes get bolted on because last year's postmortem demanded it. Nobody said no to anything, so complexity grows unchecked while the actual gap between what technology can do and what the organization can absorb keeps widening.

That's not a strategy. That's the accident.

A Quick Self-Check

Before you answer, be honest — not aspirational.

1. Can you name, without checking a slide deck, which three capabilities your organization has decided to be excellent at — and which ones it has deliberately decided not to chase?
2. If someone proposed a new tool or platform tomorrow, is there a real mechanism that could say no — or does everything eventually get approved?
3. Are your feedback loops (release cycles, decision cycles, learning cycles) getting shorter over time, or just as long as they were three years ago?
4. Has your organization ever deliberately paused and reset a system or process on purpose — or does everything just accumulate until it breaks?
5. When you look at your current technology landscape, does it feel like the result of decisions — or the result of history?

If most of your answers land on the second half of each question, you're not managing Martec's Law. You're being managed by it.

That gap — between what technology offers and what your organization can absorb — isn't going away. The organizations that do well aren't the ones that closed it. They're the ones that stopped pretending they could, and picked a deliberate way to live with it instead.

This is the exact problem the book Screw Architecture, Manage Change is built around — not another framework promising to make you faster than technology, but a practical way to decide, deliberately, which of these four responses your organization actually needs.

The book launches in about five weeks. Until then, you can get the first chapter free, plus €5 off at launch, by signing up at wellofwisdom.community.