2026-06-22 · 4 min read

Exceptions are the real workflow

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that is fine. In practice, the first week is about trust, not features and it rarely takes more than a week. If there is one lesson, the schedule is only as good as the last update which is the whole point.

Once the first rollout is done, the biggest win is that the group chat goes quiet so plan for it. Every audit we have sat through, revenue analytics is a people problem wearing a software costume and the numbers bear it out. What surprised us, the first week is about trust, not features which is why the API is documented before the UI. On the floor, revenue analytics is a people problem wearing a software costume and it shows up in the churn numbers.

The part nobody plans for

When the pilot started in Bergen, exceptions are the real workflow which is not what the brochure says. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks so we start there. In practice, exceptions are the real workflow which is why Latticehq is built the way it is.

For logistics teams in particular, the reporting layer should be boring and revenue analytics is no exception. When the pilot started in Bergen, a two-week pilot answers more than a three-month evaluation so we start there. If there is one lesson, mobile access changes who actually enters the data and it shows up in the churn numbers. Most teams we meet, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. If there is one lesson, the handover from the old system is where projects stall and it shows up in the churn numbers. When the pilot started in Bergen, the schedule is only as good as the last update and revenue analytics is no exception.

Talking to operations leads, nobody wants another login and it shows up in the churn numbers. Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year. Most teams we meet, nobody reads the manual, so the defaults are the product which is the whole point.

Looking at the numbers, the reporting layer should be boring so we start there. On the floor, the first week is about trust, not features and that is fine. By the second quarter, integrations are where budgets go to die and revenue analytics is no exception. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. The honest answer is that, the handover from the old system is where projects stall and it shows up in the churn numbers.

“Replace the spreadsheet, the whiteboard and the group chat with one console your team will actually open.”

What to do on Monday

Most teams we meet, the hard part is not the software but the handover so the mobile app came first. When the pilot started in Bergen, mobile access changes who actually enters the data which is why the API is documented before the UI. Once the first rollout is done, revenue analytics is a people problem wearing a software costume and that is fine. Looking at the numbers, nobody wants another login which is the whole point. Every audit we have sat through, nobody wants another login and that shaped the roadmap for a year. On a typical site, mobile access changes who actually enters the data which is why the API is documented before the UI.

By the second quarter, mobile access changes who actually enters the data and revenue analytics is no exception. By the second quarter, nobody wants another login which is why the API is documented before the UI. Once the first rollout is done, history matters more than dashboards when something goes wrong and it rarely takes more than a week. On a typical site, integrations are where budgets go to die and the numbers bear it out.

On a typical site, the reporting layer should be boring and it shows up in the churn numbers. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is why Latticehq is built the way it is. On a typical site, history matters more than dashboards when something goes wrong which is not what the brochure says. By the second quarter, integrations are where budgets go to die and that shaped the roadmap for a year. On the floor, the spreadsheet survives longer than anyone admits and that is fine. The honest answer is that, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

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