<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Riffle]]></title><description><![CDATA[Riffle]]></description><link>https://www.riffleresilience.com/blog</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 10:40:14 GMT</lastBuildDate><atom:link href="https://www.riffleresilience.com/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Riffle Secures Investment from Atlassian Ventures to Advance Operational Resilience]]></title><description><![CDATA[Resilience is no longer just about having a plan—it’s about how work actually continues under disruption. This article explores why that shift is happening and what it means for the future of operations.]]></description><link>https://www.riffleresilience.com/post/building-resilience-where-work-actually-happens-backed-by-atlassian-ventures</link><guid isPermaLink="false">69bf1682cf14a7a450cd66fa</guid><pubDate>Thu, 02 Apr 2026 13:40:15 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/502285_691867a674e54279902d36073071f003~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Riffle Insights</dc:creator></item><item><title><![CDATA[Time to Planning — The Cost of Getting It Wrong]]></title><description><![CDATA[I built a business continuity program exactly the way I was supposed to. And it still didn’t work. Doing It “The Right Way” When I stepped into a Business Continuity Manager role, I followed the standard approach. Start with a tool. Stand up the program. Conduct a Business Impact Analysis (BIA). Use the results to prioritize planning. It was structured. Proven. Widely accepted. And it made sense—at least on paper. So I got to work. The Timeline No One Talks About I started in July. The first...]]></description><link>https://www.riffleresilience.com/post/time-to-planning-the-cost-of-getting-it-wrong</link><guid isPermaLink="false">69c17c61e26320a33935432f</guid><pubDate>Mon, 23 Mar 2026 17:48:01 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/bb5c2003660b4ea4a780df3e91d89968.png/v1/fit/w_1000,h_567,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Shane Mathew</dc:creator></item><item><title><![CDATA[Engagement — Why Business Continuity Fails Without the Business]]></title><description><![CDATA[Most business continuity programs don’t fail because of a lack of planning. They fail because the business was never truly part of it. The Illusion of Engagement Ask most organizations if their business continuity program is “engaged,” and the answer is usually yes. They’ve conducted interviews. They’ve completed Business Impact Analyses (BIAs). They’ve held workshops and walkthroughs. On paper, the business has participated. But participation isn’t the same as engagement. Most of these...]]></description><link>https://www.riffleresilience.com/post/engagement-why-business-continuity-fails-without-the-business</link><guid isPermaLink="false">69c17baf8f0e652aaa2c10a5</guid><pubDate>Mon, 23 Mar 2026 17:45:01 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/11062b_0f7614fce9b14236a6a5cbfc73e51469~mv2_d_6016_4016_s_4_2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Shane Mathew</dc:creator></item><item><title><![CDATA[Who We Are — Rethinking Business Continuity from First Principles]]></title><description><![CDATA[Most business continuity programs don’t fail because of a lack of effort. They fail because they’re built around the wrong job. The Role I Thought I Had In 2015, I stepped into a Business Continuity Manager role at DaVita Rx. On my first day, I was introduced to the organization like this: “Here’s Shane—he’s going to make sure we don’t have any more disruptions.” It was well-intentioned. But it was also wrong. Not because disruptions aren’t important—but because eliminating them isn’t...]]></description><link>https://www.riffleresilience.com/post/who-we-are-rethinking-business-continuity-from-first-principles</link><guid isPermaLink="false">69c17549b9d5370ce3240050</guid><pubDate>Mon, 23 Mar 2026 17:40:30 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/11062b_ac2a0feb70fc403dbaa1d34ec98a4ba6~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Shane Mathew</dc:creator></item><item><title><![CDATA[Welcome to Riffle — A Different Approach to Business Continuity]]></title><description><![CDATA[Welcome to Riffle. This is where we talk about business continuity—what works, what doesn’t, and what needs to change. If you’ve spent any time in this space, you’ve likely seen the same patterns: Plans that sit unused. Exercises that don’t translate to real-world action. Programs that feel disconnected from how the business actually operates. This blog exists to address that gap. How I Got Here A while back, I was at a dinner with a group of business continuity professionals. At some point,...]]></description><link>https://www.riffleresilience.com/post/welcome-to-riffle-a-different-approach-to-business-continuity</link><guid isPermaLink="false">69c176fed25f3712fa74f33d</guid><pubDate>Mon, 23 Mar 2026 17:28:09 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/nsplsh_591d684eb19e4277b8cd7eeed66b74f0~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Shane Mathew</dc:creator></item></channel></rss>