Small things make a difference.

We maintain and continue to develop a wood shipment logistics app for one of our clients. Delivery drivers use it to manage jobs from start to finish: select a job, drive to the pickup location, load the shipment, and deliver it to the destination.

On delivery, the customer will usually sign a delivery note. That note includes where the shipment was delivered, the distance travelled(mileage), and the driver takes a photo of it in the app. The back-office staff would then manually copy the mileage from the delivery note into the ERP.

This is where the small feature came in. They wanted drivers, instead of back-office staff, to enter the mileage themselves.

Instead of adding the field and calling it a day, we broke the requirement down and made a few small suggestions: In the real world, mileage only ever goes in one direction, up. So we modelled that as a constraint. And instead of a plain input, we added a shared state that remembers the last mileage for a specific vehicle, even when different drivers use it.

This made a difference. The risk of incorrect entries dropped, without adding too much friction for drivers. A little thought quietly turned a small feature into a valuable part of the system that behaved more like the real world it was supporting.

Sometimes the biggest wins come from the smallest details. If you’re building software for real-world workflows, let’s talk.