π¨ CEO of @XMS_Germany | π Microsoft RD & MVP | π Author of @DevOpsGitHub and 3 other book | π£ Keynote speaker | π Organizer @GitHubMeetup @AzureStuttgart
Forty-eight slides. Zero working software.
That line opens Chapter 1 of The Horizon Problem.
A lot of transformations look agile on the surface but still move like waterfall underneath.
(1/4)
Heroes are useful in a crisis.
They are terrible as a habit.
If a system needs a hero to function, it isn't a system. It's a dependency with good storytelling.
Chapter 16 of The Horizon Problem. π§΅π
Tom was the expert everyone called when production burned.
Now he teaches.
"You own your pipeline. You own your environment. You own your metrics. I'm not your bottleneck. I'm your backup."
The win isn't Tom saving the day. It's nobody needing him to.
π§΅ "You're not losing control. You're gaining trust."
Scaling is where most transformations die β because orgs confuse copying success with scaling success. π
π§΅ "Because every hour you wait, the bank pays twice. Once for the work not done. Again for the work that becomes rework."
A CFO finds $126M in annual inefficiency hiding inside delays, bottlenecks, and process. π
"Teams that deliver customer value get more investment. Speed is just one factor. Impact is what matters."
Finance stops funding activity and starts measuring outcomes. The Leadership Layer shifts.
"We don't need an approval. We need a decision."
Beyond Horizon just eliminated 17 committees. Then a payments alert tested whether its leaders would really trade hierarchy for speed. π
"From this moment forward, we make decisions based on risk and context, not hierarchy."
Governance didn't disappear. Gates became guardrails, and leaders stopped outsourcing accountability to meetings.
Before: 43h from detection to rollback β six managers, three committees.
After: 18 minutes β team-level guardrails, no escalation.
Re-ran it six times. Pattern held.