1. Much of the context is abstracted away when charts and summaries are crammed into a (usually) single page. This makes it hard for people to interpret quickly and requires a high degree of data literacy
2. Data is presented that fits retrospective summaries, or what I’ve learned to know I need to look at. This usually means the dashboard is not suitable for answering new questions, putting strain on the data model or falling back to custom queries
3. Combining 1 and 2 means that the people who build the dashboards are the ones who end up using them the most. So I find them good for ops teams and similar, but fall short of the coming promise of self-service data exploration yadda yadda.
...Which means the VP still needs a monthly hand-holding meeting to review these “self-service” dashboards (or worse - you screenshot and put it in a PowerPoint)