Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASAThe outage lasted four hours. The review that followed lasted one, and within the first ten minutes it had quietly stopped being about the outage. It had become about who. Whose change went out on Friday. Who approved it. Who was on call and missed it. By the time the meeting wrapped there was a name, a sheepish apology, and a new rule about Friday deploys. Nobody asked why one person's mistake could take the whole thing down for four hours, because asking that would have led somewhere nobody in the room wanted to go. Upward. Everyone left having learned something. Not about the system. About what happens here when something breaks. Three weeks later a similar problem was building again. This time the person who could see it coming said nothing, and waited to find out if it would land on someone else first. That second silence is the whole story. A fantasy novel named the thing missing from that room thirty years before your last postmortem. In Terry Goodkind's Sword of Truth, the rule keeps surfacing, which is usually how you know one matters. The witch woman Shota speaks it. So does the spirit of a dead mother, who presses it on the hero himself, and the dead have no reason left to flatter you: "There is magic in sincere forgiveness; in the forgiveness you give, but more so in the forgiveness you receive." Read the second half again, because that's the part organizations skip. The forgiveness you give is the easy magic. Anyone can chair a blameless postmortem. The forgiveness you receive is the hard kind, because to receive it you first have to admit you needed it. You have to say the thing was partly yours. Goodkind wrote it about grief and old wounds. It's also the most precise description I know of why your bad news always arrives late.Forgiveness is not softness. It's infrastructure.In an organization, forgiveness isn't a nicety you add once the serious work is done. It's the precondition for the truth. People only tell you reality when reality is safe to tell. Make a mistake expensive enough to confess and people stop confessing. They don't stop making mistakes. They stop reporting them. The defect gets quietly patched, the slipping date gets held until it can't be hidden, the risk goes unraised. Nothing improves, because the organization no longer knows what's actually wrong with it. The fundamental underneath this Rule has a plainer name than the words on your company's slides: Trust and Candor. It's the state where people can say the hard, true thing, to a peer or straight up to power, without it costing them. Reality Transparency, everyone seeing the same true state of the work, is what Trust and Candor produces. One is the behavior, the other is the result. Take the candor away and transparency doesn't get worse. It goes underground, because you can't mandate transparency into a place that punishes the transparent. Call it the blame reflex. The instinct, the second something breaks, to reach for a name before a cause. It feels like accountability. It's the opposite. Real accountability needs the facts, and the blame reflex is the most reliable way there is to make the facts disappear. Here's the distinction organizations get backwards constantly. Forgiveness is not the absence of accountability. It's the condition that lets honest accountability exist. Forgiving the person is not the same as forgetting the failure. The line worth pinning above every postmortem: be hard on the system, soft on the people. But hard on the system means something specific. Not venting at "the process" and moving on. It means going after the system until you find what actually let the failure happen, and changing it. Blame the deadline, the missing test, the staffing as hard as you like, as long as the blame ends in a fix. A mature organization holds the system fiercely accountable and leaves the person standing. You can be that fierce with the system precisely because you've stopped holding a person hostage.The same fear, quieter the higher it climbsThe outage was the loud version. The Rule runs everywhere, and each layer up, the truth gets a little quieter, because every level has watched what happened to the last person who spoke. The developer who finds a real defect late and fixes it. That part is good. Catching your own mistake is exactly the job. The loss is everything around the fix: the commit message is vague, the bug never gets named in standup, and the one person who could warn the rest of the team stays quiet, because the last bug traced to a name is still a running joke. So the defect gets patched and the lesson gets buried. A mistake found and quietly fixed saves one afternoon. The same mistake found, named, and walked through with the team saves every colleague about to make it. The blame reflex throws the bigger save away to spare one person the smaller discomfort. The team that knows the date will slip and says so only when it's undeniable, because the last team that flagged a risk early got a month of "support" that felt a lot more like punishment. Honest Inspection needs the bad number on the table while it's still small. Punish the early flag and you guarantee you only ever see the late one. And the retro that's become a careful little performance. Everyone offers a tidy "what went well," the real problem stays off the board, and the meeting ends having changed nothing. A retro is where a team repairs itself. This one is theater, because everyone knows that naming the real problem means naming a person, and that has consequences here. One fear, losing its voice a little more at every level it climbs. By the time bad news reaches the top, it's been softened and reframed so many times that the most senior people are the least informed. They mistake the silence for things going well.The forgiveness leaders won't receiveWhich brings us back to the half of the Rule everyone skips. Most leadership teams are fluent in the forgiveness you give. No-blame postmortems. "We don't punish failure here." Posters. What's almost entirely missing is the forgiveness you receive, and you can only receive it by first owning that you needed it. By a leader saying, out loud and first, "the conditions that made this failure easy and this truth dangerous, we built those." That sentence is the actual system reset. It's also the rarest sentence in the building, because it costs status to say, and status is exactly what the blame reflex protects. That's the magic Goodkind put in the second clause. Grace handed down from a leader who never admits fault isn't grace. It's permission, granted from a safe height, and everyone can feel the difference. A team forgives the leader who owns their part. Nobody forgives the leader who only ever hands out pardons. If you've followed this series, you'll see the connection. Wizard's First Rule said people believe comfortable lies. This is where those lies get manufactured. When the truth is dangerous to say, people don't just go quiet, they start preferring the comfortable version themselves, and the green dashboard from the first Rule fills with true believers who would rather not know. No forgiveness is the engine. The comfortable lie is the exhaust.Four signals reality has gone underground1. Bad news always arrives late and large. Problems never surface small and cheap. They surface as outages and missed quarters. If nothing reaches you while it's still minor, that isn't because things are minor. 2. Postmortems produce a name, not a change. The review ends with who, and a tweak to a checklist. It does not end with the harder finding: what about the way we work made this easy to do and hard to catch. 3. "Safety" is a value, and the last person who tested it regretted it. The poster says it's safe to speak up. The organizational memory says otherwise, and people trust the memory, not the poster. 4. Grace flows down and never up. Leaders forgive the team generously. No leader has said "this one is on us" about a real failure in living memory. Forgiveness is a thing done to the people below, never received by the people above.One move, and it has to start at the topAt the next real failure, before the review, the most senior person in the room names their own part in it first. Out loud. Not "mistakes were made," not a hand-wave. The specific condition they own: the deadline they refused to move, the staffing they didn't fix, the question they made unsafe to ask. They give forgiveness, and the harder thing, they receive it, by admitting there was something to forgive. Then ban one question from the postmortem: "who did this?" Replace it with: "what made this easy to do and hard to catch?" The first hunts a person. The second hunts the system. You cannot ask both, and which one you ask is the entire culture. The counteraction to the Fourth Rule is that rule made structural: hard on the system, soft on the people, every single time, on purpose, starting with the person who has the most status to lose by saying it. Blame the system as hard as it takes to find the fix. Just stop blaming the person. That's the moment Trust and Candor stops being a poster and starts being a behavior. Before your next incident review, ask one question. What's the most recent piece of genuinely bad news that reached me early, while it was still cheap to fix? If you can't think of one, your people aren't protected. They're quiet. And a quiet organization isn't a calm one. It's one that has agreed, gently and without ever discussing it, to stop telling you things. The Rule doesn't care whether you believe it. That's what makes it a Rule. Take this Rule into your next incident review and ask: are we here to find out what to change, or who to blame, and would the person who can actually see the problem feel safe naming it? 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 | Nobody Believes your Values Page. They're Watching the Deeds. | 0 | 6.22 | 23-07-2026 |
| 2 | Your Agile Transformation is a Lie You Wanted to Be True | -6 | 4 | 25-06-2026 |
| 3 | You Helped Your Teams Into Helplessness | -2 | 6 | 02-07-2026 |
| 4 | The Wizard's Rules: A Field Guide to How Your Organization Lies to Itself | -2 | 6 | 18-06-2026 |
| 5 | Great Products Make Great Targets | 0 | 11.1 | 19-07-2026 |
| 6 | The Dashboard Was Green. The Customers Were Angry. | 0 | 7.4 | 29-07-2026 |
| 7 | Culture Follows Structure. Most Transformations Bet the Other Way. | 0 | 13.06 | 26-07-2026 |
| 8 | 💭Разговор у старого дерева. Космос сидел на камне возле старого ... | -2 | 6 | 21-07-2026 |
| 9 | ⱾİᏀᎷᎪ Как мы отдаем свою силу Существует тихая, незаметная война, ... | 0 | 7 | 27-06-2026 |