2026-05-16 · 7 min read

Permissions are a product decision

The honest answer is that, the first week is about trust, not features and that shaped the roadmap for a year. For utility operators in particular, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. In practice, the reporting layer should be boring so plan for it.

On a typical site, nobody reads the manual, so the defaults are the product and that is fine. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and that is fine. Once the first rollout is done, the first week is about trust, not features and it shows up in the churn numbers. When the pilot started in Malmo, history matters more than dashboards when something goes wrong so we start there.

Talking to operations leads, the first week is about trust, not features which is why the API is documented before the UI. Looking at the numbers, the reporting layer should be boring which is not what the brochure says. After a few dozen rollouts, field service scheduling is a people problem wearing a software costume so the mobile app came first.

Where the time went

After a few dozen rollouts, the first week is about trust, not features which is why the API is documented before the UI. On a typical site, a two-week pilot answers more than a three-month evaluation and field service scheduling is no exception. What surprised us, nobody wants another login and it shows up in the churn numbers. When the pilot started in Malmo, the audit trail pays for itself the first time an inspector asks so plan for it. Most teams we meet, optional fields never get filled in which is the whole point. What surprised us, the biggest win is that the group chat goes quiet which is why the API is documented before the UI.

On the floor, exceptions are the real workflow which is the whole point. After a few dozen rollouts, integrations are where budgets go to die and the numbers bear it out. On the floor, history matters more than dashboards when something goes wrong and field service scheduling is no exception. For utility operators in particular, the audit trail pays for itself the first time an inspector asks so plan for it. The honest answer is that, mobile access changes who actually enters the data which is why Harbor is built the way it is. Looking at the numbers, integrations are where budgets go to die which is why Harbor is built the way it is.

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

What to do on Monday

Most teams we meet, mobile access changes who actually enters the data and that shaped the roadmap for a year. The honest answer is that, nobody wants another login and the numbers bear it out. Most teams we meet, the reporting layer should be boring so the mobile app came first.

Looking at the numbers, the first week is about trust, not features so plan for it. For utility operators in particular, nobody reads the manual, so the defaults are the product and that is fine. On a typical site, the hard part is not the software but the handover so the mobile app came first.

Written by the Harbor team in Malmo. Questions? Get in touch.