A control room for management, built on data you already have

Plant operators have had control rooms for decades: screens that show the state of the machinery, live. Management, in most mid-sized companies, has nothing comparable for the business itself. The board meets monthly around slides prepared days earlier, with numbers that were already old when they were pasted in. Between one meeting and the next, the company is steered by memory and by phone.

This year I prepared a board presentation as a set of live pages: every figure read directly from the production database at the moment of viewing. Orders in progress, documents processed, field activity, growth over the previous weeks. After the meeting, those same pages became a permanent management area inside the company platform. The board slides and the daily instrument turned out to be the same object.

Why the monthly deck falls short

A deck assembled by hand has three structural costs. It consumes days of someone's work each month. It contains transcription errors, small and occasionally large. And it freezes the questions: the deck answers what was asked last quarter, while the discussion in the room moves on, and every new question is postponed to the next meeting. The numbers exist in the systems all along.

What a management control room looks like

The form is simple: a small set of pages, each answering one question the leadership actually asks. How much work did we do this week, and where. What is stuck, and since when. How the key volumes are moving against last month and last year. Each figure carries its source and its timestamp, so the reader knows what they are looking at. The pages read from the same database that runs the operations, so there is nothing to prepare and nothing to reconcile.

Two design rules keep it honest. First, every number must be traceable to the operational records, one click away from the detail behind it. Second, the pages show what the company measures, and nothing else: a control room with vanity metrics trains people to ignore it.

How to build it without a big project

The precondition is having operational data in a queryable state, which is a by-product of digitising processes. Given that, the first version of a management area is weeks of work: three or four pages, the questions that matter most, read-only access for the people who need it. It grows the way the rest of the platform grows, one page at a time, driven by the questions the leadership actually brings.

Common objections

"We have reports in our ERP." ERP reports answer the questions the vendor imagined. A management area answers yours, in your language, across all the systems involved, including the ones outside the ERP.

"Real-time is overkill for management." The value is trust rather than speed. A number with a timestamp and a source ends the meetings spent debating whose spreadsheet is right.

"Our data is not clean enough." The control room is precisely what surfaces that, gently: the first weeks of a live page do more for data quality than a year of memos, because errors become visible where they are made.

What to take home

An exercise for the next board meeting: note how old each number on the slides is, and how long it took someone to assemble them. Then list the three questions the leadership asks most often between meetings. Those three questions are the specification for the first version of your control room.

Want to see your company's numbers live instead of monthly? Let's talk.