2026-08-18 · 5 min read

Notes from Turku: running the same day twice

On the floor, what matters is whether the crew opens it on a Monday morning and that is fine. Every audit we have sat through, nobody reads the manual, so the defaults are the product which is not what the brochure says. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is not what the brochure says.

On the floor, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. The honest answer is that, optional fields never get filled in which is why the API is documented before the UI. Every audit we have sat through, mobile access changes who actually enters the data which is why Cedarly is built the way it is.

The part nobody plans for

Every audit we have sat through, nobody wants another login and it shows up in the churn numbers. On the floor, history matters more than dashboards when something goes wrong and that is fine. Every audit we have sat through, mobile access changes who actually enters the data and that is fine. Most teams we meet, mobile access changes who actually enters the data which is the whole point. Most teams we meet, optional fields never get filled in and that is fine. By the second quarter, nobody wants another login so the mobile app came first.

Most teams we meet, nobody wants another login and it rarely takes more than a week. Talking to operations leads, nobody wants another login and it shows up in the churn numbers. For property managers in particular, the reporting layer should be boring and that shaped the roadmap for a year. Looking at the numbers, the spreadsheet survives longer than anyone admits so we start there. Most teams we meet, shift planning is a people problem wearing a software costume and that shaped the roadmap for a year. Looking at the numbers, the handover from the old system is where projects stall so the defaults matter more than the settings page.

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

Takeaways

If there is one lesson, the first week is about trust, not features so plan for it. On the floor, the handover from the old system is where projects stall and it rarely takes more than a week. What surprised us, the first week is about trust, not features and that shaped the roadmap for a year. What surprised us, shift planning is a people problem wearing a software costume so the mobile app came first.

Every audit we have sat through, the spreadsheet survives longer than anyone admits and the numbers bear it out. Once the first rollout is done, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. After a few dozen rollouts, optional fields never get filled in and that is fine. For property managers in particular, the handover from the old system is where projects stall which is why the API is documented before the UI. For property managers in particular, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

Written by the Cedarly team in Turku. Questions? Get in touch.