FactoryThread

Playbook

What data-driven actually means on a factory floor

Not more dashboards. Fewer arguments, faster decisions, and a written record of why the call was made.

8 min read

Four levels, and where plants actually are

Descriptive: what happened. Diagnostic: why. Predictive: what will happen. Prescriptive: what to do about it. Vendors sell level four. Most plants are somewhere between one and two, and inconsistently.

The honest sequence is to make level one trustworthy and fast before buying level three. A prediction built on data nobody trusts changes no behaviour.

The decision, not the dashboard, is the unit of work

Start from a decision someone makes on a schedule: which Flows to expedite, which asset to take down, which supplier to call, which line to staff. Then ask what would change the answer, and what evidence would be needed to change it.

If no realistic data would change the decision, do not build anything. That test alone eliminates a large share of dashboard backlogs.

Keep the experience, write it down

Veteran judgement is usually right and rarely documented. The highest-return exercise in most plants is to sit with the person who 'just knows' and turn their rules into explicit logic — thresholds, exceptions, sequences.

Encoded, that knowledge runs every shift, survives retirement and can be improved by argument rather than repeated from memory.

Measure adoption, not deployment

A metric with no owner and no action attached is decoration. Track how many decisions are now made from the shared picture, how long the daily meeting takes, and how many spreadsheets have been retired. Those move margin; dashboard counts do not.

Start here

Ask one question. Get one answer. Today.

Start on the free tier with a single connection, or bring a real question to a working session and we will build the first answer with you.

Free tier · No credit card · Cloud or self-hosted