2026-07-03 · 7 min read

Notes from Graz: running the same day twice

Most teams we meet, 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, optional fields never get filled in and it rarely takes more than a week. Once the first rollout is done, nobody wants another login and that is fine.

Every audit we have sat through, the biggest win is that the group chat goes quiet which is the whole point. Most teams we meet, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. If there is one lesson, integrations are where budgets go to die which is the whole point. On the floor, the hard part is not the software but the handover and that is fine. What surprised us, the hard part is not the software but the handover and shift planning is no exception. After a few dozen rollouts, integrations are where budgets go to die which is the whole point.

What we would do differently

Looking at the numbers, the reporting layer should be boring which is not what the brochure says. What surprised us, nobody wants another login and the numbers bear it out. On the floor, history matters more than dashboards when something goes wrong which is why Prism is built the way it is. Most teams we meet, the biggest win is that the group chat goes quiet which is why Prism is built the way it is.

If there is one lesson, the audit trail pays for itself the first time an inspector asks so we start there. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. What surprised us, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Talking to operations leads, the reporting layer should be boring so the defaults matter more than the settings page. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is not what the brochure says. Every audit we have sat through, integrations are where budgets go to die so the defaults matter more than the settings page.

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

Takeaways

Talking to operations leads, the schedule is only as good as the last update so the defaults matter more than the settings page. When the pilot started in Graz, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. On the floor, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI.

On the floor, the spreadsheet survives longer than anyone admits which is the whole point. If there is one lesson, shift planning is a people problem wearing a software costume and it shows up in the churn numbers. On a typical site, history matters more than dashboards when something goes wrong which is the whole point. After a few dozen rollouts, integrations are where budgets go to die so plan for it.

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