The task that stopped being a task
Embedded software company with in-house hardware
Embedded software
The problem
Handling direct debits took the administration team around five hours, twice a month. Several spreadsheets had to be cross-checked by hand and the identifiers for every point of sale corrected one by one, because the bank matches each debit on an exact combination of tax ID, bank account and point of sale: a single customer changing accounts or ownership was enough to break the match.
With a hundred customers that was an afternoon. With more than two thousand it was some 120 hours a year — three full working weeks, every year, spent reconciling spreadsheets.
What was built
A web application where the administrator uploads the spreadsheets and, two minutes later, receives by email the files ready to load into the bank’s system and process the collection.
What made the replacement possible was not the coding: it was measuring first what the task actually cost. The problem was never the administrator or the spreadsheet — it was a procedure designed for a company size that had ceased to exist.
The details that make the difference
A workaround does not fail the day it is made
It fails the day the business grows, and by then nobody remembers it was a workaround. The company had gone from serving a hundred customers to over two thousand: nothing had broken, it is just that nobody looked at the processes again.
Tracing where the request came from
A good share of incoming requirements were not new needs: they were the consequence of workarounds stacked up years earlier. Tracing that origin is what almost never gets done, and it is what stops you from automating the problem instead of solving it.
How it was verified
The task ceased to exist. In time, some 120 hours a year freed up; in money, a large share of one person’s salary devoted to a single task that added nothing to the business.
- Automatización de procesos
- Aplicación web
- ISO 9001:2015
- Testing QA
The hard question first: did the business make money last month, or does it look like it did?
If the answer is uncomfortable, there is a fifteen-minute conversation worth having. The system is shown running on a demonstration business, and the way the work happens today gets mapped.