WEBVTT

1
00:00:00.120 --> 00:00:03.080
<v Speaker 1>Welcome to the deep dive. We sip through the noise

2
00:00:03.200 --> 00:00:06.839
<v Speaker 1>to find the signal, the key insights, and today you're

3
00:00:06.919 --> 00:00:11.439
<v Speaker 1>right here with us as we dive into effective graphic

4
00:00:11.480 --> 00:00:12.400
<v Speaker 1>design principles.

5
00:00:12.599 --> 00:00:16.760
<v Speaker 2>That's right, we're drawing from Leroy Bessler's Visual Data Insights

6
00:00:17.120 --> 00:00:18.879
<v Speaker 2>using SaaS ODS graphics.

7
00:00:18.960 --> 00:00:21.839
<v Speaker 1>Now it is focused on SaaS software.

8
00:00:21.359 --> 00:00:25.440
<v Speaker 2>But honestly, the core design ideas they apply pretty much everywhere, very.

9
00:00:25.440 --> 00:00:28.160
<v Speaker 1>Universal stuff totally. So our mission today is to pull

10
00:00:28.199 --> 00:00:32.320
<v Speaker 1>out those really practical, actionable tips. How can you make

11
00:00:32.320 --> 00:00:35.200
<v Speaker 1>your visuals clear, more impactful.

12
00:00:34.679 --> 00:00:37.359
<v Speaker 2>And Bestler kicks things off with well of the fundamentals.

13
00:00:37.640 --> 00:00:40.159
<v Speaker 2>He boils it down to three key objectives for any

14
00:00:40.240 --> 00:00:44.039
<v Speaker 2>visual Okay, what are they Providing precise numbers, showing what's

15
00:00:44.039 --> 00:00:47.479
<v Speaker 2>actually important, and crucially making sure it's readable. Clarity.

16
00:00:47.640 --> 00:00:50.000
<v Speaker 1>Right. The precise numbers part is interesting. It's like the

17
00:00:50.079 --> 00:00:53.000
<v Speaker 1>visual gives the overview, but the data underneath. Yeah, that's

18
00:00:53.039 --> 00:00:54.479
<v Speaker 1>the foundation exactly.

19
00:00:54.520 --> 00:00:56.679
<v Speaker 2>And he brings in that great quote from Joseph Pulitzer.

20
00:00:56.719 --> 00:01:00.520
<v Speaker 2>Oh yeah, be blief, clear, picturesque and accurate.

21
00:01:00.759 --> 00:01:04.000
<v Speaker 1>That's fantastic advice and it connects directly to what you

22
00:01:04.400 --> 00:01:07.359
<v Speaker 1>are listener are probably looking for getting the knowledge quickly,

23
00:01:07.760 --> 00:01:09.120
<v Speaker 1>you know, without feeling overwhelmed.

24
00:01:09.120 --> 00:01:15.200
<v Speaker 2>Absolutely brevity, which leads perfectly into the next big idea focus.

25
00:01:15.760 --> 00:01:19.640
<v Speaker 2>Bestlaer shares this great piece of advice from his assistant,

26
00:01:19.680 --> 00:01:21.239
<v Speaker 2>which wise, just put it on one page.

27
00:01:21.359 --> 00:01:23.920
<v Speaker 1>Huh direct, very direct, Yeah.

28
00:01:23.640 --> 00:01:27.359
<v Speaker 2>But powerful, right, limit the message, don't overload people.

29
00:01:27.439 --> 00:01:31.560
<v Speaker 1>And he has that anecdote about Miller brewing the computer report.

30
00:01:31.640 --> 00:01:35.040
<v Speaker 2>Oh yeah, the discapacity report. Apparently it was just pages

31
00:01:35.079 --> 00:01:38.719
<v Speaker 2>and pages long, kind of useless until until he's upseted it.

32
00:01:39.079 --> 00:01:42.439
<v Speaker 2>Focus just on the key yessage categories. Suddenly boom, the

33
00:01:42.480 --> 00:01:43.879
<v Speaker 2>important stuff just jumped out.

34
00:01:43.959 --> 00:01:46.840
<v Speaker 1>It's a perfect example, less clutter, more impact.

35
00:01:46.640 --> 00:01:49.319
<v Speaker 2>But and this is important, Bestler stresses, you have to

36
00:01:49.319 --> 00:01:52.680
<v Speaker 2>be transparent when you subset, meaning meaning you need to

37
00:01:52.719 --> 00:01:56.280
<v Speaker 2>tell the viewer what's included, but also what's not included.

38
00:01:56.319 --> 00:01:57.480
<v Speaker 2>Give them the context.

39
00:01:57.560 --> 00:01:59.000
<v Speaker 1>Okay, so how do you do that?

40
00:01:59.120 --> 00:02:02.599
<v Speaker 2>He suggests, using titles and subtitles clearly state you know,

41
00:02:02.680 --> 00:02:05.120
<v Speaker 2>the toward number of categories versus how many you're showing,

42
00:02:06.120 --> 00:02:10.199
<v Speaker 2>and give the grand total versus the subtotal for what's displayed,

43
00:02:10.560 --> 00:02:12.120
<v Speaker 2>maybe even the percentage of the total.

44
00:02:12.240 --> 00:02:15.120
<v Speaker 1>Ah. I see, So like top twenty cities make up

45
00:02:15.159 --> 00:02:17.879
<v Speaker 1>seventy two percent of total sales. Something like that.

46
00:02:17.960 --> 00:02:20.599
<v Speaker 2>Exactly like that. Yeah, it gives the viewer the full

47
00:02:20.680 --> 00:02:24.599
<v Speaker 2>picture even while you're focusing their attention. No surprises, got it.

48
00:02:24.599 --> 00:02:28.479
<v Speaker 1>It's about guiding, not hiding. Okay, so let's shift gears

49
00:02:28.479 --> 00:02:31.680
<v Speaker 1>a bit. This other category. Bessler has a fun name

50
00:02:31.719 --> 00:02:32.479
<v Speaker 1>for one approach.

51
00:02:32.599 --> 00:02:34.919
<v Speaker 2>He does, the pac Man pie chart.

52
00:02:35.080 --> 00:02:36.960
<v Speaker 1>Okay, explain the pac Man pie chart.

53
00:02:37.000 --> 00:02:38.879
<v Speaker 2>Well, think about it. Sometimes you have a bunch of

54
00:02:38.919 --> 00:02:41.680
<v Speaker 2>really small categories. If you group them into one tiny

55
00:02:41.800 --> 00:02:46.400
<v Speaker 2>other slice, yeah, it visually emphasizes how insignificant they are

56
00:02:46.400 --> 00:02:49.159
<v Speaker 2>compared to the main players. Like pac Man about to

57
00:02:49.159 --> 00:02:50.039
<v Speaker 2>eat a tiny dot.

58
00:02:50.159 --> 00:02:52.960
<v Speaker 1>Okay, I get the visual. So it downplays the small stuck.

59
00:02:52.840 --> 00:02:55.120
<v Speaker 2>Right, But then the opposite can also be true. A

60
00:02:55.199 --> 00:02:58.680
<v Speaker 2>large other slice can actually peak curiosity. Bessler uses an

61
00:02:58.719 --> 00:03:02.240
<v Speaker 2>example from his local government property taxes. They showed the

62
00:03:02.319 --> 00:03:06.120
<v Speaker 2>village's slices small, and a big chunk was just labeled other.

63
00:03:06.439 --> 00:03:08.759
<v Speaker 1>Making people ask exactly, Okay.

64
00:03:08.520 --> 00:03:11.599
<v Speaker 2>Where's the rest of my money going. Then it prompted

65
00:03:11.680 --> 00:03:13.520
<v Speaker 2>questions about that big other chunk.

66
00:03:13.719 --> 00:03:16.479
<v Speaker 1>Huh. So the other slice isn't just a dumping grounds.

67
00:03:16.840 --> 00:03:18.479
<v Speaker 1>It can be a communication tool.

68
00:03:18.319 --> 00:03:22.400
<v Speaker 2>Itself precisely depends on what you want to achieve. Minimize

69
00:03:22.400 --> 00:03:25.159
<v Speaker 2>something or maybe highlight a collective you want people to

70
00:03:25.199 --> 00:03:25.599
<v Speaker 2>think about.

71
00:03:25.759 --> 00:03:30.439
<v Speaker 1>Interesting. Okay, moving on sparse graphs. This sounds like it

72
00:03:30.439 --> 00:03:32.240
<v Speaker 1>connects to the keep it simple idea.

73
00:03:32.400 --> 00:03:36.000
<v Speaker 2>It absolutely does. Simple graphs are just easier and faster

74
00:03:36.080 --> 00:03:39.400
<v Speaker 2>to grasp. Less cognitive load for the viewer makes sense.

75
00:03:39.560 --> 00:03:40.840
<v Speaker 1>Any specific examples.

76
00:03:41.039 --> 00:03:44.719
<v Speaker 2>He mentions his sparse line annotation for trend data, basically

77
00:03:44.759 --> 00:03:48.080
<v Speaker 2>stripping away anything that isn't essential to seeing the trend itself.

78
00:03:48.240 --> 00:03:51.719
<v Speaker 1>So minimal gridlines, maybe fewer labels if the trend is obvious,

79
00:03:51.800 --> 00:03:52.439
<v Speaker 1>something like that.

80
00:03:52.919 --> 00:03:55.080
<v Speaker 2>And he points out that those pac Man pies we

81
00:03:55.199 --> 00:03:58.240
<v Speaker 2>just talked about they also count as sparse because they're

82
00:03:58.280 --> 00:03:59.479
<v Speaker 2>so focused and simple.

83
00:03:59.719 --> 00:04:04.960
<v Speaker 1>God keep it clean. Now, something really fundamental. Bar charts,

84
00:04:05.479 --> 00:04:07.080
<v Speaker 1>specifically the axis.

85
00:04:07.439 --> 00:04:11.680
<v Speaker 2>Ah, yes, the starting point. Bethler is very very clear

86
00:04:11.680 --> 00:04:14.919
<v Speaker 2>on this, and the rule is for bar charts without

87
00:04:15.000 --> 00:04:20.199
<v Speaker 2>negative values, the value axis must start at zero. Period.

88
00:04:20.279 --> 00:04:21.319
<v Speaker 1>Why is that so critical?

89
00:04:21.480 --> 00:04:23.839
<v Speaker 2>Because if you start at higher, say just to zoom

90
00:04:23.839 --> 00:04:25.920
<v Speaker 2>in on the tops of the bars, Yeah, you completely

91
00:04:25.959 --> 00:04:29.319
<v Speaker 2>distort the visual comparison. A bar that's twice as tall

92
00:04:29.600 --> 00:04:33.680
<v Speaker 2>should represent twice the value starting above zero rates that

93
00:04:33.680 --> 00:04:38.079
<v Speaker 2>fundamental relationship. It's misleading even if you don't mean it.

94
00:04:38.040 --> 00:04:40.879
<v Speaker 1>To be right. It exaggerates the differences visually, like that

95
00:04:40.920 --> 00:04:42.839
<v Speaker 1>five foot tall growth chart idea.

96
00:04:42.759 --> 00:04:45.839
<v Speaker 2>Exactly zero baseline unless you're dealing with negatives. It's about

97
00:04:45.920 --> 00:04:46.879
<v Speaker 2>visual accuracy.

98
00:04:47.040 --> 00:04:50.279
<v Speaker 1>Okay, And this ties into another principle he calls maximally

99
00:04:50.360 --> 00:04:51.000
<v Speaker 1>simple design.

100
00:04:51.279 --> 00:04:54.720
<v Speaker 2>Yep. Again, it's about removing clutter. But here the distinction

101
00:04:54.839 --> 00:04:57.519
<v Speaker 2>is important. It's not about limiting the information, but.

102
00:04:57.519 --> 00:04:59.519
<v Speaker 1>About limiting the unnecessary graphic.

103
00:04:59.600 --> 00:05:03.480
<v Speaker 2>You got it, extra borders, weird background patterns, three D effects,

104
00:05:03.519 --> 00:05:06.040
<v Speaker 2>anything that doesn't actually add information or clarify the data.

105
00:05:06.040 --> 00:05:09.160
<v Speaker 1>Get rid of it, Marie Condo for charts you said earlier.

106
00:05:09.000 --> 00:05:12.839
<v Speaker 2>Kind of does it spark understanding? If not, maybe it

107
00:05:12.879 --> 00:05:13.439
<v Speaker 2>doesn't belong.

108
00:05:13.560 --> 00:05:16.480
<v Speaker 1>Okay. Now let's talk footnotes. Often tiny text at the

109
00:05:16.480 --> 00:05:18.079
<v Speaker 1>bottom right, Usually yes.

110
00:05:18.240 --> 00:05:21.800
<v Speaker 2>But Bessler argues that if the footnote contains really crucial information,

111
00:05:22.000 --> 00:05:24.720
<v Speaker 2>like a major caveat or definition.

112
00:05:24.279 --> 00:05:26.319
<v Speaker 1>Which wouldn't be tiny, right, he actually.

113
00:05:26.120 --> 00:05:28.800
<v Speaker 2>Suggests making it the same size as the title text,

114
00:05:29.199 --> 00:05:30.279
<v Speaker 2>maybe even bold.

115
00:05:30.040 --> 00:05:32.000
<v Speaker 1>It wow, really that prominent?

116
00:05:32.120 --> 00:05:36.120
<v Speaker 2>If it's critical context? Yes, it signals. Hey, pay attention

117
00:05:36.120 --> 00:05:38.680
<v Speaker 2>to this. It fundamentally affects how you read this chart.

118
00:05:38.839 --> 00:05:43.319
<v Speaker 2>Boilerplate stuff, fine print, sure, keep it small, but important.

119
00:05:43.360 --> 00:05:45.439
<v Speaker 2>Context needs visibility.

120
00:05:45.519 --> 00:05:47.600
<v Speaker 1>That makes a lot of sense. Okay, what about the

121
00:05:47.639 --> 00:05:50.720
<v Speaker 1>text within the shart itself? Access labels? Values?

122
00:05:51.000 --> 00:05:55.600
<v Speaker 2>Big point here? Use horizontal text whenever humanly possible.

123
00:05:55.240 --> 00:05:57.240
<v Speaker 1>Because it's just easier to read, way easier.

124
00:05:57.839 --> 00:06:02.279
<v Speaker 2>Our eyes scan horizontally naturally vertical text, tilted text, it

125
00:06:02.360 --> 00:06:04.600
<v Speaker 2>forces you to crane your neck, slows you down.

126
00:06:04.800 --> 00:06:08.319
<v Speaker 1>So what about, say, long labels on a vertical axis.

127
00:06:08.480 --> 00:06:11.680
<v Speaker 2>He suggests trying to integrate that information elsewhere. Put in

128
00:06:11.759 --> 00:06:13.439
<v Speaker 2>the subtitle, maybe the main title if.

129
00:06:13.319 --> 00:06:16.000
<v Speaker 1>It fits naturally, or sometimes you don't even need the

130
00:06:16.120 --> 00:06:17.199
<v Speaker 1>label exactly.

131
00:06:17.360 --> 00:06:20.040
<v Speaker 2>If the horizontal axis is clearly showing dates, do you

132
00:06:20.079 --> 00:06:24.120
<v Speaker 2>really need to label it date? Probably not, The context

133
00:06:24.160 --> 00:06:25.000
<v Speaker 2>makes it obvious.

134
00:06:25.199 --> 00:06:27.600
<v Speaker 1>Good point. And what if you have lots of tick

135
00:06:27.680 --> 00:06:31.000
<v Speaker 1>marks on the horizontal access and the labels start overlapping

136
00:06:31.120 --> 00:06:32.120
<v Speaker 1>or turning vertical?

137
00:06:32.279 --> 00:06:35.480
<v Speaker 2>Yeah, that's a common problem. He suggests a few things.

138
00:06:35.759 --> 00:06:39.319
<v Speaker 2>Can the viewer reasonably infer the missing values? Maybe you

139
00:06:39.360 --> 00:06:41.399
<v Speaker 2>only label every second or third tick.

140
00:06:41.240 --> 00:06:43.160
<v Speaker 1>Mark, or strength the font shrink, the.

141
00:06:43.160 --> 00:06:46.639
<v Speaker 2>Font carefully, or some software has a stagger option putting

142
00:06:46.680 --> 00:06:50.240
<v Speaker 2>labels on two levels. Anything is better than unreadable vertical text.

143
00:06:50.360 --> 00:06:54.680
<v Speaker 1>Okay, good practical tips there. Now, thinking about graphs online

144
00:06:54.839 --> 00:06:57.759
<v Speaker 1>on the web, any specific advice definitely?

145
00:06:57.959 --> 00:07:00.399
<v Speaker 2>First, mouseover data tips are pretty much.

146
00:07:00.319 --> 00:07:02.240
<v Speaker 1>Essential, so when you hover the mouse, you.

147
00:07:02.160 --> 00:07:05.120
<v Speaker 2>See the exact value for that point or bar. It

148
00:07:05.160 --> 00:07:08.000
<v Speaker 2>adds that layer of precision without cluttering the main visual.

149
00:07:08.199 --> 00:07:09.800
<v Speaker 1>Nice. What else for webgraphs?

150
00:07:09.959 --> 00:07:13.360
<v Speaker 2>For really dense data thinks scatter plots with tons of

151
00:07:13.399 --> 00:07:17.480
<v Speaker 2>points or complex trend lines, consider linking to the underlying data,

152
00:07:17.959 --> 00:07:19.360
<v Speaker 2>maybe an Excel file.

153
00:07:19.160 --> 00:07:21.000
<v Speaker 1>So people can dig deeper if they want to.

154
00:07:21.519 --> 00:07:25.680
<v Speaker 2>Exactly gives them the option for detailed inspection without overwhelming

155
00:07:25.680 --> 00:07:27.360
<v Speaker 2>the initial graphic. You can link it right from the

156
00:07:27.399 --> 00:07:27.959
<v Speaker 2>graph page.

157
00:07:28.079 --> 00:07:30.000
<v Speaker 1>Smart and sizing, oh yeah.

158
00:07:30.000 --> 00:07:32.920
<v Speaker 2>Size the image appropriately for the screen. Show them the

159
00:07:33.079 --> 00:07:37.079
<v Speaker 2>entire picture, as Bessler puts it, avoid forcing people to

160
00:07:37.079 --> 00:07:38.519
<v Speaker 2>scroll around just to see the whole.

161
00:07:38.439 --> 00:07:42.480
<v Speaker 1>Charge right, basic usability. Okay, let's tackle the infamous pie

162
00:07:42.519 --> 00:07:45.720
<v Speaker 1>chart people love them or hate them? Bestler's take.

163
00:07:45.959 --> 00:07:50.720
<v Speaker 2>He gives best practices. Key thing include the slice description,

164
00:07:51.199 --> 00:07:54.279
<v Speaker 2>the actual value and the percentage for each slice.

165
00:07:54.319 --> 00:07:57.399
<v Speaker 1>Where do those go on the slice in a legend.

166
00:07:57.079 --> 00:07:59.720
<v Speaker 2>Either way, but make sure it's clear. He mentions using

167
00:07:59.800 --> 00:08:03.600
<v Speaker 2>call out lines if needed to avoid labels overlapping, especially

168
00:08:03.639 --> 00:08:04.519
<v Speaker 2>on smaller.

169
00:08:04.199 --> 00:08:06.480
<v Speaker 1>Slices, and the order of slices.

170
00:08:06.160 --> 00:08:09.360
<v Speaker 2>Definitely order them largest slice to smallest slice, usually starting

171
00:08:09.360 --> 00:08:12.519
<v Speaker 2>at the twelve o'clock position and going clockwise. It guides

172
00:08:12.519 --> 00:08:14.000
<v Speaker 2>the eye to what's most important.

173
00:08:14.120 --> 00:08:16.439
<v Speaker 1>Makes sense. What about that other slice and pies?

174
00:08:16.759 --> 00:08:20.319
<v Speaker 2>Generally, he advises against using another slice in a standard

175
00:08:20.319 --> 00:08:24.000
<v Speaker 2>pie chart unless you're specifically doing that pac Man thing

176
00:08:24.040 --> 00:08:27.920
<v Speaker 2>we talked about earlier for a very deliberate communication purpose.

177
00:08:28.600 --> 00:08:30.639
<v Speaker 2>Otherwise it can obscure too much.

178
00:08:30.759 --> 00:08:35.120
<v Speaker 1>Okay, got it. Color obviously huge in visuals. What are

179
00:08:35.120 --> 00:08:36.919
<v Speaker 1>the key color considerations?

180
00:08:37.159 --> 00:08:41.840
<v Speaker 2>Contrast is king, especially label text against its background slice

181
00:08:41.919 --> 00:08:46.440
<v Speaker 2>or bar color. Dark backgrounds need light text, Light backgrounds

182
00:08:46.480 --> 00:08:48.679
<v Speaker 2>need dark text, simple but critical.

183
00:08:48.720 --> 00:08:50.039
<v Speaker 1>Any tricks to make that easier?

184
00:08:50.600 --> 00:08:54.120
<v Speaker 2>He suggests choosing palettes that are either all generally light

185
00:08:54.200 --> 00:08:57.120
<v Speaker 2>fills or all generally dark fills. That way, you can

186
00:08:57.200 --> 00:08:59.519
<v Speaker 2>usually stick to one label color, either black or white

187
00:08:59.559 --> 00:09:01.200
<v Speaker 2>for everything. Simplifies things.

188
00:09:01.360 --> 00:09:04.240
<v Speaker 1>Interesting idea. What about the use of color itself, when

189
00:09:04.279 --> 00:09:05.000
<v Speaker 1>to use it when not?

190
00:09:05.279 --> 00:09:08.399
<v Speaker 2>He has this great line. Uncolor might be the right color.

191
00:09:08.600 --> 00:09:10.360
<v Speaker 1>I mean black and white basically, Yeah.

192
00:09:10.240 --> 00:09:12.080
<v Speaker 2>Black and white if you have very few categories. Maybe

193
00:09:12.120 --> 00:09:14.919
<v Speaker 2>shades of gray if you have a handful, reserve vibrant

194
00:09:14.919 --> 00:09:17.000
<v Speaker 2>color for when you really need it to differentiate many

195
00:09:17.039 --> 00:09:20.279
<v Speaker 2>distinct categories. Don't use color just for decoration.

196
00:09:20.080 --> 00:09:22.000
<v Speaker 1>So purpose driven color exactly.

197
00:09:22.240 --> 00:09:25.159
<v Speaker 2>He also mentions using transparency, which can be handy for

198
00:09:25.200 --> 00:09:27.399
<v Speaker 2>overlapping elements like in scatterplots.

199
00:09:27.480 --> 00:09:29.720
<v Speaker 1>Good tip. Any warnings about color.

200
00:09:29.600 --> 00:09:32.759
<v Speaker 2>Oh yeah, the big one is how colors look different

201
00:09:32.759 --> 00:09:35.519
<v Speaker 2>on screens versus projectors. Big difference.

202
00:09:35.559 --> 00:09:39.440
<v Speaker 1>Sometimes I've seen that happen washes everything out totally.

203
00:09:39.519 --> 00:09:42.879
<v Speaker 2>So test on the actual projector if you can. Even

204
00:09:42.919 --> 00:09:46.039
<v Speaker 2>different computer monitors can show colors surprisingly differently.

205
00:09:46.080 --> 00:09:47.240
<v Speaker 1>So what's the safest bet.

206
00:09:47.799 --> 00:09:51.279
<v Speaker 2>Black and white is universally safe. Shades of gray are

207
00:09:51.320 --> 00:09:54.759
<v Speaker 2>usually fine too, as long as they're distinct enough. Color

208
00:09:54.799 --> 00:09:58.039
<v Speaker 2>always carries that extra risk of looking wrong on different devices.

209
00:09:58.120 --> 00:10:00.960
<v Speaker 1>He mentions SaaS HLS colors briefly.

210
00:10:01.039 --> 00:10:03.200
<v Speaker 2>Yeah, just noting that if you use shades of the

211
00:10:03.240 --> 00:10:06.360
<v Speaker 2>same hue, make sure the lightness and saturation vary enough

212
00:10:06.399 --> 00:10:07.440
<v Speaker 2>to be distinguishable.

213
00:10:07.559 --> 00:10:09.879
<v Speaker 1>Okay, And bringing it back to basics. Again, just making

214
00:10:09.879 --> 00:10:11.000
<v Speaker 1>sure people can read the text.

215
00:10:11.080 --> 00:10:15.879
<v Speaker 2>Absolutely fundamental, sufficient font size, high contrast, plain background. Maybe

216
00:10:15.960 --> 00:10:20.440
<v Speaker 2>use bold strategically for emphasis readability. Trump's almost everything.

217
00:10:20.120 --> 00:10:22.240
<v Speaker 1>Else makes sense if they can't read it, what's the point?

218
00:10:22.679 --> 00:10:23.279
<v Speaker 2>Precisely?

219
00:10:23.440 --> 00:10:26.799
<v Speaker 1>Okay, couple of specific chart types to finish on three

220
00:10:26.879 --> 00:10:27.440
<v Speaker 1>D pie.

221
00:10:27.320 --> 00:10:32.240
<v Speaker 2>Charts just no, He's very blunt. They are always misleading

222
00:10:32.440 --> 00:10:36.799
<v Speaker 2>because the perspective disorts the slice proportions ods graphics actually

223
00:10:36.799 --> 00:10:38.360
<v Speaker 2>prevents you from making them directly.

224
00:10:38.440 --> 00:10:40.759
<v Speaker 1>Good riddance maybe probably, yeah.

225
00:10:40.559 --> 00:10:43.399
<v Speaker 2>Though older sends tools good, but yeah, avoid three D pies.

226
00:10:43.519 --> 00:10:44.919
<v Speaker 1>What about donut charts?

227
00:10:45.080 --> 00:10:46.919
<v Speaker 2>A donut chart is basically just a pie chart with

228
00:10:46.960 --> 00:10:49.039
<v Speaker 2>a whole It uses the same logic, same options.

229
00:10:49.080 --> 00:10:50.360
<v Speaker 1>Then you put text in the hole.

230
00:10:50.840 --> 00:10:54.480
<v Speaker 2>You can. There are options like whole label and whole value,

231
00:10:54.639 --> 00:10:58.200
<v Speaker 2>but he warns they have limitations. You don't have much

232
00:10:58.200 --> 00:11:00.919
<v Speaker 2>control over the font size, and software might cut off

233
00:11:00.960 --> 00:11:03.519
<v Speaker 2>the text or abbreviate it unexpectedly, so not.

234
00:11:03.679 --> 00:11:05.559
<v Speaker 1>Super reliable for critical info.

235
00:11:05.919 --> 00:11:09.759
<v Speaker 2>Probably not. He suggests using subtitles, footnotes, or maybe an

236
00:11:09.759 --> 00:11:11.960
<v Speaker 2>inset statement if you want more control over text that

237
00:11:12.000 --> 00:11:15.519
<v Speaker 2>appears in that central area, rather than relying solely on

238
00:11:15.559 --> 00:11:16.759
<v Speaker 2>the whole labels.

239
00:11:16.480 --> 00:11:19.360
<v Speaker 1>Okay, and don't it charts still need ordered slices and

240
00:11:19.440 --> 00:11:20.320
<v Speaker 1>clear label Oh.

241
00:11:20.320 --> 00:11:22.679
<v Speaker 2>Yeah, all the same best practices as pie charts apply.

242
00:11:22.960 --> 00:11:26.919
<v Speaker 2>Order the slices, include category names, values, percentages, keep it clear.

243
00:11:27.200 --> 00:11:31.240
<v Speaker 1>Got it? So, wrapping this all up, lots of practical

244
00:11:31.240 --> 00:11:31.759
<v Speaker 1>advice here.

245
00:11:31.840 --> 00:11:35.440
<v Speaker 2>Definitely. It boes down to clarity, focus, accuracy, and readability.

246
00:11:35.519 --> 00:11:38.960
<v Speaker 1>Prioritize the data, guide the viewer's eye, keep it clean,

247
00:11:39.080 --> 00:11:40.440
<v Speaker 1>make sure everything's legible.

248
00:11:40.720 --> 00:11:44.799
<v Speaker 2>Use elements like subsetting or even that other category thoughtfully.

249
00:11:45.200 --> 00:11:48.279
<v Speaker 2>It's all about creating those aha moments for your audience,

250
00:11:48.399 --> 00:11:50.000
<v Speaker 2>not overwhelming.

251
00:11:49.360 --> 00:11:54.279
<v Speaker 1>Them right, helping you, the listener, get those insights across effectively.

252
00:11:53.799 --> 00:11:55.519
<v Speaker 2>Which leads us to a final thought for you to

253
00:11:55.600 --> 00:11:55.879
<v Speaker 2>chew on.

254
00:11:56.240 --> 00:11:57.159
<v Speaker 1>Okay, let's hear it.

255
00:11:57.759 --> 00:11:59.679
<v Speaker 2>Think about a visual you're working on right now, or

256
00:11:59.720 --> 00:12:03.320
<v Speaker 2>maybe one you made recently. Pick just one principle we've

257
00:12:03.320 --> 00:12:07.120
<v Speaker 2>talked about today, maybe starting bars at zero or improving

258
00:12:07.240 --> 00:12:11.200
<v Speaker 2>text contrast or simplifying the design. How could you apply

259
00:12:11.279 --> 00:12:15.440
<v Speaker 2>that one principle immediately? And what difference realistically do you

260
00:12:15.440 --> 00:12:18.320
<v Speaker 2>think you would make to how well someone understands the

261
00:12:18.320 --> 00:12:19.759
<v Speaker 2>information you're trying to share.

262
00:12:20.200 --> 00:12:22.840
<v Speaker 1>That's a great takeaway action. Just one change can make

263
00:12:22.879 --> 00:12:24.759
<v Speaker 1>a big difference. And of course, if you want to

264
00:12:24.799 --> 00:12:28.799
<v Speaker 1>dive even deeper, Leroy Besler's book Visual Data Insights using

265
00:12:28.840 --> 00:12:31.320
<v Speaker 1>SaaS ODS Graphics is the place to go.

266
00:12:31.480 --> 00:12:33.279
<v Speaker 2>Absolutely a really solid resource.

267
00:12:33.480 --> 00:12:36.200
<v Speaker 1>Well thanks for joining us for this deep dive. Hopefully

268
00:12:36.240 --> 00:12:39.559
<v Speaker 1>you've got some new tools for your visual communication toolkit.