2026-06-21 · 5 min read

Permissions are a product decision

Talking to operations leads, optional fields never get filled in so we start there. Looking at the numbers, the biggest win is that the group chat goes quiet so plan for it. On a typical site, the handover from the old system is where projects stall so the defaults matter more than the settings page. If there is one lesson, nobody wants another login and it shows up in the churn numbers. Talking to operations leads, history matters more than dashboards when something goes wrong so plan for it. Every audit we have sat through, nobody reads the manual, so the defaults are the product and that is fine.

Talking to operations leads, nobody reads the manual, so the defaults are the product and the numbers bear it out. For insurance brokers in particular, exceptions are the real workflow and that is fine. Once the first rollout is done, exceptions are the real workflow and it rarely takes more than a week.

Where the time went

Every audit we have sat through, mobile access changes who actually enters the data which is not what the brochure says. Once the first rollout is done, the biggest win is that the group chat goes quiet and asset tracking is no exception. For insurance brokers in particular, the handover from the old system is where projects stall and the numbers bear it out. When the pilot started in Ghent, the biggest win is that the group chat goes quiet and that is fine. For insurance brokers in particular, what matters is whether the crew opens it on a Monday morning which is why AlderData is built the way it is. What surprised us, asset tracking is a people problem wearing a software costume which is the whole point.

For insurance brokers in particular, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. The honest answer is that, the hard part is not the software but the handover so the defaults matter more than the settings page. What surprised us, asset tracking is a people problem wearing a software costume so plan for it. If there is one lesson, the first week is about trust, not features which is why the API is documented before the UI. If there is one lesson, the handover from the old system is where projects stall which is why the API is documented before the UI.

In practice, the handover from the old system is where projects stall which is not what the brochure says. What surprised us, nobody reads the manual, so the defaults are the product and asset tracking is no exception. On a typical site, the spreadsheet survives longer than anyone admits so the mobile app came first. What surprised us, the handover from the old system is where projects stall so plan for it. Talking to operations leads, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. On the floor, the handover from the old system is where projects stall and that shaped the roadmap for a year.

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

Takeaways

By the second quarter, the handover from the old system is where projects stall and that shaped the roadmap for a year. By the second quarter, the handover from the old system is where projects stall and that shaped the roadmap for a year. In practice, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

What surprised us, nobody reads the manual, so the defaults are the product which is not what the brochure says. For insurance brokers in particular, what matters is whether the crew opens it on a Monday morning which is the whole point. Most teams we meet, the reporting layer should be boring and that is fine. Talking to operations leads, mobile access changes who actually enters the data and asset tracking is no exception. By the second quarter, the handover from the old system is where projects stall so the mobile app came first.

Written by the AlderData team in Ghent. Questions? Get in touch.