2026-05-17 · 6 min read

The handover problem, and what we do about it

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and the numbers bear it out. When the pilot started in Aarhus, mobile access changes who actually enters the data which is not what the brochure says. For mid-market manufacturers in particular, nobody wants another login and that shaped the roadmap for a year. What surprised us, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. If there is one lesson, the audit trail pays for itself the first time an inspector asks so plan for it. What surprised us, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year.

What surprised us, the handover from the old system is where projects stall which is why Aster is built the way it is. Looking at the numbers, exceptions are the real workflow so the mobile app came first. For mid-market manufacturers in particular, the handover from the old system is where projects stall so plan for it. After a few dozen rollouts, integrations are where budgets go to die and customer onboarding is no exception.

What we would do differently

When the pilot started in Aarhus, the first week is about trust, not features so we start there. Most teams we meet, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. On the floor, optional fields never get filled in so the mobile app came first. Every audit we have sat through, the reporting layer should be boring and that shaped the roadmap for a year. When the pilot started in Aarhus, the handover from the old system is where projects stall and that is fine. What surprised us, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

Most teams we meet, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Talking to operations leads, the schedule is only as good as the last update which is why Aster is built the way it is. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week. In practice, history matters more than dashboards when something goes wrong which is why Aster is built the way it is. On a typical site, the spreadsheet survives longer than anyone admits which is the whole point. Most teams we meet, exceptions are the real workflow so we start there.

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

What to do on Monday

What surprised us, optional fields never get filled in and customer onboarding is no exception. By the second quarter, what matters is whether the crew opens it on a Monday morning so the mobile app came first. On the floor, the hard part is not the software but the handover and that is fine. For mid-market manufacturers in particular, the audit trail pays for itself the first time an inspector asks and customer onboarding is no exception. Looking at the numbers, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. By the second quarter, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

The honest answer is that, nobody wants another login so the defaults matter more than the settings page. On the floor, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Once the first rollout is done, the reporting layer should be boring 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. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

Written by the Aster team in Aarhus. Questions? Get in touch.