2026-07-09 · 6 min read

Notes from Aarhus: running the same day twice

The honest answer is that, nobody reads the manual, so the defaults are the product and that is fine. Talking to operations leads, integrations are where budgets go to die which is the whole point. On the floor, mobile access changes who actually enters the data and that shaped the roadmap for a year. By the second quarter, nobody wants another login which is not what the brochure says. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. The honest answer is that, the hard part is not the software but the handover which is not what the brochure says.

Most teams we meet, the first week is about trust, not features which is the whole point. For clinical labs in particular, a two-week pilot answers more than a three-month evaluation and document workflow is no exception. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. On a typical site, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

What actually happened

Looking at the numbers, nobody wants another login so plan for it. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why Aster is built the way it is. Talking to operations leads, the first week is about trust, not features which is why Aster is built the way it is.

On the floor, what matters is whether the crew opens it on a Monday morning and document workflow is no exception. In practice, the spreadsheet survives longer than anyone admits which is not what the brochure says. Every audit we have sat through, document workflow is a people problem wearing a software costume which is why Aster is built the way it is. After a few dozen rollouts, integrations are where budgets go to die and it shows up in the churn numbers. Once the first rollout is done, the hard part is not the software but the handover and it shows up in the churn numbers.

“Aster gives clinical labs a single, dependable view of document workflow - from first request to signed-off report.”

Where this leaves us

Every audit we have sat through, exceptions are the real workflow which is why the API is documented before the UI. What surprised us, the hard part is not the software but the handover which is not what the brochure says. Once the first rollout is done, the biggest win is that the group chat goes quiet so we start there. Every audit we have sat through, the reporting layer should be boring and that shaped the roadmap for a year. The honest answer is that, document workflow is a people problem wearing a software costume which is the whole point. Once the first rollout is done, the hard part is not the software but the handover and that is fine.

The honest answer is that, optional fields never get filled in and it shows up in the churn numbers. When the pilot started in Aarhus, integrations are where budgets go to die so the defaults matter more than the settings page. After a few dozen rollouts, optional fields never get filled in and it rarely takes more than a week. For clinical labs in particular, nobody reads the manual, so the defaults are the product which is not what the brochure says.

What surprised us, nobody reads the manual, so the defaults are the product and that is fine. Once the first rollout is done, history matters more than dashboards when something goes wrong so plan for it. For clinical labs in particular, exceptions are the real workflow which is why the API is documented before the UI.

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