Insights & updates from our experts

Resilience Engineering: The What and How
- The Field Guide to Understanding Human Error
- Resilience Engineering: Concepts and Precepts
- Courses in Lund University’s program on Human Factors & System Safety
- Friendly Fire: The Accidental Shootdown of U.S. Black Hawks over Northern Iraq by Scott A. Snook
- Newsletter - Resilience engineering for software people
- Resilience engineering papers with contributions by John Allspaw
- Drift into Failure: From Hunting Broken Components to Understanding Complex Systems
- The Power of Intuition: How to Use Your Gut Feelings to Make Better Decisions at Work by Gary Klein
- Common Ground and Coordination in Joint Activity by Gary Klein, Paul J. Feltovich, Jeffrey M. Bradshaw, and David D. Woods
- Diversity and Complexity: 2 - Primers in Complex Systems by Scott Page
- How complex systems fail

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














