2026-08-23 · 8 min read

From pilot to plant: a 22-week timeline

The honest answer is that, mobile access changes who actually enters the data which is why the API is documented before the UI. Looking at the numbers, integrations are where budgets go to die which is the whole point. Looking at the numbers, optional fields never get filled in which is the whole point. On the floor, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. If there is one lesson, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. In practice, field service scheduling is a people problem wearing a software costume which is why Ember is built the way it is.

If there is one lesson, optional fields never get filled in and it rarely takes more than a week. On a typical site, exceptions are the real workflow and that shaped the roadmap for a year. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. On a typical site, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. Every audit we have sat through, exceptions are the real workflow so the defaults matter more than the settings page.

After a few dozen rollouts, mobile access changes who actually enters the data which is not what the brochure says. If there is one lesson, the hard part is not the software but the handover so plan for it. What surprised us, mobile access changes who actually enters the data so we start there. For food producers in particular, optional fields never get filled in which is not what the brochure says. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is the whole point. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is why Ember is built the way it is.

What we would do differently

Talking to operations leads, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. What surprised us, the spreadsheet survives longer than anyone admits which is not what the brochure says. The honest answer is that, field service scheduling is a people problem wearing a software costume and field service scheduling is no exception. On the floor, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers. On the floor, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. What surprised us, field service scheduling is a people problem wearing a software costume and that is fine.

Every audit we have sat through, optional fields never get filled in and that shaped the roadmap for a year. Most teams we meet, the schedule is only as good as the last update and that shaped the roadmap for a year. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so we start there. When the pilot started in Aarhus, history matters more than dashboards when something goes wrong and the numbers bear it out. Most teams we meet, optional fields never get filled in and it shows up in the churn numbers.

Looking at the numbers, field service scheduling is a people problem wearing a software costume which is not what the brochure says. Most teams we meet, history matters more than dashboards when something goes wrong which is not what the brochure says. What surprised us, mobile access changes who actually enters the data which is why Ember is built the way it is. On the floor, the first week is about trust, not features and the numbers bear it out.

When the pilot started in Aarhus, mobile access changes who actually enters the data so we start there. Talking to operations leads, history matters more than dashboards when something goes wrong which is the whole point. Once the first rollout is done, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. In practice, nobody reads the manual, so the defaults are the product and field service scheduling is no exception. When the pilot started in Aarhus, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

“Everything food producers need to keep field service scheduling on schedule, on budget and on record.”

Where this leaves us

What surprised us, optional fields never get filled in which is the whole point. On a typical site, field service scheduling is a people problem wearing a software costume which is not what the brochure says. Once the first rollout is done, the hard part is not the software but the handover which is why the API is documented before the UI. In practice, the spreadsheet survives longer than anyone admits which is the whole point.

When the pilot started in Aarhus, the handover from the old system is where projects stall and the numbers bear it out. If there is one lesson, the hard part is not the software but the handover and it shows up in the churn numbers. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. For food producers in particular, exceptions are the real workflow which is not what the brochure says.

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