Building

A Framework That Starts Working Against Itself

Nir Eyal's observation that business frameworks like OKRs can fail by reversal, not just neglect, and why that failure is harder to catch.

3 min
Nov 22, 2026
Hand-carved style minimalist pattern on warm beige textured paper, showing a spiral root network of branching lines winding inward then outward, symbolizing a system that quietly turns back on its own purpose.
AI-generated image

I have spent years inside systems that were supposed to create clarity: specs, user journeys, OKRs, delivery frameworks. Most of the time, when one of them failed, the explanation was simple. People stopped using it properly. The ritual decayed into a checkbox.

Nir Eyal names a different, quieter failure mode, and it stuck with me the moment I read it. Companies keep reaching for the same set of tools, OKRs, growth mindset training, personality tests, and assuming the only risk is neglect. But some of these frameworks don't just get abandoned. They get inverted. They end up producing the exact opposite of what they were built for, while everyone involved believes they are using the tool correctly.

The failure mode everyone expects

Neglect is the failure we're trained to watch for. A team sets OKRs in January, forgets them by March, and nobody is surprised when the quarter ends with no connection between the stated objectives and what actually got built. The fix feels obvious: discipline, better check-ins, a sharper facilitator. This is the risk every leader already has a mental model for.

The failure mode nobody is watching for

Eyal's sharper point is about what happens when the framework is being followed, carefully, consistently, and still produces the wrong behaviour. His example: OKRs, designed to push teams toward ambitious, even uncomfortable goals, quietly turn into a salary negotiation tool. Once a key result is tied to a bonus or a review, the incentive flips. People stop setting the goal that stretches them and start setting the goal they know they can hit. The framework survives. The discipline survives. The original purpose is gone.

Personality tests and growth mindset programmes can bend the same way. A tool meant to open people up to feedback and change becomes a label they hide behind, or a script they perform for a manager who wants to hear the right words. The practice looks intact from the outside. Inside, it's running backward.

Why the reversal is harder to catch than neglect

Neglect is visible. Nobody is pretending the OKRs matter. A reversal is invisible precisely because the ritual still looks healthy. Meetings happen, documents get filled in, scores get reported. The leader reviewing the dashboard has every reason to believe the system is doing its job, because every surface signal says so. That's what makes it more dangerous than simple abandonment: you can't fix what you don't think is broken.

This is where the line between following a framework and auditing a framework starts to matter. Most teams only ask the first question, are we using this. Almost nobody asks the second, is this doing to us what we think it's doing, or something else entirely.

What I take from this

Running a solo business means I am both the person who sets the goals and the person who grades them, which makes this exact failure easy to miss in my own practice. If I tie a review to how comfortable I feel at the end of a quarter, I will quietly start choosing comfortable goals. The checkbox will say the system worked.

So the question I'm sitting with isn't whether my own goal-setting routine exists. It's whether, somewhere along the way, it started rewarding the opposite of what I built it for. If you run any kind of structured self-review, it might be worth asking the same thing before the next cycle starts.

Was this note useful?

If you'd look at your own website: theuxbites, my own tool, turns its technical and usability problems into clear next steps. Three audits a month are free. Open theuxbites

One Decision

Every other week, one real decision from my own work. What I built, what I left out, what I handed to a machine and what I deliberately kept. With the reasoning, and what it cost when I got it wrong.

Not a newsletter. One decision at a time, close enough to your own work to be useful. Whether you are building a product or looking for a way to work that doesn't wear you down.

One email every two weeks. Unsubscribe in one click.

See what you are subscribing to

A Framework That Starts Working Against Itself | David Rozsa