Dashboards Are Dead. Long Live the Question

1
00:00:00,000 --> 00:00:03,400
Most organizations still think the problem is we need better dashboards.

2
00:00:03,400 --> 00:00:07,840
They are wrong, dashboards didn't fail, they expired, the executive decision model moved

3
00:00:07,840 --> 00:00:11,960
but the reporting model stayed put, like a calendar invite nobody attends but everyone

4
00:00:11,960 --> 00:00:14,000
keeps forwarding.

5
00:00:14,000 --> 00:00:18,320
And here's the uncomfortable truth, dashboards became a success metric, shipped the report,

6
00:00:18,320 --> 00:00:20,200
declared victory, move on.

7
00:00:20,200 --> 00:00:22,960
Meanwhile, leadership stopped shopping for canvases.

8
00:00:22,960 --> 00:00:26,840
They started asking for answers what changed, why it changed, who owns it, and what we do

9
00:00:26,840 --> 00:00:27,840
next.

10
00:00:27,840 --> 00:00:29,280
That is the new interface.

11
00:00:29,280 --> 00:00:32,280
Early anchor, the executive still asks a human.

12
00:00:32,280 --> 00:00:37,040
This is the pattern, every data team recognizes but pretends is fine, the dashboard exists,

13
00:00:37,040 --> 00:00:41,920
it's gold, it has the right colors, the right filters, a semantic model behind it, and

14
00:00:41,920 --> 00:00:44,240
a refreshed schedule that somebody fought for.

15
00:00:44,240 --> 00:00:47,200
You publish it, you announce it, you train people on it and you even get a couple weeks

16
00:00:47,200 --> 00:00:48,520
of polite usage.

17
00:00:48,520 --> 00:00:52,040
Then the executive pings a person anyway, not because the executive is lazy, not because

18
00:00:52,040 --> 00:00:55,920
the dashboard is bad, but because the executive isn't asking for a number.

19
00:00:55,920 --> 00:00:57,720
The executive is asking for a decision.

20
00:00:57,720 --> 00:00:59,960
A dashboard can show that revenue dipped.

21
00:00:59,960 --> 00:01:03,440
It usually can't tell you whether the dip matters, whether it's noise, whether it's a known

22
00:01:03,440 --> 00:01:07,800
operational incident, whether it's a forecast issue, whether it breaks a covenant, or whether

23
00:01:07,800 --> 00:01:10,600
it's a pricing change working as intended.

24
00:01:10,600 --> 00:01:15,480
And the moment the executive asks, should we worry, the dashboard stops being the interface.

25
00:01:15,480 --> 00:01:17,360
The human becomes the interface again.

26
00:01:17,360 --> 00:01:20,000
Because humans do three things, dashboards don't do reliably.

27
00:01:20,000 --> 00:01:21,280
First, interpretation.

28
00:01:21,280 --> 00:01:24,280
They translate a metric into a story the business can act on.

29
00:01:24,280 --> 00:01:25,480
Second, confidence.

30
00:01:25,480 --> 00:01:28,880
They can say out loud whether the number is trustworthy today or whether the pipeline is lying

31
00:01:28,880 --> 00:01:29,880
again.

32
00:01:29,880 --> 00:01:30,880
Third, ownership.

33
00:01:30,880 --> 00:01:33,040
They can answer the real question executives care about.

34
00:01:33,040 --> 00:01:35,520
Who's responsible for this and what are they doing about it?

35
00:01:35,520 --> 00:01:37,280
Now here's the part that kills me.

36
00:01:37,280 --> 00:01:40,280
Most organizations measure dashboard success by adoption.

37
00:01:40,280 --> 00:01:42,600
Views, clicks, time on page.

38
00:01:42,600 --> 00:01:46,720
But the hidden KPI, the one leadership actually experiences is decision latency.

39
00:01:46,720 --> 00:01:49,600
How long does it take to go from question to action?

40
00:01:49,600 --> 00:01:52,400
Because that's the real cost of your reporting system.

41
00:01:52,400 --> 00:01:54,920
Not licenses, not refresh capacity.

42
00:01:54,920 --> 00:01:59,440
Calender time, human attention, the delay between noticing and doing.

43
00:01:59,440 --> 00:02:03,640
And that delay is exactly why the executive message is a person instead of opening power

44
00:02:03,640 --> 00:02:04,640
BI.

45
00:02:04,640 --> 00:02:06,400
They're not trying to bypass governance.

46
00:02:06,400 --> 00:02:08,120
They're trying to bypass friction.

47
00:02:08,120 --> 00:02:10,600
Scenario one is going to make this painfully obvious.

48
00:02:10,600 --> 00:02:16,120
The executive asks, why did Emia revenue dip last week and what decisions does it affect?

49
00:02:16,120 --> 00:02:19,040
And the answer arrives before power BI even opens.

50
00:02:19,040 --> 00:02:23,920
Not because power BI is useless because it isn't, but because the interface moved upstream.

51
00:02:23,920 --> 00:02:27,240
The question became the input and the system assembled the response.

52
00:02:27,240 --> 00:02:29,000
That's the reality you're operating in.

53
00:02:29,000 --> 00:02:32,920
And if you're still shipping dashboards as the end product, you're optimizing for visibility

54
00:02:32,920 --> 00:02:35,600
while leadership is demanding decisions.

55
00:02:35,600 --> 00:02:36,840
That distinction matters.

56
00:02:36,840 --> 00:02:40,120
The foundational misunderstanding, visibility versus decisions.

57
00:02:40,120 --> 00:02:43,880
The foundational mistake is treating visibility as if it produces decisions.

58
00:02:43,880 --> 00:02:45,120
It doesn't.

59
00:02:45,120 --> 00:02:46,120
Visibility produces exposure.

60
00:02:46,120 --> 00:02:47,560
It produces screenshots.

61
00:02:47,560 --> 00:02:51,560
It produces meetings where everyone nods at the same line chart and still leaves without

62
00:02:51,560 --> 00:02:53,080
changing anything.

63
00:02:53,080 --> 00:02:56,920
And organizations keep doubling down on visibility because visibility is easy to measure.

64
00:02:56,920 --> 00:02:57,920
A dashboard exists.

65
00:02:57,920 --> 00:02:59,160
A report was shipped.

66
00:02:59,160 --> 00:03:01,040
A workspace has artifacts.

67
00:03:01,040 --> 00:03:03,320
Someone can point to a thing and say, we're data driven.

68
00:03:03,320 --> 00:03:04,320
That's not data driven.

69
00:03:04,320 --> 00:03:05,560
That's artifact driven.

70
00:03:05,560 --> 00:03:07,160
The old bargain was simple.

71
00:03:07,160 --> 00:03:10,600
Centralize the numbers, make them consistent, put them on a canvas, and the organization will

72
00:03:10,600 --> 00:03:12,000
operate better.

73
00:03:12,000 --> 00:03:16,080
Dashboards scaled visibility across the org the way SharePoint scaled document chaos.

74
00:03:16,080 --> 00:03:18,200
It wasn't pretty, but it was legible.

75
00:03:18,200 --> 00:03:19,920
For years that was rational.

76
00:03:19,920 --> 00:03:22,600
Executives had monthly rhythms, quarterly rhythms.

77
00:03:22,600 --> 00:03:23,600
Reports were periodic.

78
00:03:23,600 --> 00:03:25,320
Reports matched cadence.

79
00:03:25,320 --> 00:03:29,880
But the bargain had an unspoken assumption that seeing a metric equaled understanding it.

80
00:03:29,880 --> 00:03:32,440
And that understanding it equaled acting on it.

81
00:03:32,440 --> 00:03:34,280
That distinction matters.

82
00:03:34,280 --> 00:03:35,520
Understanding is not a chart.

83
00:03:35,520 --> 00:03:38,240
Understanding is the combination of definition, context, and consequence.

84
00:03:38,240 --> 00:03:44,080
A revenue line dropping by 3% can mean seasonality, a pipeline timing artifact, a real churn event,

85
00:03:44,080 --> 00:03:48,440
a data refreshments, a pricing rollback, or an incident in the order system.

86
00:03:48,440 --> 00:03:50,080
The visual is the least important part.

87
00:03:50,080 --> 00:03:52,280
The decision implication is the entire point.

88
00:03:52,280 --> 00:03:54,960
Dashboards don't fail because they show the wrong number.

89
00:03:54,960 --> 00:03:57,320
They fail because they don't compile meaning.

90
00:03:57,320 --> 00:03:58,800
Most dashboards expose metrics.

91
00:03:58,800 --> 00:04:00,280
They don't bind them to decisions.

92
00:04:00,280 --> 00:04:04,280
They don't encode thresholds that matter, ownership that matters, and actions that matter.

93
00:04:04,280 --> 00:04:08,840
They assume the viewer will do that binding in their head in the moment, while also juggling

94
00:04:08,840 --> 00:04:12,560
a calendar full of meetings, and a team's chat full of fires.

95
00:04:12,560 --> 00:04:14,720
So organizations end up optimizing the wrong thing.

96
00:04:14,720 --> 00:04:20,480
They optimize output, more pages, more visuals, more drill paths, more slices, more self-service.

97
00:04:20,480 --> 00:04:24,040
They measure adoption, views, bookmarks, subscriptions, training attendance.

98
00:04:24,040 --> 00:04:26,280
All of that is instrumentation on the artifact.

99
00:04:26,280 --> 00:04:28,680
None of it measures whether anyone decided anything.

100
00:04:28,680 --> 00:04:30,040
The decision model is different.

101
00:04:30,040 --> 00:04:32,080
A decision is not knowing.

102
00:04:32,080 --> 00:04:35,920
A decision is commitment under uncertainty that requires confidence, which requires

103
00:04:35,920 --> 00:04:39,160
defensibility, and defensibility requires an evidence trail.

104
00:04:39,160 --> 00:04:40,480
What definition did you use?

105
00:04:40,480 --> 00:04:41,800
What data did you use?

106
00:04:41,800 --> 00:04:43,840
What changed and why you believe it?

107
00:04:43,840 --> 00:04:47,480
This is where the reporting model starts to rot, because the dashboard is a static surface

108
00:04:47,480 --> 00:04:49,200
sitting on top of a moving system.

109
00:04:49,200 --> 00:04:53,280
Data pipelines drift, definitions drift, security roads drift, business rules drift.

110
00:04:53,280 --> 00:04:55,680
Meanwhile the dashboard still looks like it always looked.

111
00:04:55,680 --> 00:05:00,560
Same tiles, same layout, same fake feeling of stability, and then people get surprised

112
00:05:00,560 --> 00:05:03,520
when the executive asks, "Can we trust this?"

113
00:05:03,520 --> 00:05:05,240
And the room goes quiet.

114
00:05:05,240 --> 00:05:06,560
Visibility never answered that question.

115
00:05:06,560 --> 00:05:07,560
They just hit it.

116
00:05:07,560 --> 00:05:10,040
If you want a cleaner way to say it, dashboard scale metrics.

117
00:05:10,040 --> 00:05:11,520
They don't scale judgment.

118
00:05:11,520 --> 00:05:13,440
Judgment is what executives pay for.

119
00:05:13,440 --> 00:05:17,920
Judgment is what they're actually asking for when they ask a human, "Is this real?"

120
00:05:17,920 --> 00:05:19,160
And what should we do?

121
00:05:19,160 --> 00:05:21,520
The data team here is, "What's the number?"

122
00:05:21,520 --> 00:05:23,480
Leadership is asking, "What's the move?"

123
00:05:23,480 --> 00:05:25,320
So the value reframe is brutal?

124
00:05:25,320 --> 00:05:29,160
The measure of a dashboard is not whether it is viewed, it is whether someone can decide

125
00:05:29,160 --> 00:05:30,160
with it.

126
00:05:30,160 --> 00:05:34,240
Right now, without a side conversation, without a DM2, the power BI person.

127
00:05:34,240 --> 00:05:37,080
Without three follow-up questions that trigger another meeting.

128
00:05:37,080 --> 00:05:40,600
If the dashboard requires a human escort, the dashboard is not the interface.

129
00:05:40,600 --> 00:05:42,160
The human is.

130
00:05:42,160 --> 00:05:44,680
And once you admit that, the rest becomes obvious.

131
00:05:44,680 --> 00:05:46,880
Dashboards depend on fragile assumptions about humans.

132
00:05:46,880 --> 00:05:51,360
Some attention, shared definitions, shared instincts and willingness to navigate.

133
00:05:51,360 --> 00:05:52,800
Those assumptions were always weak.

134
00:05:52,800 --> 00:05:55,720
The only reason they held was because the business tolerated latency.

135
00:05:55,720 --> 00:05:56,920
They don't anymore.

136
00:05:56,920 --> 00:05:58,720
So now we move to the real problem.

137
00:05:58,720 --> 00:06:02,400
What assumptions do dashboards quietly require from your organization?

138
00:06:02,400 --> 00:06:06,120
And why those assumptions collapse under modern pace?

139
00:06:06,120 --> 00:06:07,440
The hidden assumptions.

140
00:06:07,440 --> 00:06:08,960
Dashboards require.

141
00:06:08,960 --> 00:06:10,160
Dashboards aren't bad.

142
00:06:10,160 --> 00:06:11,760
They're expensive agreements.

143
00:06:11,760 --> 00:06:16,040
They only work if your organization implicitly agrees to behave a certain way, to ask predictable

144
00:06:16,040 --> 00:06:20,840
questions, to interpret numbers consistently, to make time for exploration, and to accept

145
00:06:20,840 --> 00:06:23,960
that the interface lives somewhere nobody actually works.

146
00:06:23,960 --> 00:06:25,280
That agreement used to hold.

147
00:06:25,280 --> 00:06:26,760
Now it breaks constantly.

148
00:06:26,760 --> 00:06:27,760
Assumption one.

149
00:06:27,760 --> 00:06:29,080
People have time to interpret.

150
00:06:29,080 --> 00:06:30,680
Not time in the abstract.

151
00:06:30,680 --> 00:06:31,680
Calendar time.

152
00:06:31,680 --> 00:06:32,680
Cognitive time.

153
00:06:32,680 --> 00:06:36,520
The empty mental bandwidth required to open a report, pick the right page, remember which

154
00:06:36,520 --> 00:06:42,440
slicers are safe to touch, figure out what changed, and then translate that into a decision.

155
00:06:42,440 --> 00:06:44,880
Dashboards assume a viewer sits down and explores.

156
00:06:44,880 --> 00:06:46,240
Modern leadership does not explore.

157
00:06:46,240 --> 00:06:47,320
Modern leadership interrupts.

158
00:06:47,320 --> 00:06:48,600
They ask in teams.

159
00:06:48,600 --> 00:06:50,040
They ask in the middle of a meeting.

160
00:06:50,040 --> 00:06:51,280
They ask between flights.

161
00:06:51,280 --> 00:06:53,240
They ask while walking into another call.

162
00:06:53,240 --> 00:06:54,800
A dashboard is a destination.

163
00:06:54,800 --> 00:06:56,360
The executive lives in transit.

164
00:06:56,360 --> 00:06:58,240
That mismatch is not a UX problem.

165
00:06:58,240 --> 00:06:59,960
It's an operating model problem.

166
00:06:59,960 --> 00:07:00,960
Assumption two.

167
00:07:00,960 --> 00:07:02,880
Everyone shares definitions.

168
00:07:02,880 --> 00:07:05,480
Dashboards quietly require a semantic consensus.

169
00:07:05,480 --> 00:07:06,480
Revenue means this.

170
00:07:06,480 --> 00:07:07,640
Churn means that.

171
00:07:07,640 --> 00:07:10,440
Active user is counted this way and the filters aren't hiding exclusions.

172
00:07:10,440 --> 00:07:11,640
Nobody remembers.

173
00:07:11,640 --> 00:07:14,660
When that consensus is real, a dashboard scales nicely.

174
00:07:14,660 --> 00:07:18,120
When that consensus is fake, dashboards become argument generators.

175
00:07:18,120 --> 00:07:22,200
The cruel part is that the dashboard can look correct while being semantically wrong.

176
00:07:22,200 --> 00:07:24,120
It can be perfectly rendered nonsense.

177
00:07:24,120 --> 00:07:26,180
The organization learns this the hard way.

178
00:07:26,180 --> 00:07:27,520
You get two reports.

179
00:07:27,520 --> 00:07:31,700
Both official, both built by competent people and they disagree by 7%.

180
00:07:31,700 --> 00:07:33,920
Now the conversation is no longer about the business.

181
00:07:33,920 --> 00:07:35,200
It's about whose number is real.

182
00:07:35,200 --> 00:07:37,860
At that point, the dashboard isn't a decision surface.

183
00:07:37,860 --> 00:07:38,860
It's litigation.

184
00:07:38,860 --> 00:07:39,940
Assumption three.

185
00:07:39,940 --> 00:07:47,060
The question space is stable.

186
00:07:47,060 --> 00:07:51,060
Dashboards assume a finite, pre-defineable set of questions.

187
00:07:51,060 --> 00:07:52,060
You build pages for those questions.

188
00:07:52,060 --> 00:07:53,060
You add drill parts for the common follow-ups.

189
00:07:53,060 --> 00:07:54,060
You ship, done.

190
00:07:54,060 --> 00:07:55,060
But the moment you answer one question, the business asks the next one and the next one is

191
00:07:55,060 --> 00:07:56,060
always slightly different.

192
00:07:56,060 --> 00:07:57,060
Different time frame.

193
00:07:57,060 --> 00:07:58,060
Different segment.

194
00:07:58,060 --> 00:07:59,060
Different exception.

195
00:07:59,060 --> 00:08:01,060
Different exclude the outliers.

196
00:08:01,060 --> 00:08:02,060
Different.

197
00:08:02,060 --> 00:08:03,060
What about just partner-led deals?

198
00:08:03,060 --> 00:08:04,060
Different.

199
00:08:04,060 --> 00:08:06,060
Show me only customers who renewed after a discount.

200
00:08:06,060 --> 00:08:09,260
Dashboards can answer that eventually if someone anticipates it and builds for it.

201
00:08:09,260 --> 00:08:10,580
But question drift is infinite.

202
00:08:10,580 --> 00:08:13,980
Your report backlog becomes a mirror of organizational anxiety.

203
00:08:13,980 --> 00:08:18,260
Every new dashboard is a fossil record of some executive panic that happened once and

204
00:08:18,260 --> 00:08:20,180
got immortalized as a page tab.

205
00:08:20,180 --> 00:08:21,660
Over time you don't get inside.

206
00:08:21,660 --> 00:08:23,140
You get clutter.

207
00:08:23,140 --> 00:08:24,140
Assumption four.

208
00:08:24,140 --> 00:08:25,300
The human is the real compute layer.

209
00:08:25,300 --> 00:08:26,780
This is the one no one says out loud.

210
00:08:26,780 --> 00:08:28,500
A dashboard is not the whole system.

211
00:08:28,500 --> 00:08:32,820
The system is data set, semantic layer, visuals and then a human who completes the computation

212
00:08:32,820 --> 00:08:34,540
by interpreting and narrating.

213
00:08:34,540 --> 00:08:36,020
The human is the query planner.

214
00:08:36,020 --> 00:08:37,700
The human is the anomaly detector.

215
00:08:37,700 --> 00:08:39,180
The human is the explainer.

216
00:08:39,180 --> 00:08:40,580
The human is the ethics layer.

217
00:08:40,580 --> 00:08:43,180
The human is the does this smell wrong, sensor.

218
00:08:43,180 --> 00:08:46,260
When the human isn't available, the dashboard doesn't degrade gracefully.

219
00:08:46,260 --> 00:08:49,020
It becomes a wall of numbers with no confidence rating.

220
00:08:49,020 --> 00:08:52,020
And because the human is doing that work, the work accumulates.

221
00:08:52,020 --> 00:08:53,260
Definitions meetings.

222
00:08:53,260 --> 00:08:54,620
Metric alignment workshops.

223
00:08:54,620 --> 00:08:55,900
One off exports.

224
00:08:55,900 --> 00:08:56,900
Back channel validation.

225
00:08:56,900 --> 00:08:57,900
Screen shot threads.

226
00:08:57,900 --> 00:09:01,020
The same five people answering the same three questions over and over.

227
00:09:01,020 --> 00:09:02,500
That's institutional work.

228
00:09:02,500 --> 00:09:04,340
And it compounds.

229
00:09:04,340 --> 00:09:05,140
Assumption five.

230
00:09:05,140 --> 00:09:06,860
The dashboard is where work happens.

231
00:09:06,860 --> 00:09:07,860
It isn't.

232
00:09:07,860 --> 00:09:10,300
Work happens in outlook teams, meetings, tickets and documents.

233
00:09:10,300 --> 00:09:14,100
Dashboards are where people go to justify a decision they already made or to prepare for

234
00:09:14,100 --> 00:09:16,860
a meeting where the decision gets made somewhere else.

235
00:09:16,860 --> 00:09:20,380
That's why dashboards get opened at 8.55 for a 9 o'clock meeting.

236
00:09:20,380 --> 00:09:23,060
They're props, not interfaces.

237
00:09:23,060 --> 00:09:26,380
So when you hear dashboards are dead, what that really means is this.

238
00:09:26,380 --> 00:09:30,060
The assumptions required for dashboards to be the primary interface, no longer hold at

239
00:09:30,060 --> 00:09:31,060
enterprise scale.

240
00:09:31,060 --> 00:09:35,300
The business doesn't have the patience, the shared semantics or the attention model.

241
00:09:35,300 --> 00:09:39,940
Now the obvious question is if dashboards required all that and still managed to work for a decade,

242
00:09:39,940 --> 00:09:43,140
what made reporting rational in the first place.

243
00:09:43,140 --> 00:09:45,980
Reporting was rational, cadence, constraint and control.

244
00:09:45,980 --> 00:09:46,980
Reporting wasn't a mistake.

245
00:09:46,980 --> 00:09:50,460
It was a rational response to the environment organizations used to live in.

246
00:09:50,460 --> 00:09:56,700
The business had a cadence month end quarter end forecast calls, board packs, budget cycles.

247
00:09:56,700 --> 00:10:00,220
And because the decision rhythm was periodic, the information rhythm could be periodic to

248
00:10:00,220 --> 00:10:01,660
you could batch the pain.

249
00:10:01,660 --> 00:10:04,260
You could accept that the numbers were as of yesterday.

250
00:10:04,260 --> 00:10:06,620
Because the decision window wasn't measured in minutes.

251
00:10:06,620 --> 00:10:09,780
It was measured in meetings you already scheduled three weeks ago.

252
00:10:09,780 --> 00:10:11,780
That cadence is the first reason reporting worked.

253
00:10:11,780 --> 00:10:13,500
The second reason is constraint.

254
00:10:13,500 --> 00:10:15,420
Dashboards weren't just a way to show data.

255
00:10:15,420 --> 00:10:18,740
They were a way to constrain what the organization was allowed to argue about.

256
00:10:18,740 --> 00:10:20,740
A good report narrows the question space.

257
00:10:20,740 --> 00:10:23,140
It says, "Here are the few metrics that matter.

258
00:10:23,140 --> 00:10:28,180
Define this way, add this grain, source from these systems, and refreshed on this schedule.

259
00:10:28,180 --> 00:10:31,820
Everything outside that boundary is explicitly not the topic of today's conversation.

260
00:10:31,820 --> 00:10:32,820
That sounds limiting."

261
00:10:32,820 --> 00:10:33,820
It was.

262
00:10:33,820 --> 00:10:35,180
It was also governance.

263
00:10:35,180 --> 00:10:38,340
Because when you constrain the question space, you can govern it.

264
00:10:38,340 --> 00:10:39,620
You can make it deterministic.

265
00:10:39,620 --> 00:10:40,620
You can audit it.

266
00:10:40,620 --> 00:10:41,620
You can defend it.

267
00:10:41,620 --> 00:10:45,340
You can go into a meeting and argue about business strategy instead of arguing about whether

268
00:10:45,340 --> 00:10:47,580
net revenue includes returns this week.

269
00:10:47,580 --> 00:10:50,780
The reporting era was built on a translation layer.

270
00:10:50,780 --> 00:10:54,500
Analysts and BI developers took messy operational systems and compiled them into something

271
00:10:54,500 --> 00:10:56,620
a human could process quickly.

272
00:10:56,620 --> 00:10:57,980
That translation was not decorative.

273
00:10:57,980 --> 00:10:58,980
It was the product.

274
00:10:58,980 --> 00:11:00,140
They cleaned data.

275
00:11:00,140 --> 00:11:01,660
They normalized definitions.

276
00:11:01,660 --> 00:11:02,660
They wrote measures.

277
00:11:02,660 --> 00:11:03,660
They made trade-offs.

278
00:11:03,660 --> 00:11:06,500
They decided what the org would see and what it wouldn't.

279
00:11:06,500 --> 00:11:09,660
And in the old model, that was exactly what leadership wanted.

280
00:11:09,660 --> 00:11:12,020
Because leadership didn't want the entire data lake.

281
00:11:12,020 --> 00:11:15,660
Leadership wanted a small, governed surface area they could treat as real.

282
00:11:15,660 --> 00:11:19,340
One pane of glass, even if it was an illusion, one official truth surface.

283
00:11:19,340 --> 00:11:22,500
That's also why semantic models mattered long before AI showed up.

284
00:11:22,500 --> 00:11:24,620
A semantic model is not a power BI feature.

285
00:11:24,620 --> 00:11:26,140
It's an organizational contract.

286
00:11:26,140 --> 00:11:30,220
It's the place where you stop pretending raw tables have meaning, and you explicitly define

287
00:11:30,220 --> 00:11:31,220
it.

288
00:11:31,220 --> 00:11:32,220
Sales.

289
00:11:32,220 --> 00:11:35,700
It's the place where you stop pretending raw tables have meaning, and you simply define

290
00:11:35,700 --> 00:11:36,700
it.

291
00:11:36,700 --> 00:11:38,700
And then the data structure was created.

292
00:11:38,700 --> 00:11:39,700
And then the data structure was created.

293
00:11:39,700 --> 00:11:40,700
And then the data structure was created.

294
00:11:40,700 --> 00:11:41,700
And then the data structure was created.

295
00:11:41,700 --> 00:11:42,700
And then the data structure was created.

296
00:11:42,700 --> 00:11:43,700
And then the data structure was created.

297
00:11:43,700 --> 00:11:44,700
And then the data structure was created.

298
00:11:44,700 --> 00:11:45,700
And then the data structure was created.

299
00:11:45,700 --> 00:11:46,700
And then the data structure was created.

300
00:11:46,700 --> 00:11:47,700
And then the data structure was created.

301
00:11:47,700 --> 00:11:48,700
And then the data structure was created.

302
00:11:48,700 --> 00:11:49,700
And then the data structure was created.

303
00:11:49,700 --> 00:11:50,700
And then the data structure was created.

304
00:11:50,700 --> 00:11:51,700
And then the data structure was created.

305
00:11:51,700 --> 00:11:52,700
And then the data structure was created.

306
00:11:52,700 --> 00:11:53,700
And then the data structure was created.

307
00:11:53,700 --> 00:11:54,700
And then the data structure was created.

308
00:11:54,700 --> 00:11:55,700
And then the data structure was created.

309
00:11:55,700 --> 00:11:56,700
And then the data structure was created.

310
00:11:56,700 --> 00:12:08,180
And then the data structure was created.

311
00:12:08,180 --> 00:12:10,180
And then the data structure was created.

312
00:12:10,180 --> 00:12:11,180
And then the data structure was created.

313
00:12:11,180 --> 00:12:12,180
And then the data structure was created.

314
00:12:12,180 --> 00:12:13,180
And then the data structure was created.

315
00:12:13,180 --> 00:12:14,180
And then the data structure was created.

316
00:12:14,180 --> 00:12:15,180
And then the data structure was created.

317
00:12:15,180 --> 00:12:16,180
And then the data structure was created.

318
00:12:16,180 --> 00:12:17,180
And then the data structure was created.

319
00:12:17,180 --> 00:12:18,180
And then the data structure was created.

320
00:12:18,180 --> 00:12:19,180
And then the data structure was created.

321
00:12:19,180 --> 00:12:20,180
And then the data structure was created.

322
00:12:20,180 --> 00:12:21,180
And then the data structure was created.

323
00:12:21,180 --> 00:12:22,180
And then the data structure was created.

324
00:12:22,180 --> 00:12:23,180
And then the data structure was created.

325
00:12:23,180 --> 00:12:24,180
And then the data structure was created.

326
00:12:24,180 --> 00:12:25,180
And then the data structure was created.

327
00:12:25,180 --> 00:12:26,180
And then the data structure was created.

328
00:12:26,180 --> 00:12:29,020
Last Tuesday, that worked because the system assumed

329
00:12:29,020 --> 00:12:31,740
those humans were available at the speed the organization

330
00:12:31,740 --> 00:12:32,540
operated.

331
00:12:32,540 --> 00:12:33,740
And for a long time, they were.

332
00:12:33,740 --> 00:12:35,780
So when people dunk on dashboards as if they were always

333
00:12:35,780 --> 00:12:37,900
pointless, they're missing the real story.

334
00:12:37,900 --> 00:12:39,740
Dashboards were the only scalable interface

335
00:12:39,740 --> 00:12:42,020
for an organization that needed constrained periodic

336
00:12:42,020 --> 00:12:43,180
defensible visibility.

337
00:12:43,180 --> 00:12:44,260
But wait, it gets worse.

338
00:12:44,260 --> 00:12:46,780
The thing that broke first wasn't BI quality.

339
00:12:46,780 --> 00:12:49,180
It wasn't that people forgot how to build a star schema.

340
00:12:49,180 --> 00:12:51,700
It wasn't that power BI couldn't render enough tiles.

341
00:12:51,700 --> 00:12:52,900
What broke was the pace.

342
00:12:52,900 --> 00:12:54,860
When the business moved from cadence to interrupts,

343
00:12:54,860 --> 00:12:56,740
the reporting model didn't fail.

344
00:12:56,740 --> 00:12:59,820
It became an architecture built for the wrong time domain.

345
00:12:59,820 --> 00:13:00,620
What broke?

346
00:13:00,620 --> 00:13:02,900
Speed, scope, and trust all at once.

347
00:13:02,900 --> 00:13:05,540
Three things broke at the same time and that timing matters.

348
00:13:05,540 --> 00:13:07,620
Most organizations want to blame one thing.

349
00:13:07,620 --> 00:13:08,700
They want a single villain.

350
00:13:08,700 --> 00:13:10,460
The data team didn't govern enough.

351
00:13:10,460 --> 00:13:11,620
Users didn't adopt.

352
00:13:11,620 --> 00:13:12,700
The tool was too complex.

353
00:13:12,700 --> 00:13:13,980
The refresh was too slow.

354
00:13:13,980 --> 00:13:16,860
But dashboards didn't lose relevance because of one failure.

355
00:13:16,860 --> 00:13:18,620
They lost relevance because the environment

356
00:13:18,620 --> 00:13:20,740
changed on three axes simultaneously.

357
00:13:20,740 --> 00:13:23,220
Speed, scope, and trust.

358
00:13:23,220 --> 00:13:24,500
First, speed.

359
00:13:24,500 --> 00:13:26,900
The business moved from weekly and monthly decision cycles

360
00:13:26,900 --> 00:13:28,580
to daily and hourly ones.

361
00:13:28,580 --> 00:13:30,740
Not because executives suddenly became impatient

362
00:13:30,740 --> 00:13:34,340
as a personality flaw, because the operating surface changed.

363
00:13:34,340 --> 00:13:37,700
Digital channels, subscription revenue, supply chain volatility,

364
00:13:37,700 --> 00:13:41,460
fraud, pricing experiments, incident-driven customer experience,

365
00:13:41,460 --> 00:13:44,940
the feedback loop tightened, and dashboards stayed batch.

366
00:13:44,940 --> 00:13:46,860
Even when the refresh is near real time,

367
00:13:46,860 --> 00:13:48,420
the decision pathway is still slow.

368
00:13:48,420 --> 00:13:49,420
Someone has to notice.

369
00:13:49,420 --> 00:13:50,540
Someone has to interpret it.

370
00:13:50,540 --> 00:13:51,580
Someone has to validate.

371
00:13:51,580 --> 00:13:53,340
Someone has to explain it to someone else.

372
00:13:53,340 --> 00:13:55,780
That chain is latency, and it's not measured in data

373
00:13:55,780 --> 00:13:57,140
set refresh intervals.

374
00:13:57,140 --> 00:13:58,660
It's measured in calendar hours.

375
00:13:58,660 --> 00:14:01,540
The ugly truth is that a dashboard can refresh every five minutes

376
00:14:01,540 --> 00:14:04,140
and still be useless if the decision takes two days,

377
00:14:04,140 --> 00:14:06,940
because people don't trust it or don't know what to do with it.

378
00:14:06,940 --> 00:14:08,780
Second, scope.

379
00:14:08,780 --> 00:14:11,060
The question space exploded.

380
00:14:11,060 --> 00:14:13,020
A dashboard is built on pre-definition.

381
00:14:13,020 --> 00:14:15,580
You choose metrics, slices, levels of detail,

382
00:14:15,580 --> 00:14:17,580
and drill parts ahead of time that works

383
00:14:17,580 --> 00:14:19,300
when the business questions are stable

384
00:14:19,300 --> 00:14:21,060
and the org agrees on what matters.

385
00:14:21,060 --> 00:14:23,220
Modern organizations don't agree on what matters

386
00:14:23,220 --> 00:14:24,740
for more than a quarter.

387
00:14:24,740 --> 00:14:27,460
They don't even agree on what matters for more than a meeting.

388
00:14:27,460 --> 00:14:29,260
Every answer creates follow-ups.

389
00:14:29,260 --> 00:14:31,180
Every follow-up changes the grain.

390
00:14:31,180 --> 00:14:33,740
Every grain changes crosses a domain boundary.

391
00:14:33,740 --> 00:14:36,660
You start in revenue and end in customer success notes.

392
00:14:36,660 --> 00:14:39,340
You start in churn and end in product incident timelines.

393
00:14:39,340 --> 00:14:42,260
You start in what happened and end in who changed the policy.

394
00:14:42,260 --> 00:14:44,140
Dashboards don't do cross-domain reasoning.

395
00:14:44,140 --> 00:14:45,460
They do cross-filtering.

396
00:14:45,460 --> 00:14:48,380
So what organizations did predictably was multiply dashboards,

397
00:14:48,380 --> 00:14:50,860
a dashboard for sales, a dashboard for attention,

398
00:14:50,860 --> 00:14:52,260
a dashboard for pipeline hygiene,

399
00:14:52,260 --> 00:14:54,140
a dashboard for marketing attribution,

400
00:14:54,140 --> 00:14:56,100
a dashboard for customer escalations,

401
00:14:56,100 --> 00:14:57,860
a dashboard for exact summary.

402
00:14:57,860 --> 00:14:59,020
That's not maturity.

403
00:14:59,020 --> 00:15:00,140
That's entropy.

404
00:15:00,140 --> 00:15:03,060
Because each new dashboard is a new semantic surface area

405
00:15:03,060 --> 00:15:05,740
to govern, a new set of measures to maintain,

406
00:15:05,740 --> 00:15:08,100
a new set of RLS rules to explain,

407
00:15:08,100 --> 00:15:10,300
a new set of definitions to reconcile,

408
00:15:10,300 --> 00:15:12,660
and a new place where someone can screenshot a number

409
00:15:12,660 --> 00:15:14,740
out of context and cause a fire.

410
00:15:14,740 --> 00:15:16,820
And then leadership asks the most revealing question

411
00:15:16,820 --> 00:15:19,380
in the modern era, who owns this metric?

412
00:15:19,380 --> 00:15:20,940
That question is not about the number.

413
00:15:20,940 --> 00:15:22,940
It's about accountability.

414
00:15:22,940 --> 00:15:24,020
Third, trust.

415
00:15:24,020 --> 00:15:26,700
Trust didn't collapse because people suddenly became irrational.

416
00:15:26,700 --> 00:15:28,060
Trust collapsed because metrics

417
00:15:28,060 --> 00:15:30,060
brawled made contradictions inevitable.

418
00:15:30,060 --> 00:15:31,420
The more dashboards you ship,

419
00:15:31,420 --> 00:15:33,740
the more versions of truth you create.

420
00:15:33,740 --> 00:15:35,900
And once leaders catch you with two different answers

421
00:15:35,900 --> 00:15:38,780
to the same question, they don't just distrust those two dashboards.

422
00:15:38,780 --> 00:15:40,020
They distrust the system.

423
00:15:40,020 --> 00:15:43,660
This is the difference between a missing policy and a drifting policy.

424
00:15:43,660 --> 00:15:45,460
A missing policy creates an obvious gap.

425
00:15:45,460 --> 00:15:47,500
A drifting policy creates ambiguity.

426
00:15:47,500 --> 00:15:50,300
Amiguity is worse because it generates decision paralysis.

427
00:15:50,300 --> 00:15:52,180
It turns every meeting into a debate

428
00:15:52,180 --> 00:15:54,020
about whether the data is real

429
00:15:54,020 --> 00:15:56,500
and then the data team becomes a courtrooms stenographer

430
00:15:56,500 --> 00:15:58,020
instead of a decision engine.

431
00:15:58,020 --> 00:15:59,420
So here's the cycle.

432
00:15:59,420 --> 00:16:01,460
Speed compresses decision windows.

433
00:16:01,460 --> 00:16:03,780
Therefore, the dashboard workflow becomes too slow.

434
00:16:03,780 --> 00:16:05,500
Scope explodes the question space,

435
00:16:05,500 --> 00:16:08,100
therefore pre-built canvas is becoming complete.

436
00:16:08,100 --> 00:16:09,820
Trust collapses under metrics brawl,

437
00:16:09,820 --> 00:16:12,940
therefore self-service becomes self-incrimination.

438
00:16:12,940 --> 00:16:14,460
And when those three hit at once,

439
00:16:14,460 --> 00:16:17,940
the system does what systems always do, under stress.

440
00:16:17,940 --> 00:16:20,460
It roots around the interface. It goes back to humans.

441
00:16:20,460 --> 00:16:22,220
That's why executives escalate.

442
00:16:22,220 --> 00:16:25,620
They stop asking what's the number and start asking who owns it?

443
00:16:25,620 --> 00:16:27,220
And can you stand behind it?

444
00:16:27,220 --> 00:16:29,180
They're trying to restore determinism

445
00:16:29,180 --> 00:16:30,980
in a probabilistic environment.

446
00:16:30,980 --> 00:16:32,740
Meanwhile, the actual work of the company

447
00:16:32,740 --> 00:16:35,900
moved into team's threads and meeting recaps and ticket queues.

448
00:16:35,900 --> 00:16:38,100
So the data interface, being a separate web app

449
00:16:38,100 --> 00:16:39,700
with a separate navigation model,

450
00:16:39,700 --> 00:16:41,420
became a kind of organizational joke.

451
00:16:41,420 --> 00:16:42,220
It's not malicious.

452
00:16:42,220 --> 00:16:43,780
It's just irrelevant.

453
00:16:43,780 --> 00:16:47,060
And once latency becomes intolerable, the interface shifts.

454
00:16:47,060 --> 00:16:48,500
Not because dashboards are ugly,

455
00:16:48,500 --> 00:16:50,700
because the business can't afford the delay anymore.

456
00:16:50,700 --> 00:16:52,540
The modern business environment interrupts,

457
00:16:52,540 --> 00:16:54,020
drift and zero patience.

458
00:16:54,020 --> 00:16:56,580
Modern organizations don't run on review sessions anymore.

459
00:16:56,580 --> 00:16:57,620
They run on interrupts.

460
00:16:57,620 --> 00:16:59,780
The decision room isn't a conference room

461
00:16:59,780 --> 00:17:01,340
with a dashboard on the wall.

462
00:17:01,340 --> 00:17:03,380
It's a team's thread with three time zones,

463
00:17:03,380 --> 00:17:05,380
a meeting recap, nobody fully read,

464
00:17:05,380 --> 00:17:07,060
an email forwarded without context,

465
00:17:07,060 --> 00:17:09,060
and a ticket queue that quietly holds the truth.

466
00:17:09,060 --> 00:17:10,780
That's where work actually happens.

467
00:17:10,780 --> 00:17:12,220
That's where the pressure shows up.

468
00:17:12,220 --> 00:17:14,020
And that's where the question gets asked.

469
00:17:14,020 --> 00:17:17,340
Not as a request for a chart, but as a demand for a move.

470
00:17:17,340 --> 00:17:18,980
This is the uncomfortable truth.

471
00:17:18,980 --> 00:17:20,860
Dashboards are built like destinations.

472
00:17:20,860 --> 00:17:22,500
Modern work is built like a stream.

473
00:17:22,500 --> 00:17:24,460
So people stop traveling to the dashboard.

474
00:17:24,460 --> 00:17:26,180
They pull the question into the stream.

475
00:17:26,180 --> 00:17:27,220
They ask it where they are.

476
00:17:27,220 --> 00:17:29,980
They ask it in chat in the meeting in the dock they're editing

477
00:17:29,980 --> 00:17:31,980
and in the inbox that's already on fire.

478
00:17:31,980 --> 00:17:33,220
That is not user laziness.

479
00:17:33,220 --> 00:17:36,380
That is the natural behavior of a system optimizing for time.

480
00:17:36,380 --> 00:17:38,140
And then there's drift, not data drift

481
00:17:38,140 --> 00:17:40,260
in the machine learning sense, question drift,

482
00:17:40,260 --> 00:17:43,300
organizational drift, the constant low grade mutation

483
00:17:43,300 --> 00:17:44,980
of what the business actually wants to know.

484
00:17:44,980 --> 00:17:48,140
You can ship a dashboard that answers what is email revenue

485
00:17:48,140 --> 00:17:49,380
and you can even make it pretty.

486
00:17:49,380 --> 00:17:53,300
But the next question is, never what is email revenue?

487
00:17:53,300 --> 00:17:54,900
It's why did it change since Tuesday?

488
00:17:54,900 --> 00:17:57,700
Then is that tied to the discount program?

489
00:17:57,700 --> 00:18:00,940
Then it's exclude the partner deals because those are lagging.

490
00:18:00,940 --> 00:18:03,420
Then it's who approved the pricing exception.

491
00:18:03,420 --> 00:18:05,780
Then it's which accounts are at risk next week.

492
00:18:05,780 --> 00:18:07,060
That's not a dashboard problem.

493
00:18:07,060 --> 00:18:08,900
That's the natural shape of decision making.

494
00:18:08,900 --> 00:18:11,300
One answer spawns another question immediately.

495
00:18:11,300 --> 00:18:13,860
Dashboards were never designed for infinite follow ups.

496
00:18:13,860 --> 00:18:17,540
They were designed for finite pre-approved exploration.

497
00:18:17,540 --> 00:18:20,140
When you try to stretch that model to match real decision

498
00:18:20,140 --> 00:18:21,820
behavior, you get a familiar pattern.

499
00:18:21,820 --> 00:18:24,020
More pages, more drill-throughs, more slices,

500
00:18:24,020 --> 00:18:26,580
more executive summary tabs that are just

501
00:18:26,580 --> 00:18:28,540
the same metrics with bigger fonts.

502
00:18:28,540 --> 00:18:31,140
That's not scaling, that's coping.

503
00:18:31,140 --> 00:18:34,180
Now, layer in the third factor, zero patients.

504
00:18:34,180 --> 00:18:37,140
And to be clear, zero patients isn't the personality defect.

505
00:18:37,140 --> 00:18:39,660
It's a consequence of operating at higher velocity

506
00:18:39,660 --> 00:18:41,140
under higher accountability.

507
00:18:41,140 --> 00:18:43,540
Leaders don't have time to interpret a canvas

508
00:18:43,540 --> 00:18:45,980
because the organization punishes slow decisions

509
00:18:45,980 --> 00:18:47,660
more than it punishes imperfect ones.

510
00:18:47,660 --> 00:18:50,740
So they optimize for speed and they outsource the interpretation

511
00:18:50,740 --> 00:18:52,580
step to whoever can collapse it fastest.

512
00:18:52,580 --> 00:18:54,740
That's why the human becomes the interface again,

513
00:18:54,740 --> 00:18:57,540
the analyst, the finance lead, the operations manager.

514
00:18:57,540 --> 00:18:59,700
Whoever can answer with confidence in context,

515
00:18:59,700 --> 00:19:01,660
meanwhile, dashboards keep multiplying.

516
00:19:01,660 --> 00:19:03,660
And dashboard multiplication is not growth.

517
00:19:03,660 --> 00:19:05,020
It's entropy generation.

518
00:19:05,020 --> 00:19:07,860
Every new report creates a new semantic surface area.

519
00:19:07,860 --> 00:19:11,220
Every semantic surface area needs a definition, an owner,

520
00:19:11,220 --> 00:19:13,740
a refresh contract, a security model,

521
00:19:13,740 --> 00:19:16,100
and a reconciliation story when someone else's report

522
00:19:16,100 --> 00:19:17,020
disagrees.

523
00:19:17,020 --> 00:19:19,060
Over time, you are no longer building inside.

524
00:19:19,060 --> 00:19:21,060
You are building a museum of exceptions.

525
00:19:21,060 --> 00:19:23,140
And as entropy rises, the organization

526
00:19:23,140 --> 00:19:25,580
adapts in the most predictable way possible.

527
00:19:25,580 --> 00:19:27,700
It ignores the artifacts and roots around them.

528
00:19:27,700 --> 00:19:29,620
It starts asking, what's the real number?

529
00:19:29,620 --> 00:19:31,860
It starts asking, which report is the one we trust?

530
00:19:31,860 --> 00:19:33,860
And it starts asking, who owns this definition?

531
00:19:33,860 --> 00:19:35,700
As that's the moment the dashboard

532
00:19:35,700 --> 00:19:38,420
stops being a decision tool and becomes a political liability.

533
00:19:38,420 --> 00:19:40,500
So the modern environment does three things at once.

534
00:19:40,500 --> 00:19:42,980
It moves work into conversational surfaces.

535
00:19:42,980 --> 00:19:45,460
It increases question drift until pre-built canvases

536
00:19:45,460 --> 00:19:46,420
can't keep up.

537
00:19:46,420 --> 00:19:48,940
And it reduces tolerance for latency to almost zero.

538
00:19:48,940 --> 00:19:51,340
That combination doesn't challenge dashboards.

539
00:19:51,340 --> 00:19:52,540
It makes them optional.

540
00:19:52,540 --> 00:19:53,860
And once dashboards are optional,

541
00:19:53,860 --> 00:19:56,380
they lose the only thing they ever had, monopoly

542
00:19:56,380 --> 00:19:57,380
over attention.

543
00:19:57,380 --> 00:19:59,940
So if you want the metric that actually matters now,

544
00:19:59,940 --> 00:20:01,140
it's not usage.

545
00:20:01,140 --> 00:20:01,900
It's not adoption.

546
00:20:01,900 --> 00:20:03,980
It's not how many people bookmark the report.

547
00:20:03,980 --> 00:20:05,660
It's time from question to action.

548
00:20:05,660 --> 00:20:07,700
Because when decision latency becomes the bottleneck,

549
00:20:07,700 --> 00:20:09,980
the interface will change to whatever collapses latency

550
00:20:09,980 --> 00:20:11,060
the fastest.

551
00:20:11,060 --> 00:20:13,180
And that is exactly what is happening.

552
00:20:13,180 --> 00:20:15,700
The interface shift from canvases to intent,

553
00:20:15,700 --> 00:20:17,060
here's what people get wrong about.

554
00:20:17,060 --> 00:20:18,700
The dashboards are dead claim.

555
00:20:18,700 --> 00:20:20,620
They hear it as a design critique.

556
00:20:20,620 --> 00:20:22,540
Like the problem is layout or load time,

557
00:20:22,540 --> 00:20:24,620
or whether the CEO prefers dark mode.

558
00:20:24,620 --> 00:20:26,420
That's comforting because it keeps the problem

559
00:20:26,420 --> 00:20:29,540
in the UI layer where you can buy a new tool, run a training,

560
00:20:29,540 --> 00:20:30,740
and call it transformation.

561
00:20:30,740 --> 00:20:32,220
In reality, it is something else.

562
00:20:32,220 --> 00:20:34,140
The interface didn't get better.

563
00:20:34,140 --> 00:20:35,340
The interface moved.

564
00:20:35,340 --> 00:20:36,940
Dashboards are canvases.

565
00:20:36,940 --> 00:20:38,500
Canvases assume navigation.

566
00:20:38,500 --> 00:20:41,100
They assume a human will arrive at the right artifact,

567
00:20:41,100 --> 00:20:43,700
choose the right page, manipulate the right filters,

568
00:20:43,700 --> 00:20:46,380
interpret the right visual, and then translate that

569
00:20:46,380 --> 00:20:47,420
into a decision.

570
00:20:47,420 --> 00:20:48,540
That's not analytics.

571
00:20:48,540 --> 00:20:50,060
That's choreography.

572
00:20:50,060 --> 00:20:52,340
And choreography collapses under pressure.

573
00:20:52,340 --> 00:20:54,220
When decision windows compress, the organization

574
00:20:54,220 --> 00:20:57,220
stops tolerating navigation as a prerequisite for truth.

575
00:20:57,220 --> 00:20:59,540
So the system shifts the input mechanism

576
00:20:59,540 --> 00:21:02,900
from find the right canvas to state your intent.

577
00:21:02,900 --> 00:21:05,580
That's the interface shift from canvases to intent.

578
00:21:05,580 --> 00:21:07,620
Intent means the user doesn't express steps.

579
00:21:07,620 --> 00:21:09,180
They express the outcome they need.

580
00:21:09,180 --> 00:21:10,380
Why did revenue dip?

581
00:21:10,380 --> 00:21:12,220
What changed since Tuesday?

582
00:21:12,220 --> 00:21:13,700
Which accounts are at risk?

583
00:21:13,700 --> 00:21:15,420
What decisions does this impact?

584
00:21:15,420 --> 00:21:16,780
Those are not requests for visuals.

585
00:21:16,780 --> 00:21:18,660
They are requests for an assembled response.

586
00:21:18,660 --> 00:21:20,300
And you already see this behavior everywhere.

587
00:21:20,300 --> 00:21:22,100
People don't open a dashboard and explore

588
00:21:22,100 --> 00:21:23,540
until they feel smart.

589
00:21:23,540 --> 00:21:25,340
They ping a human and ask a question,

590
00:21:25,340 --> 00:21:28,580
because the question is the natural unit of work.

591
00:21:28,580 --> 00:21:32,180
Not the page, not the tile, not the report.

592
00:21:32,180 --> 00:21:34,820
So when AI shows up with a conversational surface,

593
00:21:34,820 --> 00:21:36,460
it doesn't replace dashboards.

594
00:21:36,460 --> 00:21:38,140
It replaces navigation.

595
00:21:38,140 --> 00:21:39,660
That distinction matters.

596
00:21:39,660 --> 00:21:42,420
Because most organizations treat navigation as harmless.

597
00:21:42,420 --> 00:21:43,860
They treat it like a minor tax.

598
00:21:43,860 --> 00:21:46,780
Click here, drill there, slice this, export that.

599
00:21:46,780 --> 00:21:48,420
But navigation is latency.

600
00:21:48,420 --> 00:21:49,860
Navigation is cognitive load.

601
00:21:49,860 --> 00:21:52,420
Navigation is where definitions get misapplied.

602
00:21:52,420 --> 00:21:53,900
And where users accidentally answer

603
00:21:53,900 --> 00:21:55,620
the wrong question with high confidence.

604
00:21:55,620 --> 00:21:58,580
Once the question becomes the UI, the interpretation burden

605
00:21:58,580 --> 00:21:59,500
shifts.

606
00:21:59,500 --> 00:22:01,900
In the dashboard era, the viewer carries the burden.

607
00:22:01,900 --> 00:22:04,060
They interpret, they contextualize, they decide

608
00:22:04,060 --> 00:22:06,380
whether it's real, they explain it to someone else.

609
00:22:06,380 --> 00:22:08,220
That makes every leader a part-time analyst,

610
00:22:08,220 --> 00:22:09,820
and it makes every decision dependent

611
00:22:09,820 --> 00:22:11,580
on who happens to be in the meeting.

612
00:22:11,580 --> 00:22:14,500
In the intent era, the system carries more of that burden.

613
00:22:14,500 --> 00:22:17,780
It chooses the data sources, runs the queries, summarizes

614
00:22:17,780 --> 00:22:19,580
the result, and returns the answer

615
00:22:19,580 --> 00:22:21,900
with enough explanation that you can defend it.

616
00:22:21,900 --> 00:22:24,220
Not because AI is magical, because the system is now

617
00:22:24,220 --> 00:22:26,260
designed to compile meaning, not display pixels.

618
00:22:26,260 --> 00:22:29,340
And yes, this is where people start panicking about hallucinations

619
00:22:29,340 --> 00:22:30,300
and governance.

620
00:22:30,300 --> 00:22:32,580
And we can't let users just ask questions.

621
00:22:32,580 --> 00:22:34,500
Good, that panic is the correct instinct.

622
00:22:34,500 --> 00:22:37,700
Because if you treat question as interface like a UX trend,

623
00:22:37,700 --> 00:22:39,540
you'll ship conditional chaos.

624
00:22:39,540 --> 00:22:41,260
A probabilistic answer engine sitting

625
00:22:41,260 --> 00:22:43,420
on top of inconsistent data semantics

626
00:22:43,420 --> 00:22:45,100
and eroded access controls.

627
00:22:45,100 --> 00:22:46,700
You don't get faster decisions.

628
00:22:46,700 --> 00:22:48,260
You get faster misinformation.

629
00:22:48,260 --> 00:22:49,860
So the interface shift has a price.

630
00:22:49,860 --> 00:22:51,860
The price is that you must formalize intent.

631
00:22:51,860 --> 00:22:54,380
You must define what questions are legitimate, what data

632
00:22:54,380 --> 00:22:57,260
contracts back them, what evidence trail must be attached,

633
00:22:57,260 --> 00:22:59,180
and what permissions gate the answer.

634
00:22:59,180 --> 00:23:00,940
The old interface hid those requirements

635
00:23:00,940 --> 00:23:03,180
behind a dashboard publishing workflow.

636
00:23:03,180 --> 00:23:06,740
The new interface exposes them, because it lets anyone ask anything,

637
00:23:06,740 --> 00:23:09,100
which means you need a control plane for questions.

638
00:23:09,100 --> 00:23:10,140
Not for reports.

639
00:23:10,140 --> 00:23:12,700
And that control plane is not a chatbot prompt template.

640
00:23:12,700 --> 00:23:15,260
It's the combination of semantic definition, identity

641
00:23:15,260 --> 00:23:17,980
enforcement and traceability that turns a question

642
00:23:17,980 --> 00:23:19,700
into a defensible answer.

643
00:23:19,700 --> 00:23:21,420
This is why the most important change

644
00:23:21,420 --> 00:23:23,820
isn't that users can type in English.

645
00:23:23,820 --> 00:23:25,860
The most important change is that the system now

646
00:23:25,860 --> 00:23:28,020
has to decide what the question means.

647
00:23:28,020 --> 00:23:29,500
That's a compiler problem.

648
00:23:29,500 --> 00:23:32,460
And if you don't build the compiler, semantic layer,

649
00:23:32,460 --> 00:23:34,620
security boundaries, govern sources,

650
00:23:34,620 --> 00:23:36,020
then the system will still answer.

651
00:23:36,020 --> 00:23:37,260
It just won't be your truth.

652
00:23:37,260 --> 00:23:39,380
So yes, dashboards are losing attention.

653
00:23:39,380 --> 00:23:41,180
But the deeper reality is harsher.

654
00:23:41,180 --> 00:23:42,900
You're watching a control plane migration.

655
00:23:42,900 --> 00:23:45,180
From a canvas-centric world where a human supplied

656
00:23:45,180 --> 00:23:47,540
interpretation to an intent-centric world

657
00:23:47,540 --> 00:23:49,980
where systems must supply interpretation,

658
00:23:49,980 --> 00:23:52,540
next comes the technical shift that made this possible

659
00:23:52,540 --> 00:23:54,620
and why it's not optional anymore.

660
00:23:54,620 --> 00:23:57,980
Questions became the interface, what changed technically.

661
00:23:57,980 --> 00:24:00,540
When people say natural language changed BI,

662
00:24:00,540 --> 00:24:02,780
they usually mean you can type a question and get a chat.

663
00:24:02,780 --> 00:24:03,620
That's not the change.

664
00:24:03,620 --> 00:24:06,580
The change is that the system stopped treating the dashboard

665
00:24:06,580 --> 00:24:08,220
as the primary interaction surface

666
00:24:08,220 --> 00:24:11,340
and started treating intent as the input to the control plane.

667
00:24:11,340 --> 00:24:13,660
In architectural terms, the interface moved from navigation

668
00:24:13,660 --> 00:24:14,900
to compilation.

669
00:24:14,900 --> 00:24:18,980
A dashboard workflow is deterministic in a narrow way.

670
00:24:18,980 --> 00:24:21,340
You choose the dataset, you choose the page,

671
00:24:21,340 --> 00:24:24,140
you choose the slicer values and the visuals update.

672
00:24:24,140 --> 00:24:25,620
The system isn't deciding anything.

673
00:24:25,620 --> 00:24:28,540
It's rendering what you already specified through clicks.

674
00:24:28,540 --> 00:24:30,500
A question-driven workflow flips that.

675
00:24:30,500 --> 00:24:33,620
You provide intent and the system chooses steps,

676
00:24:33,620 --> 00:24:36,060
which sources to touch, which measures to use,

677
00:24:36,060 --> 00:24:38,940
what joins to perform, what time frame is implied,

678
00:24:38,940 --> 00:24:43,140
what exceptions are normal and what to surface as the answer.

679
00:24:43,140 --> 00:24:45,580
That isn't visualization, that's orchestration.

680
00:24:45,580 --> 00:24:47,860
And the orchestration requires a few technical shifts

681
00:24:47,860 --> 00:24:49,220
that weren't optional before.

682
00:24:49,220 --> 00:24:52,300
First, natural language became a control plane primitive.

683
00:24:52,300 --> 00:24:53,660
Not a query language replacement,

684
00:24:53,660 --> 00:24:55,540
but a declaration of desired output.

685
00:24:55,540 --> 00:24:57,820
The system takes your sentence and builds a plan.

686
00:24:57,820 --> 00:25:00,140
Identify entities, map them to governed concepts,

687
00:25:00,140 --> 00:25:03,820
select the correct semantic layer, generate executable queries,

688
00:25:03,820 --> 00:25:07,580
and then format a response that fits the user's role and context.

689
00:25:07,580 --> 00:25:10,260
That means the question interface isn't a UI feature.

690
00:25:10,260 --> 00:25:13,060
It's an authorization and query compilation pipeline.

691
00:25:13,060 --> 00:25:15,820
Second, context-aware querying became mandatory.

692
00:25:15,820 --> 00:25:19,060
The same question cannot produce the same answer for every person

693
00:25:19,060 --> 00:25:20,980
because every person has different permissions,

694
00:25:20,980 --> 00:25:23,100
different scope and different work contexts.

695
00:25:23,100 --> 00:25:25,780
In the dashboard era, people pretended this was simple

696
00:25:25,780 --> 00:25:28,300
because you could publish different reports or apply RLS

697
00:25:28,300 --> 00:25:29,260
and call it done.

698
00:25:29,260 --> 00:25:31,940
In the question era, the system must decide in real time

699
00:25:31,940 --> 00:25:34,180
what truth surface you allowed to see.

700
00:25:34,180 --> 00:25:36,100
Identity is no longer a log-in screen event.

701
00:25:36,100 --> 00:25:37,740
Identity is part of the query plan.

702
00:25:37,740 --> 00:25:41,380
The system needs to evaluate who is asking what data they can access,

703
00:25:41,380 --> 00:25:43,060
what documents they can access,

704
00:25:43,060 --> 00:25:45,380
and what artifacts can be stitched together

705
00:25:45,380 --> 00:25:47,780
without leaking protected context.

706
00:25:47,780 --> 00:25:50,820
This is why entra-behaves less like an identity provider

707
00:25:50,820 --> 00:25:52,380
and more like an access compiler.

708
00:25:52,380 --> 00:25:54,060
It isn't just verifying you exist,

709
00:25:54,060 --> 00:25:56,980
it's constraining what the answer is allowed to be.

710
00:25:56,980 --> 00:26:00,140
Third, an agentic layer showed up between the question and the data.

711
00:26:00,140 --> 00:26:04,620
A classic NLQ feature generates a single query and returns a visual.

712
00:26:04,620 --> 00:26:06,780
An agentic layer does multi-step work.

713
00:26:06,780 --> 00:26:08,340
Retrieve relevant artifacts,

714
00:26:08,340 --> 00:26:10,100
choose between DAX and SQL paths,

715
00:26:10,100 --> 00:26:12,860
run follow-up queries when results look ambiguous,

716
00:26:12,860 --> 00:26:16,100
summarize, and then answer with explanation.

717
00:26:16,100 --> 00:26:20,020
That's why chatting with data is not the same as asking for a number.

718
00:26:20,020 --> 00:26:22,540
The agent is doing what your best analyst used to do,

719
00:26:22,540 --> 00:26:24,660
picking the right source, validating sanity,

720
00:26:24,660 --> 00:26:25,860
applying business logic,

721
00:26:25,860 --> 00:26:29,220
and then writing the narrative that turns a metric into a decision.

722
00:26:29,220 --> 00:26:32,180
Fourth, explainability stopped being a nice to have.

723
00:26:32,180 --> 00:26:33,740
If the interface is a sentence,

724
00:26:33,740 --> 00:26:35,180
and the output is a sentence,

725
00:26:35,180 --> 00:26:37,380
you're now operating a probabilistic system

726
00:26:37,380 --> 00:26:39,300
in the most dangerous format possible,

727
00:26:39,300 --> 00:26:41,420
natural language that sounds confident.

728
00:26:41,420 --> 00:26:43,420
So the platform had to add an evidence trail,

729
00:26:43,420 --> 00:26:47,100
run steps, query traces, citations, lineage,

730
00:26:47,100 --> 00:26:49,180
what it used, what filters it applied,

731
00:26:49,180 --> 00:26:51,180
what it assumed and what it couldn't confirm.

732
00:26:51,180 --> 00:26:53,020
Without that, you don't have answers.

733
00:26:53,020 --> 00:26:54,500
You have fluent liability.

734
00:26:54,500 --> 00:26:56,940
And this is where a lot of organizations hit the wall.

735
00:26:56,940 --> 00:26:59,220
They want the speed of conversational answers,

736
00:26:59,220 --> 00:27:01,100
but they're still running the old governance model

737
00:27:01,100 --> 00:27:03,780
where meaning lives in people and exceptions live in spreadsheets.

738
00:27:03,780 --> 00:27:06,180
In that environment, the agent will still respond.

739
00:27:06,180 --> 00:27:09,220
It will just respond based on whatever it can infer,

740
00:27:09,220 --> 00:27:11,500
which is how you end up with quantitative hallucination

741
00:27:11,500 --> 00:27:14,860
and executive grade confusion delivered in perfect grammar.

742
00:27:14,860 --> 00:27:17,260
So the technical change is not LLMs can talk.

743
00:27:17,260 --> 00:27:19,620
The technical change is that the platform is being rebuilt

744
00:27:19,620 --> 00:27:21,260
to compile intent into governed,

745
00:27:21,260 --> 00:27:23,500
permissioned, auditable decision outputs.

746
00:27:23,500 --> 00:27:26,260
And once that exists, the canvas can't compete

747
00:27:26,260 --> 00:27:28,660
because the canvas requires the user to supply

748
00:27:28,660 --> 00:27:30,500
what the system can now supply faster.

749
00:27:30,500 --> 00:27:32,700
This is why Microsoft's ecosystem

750
00:27:32,700 --> 00:27:34,620
makes this shift unavoidable.

751
00:27:34,620 --> 00:27:39,620
Identity, context, and data live in the same gravitational field now.

752
00:27:39,620 --> 00:27:41,340
Microsoft makes this inevitable.

753
00:27:41,340 --> 00:27:43,620
Identity plus context plus data.

754
00:27:43,620 --> 00:27:46,180
Microsoft didn't invent conversational BI.

755
00:27:46,180 --> 00:27:48,180
Microsoft just put the missing ingredients

756
00:27:48,180 --> 00:27:49,820
in the same blast radius.

757
00:27:49,820 --> 00:27:51,820
And that matters because the interface always

758
00:27:51,820 --> 00:27:53,380
migrates toward the shortest path

759
00:27:53,380 --> 00:27:54,900
between intent and execution.

760
00:27:54,900 --> 00:27:57,820
In Microsoft's world, that path runs through three things

761
00:27:57,820 --> 00:28:00,260
that already sit at the center of how enterprises work.

762
00:28:00,260 --> 00:28:03,100
Identity, collaboration, context, and governed data.

763
00:28:03,100 --> 00:28:05,060
Start with context.

764
00:28:05,060 --> 00:28:07,500
Most organizations store their operational truth

765
00:28:07,500 --> 00:28:10,220
in Microsoft 365, whether they admit it or not.

766
00:28:10,220 --> 00:28:13,060
The real story of a revenue dip is not in the data set.

767
00:28:13,060 --> 00:28:14,460
It's in the meeting where someone said,

768
00:28:14,460 --> 00:28:16,900
we're changing pricing in a mere next week.

769
00:28:16,900 --> 00:28:19,700
It's in the follow-up email where finance pushed back.

770
00:28:19,700 --> 00:28:21,700
It's in the team's thread where sales complain

771
00:28:21,700 --> 00:28:24,380
that discount approval is now taking two days.

772
00:28:24,380 --> 00:28:26,900
It's in the document where a VP quietly changed

773
00:28:26,900 --> 00:28:28,260
the target assumptions.

774
00:28:28,260 --> 00:28:29,980
Dashboards never saw any of that.

775
00:28:29,980 --> 00:28:31,900
Dashboards saw the numbers after the fact,

776
00:28:31,900 --> 00:28:34,180
stripped of the argument that created them.

777
00:28:34,180 --> 00:28:35,700
M365 is different.

778
00:28:35,700 --> 00:28:39,540
M365 is the context substrate, mail, meetings, chats, docs,

779
00:28:39,540 --> 00:28:42,380
tasks, the actual operating exhaust of the company.

780
00:28:42,380 --> 00:28:44,780
When an AI system can read that substrate,

781
00:28:44,780 --> 00:28:46,180
the question, why did this happen?

782
00:28:46,180 --> 00:28:48,220
Stops being a data visualization problem

783
00:28:48,220 --> 00:28:50,860
and becomes a cross artifact reasoning problem.

784
00:28:50,860 --> 00:28:52,460
And the thing nobody wants to say out loud

785
00:28:52,460 --> 00:28:54,860
is that why usually lives outside the warehouse?

786
00:28:54,860 --> 00:28:57,100
Now at governed data, fabric and power BI

787
00:28:57,100 --> 00:28:58,820
are not just analytics tools.

788
00:28:58,820 --> 00:29:00,780
They're where the organization can still pretend

789
00:29:00,780 --> 00:29:03,700
it has contracts, semantic models, measures,

790
00:29:03,700 --> 00:29:06,420
lineage, sensitivity labels, access boundaries.

791
00:29:06,420 --> 00:29:07,860
That is the governed substrate.

792
00:29:07,860 --> 00:29:09,980
It is the piece that keeps answering a question

793
00:29:09,980 --> 00:29:12,260
from turning into creative writing with numbers.

794
00:29:12,260 --> 00:29:13,780
So you get a split brain architecture

795
00:29:13,780 --> 00:29:15,300
that finally makes sense.

796
00:29:15,300 --> 00:29:18,580
M365 provides context, fabric provides truth,

797
00:29:18,580 --> 00:29:20,780
and the system composes an answer from both.

798
00:29:20,780 --> 00:29:22,220
That's the first inevitability.

799
00:29:22,220 --> 00:29:24,260
The second inevitability is identity.

800
00:29:24,260 --> 00:29:26,220
In most stacks, identity is an afterthought.

801
00:29:26,220 --> 00:29:28,500
You authenticate, then you go do the work.

802
00:29:28,500 --> 00:29:31,380
In Microsoft's ecosystem, identity is the control plane.

803
00:29:31,380 --> 00:29:32,980
Entra doesn't just log you in.

804
00:29:32,980 --> 00:29:35,300
It constrains what you can see, what you can query,

805
00:29:35,300 --> 00:29:36,860
and what you can stitch together.

806
00:29:36,860 --> 00:29:38,620
And once questions become the interface,

807
00:29:38,620 --> 00:29:40,620
identity becomes part of the answer itself.

808
00:29:40,620 --> 00:29:43,060
Because the answer you get is not a universal truth.

809
00:29:43,060 --> 00:29:46,260
It's your permitted truth surface compiled at runtime,

810
00:29:46,260 --> 00:29:50,020
row-level security, sensitivity labels, document permissions,

811
00:29:50,020 --> 00:29:53,260
workspace access, and whatever other entropy generators

812
00:29:53,260 --> 00:29:55,340
your org accumulated over the years.

813
00:29:55,340 --> 00:29:57,460
That sounds scary, it should.

814
00:29:57,460 --> 00:29:59,340
But it's also the only model that scales

815
00:29:59,340 --> 00:30:01,260
without turning into a data leak machine.

816
00:30:01,260 --> 00:30:02,860
The system can't just be smart,

817
00:30:02,860 --> 00:30:04,340
and it has to be correct and authorized

818
00:30:04,340 --> 00:30:05,580
in the same transaction.

819
00:30:05,580 --> 00:30:07,860
That's what identity as compiler means in practice.

820
00:30:07,860 --> 00:30:09,540
Now add the integration gravity.

821
00:30:09,540 --> 00:30:12,140
Microsoft owns the surfaces where work happens.

822
00:30:12,140 --> 00:30:15,340
Teams, outlook, word, the meeting recap,

823
00:30:15,340 --> 00:30:17,740
the chat thread where decisions actually form.

824
00:30:17,740 --> 00:30:19,900
When the answer shows up inside those surfaces,

825
00:30:19,900 --> 00:30:22,140
the dashboard stops being the default doorway,

826
00:30:22,140 --> 00:30:23,660
not because the dashboard is bad,

827
00:30:23,660 --> 00:30:26,420
because the user never left the work surface in the first place.

828
00:30:26,420 --> 00:30:28,900
This is why the Power BI will be replaced, framing,

829
00:30:28,900 --> 00:30:29,940
is childish.

830
00:30:29,940 --> 00:30:32,220
Power BI becomes the evidence substrate.

831
00:30:32,220 --> 00:30:34,300
The semantic model becomes the meaning contract.

832
00:30:34,300 --> 00:30:36,100
The dashboard becomes an exhibit.

833
00:30:36,100 --> 00:30:38,740
Meanwhile, the primary interface becomes a question

834
00:30:38,740 --> 00:30:40,820
in the same place the decision is being argued.

835
00:30:40,820 --> 00:30:43,220
And the new capability is brutally simple.

836
00:30:43,220 --> 00:30:46,540
The system can answer what used to require three meetings.

837
00:30:46,540 --> 00:30:49,860
One meeting to find the number, one meeting to explain it,

838
00:30:49,860 --> 00:30:51,620
one meeting to figure out who owns it.

839
00:30:51,620 --> 00:30:53,820
So yes, Microsoft makes this inevitable,

840
00:30:53,820 --> 00:30:56,980
not through hype, through topology, identity context,

841
00:30:56,980 --> 00:30:59,140
and data already sit in the same ecosystem.

842
00:30:59,140 --> 00:31:00,860
Therefore, the interface will collapse

843
00:31:00,860 --> 00:31:03,460
into the shortest path between what's happening

844
00:31:03,460 --> 00:31:05,100
and what are we doing about it.

845
00:31:05,100 --> 00:31:06,660
And that's the setup for scenario one,

846
00:31:06,660 --> 00:31:08,500
because this is where it stops being abstract

847
00:31:08,500 --> 00:31:09,900
and starts being uncomfortable.

848
00:31:09,900 --> 00:31:13,340
Scenario one, executive question in Microsoft 365.

849
00:31:13,340 --> 00:31:14,660
So here's the lived reality.

850
00:31:14,660 --> 00:31:16,740
Monday morning, leadership is already behind,

851
00:31:16,740 --> 00:31:19,260
not behind on dashboards, behind on decisions.

852
00:31:19,260 --> 00:31:22,140
There's a board packed due, a forecast call in two hours,

853
00:31:22,140 --> 00:31:23,700
and a team's thread that's been arguing

854
00:31:23,700 --> 00:31:25,660
about pricing since Friday night.

855
00:31:25,660 --> 00:31:29,140
The VP drops a message, EMIA revenue dipped last week, why?

856
00:31:29,140 --> 00:31:31,220
And what decisions does it affect?

857
00:31:31,220 --> 00:31:33,780
In the dashboard era, the workflow is a ritual.

858
00:31:33,780 --> 00:31:36,140
Someone forwards the question to the data person.

859
00:31:36,140 --> 00:31:37,740
The data person opens Power BI.

860
00:31:37,740 --> 00:31:39,500
They pick the executive revenue app.

861
00:31:39,500 --> 00:31:40,740
They wait for the reporter load.

862
00:31:40,740 --> 00:31:43,700
They check whether the data set refreshed, they select EMIA,

863
00:31:43,700 --> 00:31:46,620
then they pick last week, then they discover the first problem.

864
00:31:46,620 --> 00:31:48,500
The dip is real, but the dashboard

865
00:31:48,500 --> 00:31:50,500
doesn't tell you anything useful about why.

866
00:31:50,500 --> 00:31:52,180
So they do what every analyst does.

867
00:31:52,180 --> 00:31:54,460
They start the scavenger hunt, they open teams.

868
00:31:54,460 --> 00:31:57,340
They search for the last time anyone mentioned EMIA.

869
00:31:57,340 --> 00:31:59,140
They look for a thread about pricing,

870
00:31:59,140 --> 00:32:01,660
they open the meeting recap from the sales standup.

871
00:32:01,660 --> 00:32:02,900
They check emails from finance,

872
00:32:02,900 --> 00:32:04,980
because finance always knows about revenue problems

873
00:32:04,980 --> 00:32:06,500
before anyone else admits it.

874
00:32:06,500 --> 00:32:09,660
They find a slide deck where someone changed a target assumption.

875
00:32:09,660 --> 00:32:11,580
They message someone in operations to ask

876
00:32:11,580 --> 00:32:13,900
whether there was an incident in order processing.

877
00:32:13,900 --> 00:32:15,380
This is the part that matters.

878
00:32:15,380 --> 00:32:16,940
The dashboard didn't answer the question.

879
00:32:16,940 --> 00:32:19,980
It produced a number that triggered a human rooting workflow.

880
00:32:19,980 --> 00:32:22,500
That's the institutional work you've been paying for.

881
00:32:22,500 --> 00:32:24,620
Now take the same question, but assume the interface

882
00:32:24,620 --> 00:32:26,820
is Microsoft 365 co-pilot,

883
00:32:26,820 --> 00:32:28,500
sitting inside the same work surface

884
00:32:28,500 --> 00:32:30,740
where the argument is already happening.

885
00:32:30,740 --> 00:32:32,460
Why did EMIA revenue dipped last week

886
00:32:32,460 --> 00:32:34,220
and what decisions does it affect?

887
00:32:34,220 --> 00:32:36,020
For that to work, the system has to behave

888
00:32:36,020 --> 00:32:37,580
like a decision engine, not a chat toy.

889
00:32:37,580 --> 00:32:39,940
First, it has to retrieve the metric from a govern source,

890
00:32:39,940 --> 00:32:42,340
not some spreadsheet in a SharePoint site,

891
00:32:42,340 --> 00:32:44,340
not a CSV someone exported.

892
00:32:44,340 --> 00:32:45,860
It has to use the semantic model

893
00:32:45,860 --> 00:32:48,540
that encodes what revenue means in your organization,

894
00:32:48,540 --> 00:32:51,100
net versus growth, returns handling,

895
00:32:51,100 --> 00:32:53,660
currency normalization, timing rules.

896
00:32:53,660 --> 00:32:56,220
Because without that, you are not asking for an answer.

897
00:32:56,220 --> 00:32:57,620
You are asking for a story.

898
00:32:57,620 --> 00:33:00,500
Second, it has to compile identity into the answer.

899
00:33:00,500 --> 00:33:03,620
The VP asking the question is not allowed to see everything.

900
00:33:03,620 --> 00:33:06,500
And the system cannot helpfully stitch in a document

901
00:33:06,500 --> 00:33:08,300
that the VP lacks access to,

902
00:33:08,300 --> 00:33:10,140
even if that document explains everything.

903
00:33:10,140 --> 00:33:12,100
That's where Enterer functions as an access compiler,

904
00:33:12,100 --> 00:33:13,540
not a login screen.

905
00:33:13,540 --> 00:33:16,300
Permissions constrain the true surface at runtime.

906
00:33:16,300 --> 00:33:18,100
Third, it has to locate operational context.

907
00:33:18,100 --> 00:33:20,940
The revenue dip is usually downstream of something messy,

908
00:33:20,940 --> 00:33:23,660
a pricing exception, a discount approval delay,

909
00:33:23,660 --> 00:33:27,020
a supply issue, a policy change, a competitor move,

910
00:33:27,020 --> 00:33:28,580
a billing incident.

911
00:33:28,580 --> 00:33:31,060
Those details live in emails meeting recaps, tickets,

912
00:33:31,060 --> 00:33:31,900
and docs.

913
00:33:31,900 --> 00:33:33,660
The system has to traverse those artifacts

914
00:33:33,660 --> 00:33:36,020
and pull only what's relevant and permitted,

915
00:33:36,020 --> 00:33:37,740
and then it has to do the hardest part.

916
00:33:37,740 --> 00:33:39,980
A symbol and answer that supports a decision.

917
00:33:39,980 --> 00:33:41,900
Not revenue is down 4.2%.

918
00:33:41,900 --> 00:33:44,020
An executive question is never just what.

919
00:33:44,020 --> 00:33:47,860
It's what changed, why, who owns it, and what we do next.

920
00:33:47,860 --> 00:33:49,700
So the response has to look like this.

921
00:33:49,700 --> 00:33:52,300
It states the number with the govern definition,

922
00:33:52,300 --> 00:33:54,220
the scope and the comparison baseline.

923
00:33:54,220 --> 00:33:56,780
It identifies the primary driver, not as a guest,

924
00:33:56,780 --> 00:33:58,380
but as an evidence-backed link.

925
00:33:58,380 --> 00:34:00,860
A pricing change referenced in a meeting recap,

926
00:34:00,860 --> 00:34:03,020
forecast assumption change in a document,

927
00:34:03,020 --> 00:34:06,180
a customer churn event documented in a CRM note,

928
00:34:06,180 --> 00:34:09,060
an incident referenced in a support channel.

929
00:34:09,060 --> 00:34:12,420
It identifies ownership, the accountable leader or team,

930
00:34:12,420 --> 00:34:14,780
and the artifact trail that proves it.

931
00:34:14,780 --> 00:34:17,300
And it states decision impact, which downstream decisions

932
00:34:17,300 --> 00:34:21,060
are now affected, budget reallocations, forecast revisions,

933
00:34:21,060 --> 00:34:23,340
hiring freezes, campaign adjustments,

934
00:34:23,340 --> 00:34:25,980
commitments already made based on the previous assumption.

935
00:34:25,980 --> 00:34:28,980
Now, the key is not that the system can produce a paragraph.

936
00:34:28,980 --> 00:34:31,340
The key is that it can produce a defensible paragraph.

937
00:34:31,340 --> 00:34:33,860
So it must include citations, which dataset,

938
00:34:33,860 --> 00:34:35,740
which semantic model, which email thread,

939
00:34:35,740 --> 00:34:37,620
which meeting recap, which document.

940
00:34:37,620 --> 00:34:40,300
It should expose run steps, what queries were executed,

941
00:34:40,300 --> 00:34:42,900
what filters were applied, what assumptions were made.

942
00:34:42,900 --> 00:34:45,740
Because the moment the VP replies, can we trust this?

943
00:34:45,740 --> 00:34:46,860
You either have an evidence trail

944
00:34:46,860 --> 00:34:48,500
or you have conditional chaos.

945
00:34:48,500 --> 00:34:49,620
And here's the punchline.

946
00:34:49,620 --> 00:34:52,180
If the VP gets that response inside the team's thread,

947
00:34:52,180 --> 00:34:54,420
where the question was asked, the dashboard didn't lose,

948
00:34:54,420 --> 00:34:55,540
because it was ugly.

949
00:34:55,540 --> 00:34:57,180
It lost because it was late.

950
00:34:57,180 --> 00:34:59,060
Power BI didn't become worthless.

951
00:34:59,060 --> 00:35:00,740
It became supporting evidence.

952
00:35:00,740 --> 00:35:03,500
The place you go when you need to drill, audit,

953
00:35:03,500 --> 00:35:04,860
and argue about the model.

954
00:35:04,860 --> 00:35:06,660
The dashboard becomes an exhibit you pull up

955
00:35:06,660 --> 00:35:09,060
when the decision needs deeper inspection.

956
00:35:09,060 --> 00:35:10,900
But the interface, the first point of contact

957
00:35:10,900 --> 00:35:13,180
between intent and data, moved.

958
00:35:13,180 --> 00:35:16,100
The answer arrived before Power BI even opened.

959
00:35:16,100 --> 00:35:17,860
And once leadership experiences that once,

960
00:35:17,860 --> 00:35:20,900
they don't go back to navigation, they go back to questions.

961
00:35:20,900 --> 00:35:24,540
Scenario two, fabric data agents, data activator,

962
00:35:24,540 --> 00:35:26,020
from reporting to response.

963
00:35:26,020 --> 00:35:28,580
Scenario one is about an executive pulling an answer

964
00:35:28,580 --> 00:35:30,820
into the place work already happens.

965
00:35:30,820 --> 00:35:33,420
Scenario two is harsher because it shows what happens

966
00:35:33,420 --> 00:35:35,420
when the system stops waiting for you to ask.

967
00:35:35,420 --> 00:35:37,980
This is where reporting gets replaced by response.

968
00:35:37,980 --> 00:35:39,140
The old model looks familiar.

969
00:35:39,140 --> 00:35:41,660
You build a dashboard for fulfillment success rate

970
00:35:41,660 --> 00:35:44,500
or fraud rate or ticket backlog or churn risk.

971
00:35:44,500 --> 00:35:45,620
You add a threshold line.

972
00:35:45,620 --> 00:35:47,780
You maybe configure and alert something fires

973
00:35:47,780 --> 00:35:49,780
and email arrives at 2.30 a.m.

974
00:35:49,780 --> 00:35:53,060
And then nothing happens because alerts don't create decisions.

975
00:35:53,060 --> 00:35:55,340
They create notifications.

976
00:35:55,340 --> 00:35:57,300
And notifications still require the human

977
00:35:57,300 --> 00:35:58,820
to do the expensive part.

978
00:35:58,820 --> 00:36:01,460
Determine whether it's real, determine why it happened,

979
00:36:01,460 --> 00:36:04,100
determine who owns it, and determine what action

980
00:36:04,100 --> 00:36:05,900
is appropriate right now.

981
00:36:05,900 --> 00:36:09,220
So the organization recreates the same human-rooting workflow

982
00:36:09,220 --> 00:36:10,420
just with more noise.

983
00:36:10,420 --> 00:36:12,420
Someone gets paged, they open the dashboard,

984
00:36:12,420 --> 00:36:14,700
they check whether the number is a refresh artifact,

985
00:36:14,700 --> 00:36:17,340
they pull a CSV, they ask someone in operations,

986
00:36:17,340 --> 00:36:20,060
they ask someone in engineering, they ask someone in finance,

987
00:36:20,060 --> 00:36:22,180
and they eventually write the message

988
00:36:22,180 --> 00:36:24,420
that should have existed in the first place.

989
00:36:24,420 --> 00:36:25,260
This is happening.

990
00:36:25,260 --> 00:36:27,660
Here's why, here's who owns it, here's what we're doing.

991
00:36:27,660 --> 00:36:29,180
That's the institutional work again.

992
00:36:29,180 --> 00:36:31,900
Now the fabric data agents will data activator model

993
00:36:31,900 --> 00:36:34,260
shifts the center of gravity.

994
00:36:34,260 --> 00:36:37,500
Instead of publish a report and hope someone looks,

995
00:36:37,500 --> 00:36:38,940
you express intent.

996
00:36:38,940 --> 00:36:41,780
What conditions matter, what evidence is required,

997
00:36:41,780 --> 00:36:44,980
and what the system should do when those conditions appear.

998
00:36:44,980 --> 00:36:46,660
So imagine a concrete example.

999
00:36:46,660 --> 00:36:49,140
For fulfillment success rate drops below 94%

1000
00:36:49,140 --> 00:36:50,900
for any region for more than two hours.

1001
00:36:50,900 --> 00:36:54,260
Not tell me tomorrow, not show me in the Monday dashboard.

1002
00:36:54,260 --> 00:36:56,860
Two hours in a dashboard world, you can visualize it,

1003
00:36:56,860 --> 00:36:58,180
you can even alert on it.

1004
00:36:58,180 --> 00:36:59,900
But the decision still waits for humans

1005
00:36:59,900 --> 00:37:01,740
to connect dots across systems,

1006
00:37:01,740 --> 00:37:04,940
carrier performance, warehouse capacity, inventory availability,

1007
00:37:04,940 --> 00:37:07,380
order-rooting changes, incident notes.

1008
00:37:07,380 --> 00:37:09,740
In the response model, the agent does that stitching

1009
00:37:09,740 --> 00:37:11,020
as part of the event.

1010
00:37:11,020 --> 00:37:13,660
A fabric data agent sits on govern sources,

1011
00:37:13,660 --> 00:37:16,820
lake house tables, warehouse tables, semantic models,

1012
00:37:16,820 --> 00:37:19,740
it has instructions, it has a constraint schema selection,

1013
00:37:19,740 --> 00:37:21,500
it has example queries that encode

1014
00:37:21,500 --> 00:37:24,140
how the business expects questions to be answered.

1015
00:37:24,140 --> 00:37:27,060
It knows which source is authoritative for which concept,

1016
00:37:27,060 --> 00:37:28,580
that is not a convenience feature,

1017
00:37:28,580 --> 00:37:30,660
that is governance expressed as machine behaviors.

1018
00:37:30,660 --> 00:37:32,300
So when the threshold triggers,

1019
00:37:32,300 --> 00:37:35,980
the agent doesn't just say rate is 93.6%,

1020
00:37:35,980 --> 00:37:38,780
it runs the diagnostic path, segment by carrier,

1021
00:37:38,780 --> 00:37:41,340
segment by warehouse, correlate with backlog,

1022
00:37:41,340 --> 00:37:44,300
check whether the drop aligns with a known operational

1023
00:37:44,300 --> 00:37:46,940
incident log and identify ownership.

1024
00:37:46,940 --> 00:37:49,580
And then it produces an answer that looks like something

1025
00:37:49,580 --> 00:37:52,020
a competent operations lead would send.

1026
00:37:52,020 --> 00:37:56,420
For film and success rate in EMEA is 93.6% for the last two hours

1027
00:37:56,420 --> 00:37:59,140
driven primarily by carrier X in the DE hub.

1028
00:37:59,140 --> 00:38:01,660
Backlog increased 18% starting at 10.05,

1029
00:38:01,660 --> 00:38:03,780
no matching order-rooting change detected.

1030
00:38:03,780 --> 00:38:07,700
Incident ticket, INC 4721 opened by logistics ops at 10.22.

1031
00:38:07,700 --> 00:38:10,420
Recommended action, re-root DE hub orders to carrier Y

1032
00:38:10,420 --> 00:38:12,100
until backlog clears.

1033
00:38:12,100 --> 00:38:14,740
Owners, logistics ops and carrier management.

1034
00:38:14,740 --> 00:38:15,740
That's the difference.

1035
00:38:15,740 --> 00:38:17,300
The system didn't refresh a visual,

1036
00:38:17,300 --> 00:38:18,980
it executed a decision pathway,

1037
00:38:18,980 --> 00:38:21,460
and now the governance dependency becomes obvious.

1038
00:38:21,460 --> 00:38:23,340
Agents only work when names are stable,

1039
00:38:23,340 --> 00:38:26,060
definitions are stable and access boundaries are enforced.

1040
00:38:26,060 --> 00:38:28,500
If fulfillment success rate means three different things

1041
00:38:28,500 --> 00:38:32,100
across three teams, the agent becomes a faster confusion engine.

1042
00:38:32,100 --> 00:38:35,100
If the tables are mislabeled and the semantic model is sloppy,

1043
00:38:35,100 --> 00:38:37,180
the agent makes the wrong join and confidently explains

1044
00:38:37,180 --> 00:38:37,940
the wrong cause.

1045
00:38:37,940 --> 00:38:39,260
If identity boundaries are weak,

1046
00:38:39,260 --> 00:38:41,340
the agent leaks context across roles

1047
00:38:41,340 --> 00:38:42,820
and you have a compliance incident

1048
00:38:42,820 --> 00:38:44,140
disguised as a helpful answer.

1049
00:38:44,140 --> 00:38:47,700
So the real requirement for response is not better AI,

1050
00:38:47,700 --> 00:38:49,500
it's enforced meaning.

1051
00:38:49,500 --> 00:38:53,060
The uncomfortable truth is that data agents don't remove governance work.

1052
00:38:53,060 --> 00:38:56,340
They formalize it, they force you to stop relying on tribal knowledge

1053
00:38:56,340 --> 00:38:59,140
and start encoding institutional truth as contracts,

1054
00:38:59,140 --> 00:39:03,180
semantic models, verified answers, schema selection and traceable run steps.

1055
00:39:03,180 --> 00:39:05,220
And this is where dashboard stop being the point.

1056
00:39:05,220 --> 00:39:06,980
Power BI still matters as evidence.

1057
00:39:06,980 --> 00:39:08,300
It's the exhibit you audit,

1058
00:39:08,300 --> 00:39:11,180
it's the place you validate the model and inspect the slice.

1059
00:39:11,180 --> 00:39:12,460
But the operational surface,

1060
00:39:12,460 --> 00:39:14,300
the thing people experience day to day,

1061
00:39:14,300 --> 00:39:17,620
becomes conditions, responses and accountable rooting.

1062
00:39:17,620 --> 00:39:21,100
That's what decision velocity looks like when you stop measuring views

1063
00:39:21,100 --> 00:39:22,580
and start measuring time to action.

1064
00:39:22,580 --> 00:39:24,740
And once you've seen an agent do the rooting work

1065
00:39:24,740 --> 00:39:27,780
your humans used to do manually, you can't unsee the waste.

1066
00:39:27,780 --> 00:39:31,300
Sonario 3, power BI as input, not destination.

1067
00:39:31,300 --> 00:39:33,700
Here's the part that makes power BI people defensive

1068
00:39:33,700 --> 00:39:34,500
and it shouldn't.

1069
00:39:34,500 --> 00:39:37,060
Power BI didn't die, it got demoted.

1070
00:39:37,060 --> 00:39:41,300
In the dashboard era, power BI was the destination.

1071
00:39:41,300 --> 00:39:43,020
You trained people to go to the report,

1072
00:39:43,020 --> 00:39:45,100
you built navigation like it was a website

1073
00:39:45,100 --> 00:39:46,860
and you treated the canvas as the product.

1074
00:39:46,860 --> 00:39:49,620
In the question era, power BI becomes the meaning layer

1075
00:39:49,620 --> 00:39:51,460
that feeds the answer engine.

1076
00:39:51,460 --> 00:39:53,060
The report is no longer the interface.

1077
00:39:53,060 --> 00:39:55,260
The semantic model is, that distinction matters

1078
00:39:55,260 --> 00:39:57,420
because the only thing worse than a slow dashboard

1079
00:39:57,420 --> 00:39:59,180
is a fast answer that's wrong.

1080
00:39:59,180 --> 00:40:00,780
The semantic model is the contract

1081
00:40:00,780 --> 00:40:02,900
that keeps the answer deterministic.

1082
00:40:02,900 --> 00:40:05,340
It's where you define measures, relationships,

1083
00:40:05,340 --> 00:40:07,180
time intelligence and business logic

1084
00:40:07,180 --> 00:40:09,220
so that revenue isn't an opinion.

1085
00:40:09,220 --> 00:40:10,860
It's compiled logic.

1086
00:40:10,860 --> 00:40:12,740
And when co-pilot or an agent answers,

1087
00:40:12,740 --> 00:40:15,820
the safest path is not interpret raw tables.

1088
00:40:15,820 --> 00:40:18,740
The safest path is use the same governed measures

1089
00:40:18,740 --> 00:40:21,140
the organization already agreed to.

1090
00:40:21,140 --> 00:40:23,220
So if someone asks what were net sales in EMEA

1091
00:40:23,220 --> 00:40:25,380
last week excluding wholesale returns,

1092
00:40:25,380 --> 00:40:27,740
the system doesn't need a human to translate that into

1093
00:40:27,740 --> 00:40:29,940
three filters and a DAX expression.

1094
00:40:29,940 --> 00:40:32,700
It needs a semantic model that already encodes net sales

1095
00:40:32,700 --> 00:40:35,300
and already encodes the exclusions as a governed measure.

1096
00:40:35,300 --> 00:40:37,020
Power BI is still doing the hard work.

1097
00:40:37,020 --> 00:40:38,980
It's just no longer getting the applause.

1098
00:40:38,980 --> 00:40:40,700
This is also where verified answers become

1099
00:40:40,700 --> 00:40:43,020
a real control mechanism, not a gimmick

1100
00:40:43,020 --> 00:40:44,580
for high value executive questions.

1101
00:40:44,580 --> 00:40:46,060
You don't want the agent improvising.

1102
00:40:46,060 --> 00:40:48,900
You wanted routing to a prevalidated query path,

1103
00:40:48,900 --> 00:40:50,660
a known measure, a known filter set,

1104
00:40:50,660 --> 00:40:52,580
a known visualization if needed,

1105
00:40:52,580 --> 00:40:54,300
and a known explanation template.

1106
00:40:54,300 --> 00:40:56,340
That's what verified answers really are,

1107
00:40:56,340 --> 00:40:59,220
a way to turn common executive questions

1108
00:40:59,220 --> 00:41:00,700
into governed endpoints.

1109
00:41:00,700 --> 00:41:02,660
And that's why power BI remains relevant

1110
00:41:02,660 --> 00:41:05,180
even when dashboards aren't the primary surface.

1111
00:41:05,180 --> 00:41:06,860
Because power BI provides three things

1112
00:41:06,860 --> 00:41:09,140
conversational systems desperately need,

1113
00:41:09,140 --> 00:41:12,060
lineage, security, semantics and auditability,

1114
00:41:12,060 --> 00:41:13,940
lineage where the data came from,

1115
00:41:13,940 --> 00:41:17,300
what transformations happened, what models and measures were used.

1116
00:41:17,300 --> 00:41:19,780
That's your defensibility story when the CFO asks,

1117
00:41:19,780 --> 00:41:22,420
why is this number different from last month's sport pack?

1118
00:41:22,420 --> 00:41:26,540
Security semantics, RLS, OLS and the underlying permission model

1119
00:41:26,540 --> 00:41:28,980
that decides what a user is allowed to see.

1120
00:41:28,980 --> 00:41:31,700
If your answer engine doesn't inherit those controls,

1121
00:41:31,700 --> 00:41:33,460
you don't have an analytic system.

1122
00:41:33,460 --> 00:41:35,820
You have a data leakage system, auditability,

1123
00:41:35,820 --> 00:41:37,660
the ability to show the query, the filters,

1124
00:41:37,660 --> 00:41:39,180
and the model behind the answer,

1125
00:41:39,180 --> 00:41:41,980
not as a technical flex, as a compliance requirement.

1126
00:41:41,980 --> 00:41:44,100
So power BI becomes the evidence substrate.

1127
00:41:44,100 --> 00:41:45,900
Dashboards become exhibits.

1128
00:41:45,900 --> 00:41:49,220
The place you go when you need to drill, validate and argue.

1129
00:41:49,220 --> 00:41:51,020
The model becomes the input layer.

1130
00:41:51,020 --> 00:41:53,820
The thing the system uses to produce answers safely.

1131
00:41:53,820 --> 00:41:56,300
And the conversational surface becomes the first contact point.

1132
00:41:56,300 --> 00:41:57,820
The place the business actually asks.

1133
00:41:57,820 --> 00:41:59,380
This is why the right question isn't,

1134
00:41:59,380 --> 00:42:01,420
will co-pilot replace power BI?

1135
00:42:01,420 --> 00:42:03,460
The right question is, will power BI be used

1136
00:42:03,460 --> 00:42:05,220
as a governed compiler for answers?

1137
00:42:05,220 --> 00:42:07,940
Or will you let answers compile themselves from raw,

1138
00:42:07,940 --> 00:42:09,300
drifting data?

1139
00:42:09,300 --> 00:42:10,660
One of those ends in speed.

1140
00:42:10,660 --> 00:42:12,540
The other ends in conditional chaos.

1141
00:42:12,540 --> 00:42:15,700
Dashboards versus answers, the inconvenient comparison.

1142
00:42:15,700 --> 00:42:18,020
People keep comparing dashboards and AI answers

1143
00:42:18,020 --> 00:42:19,980
like they're competing visualization products.

1144
00:42:19,980 --> 00:42:20,500
They're not.

1145
00:42:20,500 --> 00:42:22,780
They're competing interaction models.

1146
00:42:22,780 --> 00:42:25,100
A dashboard is a canvas you navigate.

1147
00:42:25,100 --> 00:42:27,380
An answer is a response to system assembles.

1148
00:42:27,380 --> 00:42:28,620
That difference sounds cosmetic

1149
00:42:28,620 --> 00:42:31,020
until you watch what it does to latency, trust,

1150
00:42:31,020 --> 00:42:31,900
and accountability.

1151
00:42:31,900 --> 00:42:33,860
Start with static versus contextual.

1152
00:42:33,860 --> 00:42:35,780
Dashboards are pre-compiled.

1153
00:42:35,780 --> 00:42:38,780
Someone decided in advance what the important cuts are,

1154
00:42:38,780 --> 00:42:41,220
what the filters mean and what the default view should be.

1155
00:42:41,220 --> 00:42:42,660
The best dashboards do that well.

1156
00:42:42,660 --> 00:42:44,780
The problem is that the business rarely stays inside

1157
00:42:44,780 --> 00:42:45,900
the pre-compiled boundary.

1158
00:42:45,900 --> 00:42:48,180
The moment the context shifts, new pricing rules,

1159
00:42:48,180 --> 00:42:49,780
new segments, new exceptions,

1160
00:42:49,780 --> 00:42:52,180
the dashboard is still showing yesterday's world view.

1161
00:42:52,180 --> 00:42:55,300
An answer can be assembled on demand from current context.

1162
00:42:55,300 --> 00:42:57,500
The metric, the relevant segment,

1163
00:42:57,500 --> 00:42:59,180
the active policy changes,

1164
00:42:59,180 --> 00:43:01,980
and the work artifacts that explain the why.

1165
00:43:01,980 --> 00:43:03,700
That doesn't mean the answer is always right.

1166
00:43:03,700 --> 00:43:05,500
It means the interface can keep up with drift

1167
00:43:05,500 --> 00:43:07,900
because it isn't anchored to a fixed page layout.

1168
00:43:07,900 --> 00:43:09,180
It's anchored to intent.

1169
00:43:09,180 --> 00:43:10,740
Now the interpretation burden.

1170
00:43:10,740 --> 00:43:12,860
A dashboard makes the viewer do the final mile.

1171
00:43:12,860 --> 00:43:15,140
The viewer sees a trend, guesses what matters,

1172
00:43:15,140 --> 00:43:17,580
and decides whether the number is trustworthy.

1173
00:43:17,580 --> 00:43:20,100
If the viewer is wrong, the dashboard doesn't correct them.

1174
00:43:20,100 --> 00:43:20,780
It can't.

1175
00:43:20,780 --> 00:43:21,780
The canvas is mute.

1176
00:43:21,780 --> 00:43:24,140
That's why dashboards create screenshot warfare.

1177
00:43:24,140 --> 00:43:25,660
Someone grabs a number without the filters,

1178
00:43:25,660 --> 00:43:26,620
drops it in teams,

1179
00:43:26,620 --> 00:43:29,540
and now you're spending the afternoon explaining context

1180
00:43:29,540 --> 00:43:31,540
that should have been embedded in the response.

1181
00:43:31,540 --> 00:43:32,740
Ancels flip that.

1182
00:43:32,740 --> 00:43:35,020
The system carries more of the explanation load,

1183
00:43:35,020 --> 00:43:36,900
what changed, what it correlates with,

1184
00:43:36,900 --> 00:43:39,020
what assumptions it used, what it can cite,

1185
00:43:39,020 --> 00:43:41,100
and what it can't see due to permissions.

1186
00:43:41,100 --> 00:43:42,460
That is not nice UX.

1187
00:43:42,460 --> 00:43:45,660
It is an architectural reassignment of responsibility,

1188
00:43:45,660 --> 00:43:47,340
lagging versus near real time.

1189
00:43:47,340 --> 00:43:48,620
Dashboards can be fast,

1190
00:43:48,620 --> 00:43:50,260
but dashboards are still a workflow.

1191
00:43:50,260 --> 00:43:53,500
Notice, open, navigate, interpret, validate, communicate.

1192
00:43:53,500 --> 00:43:54,980
The refresh rate isn't the bottleneck.

1193
00:43:54,980 --> 00:43:55,820
Humans are.

1194
00:43:55,820 --> 00:43:58,500
Meanwhile, an answer engine can operate at query time

1195
00:43:58,500 --> 00:44:00,580
and can push a response into the work stream

1196
00:44:00,580 --> 00:44:01,740
where the decision is forming.

1197
00:44:01,740 --> 00:44:04,420
When you collapse the workflow, you collapse the latency.

1198
00:44:04,420 --> 00:44:07,140
Scyload versus cross domain dashboards typically live

1199
00:44:07,140 --> 00:44:08,220
on one model at a time.

1200
00:44:08,220 --> 00:44:09,660
You can stitch models together, sure,

1201
00:44:09,660 --> 00:44:11,540
but the default experience is still

1202
00:44:11,540 --> 00:44:13,140
this report, this data setters.

1203
00:44:13,140 --> 00:44:14,620
Answers don't respect those boundaries

1204
00:44:14,620 --> 00:44:16,060
because the question doesn't.

1205
00:44:16,060 --> 00:44:19,380
Why did churn spike is never answered by churn data alone?

1206
00:44:19,380 --> 00:44:21,180
It's churn plus incidents plus support load,

1207
00:44:21,180 --> 00:44:24,180
plus policy changes, plus whatever sales promised last week,

1208
00:44:24,180 --> 00:44:26,540
dashboards do cross filtering.

1209
00:44:26,540 --> 00:44:30,300
Answers do cross artifact reasoning if you've governed it.

1210
00:44:30,300 --> 00:44:31,900
And that if is the whole game,

1211
00:44:31,900 --> 00:44:34,140
here's the deeper claim that makes people uncomfortable.

1212
00:44:34,140 --> 00:44:38,020
Dashboards scale metrics, answers scale judgment.

1213
00:44:38,020 --> 00:44:40,340
Not human judgment, human still decide.

1214
00:44:40,340 --> 00:44:42,060
But the system scales the judgment work

1215
00:44:42,060 --> 00:44:43,580
that used to sit in analysts,

1216
00:44:43,580 --> 00:44:46,540
rooting to the right source, applying the correct definition,

1217
00:44:46,540 --> 00:44:48,340
identifying the likely driver,

1218
00:44:48,340 --> 00:44:51,740
and packaging the result into something decision ready.

1219
00:44:51,740 --> 00:44:52,940
When the system can do that,

1220
00:44:52,940 --> 00:44:54,460
the dashboard loses its monopoly

1221
00:44:54,460 --> 00:44:57,300
because the dashboard is no longer the shortest path

1222
00:44:57,300 --> 00:44:58,700
to a defensible move.

1223
00:44:58,700 --> 00:45:01,020
And this is the comparison that destroys the old success

1224
00:45:01,020 --> 00:45:03,100
metrics because if you measure success

1225
00:45:03,100 --> 00:45:04,380
by dashboards shipped,

1226
00:45:04,380 --> 00:45:06,100
you'll keep shipping canvases into a world

1227
00:45:06,100 --> 00:45:07,380
that no longer navigates.

1228
00:45:07,380 --> 00:45:09,700
If you measure success by report adoption,

1229
00:45:09,700 --> 00:45:11,940
you'll optimize for clicks instead of outcomes.

1230
00:45:11,940 --> 00:45:14,260
The interface changed, therefore your KPIs have to change

1231
00:45:14,260 --> 00:45:15,900
with a dashboards aren't obsolete

1232
00:45:15,900 --> 00:45:17,460
because visuals are useless.

1233
00:45:17,460 --> 00:45:19,180
They're obsolete as the primary interface

1234
00:45:19,180 --> 00:45:21,780
because the business wants answers delivered inside the work

1235
00:45:21,780 --> 00:45:23,020
with evidence fast.

1236
00:45:23,020 --> 00:45:24,860
That's the inconvenient comparison.

1237
00:45:24,860 --> 00:45:27,940
And once you accept it, you stop asking, "How do we drive usage?"

1238
00:45:27,940 --> 00:45:30,820
You start asking, "How do we reduce decision latency

1239
00:45:30,820 --> 00:45:32,820
without creating conditional chaos?"

1240
00:45:32,820 --> 00:45:35,740
The new North Star, decision velocity, not adoption.

1241
00:45:35,740 --> 00:45:38,820
Most organizations still run BI like a marketing campaign.

1242
00:45:38,820 --> 00:45:40,020
They measure adoption.

1243
00:45:40,020 --> 00:45:41,140
They celebrate view counts.

1244
00:45:41,140 --> 00:45:42,620
They screenshot the usage dashboard

1245
00:45:42,620 --> 00:45:44,540
like it's proof the strategy worked.

1246
00:45:44,540 --> 00:45:45,740
And if usage is low,

1247
00:45:45,740 --> 00:45:47,940
they assume the problem is training awareness

1248
00:45:47,940 --> 00:45:49,300
or change management.

1249
00:45:49,300 --> 00:45:50,380
That's the comfortable story

1250
00:45:50,380 --> 00:45:53,020
because it keeps the solution inside the reporting factory.

1251
00:45:53,020 --> 00:45:54,980
Build better dashboards, do more enablement,

1252
00:45:54,980 --> 00:45:56,180
create a center of excellence,

1253
00:45:56,180 --> 00:45:58,580
publish a new landing page, rename the report

1254
00:45:58,580 --> 00:45:59,660
to something friendlier.

1255
00:45:59,660 --> 00:46:01,420
But adoption is a vanity metric

1256
00:46:01,420 --> 00:46:03,980
when the interface is no longer the destination.

1257
00:46:03,980 --> 00:46:06,220
If the real workflow is ask a question in teams

1258
00:46:06,220 --> 00:46:07,820
and get a decision-ready answer,

1259
00:46:07,820 --> 00:46:09,700
then dashboard clicks on signal.

1260
00:46:09,700 --> 00:46:12,100
Their noise, worst, they can be anti-signal.

1261
00:46:12,100 --> 00:46:14,180
A high view count might just mean people keep checking

1262
00:46:14,180 --> 00:46:15,500
because they don't trust it.

1263
00:46:15,500 --> 00:46:17,340
Or because they can't get the answer they need

1264
00:46:17,340 --> 00:46:19,580
without refreshing and refiltering,

1265
00:46:19,580 --> 00:46:20,660
like it's a slot machine.

1266
00:46:20,660 --> 00:46:22,100
Decision velocity is the metric

1267
00:46:22,100 --> 00:46:24,140
that survives contact with reality.

1268
00:46:24,140 --> 00:46:25,620
Time from question to action.

1269
00:46:25,620 --> 00:46:26,380
That's it.

1270
00:46:26,380 --> 00:46:28,220
That's the thing executives actually care about

1271
00:46:28,220 --> 00:46:29,700
even when they don't have the words for it.

1272
00:46:29,700 --> 00:46:31,860
They'll say, why does it take us two days to know this?

1273
00:46:31,860 --> 00:46:34,500
They'll say, why did we find out after it was too late?

1274
00:46:34,500 --> 00:46:36,780
They'll say, why are we always reacting?

1275
00:46:36,780 --> 00:46:38,500
Those are decision-latency complaints.

1276
00:46:38,500 --> 00:46:41,300
And dashboards are optimized for consumption, not closure.

1277
00:46:41,300 --> 00:46:42,860
So the new North Star isn't

1278
00:46:42,860 --> 00:46:44,780
how many people opened the report.

1279
00:46:44,780 --> 00:46:47,060
It's how fast did the organization move

1280
00:46:47,060 --> 00:46:48,140
after the question was asked

1281
00:46:48,140 --> 00:46:49,740
and could it defend the move?

1282
00:46:49,740 --> 00:46:52,260
That distinction matters because it changes what you build.

1283
00:46:52,260 --> 00:46:53,620
If you optimize for adoption,

1284
00:46:53,620 --> 00:46:55,020
you build prettier canvases,

1285
00:46:55,020 --> 00:46:57,260
you optimize navigation, you reduce pages,

1286
00:46:57,260 --> 00:46:59,660
you tweak colors, you build executive summary tabs,

1287
00:46:59,660 --> 00:47:01,220
you treat the report like a product

1288
00:47:01,220 --> 00:47:02,820
and the user like a consumer.

1289
00:47:02,820 --> 00:47:05,020
If you optimize for decision velocity,

1290
00:47:05,020 --> 00:47:06,740
you build answer pathways.

1291
00:47:06,740 --> 00:47:09,260
You reduce institutional work, you collapse routing,

1292
00:47:09,260 --> 00:47:11,180
you pre-define the evidence trail,

1293
00:47:11,180 --> 00:47:12,940
you encode semantics so the system

1294
00:47:12,940 --> 00:47:15,620
can compile intent into a governed response.

1295
00:47:15,620 --> 00:47:17,580
You stop asking users to become analysts

1296
00:47:17,580 --> 00:47:19,020
at the worst possible moment

1297
00:47:19,020 --> 00:47:21,020
when the decision window is already closing.

1298
00:47:21,020 --> 00:47:22,860
And yes, decision velocity is measurable,

1299
00:47:22,860 --> 00:47:25,060
not with vibes, with timestamps.

1300
00:47:25,060 --> 00:47:26,380
When did the question get asked?

1301
00:47:26,380 --> 00:47:27,780
When did an answer get delivered?

1302
00:47:27,780 --> 00:47:29,260
When did an action get taken?

1303
00:47:29,260 --> 00:47:31,220
When did the action get validated as correct

1304
00:47:31,220 --> 00:47:32,620
or at least defensible?

1305
00:47:32,620 --> 00:47:33,820
If you can't measure that,

1306
00:47:33,820 --> 00:47:35,380
you're not running a decision system.

1307
00:47:35,380 --> 00:47:36,940
You're running a reporting museum.

1308
00:47:36,940 --> 00:47:39,340
This is also why decision velocity wins politically.

1309
00:47:39,340 --> 00:47:41,500
Executives will fund speed and defensibility,

1310
00:47:41,500 --> 00:47:43,260
they will not fund more dashboards.

1311
00:47:43,260 --> 00:47:45,860
A dashboard sound like operational overhead.

1312
00:47:45,860 --> 00:47:48,460
Decision velocity sounds like competitive advantage,

1313
00:47:48,460 --> 00:47:49,780
it sounds like reduced risk,

1314
00:47:49,780 --> 00:47:51,260
it sounds like fewer surprises,

1315
00:47:51,260 --> 00:47:52,540
it sounds like fewer meetings

1316
00:47:52,540 --> 00:47:54,900
that exist purely to reconcile numbers.

1317
00:47:54,900 --> 00:47:56,300
And that's the quiet shift

1318
00:47:56,300 --> 00:47:57,540
the dashboard exists,

1319
00:47:57,540 --> 00:47:59,660
but the exec still asks a human moment

1320
00:47:59,660 --> 00:48:01,020
becomes measurable failure.

1321
00:48:01,020 --> 00:48:03,100
If a dashboard is published, refreshed,

1322
00:48:03,100 --> 00:48:04,660
and beautifully designed,

1323
00:48:04,660 --> 00:48:07,180
but the actual decision still roots through three people

1324
00:48:07,180 --> 00:48:08,460
and a slack thread,

1325
00:48:08,460 --> 00:48:10,420
then the dashboard didn't reduce latency.

1326
00:48:10,420 --> 00:48:12,100
It didn't improve the decision engine,

1327
00:48:12,100 --> 00:48:13,380
it just produced an artifact.

1328
00:48:13,380 --> 00:48:14,900
So the new KPI set looks different.

1329
00:48:14,900 --> 00:48:15,980
Decision latency,

1330
00:48:15,980 --> 00:48:18,460
answer acceptance rate, escalation frequency,

1331
00:48:18,460 --> 00:48:20,740
override rate when agents recommend an action.

1332
00:48:20,740 --> 00:48:22,700
Coverage of your question portfolio,

1333
00:48:22,700 --> 00:48:24,580
which questions have a governed answer path

1334
00:48:24,580 --> 00:48:26,940
versus which ones still require heroics?

1335
00:48:26,940 --> 00:48:28,380
And once you start measuring those,

1336
00:48:28,380 --> 00:48:31,060
a lot of legacy data work stops looking like best practice

1337
00:48:31,060 --> 00:48:33,140
and starts looking like expensive theater,

1338
00:48:33,140 --> 00:48:35,020
because the goal was never to get people to click,

1339
00:48:35,020 --> 00:48:37,540
the goal was to get the organization to move

1340
00:48:37,540 --> 00:48:39,300
where humans used to sit in the loop.

1341
00:48:39,300 --> 00:48:41,460
Before the question became the interface,

1342
00:48:41,460 --> 00:48:44,020
humans were the interface, not in a poetic way,

1343
00:48:44,020 --> 00:48:45,260
in a literal systems way,

1344
00:48:45,260 --> 00:48:47,620
the organization routed questions through specific people,

1345
00:48:47,620 --> 00:48:49,380
because those people acted as translators

1346
00:48:49,380 --> 00:48:51,380
between business intent and data reality.

1347
00:48:51,380 --> 00:48:53,940
They were the query engine, the semantic layer,

1348
00:48:53,940 --> 00:48:55,340
the anomaly detector,

1349
00:48:55,340 --> 00:48:56,900
and the narrative generator,

1350
00:48:56,900 --> 00:48:59,140
all wrapped in one calendar invite.

1351
00:48:59,140 --> 00:49:02,580
Start with analysts because they absorbed the most hidden load.

1352
00:49:02,580 --> 00:49:04,820
The analyst didn't just build reports.

1353
00:49:04,820 --> 00:49:07,140
The analyst performed institutional translation,

1354
00:49:07,140 --> 00:49:08,660
taking a vague question like,

1355
00:49:08,660 --> 00:49:10,060
are we okay in Emea?

1356
00:49:10,060 --> 00:49:12,060
When converting it into which data set,

1357
00:49:12,060 --> 00:49:14,100
which definition of revenue, what date logic,

1358
00:49:14,100 --> 00:49:16,100
what exclusions, what currency, what segments,

1359
00:49:16,100 --> 00:49:17,260
and what caveats,

1360
00:49:17,260 --> 00:49:19,660
then they ran it, checked whether the result looked sane

1361
00:49:19,660 --> 00:49:21,460
and wrote the human-friendly explanation

1362
00:49:21,460 --> 00:49:22,940
that made the number usable.

1363
00:49:22,940 --> 00:49:25,100
That last part is the piece people forget,

1364
00:49:25,100 --> 00:49:26,780
the dashboard might show a line.

1365
00:49:26,780 --> 00:49:28,500
The analyst supplied confidence.

1366
00:49:28,500 --> 00:49:30,980
Yes, this is real, it's not a refresh glitch,

1367
00:49:30,980 --> 00:49:33,220
and it's driven by Germany and the UK.

1368
00:49:33,220 --> 00:49:34,500
Confidence is a product,

1369
00:49:34,500 --> 00:49:36,300
it just wasn't tracked in your backlog,

1370
00:49:36,300 --> 00:49:37,900
then there were managers.

1371
00:49:37,900 --> 00:49:40,220
Managers sat in the loop as context providers

1372
00:49:40,220 --> 00:49:41,860
and authorization routers.

1373
00:49:41,860 --> 00:49:44,300
When an executive asked why did this change,

1374
00:49:44,300 --> 00:49:46,300
the manager knew which policy had shifted,

1375
00:49:46,300 --> 00:49:47,700
which project was in flight,

1376
00:49:47,700 --> 00:49:48,940
which customer escalated,

1377
00:49:48,940 --> 00:49:51,620
and which team was quietly underwater.

1378
00:49:51,620 --> 00:49:54,340
Managers turned metrics into operational reality.

1379
00:49:54,340 --> 00:49:57,100
Sales is down because discount approvals are bottlenecked,

1380
00:49:57,100 --> 00:50:00,380
or support loads spike because of the incident on Friday.

1381
00:50:00,380 --> 00:50:02,780
Dashboards almost never included that, they couldn't.

1382
00:50:02,780 --> 00:50:05,660
Context was dynamic, political, and often undocumented,

1383
00:50:05,660 --> 00:50:07,540
so managers became the bridge between the chart

1384
00:50:07,540 --> 00:50:08,820
and the real world.

1385
00:50:08,820 --> 00:50:11,420
Then finance, because finance is where dashboards go to die.

1386
00:50:11,420 --> 00:50:14,740
Finance teams sat in the loop as definition enforcers.

1387
00:50:14,740 --> 00:50:15,820
They were the semantic layer

1388
00:50:15,820 --> 00:50:18,420
when nobody else could be trusted to be consistent.

1389
00:50:18,420 --> 00:50:20,620
They knew the difference between recognized revenue

1390
00:50:20,620 --> 00:50:21,940
and book revenue they knew,

1391
00:50:21,940 --> 00:50:23,140
which adjustments were in play,

1392
00:50:23,140 --> 00:50:25,060
and they knew which numbers were official

1393
00:50:25,060 --> 00:50:27,340
versus for internal use only.

1394
00:50:27,340 --> 00:50:29,660
In practice, this meant a lot of dashboards existed,

1395
00:50:29,660 --> 00:50:31,260
but a smaller set of people were allowed

1396
00:50:31,260 --> 00:50:33,380
to interpret them without causing a crisis.

1397
00:50:33,380 --> 00:50:36,700
That's not democratization, that's controlled translation.

1398
00:50:36,700 --> 00:50:38,860
Then IT and data engineering,

1399
00:50:38,860 --> 00:50:41,140
they sat in the loop as pipeline babysitters.

1400
00:50:41,140 --> 00:50:42,380
When a metric looked wrong,

1401
00:50:42,380 --> 00:50:44,980
the answer was rarely the business changed.

1402
00:50:44,980 --> 00:50:46,820
The answer was the pipeline drifted,

1403
00:50:46,820 --> 00:50:48,300
a source system changed a column,

1404
00:50:48,300 --> 00:50:51,180
a nightly job failed, a joint exploded cardinality,

1405
00:50:51,180 --> 00:50:52,700
a refresh window slipped,

1406
00:50:52,700 --> 00:50:55,140
or someone introduced a temporary workaround

1407
00:50:55,140 --> 00:50:56,420
that became permanent.

1408
00:50:56,420 --> 00:50:57,660
So the loop looked like this.

1409
00:50:57,660 --> 00:51:00,420
Question asked, dashboard consulted, confusion detected,

1410
00:51:00,420 --> 00:51:02,820
escalation triggered, technical verification performed,

1411
00:51:02,820 --> 00:51:04,580
narrative rewritten decision delayed,

1412
00:51:04,580 --> 00:51:05,740
that was the operating model.

1413
00:51:05,740 --> 00:51:06,860
It just wasn't written down,

1414
00:51:06,860 --> 00:51:08,700
and dashboards became meeting props.

1415
00:51:08,700 --> 00:51:10,300
Not because leaders love visuals,

1416
00:51:10,300 --> 00:51:12,860
but because dashboards provided something meetings needed,

1417
00:51:12,860 --> 00:51:15,500
a shared object to point at while people argued.

1418
00:51:15,500 --> 00:51:18,980
A dashboard on screen creates the illusion of shared reality,

1419
00:51:18,980 --> 00:51:21,180
even when definitions are drifting underneath.

1420
00:51:21,180 --> 00:51:23,500
It gives people a place to anchor their opinions.

1421
00:51:23,500 --> 00:51:26,260
But the cost is that the meeting becomes the computation layer,

1422
00:51:26,260 --> 00:51:27,700
people do the joining, the filtering,

1423
00:51:27,700 --> 00:51:28,660
the exception handling,

1424
00:51:28,660 --> 00:51:30,420
and the interpretation in real time

1425
00:51:30,420 --> 00:51:33,180
with social dynamics influencing which explanation wins.

1426
00:51:33,180 --> 00:51:34,340
That's why the same dashboard

1427
00:51:34,340 --> 00:51:35,940
can produce different decisions depending

1428
00:51:35,940 --> 00:51:36,980
on who's in the room.

1429
00:51:36,980 --> 00:51:38,940
So what exactly is AI displacing here,

1430
00:51:38,940 --> 00:51:40,220
not responsibility?

1431
00:51:40,220 --> 00:51:41,860
That doesn't get automated.

1432
00:51:41,860 --> 00:51:44,100
AI displaces routing and translation.

1433
00:51:44,100 --> 00:51:47,300
The mechanical work of mapping intent to a governed query path,

1434
00:51:47,300 --> 00:51:49,580
retrieving the relevant context artifacts,

1435
00:51:49,580 --> 00:51:51,020
summarizing what changed,

1436
00:51:51,020 --> 00:51:53,780
and packaging it into a response that can be defended.

1437
00:51:53,780 --> 00:51:57,100
It takes the work that used to require an analyst plus a manager,

1438
00:51:57,100 --> 00:51:58,540
plus three follow-up messages,

1439
00:51:58,540 --> 00:52:00,660
and compresses it into a single interaction,

1440
00:52:00,660 --> 00:52:03,180
which means your org chart isn't the control plane anymore.

1441
00:52:03,180 --> 00:52:05,340
Your control plane is the answer pipeline,

1442
00:52:05,340 --> 00:52:08,740
semantics, identity, provenance, and observability.

1443
00:52:08,740 --> 00:52:11,060
And if you don't build that pipeline deliberately,

1444
00:52:11,060 --> 00:52:12,900
the system will still root questions.

1445
00:52:12,900 --> 00:52:15,540
It'll just root them through the oldest interface you have,

1446
00:52:15,540 --> 00:52:16,700
humans with tribal knowledge,

1447
00:52:16,700 --> 00:52:18,500
and you'll keep paying for decision latency

1448
00:52:18,500 --> 00:52:19,860
like it's a cost of doing business

1449
00:52:19,860 --> 00:52:23,100
instead of treating it as an architectural defect.

1450
00:52:23,100 --> 00:52:25,100
Why this kills traditional data leadership?

1451
00:52:25,100 --> 00:52:27,780
Traditional data leadership was built around deliverables.

1452
00:52:27,780 --> 00:52:30,140
Dashboards shipped, reports published,

1453
00:52:30,140 --> 00:52:32,940
a semantic model treated like an internal product launch.

1454
00:52:32,940 --> 00:52:34,100
And if you were competent,

1455
00:52:34,100 --> 00:52:35,540
you measured success with the proxies

1456
00:52:35,540 --> 00:52:38,540
the platform handed you, view counts, refresh success,

1457
00:52:38,540 --> 00:52:41,020
workspace adoption, training attendance,

1458
00:52:41,020 --> 00:52:42,780
we reduced duplicate reports.

1459
00:52:42,780 --> 00:52:45,820
That was the old power base controlling the artifact factory.

1460
00:52:45,820 --> 00:52:46,820
But the factory doesn't matter

1461
00:52:46,820 --> 00:52:49,300
when the business stops entering through the front door.

1462
00:52:49,300 --> 00:52:52,420
In the question era, the business doesn't care what you published.

1463
00:52:52,420 --> 00:52:54,900
It cares whether the system can answer right now

1464
00:52:54,900 --> 00:52:57,500
with evidence in the place the decision is happening.

1465
00:52:57,500 --> 00:52:59,180
That is a different value proposition,

1466
00:52:59,180 --> 00:53:01,020
and it immediately devalues the skills

1467
00:53:01,020 --> 00:53:02,620
most data leaders were promoted for.

1468
00:53:02,620 --> 00:53:05,980
Because the old identity wasn't owner of decision quality.

1469
00:53:05,980 --> 00:53:07,820
It was owner of the BI tool.

1470
00:53:07,820 --> 00:53:09,060
And the tool owner model worked

1471
00:53:09,060 --> 00:53:10,980
because dashboards forced everyone to route

1472
00:53:10,980 --> 00:53:11,900
through your workflow.

1473
00:53:11,900 --> 00:53:13,500
Want a new view, file a request,

1474
00:53:13,500 --> 00:53:15,500
want a new metric, get it prioritized,

1475
00:53:15,500 --> 00:53:18,340
want to reconcile numbers, book time with the data team.

1476
00:53:18,340 --> 00:53:19,300
You controlled the calendar

1477
00:53:19,300 --> 00:53:21,860
and therefore you controlled the narrative, plot twist.

1478
00:53:21,860 --> 00:53:24,060
That wasn't governance, that was scarcity.

1479
00:53:24,060 --> 00:53:26,340
Now you're watching scarcity get removed.

1480
00:53:26,340 --> 00:53:29,220
When an executive can ask co-pilot a question in teams

1481
00:53:29,220 --> 00:53:31,700
and get a plausible answer in under a minute,

1482
00:53:31,700 --> 00:53:32,980
the political center shifts.

1483
00:53:32,980 --> 00:53:34,580
Not because co-pilot is always correct,

1484
00:53:34,580 --> 00:53:36,100
because the executive just experienced

1485
00:53:36,100 --> 00:53:37,620
a lower friction pathway.

1486
00:53:37,620 --> 00:53:39,300
The executive learned a new habit,

1487
00:53:39,300 --> 00:53:41,700
bypassed the artifact, asked the system.

1488
00:53:41,700 --> 00:53:43,980
And once that habit forms your dashboard backlog

1489
00:53:43,980 --> 00:53:45,020
becomes decorative.

1490
00:53:45,020 --> 00:53:46,860
This is where traditional leaders lose relevance.

1491
00:53:46,860 --> 00:53:48,780
They keep optimizing the artifact

1492
00:53:48,780 --> 00:53:51,020
while the organization optimizes the interaction.

1493
00:53:51,020 --> 00:53:52,820
They keep building canvases while the business

1494
00:53:52,820 --> 00:53:54,460
is buying latency reduction.

1495
00:53:54,460 --> 00:53:56,540
They keep funding BI adoption programs

1496
00:53:56,540 --> 00:53:59,140
while leaders are measuring speed and defensibility.

1497
00:53:59,140 --> 00:54:00,620
They keep arguing about visual design

1498
00:54:00,620 --> 00:54:03,100
while the board asks why the organization can't answer,

1499
00:54:03,100 --> 00:54:06,220
what changed since Tuesday, without scheduling a meeting.

1500
00:54:06,220 --> 00:54:09,700
This is the moment the old success metrics turn into liabilities.

1501
00:54:09,700 --> 00:54:11,540
If you celebrate dashboards shipped,

1502
00:54:11,540 --> 00:54:13,580
you're celebrating production, not outcomes.

1503
00:54:13,580 --> 00:54:16,580
If you celebrate report usage, you might be celebrating confusion.

1504
00:54:16,580 --> 00:54:18,020
If you celebrate self-service,

1505
00:54:18,020 --> 00:54:20,420
you might be celebrating uncontrolled semantics.

1506
00:54:20,420 --> 00:54:22,020
A thousand people answering a question,

1507
00:54:22,020 --> 00:54:24,980
a thousand different ways with high confidence and low agreement.

1508
00:54:24,980 --> 00:54:28,540
And the more you scale that model, the more entropy you generate.

1509
00:54:28,540 --> 00:54:30,940
This is also why the data leadership role

1510
00:54:30,940 --> 00:54:33,860
collapses into AI leadership, whether you like it or not.

1511
00:54:33,860 --> 00:54:35,380
Because once questions are the interface,

1512
00:54:35,380 --> 00:54:36,660
answers become the product.

1513
00:54:36,660 --> 00:54:38,900
Not data sets, not reports, answers.

1514
00:54:38,900 --> 00:54:40,420
And answers have a life cycle.

1515
00:54:40,420 --> 00:54:43,180
They have inputs, constraints, evidence trails,

1516
00:54:43,180 --> 00:54:45,300
escalation paths and failure modes.

1517
00:54:45,300 --> 00:54:46,580
They are not static artifacts.

1518
00:54:46,580 --> 00:54:49,980
They are generated outputs that must remain defensible under audit,

1519
00:54:49,980 --> 00:54:52,940
under regulatory scrutiny and under internal challenge.

1520
00:54:52,940 --> 00:54:56,180
Most traditional data leadership models aren't built to own that.

1521
00:54:56,180 --> 00:54:57,860
They're built to publish and move on.

1522
00:54:57,860 --> 00:54:59,980
But the business doesn't experience published.

1523
00:54:59,980 --> 00:55:02,300
The business experience is answered.

1524
00:55:02,300 --> 00:55:03,820
So the natural selection pressure hits,

1525
00:55:03,820 --> 00:55:06,620
leaders who can't govern answers will get routed around.

1526
00:55:06,620 --> 00:55:08,940
Leaders who can't reduce decision latency

1527
00:55:08,940 --> 00:55:11,900
without creating conditional chaos will be treated as blockers.

1528
00:55:11,900 --> 00:55:13,940
Leaders who can't explain why the answer is correct

1529
00:55:13,940 --> 00:55:16,460
will lose trust faster than leaders who are simply slow.

1530
00:55:16,460 --> 00:55:18,740
And here's the line that usually lands like a brick.

1531
00:55:18,740 --> 00:55:21,820
If the CEO asks co-pilot instead of your dashboard,

1532
00:55:21,820 --> 00:55:23,700
your operating model already changed.

1533
00:55:23,700 --> 00:55:26,220
Not next quarter, not in the future, but already.

1534
00:55:26,220 --> 00:55:28,060
Because the CEO didn't ask for a report,

1535
00:55:28,060 --> 00:55:29,580
the CEO asked for an answer.

1536
00:55:29,580 --> 00:55:31,300
And the organization will always privilege

1537
00:55:31,300 --> 00:55:33,500
the shortest path from intent to action

1538
00:55:33,500 --> 00:55:35,220
until that path produces a disaster

1539
00:55:35,220 --> 00:55:37,140
at which point it will demand governance.

1540
00:55:37,140 --> 00:55:39,700
Not dashboards, that's the trap for traditional leadership.

1541
00:55:39,700 --> 00:55:42,380
They defend dashboards as if dashboards are governance.

1542
00:55:42,380 --> 00:55:43,060
They are not.

1543
00:55:43,060 --> 00:55:46,420
Dashboards are a presentation layer sitting on top of governance.

1544
00:55:46,420 --> 00:55:49,620
And in too many orgs, they're sitting on top of governance theater.

1545
00:55:49,620 --> 00:55:52,660
Definitions that drift, permissions that erode,

1546
00:55:52,660 --> 00:55:54,060
exceptions that pile up.

1547
00:55:54,060 --> 00:55:55,980
Lineage nobody checks until something breaks.

1548
00:55:55,980 --> 00:55:57,420
AI doesn't create those problems.

1549
00:55:57,420 --> 00:56:00,220
AI just makes them visible in plain English to everyone.

1550
00:56:00,220 --> 00:56:03,140
So yes, this kills traditional data leadership.

1551
00:56:03,140 --> 00:56:06,580
Because traditional leadership was measured by artifacts

1552
00:56:06,580 --> 00:56:08,860
and the business is moving to outcomes.

1553
00:56:08,860 --> 00:56:11,740
Answer quality, decision velocity and defensibility.

1554
00:56:11,740 --> 00:56:13,860
You can keep shipping dashboards into that world.

1555
00:56:13,860 --> 00:56:18,380
The system will let you and the business will keep asking questions somewhere else.

1556
00:56:18,380 --> 00:56:20,900
AI leadership owning the answer lifecycle.

1557
00:56:20,900 --> 00:56:24,380
So the role doesn't become AI leader because someone bought licenses.

1558
00:56:24,380 --> 00:56:27,660
It becomes AI leadership because the unit of value changed

1559
00:56:27,660 --> 00:56:29,860
from a report to an answer.

1560
00:56:29,860 --> 00:56:31,900
And answers have life cycles, failure modes,

1561
00:56:31,900 --> 00:56:34,540
and blast radiuses that dashboards never had.

1562
00:56:34,540 --> 00:56:38,180
In the dashboard world, leadership could pretend governance was a publishing workflow.

1563
00:56:38,180 --> 00:56:40,740
You reviewed the report, blessed the numbers, hit publish,

1564
00:56:40,740 --> 00:56:45,100
and then you let the organization argue about screenshots until the next refresh.

1565
00:56:45,100 --> 00:56:47,020
That model assumed the artifact was static.

1566
00:56:47,020 --> 00:56:50,100
In the question world, the artifact is generated at runtime.

1567
00:56:50,100 --> 00:56:52,140
Every answer is an execution.

1568
00:56:52,140 --> 00:56:57,060
A compilation of intent, a query plan, a set of sources, a set of permissions,

1569
00:56:57,060 --> 00:57:00,900
and a narrative wrapper that people will treat as truth because it sounds like truth.

1570
00:57:00,900 --> 00:57:03,860
So AI leadership is not about adopting co-pilot.

1571
00:57:03,860 --> 00:57:07,740
AI leadership is owning the answer lifecycle end to end.

1572
00:57:07,740 --> 00:57:10,140
How answers are produced, what they're allowed to use,

1573
00:57:10,140 --> 00:57:14,300
how they're verified, how they're audited, and what happens when they're wrong.

1574
00:57:14,300 --> 00:57:17,980
That distinction matters because most organizations are about to do the lazy version.

1575
00:57:17,980 --> 00:57:20,300
They'll roll out chat, call it empowerment,

1576
00:57:20,300 --> 00:57:23,500
and then act surprised when the first executive meeting goes sideways

1577
00:57:23,500 --> 00:57:26,940
because two leaders ask the same question and got two different answers.

1578
00:57:26,940 --> 00:57:28,220
That's not an AI problem.

1579
00:57:28,220 --> 00:57:30,140
That's an ownership problem.

1580
00:57:30,140 --> 00:57:33,460
Owning the answer lifecycle starts with a boring, non-negotiable move.

1581
00:57:33,460 --> 00:57:36,660
Define the classes of answers your organization will tolerate.

1582
00:57:36,660 --> 00:57:39,140
Some answers are exploratory, they're allowed to be fuzzy,

1583
00:57:39,140 --> 00:57:41,660
they're for analysts and operators who know how to validate.

1584
00:57:41,660 --> 00:57:43,700
Some answers are executive grade.

1585
00:57:43,700 --> 00:57:46,220
They must be deterministic, grounded in governed measures,

1586
00:57:46,220 --> 00:57:47,620
and accompanied by citations.

1587
00:57:47,620 --> 00:57:50,900
Some answers are prohibited, not because the user isn't trusted,

1588
00:57:50,900 --> 00:57:53,540
but because the system can't produce a defensible response

1589
00:57:53,540 --> 00:57:57,740
without violating a contract, privacy, legal, confidentiality,

1590
00:57:57,740 --> 00:57:59,900
or simply lack of reliable semantics.

1591
00:57:59,900 --> 00:58:03,860
If you don't classify answers, you default to one category improvisation.

1592
00:58:03,860 --> 00:58:07,300
An improvisation at enterprise scale becomes conditional chaos.

1593
00:58:07,300 --> 00:58:12,580
Next, answer ownership means you govern how the system maps words to meaning.

1594
00:58:12,580 --> 00:58:14,660
Because natural language is not a query language,

1595
00:58:14,660 --> 00:58:16,340
it's ambiguity wrapped in confidence.

1596
00:58:16,340 --> 00:58:20,580
When someone asks revenue, do they mean booked, recognized, net gross,

1597
00:58:20,580 --> 00:58:23,500
excluding returns in local currency or normalized?

1598
00:58:23,500 --> 00:58:27,060
When someone asks customer, do they mean account, contact, paying tenant,

1599
00:58:27,060 --> 00:58:30,340
active subscription or anyone who clicked a marketing link once?

1600
00:58:30,340 --> 00:58:33,460
Dashboards avoided this by forcing users into pre-model definitions.

1601
00:58:33,460 --> 00:58:35,260
Questions don't.

1602
00:58:35,260 --> 00:58:38,900
So you need a semantic layer that acts like a compiler dictionary,

1603
00:58:38,900 --> 00:58:42,420
measures, dimensions, relationships, synonyms, and constraints.

1604
00:58:42,420 --> 00:58:46,020
That's what keeps the system from answering the wrong question perfectly.

1605
00:58:46,020 --> 00:58:48,140
Then comes the part everyone underestimates.

1606
00:58:48,140 --> 00:58:49,780
Evidence and traceability.

1607
00:58:49,780 --> 00:58:53,540
Answer ownership means every answer is shipped with a defensability bundle,

1608
00:58:53,540 --> 00:58:55,020
which governed sources were used,

1609
00:58:55,020 --> 00:58:57,860
what filters were applied, what queries were executed,

1610
00:58:57,860 --> 00:59:00,220
and what context artifacts were referenced.

1611
00:59:00,220 --> 00:59:01,900
Not because auditors are coming tomorrow,

1612
00:59:01,900 --> 00:59:06,620
because the first time leadership makes a high-stakes decision of an AI answer,

1613
00:59:06,620 --> 00:59:07,940
someone will challenge it.

1614
00:59:07,940 --> 00:59:12,020
And if your only defense is the model set-so, you've already failed.

1615
00:59:12,020 --> 00:59:14,220
A leader can't defend the model set-so.

1616
00:59:14,220 --> 00:59:17,500
A leader can defend this answer came from this semantic model,

1617
00:59:17,500 --> 00:59:21,220
this measure definition, this data refresh and these supporting artifacts,

1618
00:59:21,220 --> 00:59:23,500
and it respected these access boundaries.

1619
00:59:23,500 --> 00:59:27,580
That's what answer leadership produces, explainability as an operational requirement,

1620
00:59:27,580 --> 00:59:28,740
not a moral preference.

1621
00:59:28,740 --> 00:59:32,620
And finally, owning the answer life cycle means you govern the operational loop

1622
00:59:32,620 --> 00:59:34,140
after the answer is delivered.

1623
00:59:34,140 --> 00:59:37,660
Dashboards didn't have a feedback loop beyond someone complained.

1624
00:59:37,660 --> 00:59:39,060
Answers need observability.

1625
00:59:39,060 --> 00:59:42,580
What questions get asked, which answers get accepted, which ones get escalated,

1626
00:59:42,580 --> 00:59:44,220
where humans override the system,

1627
00:59:44,220 --> 00:59:47,620
and where the same question keeps returning conflicting results.

1628
00:59:47,620 --> 00:59:49,740
Those signals aren't analytics vanity metrics.

1629
00:59:49,740 --> 00:59:52,260
They are the health metrics of your decision engine.

1630
00:59:52,260 --> 00:59:55,020
If override rates spike, the system lost trust.

1631
00:59:55,020 --> 00:59:58,300
If escalation's cluster around one domain, your semantics are drifting.

1632
00:59:58,300 --> 01:00:01,460
If the same leader keeps asking the same question, you didn't deliver closure,

1633
01:00:01,460 --> 01:00:02,540
you delivered a number.

1634
01:00:02,540 --> 01:00:04,300
So yes, AI leadership is governance,

1635
01:00:04,300 --> 01:00:07,420
but not governance as policy documents and committee meetings.

1636
01:00:07,420 --> 01:00:11,700
Governance as enforced system behavior, semantics, identity boundaries,

1637
01:00:11,700 --> 01:00:14,260
provenance, and observable decision pathways.

1638
01:00:14,260 --> 01:00:15,300
That's the new job.

1639
01:00:15,300 --> 01:00:17,860
Because the platform will generate answers either way.

1640
01:00:17,860 --> 01:00:20,900
Your choice is whether those answers are your organization's truth

1641
01:00:20,900 --> 01:00:23,780
or just another entropy generator that speaks fluent English.

1642
01:00:23,780 --> 01:00:25,860
Non-negotiables for trustworthy answers.

1643
01:00:25,860 --> 01:00:29,260
If questions are the interface, then trust becomes the product.

1644
01:00:29,260 --> 01:00:30,300
And trust is not a vibe.

1645
01:00:30,300 --> 01:00:34,340
It's a set of constraints that survive stressed humans, rushed executives,

1646
01:00:34,340 --> 01:00:37,340
and the platform's natural tendency to road around intent.

1647
01:00:37,340 --> 01:00:41,700
So here are the non-negotiables, not best practices system laws.

1648
01:00:41,700 --> 01:00:43,980
First, you need trusted data contracts.

1649
01:00:43,980 --> 01:00:45,860
Not just we have a lake house.

1650
01:00:45,860 --> 01:00:48,420
Contracts mean stable semantics, stable schemers,

1651
01:00:48,420 --> 01:00:51,820
and an explicit definition of what each metric is allowed to mean.

1652
01:00:51,820 --> 01:00:55,620
When a system answers revenue, it must have a single authoritative definition

1653
01:00:55,620 --> 01:00:59,220
to bind to, or you've turned language into an entropy generator.

1654
01:00:59,220 --> 01:01:02,380
This is why the semantic model matters more than the report.

1655
01:01:02,380 --> 01:01:03,740
The report is presentation.

1656
01:01:03,740 --> 01:01:07,500
The model is the contract, and contracts have to include quality expectations.

1657
01:01:07,500 --> 01:01:09,220
If the upstream system produces nulls,

1658
01:01:09,220 --> 01:01:11,980
later-riving records, duplicates, or inconsistent keys,

1659
01:01:11,980 --> 01:01:14,180
you don't solve that with prompt engineering.

1660
01:01:14,180 --> 01:01:16,060
You solve it with contracts and enforcement.

1661
01:01:16,060 --> 01:01:19,660
Data is valid, complete enough, and refreshed on a known cadence.

1662
01:01:19,660 --> 01:01:22,540
Otherwise, the answer engine will politely summarize garbage.

1663
01:01:22,540 --> 01:01:24,660
Second, you need controlled query surfaces.

1664
01:01:24,660 --> 01:01:28,140
Most organizations think connect co-pilot to all data is empowerment.

1665
01:01:28,140 --> 01:01:30,900
It's not. It's uncontrolled interpretation at scale.

1666
01:01:30,900 --> 01:01:34,300
The answer engine must have a constraint set of sanctioned pathways.

1667
01:01:34,300 --> 01:01:37,980
Semantic models, curated views, verified answers,

1668
01:01:37,980 --> 01:01:39,260
and explicit schema selection.

1669
01:01:39,260 --> 01:01:41,460
If you let the agent roam raw tables,

1670
01:01:41,460 --> 01:01:44,140
you're asking it to invent relationships, invent business meaning,

1671
01:01:44,140 --> 01:01:45,820
and improvise calculation logic.

1672
01:01:45,820 --> 01:01:49,260
That is how you get quantitative hallucinations that looks like competence.

1673
01:01:49,260 --> 01:01:52,420
The control surface is where you decide these columns are safe,

1674
01:01:52,420 --> 01:01:55,060
these measures are canonical, these tables represent truth,

1675
01:01:55,060 --> 01:01:57,300
and these combinations are prohibited.

1676
01:01:57,300 --> 01:01:59,220
It's also where you define answer classes,

1677
01:01:59,220 --> 01:02:01,220
exploratory versus executive grade.

1678
01:02:01,220 --> 01:02:04,060
Executive grade answers root through verified artifacts.

1679
01:02:04,060 --> 01:02:08,020
Always, you don't want creativity in the numbers that trigger hiring freezes.

1680
01:02:08,020 --> 01:02:11,220
Third, you need identity boundaries that compile into every answer.

1681
01:02:11,220 --> 01:02:13,300
Identity cannot be an authentication event.

1682
01:02:13,300 --> 01:02:15,860
It must be evaluated as part of the query plan.

1683
01:02:15,860 --> 01:02:19,780
That means row level security, object level security, and document permissions

1684
01:02:19,780 --> 01:02:23,140
all need to be enforced in the same transaction that produces the answer.

1685
01:02:23,140 --> 01:02:25,500
Because the failure mode here is not wrong number,

1686
01:02:25,500 --> 01:02:28,020
the failure mode is right number, wrong audience.

1687
01:02:28,020 --> 01:02:32,140
And once you stitch M365 context into answers that failure mode gets worse.

1688
01:02:32,140 --> 01:02:34,460
The system can accidentally join a confidential email

1689
01:02:34,460 --> 01:02:38,340
with a broadly accessible data set and leak context through a summary sentence.

1690
01:02:38,340 --> 01:02:40,540
So the boundary isn't just data permissions,

1691
01:02:40,540 --> 01:02:42,740
it's cross artifact stitching permissions.

1692
01:02:42,740 --> 01:02:46,580
You need entra and the underlying control plane to constrain what can be fused.

1693
01:02:46,580 --> 01:02:50,700
Fourth, governance and provenance must be built into the answer, not bolted on later.

1694
01:02:50,700 --> 01:02:53,540
People talk about citations like their UX polish.

1695
01:02:53,540 --> 01:02:54,180
They're not.

1696
01:02:54,180 --> 01:02:59,140
Citations are the only things standing between helpful assistant and legal discovery.

1697
01:02:59,140 --> 01:03:01,540
Every high value answer needs a provenance trail,

1698
01:03:01,540 --> 01:03:04,180
which data set, which semantic model, which refresh time,

1699
01:03:04,180 --> 01:03:07,500
which files or emails, which meeting recap, which workspace.

1700
01:03:07,500 --> 01:03:11,460
And if the system can't cite, it should downgrade the answer class.

1701
01:03:11,460 --> 01:03:14,740
I can't confirm this from governed sources instead of guessing.

1702
01:03:14,740 --> 01:03:17,540
This is where purview style lineage and catalog discipline

1703
01:03:17,540 --> 01:03:21,060
stop being compliance theater and become operational requirements.

1704
01:03:21,060 --> 01:03:23,700
If you can't trace the answer, you can't defend the decision.

1705
01:03:23,700 --> 01:03:27,380
And if you can't defend the decision, your velocity is just a faster way to be wrong.

1706
01:03:27,380 --> 01:03:30,020
Fifth, you need observability for the answer pipeline.

1707
01:03:30,020 --> 01:03:31,740
Dashboards had usage metrics.

1708
01:03:31,740 --> 01:03:33,540
Answers require decision telemetry.

1709
01:03:33,540 --> 01:03:36,580
You need to log who asked what they asked, what artifacts were used,

1710
01:03:36,580 --> 01:03:40,260
what queries were executed, what filters were applied and what the system returned.

1711
01:03:40,260 --> 01:03:42,660
Not for surveillance, for incident response.

1712
01:03:42,660 --> 01:03:46,340
Because answers will fail, definitions will drift, a source system will change,

1713
01:03:46,340 --> 01:03:47,780
a model will be updated.

1714
01:03:47,780 --> 01:03:51,940
And when an executive says this is wrong, you need to replay the pathway like a transaction log.

1715
01:03:51,940 --> 01:03:54,820
Otherwise, you're back to tribal debugging in teams.

1716
01:03:54,820 --> 01:03:57,700
Sixth, you need an operating model for escalation and review.

1717
01:03:57,700 --> 01:04:02,100
When the system can't answer deterministically, it must road to a human with context.

1718
01:04:02,100 --> 01:04:04,020
Not a generic mailbox, an owner.

1719
01:04:04,020 --> 01:04:07,540
Answer ownership means you know who is responsible for the definition,

1720
01:04:07,540 --> 01:04:12,260
who is responsible for the source and who is responsible for approving the verified version.

1721
01:04:12,260 --> 01:04:15,220
If you don't define escalation parts, you get shadow governance.

1722
01:04:15,220 --> 01:04:20,100
People copy the answer into Excel, fix it, and now the organization has two truths again.

1723
01:04:20,100 --> 01:04:22,100
And finally, you need to accept the core constraint.

1724
01:04:22,100 --> 01:04:23,620
AI doesn't fix bad leadership.

1725
01:04:23,620 --> 01:04:25,380
It exposes it in natural language.

1726
01:04:25,380 --> 01:04:28,900
So if you don't enforce these non-negotiables, you will still get answers.

1727
01:04:28,900 --> 01:04:31,220
Fast ones, fluent ones, confident ones.

1728
01:04:31,220 --> 01:04:34,580
And they'll be the most expensive lies your organization has ever produced.

1729
01:04:34,580 --> 01:04:37,140
The practical shift, inventory questions.

1730
01:04:37,140 --> 01:04:38,100
Not reports.

1731
01:04:38,100 --> 01:04:43,860
If this landed with you, the next move is not replete from BI or train everyone to prompt better.

1732
01:04:43,860 --> 01:04:46,980
The next move is administrative, which is why most orgs won't do it.

1733
01:04:46,980 --> 01:04:49,860
Replace the dashboard backlog with a question portfolio.

1734
01:04:49,860 --> 01:04:52,340
Because a dashboard backlog is a list of canvases,

1735
01:04:52,340 --> 01:04:56,580
a question portfolio is a list of decisions the business keeps failing to make quickly.

1736
01:04:56,580 --> 01:05:01,860
Start by pulling 10 executives and operators into a room and banning solution language.

1737
01:05:01,860 --> 01:05:06,420
No, we need a dashboard for no, we need a report that shows those are artifacts.

1738
01:05:06,420 --> 01:05:07,380
They are the wrong unit.

1739
01:05:07,380 --> 01:05:10,100
Ask for the questions they actually ask humans today.

1740
01:05:10,100 --> 01:05:13,060
The ones that trigger meetings, escalations and late-night threads.

1741
01:05:13,060 --> 01:05:16,660
The ones that generate institutional work because nobody can answer them cleanly,

1742
01:05:16,660 --> 01:05:18,180
then write them down verbatim.

1743
01:05:18,180 --> 01:05:21,780
In their messy political non-analyst language, why is it me or down again?

1744
01:05:21,780 --> 01:05:23,060
Are we going to miss forecast?

1745
01:05:23,060 --> 01:05:26,020
Which customers are at risk because support is behind?

1746
01:05:26,020 --> 01:05:27,300
Where are we leaking margin?

1747
01:05:27,300 --> 01:05:28,500
Who approved this?

1748
01:05:28,500 --> 01:05:30,260
That list is your interface spec.

1749
01:05:30,260 --> 01:05:32,020
Now classify each question.

1750
01:05:32,020 --> 01:05:33,300
Not with a governance committee.

1751
01:05:33,300 --> 01:05:37,060
With four blunt tags, value does this change revenue, cost or risk?

1752
01:05:37,060 --> 01:05:37,700
Frequency.

1753
01:05:37,700 --> 01:05:42,100
Is this daily noise or weekly cadence or an executive surprise?

1754
01:05:42,100 --> 01:05:46,420
Latency tolerance, do you need it in five minutes, five hours or five days?

1755
01:05:46,420 --> 01:05:47,140
Risk profile.

1756
01:05:47,140 --> 01:05:50,580
Does a wrong answer cause embarrassment or does it create legal exposure?

1757
01:05:50,580 --> 01:05:54,020
That classification is how you decide what gets a verified answer path

1758
01:05:54,020 --> 01:05:55,780
versus what stays exploratory.

1759
01:05:55,780 --> 01:05:59,860
High value, high frequency, low latency, high risk questions get engineered first.

1760
01:05:59,860 --> 01:06:01,700
Not built, engineered.

1761
01:06:01,700 --> 01:06:05,220
Because now you're designing an answer pathway, not a page layout.

1762
01:06:05,220 --> 01:06:07,620
For each top question, force, explicitness.

1763
01:06:07,620 --> 01:06:09,460
What is the authoritative data source?

1764
01:06:09,460 --> 01:06:11,380
Which semantic model defines the terms?

1765
01:06:11,380 --> 01:06:13,540
What permissions constrain the truth surface?

1766
01:06:13,540 --> 01:06:16,020
What context artifacts are relevant and permissible?

1767
01:06:16,020 --> 01:06:18,100
Meeting recaps, emails, tickets, docs?

1768
01:06:18,100 --> 01:06:20,340
What does evidence look like for this question?

1769
01:06:20,340 --> 01:06:23,140
Citations, lineage, run steps?

1770
01:06:23,140 --> 01:06:26,740
And what's the escalation path when the system can't answer deterministically?

1771
01:06:26,740 --> 01:06:29,140
This is where most teams discover the uncomfortable part.

1772
01:06:29,140 --> 01:06:30,180
The question is easy.

1773
01:06:30,180 --> 01:06:31,620
The answer pathway is not.

1774
01:06:31,620 --> 01:06:35,540
Because the answer pathway reveals where your organization has been relying on

1775
01:06:35,540 --> 01:06:39,620
tribal knowledge, a hidden filter, an unwritten definition,

1776
01:06:39,620 --> 01:06:44,420
a spreadsheet correction, a policy exception that everybody knows but nobody codified.

1777
01:06:44,420 --> 01:06:45,460
Good, that's the point.

1778
01:06:45,460 --> 01:06:46,740
Those are entropy generators.

1779
01:06:46,740 --> 01:06:50,100
Now you can see them, then decide the surface for each question.

1780
01:06:50,100 --> 01:06:52,020
Some questions become verified answers,

1781
01:06:52,020 --> 01:06:54,500
prevalidated measures, constrained schema,

1782
01:06:54,500 --> 01:06:57,620
predictable outputs, executive grade defensibility.

1783
01:06:57,620 --> 01:06:59,220
Some questions remain exploratory.

1784
01:06:59,220 --> 01:07:04,100
The agent can query, summarize and propose but it must disclose uncertainty and show its steps.

1785
01:07:04,100 --> 01:07:05,940
Some questions become prohibited,

1786
01:07:05,940 --> 01:07:08,900
not because you're controlling people but because you're controlling blast radius.

1787
01:07:08,900 --> 01:07:11,540
If the system can't answer safely, it should refuse.

1788
01:07:11,540 --> 01:07:14,580
Once you do that, you can finally define answer SLOs,

1789
01:07:14,580 --> 01:07:15,620
not refresh schedules.

1790
01:07:15,620 --> 01:07:17,540
Answer SLOs.

1791
01:07:17,540 --> 01:07:22,660
For this question, we deliver within five minutes with citations using this semantic model

1792
01:07:22,660 --> 01:07:24,580
and we log every execution.

1793
01:07:24,580 --> 01:07:28,180
That is how decision velocity becomes a real operating model instead of a slogan.

1794
01:07:28,180 --> 01:07:31,460
And the final move is political, stop celebrating dashboards shipped.

1795
01:07:31,460 --> 01:07:36,180
Start publishing a weekly list of questions that now resolve without human rooting.

1796
01:07:36,180 --> 01:07:37,300
Time from question to answer.

1797
01:07:37,300 --> 01:07:40,500
Escalation rate, override rate, that's the scoreboard that matters.

1798
01:07:40,500 --> 01:07:44,180
That's how you prove the interface shifted and you're governing it instead of being surprised by it.

1799
01:07:44,180 --> 01:07:47,940
Stop asking which dashboard should we build next?

1800
01:07:47,940 --> 01:07:50,820
Because that assumes navigation is still the interface.

1801
01:07:50,820 --> 01:07:54,740
The only question that matters now is which business questions deserve instant trust

1802
01:07:54,740 --> 01:07:57,780
where the answers and what evidence trail makes them defensible.

1803
01:07:57,780 --> 01:08:01,460
Drop a comment with the one executive question your org can't answer fast today

1804
01:08:01,460 --> 01:08:05,220
and tell me what it roots through people, dashboards or pure chaos.

1805
01:08:05,220 --> 01:08:09,060
Subscribe if you want more architectural truths, not vendor therapy.