Why Every Operational System Should Begin with a Needs Assessment
Mitzi Orkus
Why Every Operational System Should Begin with a Needs Assessment
8:49
Authored by Mitzi Orkus, Director of Strategic Growth, KAStrack
Organizations usually start looking for operational software because something has to change. Sometimes it's an obvious problem: an audit exposes gaps in documentation, a certification expires without anyone noticing, or a corrective action goes unresolved because responsibility was never clearly established. Other times nothing has gone wrong yet, but the organization is growing, adding locations, and finding that the spreadsheets and informal processes that worked at one scale won't carry the next.
Either way, the next move is usually to start looking at software, and that's where the process gets ahead of itself. Before anyone decides what a system should do, someone has to understand how the operation actually works.
What a demo can't show you
A good demo shows you what a system can do. It becomes a problem when it also decides what the organization needs. A system can look impressive in a controlled environment, with workflows that make sense and reports that are neatly organized, but that's not necessarily how your operation runs.
Maybe the organization has three locations following slightly different procedures. Maybe supervisors are maintaining their own tracking spreadsheets because the official process doesn't account for the exceptions they encounter. Maybe leadership believes inspections are being documented at the end of every shift, while the people performing them are collecting paper forms and entering the information several days later.
Those differences matter when you're designing a system people will actually use.
One of the first things I want to understand in a Needs Assessment is whether the process leadership describes is the same one employees follow. Sometimes it is. Other times there's a gap, and that doesn't mean anyone is doing something wrong. Different people see different parts of the operation, and informal workarounds become so routine that nobody thinks to mention them. But if we configure a system around an incomplete understanding of the work, we'll reproduce those gaps in a new place.
What a Needs Assessment should accomplish
At KAStrack, a Needs Assessment is where we learn how the organization operates before making recommendations about configuration and implementation. We examine the processes the organization relies on, how responsibilities are assigned, where records are maintained, and what happens when work doesn't go according to plan. We also want to understand what leadership needs to know and what frontline employees need in order to do their jobs.
The goal isn't simply to identify problems that software might solve. It's to establish a shared understanding of the operation and what would need to change for a new system to be useful.
One of the most valuable parts of this process is the written report. Every organization that completes a KAStrack Needs Assessment receives a formal report it can keep, whether or not it decides to buy the software. It documents what we learned about the operation, the gaps and opportunities we found, and our recommendations for moving forward. It also gives the client something concrete to review instead of relying on a meeting or a demo, and a chance to correct us. If our understanding of a process is incomplete, they can say so before that misunderstanding becomes part of an implementation. That's a much better foundation for a software decision.
Why the Needs Assessment Comes First
“I’ve learned that when an operational system is chosen before the operation is understood, the result is often wasted effort and expense. The company may end up with something it doesn’t need, isn’t ready for, or can’t use within its existing culture.
The frontline usually makes that clear quickly. If a system doesn’t fit the way people do the work, they won’t adopt it. Without that adoption, leadership won’t get the results it expected, and the system won’t help build a stronger culture. Going straight to configuration before listening is a quick way to discover that the solution looked right on paper but wasn’t fit for purpose.
That’s why the relationship with the client matters more than the technology by itself. KAStrack is an operational framework, and every organization has its own needs and constraints: its org chart, the people who fill different roles, and the workflows it actually uses. Off-the-shelf technology makes assumptions. Those assumptions don’t always match the customer.
The conversations between our team and the client help us understand how the organization functions and what it needs for implementation to succeed. That shared understanding is what allows us to configure a framework around the organization’s real work, rather than ask people to reshape their work around a standard setup. What gets built in KAStrack should reflect that organization’s purpose and needs.
For a compliance, safety, or operations leader, the most important thing to bring to a Needs Assessment is honesty about how the organization works today. The goal isn’t to fit into something already engineered for you. It’s to understand your operation well enough to design the right structure for it. There isn’t one process we use for every organization. The way a client’s KAStrack account is configured depends on the workflows people use in practice and what the organization needs.”
Robert Claypool, Founder, KAStrack
What gets decided before anything is configured
Configuration isn't just a technical decision. Someone has to decide which responsibilities belong to which roles, what information gets captured, what happens when a deadline is missed, and who has the authority to review and approve completed work. Those decisions exist whether or not the organization has software to manage them. A Needs Assessment is where the team looks at them before they turn into configuration problems.
It also separates the issues that need a system change from the ones that need a management decision. If nobody has established who is responsible for confirming that a corrective action was completed, another status field won't fix that. The organization still has to decide what accountability looks like. Once those expectations are set, the technology can support them.
And because operations change, the work doesn't end at implementation. For clients on KAStrack Complete, a Quarterly Continuous Review gives the client and us a regular chance to revisit workflows, look at what's working, and adjust as the organization evolves. The Needs Assessment sets the starting point. The Continuous Reviews keep the system aligned with the work.
Before you choose an operating system
If you're evaluating operational software, I'd encourage you to ask a few questions before comparing features.
For operations leaders: Has anyone examined how the work is actually performed, including the exceptions, workarounds, and informal processes that don't appear in written procedures?
For executives: Can your team explain which operational problems the system needs to address, how success will be evaluated, and what might need to change for implementation to succeed?
For software providers: Can you explain how the organization's requirements will influence configuration, rather than simply demonstrating the available features?
A Needs Assessment won't eliminate every challenge that comes with implementation. But it can identify important requirements and constraints before an organization commits to an approach that doesn't fit. The first question shouldn't be which system has the most features. It should be whether the organization understands what the system needs to accomplish.
That's where we start at KAStrack.
If you'd like to examine how your operation works today, where the gaps are, and what a system would need to support, we can start with a Needs Assessment.
Have a question about this? Email Mitzi directly at morkus@kastrack.com.
About the author: Mitzi Orkus, a petroleum engineer turned growth strategist, is the Director of Strategic Growth at KAStrack. Before joining the company, she was a client for six years, using KAStrack to improve the way she ran her own business. Today, she helps other organizations move from chasing proof to producing it as part of how work is done.
Read the earlier articles in this series:
