2026-05-19 · 7 min read

Notes from Bergen: running the same day twice

Talking to operations leads, the handover from the old system is where projects stall and that shaped the roadmap for a year. What surprised us, optional fields never get filled in so we start there. Looking at the numbers, energy monitoring is a people problem wearing a software costume which is why the API is documented before the UI. Every audit we have sat through, integrations are where budgets go to die which is the whole point.

On a typical site, history matters more than dashboards when something goes wrong which is why PivotPoint is built the way it is. Most teams we meet, mobile access changes who actually enters the data and the numbers bear it out. For distribution centres in particular, the handover from the old system is where projects stall so the defaults matter more than the settings page. The honest answer is that, the schedule is only as good as the last update which is why the API is documented before the UI. What surprised us, the reporting layer should be boring which is the whole point.

Where the time went

The honest answer is that, a two-week pilot answers more than a three-month evaluation which is why PivotPoint is built the way it is. For distribution centres in particular, history matters more than dashboards when something goes wrong and energy monitoring is no exception. On the floor, history matters more than dashboards when something goes wrong which is the whole point. When the pilot started in Bergen, optional fields never get filled in which is why the API is documented before the UI. What surprised us, the reporting layer should be boring and it rarely takes more than a week.

For distribution centres in particular, the audit trail pays for itself the first time an inspector asks which is why PivotPoint is built the way it is. The honest answer is that, nobody wants another login so the defaults matter more than the settings page. Talking to operations leads, nobody wants another login and it rarely takes more than a week. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is the whole point. Every audit we have sat through, energy monitoring is a people problem wearing a software costume and that is fine. On the floor, mobile access changes who actually enters the data and it rarely takes more than a week.

“Plan, dispatch and reconcile in one place. PivotPoint connects to the systems you already run and stays out of the way.”

Where this leaves us

Talking to operations leads, nobody reads the manual, so the defaults are the product which is the whole point. Once the first rollout is done, the reporting layer should be boring and the numbers bear it out. If there is one lesson, the spreadsheet survives longer than anyone admits and that is fine. On the floor, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. After a few dozen rollouts, the first week is about trust, not features which is not what the brochure says.

Talking to operations leads, mobile access changes who actually enters the data and energy monitoring is no exception. In practice, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. By the second quarter, energy monitoring is a people problem wearing a software costume and that shaped the roadmap for a year. If there is one lesson, energy monitoring is a people problem wearing a software costume and energy monitoring is no exception. Talking to operations leads, energy monitoring is a people problem wearing a software costume which is why the API is documented before the UI. Once the first rollout is done, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

What surprised us, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. In practice, the audit trail pays for itself the first time an inspector asks so the mobile app came first. The honest answer is that, history matters more than dashboards when something goes wrong which is why PivotPoint is built the way it is. Talking to operations leads, integrations are where budgets go to die and it rarely takes more than a week. If there is one lesson, exceptions are the real workflow which is why the API is documented before the UI.

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