1
00:00:00,080 --> 00:00:02,840
Welcome back to the deep Dive. 
If you've ever looked at a 

2
00:00:02,840 --> 00:00:05,680
complex problem, you know, 
whether it's organizational 

3
00:00:05,680 --> 00:00:09,600
inertia, customer retention, or 
even improving public services 

4
00:00:09,600 --> 00:00:12,560
and thought, there has to be a 
more creative way to solve this 

5
00:00:12,760 --> 00:00:14,640
than today's deep dive is for 
you. 

6
00:00:15,280 --> 00:00:17,600
We're pulling apart Design 
Thinking, or DT. 

7
00:00:18,040 --> 00:00:22,080
It's a methodology that started 
with graphic and product 

8
00:00:22,080 --> 00:00:25,320
designers, but has since just 
exploded into this essential 

9
00:00:25,320 --> 00:00:28,920
strategy for tacking complexity 
in, well, every field 

10
00:00:28,920 --> 00:00:30,040
imaginable. 
That's right. 

11
00:00:30,040 --> 00:00:33,040
We've synthesized the sources to
get you immediately to the core 

12
00:00:33,040 --> 00:00:35,760
concepts. 
Our mission today is to define, 

13
00:00:35,760 --> 00:00:39,520
you know, the necessary 
conditions for using DT, explain

14
00:00:39,520 --> 00:00:41,520
why this approach is so 
fundamentally different from 

15
00:00:41,520 --> 00:00:44,760
traditional problem solving, and
then walk through the three 

16
00:00:44,760 --> 00:00:48,320
interconnected phases, 
inspiration, ideation and 

17
00:00:48,320 --> 00:00:51,400
implementation that really 
define the designers mindset. 

18
00:00:51,400 --> 00:00:53,920
This is your rapid deep 
shortcut. 

19
00:00:53,920 --> 00:00:56,600
I love that phrase the designers
mindset, because while design 

20
00:00:56,600 --> 00:00:59,080
thinking feels incredibly 
modern, sort of Silicon Valley 

21
00:00:59,080 --> 00:01:02,800
approved, the sources are quick 
to point out that the 

22
00:01:02,800 --> 00:01:07,760
techniques, things like empathy,
maps, rapid prototyping, they 

23
00:01:07,760 --> 00:01:11,960
have roots stretching way back 
to the 1960s, borrowed directly 

24
00:01:11,960 --> 00:01:14,120
from architecture and industrial
design. 

25
00:01:14,120 --> 00:01:15,720
It was an operational shift, 
really. 

26
00:01:15,720 --> 00:01:18,440
For decades, these techniques 
were used to make sure a new 

27
00:01:18,440 --> 00:01:21,440
lamp was functional or a new 
user interface was intuitive. 

28
00:01:21,520 --> 00:01:23,120
Right for physical things. 
Exactly. 

29
00:01:23,120 --> 00:01:26,240
Yeah, The turning point was the 
realization that these human 

30
00:01:26,240 --> 00:01:29,040
centered techniques, they 
weren't restricted to physical 

31
00:01:29,040 --> 00:01:30,960
objects. 
They could solve organizational 

32
00:01:30,960 --> 00:01:34,080
challenges, educational 
deficits, or even policy issues.

33
00:01:34,280 --> 00:01:37,320
And the company most responsible
for taking this mindset 

34
00:01:37,320 --> 00:01:41,000
mainstream in the 90s and really
formalizing the phrase design 

35
00:01:41,000 --> 00:01:45,040
thinking is IDO, the US based 
design consultancy. 

36
00:01:45,480 --> 00:01:47,840
They're famous for helping 
design Apple's first 

37
00:01:47,840 --> 00:01:51,680
commercially successful mice, 
among many other foundational 

38
00:01:51,680 --> 00:01:53,800
products. 
They really proved that this 

39
00:01:53,800 --> 00:01:57,080
human centered, iterative 
approach could generate genuine 

40
00:01:57,080 --> 00:02:00,440
market disrupting innovation. 
And that innovation is precisely

41
00:02:00,440 --> 00:02:02,400
the goal. 
But we need to establish a very 

42
00:02:02,400 --> 00:02:04,760
important caveat right off the 
bat, a point our source is 

43
00:02:04,760 --> 00:02:07,680
really stress. 
DT is not a universal panacea. 

44
00:02:08,039 --> 00:02:09,560
You don't use it for every 
business problem. 

45
00:02:09,600 --> 00:02:12,480
When do we use it then? 
If someone is listening and has 

46
00:02:12,480 --> 00:02:15,440
a task list, how do they know 
which items deserve the DT 

47
00:02:15,440 --> 00:02:17,240
approach? 
You should deploy design 

48
00:02:17,240 --> 00:02:20,320
thinking specifically for 
problems where both the problem 

49
00:02:20,320 --> 00:02:23,160
and the solution are unclear. 
Uncertainty is the key 

50
00:02:23,160 --> 00:02:25,520
ingredient here. 
OK, let's use the contrasting 

51
00:02:25,520 --> 00:02:27,800
examples from the material to 
really make that distinction 

52
00:02:27,800 --> 00:02:31,000
stick for you. 
Say a company is hired to build 

53
00:02:31,040 --> 00:02:35,280
a robust web-based system for 
managing online multiple choice 

54
00:02:35,280 --> 00:02:37,760
exams. 
That is a clear cut case. 

55
00:02:37,880 --> 00:02:41,240
The problem is defined, we need 
a testing platform and the 

56
00:02:41,240 --> 00:02:44,440
solution is known right? 
A web application with standard 

57
00:02:44,440 --> 00:02:47,480
features like user accounts, 
database integration, greeting 

58
00:02:47,480 --> 00:02:50,240
mechanisms. 
You use standard, often agile 

59
00:02:50,240 --> 00:02:53,640
based practices here. 
So user stories talking to a 

60
00:02:53,640 --> 00:02:55,040
product owner. 
Exactly. 

61
00:02:55,080 --> 00:02:57,840
That's sufficient to identify 
requirements and execute the 

62
00:02:57,840 --> 00:02:59,760
project. 
You don't need a designer to 

63
00:02:59,760 --> 00:03:02,640
question the fundamental premise
of multiple choice exams. 

64
00:03:02,640 --> 00:03:05,640
Now let's switch gears. 
A major university wants to 

65
00:03:05,640 --> 00:03:08,960
develop an innovative method for
teaching software engineering to

66
00:03:08,960 --> 00:03:12,520
the next generation of students.
That is a massive conceptual 

67
00:03:12,520 --> 00:03:15,040
leap. 
The demand is totally unclear. 

68
00:03:15,440 --> 00:03:18,480
They don't know if the solution 
involves a new curriculum, A 

69
00:03:18,480 --> 00:03:22,040
mandatory internship program, or
maybe developing a new 

70
00:03:22,040 --> 00:03:23,800
collaborative software suite 
entirely. 

71
00:03:23,800 --> 00:03:25,480
They don't even know if software
is required. 

72
00:03:25,480 --> 00:03:27,640
Exactly. 
The university is dealing with a

73
00:03:27,640 --> 00:03:31,760
deeply uncertain future state. 
Design thinking is essential 

74
00:03:31,760 --> 00:03:35,120
here to unpack the true needs of
the learners and prototype 

75
00:03:35,120 --> 00:03:37,800
potential educational models 
before committing huge 

76
00:03:37,800 --> 00:03:39,680
resources. 
So if you're staring at 

77
00:03:39,680 --> 00:03:42,560
complexity and you don't even 
know what questions to ask, 

78
00:03:42,560 --> 00:03:46,160
that's your trigger for DT. 
Absolutely, and fundamental to 

79
00:03:46,160 --> 00:03:49,040
managing that uncertainty is the
team structure itself. 

80
00:03:49,600 --> 00:03:52,760
DT processes rely on 
multidisciplinary teams. 

81
00:03:53,240 --> 00:03:55,760
You need professionals from 
development, marketing, 

82
00:03:55,760 --> 00:03:58,440
education, maybe anthropology 
all working together. 

83
00:03:58,440 --> 00:04:00,960
Why is that multidisciplinarity 
so crucial though? 

84
00:04:01,240 --> 00:04:03,680
Can't a smart team of four 
engineers just solve the 

85
00:04:03,680 --> 00:04:05,440
problem? 
Because if everyone is looking 

86
00:04:05,440 --> 00:04:10,160
at the problem through the same 
lens, say a purely technical 1, 

87
00:04:10,480 --> 00:04:12,360
you will always arrive at a 
technical solution. 

88
00:04:12,360 --> 00:04:14,160
You risk developing a faster 
horse. 

89
00:04:14,400 --> 00:04:16,480
You risk developing a faster 
horse. 

90
00:04:17,040 --> 00:04:20,240
A multidisciplinary team breaks 
that professional bias, 

91
00:04:20,480 --> 00:04:23,560
maximizing the chances of 
generating those truly 

92
00:04:23,560 --> 00:04:26,280
out-of-the-box ideas needed for 
innovative solutions. 

93
00:04:26,600 --> 00:04:30,160
That sets the stage perfectly. 
Now we can get into the process 

94
00:04:30,160 --> 00:04:32,480
itself. 
The sources remind us that DT is

95
00:04:32,480 --> 00:04:34,440
not a checklist, not a strict 
algorithm. 

96
00:04:34,840 --> 00:04:38,520
It's characterized by three core
activities, inspiration, 

97
00:04:38,720 --> 00:04:41,400
ideation, and implementation. 
Let's start with the foundation 

98
00:04:41,800 --> 00:04:44,720
inspiration. 
Inspiration is synonymous with 

99
00:04:44,720 --> 00:04:48,360
deep, radical empathy. 
Before proposing anything, 

100
00:04:48,560 --> 00:04:51,480
designers have to internalize 
and genuinely experience the 

101
00:04:51,480 --> 00:04:54,120
problem from the perspective of 
those who are affected. 

102
00:04:54,120 --> 00:04:57,760
The users, how far did they go 
to gather that kind of insight? 

103
00:04:57,760 --> 00:04:59,680
I mean, it has to be more than 
sending out a survey, right? 

104
00:04:59,720 --> 00:05:02,280
Miles more, Yeah. 
The techniques are rooted in 

105
00:05:02,280 --> 00:05:05,640
ethnographic studies, intensive 
interviewing, visiting users in 

106
00:05:05,640 --> 00:05:08,200
their workplaces, observing 
behaviors in their natural 

107
00:05:08,200 --> 00:05:10,200
environments. 
It's about uncovering the 

108
00:05:10,200 --> 00:05:14,280
unspoken needs, the subtle, 
everyday frustrations that users

109
00:05:14,280 --> 00:05:15,800
might not even realize they 
have. 

110
00:05:16,080 --> 00:05:19,120
This is where those great 
stories that define design 

111
00:05:19,120 --> 00:05:22,160
thinking come in. 
The sources share that powerful 

112
00:05:22,160 --> 00:05:25,360
anecdote from Tim Brown, the 
former IDEO executive. 

113
00:05:25,960 --> 00:05:28,480
A designer was tasked with 
improving customer care at a 

114
00:05:28,480 --> 00:05:30,840
hospital. 
So instead of just relying on 

115
00:05:30,840 --> 00:05:34,360
patient interviews or comment 
cards, the designer simulated 

116
00:05:34,360 --> 00:05:36,600
having a broken foot, right? 
They put themselves in a 

117
00:05:36,600 --> 00:05:39,440
wheelchair and tried to navigate
the waiting rooms, the check in 

118
00:05:39,440 --> 00:05:40,960
process, the appointment 
scheduling. 

119
00:05:41,240 --> 00:05:43,600
They deliberately experienced 
the service first hand. 

120
00:05:44,200 --> 00:05:47,360
That level of dedication is 
necessary because it reveals 

121
00:05:47,360 --> 00:05:52,080
things no survey or interview 
ever would The subtle 

122
00:05:52,200 --> 00:05:55,040
infrastructural failures or, you
know, the emotional distance in 

123
00:05:55,040 --> 00:05:57,400
the care process. 
That is next level dedication, 

124
00:05:57,400 --> 00:06:00,600
but it sounds incredibly time 
consuming and quality, so this 

125
00:06:00,600 --> 00:06:03,720
raises a challenge. 
DT gives less emphasis to 

126
00:06:03,720 --> 00:06:06,240
traditional instruments like 
large scale surveys or 

127
00:06:06,240 --> 00:06:09,800
quantitative market research. 
Why sideline what most companies

128
00:06:09,800 --> 00:06:13,080
rely on as reliable data? 
It's not about ignoring data 

129
00:06:13,080 --> 00:06:16,560
entirely. 
It's about prioritizing insight 

130
00:06:16,560 --> 00:06:20,680
over sheer volume. 
Quantitative data tells you what

131
00:06:20,680 --> 00:06:23,000
happened. 
Design thinking cease to 

132
00:06:23,000 --> 00:06:26,040
understand why it happened and 
what hasn't happened yet. 

133
00:06:26,880 --> 00:06:29,400
We always rely on those 
legendary quotes to explain the 

134
00:06:29,400 --> 00:06:32,360
limitation of just asking users 
directly. 

135
00:06:32,400 --> 00:06:35,840
The faster horse phenomenon. 
Precisely Henry Ford's reputed 

136
00:06:35,840 --> 00:06:37,240
line. 
If I'd asked customers what they

137
00:06:37,240 --> 00:06:39,400
wanted, they would have told me 
a faster horse. 

138
00:06:40,240 --> 00:06:42,320
Users are constrained by their 
current reality. 

139
00:06:42,560 --> 00:06:45,440
They can describe the pain, but 
they can't leapfrog into 

140
00:06:45,440 --> 00:06:47,920
innovation. 
And Steve Jobs echoed that 

141
00:06:47,920 --> 00:06:50,640
sentiment decades later. 
He said people don't know what 

142
00:06:50,640 --> 00:06:52,160
they want until you show it to 
them. 

143
00:06:52,200 --> 00:06:54,400
Exactly. 
So the designer's job is to read

144
00:06:54,400 --> 00:06:56,880
between the lines of what the 
customer says they need and 

145
00:06:56,880 --> 00:07:00,480
infer A revolutionary solution 
they haven't even conceived of 

146
00:07:00,480 --> 00:07:01,280
yet. 
Yes. 

147
00:07:02,000 --> 00:07:05,480
Our role is to uncover the 
latent needs, and to help us do 

148
00:07:05,480 --> 00:07:08,800
that, the inspiration phase uses
some powerful advanced 

149
00:07:08,800 --> 00:07:10,800
techniques. 
The first is paying attention to

150
00:07:10,800 --> 00:07:13,040
extreme users. 
This is fascinating. 

151
00:07:13,040 --> 00:07:16,200
Why focus on the margins? 
Why look at the children, the 

152
00:07:16,200 --> 00:07:19,760
elderly, the early adopters, or 
the very best and worst 

153
00:07:19,760 --> 00:07:23,360
performers in a system? 
Because average users tend to 

154
00:07:23,360 --> 00:07:26,640
smooth out the data, they hide 
infrastructure weaknesses. 

155
00:07:27,200 --> 00:07:30,480
Extreme users push the system to
its breaking point. 

156
00:07:31,040 --> 00:07:33,800
If you design a process that 
successfully accommodates the 

157
00:07:33,800 --> 00:07:37,800
most technologically illiterate 
elderly user or the most 

158
00:07:37,800 --> 00:07:41,880
demanding power user early 
adopter, you create a robust 

159
00:07:41,880 --> 00:07:44,800
solution that works seamlessly 
for everyone in between. 

160
00:07:45,880 --> 00:07:49,200
Their needs aren't just 
magnified, they reveal hidden 

161
00:07:49,200 --> 00:07:51,720
constraints and unexpected 
potential. 

162
00:07:52,120 --> 00:07:54,920
And the second technique in this
inspiration phase, which is 

163
00:07:55,080 --> 00:07:58,120
maybe the most intellectual 
demanding, is reframing. 

164
00:07:58,680 --> 00:08:01,240
This means intentionally 
changing the fundamental 

165
00:08:01,240 --> 00:08:03,960
definition of the problem the 
client originally brought to 

166
00:08:03,960 --> 00:08:05,200
you. 
It's transformative. 

167
00:08:05,440 --> 00:08:08,280
You step back and say the 
problem isn't what you think it 

168
00:08:08,280 --> 00:08:09,880
is. 
The example from the sources is 

169
00:08:09,880 --> 00:08:11,760
brilliant. 
A publisher struggling to sell 

170
00:08:11,760 --> 00:08:13,760
books. 
The expected path is better 

171
00:08:13,760 --> 00:08:16,200
marketing, better distribution, 
maybe cheaper paper. 

172
00:08:16,200 --> 00:08:19,360
The usual stuff, right? 
But the team reframes the 

173
00:08:19,360 --> 00:08:21,880
problem entirely. 
They redefine the core assets. 

174
00:08:21,880 --> 00:08:23,960
What do you mean? 
They realize the core asset 

175
00:08:23,960 --> 00:08:27,360
isn't the physical book, it's 
the curated intellectual content

176
00:08:27,360 --> 00:08:31,040
within the catalog. 
By reframing the problem from we

177
00:08:31,040 --> 00:08:34,240
are bad at selling books to we 
are inefficiently delivering 

178
00:08:34,240 --> 00:08:37,200
knowledge, they completely shift
the solution space. 

179
00:08:37,280 --> 00:08:39,919
And they start offering online 
courses based on their catalog. 

180
00:08:39,919 --> 00:08:42,280
Exactly. 
It transforms the business model

181
00:08:42,280 --> 00:08:44,880
entirely. 
Drive from the same core assets.

182
00:08:45,320 --> 00:08:47,400
That is the power of the 
designer's mindset. 

183
00:08:47,400 --> 00:08:50,200
It's not about optimization, 
it's about transformation. 

184
00:08:50,720 --> 00:08:54,960
So we have our inspiration, our 
deep empathy, our reframed 

185
00:08:54,960 --> 00:08:57,120
problem. 
Now we shift into phase two 

186
00:08:57,480 --> 00:09:00,120
ideation. 
Ideation is where we generate 

187
00:09:00,120 --> 00:09:01,920
and rapidly test those 
possibilities. 

188
00:09:02,200 --> 00:09:06,320
It has two main highly active 
sub processes, divergent and 

189
00:09:06,320 --> 00:09:09,200
convergent thinking and then 
prototyping and testing. 

190
00:09:09,280 --> 00:09:10,880
Let's talk about that thinking. 
Dynamic. 

191
00:09:10,880 --> 00:09:13,400
Divergent thinking is the blue 
sky moment, right? 

192
00:09:13,440 --> 00:09:16,200
You go wide quantity over 
quality, sketching, 

193
00:09:16,280 --> 00:09:18,880
brainstorming, no judgement. 
The necessary chaos. 

194
00:09:18,880 --> 00:09:22,080
Generating hundreds of ideas, 
conventional or unconventional. 

195
00:09:22,280 --> 00:09:25,720
Yes, since the goal is 
innovative solutions, you have 

196
00:09:25,720 --> 00:09:28,160
to maximize your volume of raw 
material. 

197
00:09:28,800 --> 00:09:32,040
We rely on the wisdom of the two
time Nobel Prize winner Linus 

198
00:09:32,040 --> 00:09:35,440
Pauling. 
To have a good idea, you must 

199
00:09:35,440 --> 00:09:39,240
first have lots of ideas. 
If you only generate 10 ideas, 

200
00:09:39,560 --> 00:09:42,200
the best you can hope for is an 
incremental improvement. 

201
00:09:42,200 --> 00:09:44,880
So you fill the whiteboard and 
then you apply the brakes and 

202
00:09:44,880 --> 00:09:47,120
move to convergent thinking. 
Which is the necessary 

203
00:09:47,120 --> 00:09:49,880
discipline? 
It's narrowing down grouping, 

204
00:09:50,120 --> 00:09:54,080
prioritizing and discarding the 
non feasible or less impactful 

205
00:09:54,080 --> 00:09:56,560
ideas. 
The team collaboratively 

206
00:09:56,560 --> 00:09:59,160
determines which limited set of 
solutions is worth the 

207
00:09:59,160 --> 00:10:01,760
investment of prototyping. 
And once you have those few best

208
00:10:01,760 --> 00:10:04,720
ideas, you jump straight into 
the second ideation activity, 

209
00:10:04,760 --> 00:10:07,800
prototyping and testing. 
But you mentioned low fidelity 

210
00:10:07,800 --> 00:10:09,800
is key. 
Why not build something polished

211
00:10:09,800 --> 00:10:12,080
right away? 
You must fail cheaply and 

212
00:10:12,080 --> 00:10:14,280
quickly. 
Prototyping is about making the 

213
00:10:14,280 --> 00:10:16,880
abstract tangible without a 
major investment. 

214
00:10:17,360 --> 00:10:20,240
The sources highlight that 
famous IDO anecdote. 

215
00:10:20,360 --> 00:10:23,480
When they built the very first 
mouse prototype for Apple, they 

216
00:10:23,480 --> 00:10:25,880
weren't using high grade 
plastics or advanced machinery. 

217
00:10:25,960 --> 00:10:28,720
They used a roll on deodorant 
ball and a margarine container. 

218
00:10:28,920 --> 00:10:30,880
Exactly. 
That is the genius of Low 

219
00:10:30,880 --> 00:10:32,760
Fidelity. 
It cost pennies. 

220
00:10:32,880 --> 00:10:35,840
You build it in an afternoon and
you put it in a user's hand. 

221
00:10:36,360 --> 00:10:39,400
The user immediately tells you 
the shape is wrong or the 

222
00:10:39,400 --> 00:10:41,000
placement of the button is 
awkward. 

223
00:10:41,000 --> 00:10:44,400
You learn what's wrong before 
you spend $100,000 on tooling. 

224
00:10:44,440 --> 00:10:47,800
Right, It manages financial risk
while maximizing learning. 

225
00:10:48,120 --> 00:10:51,720
The prototyping can get tricky 
if you're not building a 

226
00:10:51,720 --> 00:10:53,680
physical object. 
I mean, if you're designing a 

227
00:10:53,680 --> 00:10:56,760
service or a new software 
interface, how do you manage 

228
00:10:56,760 --> 00:11:00,120
that low fidelity test? 
For services, it sometimes 

229
00:11:00,120 --> 00:11:03,360
requires setting up an 
improvised physical space, maybe

230
00:11:03,360 --> 00:11:06,520
using cheap furniture or 
Styrofoam to simulate the user 

231
00:11:06,520 --> 00:11:09,840
journey, much like the designer 
simulating the broken foot. 

232
00:11:10,320 --> 00:11:13,320
For software interfaces or 
complex processes, you use 

233
00:11:13,320 --> 00:11:15,320
storyboards. 
Storyboards being simple 

234
00:11:15,320 --> 00:11:18,520
drawings or visual narratives 
that depict the users step by 

235
00:11:18,520 --> 00:11:21,000
step journey through the 
proposed new service or 

236
00:11:21,000 --> 00:11:22,640
interface. 
Exactly. 

237
00:11:22,760 --> 00:11:25,320
They serve as effective 
prototypes because they allow 

238
00:11:25,320 --> 00:11:28,400
the team and the user to 
identify friction points and 

239
00:11:28,400 --> 00:11:31,880
logical flaws before a single 
line of code is written or a 

240
00:11:31,880 --> 00:11:36,320
single policy is finalized. 
They are cheap, fast and easy to

241
00:11:36,320 --> 00:11:39,000
modify. 
So we've been inspired, we've 

242
00:11:39,000 --> 00:11:42,240
ideated and prototyped, and 
we've selected a viable, tested 

243
00:11:42,240 --> 00:11:45,040
solution. 
This leads us to the final phase

244
00:11:45,400 --> 00:11:48,040
implementation. 
Now this phase sounds like the 

245
00:11:48,040 --> 00:11:50,280
handoff to the rest of the 
organization, marketing, 

246
00:11:50,280 --> 00:11:53,360
production, sales. 
It's more than a handoff, it's 

247
00:11:53,360 --> 00:11:55,960
accompaniment. 
Once the solution is chosen, the

248
00:11:55,960 --> 00:11:58,160
designer has to help shepherd 
its execution. 

249
00:11:58,640 --> 00:12:00,880
The implementation phase 
involves assisting with 

250
00:12:00,880 --> 00:12:04,040
organizational explanation, 
communicating why this radical 

251
00:12:04,040 --> 00:12:06,280
new solution was chosen, and 
helping develop the 

252
00:12:06,280 --> 00:12:08,320
communication and marketing 
strategies. 

253
00:12:08,440 --> 00:12:11,480
That sounds critical, especially
for a radical reframing like the

254
00:12:11,480 --> 00:12:14,480
publisher example changing the 
business from books to courses. 

255
00:12:14,720 --> 00:12:17,680
The design team has to sell that
radical shift internally. 

256
00:12:17,960 --> 00:12:22,440
Precisely if the idea generated 
an ideation is truly innovative,

257
00:12:22,680 --> 00:12:25,160
it may not conform to the 
organization's existing 

258
00:12:25,160 --> 00:12:28,800
structure or sales channels. 
The implementation phase 

259
00:12:28,800 --> 00:12:30,760
addresses that organizational 
inertia. 

260
00:12:31,360 --> 00:12:34,400
The designer provides the 
context and the human centered 

261
00:12:34,400 --> 00:12:37,560
narrative that proves this 
strained new idea is exactly 

262
00:12:37,560 --> 00:12:40,720
what the user actually needed. 
No, you just walked us through 

263
00:12:40,720 --> 00:12:43,160
inspiration, ideation, and 
implementation. 

264
00:12:43,440 --> 00:12:46,000
Hearing it laid out that way, it
sounds like a perfect linear 

265
00:12:46,000 --> 00:12:48,760
assembly line. 
But our sources are very clear 

266
00:12:48,760 --> 00:12:52,120
that this is a common and 
dangerous misconception. 

267
00:12:52,360 --> 00:12:54,480
Absolutely. 
Design thinking is fundamentally

268
00:12:54,480 --> 00:12:57,000
non sequential. 
It is always possible and 

269
00:12:57,000 --> 00:12:59,960
usually necessary to loop back 
to a previous stage. 

270
00:13:00,480 --> 00:13:02,560
The process is iterative, not 
linear. 

271
00:13:02,640 --> 00:13:04,680
What's the most common reason 
you would loop backward? 

272
00:13:04,680 --> 00:13:07,520
Well, say you're deep in the 
ideation phase brainstorming 

273
00:13:07,520 --> 00:13:10,640
ideas, and you realize that all 
your best ideas rely on 

274
00:13:10,640 --> 00:13:14,080
understanding how a specific 
minority user group interacts 

275
00:13:14,080 --> 00:13:16,840
with technology data you just 
didn't gather during the initial

276
00:13:16,840 --> 00:13:18,120
research you have. 
A blind spot. 

277
00:13:18,480 --> 00:13:20,600
A huge 1. 
So you have to stop, loop 

278
00:13:20,600 --> 00:13:23,440
immediately back to inspiration,
conduct those specific 

279
00:13:23,440 --> 00:13:27,120
ethnographic studies, and then 
return to ideation armed with a 

280
00:13:27,120 --> 00:13:30,600
necessary insight. 
Or conversely, you build the low

281
00:13:30,600 --> 00:13:33,920
fidelity prototype, test it with
real users, and it fails 

282
00:13:33,920 --> 00:13:36,280
spectacularly. 
You don't just push it into 

283
00:13:36,280 --> 00:13:39,280
implementation anyway. 
You can jump back to ideation or

284
00:13:39,280 --> 00:13:42,440
potentially even all the way 
back to inspiration to redefine 

285
00:13:42,440 --> 00:13:44,160
the need and generate a new 
path. 

286
00:13:44,400 --> 00:13:47,840
That constant iterative 
movement, often illustrated by 

287
00:13:47,840 --> 00:13:50,200
interconnected loops, is what 
defines DT. 

288
00:13:50,320 --> 00:13:52,480
It's a learning cycle, not a 
production line. 

289
00:13:53,240 --> 00:13:56,240
The solution emerges through 
continuous refinement and user 

290
00:13:56,240 --> 00:13:59,360
feedback, not by following a 
rigid set of steps. 

291
00:14:00,080 --> 00:14:03,200
So what does this entire 
framework, this ability to 

292
00:14:03,240 --> 00:14:05,840
empathize deeply, generate 
widely, and iterate 

293
00:14:05,840 --> 00:14:08,360
relentlessly, require from the 
individual? 

294
00:14:08,800 --> 00:14:11,560
What are the essential traits of
a successful design thinker 

295
00:14:11,560 --> 00:14:13,760
according to Tim Brown? 
The traits are rooted in 

296
00:14:13,760 --> 00:14:17,600
synthesis and perspective. 
First, the capacity to identify 

297
00:14:17,600 --> 00:14:20,640
patterns hidden within complex, 
often contradictory information.

298
00:14:21,080 --> 00:14:23,680
Second, the skill of taking 
those identified fragments and 

299
00:14:23,680 --> 00:14:26,000
synthesizing brand new novel 
ideas. 

300
00:14:26,320 --> 00:14:30,680
And perhaps most vital, the 
ability to genuinely empathize 

301
00:14:30,680 --> 00:14:32,880
with people who are 
fundamentally different from 

302
00:14:32,880 --> 00:14:35,360
oneself, moving beyond self 
reference. 

303
00:14:35,360 --> 00:14:38,760
That makes design thinking feel 
less like a methodology manual 

304
00:14:38,760 --> 00:14:41,400
and more like a mastery of 
perspective And intellectual 

305
00:14:41,400 --> 00:14:45,440
agility is a powerful framework 
for tackling massive complexity 

306
00:14:45,440 --> 00:14:48,600
and deep uncertainty by focusing
relentlessly on the human 

307
00:14:48,600 --> 00:14:51,400
experience and daring to 
completely reframe the original 

308
00:14:51,400 --> 00:14:52,880
problem. 
Thank you for joining us on this

309
00:14:52,880 --> 00:14:53,480
deep dive.