Change Management for Analytics (Without the Theater)

Training decks do not retire shadow Excel. Owners, defaults, and one app do.

You can run a launch week, a town hall, and a badge on the intranet. On Tuesday the plant controller still opens last month’s workbook. That is not a people problem. It is a change design that never named what stops.

Adoption is not a communications campaign

Most Power BI “change programs” are a calendar of awareness. Kickoff. Demo. Optional training. A PDF of click paths. Then go-live, which means a link in an email.

Awareness does not move a close. Operators change when the new path is faster than the old file, the number matches finance, and a leader stops accepting the old file. If any of those three is missing, the deck was theater.

This is not why nobody opens the dashboard. That piece is the product: grain, speed, trust. This piece is the operating change: who stops, who owns, what the default is on Monday. Delivery without that change ships a museum. We already said programs stall on scope and owners in analytics programs fail in delivery. Here the stall is after the ship: the work still lives in the twin.

Hands-on sequence and adoption is the job Alluvium scopes as data project management and change leadership. Strategy still matters. If the report is not tied to a decision, no amount of coaching will make it a habit. That is from dashboards to decisions. Do not confuse a decision map with a training plan.

What practical change actually is

It is a named owner for the new way of working—not a “champion network” with no authority.

It is a default. The Monday pack is the app. The meeting agenda uses the app. Email attachments of the old file are returned, not praised.

It is a retire list with dates. Twin workbooks, twin reports, twin extracts. If you cannot name what dies, you did not change anything. You added inventory.

It is a first-week desk: access, grain, and “where did my tab go.” If that desk is an IT ticket, the workbook wins by lunch.

It is leadership behavior. If the CFO still asks for the file by name, the organization heard the real instruction.

The costs of theater

1. The twin never dies. You paid for a model and kept the close in a shared drive. Two truths. Two refreshes. The argument in the meeting is which file is live. Change that does not retire is a duplicate cost, not a transition.

2. Training teaches a product nobody will use. Click-path hours on a page that is slower than Excel, or that disagrees with the controller, teach one lesson: stay on the spreadsheet. You burned calendar. You did not change the work.

3. Local heroes become the bottleneck. One analyst who “gets Power BI” fields every ping. When they are out, the plant reverts. That is not adoption. That is a single point of failure wearing a success story.

4. Leaders keep two stacks. They nod in the steering meeting and still request the old pack. The floor copies the leader. You cannot train your way past an executive who will not switch.

5. Shadow process goes quieter, not away. People stop arguing in the channel. They keep a private file. You see “green” adoption because the ticket volume dropped. The decision still runs on a copy.

6. The next launch is already discounted. After two theatrical go-lives, the plant will sit through the third demo and change nothing. Trust in the program is a finite stock. You spent it on slides.

If last Tuesday’s meeting still used a workbook the program claimed to replace, you already have the bill.

What not to do

Do not schedule change after go-live. If adoption is “phase two,” phase two is never staffed.

Do not measure success by attendance at training. Measure by files retired, meetings that run from the app, and questions that go to the steward instead of the hero.

Do not keep the old file “just for this cycle.” That sentence is how twins become permanent.

How to fix it

1. Name the stop. Write the workbook, extract, or email pack that this release replaces. Owner. Date. What happens if someone still sends it. If you cannot name the stop, you are launching a hobby.

2. Make one app the default. Viewers should not hunt workspaces. The Monday pack lives in one place. Personal bookmarks are fine. Personal published twins are not. An app is how you stop “which report is live” without a lecture.

3. Put change tasks on the same board as build. Who loses the file. Who is trained. Who covers week one. Who tells leadership the old pack is closed. Assign names. If it is not on the board, it will lose to a visual polish ticket.

4. Change the meeting, not the inbox. The first live week, the agenda owner opens the app in the room. Questions that used to be “send me the file” become filters. If the meeting still needs a paste, the product is wrong—or the chair is not on board. Fix that before you schedule more training.

5. Staff a first-week desk, then taper. A named person for access, grain, and “where did my tab go.” Time-box it. Capture the repeats as model or app fixes. Do not let the desk become a permanent report factory. That is how you recreate the IT wait inside change.

6. Leaders go first, in public. The CFO, plant lead, or VP who asked for the program uses the app in the first meeting they chair. They refuse the twin. That is the only communication that scales. Town halls are optional after that.

Start with one meeting and one file. Prove the stop. A Power BI Quickstart can stand up the product. Change is whether it replaces the work. If you lack someone who can own sequence, stakeholders, and the stop, that is the change leadership job. A borrowed lead for a quarter beats a laminated comms plan.

What good looks like

The old file has a tombstone date. People still remember it. They do not open it.

The Monday agenda assumes the app. Exceptions are a filter, not a side workbook.

Questions go to the measure steward, not to whoever built the first page.

Training is short and late—after the page is faster than the spreadsheet and agrees with finance. Not instead of that.

FAQ

Do we need a change-management methodology? No. You need a stop list, a default, and a leader who will not take the old file. Frameworks without those three are theater with better branding.

What if the new report is worse than the spreadsheet? Then do not force the switch. Fix grain, refresh, and trust first. Change cannot rescue a bad product. That is the adoption post, not this one.

Get started

Stop scheduling another launch week. Write the file that dies, the app that replaces it, and the person who will refuse the twin.

Need a 30-minute look at why the dashboard shipped and the workbook still runs Tuesday? Contact Alluvium. We will map one meeting, one stop, and the first-week desk—not another training deck.

Book a 30-minute consult.