We Make Resilience Work.
We help engineering organizations understand why they keep having the same types of incidents — despite doing incident analysis, GameDays, operational readiness reviews, monitoring, chaos engineering, and increasingly, even AI.
SCROLL ↓THESIS_Your organization has invested in resilience practices, but the feedback loops that should turn those practices into actual learning are broken.
You'll recognize this.
IS THIS YOUR REALITY_These aren't isolated problems. They share a common root. Incidents get reviewed but the insights don't spread. Experiments get run but the results don't change decisions. The gap between how your resilience program looks on paper and how it works in practice is where the real problem lives.
NEW BOOK_
Why We Still Suck at Resilience.
Your organization does incident reviews, runs GameDays, and practices chaos engineering. So why do the same incidents keep happening? This book explains why, and what to do about it.
HOW WE WORK_Start with diagnosis, then build from there.
Most organizations 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.
-
Your organization keeps having the same types of incidents despite doing retros, chaos engineering, and architecture reviews. Something organizational is broken — but what?
We diagnose the feedback loop failures and organizational 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 prioritized, actionable recommendations
✓ 2-hour executive readout session with your leadership team
6-8 weeks from kickoff to delivery
-
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 programs from scratch, rebuilding incident analysis processes to focus on organizational 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
2-4 months, after assessment
-
For organizations 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 organizational health assessments
✓ Ongoing advisory as you implement changes
✓ Access for architecture reviews and escalations
6-12+ months of collaboration
No prescriptive checklists. We study your organization'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
WHAT PEOPLE SAY_The work speaks for itself.
Our team
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 organization, 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 organizations keep having the same incidents despite doing all the right things, and his framework goes beyond tooling and process into the organizational 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 organizations across the world to diagnose broken resilience programs and help teams build the capabilities to fix them. He advises VC portfolio companies on engineering practices, serves on advisory boards, and speaks regularly at conferences across the globe.
Based in Finland. Working globally.START A CONVERSATION_Ready to stop fighting fires?
The best first step is a conversation to understand your current challenges and resilience goals. We'll explore whether our approach aligns with your needs and discuss which step in the journey makes sense for your organization.