Retire GTM dashboards that no longer support decisions
Decide whether to retain, repair or retire a GTM dashboard by checking its decisions, users, dependencies and replacement path.

Identify the decision behind the dashboard
Start with the owner and the decision the dashboard is intended to support. Ask for a recent example: a campaign was adjusted, a seller followed up on an opportunity or a launch milestone changed. A familiar report name is not enough to establish that the dashboard still has an active purpose.
Record its audience, review cadence, source systems and known limitations. Check whether the dashboard is used seasonally or during a particular planning cycle before interpreting low recent usage as evidence that it is unnecessary.
Check dependencies before removing access
Find scheduled exports, embedded views, saved links and recurring meetings that depend on the dashboard. Ask the report owner who receives its outputs, including people who never open the dashboard directly. Usage counts alone can miss those readers.
Distinguish the presentation from the underlying data model. Retiring a redundant view should not accidentally remove a shared dataset or disrupt another report. The authorized system owner decides what technical changes are safe.
Choose retain, repair, consolidate or retire
Retain a dashboard when it supports a current decision and its definitions are understood. Repair it when the decision remains useful but the data, filters or presentation are unreliable. Consolidate overlapping views only after checking whether they use the same audience, period and metric definitions.
Retire a view when its owner confirms that the decision is no longer needed or an agreed replacement covers it. Document the reason, affected users and target date. Keep unresolved differences visible rather than calling two reports duplicates because their titles sound similar.
Example: two campaign reports disagree
Illustrative review: a weekly campaign dashboard and a monthly executive report both show conversions, but one counts submissions and the other counts qualified accounts. The reviewer first clarifies the definitions. The two totals should not be merged as if they describe the same event.
The team may keep both views with clearer labels, or retire one after agreeing how its decision will be supported elsewhere. Record the definition and replacement link in the retirement notice so readers understand what changed.
Complete the transition and check for missed users
Notify affected users before the change, provide the replacement where one exists and update links in operating documents. Preserve required historical records under the organization’s retention policy. Avoid deleting source data merely because its dashboard is no longer useful.
After the agreed transition, confirm that exports and scheduled messages behave as intended. Keep a named contact and a route for reporting missed dependencies. Record the final disposition and any remaining exception so the next owner can understand the reporting landscape.