SaaS Incident Management Best Practices – Epilogue (The STORM™ Series)

“If you want a happy ending; that depends, of course, on where you stop your story.” (Orson Welles) This is the final post, covering Incident Management in a SaaS Operational Environment. The previous posts discussed the Prologue, Act I and Act II which covered the preparations and how to react and then how to act in an incident. As much as

SaaS Incident Management Best Practices – Act II (The STORM™ Series)

“A thought which does not result in an action is nothing much, and an action which does not proceed from a thought is nothing at all” (Georges Bernanos)   This post is the third, covering Incident Management in a SaaS Operational Environment. The previous post covering the initial activities of the incident, discusses the more reactive

SaaS Incident Management Best Practices – Act I (The STORM™ Series)

“It is not stress that kills us; it is our reaction to it” (Hans Selye) This is the second posting of the Incident Management Best Practices.  The first part covered the Prologue – the preparations that will improve your survival rate for the next incident that is just waiting to happen. The main story contains

How to Get Customers to Help You Innovate

Where does innovation begin? When you consider how world-changing products have been developed, it’s natural to think that a visionary leader like Steve Jobs is the most important ingredient in driving innovation. However, many innovations have been generated without a single creative genius as their architect. Sometimes it’s the research of many people over many

SaaS Incident Management Best Practices (The STORM™ Series)

Dani Shomron, a veteran of the software industry, has been active in SaaS since 2000 and has been writing in his SaaS Perspectives blog since 2006. He is an international expert on Transition to SaaS and SaaS Service Operations, Over the years of running and consulting on SaaS Service Operations, Dani developed the STORM™ methodology