Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASAThe team had earned its standing ovation, and it wanted one. Two months of late nights. A release pushed out over a weekend nobody got back. The kind of finish that gets a team a reputation for grit. In the review, they walked through all of it, the heroics and the saves, with the quiet pride of people who'd been through something together. Then a new stakeholder, who hadn't been in the trenches and so could still see clearly, asked the one question. "So did it work? Are customers using it?" The room went quiet, because the honest answer was no. Adoption was flat. The thing they'd half killed themselves to ship was, so far, a feature nobody had asked for, delivered heroically. They'd worked hard enough to deserve a medal. They just hadn't done the thing that earns the only prize that counts. There's a rule for exactly this, and it's carved in stone. In Terry Goodkind's Sword of Truth, the Eighth Rule arrives as an inscription on the base of an ancient statue, left by a wizard dead for thousands of years. Two words, in a dead language called High D'Haran: Talga Vassternich. Translated, it reads: deserve victory. The old wizard meant more by it than a battle cry. Be justified in your convictions, be completely committed, and earn what you want, instead of waiting for someone to hand it to you. Goodkind carved it for warriors walking into a fight they could lose. It also happens to be the single most uncomfortable sentence you can read aloud in most agile transformations."Deserve" isn't about who worked hardest. It's about commitment.Now here's the catch. When the Rule says deserve victory, it isn't talking about moral worth, about which team is the nicest or logged the most hours. It's talking about commitment. Not the word people reach for when the outcome didn't land. The real thing: a team that genuinely commits to its goal and to each other, and then goes and does whatever that takes, instead of waiting around for someone else to make it happen. That's the line most organizations spend enormous energy blurring: the line between working hard and owning the outcome. They are not the same. They are barely even related. Effort is what you spend. Owning the outcome is what you commit to and go make happen. Customers and markets are profoundly uninterested in how tired the team is. They respond to what it actually took ownership of and delivered. Call it the effort dividend: the payout a team feels owed for how hard it worked. Reality never pays it. There is no exchange rate between exhaustion and outcomes. A team can spend a quarter of overtime and earn nothing, while a calmer, more capable team ships something that lands in two weeks, and the universe will not feel the injustice, because there isn't one. One team built the capability. The other built a reputation for grit. This is why the Rule is so despised in practice. It quietly refuses to accept the currencies organizations most want to pay with.The currencies reality won't acceptWatch what gets offered up in place of capability, and watch reality decline each one. There's effort itself. "We worked so hard, the team was completely committed." All true, all worthy of respect, and all irrelevant to whether the customer's life got better. The capability to produce the outcome without heroics has a name in this work: Skill Completeness, the team actually having what it takes to do the job end to end, rather than papering the gaps over with someone's weekend. Heroics aren't a sign of a great team. They're the interest payment on a capability the team never built. There's busyness. Calendars packed wall to wall, everyone maxed out, and the fullness read as contribution. Usually it's the opposite. A system running at a hundred percent has no capacity to absorb a surprise or learn anything, which is precisely why it produces so many surprises and learns so little. There's the heroic deadline, and what it quietly cost. The win was real, but it was bought by cutting the testing and shipping the kind of quality that comes back as next quarter's firefight. That's the other fundamental this Rule sits on: Commitment to Quality. You don't deserve speed by sacrificing quality to hit a date. You earn durable speed by building quality in, so the next release doesn't have to be a rescue. A team that wins by burning quality hasn't earned a victory. It's taken out a loan. And there's the quietest one of all: waiting. A team runs into something it can't do on its own, and instead of going after it, it waits to be rescued. Every time, it's reasonable. The thing really is, technically, someone else's job. But the commitment this Rule is about is the exact opposite of waiting to be saved. Don't wait for the blocker to be cleared; go clear it, or go find who can. Don't wait to be handed the real customer need; go dig it out yourselves. Don't wait for the org to arrange training for the skill you're missing; close the gap. That's the commitment, and it has a name in this work: Outcome Ownership, the team owning not just the result but the whole path to it, including the parts that would be so much easier to leave for someone else. The team that deserves the win is the one that picks these up itself, instead of filing a ticket and waiting for rescue. And at the top, there's the organization that wants the outcome and keeps every constraint. Leaders demand speed and innovation while approval chains and utilization targets stay exactly as they were, and then wait, a little impatiently, to be handed the agility they ordered. That's the Rule's other half, the part about waiting for others to give you what you desire. You don't get adaptability by wanting it. You earn it by removing the things that block it, which is harder than wanting, and rarer.Four signs a team is waiting to be given what it hasn't earned1. Poor outcomes get defended with effort. The result didn't land, and the case for the defense is the timesheet. "But we were completely committed." Commitment is being offered as the achievement, because the achievement is missing. 2. Heroics are normal, and celebrated. The weekend save, the last-minute rescue, treated as excellence rather than read as the symptom they are: a capability the team keeps having to fake under pressure. 3. "We're doing Scrum" is offered as proof of progress. Performing the practices stands in for building the capability. The ceremonies are running, so surely the deserving is happening. It isn't. Doing the framework was never the same as being able to do the work. 4. The organization mandates the outcome and changes nothing else. It wants agility and better results, and keeps every structure that prevents them. It has confused ordering the victory with earning it.One move: trade the wish for the capabilityIn your next planning conversation, ban one question until you've answered a better one. The banned question is "what do we want to achieve?" The better one, which has to come first: "what would we have to build to become a team that can achieve this reliably, not heroically?" That single swap moves the conversation off desire and onto capability, which is the only thing the Rule says you can actually earn a victory with. For a leadership team, the version is sharper still: not "what outcome do we want," but "what constraint would we have to remove for this outcome to be earnable at all?" The counteraction to the Eighth Rule is to stop paying reality in effort and start committing for real: to the goal, and to each other. And then to act on that commitment by going and getting whatever the goal needs, instead of waiting to be handed it. That commitment is Outcome Ownership, the team owning the result and the whole path to it. It shows up as two capabilities you build rather than wish for. Skill Completeness, the competence to produce the outcome without a rescue. Commitment to Quality, the discipline that makes speed sustainable instead of borrowed. Effort buys none of it. You commit, and you build, before the win, not after the loss. Before you celebrate the next heroic quarter, ask one question. When did this team last hit the outcome without anyone's weekend? If every win needs a hero, you don't have a capable team yet. You have a tired one. And you can't run a team on tired for long. Lean on it long enough and the people you keep relying on burn out or leave, and then you don't even have the tired team. This is where the discipline arc turns hard. The Sixth Rule said think clearly. The Seventh said face forward. The Eighth is the one that refuses to let intention count as achievement. Facing the right direction earns you nothing. Working yourself to the bone earns you nothing. Reality settles its accounts in capability, and capability has to be built before the win, never invoiced after the loss. The Rule doesn't care whether you believe it. That's what makes it a Rule. Take this Rule into your next big win and ask: did we earn this by building something that makes the next one easier, or did we just survive it, and call surviving a strategy? 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 Last Failed Transformation is not a Strategy | 0 | 5.62 | 06-08-2026 |
| 2 | You Helped Your Teams Into Helplessness | -2 | 6 | 02-07-2026 |
| 3 | The Most Passionate Transformations Make the Worst Decisions | -2 | 6 | 09-07-2026 |
| 4 | Nobody Believes your Values Page. They're Watching the Deeds. | 0 | 6.22 | 23-07-2026 |
| 5 | The Wizard's Rules: A Field Guide to How Your Organization Lies to Itself | -2 | 6 | 18-06-2026 |
| 6 | Your framework has been doing your thinking. That's the problem. | 0 | 5.78 | 30-07-2026 |
| 7 | “Scrum didn’t work for us.” | 0 | 8.1 | 30-07-2026 |
| 8 | Great Products Make Great Targets | 0 | 11.1 | 19-07-2026 |
| 9 | Incremental Delivery and the Need for Speed | 0 | 15.1 | 14-07-2026 |
| 10 | 🇩🇪 Konflikte surfen statt lösen | 0 | 18.59 | 30-07-2026 |