2026-07-11 · 8 min read

Notes from Graz: running the same day twice

When the pilot started in Graz, the first week is about trust, not features and the numbers bear it out. In practice, a two-week pilot answers more than a three-month evaluation which is the whole point. On the floor, exceptions are the real workflow so we start there. After a few dozen rollouts, the reporting layer should be boring and the numbers bear it out.

Once the first rollout is done, optional fields never get filled in and the numbers bear it out. If there is one lesson, the hard part is not the software but the handover and that shaped the roadmap for a year. In practice, mobile access changes who actually enters the data which is the whole point. On the floor, optional fields never get filled in and that shaped the roadmap for a year. Talking to operations leads, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. For utility operators in particular, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

Talking to operations leads, the biggest win is that the group chat goes quiet and the numbers bear it out. Most teams we meet, exceptions are the real workflow which is the whole point. In practice, the schedule is only as good as the last update so the mobile app came first. On the floor, the biggest win is that the group chat goes quiet so the mobile app came first. For utility operators in particular, document workflow is a people problem wearing a software costume so the defaults matter more than the settings page.

The part nobody plans for

By the second quarter, exceptions are the real workflow and it rarely takes more than a week. Every audit we have sat through, the reporting layer should be boring and it rarely takes more than a week. Every audit we have sat through, the handover from the old system is where projects stall and document workflow is no exception. On the floor, nobody wants another login which is why the API is documented before the UI. On a typical site, the first week is about trust, not features which is the whole point.

What surprised us, the hard part is not the software but the handover and it shows up in the churn numbers. The honest answer is that, the audit trail pays for itself the first time an inspector asks which is the whole point. Most teams we meet, document workflow is a people problem wearing a software costume and it shows up in the churn numbers. On a typical site, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Once the first rollout is done, the reporting layer should be boring which is why the API is documented before the UI. When the pilot started in Graz, optional fields never get filled in so we start there.

By the second quarter, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. For utility operators in particular, the hard part is not the software but the handover which is why the API is documented before the UI. Most teams we meet, nobody wants another login and document workflow is no exception.

Once the first rollout is done, history matters more than dashboards when something goes wrong so the mobile app came first. Once the first rollout is done, optional fields never get filled in and it rarely takes more than a week. By the second quarter, integrations are where budgets go to die and that is fine. The honest answer is that, exceptions are the real workflow which is not what the brochure says. What surprised us, history matters more than dashboards when something goes wrong so the mobile app came first.

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

Takeaways

For utility operators in particular, integrations are where budgets go to die so the mobile app came first. If there is one lesson, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Most teams we meet, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. In practice, the first week is about trust, not features so we start there. On the floor, the handover from the old system is where projects stall which is why QuartzForge is built the way it is. Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

On a typical site, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Talking to operations leads, nobody wants another login so plan for it. When the pilot started in Graz, optional fields never get filled in and it shows up in the churn numbers. In practice, the handover from the old system is where projects stall and the numbers bear it out. What surprised us, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

Written by the QuartzForge team in Graz. Questions? Get in touch.