We Make Resilience Work.
Most organisations are in a resilience crisis they haven't named yet. Similar incidents, every quarter, despite the postmortems, the dashboards, and increasingly, the AI. We help you see what your practices stopped showing you.
You'll recognise this.
Most of our engagements are undeclared crisis management projects.
The organisation has the practices — incident reviews, chaos engineering, DR plans — but the feedback loops that should turn those practices into learning are broken. Signals get absorbed without action. Prevention work loses to the backlog every quarter. The people closest to the problems can see what's wrong, but the organisational structure doesn't carry that information to where decisions get made.
Start with diagnosis,
then build from there.
Most organisations start with the Resilience Assessment. Once we've identified what's actually broken, we can help you strengthen specific capabilities or partner for long-term transformation. But diagnosis comes first — you need to know what to fix.
The problem you're facing: Your organisation keeps having the same types of incidents despite doing retros, chaos engineering, and architecture reviews. Something organisational is broken — but what?
We diagnose the feedback loop failures and organisational patterns that prevent your teams from learning and adapting. We embed with your teams to see how work actually happens versus how it's described. We participate in your incident reviews, observe GameDays, sit in on chaos experiments, and join operational readiness reviews. We watch how teams interact, what incentives and pressures they face, and where the gaps appear between policy and practice.
Through this combination of observation and structured interviews, we identify exactly what's blocking resilience and give you a clear roadmap to fix it.
- Embedded observation of your actual resilience practices (incident reviews, GameDays, ORRs, chaos experiments)
- Stakeholder interviews across engineering, ops, and leadership
- Deep analysis of your feedback loops and incident patterns
- Written report with prioritised, actionable recommendations
- 2-hour executive readout session with your leadership team
Once we've identified what's broken, we help you build specific capabilities to address the gaps. These are focused 2-4 month engagements that build one capability deeply.
Recent Strengthen engagements have included designing chaos engineering programmes from scratch, rebuilding incident analysis processes to focus on organisational learning rather than action-item compliance, and establishing Operational Readiness Reviews that teams actually trust.
- Chaos Engineering Programs — Design and implement systematic resilience testing
- Operational Readiness Reviews — Validate systems are actually ready for production
- Incident Analysis Process — Improve how your teams learn from failures
For organisations ready for comprehensive change, we offer ongoing strategic partnership to embed resilience into your culture and operations. We become a long-term partner embedded in your leadership rhythm, joining monthly strategy sessions, running quarterly health assessments, and serving as a sounding board when new challenges emerge.
- Monthly strategic sessions with leadership
- Quarterly organisational health assessments
- Ongoing advisory as you implement changes
- Access for architecture reviews and escalations
No prescriptive checklists. We study your organisation's culture first
Founder-led. The person you talk to is the person doing the work
Diagnosis before prescription. We don't sell solutions to problems we haven't seen
What you need to hear, not what you want to hear
The work speaks
for itself.
Adrian Hornsby has spent nearly 25 years building and operating software systems, from research and telecommunications at Nokia through multiple startups to nearly a decade at AWS, where he progressed from Solutions Architect to Principal Engineer on the AWS Fault Injection Service team. He authored much of AWS's resilience and chaos engineering guidance, trained field communities across the organisation, and worked with internal teams including Prime Video, Amazon Search, and Lambda. He also holds a patent for fault-injection impact zone identification.
He is the author of Why We Still Suck at Resilience and writes the Resilience Bites newsletter. His work draws on resilience engineering research to explain why organisations keep having similar incidents despite doing all the right things, and his framework goes beyond tooling and process into the organisational patterns, feedback loops, and tensions that determine whether resilience efforts actually work.
Today, through Resilium Labs, Adrian works with Fortune 500 companies and growth-stage organisations across the world to diagnose broken resilience programmes and help teams build the capabilities to fix them. Most of these engagements are undeclared crisis management projects — organisations that aren't in flames, but can't see what's wrong. He advises VC portfolio companies on engineering practices, serves on advisory boards, and speaks regularly at conferences across the globe.
Why We Still Suck at Resilience
“What accumulates isn’t always what matters.”
Chapter 3 — Why Practices Fail to Build Learning
Your organisation does incident reviews, runs GameDays, and practises chaos engineering. So why do similar incidents keep happening? This book explains why, and what to do about it.
Writing on resilience,
organisations, and AI.
Free tools. No sign-up.
Built to make visible the things most organisations leave invisible.
Ready to find out what's actually broken?
The best first step is a conversation to understand your current challenges and resilience goals. We'll help you figure out which step in the journey makes sense for your organisation.
Book a Diagnostic Call