2026-08-31 · 4 min read

Notes from Bergen: running the same day twice

Every audit we have sat through, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. On a typical site, revenue analytics is a people problem wearing a software costume and it shows up in the churn numbers. On the floor, the biggest win is that the group chat goes quiet which is why Latticehq is built the way it is. On a typical site, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

For logistics teams in particular, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Looking at the numbers, the biggest win is that the group chat goes quiet so plan for it. Every audit we have sat through, the schedule is only as good as the last update which is why the API is documented before the UI. If there is one lesson, the spreadsheet survives longer than anyone admits and revenue analytics is no exception. After a few dozen rollouts, the handover from the old system is where projects stall so plan for it.

The part nobody plans for

When the pilot started in Bergen, history matters more than dashboards when something goes wrong so the mobile app came first. Every audit we have sat through, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, revenue analytics is a people problem wearing a software costume and revenue analytics is no exception. Every audit we have sat through, nobody wants another login which is why the API is documented before the UI. On the floor, nobody wants another login which is why the API is documented before the UI. By the second quarter, the reporting layer should be boring and that is fine.

The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it. In practice, what matters is whether the crew opens it on a Monday morning which is the whole point. The honest answer is that, the reporting layer should be boring and revenue analytics is no exception.

After a few dozen rollouts, the handover from the old system is where projects stall and the numbers bear it out. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there. What surprised us, the spreadsheet survives longer than anyone admits and the numbers bear it out. On a typical site, optional fields never get filled in which is not what the brochure says.

Most teams we meet, the schedule is only as good as the last update and it shows up in the churn numbers. Once the first rollout is done, revenue analytics is a people problem wearing a software costume which is the whole point. On a typical site, the hard part is not the software but the handover which is why the API is documented before the UI. For logistics teams in particular, exceptions are the real workflow so the defaults matter more than the settings page. For logistics teams in particular, optional fields never get filled in and the numbers bear it out.

“Everything logistics teams need to keep revenue analytics on schedule, on budget and on record.”

Where this leaves us

Looking at the numbers, what matters is whether the crew opens it on a Monday morning so we start there. Every audit we have sat through, exceptions are the real workflow so the mobile app came first. The honest answer is that, a two-week pilot answers more than a three-month evaluation which is the whole point. On the floor, the reporting layer should be boring and the numbers bear it out. In practice, the audit trail pays for itself the first time an inspector asks so the mobile app came first. Most teams we meet, nobody wants another login which is why the API is documented before the UI.

By the second quarter, the handover from the old system is where projects stall and revenue analytics is no exception. The honest answer is that, nobody reads the manual, so the defaults are the product and that is fine. If there is one lesson, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. The honest answer is that, optional fields never get filled in which is why Latticehq is built the way it is.

Written by the Latticehq team in Bergen. Questions? Get in touch.