In this article, Will Mosenthal, Director of Transformation & Delivery at PKG Safety Innovation, explains why business analysis is the missing role in many safety technology projects and how to set it up well.
It's three months after the go-live of the new digital safety management system. At the monthly safety leadership meeting, a site manager raises that supervisors can't close out corrective actions from the field in the new system. The technology vendor points to the agreed specification. Closing corrective actions from the field had never been included. Nobody realised they needed to ask for it.
Most people who have worked on a safety technology project have sat in some version of this meeting. The instinct is nearly always to blame the product or the vendor. In our experience, the cause starts earlier in the project lifecycle. More often than not, there was no one owning the work of defining what the system needed to do, in enough detail, with the right people agreeing to it before anyone built it. This is what a Business Analyst (BA) does.
The role of a BA
The International Institute of Business Analysis (IIBA), the global professional body for the discipline, describes business analysis as enabling change by "defining needs and recommending solutions that deliver value to stakeholders". The best BAs are solution agnostic and aren't tied to a tool, trend or methodology, and their focus is the root of the problem, not the solution they've been handed. In practice, good BA work covers ten key activities across the whole life of a project, from before anything is built to after go-live.
- Understanding the current state. Before anything is designed, a BA works out why the organisation needs to change and how that need relates to the way it currently operates. That means mapping how a business process is actually carried out, not how the documented procedure says it should be. The future state is then defined against that baseline.
- Eliciting needs, not wants. IIBA describes elicitation as drawing out the "actual needs of stakeholders, not simply their expressed desires". A request for a new form is a desire articulated as a solution. The need might be faster turnaround on approvals, which a form may or may not solve.
- Specifying requirements to a standard. The IIBA's BABOK Guide sets out the characteristics of a good requirement, including that it is unambiguous and testable. "The system should be easy to use" fails that test. "A field worker can submit a form from a phone with no network connection" would pass it.
- Supporting vendor selection. Agreed requirements give procurement something concrete to buy against. The BA helps turn them into the tender or request for proposal, shapes the evaluation criteria and assesses how each vendor's response measures up against what the business actually needs.
- Understanding the solution. A BA works with the vendor to learn what the product does as standard, what can be configured and what would need to be custom built. With that knowledge, the BA can show the business where the product fits its needs and where it doesn't. Sometimes, the BA will facilitate a decision to change a business process rather than the system being implemented.
- Mapping data and integrations. In most organisations, data sits across several disparate systems. A BA works out how fields map between them, where master records must be held and what data needs cleaning before it is migrated into the new system. A BA also defines upfront how long data needs to be retained and how the legacy system will be decommissioned, which is often overlooked in technology projects.
- Facilitating decisions. The BA doesn't approve requirements, but they do broker the process for how decisions get made, including who decides, how changes are assessed and how priorities are set. The BA analyses options and their impact, and the sponsor or product owner decides.
- Proving it works. A testable requirement becomes the basis for testing. The BA defines or reviews acceptance criteria, supports user acceptance testing and traces each defect back to the requirement it breaks. This drives the distinction between a genuine defect and a missed requirement.
- Preparing the business for go-live. The BA supports the move to the new system and ways of working, including cutover and training. They know exactly how the new process differs from the old one, so they're often best placed to shape training and change activities for each role and across the organisation.
- Evaluating the solution. The BABOK's final knowledge area asks whether the solution, once in use, delivers the value it was meant to. In practice, that means measuring against the baseline set at the start. This works best when the BA captured reporting requirements during design, so the data stakeholders need is still being collected long after go-live. This is a critical input to assessing the return on investment of a new technology solution.
What we see in safety technology projects
When implementing new technology in safety teams, business analysis often falls to a safety systems lead or similar role. The BA work described above is added on top of the project management and vendor management for the implementation, as well as all the other responsibilities and expectations of their day job. In our experience, few safety systems leads have had formal training or prior experience as a BA. This exposes a structural gap in how technology is implemented, and the impact often isn't seen until later.
We consistently see three signs that a safety technology project would benefit from a BA:
- The vendor's standard configuration has become your default requirements.
- Scope disagreements are settled by whoever holds the strongest view in the room.
- System defects are being raised against things nobody specified.
Most safety professionals would agree that the most effective time to manage a risk is when the work is being designed. This is the core principle behind our Better Work, By Design™ philosophy at Pocketknife Group. How work is designed shapes how it's experienced and performed, so the best time to get it right is before anything has been built, which is why the business analysis work on scope and requirements is critical to the success of a technology implementation.
Our perspective on business analysis done well
Separate the roles
Keep your safety experts close to the project as the source of requirements, and staff the business analysis with dedicated and experienced BAs.
On projects where we've seen a dedicated BA in place, the safety team has been able to stay focused on its own work, and requirements and scope have had a clear owner. The role doesn't always have to be a full-time hire. Even part-time, or for the critical early phases, a BA changes more than the safety lead's workload. In a lot of organisations, a BA's cost (and focus) can be split across multiple projects and budgets.
In our experience, a BA without a safety background has to ask the questions an expert wouldn't. This brings unstated assumptions into the open and produces requirements IT and the vendor can build from. Safety expertise is still essential, but the safety expert is the best source of requirements, not their author.
Consider the organisational structure
In most businesses, the BA role typically sits in the IT or digital organisation, often aligning to a specific part of the business, such as Finance or HR, which helps build relationships and functional context over time. For safety, the BA should be aligned to the function and work with an accountable safety product owner. Wherever the role sits, three principles help:
- Have the BA report to the business product owner. Vendors often bring their own analysts, but their job is to fit you to the product. Your BA's job is to represent what the business needs.
- Engage the BA before vendor contracts are signed. If the contract is signed before requirements are agreed, the vendor delivers its standard product first, and the real requirements work only starts after go-live.
- Put the BA alongside a project manager, not in place of one. The PM runs the project. The BA defines what it delivers.
A BA can't make decisions on the business's behalf. If nobody owns the product, or leaders aren't aligned on what they want, requirements will stall however good the analyst is. This is an organisational and cultural issue common to all technology transformations, not just safety.
Get the BA into the field
The people who will use a new safety technology every day are supervisors and frontline workers, and what they do on site rarely matches what gets described in a workshop room. Time spent watching an inspection or an investigation happen exposes the workarounds and connectivity gaps a requirement has to account for. This is why onsite immersion and observation is an integral part of PKG's Discovery process on our consulting engagements.
Use AI to make good BA work faster
Much of a BA's time goes on capturing and documenting what stakeholders say. At PKG, we use meeting transcripts and large language models to draft workshop summaries, first-cut requirements and process descriptions far quicker than we could by hand. The tools don't know which points matter or what a stakeholder left unsaid, so every draft still needs an experienced analyst to check it and take responsibility for it.
Conclusions
Organisations invest heavily in safety platforms and vendors, but rarely in the business analysis that connects the system to the work. Business analysis is a discipline with its own body of knowledge and professional standards, which we recommend embracing. Bring in a BA as soon as you think you have a problem to solve, and certainly before any new technology contract is signed. Make sure the work has a clear owner on the business side. Then your safety professionals can do what they're best at, which is the work of keeping employees safe.
If your organisation is working on bridging the gap between safety and technology or looking to build BA capability and would like to know more, please get in touch with Will Mosenthal – will@pocketknifegroup.com




