Build around the workflow, not the template.
The fastest way to make good software useless is to design it around how the industry says you should work instead of how you actually do.
Every off-the-shelf system arrives with an opinion about how your business should run. It has a fixed path from enquiry to quote to order to invoice, and it assumes yours matches. For a generic business it might. For one with a real history and a real way of doing things, the template and the reality drift apart on day one, and the team quietly starts working around the software.
The workaround is the signal
When you watch how a business really operates, the workarounds tell you everything. The spreadsheet someone keeps alongside the official system. The WhatsApp group where the real scheduling happens. The step everyone knows to do but no tool records. These are not bad habits. They are the business logic that the template failed to capture, surviving in the only place it could.
If your team maintains a shadow spreadsheet next to the official system, the spreadsheet is telling you what the software should have been.
Design from observation, not assumption
Good internal software starts by studying how the work actually moves through the business. Who touches a job and in what order. Where decisions get made and what information they need. Where things wait, get duplicated, or fall through. Only once that real workflow is understood does it make sense to build, and what you build then mirrors the operation instead of fighting it.
- Map the real path a job takes, including the unofficial steps nobody documented.
- Find the points where information is re-entered by hand and design those out.
- Keep the decisions with the people who actually make them, and give them the data to do it.
- Let the software follow the operation, so adoption is effortless rather than enforced.
Why this matters for adoption
Software built around a template needs training, enforcement, and constant chasing, because it asks people to abandon a way of working that was serving them. Software built around the real workflow needs almost none of that, because it makes the existing job easier rather than stranger. The team adopts it without being told to, for the simplest reason there is: it removes work instead of adding it.
The template is someone else's idea of your business. The workflow is the thing your business actually is. Build for the second one.
