Your team can be busy all day and still struggle to move work forward. Before adding another application, follow one piece of work from beginning to end.
Take a customer order, a new enquiry or a recurring report. Where does it arrive? Who checks it? What gets copied? When does someone wait for an answer? These questions often reveal a more useful starting point than a list of software features.
The tool is only one part of the change
The OECD’s research on digital transformation in smaller businesses identifies barriers that extend beyond technology access, including skills, resources and organisational capacity.[1] Buying a platform does not, by itself, resolve unclear ownership or unreliable information.
Our view is that the first investment should be understanding the work. Technology becomes easier to evaluate when you can explain the problem it needs to solve.
Follow the handovers
Ask the people doing the work to walk through a recent example. Include the awkward cases, not only the ideal process. A workflow that looks simple on a diagram may depend on someone remembering a customer’s special requirements or checking a second spreadsheet.
- Where is the same information entered again?
- Which steps wait for a person to notice an email?
- What information is routinely missing?
- Who deals with exceptions, and how do they find out?
For an illustrative wholesale business, an order might move from email to a spreadsheet, then to inventory and accounts. Each tool may work well individually. The friction sits between them.
Remove. Simplify. Connect. Then automate.
We use this sequence as a practical starting point, not a universal formula.
- Remove steps that no longer serve a purpose, such as maintaining a report nobody uses.
- Simplify the rules, ownership and information needed to complete the work.
- Connect systems where supported interfaces can remove repeated entry.
- Build or automate the remaining work where the expected value justifies it.
Sometimes a custom application is appropriate. Sometimes the existing platform already has the feature you need. The decision should follow the process, its constraints and the cost of maintaining the solution.
Measure the whole job
Record a baseline before changing anything. Look at active handling time, waiting time, rework and exceptions. A faster step can still create more checking elsewhere.
As a simple illustration, reducing a task from 12 minutes to seven across 60 weekly cases creates five hours of gross capacity. That is not automatically five hours of cost savings. You still need to account for review, maintenance and how the released time will be used.
A useful pilot has an owner, a defined scope and a review date. Ask whether the team uses it, whether errors have moved elsewhere and whether the benefit remains after support effort.
How we would approach it with you
We would start with one process that matters to your business, map it with your team and agree on the outcome. From there, we can help with process planning, integrations, custom applications or automation. The aim is a simpler way of working that your team can sustain.
Research & further reading
1. OECD, The Digital Transformation of SMEs (2021). The workflow and time-saving example above are illustrative, not client results.