The 15-Minute Meeting Every Leadership Team Should Have
If a disruption hit your business tomorrow, would your team respond with confidence — or discover the gaps in real time? September is National Preparedness Month. Here are five questions that reveal exactly where you stand.
The 15-minute preparedness meeting is a short leadership conversation built around five questions: what to restore first, who makes decisions during a disruption, how you'll communicate if normal tools fail, your biggest operational dependency, and what you'd wish you had prepared. September — National Preparedness Month — is the ideal time to run it. Clear answers signal readiness; uncertain answers reveal the gaps to fix first.
Why National Preparedness Month is the perfect time to run this meeting
If an unexpected disruption hit your business tomorrow — a ransomware attack, a burst pipe, a multi-day power outage — would your team handle it with confidence? Most owners assume the answer is yes. In practice, many don't discover the gaps in communication, decision-making, and recovery until they're already responding in the moment.
September is National Preparedness Month, the FEMA-backed campaign that encourages organizations to check their readiness before an emergency forces the issue. It's a natural prompt for a conversation most leadership teams keep postponing. The good news: you don't need an all-day offsite or a 40-page binder. You need 15 minutes, the right people in the room, and five direct questions.
We've spent more than 20 years helping Rhode Island, Massachusetts, and Connecticut businesses recover from the disruptions that actually happen here — winter storms, hardware failures, cyber incidents, and the occasional "the one person who knew how to do that just left." The pattern is consistent: the businesses that weather disruption best aren't the ones with the most technology. They're the ones that checked instead of assumed.
The gap between confidence and readiness is wider than most owners expect:
What are the five questions?
Here's the whole meeting at a glance. Read each question aloud, then gauge your team's answer against what readiness actually sounds like.
| The question | A prepared answer sounds like | A warning sign |
|---|---|---|
| What do we restore first? | "We know the two or three functions that protect revenue and customers, and the order to bring them back." | "We'd try to restore everything at once." |
| Who makes the call? | Named owners for starting the response, updating staff, customer comms, and vendors. | "We'd figure that out in the moment." |
| How do we communicate? | A backup channel employees and customers already know about. | Everything runs through email and one phone system. |
| What's our biggest dependency? | We've identified our single points of failure and documented them. | One person or one system holds knowledge no one else has. |
| What would we wish we'd done? | Backups tested, contacts current, key processes written down. | "We assume it works, but we haven't actually checked." |
If our business stopped operating tomorrow, what would need to be restored first?
You likely know which tools your team touches every day. Recovery planning asks a sharper question: if everything stopped at once, what has to come back first? The honest answer is rarely "all of it." It's the handful of functions that protect customers, revenue, and the work already in motion — customer support, payment processing, scheduling, order fulfillment, or the files employees need to keep moving.
For a medical practice, that might be the electronic health record and the phones. For a manufacturer, it could be the systems that keep the floor running and orders shipping. For a professional services firm, it's often email, document access, and billing. The specifics vary; the discipline doesn't. When you rank recovery priorities before a disruption, your team stops trying to fix everything simultaneously and starts protecting what can't sit idle. That ranking is the foundation of a recovery time objective — the target for how quickly each critical system needs to be back.
Who is responsible for making decisions during a disruption?
Pressure exposes unclear ownership fast. When people don't know who can make the call, they wait for approval, duplicate effort, or pull leaders into three separate conversations that slow everything down. A workable plan names who does what: who starts the response, who updates employees, who talks to customers, and who coordinates with vendors, service providers, and your IT partner.
These roles aren't a rigid chain of command — they're a way to remove hesitation when timing matters. In a small business, one person may own several roles, and that's fine, as long as it's decided in advance rather than improvised at 7 a.m. during an outage. Write the names down, and make sure a backup is named for anyone who might be unreachable. Clear ownership is what lets people act with confidence when the normal routine breaks down, instead of freezing until someone senior weighs in.
How would we communicate if our normal tools weren't available?
Email, phones, and collaboration platforms feel dependable right up until they don't. When they go down, even simple communication gets harder than it should. Three questions surface the gap quickly: if employees couldn't reach their email, would they know where to look for instructions? If the phone system failed, how would customers reach your team? If your usual collaboration tool went dark, where would leadership post updates and assign work?
A backup communication plan doesn't have to be elaborate. It needs one dependable, pre-agreed place for people to turn — a text-message tree, a secondary messaging app, a call-forwarding path, or a simple status page. The key is that employees and customers already know about it before they need it. For New England businesses that lose power and connectivity to winter storms more often than they'd like, a communication fallback isn't a theoretical exercise — it's the difference between a calm response and a scramble.
What's our biggest operational dependency?
Some risks hide in plain sight because they quietly hold the business together every day. It might be one software platform, a single internet connection, a third-party provider, or an employee who knows a process no one else fully understands. Under normal conditions these dependencies look harmless. The problem is that a single failure can ripple across several parts of the business at once.
Ask the question directly: if this one system, provider, or person suddenly wasn't available, what would break, and how much of the business would it touch? The answer tells you where to invest first — documentation, testing, a backup option, or outside support. This is also where "key person risk" often lives in small companies: the office manager who alone knows the billing workflow, or the technician who set up the network years ago. Naming those single points of failure is uncomfortable, which is exactly why so few teams do it — and why it's worth 60 seconds of honesty in this meeting.
If a disruption took place tomorrow, what would we wish we'd prepared today?
This question works because it drops leaders straight into the moment they're trying to avoid. The answers tend to be concrete and a little humbling: we wish we'd documented that process, tested the backups, updated the contact list, agreed on who does what, or decided the order in which systems should come back online. None of it sounds urgent during a normal week, which is precisely why it keeps getting pushed aside.
Preparation buys you room to respond instead of react. The best recovery plans answer questions before anyone has to ask them — so the team spends a disruption executing a plan, not inventing one. If your honest answer to this question is a list of "we've been meaning to," that list is your roadmap. Pick the top one or two items and close them this quarter, before something else sets the timeline for you.
How to run your 15-minute preparedness meeting
The format is deliberately simple so it actually happens. Use this as your agenda.
What this means for RI, MA & CT businesses
Preparedness looks a little different in southern New England, where weather, infrastructure, and compliance all shape the risk picture.
New England weather is an operational risk
Nor'easters, ice storms, and summer thunderstorms knock out power and connectivity across RI, MA, and CT every year. A recovery plan that assumes the lights stay on isn't really a plan.
Downtime hits small teams hardest
When a 15- or 30-person business loses its core systems, there's no spare department to absorb the work. Every hour offline is felt immediately across the whole company.
Compliance is part of readiness
Massachusetts 201 CMR 17.00 and Rhode Island's breach-notification law both expect documented safeguards and a response process — the same things this meeting surfaces.
A local partner who actually answers
From our North Smithfield headquarters, our team responds without outsourcing, and onsite visits are included in our plans — so help is local when a disruption is anything but convenient.
Where an IT provider comes in
After working through the five questions, you'll know which answers feel solid and which rest on assumptions. That's where the right IT partner helps: identifying operational risks, testing recovery processes, verifying that backups actually restore, documenting key systems, and connecting technology planning to your business goals. The point isn't to make preparedness feel technical — it's to understand how your systems, people, and processes work together when pressure hits. It's the same principle behind IT Free Fall, the book our team wrote for owners who want technology to support the business instead of surprise it.
Business preparedness FAQs
National Preparedness Month is a FEMA-backed awareness campaign held every September that encourages individuals and organizations to prepare for emergencies before they happen. For businesses, it's a natural prompt to review disaster recovery, communication, and continuity plans while there's no active crisis forcing the decisions.
It's a short, focused leadership conversation built around five questions: what to restore first, who makes decisions during a disruption, how you'll communicate if normal tools fail, your biggest operational dependency, and what you'd wish you had prepared. Clear answers signal readiness; uncertain answers reveal gaps to fix before a disruption forces the issue.
At minimum, review preparedness once a quarter, and again after any major change such as a new core system, an office move, or a significant staffing shift. A brief, recurring check keeps recovery priorities, contact lists, and responsibilities current — which matters because outdated plans tend to fail at exactly the wrong moment.
A backup is a copy of your data. A disaster recovery plan is the documented process for restoring systems, data, and operations after a failure — including who does what, in what order, and how quickly. Backups are one ingredient; a recovery plan is the full recipe. Many businesses have backups but have never tested whether they can actually recover from them.
RTO stands for Recovery Time Objective — the target for how quickly a specific system or function needs to be back online after a disruption. It matters because it forces you to rank what's critical and to size your backup and recovery approach accordingly. A shorter RTO for revenue-critical systems usually justifies a more resilient recovery setup.
Yes. Small businesses are often more exposed than large ones because they have less slack to absorb a disruption. Rhode Island, Massachusetts, and Connecticut businesses also face regular weather-related outages, and rules like Massachusetts 201 CMR 17.00 and Rhode Island's breach-notification law expect documented safeguards and a response process. A continuity plan addresses both the operational and the compliance side.
A good IT provider helps identify operational risks and single points of failure, test recovery processes, verify that backups actually restore, document key systems, and connect technology planning to business goals. The aim is a plan your team can execute under pressure rather than one that only exists on paper — and a local partner can be onsite quickly when a disruption calls for it.
Preparation gives you room to respond instead of react
If your leadership team can answer all five questions clearly, you already have a strong sense of how your business would hold up under pressure. If a few answers feel uncertain, you've found exactly what to strengthen before it matters. Schedule a discovery call and we'll help you pressure-test your readiness and build a recovery plan that's ready before you need it.
Schedule a discovery call