2026-06-21 · 7 min read

16 questions to ask before you buy a console

On the floor, exceptions are the real workflow so the defaults matter more than the settings page. On a typical site, nobody reads the manual, so the defaults are the product which is not what the brochure says. Talking to operations leads, the spreadsheet survives longer than anyone admits so plan for it. The honest answer is that, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. By the second quarter, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Looking at the numbers, the schedule is only as good as the last update so plan for it.

By the second quarter, mobile access changes who actually enters the data so the defaults matter more than the settings page. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. On the floor, the first week is about trust, not features so plan for it. The honest answer is that, the schedule is only as good as the last update so plan for it. By the second quarter, the schedule is only as good as the last update and that is fine.

Where the time went

When the pilot started in Wroclaw, exceptions are the real workflow which is why the API is documented before the UI. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so we start there. In practice, integrations are where budgets go to die and quality inspection is no exception.

When the pilot started in Wroclaw, integrations are where budgets go to die so we start there. In practice, nobody wants another login which is the whole point. When the pilot started in Wroclaw, optional fields never get filled in so plan for it. Every audit we have sat through, the schedule is only as good as the last update which is the whole point.

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

What to do on Monday

If there is one lesson, the schedule is only as good as the last update and the numbers bear it out. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is why Terrahq is built the way it is. If there is one lesson, the hard part is not the software but the handover which is why the API is documented before the UI. Talking to operations leads, the spreadsheet survives longer than anyone admits and quality inspection is no exception.

Most teams we meet, history matters more than dashboards when something goes wrong which is why Terrahq is built the way it is. Talking to operations leads, nobody wants another login and that is fine. When the pilot started in Wroclaw, the schedule is only as good as the last update and that shaped the roadmap for a year. On the floor, the handover from the old system is where projects stall which is not what the brochure says.

Written by the Terrahq team in Wroclaw. Questions? Get in touch.