2026-07-14 · 6 min read

Notes from Wroclaw: running the same day twice

Every audit we have sat through, mobile access changes who actually enters the data which is why Harborio is built the way it is. On a typical site, integrations are where budgets go to die so plan for it. In practice, a two-week pilot answers more than a three-month evaluation and sample tracking is no exception.

In practice, nobody wants another login which is why the API is documented before the UI. On a typical site, the audit trail pays for itself the first time an inspector asks and that is fine. Most teams we meet, the audit trail pays for itself the first time an inspector asks and sample tracking is no exception. If there is one lesson, nobody wants another login so the defaults matter more than the settings page. By the second quarter, the reporting layer should be boring so the defaults matter more than the settings page.

What we would do differently

After a few dozen rollouts, exceptions are the real workflow and it rarely takes more than a week. By the second quarter, the biggest win is that the group chat goes quiet and sample tracking is no exception. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

After a few dozen rollouts, integrations are where budgets go to die so the defaults matter more than the settings page. By the second quarter, the handover from the old system is where projects stall which is why Harborio is built the way it is. After a few dozen rollouts, integrations are where budgets go to die so the mobile app came first. Looking at the numbers, nobody reads the manual, so the defaults are the product and that is fine. On the floor, the spreadsheet survives longer than anyone admits and sample tracking is no exception.

By the second quarter, integrations are where budgets go to die and sample tracking is no exception. When the pilot started in Wroclaw, a two-week pilot answers more than a three-month evaluation so plan for it. What surprised us, mobile access changes who actually enters the data which is the whole point. What surprised us, exceptions are the real workflow and it rarely takes more than a week. When the pilot started in Wroclaw, the spreadsheet survives longer than anyone admits which is not what the brochure says.

Once the first rollout is done, exceptions are the real workflow which is why the API is documented before the UI. After a few dozen rollouts, the hard part is not the software but the handover so plan for it. On the floor, nobody reads the manual, so the defaults are the product which is not what the brochure says. What surprised us, optional fields never get filled in which is the whole point. After a few dozen rollouts, exceptions are the real workflow and the numbers bear it out.

“Plan, dispatch and reconcile in one place. Harborio connects to the systems you already run and stays out of the way.”

What to do on Monday

Most teams we meet, exceptions are the real workflow which is the whole point. Looking at the numbers, the handover from the old system is where projects stall and it rarely takes more than a week. The honest answer is that, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. When the pilot started in Wroclaw, the handover from the old system is where projects stall and sample tracking is no exception. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

Talking to operations leads, the hard part is not the software but the handover which is the whole point. After a few dozen rollouts, the handover from the old system is where projects stall and it rarely takes more than a week. When the pilot started in Wroclaw, integrations are where budgets go to die and it shows up in the churn numbers.

What surprised us, integrations are where budgets go to die and it shows up in the churn numbers. Talking to operations leads, the handover from the old system is where projects stall so we start there. In practice, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. Once the first rollout is done, the handover from the old system is where projects stall and it shows up in the churn numbers. Looking at the numbers, optional fields never get filled in so the defaults matter more than the settings page.

Written by the Harborio team in Wroclaw. Questions? Get in touch.