2026-05-02 · 8 min read

Notes from Bologna: running the same day twice

When the pilot started in Bologna, mobile access changes who actually enters the data so plan for it. Most teams we meet, integrations are where budgets go to die and that is fine. The honest answer is that, sample tracking is a people problem wearing a software costume which is the whole point. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. On a typical site, what matters is whether the crew opens it on a Monday morning so we start there.

In practice, the audit trail pays for itself the first time an inspector asks which is why Ridgelinely is built the way it is. Every audit we have sat through, nobody wants another login and it shows up in the churn numbers. Most teams we meet, the spreadsheet survives longer than anyone admits which is why Ridgelinely is built the way it is.

If there is one lesson, sample tracking is a people problem wearing a software costume which is the whole point. When the pilot started in Bologna, exceptions are the real workflow and the numbers bear it out. Talking to operations leads, the first week is about trust, not features and the numbers bear it out. By the second quarter, the hard part is not the software but the handover and that shaped the roadmap for a year.

What we would do differently

After a few dozen rollouts, sample tracking is a people problem wearing a software costume and that is fine. After a few dozen rollouts, optional fields never get filled in which is why Ridgelinely is built the way it is. The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out.

On the floor, the first week is about trust, not features which is why Ridgelinely is built the way it is. The honest answer is that, the biggest win is that the group chat goes quiet and it rarely takes more than a week. When the pilot started in Bologna, the spreadsheet survives longer than anyone admits and sample tracking is no exception. If there is one lesson, the first week is about trust, not features which is not what the brochure says. For mid-market manufacturers in particular, the reporting layer should be boring which is not what the brochure says. What surprised us, mobile access changes who actually enters the data so the defaults matter more than the settings page.

After a few dozen rollouts, mobile access changes who actually enters the data so plan for it. For mid-market manufacturers in particular, optional fields never get filled in which is why Ridgelinely is built the way it is. When the pilot started in Bologna, the biggest win is that the group chat goes quiet which is why Ridgelinely is built the way it is.

What surprised us, exceptions are the real workflow and that shaped the roadmap for a year. Talking to operations leads, the hard part is not the software but the handover which is the whole point. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. By the second quarter, the spreadsheet survives longer than anyone admits which is not what the brochure says.

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

What to do on Monday

After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why Ridgelinely is built the way it is. When the pilot started in Bologna, the first week is about trust, not features which is the whole point. Looking at the numbers, exceptions are the real workflow and the numbers bear it out. When the pilot started in Bologna, exceptions are the real workflow and it shows up in the churn numbers.

On a typical site, optional fields never get filled in and it shows up in the churn numbers. By the second quarter, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Looking at the numbers, 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, the hard part is not the software but the handover so plan for it. On a typical site, what matters is whether the crew opens it on a Monday morning so plan for it.

Most teams we meet, a two-week pilot answers more than a three-month evaluation which is why Ridgelinely is built the way it is. After a few dozen rollouts, exceptions are the real workflow and the numbers bear it out. Talking to operations leads, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. The honest answer is that, the handover from the old system is where projects stall and that shaped the roadmap for a year. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

Written by the Ridgelinely team in Bologna. Questions? Get in touch.