One of the most common things we hear from business owners is some version of: “If we just had a better system, my team would finally follow the process.”
It’s an understandable hope. It’s also usually wrong.
Here’s the uncomfortable truth: if a process doesn’t get followed on pen and paper, it won’t get followed once it’s online either — no matter how great and easy the system. Software doesn’t create discipline… it just makes the same behaviour faster. People have run entire businesses on paper ledgers and index cards for centuries. The format was never the problem.
Why people skip processes
Non-compliance is rarely laziness or a bad attitude. Many decades of workplace research keep landing on the same point: people tend to default to the path of least resistance, and the unconscious pull to make life simpler usually beats the abstract instruction that they’re “supposed to” do something. When a step feels like friction, it gets dropped.
Common reasons a process will be ignored:
- It’s genuinely optional — nothing breaks and no one notices if you skip it
- It’s slower than the workaround people have already invented
- They never really learned it — it was mentioned once, not embedded, not reinforced
- It doesn’t match reality of the business — designed in the office, useless on the job
- There’s no consequence — skipping it costs them nothing
Importantly “we didn’t have the right software” isn’t on that list.
The real fix: make the process non-optional
The goal of a new system isn’t to make the right thing possible. It’s to make the wrong thing hard or impossible. A process people can route around is a suggestion, not a process.
That means redesigning the workflow so the system is:
- The only path — the job can’t progress without the step (you can’t invoice until sign-off is recorded)
- The fastest path — so following the process is easier than not, so the path of least resistance is the process
- The default — the right action is pre-filled, pre-selected, already in front of them
- Self-checking — missing or wrong data is flagged at the point of entry, not months later
Before you build anything
Get honest about two things first:
- Does the current process actually work? If your best people route around it, the process may be the problem, not them. A system that automates a broken process just breaks faster.
- How and where can it be skipped today, and why? Every skip point is a design requirement for the new system.
Software is brilliant at enforcing a good process — gating steps, removing manual workarounds, making the right thing the easy thing. It can’t invent the discipline the underlying process never had.
So the question isn’t “what system will make them comply?” It’s “how do we change the process so compliance isn’t optional?” Get that right, and the software almost builds itself.
