2026-09-03 · 6 min read

Notes from Wroclaw: running the same day twice

On a typical site, nobody wants another login which is the whole point. On the floor, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. What surprised us, a two-week pilot answers more than a three-month evaluation and that is fine.

By the second quarter, history matters more than dashboards when something goes wrong and fleet telemetry is no exception. Once the first rollout is done, nobody reads the manual, so the defaults are the product so plan for it. By the second quarter, the reporting layer should be boring and that is fine.

What actually happened

What surprised us, fleet telemetry is a people problem wearing a software costume and that shaped the roadmap for a year. In practice, nobody reads the manual, so the defaults are the product which is the whole point. On the floor, exceptions are the real workflow which is why the API is documented before the UI. When the pilot started in Wroclaw, what matters is whether the crew opens it on a Monday morning so the mobile app came first. Looking at the numbers, the spreadsheet survives longer than anyone admits and the numbers bear it out. Looking at the numbers, exceptions are the real workflow and that shaped the roadmap for a year.

On the floor, exceptions are the real workflow and fleet telemetry is no exception. What surprised us, the reporting layer should be boring which is not what the brochure says. Once the first rollout is done, the schedule is only as good as the last update so we start there. Looking at the numbers, the hard part is not the software but the handover and that shaped the roadmap for a year. When the pilot started in Wroclaw, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page.

The honest answer is that, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. By the second quarter, nobody reads the manual, so the defaults are the product so we start there. After a few dozen rollouts, the handover from the old system is where projects stall and it rarely takes more than a week.

Talking to operations leads, optional fields never get filled in and fleet telemetry is no exception. In practice, the schedule is only as good as the last update and that is fine. Once the first rollout is done, the reporting layer should be boring which is why Basalt Forge is built the way it is.

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

What to do on Monday

On the floor, fleet telemetry is a people problem wearing a software costume and the numbers bear it out. When the pilot started in Wroclaw, nobody wants another login and the numbers bear it out. For property managers in particular, nobody reads the manual, so the defaults are the product and fleet telemetry is no exception. Once the first rollout is done, the handover from the old system is where projects stall and that is fine. On the floor, a two-week pilot answers more than a three-month evaluation which is why Basalt Forge is built the way it is.

Looking at the numbers, history matters more than dashboards when something goes wrong and that is fine. Most teams we meet, history matters more than dashboards when something goes wrong which is why Basalt Forge is built the way it is. Every audit we have sat through, exceptions are the real workflow which is the whole point.

When the pilot started in Wroclaw, the first week is about trust, not features so the defaults matter more than the settings page. The honest answer is that, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Every audit we have sat through, optional fields never get filled in which is why Basalt Forge is built the way it is. For property managers in particular, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

Written by the Basalt Forge team in Wroclaw. Questions? Get in touch.