R4 — Budget 20-30% of build effort annually for maintenance from day one; assign a metric-definitions owner; audit quarterly and archive any dashboard unopened in 30+ days

Rule: Every dashboard build must include maintenance budget = 20-30% of build effort annually (Custom-embedded 3-year TCO converges on $300K-$630K (multiple, mostly vendor sources) with 20-30% annual maintenance; hidden costs are multi-tenancy/RLS, performance at scale, perpetual maintenance, Dashboard rot: data sources change schemas, metric definitions drift across departments, organizational attention wanes; custom/embedded builds carry the heaviest ~20-30%/yr maintenance burden). Assign a metric-definitions owner. Audit quarterly and archive any dashboard unopened in 30+ days.

Reconsider-the-approach benchmark: if adoption of an internal dashboard sits below ~25-30% of intended users after 90 days, the problem is workflow fit or trust, not features — fix those before adding anything.

Why: Adoption stagnation (BARC / Eckerson Group (March 2022, 214 D&A leaders surveyed Nov-Dec 2021) — BI/analytics adoption at 25% of employees on average; "stuck around 20% for many years" per Eckerson, Gartner — "pervasive business intelligence remains elusive, with BI and analytics adoption at about 30% of all employees" (doc 3753469, Howson & Sallam)) is the cumulative effect of un-maintained, un-audited dashboards. Schema drift propagates the moment a vendor changes a column. Same lesson as portal brief's R4 — Treat data custody as a project line item, not a footnote: PIPEDA consent + MFA + encryption + breach response plan + 24-month breach records all live in scope before launch and data-tools brief's R5 — Budget for pipeline maintenance from day one; if the client can't commit to upkeep, rent the managed version instead of building one.

How to apply:

• Quarterly dashboard audit: list every dashboard, last-opened date, metric-owner.
• Dashboards unopened in 30+ days are archived (not deleted — archived) so the maintenance load shrinks naturally.
• Below-threshold adoption triggers a workflow-fit / trust audit before any feature work.