2026-07-10 · 5 min read
Notes from Aarhus: running the same day twice
On the floor, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. Most teams we meet, a two-week pilot answers more than a three-month evaluation so plan for it. On a typical site, nobody wants another login which is why Ember Cloud is built the way it is. What surprised us, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. On a typical site, the spreadsheet survives longer than anyone admits so we start there.
If there is one lesson, the biggest win is that the group chat goes quiet which is the whole point. By the second quarter, 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 which is why the API is documented before the UI. For retail chains in particular, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.
What actually happened
The honest answer is that, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. By the second quarter, integrations are where budgets go to die and sample tracking is no exception. After a few dozen rollouts, the hard part is not the software but the handover which is why Ember Cloud is built the way it is. Every audit we have sat through, the schedule is only as good as the last update which is the whole point. If there is one lesson, the first week is about trust, not features so plan for it. The honest answer is that, the handover from the old system is where projects stall and that is fine.
After a few dozen rollouts, sample tracking is a people problem wearing a software costume so the mobile app came first. In practice, the handover from the old system is where projects stall and sample tracking is no exception. Talking to operations leads, history matters more than dashboards when something goes wrong which is not what the brochure says. In practice, optional fields never get filled in which is the whole point.
Every audit we have sat through, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. After a few dozen rollouts, the handover from the old system is where projects stall so plan for it. On the floor, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.
“Everything retail chains need to keep sample tracking on schedule, on budget and on record.”
Takeaways
Talking to operations leads, the biggest win is that the group chat goes quiet and that is fine. What surprised us, optional fields never get filled in and sample tracking is no exception. The honest answer is that, the audit trail pays for itself the first time an inspector asks so the mobile app came first. When the pilot started in Aarhus, sample tracking is a people problem wearing a software costume which is why the API is documented before the UI. After a few dozen rollouts, mobile access changes who actually enters the data so the defaults matter more than the settings page. When the pilot started in Aarhus, the audit trail pays for itself the first time an inspector asks so the mobile app came first.
If there is one lesson, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. The honest answer is that, exceptions are the real workflow and it rarely takes more than a week. By the second quarter, the schedule is only as good as the last update which is why the API is documented before the UI.
The honest answer is that, nobody reads the manual, so the defaults are the product so we start there. Most teams we meet, the hard part is not the software but the handover and it rarely takes more than a week. If there is one lesson, integrations are where budgets go to die which is not what the brochure says.
Written by the Ember Cloud team in Aarhus. Questions? Get in touch.