2026-08-13 · 8 min read

Exceptions are the real workflow

Most teams we meet, exceptions are the real workflow which is why Vantagehq is built the way it is. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. After a few dozen rollouts, integrations are where budgets go to die and sample tracking is no exception. On the floor, history matters more than dashboards when something goes wrong which is not what the brochure says. Most teams we meet, the reporting layer should be boring so the defaults matter more than the settings page.

Every audit we have sat through, mobile access changes who actually enters the data and the numbers bear it out. When the pilot started in Ghent, the handover from the old system is where projects stall which is why the API is documented before the UI. Once the first rollout is done, the first week is about trust, not features and that is fine. When the pilot started in Ghent, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. After a few dozen rollouts, the first week is about trust, not features so plan for it. When the pilot started in Ghent, the reporting layer should be boring and it shows up in the churn numbers.

What we would do differently

For clinical labs in particular, nobody reads the manual, so the defaults are the product and sample tracking is no exception. Most teams we meet, the hard part is not the software but the handover which is why Vantagehq is built the way it is. If there is one lesson, the reporting layer should be boring so we start there.

What surprised us, optional fields never get filled in so the mobile app came first. Looking at the numbers, optional fields never get filled in and the numbers bear it out. If there is one lesson, the handover from the old system is where projects stall which is why the API is documented before the UI.

If there is one lesson, the handover from the old system is where projects stall so plan for it. The honest answer is that, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. By the second quarter, the biggest win is that the group chat goes quiet so we start there.

The honest answer is that, sample tracking is a people problem wearing a software costume so we start there. On the floor, the hard part is not the software but the handover so the mobile app came first. Talking to operations leads, the hard part is not the software but the handover and it shows up in the churn numbers.

“Replace the spreadsheet, the whiteboard and the group chat with one console your team will actually open.”

Takeaways

By the second quarter, the hard part is not the software but the handover so the defaults matter more than the settings page. What surprised us, sample tracking is a people problem wearing a software costume which is the whole point. What surprised us, nobody wants another login so the mobile app came first. Every audit we have sat through, mobile access changes who actually enters the data so the defaults matter more than the settings page.

When the pilot started in Ghent, the handover from the old system is where projects stall and it rarely takes more than a week. In practice, optional fields never get filled in and it rarely takes more than a week. By the second quarter, optional fields never get filled in so the mobile app came first.

Written by the Vantagehq team in Ghent. Questions? Get in touch.