this repo has no description
:art:
+7
-6
+7
-6
Data/Dashboards.md
+7
-6
Data/Dashboards.md
···
12
12
- Purpose and explanation of the data being shown.
13
13
- Caveats and assumptions.
14
14
- Extra Context:
15
-
- Why this dashboard exists.
16
-
- Who it's for.
17
-
- When it was built, and if and when it's set to expire .
18
-
- What features it's tracking via links to team repositories, project briefs, screenshots, or video walkthroughs.
15
+
- Why this dashboard exists.
16
+
- Who it's for.
17
+
- When it was built, and if and when it's set to expire .
18
+
- What features it's tracking via links to team repositories, project briefs, screenshots, or video walkthroughs.
19
19
- Take Aways.
20
20
- Metadata (owner, related OKRs, TTL, …).
21
21
- Make them so its easy to go one layer down (X went down in Y location, or for Z new users, etc).
···
40
40
- **It's usually not possible to generate meaningful insight simply by looking at line charts in a dashboard** A chart alone cannot possibly convey everything, and that kind of thinking inhibits our ability to influence the business with our work.
41
41
- Specially, if [there are 10 unrelated charts in the same dashboard](https://www.deathofdashboards.com/).
42
42
- Building a dashboard requires gathering lot of context. Once built, only a few users aware of all the context can really use it in the proper way.
43
+
- They can serve endless needs, but in doing so, rarely do they serve _particular_ needs perfectly
43
44
- Dashboards shouldn't be single-use
44
45
- Ask this:
45
-
- Can this new dashboard request be added into an existing one?
46
-
- What are you going to do differently by looking at the Dashboard? Focus on that [[Metrics|metric]] and add it to the main Dashboard
46
+
- Can this new dashboard request be added into an existing one?
47
+
- What are you going to do differently by looking at the Dashboard? Focus on that [[Metrics|metric]] and add it to the main Dashboard
47
48
- Beware of the death by 1,000 filters: After a dashboard had gone live, you'll be flooded with requests for new views, filters, fields, pages, everything
48
49
- Dashboards are decision-making infrastructure, and infrastructure needs to be maintained. Be explicit about which Dashboards are disposable and add a TTL to them.
49
50
- The numbers and charts on a dashboard very rarely have any direct personal meaning to the people using it. There's tons of other work to do, and unless that dashboard is directly tied to your performance or compensation, there are probably more important things to look at. People are more likely to check stock prices when they actually own (and thus benefit from) the stock.