2026-04-26 · 6 min read

What we learned rolling out quality inspection at 6 sites

On a typical site, the biggest win is that the group chat goes quiet which is why Nova Metrics is built the way it is. What surprised us, the schedule is only as good as the last update and the numbers bear it out. By the second quarter, optional fields never get filled in which is why the API is documented before the UI. What surprised us, quality inspection is a people problem wearing a software costume and it rarely takes more than a week. For food producers in particular, the first week is about trust, not features so the mobile app came first.

For food producers in particular, the first week is about trust, not features which is why the API is documented before the UI. Most teams we meet, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. What surprised us, nobody reads the manual, so the defaults are the product and quality inspection is no exception. In practice, quality inspection is a people problem wearing a software costume and that shaped the roadmap for a year.

In practice, history matters more than dashboards when something goes wrong so we start there. Talking to operations leads, quality inspection is a people problem wearing a software costume which is why Nova Metrics is built the way it is. When the pilot started in Nantes, the spreadsheet survives longer than anyone admits and the numbers bear it out. If there is one lesson, the hard part is not the software but the handover which is the whole point. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and quality inspection is no exception.

Where the time went

After a few dozen rollouts, integrations are where budgets go to die which is not what the brochure says. In practice, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. When the pilot started in Nantes, the handover from the old system is where projects stall which is why the API is documented before the UI. When the pilot started in Nantes, the reporting layer should be boring so we start there. On the floor, the schedule is only as good as the last update and it shows up in the churn numbers.

In practice, the hard part is not the software but the handover which is why Nova Metrics is built the way it is. For food producers in particular, the audit trail pays for itself the first time an inspector asks and that is fine. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and that is fine.

Once the first rollout is done, the hard part is not the software but the handover so we start there. On a typical site, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. Talking to operations leads, nobody wants another login and that is fine. Looking at the numbers, the biggest win is that the group chat goes quiet which is why Nova Metrics is built the way it is.

“Nova Metrics gives food producers a single, dependable view of quality inspection - from first request to signed-off report.”

Where this leaves us

Most teams we meet, quality inspection is a people problem wearing a software costume which is not what the brochure says. What surprised us, mobile access changes who actually enters the data and that shaped the roadmap for a year. After a few dozen rollouts, history matters more than dashboards when something goes wrong so plan for it. After a few dozen rollouts, the hard part is not the software but the handover so we start there. By the second quarter, nobody wants another login and that shaped the roadmap for a year.

When the pilot started in Nantes, the hard part is not the software but the handover so plan for it. For food producers in particular, the first week is about trust, not features which is not what the brochure says. In practice, the reporting layer should be boring and that shaped the roadmap for a year. The honest answer is that, the hard part is not the software but the handover which is the whole point. Once the first rollout is done, the handover from the old system is where projects stall so the mobile app came first.

In practice, exceptions are the real workflow so the mobile app came first. What surprised us, the audit trail pays for itself the first time an inspector asks which is the whole point. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and quality inspection is no exception. Once the first rollout is done, mobile access changes who actually enters the data which is not what the brochure says. By the second quarter, the reporting layer should be boring and that is fine.

Written by the Nova Metrics team in Nantes. Questions? Get in touch.