Why the Plant Manager Prints the Dashboard

The plant manager prints the dashboard before the huddle. It is not nostalgia for paper. The app failed the stand-up.

If the floor needs a sheet, you missed the grain, the speed, or a screen people can trust with gloves on.

Printing is a product signal, not a culture problem

When ops rebuilds the shift in Excel, it is often a grain problem, covered in ops still runs the plant from spreadsheets. Late insight on downtime is a clock on the line, covered in slow BI and manufacturing downtime. This post is about the printout.

A printed page means someone decided the live app would not survive the huddle. Maybe the grain is wrong or the refresh is too late. Maybe the screen is unreadable on the floor, sits behind a login nobody will fight at 6:20 a.m., or is too fragile to trust when the room is standing and the shift is already moving.

Manufacturing leaders do not print for fun. They print to carry a stable artifact into a short meeting where phones stay in pockets and projectors fail. Your Power BI app has to earn that slot, or accept that paper stays the real distribution system.

Power BI for manufacturing only works when the huddle product matches how the floor actually runs.

Why the printout wins

Grain. The huddle needs line, cell, crew, and shift. A plant-total scorecard is a leadership view, and supervisors will not stand around a monthly OEE tile.

Speed. The board can wait for close. The stand-up cannot. If the page shows yesterday’s book or this morning’s failure, paper from a local export that “mostly works” beats a red X on the wall.

Trust under real conditions. Gloves, distance from the monitor, glare, a login that times out, a slicer someone left on the wrong plant. The huddle needs a view that is hard to mis-set and easy to point at.

Stability for accountability. A printed sheet becomes the record of what the room saw. If the live page moves mid-meeting because a refresh lands or a filter changes, managers lose the shared object. Paper is crude, but it is fixed.

None of that means you should design for printers forever. It means the live product has to beat paper at the jobs paper currently does.

The costs of an app the floor prints around

1. The huddle and the executive pack diverge. Leadership sees a polished app while the floor runs on a printed cousin with different filters. Same brand, two operating realities, and the arguments migrate upstairs.

2. Adoption metrics lie. Opens from the plant manager’s office can look healthy while the stand-up never uses the live page. Nobody opens the dashboard can also mean “opens, prints, leaves.”

3. Shadow versions multiply. Each print becomes a personal ritual with a different time, different slicers, and a different page. By Thursday three supervisors hold three sheets, and reconciliation becomes a side job.

4. Refresh and gateway issues stay invisible upstairs. The floor already adapted with paper, so leadership thinks the app is live. The morning failure only hurts the people who still try the wall screen.

5. Safety and access shortcuts appear. Shared logins on a kiosk, passwords on sticky notes, unattended sessions. When the official path is clumsy, the floor invents its own. That is an access design failure, not a character flaw.

6. Analysts polish the wrong surface. Effort goes into executive polish while the huddle page stays cluttered, slow, or stuck at plant total. The people who run the asset never got a product.

7. Continuous improvement stalls. If scrap, downtime, and throughput only show up cleanly in a printed weekly pack, the shift cannot manage them daily. Problems age into reports.

8. You fund licenses for a brochure. Capacity, gateways, and models keep running while the floor’s decision cadence still runs on paper. The program paid for a wall decoration and a printer tax.

How to fix it: build a huddle product that beats paper

1. Watch one stand-up without fixing anything. Note what gets printed, what gets said, what goes on the whiteboard, and what never appears. Design for that ritual, not from the executive theme.

2. Name the huddle grain in the model. That means shift, line or work center, crew where it matters, and the few KPIs the stand-up owns. If the fact table cannot support that, stop blaming adoption and fix the model first.

3. Match refresh to the meeting, not the board pack. An operational snapshot with a clear as-of can be worth more than a perfect booked number that arrives after the shift started. Label the clock, and do not pretend operational and close views belong on the same tile.

4. Design for glance and distance. Use large type, few visuals, unmistakable plant and shift context, and minimal slicers on the huddle page. Put deep diagnostics on a steward page, not the wall view.

5. Make the default safe. The page should land on the right plant and shift without a scavenger hunt. Saved views beat tribal knowledge about which bookmark to click. If a wrong filter can silently lie, the floor will print a version that cannot drift mid-meeting.

6. Solve the floor access path. Use kiosk mode, a properly managed shared device policy, or a simple posted view that does not depend on personal mailboxes at 6:15 a.m. Login friction alone keeps the printer employed.

7. Give the huddle a stable artifact without giving up the model. If the room needs a fixed record, produce a scheduled export or paginated snapshot from the governed dataset, not a hand-sliced pbix copy. Paper can be an output of the trusted model. It should not be a forked truth.

8. Retire the competing personal prints on a date. Once the huddle page works, ask managers to stop the private exports that drift. Use the same retirement discipline as how to retire a dashboard: owner, replacement, date.

9. Review after four weeks of stand-ups. Did printing drop? Did arguments about “which sheet” drop? Did actions still get owners? Success means the huddle runs on one trusted surface, screen first, with a governed print only if the ritual still needs a sheet to carry in.

What good looks like

The wall screen or huddle tablet opens the same governed view every morning. The as-of is obvious, the grain matches the asset, and the page is readable from standing distance.

If someone still prints, they print that view on purpose, as a carry sheet from the official model, not a rebuilt cousin from last night’s export.

Executives still get their pack, and the floor is not asked to run a shift from a board layout. Manufacturing reporting earns trust when the stand-up stops needing a workaround.

Executive takeaway

A plant manager who prints the dashboard is handing you requirements.

Fix the huddle grain, the morning clock, floor access, and glance design. Then paper shrinks because the live product finally wins the stand-up, not because you banned printers.

Want to know why the floor still prints around Power BI? Book a session. We’ll map one huddle, the grain and refresh it needs, and the page that should replace the printout. Or start with a Free Model Health check.