Most of what goes wrong with a BIA doesn't look wrong at the time. The workshop runs to schedule, the template gets filled in, and everyone leaves with the box ticked. The problems show up months later, when a plan is built on a recovery time nobody can meet, or an exercise rests on a dependency nobody mentioned.
The BIA is where most of a BCM program starts. Recovery priorities, continuity plans, the scenarios you exercise and the picture leadership gets during an incident all rest on what people told you in those first conversations. If the answers are guesses, the guesses travel.
That's why I've come to think data quality is mostly decided before anyone answers a question. It depends on how well the person answering has been prepared: whether they understand why you're asking, know what you need from them, and get the question in words they recognize.
In my last field note, I wrote about what happened when we showed a team their BIA as a picture, and how much more invested they became once they could see where they fit. This time I want to take a step back and explore what happens before and during data collection, and why that matters just as much as what we eventually do with the data.
The people with the answers aren't BCM people
Most of the knowledge a BIA needs sits with people who don't work in business continuity. They run payroll, manage a warehouse, look after a customer platform. They know their work in detail. They just haven't been asked to describe it in BCM terms before, and often nobody has told them why it matters.
When people don’t fully understand the purpose of the BIA, it can affect both their engagement and the information they provide. Some may see it as another task competing with their daily responsibilities, while others may struggle to assess what is genuinely critical to the business. In workshops, I’ve seen how this can lead to recovery requirements that don’t necessarily reflect the actual consequences of disruption.
Providing more guidance isn't necessarily the solution. Written instructions can be helpful, but they don’t always give people the context they need to understand what we’re asking or why it matters. That’s why I think it’s important to focus not only on what information we need from participants, but also on how we engage them and help them understand the purpose of the BIA.
Engagement starts before the first question
I’ve come to see BIA workshops as more than an opportunity to collect information. They’re also about getting people engaged in the process and helping them understand why their input matters. And I’ve noticed that the groundwork for that engagement often starts well before the workshop itself.
Leadership. Function heads need to be on board, and that rarely happens because BCM asked nicely. It tends to come from proof: a customer's due diligence questionnaire, a regulator asking questions, or a disruption that's still fresh in everyone's mind. Those are the moments to show what the BIA is for.
Sponsorship. Getting leadership on board once is different from having them stay there. A sponsor removes barriers, makes decisions when teams disagree, and keeps continuity on the agenda after the first round of workshops is over. That's what makes the BIA a business priority instead of a BCM request.
Ambassadors. Everyone owns a piece of BCM, but someone in each function, location or team needs to own it locally. A trusted person inside the team gets better answers than I do from the outside, because they know where the real dependencies sit.
Language. People need to understand what we're asking, and why. That sounds obvious (and honestly, it applies to far more than BCM), but the language we use can be one of the biggest barriers to getting meaningful BIA data. I'll come back to that in a moment.
Now, leadership buy-in, sponsorship and building an ambassador network aren't things you tick off before starting your BIA. They're ongoing efforts, and often take years to get right. So don't read this as a checklist of things you must have in place before collecting data. Think of them as levers that make the process easier, and your BCM program stronger, over time.
But there are also things you can do right now, before the next workshop, that make a real difference. And much of it comes down to preparation.
A short pre-read sent ahead of the workshop, explaining what you will be doing, why a specific team was asked, and what we'll do with the answers, changes the room. People arrive knowing why they're important to it. A simple template showing the kind of information we'll ask about means they can think it through beforehand. Then the workshop time goes on discussion, agreement and buy-in, rather than spending most of it interviewing people cold.
Drop the jargon, use the scenario
BCM comes with its own terminology. MTPD, RTO and RPO all serve a specific purpose, but they’re not necessarily familiar concepts to the people participating in BIA workshops. That’s why, rather than focusing on technical terminology, we use language people can relate to.
In the workshops we facilitate, we try to make questions as practical as possible. Instead of asking about the maximum tolerable period of disruption, we explore when a disruption starts to hurt the business and at what point the consequences become intolerable.
Scenarios can help make those questions more concrete. For example, we’ll ask something like: “if this service went down, when would your customers notice? When would it become a serious problem?” These conversations help us understand how the consequences of disruption develop over time and establish recovery requirements based on actual impact.
The substance stays the same for every team, role and level. The language changes.
There’s another aspect of language worth paying attention to. Different parts of the business often use different names for the same process, system or supplier. One team’s “order platform” might be another team’s “the portal”. If we don’t recognise these differences, we risk collecting inconsistent information across BIAs. Understanding the language people use in their daily work helps us identify connections between teams and build a more accurate picture of the organization’s dependencies.
Match the method to the data
Getting people engaged is one part of the process. Another is how to collect the information we need. A BIA involves different types of information, and not all of it requires the same approach.
Some of it needs a room. Not all of it does. Identifying what’s critical, understanding how much disruption the business can tolerate, and exploring dependencies across teams often require discussion and judgement. Having the right people involved creates an opportunity to challenge assumptions and build a shared understanding.
Some information is relatively straightforward to collect, such as which systems a team uses, how many people are involved in delivering an activity, or which suppliers they depend on. A questionnaire can be a useful starting point for gathering this information. But understanding how those dependencies support specific activities, and what happens when they’re unavailable, often requires further discussion. The challenge is knowing which questions can be answered independently and which benefit from a conversation.
Then there's the large middle ground: questions that need some back and forth, but not a full workshop. This is where a guided conversation can help. Someone asks questions in plain language, follows up when an answer needs clarification, and allows people to contribute without necessarily scheduling another meeting. At Fortiv, we’ve been running BIA interviews this way with a voice agent, and it's been interesting to see how much more people say when they're talking instead of typing.
The point isn’t to replace workshops, but to use them where they add the most value, while finding more efficient ways to collect information that doesn’t require everyone in the same room.
Knowing when to stop digging
There's a temptation, once people are engaged and answering well, to keep asking. Another field, another dependency layer, another round of questions. It feels thorough. But more data doesn't build resilience on its own. What builds it is the signal that comes out of the data: relevant evidence, then choices you can act on.
The more complexity you build into collection, the harder that signal is to find. Every extra question costs the person answering a little more attention, and you'll feel it in the quality of the later answers.
So I try to keep the scope honest:
- Start with the products, services and outcomes that matter most.
- Get the people in the room who understand the business impact, the customer commitments, the regulatory obligations and the operational dependencies.
- Work out what has to continue, who and what makes it possible, and where disruption would have unacceptable consequences.
Once you know what you need to protect, stop digging. Then take what you've collected back to the people who gave it to you, so they can see what it became. I wrote about that step last time, and it's what makes the next round of collection easier.
Good BIA data comes from asking the right questions, of people who understand why they’re being asked. That work starts well before the workshop, and in my experience, it’s where the quality of everything that follows is decided.
Field Notes on Resilience is a series by Nynne Svenningsen, BCM Consultant at Fortiv, sharing observations from the field on how resilience and business continuity are applied in practice.




