How to Retire a Dashboard Without a Fight

Sunsetting a report needs an owner, a replacement, and a date. Silence is how zombies survive.

You can inventory forever. If nothing turns off, the estate is a museum with a refresh schedule.

This is the funeral, not the census, and not the front door

Dashboard sprawl is a tax is the estate: inventory, certify, retire as a slogan. This piece is the ritual. Who speaks. What replaces the page. When the bookmark dies. How you handle the one person who still cares.

Stop commissioning a dashboard per question is intake—how the next file is born. This post is how the old one is allowed to die. If you only cut demand, the attic stays full. If you only catalog, the attic gets labels.

Retirement is change work, not a workspace setting. People bookmarked a page that once saved them. They will not notice a wiki tag. They will notice a broken link on Monday. That shock is a fight or a planned handoff.

What a retirement ritual contains

Three facts, written, before you hide anything.

Owner. The person who may turn it off. Not “the business.” A name and a backup. If nobody will sign the off switch, you do not have a candidate. You have a rumor that it is unused.

Replacement. Where the same decision now lives. Certified app. Connected Excel on the model. A labeled working paper with an expiry. “Nowhere” is allowed only when the decision is dead. “Nowhere, but keep refreshing just in case” is how zombies feed.

Date. A day the file stops being official. A day refresh stops. A day the workspace archives. Vague “soon” is how last year’s report outlives its author.

Announce those three. Then do them. The fight happens in the announcement, while you can still answer. The fight that happens after a silent takedown is personal.

What unowned sunset costs

1. Zombies eat the morning window. Unused reports still refresh and collide at 6 a.m. The 7 a.m. surprise is often a job nobody needed. Retirement is capacity you do not have to buy.

2. The certified number stays buried. People open the page they know. The old name wins. The steward’s app looks empty. Adoption fails because the wrong door still works.

3. Risk sits in the long tail. Old RLS, columns, vendors in a filter. Nobody reviews a report that “might still be used.” Access that was fine for a project is not fine two years later. See hidden costs of Power BI governance.

4. Analysts rebuild instead of pointing. Copying feels safer than retiring. Drift continues. You pay to keep two truths and to explain them: why reports show different numbers.

5. Every takedown becomes political. Without a ritual, removal looks like a slight. With a ritual, it looks like operations. Silence trains hoarding. Then cleanup needs a hero project.

6. Intake has nowhere to send people. You told them to stop commissioning pages. If the old page still lives, they keep using it and keep asking for twins. Retirement is how the intake rule becomes real.

No invented usage percentages. Pull the usage you have. Ask the EA who builds the pack. If both are quiet, that is data. It is not a reason to sneak.

What not to do

Do not delete on a Friday with no redirect. That is how you earn a VP screenshot and a zombie resurrection by Monday.

Do not recertify everything as a substitute for sunset. Most of the estate is working paper. Treat it that way.

Do not wait for unanimous consent. Unanimous consent is how nothing dies. The owner decides. The announcement is the appeal window.

Do not retire the certified model to punish sprawl. Retire brochures. The product stays. Killing the model because twenty reports hung off it is arson.

Do not measure success by reports deleted in a week. Measure by refresh jobs gone, meetings pointed at the certified app, and zombies that did not come back at 90 days.

How to retire it without a brawl

1. Prove neglect or replacement before you pick a date. Usage near zero for a cycle, or a certified view that already answers the same decision. “I don’t like this page” is not a ritual. If usage is real, you have a migration, not a funeral. Say so. Fund the move.

2. Name the owner of the off switch. Often the steward of the domain, not the original author. Authors leave. Stewards remain. If the author is the only one who understands the page, you have a tribal-knowledge problem as well—the next post in this series. Still name who turns it off.

3. Write the replacement in one line. “Use Plant Throughput app, page Shift.” “Use Inventory cash, connected Excel.” “Decision retired; no report.” Put that line in the announcement, on the old page banner, and in the app navigation. People follow a door, not a lecture.

4. Publish the calendar. Day 0: banner—“this page sunsets on DATE, go here.” Then announce to known users from usage, not a company novel. Sunset: redirect or a landing page that names the replacement. Then refresh dies. Then archive so the workspace does not look live. Short gaps. Long “deprecation” is wallpaper.

5. Hold office hours, not a trial. One session. Bring the replacement. If someone has a recurring need the certified model cannot meet, that is a model backlog item or a labeled sandbox—not a stay of execution for the zombie. If they scream, they just volunteered to own a new product with a steward. They did not earn an indefinite twin.

6. Log the funeral and watch for resurrection. What died, what replaced it, date, owner. Review at 30 and 90 days. A copy with a new name is intake failure. Send it through the commissioning rule. The ritual is what you do this week to one file.

Change leadership is the job: data project management. If nobody can say which decisions the estate serves, you need a roadmap before a mass grave. Start with one domain. Prove a quiet sunset.

What good looks like

The old URL does not pretend to be current. It points.

Refresh jobs match the certified set, not the attic.

When someone asks for the old name, a person can say the new name in one breath.

Fights happen in the two-week window, in the open. They do not happen as a surprise outage.

[Judgment:] if you cannot name who is allowed to turn a report off, you do not have governance. You have a warehouse with no loading dock.

Frequently asked questions

What if a senior leader still uses the old page? Then it is a migration. Banner, replacement, date, walkthrough. Rank does not freeze a zombie. Rank gets a better handoff.

Should we keep a read-only archive forever? A dated export or an archived workspace is fine. A live refresh of an unofficial truth is not an archive. It is a competitor.

How is this different from unused reports as a smell? That later piece is the diagnostic. This is the ceremony once you have picked a body.

Do we need a CoE to retire files? No. You need an owner, a replacement line, and a date. A committee without those three is how silence wins.

Get started

Pick one zombie. Write owner, replacement, date. Announce. Turn it off.

Need a 30-minute look at a sunset that will stick? Contact Alluvium. We’ll map one report, the certified door it should point to, and the calendar—not a catalog project.

Book a 30-minute consult.