2026-07-29 · 7 min read

Exceptions are the real workflow

In practice, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Once the first rollout is done, optional fields never get filled in so plan for it. Most teams we meet, a two-week pilot answers more than a three-month evaluation which is the whole point. After a few dozen rollouts, the schedule is only as good as the last update which is the whole point. Every audit we have sat through, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Looking at the numbers, optional fields never get filled in which is why the API is documented before the UI.

Once the first rollout is done, nobody reads the manual, so the defaults are the product and quality inspection is no exception. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. The honest answer is that, optional fields never get filled in and quality inspection is no exception.

Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Looking at the numbers, history matters more than dashboards when something goes wrong which is not what the brochure says. On a typical site, exceptions are the real workflow so plan for it.

Where the time went

Talking to operations leads, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. By the second quarter, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Looking at the numbers, mobile access changes who actually enters the data and quality inspection is no exception. On the floor, integrations are where budgets go to die which is why Fathomhq is built the way it is.

Every audit we have sat through, quality inspection is a people problem wearing a software costume which is the whole point. After a few dozen rollouts, quality inspection is a people problem wearing a software costume and that is fine. Looking at the numbers, the reporting layer should be boring which is not what the brochure says.

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

Where this leaves us

The honest answer is that, mobile access changes who actually enters the data so the mobile app came first. The honest answer is that, exceptions are the real workflow and that is fine. Talking to operations leads, the first week is about trust, not features and that shaped the roadmap for a year. Looking at the numbers, the spreadsheet survives longer than anyone admits so plan for it. When the pilot started in Tallinn, optional fields never get filled in which is why the API is documented before the UI. Talking to operations leads, nobody wants another login and it rarely takes more than a week.

On the floor, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Every audit we have sat through, nobody reads the manual, so the defaults are the product so the mobile app came first. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is why Fathomhq is built the way it is. Once the first rollout is done, history matters more than dashboards when something goes wrong which is why Fathomhq is built the way it is. In practice, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

Written by the Fathomhq team in Tallinn. Questions? Get in touch.