Your Last Failed Transformation is not a Strategy

Дата публикации: 06-08-2026 22:00:00

"We tried that before." Four words, and the idea was dead. Nobody asked when "before" was, or what was different then, or whether the thing that killed it last time even still exists. The four words did all the work a careful argument would have done, minus the argument. The meeting moved on, a little more certain that nothing here ever really changes, which by now is the one thing the team can reliably predict. Listen for it and you'll hear a whole liturgy. "That'll never work here." "Management will never allow it." "The legacy system makes it impossible." "This is just how we are." Each one is a door, quietly closing. And behind enough closed doors, a team can talk itself into believing the building has no exits. There's a line in a fantasy series that names what the team has lost. In Terry Goodkind's Sword of Truth, the hero doesn't invent the Seventh Rule. He finds it, written down long before him, in an ancient book carried most of the way across a continent to reach him. He reads it out to the people around him, the way you'd hand someone a tool they didn't know was missing: "Life is the future, not the past." The book is careful about the past, which is the part most quotes leave off. The past can teach you how to do a thing, it can comfort you, it's the foundation everything already stands on. But only the future holds life. To live in the past is to embrace what's already dead. The book's own gloss on the rule is the part worth carrying into any team. As thinking beings, it says, we're meant to use our intellect, not a blind devotion to what came before, to make the next rational choice. That is exactly what this series calls Decisive Adaptation: you choose your next move from what reality shows now, not from what it showed you then. Goodkind wrote the rule for people haunted by old wars. It also describes a team that has quietly handed its steering to a version of the world that no longer exists.Experience is evidence. It is not a verdict.The past is data, and data is useful. The trouble starts the moment a team stops treating it as data and starts treating it as a verdict, a closed prediction about a future that hasn't happened yet. Learning from the past and living in it look identical for about one sentence, then they head in opposite directions. Learning from it means using what happened to design a smarter next attempt. Living in it means using what happened to cancel the attempt before it starts. One produces an experiment. The other produces a reason not to run one, delivered with the confidence of someone who's "seen this before." Call it the closed case. A team closes a case when it takes a single past outcome and files it as a permanent ruling: tried it, didn't work, matter settled. And once a case is closed, no new evidence is allowed in. The market changed, the people who blocked it left two reorgs ago, none of it reaches the team, because the team stopped looking the day it banged the gavel. That's Honest Inspection switched off at the source. Inspection means re-examining the evidence as it stands now, and a closed case is a standing refusal to look again. Notice what the closed case wears as a disguise. It calls itself realism. The team that has already decided nothing will work will tell you, with some pride, that it's just being realistic. It isn't. Realism weighs the evidence and stays open to the next data point. What's actually happening is cynicism, which took one bad experience and shut the books, and cynicism in a smart team is almost impossible to argue with, because it sounds exactly like wisdom.The cases this team has already closedThe past doesn't stop a team all at once. It does it one closed case at a time, and after enough of them the team is governed entirely by rulings nobody reviews. There's the idea that dies on contact with a date. Someone proposes a change, and the answer is "we tried that in 2019," as if a calendar were an argument. The reflex is historical, not analytical, and it ends the conversation before anyone checks whether 2019's obstacle is still standing. There's the retro that's become a museum tour. The hour goes almost entirely to what hurt, the same wounds walked past respectfully every two weeks, and almost none of it to the only question a retro exists to answer: what small thing do we move next. A retro is supposed to be about the next step. This one is about admiring the corpse of the last one. There's "legacy," the word that ends all discussion. Old architecture, old contracts, all of it real and genuinely constraining. But the word gets used as a full stop instead of a starting point. "It's legacy" is treated as a verdict, when the honest version is just a sentence that should be followed by "so here's what we design around it." And there's the whole organization, still optimized for yesterday's company. The approval built for a risk that no longer exists. The structure that solved a problem the company stopped having years ago, defended now purely because it's still there. Four verdicts, all handed down by the past, all still somehow in force.Four signs the past is running the team1. New ideas get answered with a date, not an analysis. "We tried that in 2019." Nobody establishes what was different then, or whether it still is. History is being used to close the question, not open it. 2. The retro replays pain and designs nothing. Most of the hour goes to what went wrong and almost none to the smallest next move. The team leaves having felt the past, not changed the future. 3. "Legacy" ends conversations. The moment the word appears, thinking stops, as though it named a fate rather than a constraint you could engineer around. 4. The team's most confident forecast is that nothing will change. And it's right, reliably, because it keeps making sure. The prediction and the cause are the same thing.One move: reopen one closed casePick one idea the team is certain won't work, because it didn't before. Put the "before" on trial with three questions. When exactly did we try it? What was different then? Is that difference still true today? Run it honestly and you'll find, about half the time, that the thing that killed the idea is gone. The blocker got promoted out. The constraint quietly retired. Nobody noticed, because the case was closed, and closed cases don't reopen on their own. To keep it from happening again, split every "what went wrong" in your next retro into two columns: what did this teach us, and what's the smallest different thing we could try next. The past earns a seat at that table. It does not get to chair the meeting. The counteraction to the Seventh Rule is to treat the past as evidence you weigh, never a verdict you obey, which is exactly what Decisive Adaptation asks for. You change direction on what the evidence shows now, and "we tried it in 2019" is not evidence. It's a memory, and memories don't get a vote they haven't re-earned with current facts. Before you let history close the next conversation, ask one question. When did this team last try something it was sure wouldn't work, and find out the world had moved? If you can't remember one, the team isn't being realistic. It's being governed by a version of reality that retired years ago and never told anyone it left. This follows straight from the last Rule. Wizard's Sixth Rule said to let reason rule. The Seventh adds the catch nobody mentions: reason is only as good as the evidence you feed it, and a team running on "we tried that before" has quietly put reason on a diet of expired data. Sometimes the closed case is older than cynicism, too. Sometimes it's scar tissue from a team that once proposed something, got punished for it, and learned to shut the case itself before anyone else could. The past doesn't only forecast. Sometimes it's hiding. The Rule doesn't care whether you believe it. That's what makes it a Rule. Take this Rule into your next retro and ask: which of the things we "already know won't work" have we actually re-tested against the world as it is now, not the world as it was when we last tried?  If this Rule cut close, pass the blade on. Share. 
Welcoming your comments on this!
Don't want to miss any of these articles? Have the “Fundamentals before Frameworks” series in your mailbox.Wishing you an inspiring read and a wonderful journey.Scrum on!



Image

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Your framework has been doing your thinking. That's the problem.	0	5.78	30-07-2026
2	Customers Don't Buy your Exhaustion	0	5.62	13-08-2026
3	Your Agile Transformation is a Lie You Wanted to Be True	-6	4	25-06-2026
4	The Wizard's Rules: A Field Guide to How Your Organization Lies to Itself	-2	6	18-06-2026
5	You Helped Your Teams Into Helplessness	-2	6	02-07-2026
6	Nobody Believes your Values Page. They're Watching the Deeds.	0	6.22	23-07-2026
7	Focus Is Not Genius. It Is a Kata.	0	12.38	09-08-2026
8	You Can Ignore the Flow Data. It Still Decides When You Ship.	0	13.6	12-07-2026
9	From Chaos to Control, Part 6 - Adapt and Control	0	10.61	22-07-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 9. Тональность: 0. Информативность: 5.62. Источник: scrum.org.