2026-09-15 · 8 min read

Notes from Turku: running the same day twice

If there is one lesson, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. For clinical labs in particular, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and that is fine. For clinical labs in particular, the reporting layer should be boring and that is fine. For clinical labs in particular, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

Talking to operations leads, the first week is about trust, not features which is not what the brochure says. What surprised us, the biggest win is that the group chat goes quiet and it rarely takes more than a week. In practice, the first week is about trust, not features so we start there.

After a few dozen rollouts, optional fields never get filled in and document workflow is no exception. Looking at the numbers, mobile access changes who actually enters the data so plan for it. Once the first rollout is done, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. For clinical labs in particular, integrations are where budgets go to die and document workflow is no exception.

What we would do differently

After a few dozen rollouts, the handover from the old system is where projects stall which is the whole point. What surprised us, exceptions are the real workflow and document workflow is no exception. When the pilot started in Turku, nobody reads the manual, so the defaults are the product and the numbers bear it out. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there. Most teams we meet, what matters is whether the crew opens it on a Monday morning so the mobile app came first. By the second quarter, the biggest win is that the group chat goes quiet and that is fine.

The honest answer is that, the spreadsheet survives longer than anyone admits which is the whole point. In practice, mobile access changes who actually enters the data so the defaults matter more than the settings page. Talking to operations leads, the hard part is not the software but the handover and that is fine. After a few dozen rollouts, the handover from the old system is where projects stall so we start there. Every audit we have sat through, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. By the second quarter, the hard part is not the software but the handover which is why Almanachq is built the way it is.

For clinical labs in particular, nobody wants another login which is not what the brochure says. In practice, the first week is about trust, not features so plan for it. Once the first rollout is done, optional fields never get filled in which is the whole point.

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

What to do on Monday

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is the whole point. Every audit we have sat through, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. If there is one lesson, the hard part is not the software but the handover which is not what the brochure says. When the pilot started in Turku, document workflow is a people problem wearing a software costume so plan for it. Talking to operations leads, document workflow is a people problem wearing a software costume so plan for it. On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out.

By the second quarter, optional fields never get filled in and it shows up in the churn numbers. On the floor, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. On the floor, nobody wants another login which is not what the brochure says.

Once the first rollout is done, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. After a few dozen rollouts, the first week is about trust, not features and it shows up in the churn numbers. In practice, the hard part is not the software but the handover and it rarely takes more than a week. What surprised us, the schedule is only as good as the last update which is why the API is documented before the UI. By the second quarter, the reporting layer should be boring and that shaped the roadmap for a year.

Written by the Almanachq team in Turku. Questions? Get in touch.