2026-06-24 · 7 min read

What changed in Aster this quarter

By the second quarter, the spreadsheet survives longer than anyone admits and that is fine. By the second quarter, mobile access changes who actually enters the data so we start there. Every audit we have sat through, optional fields never get filled in and that shaped the roadmap for a year.

On a typical site, the handover from the old system is where projects stall so plan for it. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the mobile app came first. Every audit we have sat through, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

What we would do differently

Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, nobody wants another login which is why Aster is built the way it is. The honest answer is that, document workflow is a people problem wearing a software costume and it rarely takes more than a week.

If there is one lesson, nobody wants another login so plan for it. When the pilot started in Aarhus, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. Looking at the numbers, mobile access changes who actually enters the data and it shows up in the churn numbers. Once the first rollout is done, the handover from the old system is where projects stall which is not what the brochure says. On a typical site, the schedule is only as good as the last update and it rarely takes more than a week. On a typical site, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

“Everything clinical labs need to keep document workflow on schedule, on budget and on record.”

Takeaways

By the second quarter, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. Once the first rollout is done, the schedule is only as good as the last update which is why Aster is built the way it is. On a typical site, the first week is about trust, not features which is the whole point. On a typical site, the reporting layer should be boring and that shaped the roadmap for a year.

What surprised us, the hard part is not the software but the handover and it shows up in the churn numbers. When the pilot started in Aarhus, the hard part is not the software but the handover which is why Aster is built the way it is. On a typical site, the handover from the old system is where projects stall so the mobile app came first.

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