A year ago, the industry got a new term: ResOps. I wasn’t sure buyers would ever self-identify with it, or that it wasn’t just a new label for a product stack.
A year later, I’ve changed my mind, with the recognition that ResOps can’t be just for the CIO’s and CISO’s teams. Two objections, two revelations, who still needs to be in the room, and why.
A year ago, one data protection vendor introduced the term ‘ResOps’ (Resilience Operations). Initially, I didn’t get it … now, I do.
Objection One: Who calls themselves ResOps?
With 35 years in one industry, I’m often leery when any vendor tries to redefine a market by changing or creating new taxonomy. In this case, my misgiving was due to me spending half my time with tech vendors and the other half with business continuity, crisis management, and disaster recovery communities. In all that time, I’d never heard someone self-identify as a VP or Director of ‘Resilience Operations’ and definitely not a CRO of that acronym. So, my concern was: would the buyer self-identify with this new term?
DPM’s own Organizational Resilience research reveals that there are myriad stakeholders involved in any enterprise resilience initiative; in fact, those BC, CM/EM, IT-DR, and InfoSec roles often don’t align until the C-suite.
Revelation One: ResOps requires encompassing the diverse perspectives and personas (well beyond IT and security) that collaborate in order to achieve resilience outcomes.
Objection Two: Is ResOps a Product or Suite?
No! You cannot productize a business outcome; case in point: no one can buy ‘Business Continuity’. You can buy the technologies, establish the processes, and hire the people to enable your organization to have higher business continuity. If a vendor decides that the breadth of their offerings’ technical capabilities meets what they believe orgs need to achieve resilience, then it would be tempting to over-rotate and call their platform or solution a ResOps ‘stack’. The problem is that you cannot buy a box of resilience like you can a carton of milk.
Revelation Two: ResOps cannot be commoditized or packaged. Aligning product strategy and feature prioritization around enabling ResOps scenarios is a very good thing; just don’t over-sell it as a business outcome.
What does ResOps mean for the industry?
If ResOps isn’t just about people nor about technology, then what is it?
In the classic triangle of ‘People, Process, Technology‘, ResOps is or ought to be the ‘process‘; or more specifically, the strategy and culture of continuous improvement through the collaboration of rallied stakeholders (people) leveraging technologies that are purpose-built to help enable resilience outcomes.
Commvault got it right when they introduced the ResOps term. Their launch message was a framework, but the content that followed was aimed at the people; and that’s what worked, because it elevated the visibility of those diverse and often siloed resilience professionals and leaders, and the strategic weight of their work. Veeam validated the terminology six months later, such that ResOps stopped being a single vendor’s taxonomy and is, instead, the new market condition. This does not dismiss the technical innovations of those two nor the other data protection and resilience vendors; ResOps simply names the mindset that encompasses more than just great tech.
That said, most of the ResOps conversation so far has largely centered on bridging IT operations and security; the CIO’s teams and the CISO’s teams. That’s the right place for technology vendors to start the conversation, but resilience has never been only an IT outcome. The business continuity, disaster recovery, and crisis management professionals who own the plans, run the exercises, and answer to the board when operations stop have to be in the room. And so do the mitigations that never touch a backup server (alternate work sites, manual workarounds, crisis communications, supplier contingencies). Otherwise, ResOps risks becoming ‘SecOps with Backups‘.
Between the ever-present threat of cyber, the heightening challenges around identity, and the alarming ramifications of errant AI, the pivot from ‘Reactive to Proactive to Continuous‘ cannot be overstated.
That maturation of people, process, and technology has already been borne out through DevOps and SecOps, so it makes sense that ResOps would help transform its market in a similar way; by allowing everyone to assess myriad technologies, utilized by disparate personas with unique mandates, that ought to be better connected in their processes and metrics, while aligning to a shared business outcome with existential ramifications.
To those using (as well as those not yet using) the ResOps term, differentiation will not come through marketing superlatives or features. It will come from whether the diverse personas (not just the CIO and CISO, but also the BC/DR, crisis, and business leaders) believe those capabilities will help them work together to achieve their org’s resilience goals.
Welcome to ResOps; now, let’s make sure everyone who owns the outcome is in the room.
Follow DPM on LinkedIn for weekly vlogs and other commentary on data protection, BC/DR, cyber resilience, and BaaS-DRaaS.
Leave your thoughts on the LinkedIn article.


