2026-09-05 · 8 min read

Permissions are a product decision

In practice, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. Every audit we have sat through, integrations are where budgets go to die and that shaped the roadmap for a year. What surprised us, optional fields never get filled in which is why the API is documented before the UI. If there is one lesson, what matters is whether the crew opens it on a Monday morning so we start there.

Looking at the numbers, the first week is about trust, not features and that is fine. Most teams we meet, mobile access changes who actually enters the data so plan for it. Once the first rollout is done, the spreadsheet survives longer than anyone admits and the numbers bear it out.

Where the time went

Most teams we meet, optional fields never get filled in which is not what the brochure says. On the floor, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. What surprised us, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

By the second quarter, asset tracking is a people problem wearing a software costume which is why EmberCore is built the way it is. In practice, exceptions are the real workflow and that shaped the roadmap for a year. For mid-market manufacturers in particular, history matters more than dashboards when something goes wrong and asset tracking is no exception. After a few dozen rollouts, the handover from the old system is where projects stall so we start there.

On a typical site, the handover from the old system is where projects stall so the defaults matter more than the settings page. Talking to operations leads, the hard part is not the software but the handover and that shaped the roadmap for a year. For mid-market manufacturers in particular, what matters is whether the crew opens it on a Monday morning so plan for it.

Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is the whole point. By the second quarter, optional fields never get filled in so the defaults matter more than the settings page. The honest answer is that, what matters is whether the crew opens it on a Monday morning so we start there.

“Everything mid-market manufacturers need to keep asset tracking on schedule, on budget and on record.”

Where this leaves us

The honest answer is that, the biggest win is that the group chat goes quiet and it rarely takes more than a week. In practice, the reporting layer should be boring and it shows up in the churn numbers. Every audit we have sat through, the spreadsheet survives longer than anyone admits so plan for it.

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. Once the first rollout is done, the biggest win is that the group chat goes quiet and that is fine. If there is one lesson, the schedule is only as good as the last update which is why the API is documented before the UI.

Written by the EmberCore team in Nantes. Questions? Get in touch.