Verdant: Executive Dashboard With Too Many Filters

Design for a five-second read. Put four single-value tiles across the top: MRR, net new MRR, logo churn rate, and SLA attainment. These answer the executives' four stated questions and should use large numbers, clear labels, and conditional colors only where thresholds are agreed, such as SLA red below 95%. Below that, add an MRR trend line for the last 13 weeks and a net new MRR bar chart by week or segment. The last two tiles can cover the new asks: pipeline coverage as a single value or bullet-style comparison to target, and ticket backlog by priority as a horizontal bar chart. Avoid pie charts and dense tables on the first screen. Place the most decision-critical metric top-left because that is where scanning starts. Use a text tile as a short section header, not as decoration. For mobile, order tiles so the four KPIs appear first in a single column, and keep each tile to one number or one simple trend. The deep detail should move to a linked second page, not the first screen.

Treat the executive dashboard as a curated view, not a query builder. Keep three global filters: date range, region, and customer segment. Set sensible defaults, such as the last 13 complete weeks and all regions, and make the date range the only filter most executives touch. Move plan, CSM, industry, country, channel, and product tier to a separate 'Deep Dive' dashboard with its own tiles and filters. On the executive dashboard, use each tile's 'Listen' settings so irrelevant filters do not create impossible combinations or empty results; for example, the support tile may not need the sales channel filter. Use user attributes for stable scoping, such as region or business unit, only when the audience is genuinely segmented; do not use them to replace a needed date filter. 'No data' often comes from cross-filtering unrelated dimensions, so reduce the filter set and separate exploratory views. This also lowers load time because fewer tiles rerun with every filter change. Preserve self-service by linking to the deep-dive dashboard and documenting which questions belong where.

Before adding two metrics, cut the existing surface area. Reduce 14 tiles to 8, remove unused filters, and replace wide tables with a few columns or a single-value tile. Check each tile's query in System Activity; identify the slowest tiles and simplify joins, add a limit where appropriate, or pre-aggregate in LookML if the source is stable. Use dashboard caching and avoid unnecessary auto-refresh; executives reviewing weekly data do not need a live query every time the page opens. For mobile, use a single-column layout, increase whitespace, and hide detail tiles behind a link rather than shrinking them. Put the four KPIs first so mobile users see them without scrolling. Adding pipeline coverage and ticket backlog is feasible if the grain matches the existing Explore; if either requires a new join that multiplies rows, do not add it to the same dashboard until the join is tested. The risk is that a cleaner dashboard feels less flexible. Mitigate that by providing the deep-dive dashboard and a short note on where to find detail, rather than keeping every filter on the executive page.