9 May 2026
Heroics and the system that required rescuing.
Every late-night save is a system that did not catch the issue earlier. The best operators stop rewarding heroics and start rewarding boredom.
One thing I have noticed in high-growth delivery teams: they accidentally reward heroics. The person who saves the client relationship at 11pm on Thursday becomes the benchmark. The internal narrative cements around them.
Almost nobody asks the prior question: why did the system require rescuing in the first place?
Heroics are a signal of architectural debt. Every late-night save is a process that did not catch the issue earlier, a handoff that did not communicate, a decision right that was not clear, a metric that was not watched. The hero is doing the work the system should have done.
The seductive part of AI right now is that it can make heroic teams faster at being heroic. The actual move is to use AI to surface where the heroics keep being needed and to fix the system there.
The best operators I know stop rewarding heroics and start rewarding boredom. Boring delivery means the system is doing its job.
More from the Friday Frame archive.
- 9 October 2026
What’s changed since we approved it?
Does the approval still fit the work?
- 2 October 2026
What changes after the training?
Training becomes useful when people have the workflows, incentives and support to put what they learn into practice.
- 25 September 2026
A shared platform still needs local judgement.
Scaling across markets means deciding what stays consistent, what local teams can adapt and who has authority to act.
Get a heads up when there is new writing here.
I publish irregularly. The Friday Frame ships most weeks. The longer essays land when they are ready. Drop your email and you will get a note when something new goes up, or when an existing post gets a meaningful rewrite. Nothing else.