jraines 5 hours ago

A dashboard is mostly a saved bunch of queries with a visual-aid in interpretting them.

Staleness, which Majors alludes to, is one problem.

The visuals being a poor aid to interpretability is another.

Usually these problems are coexisting & compounding: there’s too many charts here, half of them are out of date, half I don’t know how to make sense of them, and I’m not sure which half is which.

It would be interesting to revisit some of these problems in the AI era, because often the missing layer is a guide & runbook (which maybe an agent could do) that’s better than “page everyone who might know why this chart looks bad”

Reminds me of another fun dashboard question which is like “how many different ‘single source of truth’s does your company have and how many are true?”

danielvaughn 5 hours ago

Anyone know of any "data navigation" UXs like the post mentions? I'd bet someone out there is working on something like it.

rrr_oh_man 5 hours ago

that just reads like an ad for Honeycomb wrapped in a blog post

  • jraines 5 hours ago

    It’s mostly a light criticism of the Honeycomb perspective. All the value is presumably in the outbound links to thinking about dashboards that the author laments is being ignored.