The quiet quitting of strategy

There's a particular kind of organisational silence I've come to recognise. It happens around an initiative that everyone privately knows is dying but nobody has officially called time on. The status reports get a little vaguer each week. The owner's updates get shorter. The metric that was supposed to move stops being mentioned. Then one quarter the slide just isn't there anymore, and nobody asks where it went, because asking would be awkward for several people in the room.

This is the quiet quitting of strategy. Not a decision. An evaporation.

I want to talk about why it happens, what it costs, and — because I'm tired of writing pieces that diagnose without prescribing — what I think you can actually do about it.

How an initiative quietly dies

The pattern is almost always the same. A strategic initiative is announced with great clarity at the start of the year. It has an owner, a sponsor, a metric, a rough timeline. The first quarter goes well enough — the team is staffed, work is starting, the slides look credible. Somewhere in Q2, the first problem appears: a dependency the team didn't know about, a hiring freeze, a competing priority that arrived from somewhere upstream. The owner mentions it in their update, expecting a conversation. The conversation doesn't really happen — there's too much else on the agenda — and the issue gets a yellow status and a "let's track it."

By Q3, the team has quietly de-scoped twice. The metric is no longer mentioned because nobody wants to highlight that it hasn't moved. The owner has rotated some of their best people onto something more visible, because their performance review depends on shipping something, and this initiative isn't going to be it. The status report still says "in progress," because nobody has the authority — or the appetite — to mark it dead.

By Q4 planning, the initiative just doesn't make it onto next year's deck. Nobody removes it formally. It is simply not re-listed. And the question "what happened to that?" never gets asked, because asking it would force the room to acknowledge that a thing the company committed to a year ago, in front of the board, has been silently abandoned, and there might be other things in the same condition.

Why this is worse than a clean kill

A clean kill is fine. Companies should kill initiatives. The strategic landscape changes, you learn new things, you discover the bet was wrong — killing the initiative and reallocating its capacity is one of the healthiest things a leadership team can do. A clean kill produces a memo, a learning, a debrief, and a freed-up team that knows it's been freed up.

Quiet quitting produces none of those things. It produces:

A team that knows the initiative is dead but is still nominally working on it, because no one told them to stop. So they continue going through the motions at reduced intensity, burning capacity that could be deployed elsewhere.

A leadership team that has not actually faced the fact that a bet didn't work, which means they haven't extracted the lesson, which means they're likely to make the same kind of bet again next year in slightly different costume.

A board that thinks the company is executing on the strategy it was shown, because nobody has officially un-shown it.

And — this is the one that compounds — a culture in which people learn that the safest way to handle a failing initiative is to let it fade rather than to call it. Once that's the norm, every initiative becomes a candidate for quiet quitting, and the company loses the ability to talk honestly about what is and isn't working.

Why nobody calls it

It would be easy to blame this on cowardice, but I don't think that's right. The people involved are not cowards. They're operating in an environment where the calling-it move has worse personal economics than the fading-it move.

If you publicly kill your own initiative, you have to explain it. You have to face questions about why you committed to it in the first place. You have to absorb the political cost of having been wrong about something visible. Your peers, who have their own slowly-dying initiatives, are quietly grateful you didn't set a precedent — but they're not going to defend you publicly. The board observer will remember the kill more than the original commitment.

Whereas if you just let the thing fade, the cost is diffuse and nobody pays it directly. The team's capacity drains away invisibly. The strategic gap appears later, attributed to "market conditions." Nobody is on the hook for a specific moment of failure.

The incentives, in other words, are pointed at fading. The system asks people to do the harder thing — call it — and gives them nothing in exchange.

What might actually fix it

A few things, in increasing order of how much they require you to change.

First, the smallest: every quarterly review should have a column not for "status" but for "still worth doing — yes/no." Force the question. The status column lets people stay in yellow forever. The yes/no column does not. The default answer should be "yes" only if the team can articulate, in two sentences, why this initiative is still the best use of its capacity given everything else that's now on the table. If they can't, that's not a kill yet — it's a flag.

Second, slightly bigger: separate the person who reports status from the person who decides continuation. The owner has too much skin in the game to neutrally assess whether their initiative still deserves to exist. Someone with no personal stake — a chief of staff, a portfolio reviewer, anyone — should be the one making the continue/kill recommendation, with the owner contributing facts but not the verdict.

Third, and this is the one most companies won't do: reward kills. Not abstractly. Concretely. When an owner brings a "this isn't working, we should stop" recommendation to a portfolio review, that should be a positive event in their record, not a negative one. The signal you want to send is: catching a dying initiative early and freeing its capacity is exactly the behaviour we hire leaders to do. Until you make that real — until it shows up in promotion conversations and review write-ups — people will keep doing the math and concluding that fading is safer.

The Vindaris view

We didn't set out to solve this problem when we started Vindaris, but we keep ending up adjacent to it. When goals, initiatives and capacity sit in one system that everyone can see, quiet quitting gets harder. The capacity that's being silently drained becomes visible. The initiative that's been yellow for nine months stops looking like a status — it starts looking like an answer. And the conversation that wasn't going to happen in the leadership meeting becomes harder to avoid.

That's the actual leverage. Not a better dashboard. A system in which a strategic bet cannot quietly disappear, because every piece of evidence about its life — capacity, commitment, ownership, progress — is sitting in plain view of the same people who will be asked, at the end of the year, what we got for the money.

Strategies should be killed, openly, with a debrief and a freed team and a lesson. They should not be allowed to evaporate. The job of an operating model is to make the first cheap and the second impossible.

Es gibt eine besondere Art organisatorischer Stille, die ich erkennen gelernt habe. Sie umgibt eine Initiative, von der jeder privat weiß, dass sie stirbt, aber niemand offiziell den Zeitpunkt benannt hat. Die Status-Reports werden jede Woche etwas vager. Die Updates des Owners werden kürzer. Die Metrik, die sich bewegen sollte, wird nicht mehr erwähnt. Dann ist die Folie eines Quartals einfach nicht mehr da, und niemand fragt, wohin sie verschwunden ist, weil die Frage für mehrere Personen im Raum unangenehm wäre.

Das ist das stille Aufgeben der Strategie. Keine Entscheidung. Eine Verdunstung.

Wie eine Initiative still stirbt

Das Muster ist fast immer gleich. Die Initiative wird zu Jahresbeginn mit großer Klarheit angekündigt. Q1 läuft gut genug. In Q2 taucht das erste Problem auf — eine Abhängigkeit, ein Hiring-Freeze, eine konkurrierende Priorität. Der Owner erwähnt es; das Gespräch findet nicht wirklich statt. Bis Q3 hat das Team zweimal de-scopt. Bei der Q4-Planung steht die Initiative einfach nicht mehr auf der Folie. Niemand entfernt sie formal. Sie wird nur nicht mehr aufgeführt.

Warum das schlimmer ist als ein sauberer Kill

Ein sauberer Kill ist gesund. Er produziert eine Erkenntnis, ein Debrief, ein freigesetztes Team. Stilles Aufgeben produziert ein Team, das weiß, dass die Initiative tot ist, aber nominell noch daran arbeitet. Ein Führungsteam, das die Lektion nicht extrahiert hat. Einen Board, der glaubt, dass die Strategie umgesetzt wird. Und eine Kultur, in der Verblassen sicherer ist als Benennen.

Warum niemand es benennt

Es liegt nicht an Feigheit. Es liegt an Anreizen. Wer eine eigene Initiative öffentlich tötet, muss sie erklären, Fragen beantworten, politische Kosten tragen. Wer sie verblassen lässt, zahlt nichts direkt. Das System bittet Menschen, das Schwierigere zu tun, und gibt ihnen nichts dafür.

Was tatsächlich helfen könnte

Drei Hebel, in zunehmender Schwere: Erstens, in jedem Quartals-Review eine Spalte „noch tun — ja/nein" statt „Status". Zweitens, die Person, die Status meldet, von der Person trennen, die über die Fortsetzung entscheidet. Drittens — und das tun die wenigsten — Kills belohnen. Konkret. In Beförderungsgesprächen.

Die Vindaris-Sicht

Wenn Ziele, Initiativen und Kapazität in einem sichtbaren System sitzen, wird stilles Aufgeben schwieriger. Die still abfließende Kapazität wird sichtbar. Die seit neun Monaten gelbe Initiative sieht nicht mehr wie ein Status aus, sondern wie eine Antwort. Strategien sollten getötet werden — offen, mit Debrief, mit Lektion. Sie sollten nicht verdunsten dürfen.