The Birchgold dashboard is the screen the team opens in the morning, not a report they email once a week

Birch Gold Group already had the data. What they did not have was one place the whole ops desk trusted. Numbers lived in sheets, in inboxes, and in the head of the person who built the last export. We put internal dashboards on top of that work, then wired the automations that keep those screens current. About twenty hours a week came back because people stopped rebuilding the same picture.

The test we used was simple. If the floor does not open the dashboard before they open Slack, we failed. A chart that looks expensive and sits unused is worse than a spreadsheet, because now you have two sources and no owner.

What has to be on the screen if people will live in it

Live work, not last month. Exceptions, not only totals. The row that is stuck, the owner of that row, and the time it has been stuck. If the screen cannot tell you who to call, it is decoration.

We also put the boring counts on purpose: volume, age, retries. Those are the numbers that go wrong on Friday. When a job succeeds with empty data, the dashboard has to say so. A green tick with no payload is how you train a team to stop looking.

The paper next to the keyboard still matters

Some people still want a printed list for the stand-up. That is fine. The print comes from the same source as the screen. We did not leave a shadow spreadsheet “for the people who do not like the tool.” That shadow file is how the dashboard dies in six weeks.

If you ask us for a dashboard, we will ask who opens it at 9:00 and what they do in the first ten minutes. If you cannot name that, we will fix the workflow first and draw the screen second.