The story usually goes like this. Reports take too long, nobody knows where the latest document is, and everyone follows a slightly different process. Somebody suggests a system. A system is bought. Six months later the reports still take too long, the documents are now in two places, and the spreadsheet everyone actually uses has quietly come back.
The system was not the problem. The process was, and the system faithfully automated it.
Software copies the process it finds
A platform does exactly what it is configured to do. If responsibilities are unclear, it will not clarify them. If two people capture the same information, it will store it twice. If nobody knows who approves what, the approval step becomes a button nobody presses. Technology makes a good process faster and a broken one more expensive.
Five questions before you buy anything
- What are people actually trying to do? Not the department’s mission, the task. Capture an enquiry, approve a payment, produce a monthly report.
- Where does the process fail today? Handovers, duplicate capture, waiting for a decision, information that lives in someone’s head.
- What information is genuinely needed? Most forms ask for more than anyone uses. Fewer fields, kept accurate, beat many fields half filled.
- Can the tools you already pay for do the job? Microsoft 365, a shared folder structure, a form and a well-built spreadsheet solve more than people expect.
- What will people realistically use? A system that needs a specialist to update it will not be updated.
Process first, then the system
Map how the work moves through the organisation as it actually happens: who does what, in what order, with what information, and where the delays are. Remove the unnecessary steps. Write the improved process down in plain language so two people follow it the same way. Only then decide whether a tool is needed, and which one.
Sometimes you need a better system. Sometimes you need to use the one you have properly. Sometimes a spreadsheet is still enough. The job is to know the difference.
Adoption is a people job
A good system still fails when roles are undefined, training is thin or support disappears after go-live. Budget time for the people side: a walkthrough with the team, a short written guide, and someone available for questions in the first weeks. Implementation does not end when the login details are sent.
Where to start
Pick one process that hurts. Map it on one page. Fix the handovers and the duplicate capture. Then ask whether a tool would help. If it would, choose the simplest one that fits, and plan the adoption before the purchase.
This is the work Naleli Innovations does under Digital Operations & Solutions: process first, system second, and support until people can use it to do the work. If your systems or spreadsheets are getting harder to manage, tell us what is happening.