About Resilium Labs

I started Resilium Labs to do one thing well: find out why organisations keep having the same incidents, and help them change what produces them. It is founder-led on purpose.

I have spent 25 years building and operating systems, most recently as a Principal Engineer at AWS, where I worked on fault injection and wrote much of Amazon's guidance on resilience and chaos engineering.

The approach draws on disciplines most software teams never encounter: safety engineering, resilience engineering, and cognitive systems engineering, the study of how people and systems cope with what they did not plan for. Resilium Labs brings those principles into software engineering and operational excellence. Seen this way, resilience is not a state you reach or verify once. It is a capacity you build, exercise, and sustain: engineered, not assumed.

I wrote Why We Still Suck at Resilience because many organisations respond to incidents well and still keep having them. The response is not the problem. The problem is when the conditions that produced the incident stay in place, so the same failure comes back. My work starts with diagnosis, finding where that deeper work has stalled, then does the operational excellence to change those conditions so the same failure stops coming back.

Changing the wider organisation often needs depth across areas no single person carries: how leaders behave under pressure, how security and governance meet delivery, how software and data are built and operated. For that I bring in the Collective, a small group of senior specialists I have worked with directly and trust.

Resilium Labs is based in Helsinki and works with engineering organisations globally. If the same incidents keep coming back and you want to know why, the first step is a conversation.