Creating & Maintaining Impactful Dashboards'
summary
Defines three dashboard types—BI/MI for strategy, execution for ops/dev, and project/feature boards—and shows concrete practices: build dashboards after stakeholder conversations, use Grafana, Zabbix, Tableau or Elastic depending on query needs, and retire or rotate dashboards when campaigns end. Gives a real failure example of a persistent meaningless alert labeled red 72 and a win where exploratory dashboards tune alert thresholds. Claims dashboards measurably increase cross-team communication, catch load problems before campaigns, and should be treated as evolving assets.
AI-written summary · about
chapters (6)
- 0:00Start
- 20:24Don't Know What The Metrics Are For
- 22:35Tick Box Exercise
- 25:40Talking To Stakeholders
- 26:44Requirement Gathering & Pushing Back
- 33:12How Can I Pick Which Tools To Use?
related talks
35mWho Needs Dashboards?
42mWho Needs Dashboards?
53mDashboards: interactive data visualization
37mMaking Informed Decisions: Guidelines for Creating an Effective Dashboard
41mEffective Dashboard Design Using
21mDashboards and Runbooks: Scrapbooking for Engineers
25mBeyond Dashboards: Cultivating the Observability Mindset
18mExtend the Life of Your Dashboards: An Anti-Christmas-Tree Survival Guide