Article 01
What errors actually cost you
The hours lost to repetitive admin are easy enough to count. The errors it produces are not, and that is exactly why they are worth thinking about.
Insights
Longer pieces on the same patterns the audit looks for: where the hours go, where the errors come from, and why projects go wrong before anyone starts building.
Article 02
The request already contains an answer
People don't bring problems, they bring solutions. That's generous of them, and it's on the developer, not the client, when the solution ships without the problem ever being asked about.
Article 03
Why asking for one thing at a time costs more
You have a budget and no appetite for a big project, so you ask for the first piece and add the rest later. That is a sensible instinct, and it is also how software quietly ends up costing more than it needed to.
Recognise one of these?
Tell me which task takes the most time, and we'll see whether it's worth fixing.
Book a free 20-minute call
I'm Barnabas Kecskes, based in Telford. I wrote these from projects I've worked on. See what I've built.