1
00:00:00,000 --> 00:00:02,900
Links option, you high level, 
you need to allow a group of 

2
00:00:02,900 --> 00:00:05,700
people to do successful. 
It's about a limit. 

3
00:00:05,700 --> 00:00:08,100
What is the vision? 
And then you try to align, what 

4
00:00:08,100 --> 00:00:10,000
is the MVP? 
The minimum viable product? 

5
00:00:10,000 --> 00:00:11,500
What's that? 
Very first step. 

6
00:00:11,800 --> 00:00:15,100
When you think about a minimum 
viable product, you need to 

7
00:00:15,100 --> 00:00:18,800
think about it from three 
angles, the business angle the 

8
00:00:18,800 --> 00:00:22,100
users, and then the engineers 
getting those three perspectives

9
00:00:22,100 --> 00:00:24,300
together. 
So they align and the site. 

10
00:00:24,300 --> 00:00:25,300
Okay. 
What is that? 

11
00:00:25,300 --> 00:00:31,500
Very first step. 
Hey everyone. 

12
00:00:32,000 --> 00:00:36,700
My name is Henry Surya be Robin.
And you're listening to the 

13
00:00:36,700 --> 00:00:39,900
tekhelet journal. 
The show will be bringing you 

14
00:00:39,900 --> 00:00:43,400
the greatest technical leaders 
practitioners and thought 

15
00:00:43,400 --> 00:00:46,800
leaders in the industry to 
discuss about their Journey 

16
00:00:47,100 --> 00:00:51,400
ideas and practices that we all 
can learn and apply to build a 

17
00:00:51,400 --> 00:00:55,100
highly performing technical team
and to make an impact in your 

18
00:00:55,100 --> 00:00:58,800
personal work. 
So let's dive into our Journal. 

19
00:01:03,900 --> 00:01:05,900
Hi, everyone. 
Another Goes by. 

20
00:01:05,900 --> 00:01:08,700
And I'm back here again with a 
new episode of the tekhelet 

21
00:01:08,700 --> 00:01:11,600
journal podcast. 
Thank you so much for tuning in 

22
00:01:11,700 --> 00:01:14,400
and spending your time with me 
today, listening to this 

23
00:01:14,400 --> 00:01:16,800
episode. 
If you're new, to the podcast 

24
00:01:16,900 --> 00:01:19,200
know that technology, you know, 
is available for you to 

25
00:01:19,200 --> 00:01:22,800
subscribe on major podcast apps 
such as Spotify and apple 

26
00:01:22,800 --> 00:01:27,500
podcast Google podcast, YouTube,
and many others also, check out 

27
00:01:27,500 --> 00:01:30,100
and follow technology, you know,
social media channels on 

28
00:01:30,100 --> 00:01:33,800
LinkedIn Twitter and Instagram 
and you can find amazing quotes 

29
00:01:33,800 --> 00:01:37,100
and words of wisdom. 
From every podcast episode and I

30
00:01:37,107 --> 00:01:40,500
share them on those channels to 
give us some inspiration for us 

31
00:01:40,500 --> 00:01:43,400
to get better each day. 
And if you're thinking about 

32
00:01:43,400 --> 00:01:46,900
making some contribution to the 
show and support the creation of

33
00:01:46,900 --> 00:01:51,100
this podcast, please consider 
joining as a patron by visiting 

34
00:01:51,100 --> 00:01:53,500
technology, you know, dot, f /, 
Patron. 

35
00:01:53,900 --> 00:01:57,600
I highly appreciate any kind of 
support and your contribution 

36
00:01:57,700 --> 00:02:00,400
would help me towards 
sustainably producing this show 

37
00:02:00,600 --> 00:02:03,300
every week. 
But today's episode. 

38
00:02:03,400 --> 00:02:06,300
I am happy to share my 
conversation with Paulo. 

39
00:02:06,300 --> 00:02:10,300
Caroli Paulo is a principal 
consultant at thoughtworks 

40
00:02:10,600 --> 00:02:14,600
co-founder of agile, Brazil and 
the author of the bestseller, 

41
00:02:14,600 --> 00:02:18,000
lean Inception, and the reason 
fun retrospectives. 

42
00:02:18,700 --> 00:02:21,400
I learn about lean Inception. 
When I used to work at 

43
00:02:21,400 --> 00:02:25,200
thoughtworks, and during my time
there, I found that lead 

44
00:02:25,200 --> 00:02:28,300
Inception is one of the key 
techniques that thoughtworks 

45
00:02:28,300 --> 00:02:31,500
uses in many Klein engagements 
to bring everyone. 

46
00:02:31,600 --> 00:02:35,300
Together come up with a 
successful product vision and 

47
00:02:35,300 --> 00:02:38,600
create alignment between 
multiple stakeholders involved. 

48
00:02:38,900 --> 00:02:41,100
And hence. 
Most of the projects that 

49
00:02:41,100 --> 00:02:44,600
started with an exception will 
most likely result in a 

50
00:02:44,600 --> 00:02:49,500
successful project delivery in 
this episode Paulo share with me

51
00:02:49,500 --> 00:02:51,400
the history of thought Works 
Inception. 

52
00:02:51,900 --> 00:02:55,700
How it evolved into the current 
Lynn Inception and its 

53
00:02:55,700 --> 00:02:58,000
connection With The Lean Startup
movement. 

54
00:02:58,400 --> 00:03:02,000
He also explain the similarities
and differences between Lynn 

55
00:03:02,000 --> 00:03:05,100
Inception and the other 
well-known design Sprint, 

56
00:03:05,500 --> 00:03:09,100
including the interesting story 
on how both techniques were 

57
00:03:09,100 --> 00:03:13,000
developed almost at the same 
time and why they ended up quite

58
00:03:13,000 --> 00:03:17,000
similar, but different in a few 
strategic ways Paulo. 

59
00:03:17,000 --> 00:03:20,500
Also shared an example, how to 
come up with a good product 

60
00:03:20,500 --> 00:03:24,900
Vision, the concept of MVP 
canvas and the importance of 

61
00:03:24,900 --> 00:03:29,400
Shifting, our mindset project 
mindset to product mindset in 

62
00:03:29,400 --> 00:03:31,400
the second half of our 
conversation. 

63
00:03:31,900 --> 00:03:34,600
Paolo then shared his latest 
contribution, fun 

64
00:03:34,600 --> 00:03:37,600
retrospectives, which brings 
together many different 

65
00:03:37,600 --> 00:03:40,500
techniques to conduct effective.
Retrospectives. 

66
00:03:41,300 --> 00:03:43,200
He explained. 
The reasoning behind the fund 

67
00:03:43,200 --> 00:03:45,600
techniques. 
Share some of those fun 

68
00:03:45,600 --> 00:03:48,800
activities that we all can try 
in our next retrospectives, 

69
00:03:49,100 --> 00:03:52,300
including the interesting token 
of appreciation technique. 

70
00:03:53,000 --> 00:03:55,500
He also emphasized the 
importance of psychological 

71
00:03:55,500 --> 00:03:59,500
safety and facilitation skills 
in a good retrospective. 

72
00:04:00,100 --> 00:04:03,100
And if you are interested to 
find out, My examples of fun 

73
00:04:03,100 --> 00:04:06,200
retrospectives that you can try.
You can check them out on his 

74
00:04:06,200 --> 00:04:08,700
website at fundraiser 
respectives.com. 

75
00:04:09,700 --> 00:04:12,700
I hope you will enjoy this 
episode and if you like it, 

76
00:04:12,700 --> 00:04:16,500
consider helping the show by 
living it a rating review or 

77
00:04:16,500 --> 00:04:20,300
comment on your podcast app or 
social media channels, those 

78
00:04:20,300 --> 00:04:23,400
reviews and comments are one of 
the best ways to help me get 

79
00:04:23,400 --> 00:04:27,200
this podcast to reach more 
listeners and hopefully they can

80
00:04:27,200 --> 00:04:30,000
also benefit from the contents 
in this podcast. 

81
00:04:30,400 --> 00:04:33,300
Let's get this episode. 
Started right after our short 

82
00:04:33,300 --> 00:04:36,000
sponsor message. 
Are you looking for a new cool 

83
00:04:36,000 --> 00:04:39,500
swag tekhelet Journal. 
Now offers you some swags that 

84
00:04:39,500 --> 00:04:43,300
you can purchase online. 
These wax are printed on demand 

85
00:04:43,300 --> 00:04:46,700
based on your preference and 
will be delivered safely to you 

86
00:04:46,700 --> 00:04:49,200
all over the world where 
shipping is available. 

87
00:04:49,700 --> 00:04:52,300
Check out all the cool swag is 
available by visiting 

88
00:04:52,300 --> 00:04:55,000
technology. 
No, dot f / shop, and don't 

89
00:04:55,000 --> 00:04:57,900
forget to break yourself. 
Once you receive any of those 

90
00:04:57,900 --> 00:05:03,100
tracks. 
Welcome back to a new episode of

91
00:05:03,100 --> 00:05:04,500
the package. 
You know, today. 

92
00:05:04,500 --> 00:05:07,200
I have a special guest. 
His name is Paulo Carly. 

93
00:05:07,500 --> 00:05:09,900
He's a colleague of mine last 
time in thought works. 

94
00:05:10,200 --> 00:05:12,000
So he wrote a book called lean 
inception. 

95
00:05:12,200 --> 00:05:14,800
For those of you who are not 
aware of, it is actually one of 

96
00:05:14,800 --> 00:05:18,300
the technique that works use 
still doing I guess for all 

97
00:05:18,300 --> 00:05:20,200
customers before they start a 
project. 

98
00:05:20,200 --> 00:05:22,600
They will conduct a little 
Inception and understand what 

99
00:05:22,600 --> 00:05:25,300
the products come up with the 
agreement about how to build the

100
00:05:25,300 --> 00:05:27,800
products, how to put your 
products until you come up with 

101
00:05:27,800 --> 00:05:30,100
an agreement of what kind of MVP
that you want to build. 

102
00:05:30,200 --> 00:05:33,000
It is a very good technique. 
And so I'd love to have a talk 

103
00:05:33,000 --> 00:05:35,700
today with Paulo to understand 
further, but Linens, option and 

104
00:05:35,700 --> 00:05:37,900
also to share with all of you 
Sao, Paulo. 

105
00:05:37,900 --> 00:05:40,200
Welcome to the show. 
Thanks for agreeing for this. 

106
00:05:40,900 --> 00:05:41,500
Thank you. 
Thank you. 

107
00:05:41,500 --> 00:05:43,800
It's a pleasure to be here. 
Sao, Paulo. 

108
00:05:43,800 --> 00:05:45,900
Maybe to introduce yourself in 
the beginning. 

109
00:05:45,900 --> 00:05:48,400
Maybe telling about your career 
Journey or highlights and 

110
00:05:48,400 --> 00:05:50,200
turning points. 
Sure. 

111
00:05:50,300 --> 00:05:52,200
So I'm Paulo Caroli. 
I am Brazilian. 

112
00:05:52,200 --> 00:05:56,000
I was born and raised in Rio de 
Janeiro, but I went through the 

113
00:05:56,000 --> 00:05:58,800
software engineering school. 
I did a master in Brazil, and 

114
00:05:58,800 --> 00:06:01,900
then I went to Silicon Valley 
those back in the day, so, The 

115
00:06:01,900 --> 00:06:04,600
late 90s, there was a whole fish
current of developer. 

116
00:06:04,900 --> 00:06:07,500
I used to go to the Hoops, La 
conférence a big conference in 

117
00:06:07,500 --> 00:06:09,900
us and fell in love with Silicon
Valley. 

118
00:06:09,900 --> 00:06:12,100
And one of the trips to the 
conference event acidic 

119
00:06:12,100 --> 00:06:13,900
environment, like, oh, I want to
leave here. 

120
00:06:14,000 --> 00:06:17,300
So I moved to Silicon Valley, 
spent eight years there. 

121
00:06:17,600 --> 00:06:21,700
I worked on quite a few startups
when I got in West, which was in

122
00:06:21,700 --> 00:06:25,700
2000 because of object-oriented 
is total can't pack which wrote 

123
00:06:25,700 --> 00:06:28,800
the book extreme program 
explaining and then I met him in

124
00:06:28,800 --> 00:06:31,300
2000 and then I start following 
those things. 

125
00:06:31,500 --> 00:06:34,600
That they were called the child.
It was one of the reasons that I

126
00:06:34,608 --> 00:06:37,200
went to work for fought works 
because a lot of those folks 

127
00:06:37,200 --> 00:06:39,800
quite a few of those went to 
worked for fought work. 

128
00:06:39,800 --> 00:06:42,200
So I did the same when I joined 
falters. 

129
00:06:42,200 --> 00:06:45,000
I always had that Lee startup 
thing on me like a real like 

130
00:06:45,000 --> 00:06:48,900
that side, but I also like the 
Jets on side and the pot works. 

131
00:06:48,900 --> 00:06:52,500
You should work for big clients.
Then I started traveling a lot, 

132
00:06:52,500 --> 00:06:56,000
serve organizations and move to 
Asia in Europe, back to Brazil 

133
00:06:56,400 --> 00:06:59,700
from a developer. 
I start being a facilitator. 

134
00:06:59,900 --> 00:07:01,400
One thing I realized I was 
pretty good. 

135
00:07:01,600 --> 00:07:03,900
Getting people together through 
a lie about something. 

136
00:07:04,000 --> 00:07:06,200
You should the beginning of the 
project was a very important 

137
00:07:06,200 --> 00:07:09,100
part fast for a developer who 
work for six months, one year. 

138
00:07:09,100 --> 00:07:11,800
And you don't see your product, 
like be successful. 

139
00:07:11,800 --> 00:07:13,800
It was really bad. 
And then I start getting 

140
00:07:13,800 --> 00:07:16,200
involved from the beginning 
phase, what's called an 

141
00:07:16,207 --> 00:07:18,900
exception demo. 
Well, what can we do to better 

142
00:07:18,900 --> 00:07:21,600
align, so we have a great 
success with our product, our 

143
00:07:21,600 --> 00:07:25,500
team. 
And then from 2011 forward, I 

144
00:07:25,500 --> 00:07:29,400
start to concentrate those in 
Saturn's to be more lean lean, 

145
00:07:29,400 --> 00:07:31,800
asked likely shorter and more. 
Active. 

146
00:07:31,800 --> 00:07:34,500
Imagine that tunnel with such. 
I will try to be more effective 

147
00:07:34,500 --> 00:07:39,300
now 2011, like 10 years after 
the German faster and we could 

148
00:07:39,300 --> 00:07:41,400
be even better before. 
The beginning of the bridge was 

149
00:07:41,400 --> 00:07:43,200
an exception. 
But was like, oh, let's 

150
00:07:43,200 --> 00:07:45,900
understand all the user stories 
and then installs and laugh. 

151
00:07:45,900 --> 00:07:48,400
And I realised, thanks, God. 
I used to live in Silicon Valley

152
00:07:48,400 --> 00:07:50,600
and they was following the 
movements from there. 

153
00:07:50,600 --> 00:07:53,700
We gave a name to to Lean 
Startup and we should start with

154
00:07:53,700 --> 00:07:56,000
the MVP. 
That's why the Inception it's 

155
00:07:56,000 --> 00:07:59,000
leave because of in start-up. 
It was a big shift on my career 

156
00:07:59,000 --> 00:08:01,500
and I think I'm fought works in 
the projects that I was working.

157
00:08:01,600 --> 00:08:04,100
Working nearby. 
That's why I lease option. 

158
00:08:04,400 --> 00:08:07,000
Start spreading the word around 
the globe in Brazil. 

159
00:08:07,000 --> 00:08:10,300
It's a big thing because it was 
living there thing from 2011, 

160
00:08:10,300 --> 00:08:14,800
2019, which was really good. 
And because I had three kids in 

161
00:08:14,808 --> 00:08:15,900
Brazil. 
During those years. 

162
00:08:15,900 --> 00:08:18,100
I was not traveling abroad to a 
lot. 

163
00:08:18,400 --> 00:08:20,600
So it's doing a lot of cleaning 
Setters for precision 

164
00:08:20,600 --> 00:08:22,800
components. 
So in Brazil, like everybody's 

165
00:08:22,800 --> 00:08:26,700
doing exceptional days, 2019 and
moved to Europe. 

166
00:08:27,000 --> 00:08:30,600
And now, if the remote will, I 
start doing morning settings all

167
00:08:30,600 --> 00:08:34,000
over the Globe, remotely. 
Now, I think that the word 

168
00:08:34,000 --> 00:08:37,700
spread and faster, so maybe if 
you can share, what is Lynn 

169
00:08:37,700 --> 00:08:40,700
Inception in high level summary 
for people who are not aware of 

170
00:08:40,700 --> 00:08:41,900
it? 
Sure. 

171
00:08:41,900 --> 00:08:44,700
Links option, high level. 
You need to allow a group of 

172
00:08:44,700 --> 00:08:47,200
people to do successful. 
That's it. 

173
00:08:47,200 --> 00:08:49,500
It's about a limit. 
Usually, go to a company 

174
00:08:49,500 --> 00:08:52,200
Corporation or product. 
It doesn't matter. 

175
00:08:52,300 --> 00:08:54,100
There is efficient. 
Hey, that's amazing. 

176
00:08:54,100 --> 00:08:56,400
That's a visual who we are. 
All going to be rich, very 

177
00:08:56,400 --> 00:08:59,000
successful. 
Yeah, and then what and then you

178
00:08:59,008 --> 00:09:01,400
need to align is this strategy 
like what's the path? 

179
00:09:01,800 --> 00:09:06,400
Traditionally, we would go with 
the stratagems like a long train

180
00:09:06,400 --> 00:09:08,500
wreck. 
We need to do these and these 

181
00:09:08,500 --> 00:09:11,400
and that and that we realize the
woods, not like that. 

182
00:09:11,600 --> 00:09:14,200
So only sexual life that group 
of people. 

183
00:09:14,200 --> 00:09:15,500
Okay? 
What is the vision? 

184
00:09:15,700 --> 00:09:18,100
And then we try to align, what 
is the aim to be the minimum 

185
00:09:18,100 --> 00:09:20,200
viable product? 
So we are okay with division 

186
00:09:20,200 --> 00:09:23,500
would support have division. 
But what's that very first step.

187
00:09:23,800 --> 00:09:26,700
It's very hard to lie about that
very first step because when 

188
00:09:26,700 --> 00:09:30,400
think about a minimum viable 
product, you need to think about

189
00:09:30,400 --> 00:09:33,500
it, from three. 
The business angle, which is 

190
00:09:33,500 --> 00:09:35,200
super important business behind 
it. 

191
00:09:35,200 --> 00:09:37,200
It doesn't matter if you're a 
small comparable countries, that

192
00:09:37,200 --> 00:09:40,100
business the users because you 
always build something for 

193
00:09:40,100 --> 00:09:43,500
someone to use and like, you 
want the users to love it and 

194
00:09:43,500 --> 00:09:47,100
then the engineers because you 
need to do it right when you put

195
00:09:47,100 --> 00:09:49,800
those three people together to 
figure out what is that minimum.

196
00:09:50,000 --> 00:09:52,800
It's not that easy because each 
one has different perspective 

197
00:09:52,800 --> 00:09:55,500
and they want different things. 
So nice about it, getting those 

198
00:09:55,500 --> 00:09:58,400
three perspectives together. 
So they align and the site. 

199
00:09:58,400 --> 00:10:01,800
Okay, what is that? 
Very first step and you And it's

200
00:10:01,800 --> 00:10:05,200
also a revolution since it was 
created before, right? 

201
00:10:05,300 --> 00:10:08,400
Like you mentioned the portion 
of the lean so it becomes mean 

202
00:10:08,400 --> 00:10:11,200
Inception. 
So, how do you actually combine 

203
00:10:11,200 --> 00:10:13,900
this Lean Startup movement with 
this Inception? 

204
00:10:13,900 --> 00:10:15,700
And how does this relate to 
design? 

205
00:10:15,700 --> 00:10:18,100
Thinking, to me? 
It sounds little bit similar. 

206
00:10:18,600 --> 00:10:20,600
Yeah. 
No, it's definitely has a lot of

207
00:10:20,600 --> 00:10:23,100
influence from. 
So, I think you have to put this

208
00:10:23,100 --> 00:10:25,200
in perspective. 
I was in u.s. 

209
00:10:25,200 --> 00:10:30,100
From 2000 to 2008. 
So I was there in the beginning 

210
00:10:30,100 --> 00:10:32,800
of th eye movement. 
So, How you transpose, chime 

211
00:10:32,800 --> 00:10:34,100
movement, but I wasn't 
developed. 

212
00:10:34,300 --> 00:10:37,000
So I had the pain off own 
Sprouts, not successful because 

213
00:10:37,000 --> 00:10:39,100
like a build something, and no 
one's using. 

214
00:10:39,100 --> 00:10:42,700
This is from 2000-2008 before 
that on the 90s. 

215
00:10:42,700 --> 00:10:45,500
I was object oriented person. 
So I like object-oriented 

216
00:10:45,500 --> 00:10:48,800
analysis, design implementation,
all the things that used to have

217
00:10:48,800 --> 00:10:51,100
like years ago. 
But from that, there was 

218
00:10:51,100 --> 00:10:54,200
something interesting because we
used to have Inception phase 

219
00:10:54,600 --> 00:10:56,400
Factor original created. 
Uml. 

220
00:10:56,500 --> 00:10:59,400
Another thing they create was 
the rational unified process, 

221
00:10:59,400 --> 00:11:01,400
which was a child like the 
industry. 

222
00:11:01,500 --> 00:11:05,000
Is moving towards which are more
agile and group was one of those

223
00:11:05,100 --> 00:11:07,400
first met adults that show them 
today. 

224
00:11:07,400 --> 00:11:09,100
If you look at it, like, oh, it 
was so slow. 

225
00:11:09,100 --> 00:11:11,800
But that I'm stressed. 
And then they named that 

226
00:11:11,800 --> 00:11:14,600
beginning of the understanding 
of what we need to do on a 

227
00:11:14,600 --> 00:11:18,600
project as an exception. 
So when I went to us and we 

228
00:11:18,600 --> 00:11:22,300
start with the achaia movement. 
Now, we start doing more like a 

229
00:11:22,300 --> 00:11:25,500
fat giant sections, where we 
understand everything we need to

230
00:11:25,500 --> 00:11:28,500
do for that project. 
We used to use the word closure.

231
00:11:28,700 --> 00:11:31,400
You the map it to user stories 
for it. 

232
00:11:31,700 --> 00:11:34,600
Another colleague of ours just 
that he wrote abuser start 

233
00:11:34,600 --> 00:11:36,600
mapping. 
That's from that period where we

234
00:11:36,600 --> 00:11:39,800
try to understand everything, 
the users, their Journey. 

235
00:11:39,800 --> 00:11:43,600
The business needs and remember 
everything to user stories. 

236
00:11:43,600 --> 00:11:47,100
And we do this huge release 
planning with all the Springs. 

237
00:11:47,100 --> 00:11:50,100
Those three, two, one, two, 
three, even estimate. 

238
00:11:50,100 --> 00:11:52,300
Everything. 
And have story point and has 

239
00:11:52,300 --> 00:11:55,400
burned up for own. 
We're going to deliver 300 story

240
00:11:55,400 --> 00:11:58,300
points and have that release 
plan for one year, nowadays 

241
00:11:58,300 --> 00:12:00,900
looking back. 
I'm like, wow, I was crazy to do

242
00:12:00,900 --> 00:12:02,800
that. 
Why I'm saying this because like

243
00:12:02,800 --> 00:12:05,600
in 2011, they start that 
movement is Silicon Valley. 

244
00:12:05,800 --> 00:12:08,500
They're like hey, I don't care 
about doing a charm not we 

245
00:12:08,500 --> 00:12:11,200
cannot do the product for one 
year to see if it makes sense to

246
00:12:11,200 --> 00:12:13,100
the user. 
Let's do something. 

247
00:12:13,300 --> 00:12:15,600
The minimum thing we can do to 
validate if you're going in a 

248
00:12:15,608 --> 00:12:17,500
good direction and that's the 
entropy. 

249
00:12:18,000 --> 00:12:21,400
So the link separate is a shift 
from Latin understand overall 

250
00:12:21,400 --> 00:12:23,100
project to. 
Yeah, that's talked about the 

251
00:12:23,100 --> 00:12:25,800
vision and then figure out how 
do we get started? 

252
00:12:26,000 --> 00:12:29,000
So the focus is not more on real
easy planning of the, all the 

253
00:12:29,000 --> 00:12:30,900
user Stories, the focus, like, 
okay. 

254
00:12:31,100 --> 00:12:33,400
How do we Start when you talk 
about them a bit. 

255
00:12:33,600 --> 00:12:37,000
Now the folks not that much on 
what we're all these stars 

256
00:12:37,000 --> 00:12:38,800
behind it. 
It's more like where you find 

257
00:12:38,800 --> 00:12:40,900
the day. 
What I Potter for today, you 

258
00:12:40,900 --> 00:12:44,600
know, let's talk about business,
the user experience. 

259
00:12:44,600 --> 00:12:47,200
And then the Aging your side. 
What is the minimum we can do to

260
00:12:47,200 --> 00:12:49,400
validate your going? 
A good direction, of course 

261
00:12:49,400 --> 00:12:52,900
after the except sure if you are
a software delivery team, you 

262
00:12:52,900 --> 00:12:55,600
break it, you choose. 
Sorry, but now became much 

263
00:12:55,600 --> 00:12:59,100
easier because it's much smaller
and if Parts aligned, so that's 

264
00:12:59,100 --> 00:13:01,400
the shift only exceptions like 
bringing that. 

265
00:13:01,500 --> 00:13:04,600
Start up thinking as a 
centerpiece in throat come like 

266
00:13:04,600 --> 00:13:06,500
a center result of that 
alignment. 

267
00:13:06,600 --> 00:13:11,200
And of course as a set which 
2011 design thinking as a 

268
00:13:11,200 --> 00:13:13,800
movement something that was 
getting more and more popular 

269
00:13:13,800 --> 00:13:17,000
throughout I myself and I'm 
really good facilitator, besides

270
00:13:17,000 --> 00:13:20,300
being a software engineer that 
like process and Improvement, a 

271
00:13:20,300 --> 00:13:22,700
really good facilitator. 
So I brought all of my 

272
00:13:22,700 --> 00:13:25,500
facilitation skills on cultural 
a group of people from different

273
00:13:25,500 --> 00:13:27,700
perspectives. 
You need a lot of eye skills, 

274
00:13:27,700 --> 00:13:31,200
like handling both States, the 
cluster and do a fishbowl. 

275
00:13:31,500 --> 00:13:33,500
Kind of stuff. 
The book has two sides. 

276
00:13:33,500 --> 00:13:36,000
Once like a, let's talk about 
them to be, it's very important.

277
00:13:36,000 --> 00:13:38,900
We should focus on it. 
The sequence of activities, they

278
00:13:38,900 --> 00:13:41,000
work. 
Well really well, so if you want

279
00:13:41,000 --> 00:13:43,800
to figure out, okay, how shall I
group of people do them DP? 

280
00:13:44,000 --> 00:13:46,200
You can do. 
Like, I did took me like four or

281
00:13:46,208 --> 00:13:49,700
five years to figure out a good 
segments of activities that went

282
00:13:49,700 --> 00:13:53,700
well, and I was running cetera, 
like, almost every week or you 

283
00:13:53,700 --> 00:13:56,200
follow that recipe, that you're 
going to figure out how we 

284
00:13:56,200 --> 00:13:57,900
follow these. 
We achieve great results, 

285
00:13:57,900 --> 00:13:59,900
attend. 
So that's the link steps 

286
00:13:59,900 --> 00:14:04,100
techniques of the Activities and
the sequence and why MVP with 

287
00:14:04,100 --> 00:14:06,800
some tips and ideas on, how do 
you facilitate it? 

288
00:14:07,200 --> 00:14:09,700
How about the design thinking? 
Because design thinking, I mean,

289
00:14:09,700 --> 00:14:11,800
we also have this print design, 
right? 

290
00:14:12,100 --> 00:14:15,800
Sounds like it's also similar 
time frame where you envision. 

291
00:14:15,800 --> 00:14:17,900
What do you want to build? 
And you have an MVP at the end 

292
00:14:17,900 --> 00:14:20,100
of it. 
So, what's the difference here, 

293
00:14:20,600 --> 00:14:22,300
design, Sprint. 
In Inception, right? 

294
00:14:22,500 --> 00:14:24,900
I find it fascinating, Jake a 
nap. 

295
00:14:25,000 --> 00:14:26,700
He was also in Silicon Valley, 
right? 

296
00:14:26,800 --> 00:14:28,400
I think he's a little younger 
than me. 

297
00:14:28,700 --> 00:14:31,300
I was more of a developer who 
was more of a designer. 

298
00:14:31,800 --> 00:14:34,300
You have the difference there, 
but he was leaving Silicon 

299
00:14:34,300 --> 00:14:35,700
Valley. 
We went through similar 

300
00:14:35,700 --> 00:14:37,600
companies. 
He was feeling the same pain 

301
00:14:37,600 --> 00:14:40,600
that I was trans like, damn it. 
I need to align these people to 

302
00:14:40,600 --> 00:14:42,000
figure out what they're going to
do. 

303
00:14:42,100 --> 00:14:45,000
Even as a poisonous. 
I was a consultant at Google for

304
00:14:45,000 --> 00:14:46,600
one year. 
The same time that he was there 

305
00:14:46,600 --> 00:14:48,900
as well. 
We almost work on the same thing

306
00:14:49,100 --> 00:14:51,500
was very interesting. 
If I remember in front, of 

307
00:14:51,500 --> 00:14:54,300
course, like both of us were not
famous about like remember 

308
00:14:54,300 --> 00:14:56,600
others designed to do, which I 
like his style. 

309
00:14:56,600 --> 00:14:59,300
I could see is a good 
facilitator, Google shoot. 

310
00:14:59,400 --> 00:15:01,300
So welcome different teams. 
What? 

311
00:15:01,400 --> 00:15:05,000
Happening is in common, both of 
us, use design thinking both 

312
00:15:05,000 --> 00:15:06,900
States and okay, how to align 
people. 

313
00:15:07,100 --> 00:15:09,800
The Double Diamond open the 
options and then you close some 

314
00:15:09,800 --> 00:15:12,000
options. 
Both of us, have that same Style

315
00:15:12,200 --> 00:15:14,200
Both of Us. 
Came to the conclusion that like

316
00:15:14,200 --> 00:15:17,400
do know what it is a week. 
It is a five-day thing. 

317
00:15:17,600 --> 00:15:20,100
I have time sometime whether I 
would make it or sometimes would

318
00:15:20,100 --> 00:15:22,500
make it shorter. 
If re shorter. 

319
00:15:22,600 --> 00:15:24,500
You don't have time to have a 
brainstorm. 

320
00:15:24,600 --> 00:15:27,200
It's more like if you try to do 
something in science, printer 

321
00:15:27,200 --> 00:15:30,400
Inception one day. 
Probably someone telling that's 

322
00:15:30,400 --> 00:15:33,400
what I want to go figure. 
If you have an a week, you can 

323
00:15:33,400 --> 00:15:36,000
open the options and then make a
decision process. 

324
00:15:36,000 --> 00:15:38,800
That then the thing is, like, 
from the time, I was working on 

325
00:15:38,800 --> 00:15:41,400
Google went to India and they 
were always running status for 

326
00:15:41,400 --> 00:15:42,800
UK. 
And then I went to Brazil. 

327
00:15:43,000 --> 00:15:45,500
So I was not following what he 
was doing and he was not 

328
00:15:45,500 --> 00:15:47,300
following what I was doing 
Special, that I was writing a 

329
00:15:47,308 --> 00:15:50,500
lot in Portuguese, and we came 
to a lot of similarities based 

330
00:15:50,500 --> 00:15:53,400
on practical experience. 
But the place where we do 

331
00:15:53,400 --> 00:15:55,700
virtue, where we do difference. 
And of course, this has to do 

332
00:15:55,700 --> 00:16:00,300
for backgrounds, he has that 
week about the design team. 

333
00:16:00,600 --> 00:16:02,600
So he is Is more focus on the 
design. 

334
00:16:02,600 --> 00:16:05,500
So get that people that we 
figure out the design, they will

335
00:16:05,500 --> 00:16:07,400
have some options for the 
designer. 

336
00:16:07,400 --> 00:16:10,100
Put in front of users is going 
to get like five users. 

337
00:16:10,100 --> 00:16:12,700
For example, they will test and 
then they'll decide. 

338
00:16:12,700 --> 00:16:15,400
Okay. 
We have one Winnie prototype, 

339
00:16:15,500 --> 00:16:18,800
but based on a design on 
interface at the end result. 

340
00:16:18,800 --> 00:16:21,200
It's a prototype, it comes from 
the design world. 

341
00:16:21,300 --> 00:16:23,900
I come from this doctor. 
I come from my childhood where 

342
00:16:23,900 --> 00:16:28,600
we used to have the user story, 
that's tells you exactly what's 

343
00:16:28,600 --> 00:16:31,700
the file its going to bring, how
I'm going to implement and Even 

344
00:16:31,700 --> 00:16:34,800
testing the face. 
I don't want that as an entity 

345
00:16:34,900 --> 00:16:37,200
as I named the be, I want to be 
very clear. 

346
00:16:37,800 --> 00:16:40,800
What do I want to validate? 
But I don't want to specify the 

347
00:16:40,800 --> 00:16:42,900
how so it's a big difference to 
know. 

348
00:16:42,900 --> 00:16:45,400
If at the end of the week, we 
have a prototype and use the 

349
00:16:45,400 --> 00:16:48,000
prototype for something bigger. 
That's design. 

350
00:16:48,000 --> 00:16:51,600
Sprint on the link section. 
You are like a group of people 

351
00:16:51,600 --> 00:16:55,400
of the vision and you have 
planned for them to be but you 

352
00:16:55,400 --> 00:16:58,500
do not have a prototype, use the
product for something bigger 

353
00:16:58,500 --> 00:17:01,300
MVPs, a plan for something small
that first. 

354
00:17:01,400 --> 00:17:03,100
Step. 
That's a major difference. 

355
00:17:03,300 --> 00:17:06,400
Is that strategic difference? 
If you think, you know, we're 

356
00:17:06,400 --> 00:17:09,900
going to know the big picture. 
If you are read a line about 

357
00:17:09,900 --> 00:17:13,500
what you want Zayn Springs, if 
you wanna lie about what we 

358
00:17:13,500 --> 00:17:15,800
want. 
How do we start link section or 

359
00:17:15,800 --> 00:17:17,599
you combine both and then it's 
amazing. 

360
00:17:18,099 --> 00:17:21,300
So then my next question will 
be, how often do you run? 

361
00:17:21,300 --> 00:17:23,800
This Linens option? 
Is it like if you have a new 

362
00:17:23,800 --> 00:17:25,900
product only or is it? 
Like, even if you have a 

363
00:17:25,900 --> 00:17:29,100
product, you can continuously 
run these inceptions from time 

364
00:17:29,100 --> 00:17:31,000
to time, maybe quarterly or 
something like that. 

365
00:17:31,500 --> 00:17:34,300
What's the Frequency to run? 
This kind of inception? 

366
00:17:34,800 --> 00:17:36,700
First? 
I want to bring another person 

367
00:17:36,700 --> 00:17:39,900
which I really admire his work. 
Marty cake Mark Kagan writes a 

368
00:17:39,900 --> 00:17:42,600
lot and talks a lot about 
product teams that you should 

369
00:17:42,600 --> 00:17:44,700
have a product team and 
everybody's together. 

370
00:17:44,900 --> 00:17:48,000
So, in the perfect world, if you
have a very strong product team,

371
00:17:48,000 --> 00:17:50,600
everybody's together the whole 
time, they're doing continuous 

372
00:17:50,600 --> 00:17:52,800
Discovery. 
They are line. 

373
00:17:52,800 --> 00:17:55,200
It is the same team. 
You probably don't need the 

374
00:17:55,200 --> 00:17:57,700
inside from because the team's 
aligned, they are doing 

375
00:17:57,700 --> 00:18:00,300
Discovery and they are also 
developed the product. 

376
00:18:00,400 --> 00:18:03,300
They know what they need to do. 
Do just do it continuously, but 

377
00:18:03,300 --> 00:18:06,400
it's very rare to find those 
people and sometimes difficult 

378
00:18:06,400 --> 00:18:09,400
the company to structured 
organization with product. 

379
00:18:09,400 --> 00:18:11,500
Image. 
Majority of organizations are go

380
00:18:11,500 --> 00:18:14,500
through, even though I love 
those stories about product 

381
00:18:14,500 --> 00:18:16,000
teams. 
That's what we should Aspire 

382
00:18:16,000 --> 00:18:18,400
for. 
But sometimes we're not there 

383
00:18:18,400 --> 00:18:22,100
and then we need somehow to get 
some people together chow line. 

384
00:18:22,100 --> 00:18:24,100
Okay, what we're going to do. 
What is the vision? 

385
00:18:24,100 --> 00:18:26,500
Sometimes, you do have some 
scope, we're going on. 

386
00:18:26,700 --> 00:18:29,600
So some people that they 
discover get together some 

387
00:18:29,600 --> 00:18:31,300
business people that maybe 
they're not. 

388
00:18:31,400 --> 00:18:33,900
Of the protein, do not get the 
whole time and then they change 

389
00:18:33,900 --> 00:18:35,500
years. 
Unfortunately, they are not 

390
00:18:35,500 --> 00:18:37,600
sitting together with the 
project team the whole time. 

391
00:18:37,800 --> 00:18:41,500
Then you need an exception. 
So when there is a, uh, moment, 

392
00:18:41,800 --> 00:18:45,000
new feature coming or important 
thing, that we need to align, 

393
00:18:45,200 --> 00:18:49,500
that's perfect for an inset from
if the group get aligned and it 

394
00:18:49,500 --> 00:18:51,900
is the same group. 
Probably don't need another 

395
00:18:51,900 --> 00:18:55,000
interception because the red 
line your line about the visual 

396
00:18:55,000 --> 00:18:58,300
and the MVP not about 
continuously working or people 

397
00:18:58,300 --> 00:19:00,200
teach a little bit, like it's 
normal work. 

398
00:19:00,200 --> 00:19:01,800
It's not an insect. 
Anymore. 

399
00:19:02,000 --> 00:19:04,600
If the pivot, it's a huge change
of Direction. 

400
00:19:04,700 --> 00:19:07,000
Then you need to lie again, then
you do an exception. 

401
00:19:07,300 --> 00:19:09,300
It's not like continues. 
Deliver course, content 

402
00:19:09,300 --> 00:19:10,200
Discovery. 
It is. 

403
00:19:10,200 --> 00:19:11,900
Okay. 
Let me try and get together 

404
00:19:11,900 --> 00:19:14,400
online. 
So if I understand correctly is 

405
00:19:14,400 --> 00:19:17,200
that every time you have 
probably a potential difference 

406
00:19:17,200 --> 00:19:19,800
in terms of vision and 
Alignment, you will conduct this

407
00:19:19,800 --> 00:19:21,600
Lynn Inception. 
In order to bring everybody 

408
00:19:21,600 --> 00:19:24,100
towards the same vision and 
towards the same environment in 

409
00:19:24,100 --> 00:19:27,300
order to build the same kind of 
understanding of MVP or in terms

410
00:19:27,300 --> 00:19:28,600
of product. 
Is that a correct? 

411
00:19:28,600 --> 00:19:31,200
Understanding perfect words, I 
never knew. 

412
00:19:31,400 --> 00:19:34,900
Either alya real life people 
about Visual and density. 

413
00:19:35,200 --> 00:19:38,300
That's a cultural exception and 
it's also critical to have these

414
00:19:38,300 --> 00:19:42,600
three types of people from 
Business, from The yes, and also

415
00:19:42,600 --> 00:19:45,300
from users. 
I will say it's critical to have

416
00:19:45,300 --> 00:19:49,100
those three perspectives because
sometimes you go to a start-up 

417
00:19:49,200 --> 00:19:51,300
and you do not have a lot of 
people because they're shocked 

418
00:19:51,300 --> 00:19:54,200
that even though you don't have 
the three kinds of people you 

419
00:19:54,200 --> 00:19:56,700
want to invite the three 
perspectives in the room. 

420
00:19:57,000 --> 00:19:59,600
So I did run inside for a very 
smart entrepreneur. 

421
00:19:59,900 --> 00:20:02,400
The second day where me trick 
About the personas and the 

422
00:20:02,400 --> 00:20:04,800
journeys. 
He dressed differently broadcast

423
00:20:04,800 --> 00:20:07,300
seems as if he were the Persona.
Like, I thought that amazing 

424
00:20:07,300 --> 00:20:10,000
because he was inviting the 
perspective of the users. 

425
00:20:10,200 --> 00:20:12,500
Of course, there's more to start
up, right? 

426
00:20:12,800 --> 00:20:15,200
Big companies is different 
because imp accomplice, you 

427
00:20:15,200 --> 00:20:18,400
wanna invite the people that 
represent those two respects and

428
00:20:18,400 --> 00:20:20,400
you do have sometimes more than 
one people. 

429
00:20:20,500 --> 00:20:23,000
And then the chance, like okay, 
there are people who are how 

430
00:20:23,000 --> 00:20:26,200
they align in the startup 
invited perspective, even though

431
00:20:26,200 --> 00:20:29,400
you do not have people, or I 
don't have all the engineer 

432
00:20:29,400 --> 00:20:31,200
seen, But You Wanna invite a 
date? 

433
00:20:31,400 --> 00:20:34,600
Perspective each of them. 
So maybe if you can walk through

434
00:20:34,600 --> 00:20:38,100
in terms of high level. 
What is typical agenda of Al in 

435
00:20:38,100 --> 00:20:39,900
Inception? 
Sure. 

436
00:20:39,900 --> 00:20:41,600
First. 
I like to think about it from 

437
00:20:41,600 --> 00:20:44,600
outside in first. 
What is the goal of the week? 

438
00:20:44,800 --> 00:20:46,700
What is the vision? 
And what is the MVP? 

439
00:20:47,100 --> 00:20:50,100
So if that's the goal of the 
week before that week, you need 

440
00:20:50,100 --> 00:20:53,200
to understand why I'm bringing 
the group together to talk about

441
00:20:53,200 --> 00:20:55,800
the vision. 
So problem there was a night 

442
00:20:55,800 --> 00:20:57,900
versus a lot. 
We component that use a lot of 

443
00:20:57,900 --> 00:21:00,900
project and not old style but 
more traditional approach 

444
00:21:00,900 --> 00:21:03,100
Korean. 
And finance oriented pro has a 

445
00:21:03,100 --> 00:21:05,800
portfolio of projects and send 
one of the initial hate is a 

446
00:21:05,800 --> 00:21:08,400
really good project and I'm 
like, okay got an approval. 

447
00:21:08,500 --> 00:21:11,500
And then after you get approval,
maybe the during sex, if you're 

448
00:21:11,500 --> 00:21:15,200
a company doing like Discovery, 
a lot of Discovery going on and 

449
00:21:15,200 --> 00:21:18,000
looks like by comparing those 
five different doctors. 

450
00:21:18,000 --> 00:21:20,800
This one's a winner. 
Let's do an Insight on that one.

451
00:21:21,100 --> 00:21:23,500
Show due to different sites. 
Our customers search. 

452
00:21:23,500 --> 00:21:26,600
You have a lot of customer, 
research and data and user 

453
00:21:26,600 --> 00:21:28,300
research. 
Oh cool. 

454
00:21:28,300 --> 00:21:29,900
Looks like we have something 
here. 

455
00:21:30,100 --> 00:21:32,800
Call for a link sadness. 
There's something that happened 

456
00:21:32,800 --> 00:21:35,500
before an exception or even a 
design Sprint. 

457
00:21:35,800 --> 00:21:38,000
That's the design Sprint and 
prototype of big thing. 

458
00:21:38,000 --> 00:21:40,100
Okay. 
Now, how do we start even test a

459
00:21:40,100 --> 00:21:43,000
few users but like you use now 
in each week about entropy and 

460
00:21:43,000 --> 00:21:45,700
really validated. 
So, put in the hands of the user

461
00:21:45,800 --> 00:21:48,500
only invited down to test the 
Prototype, which is amazing, but

462
00:21:48,500 --> 00:21:50,600
let's not figure out what is the
entropy that we're going to put 

463
00:21:50,600 --> 00:21:53,200
in our hands. 
So call for a new Snapdragon. 

464
00:21:53,500 --> 00:21:56,700
So I talk to about what happens 
before they go off the week 

465
00:21:56,900 --> 00:21:59,000
because there is that go of the 
week the week. 

466
00:21:59,000 --> 00:22:01,300
Need to start for kickoff. 
What's the key? 

467
00:22:01,900 --> 00:22:03,300
You tell the story of what 
happened before? 

468
00:22:03,300 --> 00:22:07,000
Hey, we're here like 10 15 
people together because this is 

469
00:22:07,000 --> 00:22:08,900
the top priority project for a 
company. 

470
00:22:08,900 --> 00:22:10,700
Here's the differing wax 
research. 

471
00:22:10,900 --> 00:22:13,500
Here's the data from the 
business request, like whatever 

472
00:22:13,500 --> 00:22:17,200
information have that's shared 
on the kickoff, and then the 

473
00:22:17,200 --> 00:22:19,900
main sponsor, whoever that 
person is probably make a 

474
00:22:19,900 --> 00:22:21,500
beautiful speech. 
Hey, we're here. 

475
00:22:21,500 --> 00:22:23,700
It's going to be amazing, the 
best team ever. 

476
00:22:23,700 --> 00:22:27,200
The best Enterprise, the best 
product, whatever, so kickoff 

477
00:22:27,200 --> 00:22:31,200
speech from the main sponsor 
information of why we're here. 

478
00:22:31,400 --> 00:22:32,700
Why did you call for these 
links? 

479
00:22:32,700 --> 00:22:35,300
74. 
Disa initiative and three. 

480
00:22:35,500 --> 00:22:38,800
You should myself or whoever's 
the facilitator to bring the 

481
00:22:38,800 --> 00:22:40,900
importance of? 
Hey, you know, what's in 

482
00:22:40,900 --> 00:22:41,800
start-up. 
Do you know what? 

483
00:22:41,800 --> 00:22:44,500
Same CPU will talk about the big
Vision, but at the end of the 

484
00:22:44,500 --> 00:22:46,500
week, you're going to have X zp 
to get. 

485
00:22:46,500 --> 00:22:48,200
There were going to follow this 
agenda. 

486
00:22:48,500 --> 00:22:50,300
So you need to bring that Master
on the agenda. 

487
00:22:50,500 --> 00:22:52,300
It's a very important message 
that you need to bring on the 

488
00:22:52,300 --> 00:22:53,900
cuff. 
Why is that? 

489
00:22:54,100 --> 00:22:56,900
Because you want to bring it up 
like hey, whoever stay in the 

490
00:22:56,900 --> 00:22:59,200
room. 
I want respect from the business

491
00:22:59,200 --> 00:23:01,300
from the users and from the 
engineer. 

492
00:23:01,700 --> 00:23:05,900
Together is not like the old 
world where someone okay, here 

493
00:23:05,900 --> 00:23:07,800
is the business. 
Requirement document. 

494
00:23:07,900 --> 00:23:10,800
Here's the data from the users. 
Here are the engineers. 

495
00:23:10,800 --> 00:23:13,200
They need to separate meetings 
and then through all those 

496
00:23:13,200 --> 00:23:16,000
documents. 
Let's hire consultancy figure 

497
00:23:16,000 --> 00:23:17,300
out and tell me what I should 
do. 

498
00:23:17,400 --> 00:23:19,100
No. 
No, we don't work like this 

499
00:23:19,100 --> 00:23:21,200
anymore. 
Yeah, let's talk about this and 

500
00:23:21,200 --> 00:23:22,800
a half price. 
Listen, let's talk about user. 

501
00:23:22,800 --> 00:23:24,100
Of course. 
Listen, let's talk about 

502
00:23:24,100 --> 00:23:26,800
engineers are very resistant. 
And then together, we are going 

503
00:23:26,800 --> 00:23:29,800
to figure out what Stanley P. 
It's not external thing that 

504
00:23:29,800 --> 00:23:32,700
some opala karate. 
He's really smart draw, all the 

505
00:23:32,700 --> 00:23:35,200
information in and at the end 
you bring the plan for them. 

506
00:23:35,300 --> 00:23:38,000
No, not at all. 
In fact, there is no such thing 

507
00:23:38,000 --> 00:23:41,000
as a perfect plan for MVP. 
The perfect thing is like, 

508
00:23:41,000 --> 00:23:43,500
people are lying about that plan
and they'll make the plan of 

509
00:23:43,500 --> 00:23:45,200
success. 
They'll make the trend of 

510
00:23:45,200 --> 00:23:48,000
success, not because they 
followed the plan because they 

511
00:23:48,000 --> 00:23:51,200
are aligned, they know what they
want, and they will pivot 

512
00:23:51,200 --> 00:23:54,600
together, especially work with 
them with me with people a lot. 

513
00:23:54,600 --> 00:23:57,300
So it's not about the plan is 
about to be aligned. 

514
00:23:57,700 --> 00:24:00,200
So that strong message is on the
cuff. 

515
00:24:00,600 --> 00:24:02,200
Now that I have this, Drug 
message. 

516
00:24:02,200 --> 00:24:06,200
Also on the cough you tell. 
Okay, Friday, 3:00 p.m. 

517
00:24:06,400 --> 00:24:09,100
We're going to have a showcase, 
a review of the week. 

518
00:24:09,200 --> 00:24:13,300
Well, it's going to be nowadays 
in Euro, whatever to use past 

519
00:24:13,300 --> 00:24:14,600
year. 
It's going to be on the walls 

520
00:24:14,600 --> 00:24:17,100
here everything we did but we're
going to show you the final 

521
00:24:17,100 --> 00:24:18,900
outcome, which is what is the 
vision? 

522
00:24:19,000 --> 00:24:21,700
What is the plan for them? 
So I invite you stakeholder, 

523
00:24:21,700 --> 00:24:24,100
that would love to be here. 
But I do know you don't have 

524
00:24:24,100 --> 00:24:26,300
time to be here because you have
other things going on. 

525
00:24:26,500 --> 00:24:29,000
I invite you to come back here 
Friday at 3 p.m. 

526
00:24:29,000 --> 00:24:31,200
And we have a conversation or it
over sessions. 

527
00:24:31,300 --> 00:24:33,900
At the presentation because I 
want to hear your input as well 

528
00:24:33,900 --> 00:24:36,100
to see if whatever plan we come 
up with. 

529
00:24:36,100 --> 00:24:38,700
It's a good plan. 
So that's the beginning and the 

530
00:24:38,700 --> 00:24:39,800
end of the week. 
Now. 

531
00:24:39,800 --> 00:24:41,700
I'm going to go day by day. 
They won. 

532
00:24:41,800 --> 00:24:44,900
It's more about understanding 
more about the business context.

533
00:24:44,900 --> 00:24:48,000
We rely invalidated business 
context to use that product 

534
00:24:48,000 --> 00:24:50,000
vision statement from Jeffrey 
Moore. 

535
00:24:50,200 --> 00:24:53,700
What is this product what? 
It's not and if possible bring a

536
00:24:53,700 --> 00:24:56,900
product perspective, right? 
We need to make that shift from 

537
00:24:56,900 --> 00:24:59,900
projects to product. 
So that's why I use the product 

538
00:24:59,900 --> 00:25:02,800
Vision to know whatever your To 
keep that as a box. 

539
00:25:02,900 --> 00:25:05,000
It is a box of product to 
deliver something. 

540
00:25:05,100 --> 00:25:06,900
What is the name that goes in 
the box? 

541
00:25:07,000 --> 00:25:10,300
If you love the product template
statement, everybody together, 

542
00:25:10,500 --> 00:25:12,700
it's different than the 
statement that comes from the 

543
00:25:12,700 --> 00:25:14,400
product manager of the product 
owner. 

544
00:25:14,400 --> 00:25:17,100
The business owner know, we are 
going to kill it together 

545
00:25:17,100 --> 00:25:19,400
because we're together here in 
the were all understood, what we

546
00:25:19,408 --> 00:25:21,600
want out of this. 
So first thing, a lot of things 

547
00:25:21,600 --> 00:25:24,300
about everybody's together. 
It's a little bit more from the 

548
00:25:24,300 --> 00:25:28,100
business perspective, right? 
They chew it's a little bit more

549
00:25:28,100 --> 00:25:31,100
from the user perspective. 
Let's share the information we 

550
00:25:31,100 --> 00:25:34,100
have about on the personas. 
If you had user research this 

551
00:25:34,100 --> 00:25:37,200
deeper in the room together and 
together we shared information. 

552
00:25:37,400 --> 00:25:39,000
It's not a presentation 
together. 

553
00:25:39,000 --> 00:25:42,200
We are drawing, who do we 
believe are the personas that we

554
00:25:42,200 --> 00:25:44,900
think will be backed by the 
singular beauty of where the 

555
00:25:44,900 --> 00:25:47,400
personas you should talk about 
before making decisions. 

556
00:25:47,800 --> 00:25:49,700
And then the Chinese were the 
user Journeys. 

557
00:25:49,700 --> 00:25:52,400
That those personas go to solve 
their problems today. 

558
00:25:53,000 --> 00:25:54,800
That's it. 
It's like they want. 

559
00:25:54,800 --> 00:25:56,900
Respect from the business that 
you perspective from the 

560
00:25:56,908 --> 00:25:59,600
personas. 
They create a freeze of product 

561
00:25:59,600 --> 00:26:01,200
attribute. 
It's a feature brainstorm. 

562
00:26:01,400 --> 00:26:03,100
Okay. 
Now that we look at the business

563
00:26:03,100 --> 00:26:06,100
goals, the Persona needs, which 
feature, should we build to 

564
00:26:06,100 --> 00:26:08,700
fulfill those business goals, 
and to help achieve those 

565
00:26:08,700 --> 00:26:10,700
personas needs? 
If you look at the journeys, it 

566
00:26:10,700 --> 00:26:13,300
might be easier to find the 
feature ideas, but it might look

567
00:26:13,300 --> 00:26:15,700
at the Persona needs at the 
business goes and that's it. 

568
00:26:15,800 --> 00:26:18,600
It's a feature brainstorming. 
You have some boundaries around 

569
00:26:18,600 --> 00:26:20,400
it. 
You're not starting with a free 

570
00:26:20,400 --> 00:26:22,200
children, instrument is very 
dangerous. 

571
00:26:22,500 --> 00:26:24,600
Sometimes you get the engineers 
and they won't start from the 

572
00:26:24,600 --> 00:26:26,400
future brainstorming from the 
technical perspective. 

573
00:26:26,400 --> 00:26:29,000
No, no, like when you put the 
future brainstormed, it's hard 

574
00:26:29,000 --> 00:26:31,800
for me to say because I'm a 
engineer myself, but When you do

575
00:26:31,800 --> 00:26:34,700
the future, brainstorm on day 
three, they're more boundaries 

576
00:26:34,700 --> 00:26:36,400
around it. 
So even if you come up with an 

577
00:26:36,400 --> 00:26:39,000
amazing technique, right? 
You like it has a mistaken idea 

578
00:26:39,000 --> 00:26:40,500
to. 
So some of the, probably 

579
00:26:40,500 --> 00:26:42,900
different abuser of the users. 
It's important to have those 

580
00:26:42,900 --> 00:26:45,200
followers. 
Otherwise, we going to glued 

581
00:26:45,200 --> 00:26:48,000
myself on that as Engineers many
times, you think about the 

582
00:26:48,008 --> 00:26:49,800
solutions before think about the
pros. 

583
00:26:50,200 --> 00:26:53,900
So when it is on day three, it 
makes you think it's more about 

584
00:26:53,900 --> 00:26:58,200
the problem than the solution 
and then it, we also start 

585
00:26:58,200 --> 00:27:00,800
making a review for each of 
those feature. 

586
00:27:00,900 --> 00:27:03,300
And that's That's its. 
I'm thinking again, you're 

587
00:27:03,300 --> 00:27:06,000
opening the office writer than 
fish grease from your opening. 

588
00:27:06,000 --> 00:27:07,700
We're not think about them to 
pee yet. 

589
00:27:07,900 --> 00:27:11,200
So it's a brainstorm and then 
they trained before you start to

590
00:27:11,200 --> 00:27:12,800
make a review of all those 
features. 

591
00:27:13,000 --> 00:27:16,600
We understand that an isolated. 
It's like small Lego bricks. 

592
00:27:17,000 --> 00:27:19,000
We know the vision. 
We don't know what Stanley be 

593
00:27:19,200 --> 00:27:21,800
but to talk about possible 
species of those rigs. 

594
00:27:21,800 --> 00:27:24,700
Those features and the review. 
Each one of them individually 

595
00:27:24,700 --> 00:27:27,500
from the perspective of the 
business, the users and the 

596
00:27:27,500 --> 00:27:31,500
technology and then what you do 
on day, five in the morning, He 

597
00:27:31,500 --> 00:27:31,800
is. 
Okay. 

598
00:27:31,800 --> 00:27:35,400
Now that we talk about often 
visual look back at those user 

599
00:27:35,400 --> 00:27:37,900
Journeys, and answer the 
question, how to improve their 

600
00:27:37,900 --> 00:27:41,000
lives with our features. 
And once we start answering this

601
00:27:41,000 --> 00:27:44,800
question, you have a sequencer 
in which order should we work on

602
00:27:44,800 --> 00:27:46,700
those features to fulfill those 
needs? 

603
00:27:47,000 --> 00:27:50,000
But wait a second. 
We are nailing section and now 

604
00:27:50,000 --> 00:27:51,500
is the time of this strategy, 
right? 

605
00:27:51,600 --> 00:27:53,800
So in all the information, how 
do you think big? 

606
00:27:53,800 --> 00:27:56,800
But start small invalidate and 
then this goes on the sequencer 

607
00:27:56,800 --> 00:27:58,600
and usually the sequencer people
go. 

608
00:27:58,600 --> 00:28:01,200
Oh, I think he is the MVP, but 
people need to talk about. 

609
00:28:01,400 --> 00:28:03,600
What is the next increment? 
What do you think will come 

610
00:28:03,600 --> 00:28:04,300
after? 
That? 

611
00:28:04,500 --> 00:28:07,500
It's also part of the strategy 
even though we will focus on 

612
00:28:07,500 --> 00:28:10,100
them to be the following week, 
the business trip. 

613
00:28:10,100 --> 00:28:13,200
Especially we need a strategy. 
That's not only the first step. 

614
00:28:13,200 --> 00:28:15,800
Your first lap is also 
influenced by what we think we 

615
00:28:15,800 --> 00:28:18,100
have enough. 
And then from that you go to the

616
00:28:18,100 --> 00:28:21,100
MVP canvas, which goes in 
Greater detail about that very 

617
00:28:21,100 --> 00:28:23,600
first step. 
And that's the final day they 

618
00:28:23,600 --> 00:28:27,800
five and showcase. 
So if I can summarize probably 

619
00:28:27,800 --> 00:28:30,500
from the beginning, you have the
kickoff from the project 

620
00:28:30,500 --> 00:28:32,600
sponsor. 
I think the right mind set, the 

621
00:28:32,600 --> 00:28:35,700
right goal for everybody within 
this Inception workshop. 

622
00:28:35,800 --> 00:28:38,300
And then, on day one, you talked
about the business, you set up 

623
00:28:38,300 --> 00:28:41,600
the vision, what the product is 
all about, and set a vision that

624
00:28:41,600 --> 00:28:44,900
everybody agrees, they to is 
about user perspective. 

625
00:28:44,900 --> 00:28:48,100
Understand sona's, user Journeys
involved. 

626
00:28:48,300 --> 00:28:51,200
They tree is about feature 
brainstorming what this product 

627
00:28:51,200 --> 00:28:53,600
would have in terms of 
capabilities and features. 

628
00:28:53,900 --> 00:28:57,000
And The crucial thing is about 
setting the boundaries not to 

629
00:28:57,000 --> 00:28:59,400
come up with the features 
without Vision, but coming up 

630
00:28:59,400 --> 00:29:03,200
from Vision into the future. 
Yes, and then they for you do 

631
00:29:03,200 --> 00:29:06,800
some kind of review from the tag
from the ux, from the business 

632
00:29:06,800 --> 00:29:09,100
perspective. 
And then on day 5, you agree. 

633
00:29:09,100 --> 00:29:12,300
What kind of MVP that you want 
to build, including the sequence

634
00:29:12,300 --> 00:29:15,000
of the pictures that you want to
build and then the last 

635
00:29:15,000 --> 00:29:17,000
deliverable will be the MVP 
conference. 

636
00:29:17,700 --> 00:29:19,400
Exactly. 
Well, when your party thing 

637
00:29:19,400 --> 00:29:22,500
about the tree is, if your 
product, it's a little more 

638
00:29:22,500 --> 00:29:25,100
technical data, we might get a 
little more technical as well. 

639
00:29:25,200 --> 00:29:27,800
It's okay, when you do the 
freaky brainstorm, as engineer 

640
00:29:27,800 --> 00:29:30,800
know that, sometimes we need to 
get into some technical details.

641
00:29:30,900 --> 00:29:34,000
It's Okay, don't get into too 
much detail because you don't 

642
00:29:34,000 --> 00:29:35,200
know yet. 
What's 1050? 

643
00:29:35,400 --> 00:29:38,900
Because our first level just for
us to understand those those 

644
00:29:38,900 --> 00:29:41,400
blocks. 
And all those features make 

645
00:29:41,400 --> 00:29:43,800
sense in terms of vision. 
You mentioned, there's a 

646
00:29:43,800 --> 00:29:47,100
template that you came up with. 
So maybe if you can share 

647
00:29:47,100 --> 00:29:51,000
because to me Vision sounds a 
little bit vague right about so 

648
00:29:51,000 --> 00:29:54,600
many things but what is a good 
template for division? 

649
00:29:54,700 --> 00:29:57,900
The first thing you realize is 
Visions way, I'm not talk about 

650
00:29:57,900 --> 00:29:59,500
the organization of these. 
You think this is very 

651
00:29:59,500 --> 00:30:01,100
important. 
I'm talk more about that. 

652
00:30:01,300 --> 00:30:03,400
Product vision and I like the 
word product. 

653
00:30:03,400 --> 00:30:07,200
It's not a project, the product,
even if you are within a project

654
00:30:07,200 --> 00:30:09,200
scope, you need to figure out 
and building something. 

655
00:30:09,200 --> 00:30:11,100
What is this? 
Sometimes people are not very 

656
00:30:11,100 --> 00:30:13,200
sure. 
We're building at Microsoft's, 

657
00:30:13,200 --> 00:30:15,000
know it. 
What are you building 

658
00:30:15,300 --> 00:30:17,400
imaginative is in a box. 
Where is the box? 

659
00:30:17,700 --> 00:30:21,300
Who are you building for? 
What needs do these people have?

660
00:30:21,500 --> 00:30:23,400
What is different from what you 
have today? 

661
00:30:23,700 --> 00:30:26,600
What is the main thing that in 
your beauty is bringing to this 

662
00:30:26,600 --> 00:30:29,900
people. 
So Jeffrey Moore jeffandmarie is

663
00:30:29,900 --> 00:30:32,900
amazing writer. 
I really liked his work on his 

664
00:30:32,900 --> 00:30:36,200
book, Crossing the cows. 
He was really good on the early 

665
00:30:36,200 --> 00:30:39,600
adopters on that graph that he 
makes like, oh, you have their 

666
00:30:39,600 --> 00:30:42,200
doctors and then you need to go 
to the early majority. 

667
00:30:42,500 --> 00:30:44,200
It's hard. 
That's where the links are for 

668
00:30:44,200 --> 00:30:47,200
kind of fit. 
We kind of already agree that 20

669
00:30:47,200 --> 00:30:49,900
think we have a solution to do 
you have that on the kickoff? 

670
00:30:50,500 --> 00:30:52,200
How's the tell me? 
What is the product? 

671
00:30:52,400 --> 00:30:54,900
So he has a product Vision 
template. 

672
00:30:55,200 --> 00:30:58,400
So the template I use is from 
Jeffrey's more, which is amazing

673
00:30:58,800 --> 00:31:01,100
Reddit in go, his book from 
1991. 

674
00:31:01,600 --> 00:31:05,200
The template goes like this for,
that's what I find. 

675
00:31:05,200 --> 00:31:07,000
It's amazing. 
I don't even think it's 

676
00:31:07,000 --> 00:31:08,000
grammatically. 
Correct. 

677
00:31:08,000 --> 00:31:10,500
In English. 
You start the sentence for who 

678
00:31:10,600 --> 00:31:12,400
is this thing that you come up 
with? 

679
00:31:12,800 --> 00:31:18,100
Who were they nice that these 
people have for, who, the, what 

680
00:31:18,100 --> 00:31:19,700
is the name of the thing? 
Your beauty? 

681
00:31:19,800 --> 00:31:22,200
Give it a name and then, like, a
product means, any more like 

682
00:31:22,200 --> 00:31:24,700
that box needs a name. 
What is that box? 

683
00:31:24,700 --> 00:31:27,900
It's a mobile app. 
It's a collection of apis. 

684
00:31:28,100 --> 00:31:29,900
It's a data mesh. 
What is it? 

685
00:31:30,100 --> 00:31:32,800
Because sometimes we confuse it.
Product is a project. 

686
00:31:32,800 --> 00:31:34,400
It's a team. 
What is it? 

687
00:31:34,700 --> 00:31:38,100
That were the main 
characteristic of that thing or 

688
00:31:38,100 --> 00:31:42,000
those people today, without that
boxer, put in front of them, our

689
00:31:42,000 --> 00:31:44,100
product? 
What is the main differentiator?

690
00:31:44,500 --> 00:31:47,000
I find that template amazing 
because it forces you to think 

691
00:31:47,000 --> 00:31:50,600
about all those perspectives to 
start with few start from there.

692
00:31:50,900 --> 00:31:53,000
So I'm not going from the 
organization's Vision 

693
00:31:53,000 --> 00:31:55,000
perspective. 
I'm not going for all the teams 

694
00:31:55,000 --> 00:31:58,700
aligned on that box because 
later on at the end of the week,

695
00:31:58,800 --> 00:32:01,200
I want to even a smaller boxes, 
not even a bottle. 

696
00:32:01,400 --> 00:32:04,300
The MGP, but I need to start 
from somewhere, but I'm not 

697
00:32:04,300 --> 00:32:06,200
going to start from somewhere. 
You Joe. 

698
00:32:06,200 --> 00:32:09,700
What's the organization of these
old Tesla of issues to make this

699
00:32:09,700 --> 00:32:11,800
a better world through the 
environmental? 

700
00:32:12,000 --> 00:32:14,600
Yes, talk about the product 
creation, put this in 

701
00:32:14,600 --> 00:32:17,500
perspective, the shift from 
product to product as a product.

702
00:32:17,500 --> 00:32:20,000
That's why I like Market Kagan 
because you talk about product 

703
00:32:20,000 --> 00:32:22,400
team, just like data as a 
product. 

704
00:32:22,400 --> 00:32:24,700
Like, that's the thing like we 
need to think about those 

705
00:32:24,700 --> 00:32:26,900
solutions that were building as 
a product. 

706
00:32:27,100 --> 00:32:29,700
And Denise have started. 
What is the product Vision? 

707
00:32:30,200 --> 00:32:32,600
Really be can give an Example 
because just now when you 

708
00:32:32,600 --> 00:32:35,000
describe it, it's a little bit 
like in pieces, right? 

709
00:32:35,000 --> 00:32:38,300
So maybe if you can take one 
product example, and come up 

710
00:32:38,300 --> 00:32:42,100
with the hypothetical vision for
us to understand better, if 

711
00:32:42,100 --> 00:32:44,400
that's okay. 
I can also view it from the 

712
00:32:44,400 --> 00:32:47,600
clients because great majority 
of the Inception of the clients,

713
00:32:47,600 --> 00:32:49,700
right? 
With disclosure their product. 

714
00:32:49,700 --> 00:32:53,200
We just I'll give you a from the
book for people that like 

715
00:32:53,200 --> 00:32:57,400
playing soccer who need to find 
other colleagues to play. 

716
00:32:57,400 --> 00:33:01,200
After work hours, the finder 
soccer. 

717
00:33:01,400 --> 00:33:05,900
Colleagues at is a mobile app 
that helps connect people to 

718
00:33:05,900 --> 00:33:10,300
play soccer after work hours or 
at lunch time unlike well 

719
00:33:10,600 --> 00:33:13,500
getting fat because it did not 
find the people or like sending 

720
00:33:13,500 --> 00:33:15,800
messages on generic WhatsApp 
group and place. 

721
00:33:15,800 --> 00:33:19,900
Good groups. 
Our rad will connect you to 

722
00:33:20,000 --> 00:33:23,900
people nearby that have the same
problem and it should play that 

723
00:33:23,900 --> 00:33:24,900
game. 
At the end of the day. 

724
00:33:25,600 --> 00:33:28,800
That's a product Creation. 
In fact, it did happen in one of

725
00:33:28,800 --> 00:33:31,200
the Inception but was for a 
community Brazil longer. 

726
00:33:32,000 --> 00:33:34,900
They create a mobile app for 
that, and of course, it's only 

727
00:33:34,900 --> 00:33:36,800
the vision, right? 
We haven't talked about them. 

728
00:33:36,800 --> 00:33:39,000
You can anything, but it get us 
started. 

729
00:33:39,200 --> 00:33:42,700
Get it started as the business 
perspective to users and the 

730
00:33:42,700 --> 00:33:45,600
technical respect and you should
go through all the actives and a

731
00:33:45,600 --> 00:33:48,500
week at the end of the week, you
have for them to pee. 

732
00:33:49,300 --> 00:33:50,900
Thanks for giving the 
illustration. 

733
00:33:51,100 --> 00:33:53,800
So, the other thing that I find,
very interesting from Lynn 

734
00:33:53,800 --> 00:33:56,700
Inception is the concept of this
MVP canvas. 

735
00:33:57,000 --> 00:34:00,300
Maybe you can share a bit. 
What is MVP canvas, starts 

736
00:34:00,300 --> 00:34:02,700
running exceptions. 
Also, and 11 and culture works 

737
00:34:02,700 --> 00:34:04,900
in Brazil. 
We have Potter Porto Alegre, 

738
00:34:04,900 --> 00:34:08,199
where I was working at 200 
people is a city in the South. 

739
00:34:08,199 --> 00:34:10,699
We had for example, and 
portraits received to other 

740
00:34:10,699 --> 00:34:14,000
cities and I was invited to run 
all the exceptions tell great. 

741
00:34:14,000 --> 00:34:17,600
Majority of them the teams that 
I would run the reception 

742
00:34:17,600 --> 00:34:20,100
support legs in the South 
majority of pressure from some 

743
00:34:20,100 --> 00:34:23,199
pole will travel some power on 
and Inception and those things 

744
00:34:23,199 --> 00:34:25,800
would come back to Porto Alegre 
where I was living and working. 

745
00:34:26,300 --> 00:34:28,900
They would go better to the 
teams that were in receiving 

746
00:34:29,100 --> 00:34:31,199
even though I was running the 
same insect. 

747
00:34:31,500 --> 00:34:33,199
And I was like why is this 
happened? 

748
00:34:33,500 --> 00:34:36,500
And then I realized that the 
weeks after the Inception I 

749
00:34:36,500 --> 00:34:38,699
would walk by the name of the 
item select. 

750
00:34:38,699 --> 00:34:40,900
Hey, how's that? 
And we be doing how are you 

751
00:34:40,900 --> 00:34:43,800
validating them to be? 
Because we only set to talk 

752
00:34:43,800 --> 00:34:45,400
about the building blocks of 
time, the p.m. 

753
00:34:45,400 --> 00:34:47,699
Like, okay. 
Now you're getting close like 

754
00:34:47,699 --> 00:34:50,300
how you're releasing. 
Are you open it to all a 

755
00:34:50,300 --> 00:34:52,800
specific group of you? 
For your courage to hold clients

756
00:34:52,800 --> 00:34:55,199
database? 
Which part of the journey, 

757
00:34:55,199 --> 00:34:58,100
sorry, validating with them the 
because on except a couple of 

758
00:34:58,100 --> 00:34:59,800
turns, but then people is very 
full. 

759
00:34:59,800 --> 00:35:01,700
Right? 
And I would go like Like, what 

760
00:35:01,700 --> 00:35:03,800
is the expected result for the 
MVP? 

761
00:35:03,900 --> 00:35:06,500
Not for the product? 
Okay, that and would be that 

762
00:35:06,500 --> 00:35:07,400
you're releasing. 
Now. 

763
00:35:07,600 --> 00:35:10,600
What do you want? 
I want everybody to play soccer 

764
00:35:10,600 --> 00:35:13,000
or like that one. 
What do I measure on that? 

765
00:35:13,000 --> 00:35:15,200
Empty P. 
That MP has very few features. 

766
00:35:15,400 --> 00:35:17,900
What are the metrics that are 
plugged in to verify it? 

767
00:35:18,200 --> 00:35:21,100
So I realized that I was making 
questions that I should have 

768
00:35:21,100 --> 00:35:23,800
left them written down during 
the link section. 

769
00:35:24,100 --> 00:35:26,400
Even though I would make all 
those questions, the Inception 

770
00:35:26,400 --> 00:35:29,300
do just vanish after that, 
because the teams would go the 

771
00:35:29,300 --> 00:35:32,400
next week and build user stories
and The backlog of work, and 

772
00:35:32,400 --> 00:35:34,100
that's it. 
And then you go and delivery 

773
00:35:34,100 --> 00:35:36,500
mode and you do lose a little 
bit of that strategy. 

774
00:35:36,900 --> 00:35:41,000
So I decide to bring this as a 
canvas on the link section and 

775
00:35:41,000 --> 00:35:42,900
then all the things would come 
some dealing exception. 

776
00:35:43,100 --> 00:35:47,200
So, when they go to their table 
and you sit together and have to

777
00:35:47,200 --> 00:35:50,000
know the sequencer in the 
backlog of work next to it, they

778
00:35:50,000 --> 00:35:52,700
would have them campus. 
All they know is that bridge of 

779
00:35:52,700 --> 00:35:55,400
okay, why we're building these 
and how we're going to solve the

780
00:35:55,400 --> 00:35:58,100
results or how you're going to 
get information. 

781
00:35:58,100 --> 00:36:01,100
So then we can converse has 
seven blocks one. 

782
00:36:01,300 --> 00:36:04,400
What is the impurity proposal? 
Which very narrow focus on them 

783
00:36:04,400 --> 00:36:07,600
that they write the proposal of 
these MVPs to validate if 

784
00:36:07,600 --> 00:36:10,900
people, from that neighborhood, 
Who download that something 

785
00:36:10,900 --> 00:36:12,600
really small? 
It's documented. 

786
00:36:12,600 --> 00:36:13,600
Personas. 
Okay. 

787
00:36:13,800 --> 00:36:17,000
For all the persons over, talk 
only about amateur soccer 

788
00:36:17,000 --> 00:36:19,200
players from neighbor or not, 
talk about them, or 

789
00:36:19,200 --> 00:36:22,300
professional, the people that 
own soccer fields, that want to 

790
00:36:22,300 --> 00:36:24,600
make some money renting, then 
maybe the coaches. 

791
00:36:24,800 --> 00:36:26,600
No. 
No, this one's only for amateur 

792
00:36:26,600 --> 00:36:28,700
soccer players, not all over 
Brazil. 

793
00:36:28,700 --> 00:36:31,200
Only that one neighborhood where
I have one soccer. 

794
00:36:31,400 --> 00:36:33,900
That I could rent, the user 
Journeys. 

795
00:36:33,900 --> 00:36:36,500
What are the user Journeys that 
their impact on this MVP? 

796
00:36:36,500 --> 00:36:39,700
Well, this empathy. 
It's only finding other people 

797
00:36:39,700 --> 00:36:42,100
to play with you. 
We cannot share the view. 

798
00:36:42,100 --> 00:36:44,700
You cannot do this and that, and
that you cannot create a 

799
00:36:44,700 --> 00:36:46,000
tournament. 
It's only that one. 

800
00:36:46,100 --> 00:36:48,100
It's very specific or talk about
entropy. 

801
00:36:48,400 --> 00:36:51,300
Okay, what are the features? 
Our workout is that we need to 

802
00:36:51,300 --> 00:36:54,200
get it solved on this empty p 0.
We need to make the good of form

803
00:36:54,200 --> 00:36:57,600
work, but when I connect with 
WhatsApp, we want to be calling 

804
00:36:57,600 --> 00:36:59,500
people, so, okay. 
We need at least integration 

805
00:36:59,500 --> 00:37:02,000
with Google form WhatsApp. 
You Detailed the work. 

806
00:37:02,000 --> 00:37:05,600
Which did what to expect result.
Well, damn it. 

807
00:37:05,700 --> 00:37:07,200
Okay. 
Are going to make this work. 

808
00:37:07,600 --> 00:37:10,400
Oh, we should hire Edwards on 
Google for that neighborhood. 

809
00:37:10,400 --> 00:37:13,100
Okay, cool. 
So let's hire like $200 on that 

810
00:37:13,100 --> 00:37:16,600
words. 
So, $200 with these, we can buy 

811
00:37:16,600 --> 00:37:20,400
100,000, click to raise to 
expect that at least 10% of 

812
00:37:20,400 --> 00:37:22,900
those will click. 
And from those of the least, and

813
00:37:23,100 --> 00:37:27,000
these number of downloads that 
and schedule match, qu you in a 

814
00:37:27,008 --> 00:37:29,800
second, but we should have the 
any passive they play the match.

815
00:37:29,800 --> 00:37:32,800
We should contact them, or Going
to contact them know, we figure 

816
00:37:32,800 --> 00:37:34,300
out. 
It's a message know, we can call

817
00:37:34,300 --> 00:37:37,200
them so that you people. 
Okay, we expect then it has to 

818
00:37:37,200 --> 00:37:40,900
be at least this number. 
So, you know the Matrix and once

819
00:37:40,900 --> 00:37:43,400
you know all of this, what is 
the cost and schedule? 

820
00:37:43,700 --> 00:37:46,800
Oh Constance guys. 
Well, 200 bucks for the Google 

821
00:37:46,800 --> 00:37:48,900
ads. 
Well, we need the team. 

822
00:37:48,900 --> 00:37:51,100
No, don't need the team. 
We can do this ourselves. 

823
00:37:51,100 --> 00:37:52,900
Only three weeks we can get this
done. 

824
00:37:52,900 --> 00:37:55,300
And after it's done. 
We need at least one month 

825
00:37:55,300 --> 00:37:57,700
collecting data to decide the 
next steps. 

826
00:37:58,000 --> 00:37:59,800
That's called cause a schedule. 
That's it. 

827
00:37:59,800 --> 00:38:03,200
That's your chemist. 
It's very narrow Focus or them. 

828
00:38:04,200 --> 00:38:07,200
Yeah, if I can probably try to 
summarize so there are seven 

829
00:38:07,200 --> 00:38:09,400
different key things in the MVP 
canvas. 

830
00:38:09,700 --> 00:38:12,600
The first is was the MVP all 
about maybe the vision of that 

831
00:38:12,600 --> 00:38:16,200
particular MVP is not the whole 
product, definitely and then who

832
00:38:16,200 --> 00:38:19,700
are the personas involved and 
what kind of musician is that? 

833
00:38:19,700 --> 00:38:23,700
You will build as part of that 
and BP the features that you 

834
00:38:23,800 --> 00:38:27,400
committed to build for this MVP.
And then what is the expected 

835
00:38:27,400 --> 00:38:31,000
results or what are the expected
results that you want to achieve

836
00:38:31,000 --> 00:38:33,300
with? 
Mdp, and then you will have to 

837
00:38:33,300 --> 00:38:36,600
find out some metrics in order 
to validate those results. 

838
00:38:36,800 --> 00:38:40,400
And then the last point is about
cost and schedule like how much 

839
00:38:40,400 --> 00:38:43,600
cause you need to build and how 
long the time required to build 

840
00:38:43,600 --> 00:38:46,100
the product. 
So Paula, I know that you also 

841
00:38:46,100 --> 00:38:48,700
wrote another book called fund 
retrospectives, right? 

842
00:38:48,700 --> 00:38:51,600
So the word fun here is very 
interesting because many people 

843
00:38:51,600 --> 00:38:54,800
know about retrospectives, but 
why specifically fun 

844
00:38:54,800 --> 00:38:56,800
retrospectives? 
Yeah. 

845
00:38:56,800 --> 00:38:58,700
In fact, like I said, I have to 
live like this link. 

846
00:38:58,700 --> 00:39:02,200
Second favorite respected. 
It's just my Things are and both

847
00:39:02,200 --> 00:39:04,100
of them. 
Put people at the center, right?

848
00:39:04,100 --> 00:39:06,200
As a lot of facilitation, but 
like putting people at the 

849
00:39:06,200 --> 00:39:08,800
center of the dough, making 
decisions or improving the way 

850
00:39:08,800 --> 00:39:12,000
they work with respects to 
influenced by scrum as it was 

851
00:39:12,000 --> 00:39:13,600
really smart. 
When they said a you should 

852
00:39:13,600 --> 00:39:15,700
always have a respect in your 
streets. 

853
00:39:15,900 --> 00:39:18,300
You should have one 
retrospective per week because 

854
00:39:18,300 --> 00:39:21,000
sometimes don't you scramble 
should have retrospect per week.

855
00:39:21,200 --> 00:39:22,800
Is that continuous Improvement 
moment? 

856
00:39:22,800 --> 00:39:24,500
There. 
Were you get together for team? 

857
00:39:24,500 --> 00:39:27,900
And say, hey, let's listen to 
each other and see, how can we 

858
00:39:27,900 --> 00:39:31,000
be more effective as a group. 
It's a moment to listen to each 

859
00:39:31,000 --> 00:39:34,000
other. 
To look for process improvements

860
00:39:34,000 --> 00:39:36,500
but a lot of the tests should 
going to people improvements. 

861
00:39:36,700 --> 00:39:39,600
It's almost like if you go to 
therapy every week is that one 

862
00:39:39,600 --> 00:39:43,100
hour of your therapy, but a 
group thing for that reason, 

863
00:39:43,100 --> 00:39:45,300
many times you get the group 
together. 

864
00:39:45,400 --> 00:39:48,700
We work on software delivery. 
The glass is always half full. 

865
00:39:49,000 --> 00:39:52,900
It's never. 
The glass is filled know. 

866
00:39:52,900 --> 00:39:56,900
It's always half full and for 
some reason, you get people 

867
00:39:56,900 --> 00:40:01,100
together my reservations, that 
have a tendency to focus on the 

868
00:40:01,200 --> 00:40:04,600
- thing we have a tennis jaw 
say, oh, look the glass 

869
00:40:04,600 --> 00:40:06,700
half-full. 
We never celebrate the glasses. 

870
00:40:07,000 --> 00:40:09,200
We all said the glass half-empty
not have food. 

871
00:40:09,200 --> 00:40:11,000
So I put the word there for two 
reasons. 

872
00:40:11,000 --> 00:40:14,800
Once hey, you should celebrate 
the achievements and teams when 

873
00:40:14,800 --> 00:40:18,400
they're happy to deliver more. 
So if you celebrate that, the 

874
00:40:18,400 --> 00:40:20,300
glass is half, who is? 
Much better than if you keep on 

875
00:40:20,300 --> 00:40:22,700
saying, what do you do to fill 
up the other half? 

876
00:40:23,000 --> 00:40:26,900
So, the funder one is strike one
to remember, to celebrate the 

877
00:40:26,900 --> 00:40:30,700
achievements and to make it a 
light environment because we do 

878
00:40:30,700 --> 00:40:32,800
need to talk. 
To both problems as well. 

879
00:40:33,000 --> 00:40:36,700
It is important, but in order to
be effective and bring difficult

880
00:40:36,700 --> 00:40:40,200
conversations, it needs to be a 
friendly environment. 

881
00:40:40,500 --> 00:40:43,300
So before getting to, hey, 
Henry, how are you doing? 

882
00:40:43,300 --> 00:40:45,400
I need to talk about a problem 
like, hello. 

883
00:40:45,400 --> 00:40:47,700
This is the context, let Heaven 
sighs. 

884
00:40:47,700 --> 00:40:49,800
Let's laugh. 
Let's relax. 

885
00:40:50,100 --> 00:40:53,400
Let's talk about the prime 
directive and then maybe not, 

886
00:40:53,400 --> 00:40:54,800
maybe we're going to bring the 
problem. 

887
00:40:54,800 --> 00:40:57,700
But like now, the environments 
is more of a light heart. 

888
00:40:58,200 --> 00:41:01,400
So that is why the front showed 
up there and also our colleague,

889
00:41:01,400 --> 00:41:04,100
Pat Kwa. 
We were together for a few years

890
00:41:04,400 --> 00:41:06,400
and he also is really good, the 
retrospect. 

891
00:41:06,400 --> 00:41:09,600
He also has a book on 
retrospective and when I was 

892
00:41:09,600 --> 00:41:12,900
selecting the name of the book 
and the website and I like, they

893
00:41:12,900 --> 00:41:15,000
pat, I need the name. 
What should I call it? 

894
00:41:15,200 --> 00:41:17,300
Then? 
It'll follow you because make 

895
00:41:17,300 --> 00:41:20,200
the retrospectives more fun, 
even though we talk about 

896
00:41:20,200 --> 00:41:23,000
serious stuff like whenever 
you're facilitate you make it 

897
00:41:23,000 --> 00:41:26,000
fun, make it light. 
I'm not go far with respect to 

898
00:41:26,000 --> 00:41:28,900
thank you and then it became Our
perspectives. 

899
00:41:29,400 --> 00:41:32,000
Thanks for sharing the story. 
So you mentioned a couple of 

900
00:41:32,000 --> 00:41:34,100
things, very interesting. 
The first thing is about 

901
00:41:34,100 --> 00:41:36,700
celebration, right? 
So what are some of the probably

902
00:41:36,700 --> 00:41:40,200
examples of activities that you 
can do to come up with this 

903
00:41:40,200 --> 00:41:43,700
celebration within a team? 
Once very simple, look, you go 

904
00:41:43,700 --> 00:41:46,100
to retrospect. 
Usually, like split the born 

905
00:41:46,100 --> 00:41:50,600
into two or three areas or for 
when you split the board into 

906
00:41:50,600 --> 00:41:55,200
Aries named one of theirs. 
Thank you and then say, hey on 

907
00:41:55,200 --> 00:41:57,800
here, please write down. 
Thank you, notes jerk. 

908
00:41:57,900 --> 00:42:00,400
Colleagues write down. 
Why do you want to thank them 

909
00:42:00,400 --> 00:42:02,600
for usual respects about a 
period? 

910
00:42:02,600 --> 00:42:06,100
Like thank you or named one of 
theirs accomplishment. 

911
00:42:06,200 --> 00:42:08,200
That's right down the 
accomplishments we did during 

912
00:42:08,200 --> 00:42:10,300
this period. 
That super simple like I'm not 

913
00:42:10,300 --> 00:42:14,200
even tell you exactly what 
retrospect activities but 

914
00:42:14,200 --> 00:42:17,700
whatever retrospective style 
Gore activity is Select think 

915
00:42:17,700 --> 00:42:21,200
about F1 error for thing for 
acknowledgement for 

916
00:42:21,200 --> 00:42:24,400
accomplishment as you asked for 
it people want, right? 

917
00:42:24,400 --> 00:42:27,200
I think it's human nature. 
We will talk about the problems 

918
00:42:27,400 --> 00:42:29,700
if you're going. 
About the problems have one area

919
00:42:29,700 --> 00:42:33,400
and say thank you another one, 
active super simple. 

920
00:42:33,700 --> 00:42:36,900
This was more fun presidential, 
bring a box of chocolate. 

921
00:42:37,100 --> 00:42:41,400
And then you named it, a token 
of appreciation then introduce 

922
00:42:41,400 --> 00:42:44,400
it as a facilitator. 
Hey, once part of the respective

923
00:42:44,400 --> 00:42:45,900
we are going to appreciate each 
other. 

924
00:42:45,900 --> 00:42:49,000
So I have a chocolate box here. 
Let's please form a circle. 

925
00:42:49,100 --> 00:42:53,100
I'm going to start. 
I wanna appreciate Henry for 

926
00:42:53,100 --> 00:42:54,400
that day. 
All day. 

927
00:42:54,400 --> 00:42:57,700
Sprint planning. 
He was really helpful to me. 

928
00:42:57,900 --> 00:43:00,700
When he brought these lights and
show done, all the things we did

929
00:43:00,700 --> 00:43:02,000
last week. 
So Henry, thank you. 

930
00:43:02,000 --> 00:43:04,000
And then, I walk too, hairy for 
box of chocolate. 

931
00:43:04,000 --> 00:43:08,500
Harry, get one chocolate and now
you appreciate someone else. 

932
00:43:08,500 --> 00:43:11,800
And then you give him that 
person a chocolate and verbally.

933
00:43:11,800 --> 00:43:13,700
Tell why you're doing it. 
It's amazing. 

934
00:43:13,700 --> 00:43:16,200
The result going face-to-face. 
Thank each other. 

935
00:43:16,200 --> 00:43:19,900
In front of the group that boost
the group, more of, its amazing.

936
00:43:20,200 --> 00:43:22,000
Simple. 
Some box office equipment. 

937
00:43:22,200 --> 00:43:25,300
I just feel bad because until 
now I didn't find remote 

938
00:43:25,300 --> 00:43:28,600
automated like you could say, 
thank you, but like Chocolate 

939
00:43:28,600 --> 00:43:31,400
taste, how do we make it happen 
to remotely do? 

940
00:43:31,400 --> 00:43:33,400
How would you do it remotely? 
Because these days. 

941
00:43:33,400 --> 00:43:35,900
Everyone is remote, right? 
Yeah. 

942
00:43:35,900 --> 00:43:38,800
I did that one remote, like you 
made a circle and we're all new 

943
00:43:38,800 --> 00:43:41,400
reference like to put the 
people's Avatar in circle. 

944
00:43:41,500 --> 00:43:44,200
And then it's time like one 
person would walk with a flower 

945
00:43:44,200 --> 00:43:46,300
to do with other one and 
verbalize white season. 

946
00:43:46,300 --> 00:43:48,900
The flour and the Little Flower 
would stay there in person. 

947
00:43:48,900 --> 00:43:50,700
I prefer because I like 
chocolate. 

948
00:43:50,800 --> 00:43:54,600
It is something when you receive
a compliment and right after 

949
00:43:54,600 --> 00:43:56,800
that to have a taste of 
chocolate in your mouth. 

950
00:43:57,200 --> 00:44:00,600
That's a Amazing home because 
it's like, you get the 

951
00:44:00,607 --> 00:44:03,700
government and then your body 
also gets a cobbler, a nice 

952
00:44:03,700 --> 00:44:06,100
tasty. 
It's a really good thing, but 

953
00:44:06,100 --> 00:44:08,700
when we need to verbalize, at 
least I know we removed. 

954
00:44:09,100 --> 00:44:11,800
One thing I did like I did a 
token of appreciation. 

955
00:44:12,000 --> 00:44:14,500
I organized the liver chocolate 
for everybody. 

956
00:44:14,500 --> 00:44:16,100
On the meeting. 
So they all received the 

957
00:44:16,100 --> 00:44:18,000
package, I said, they are going 
to receive a fax. 

958
00:44:18,000 --> 00:44:19,100
Please. 
Don't open before the 

959
00:44:19,100 --> 00:44:21,400
retrospective. 
You can only eat. 

960
00:44:21,400 --> 00:44:22,800
When you receive the 
appreciation. 

961
00:44:22,900 --> 00:44:24,500
It was cool. 
It work out. 

962
00:44:25,000 --> 00:44:27,700
Yeah, the one I've experienced 
before is somebody giving the 

963
00:44:27,900 --> 00:44:29,800
Post. 
It's just a posted with maybe a 

964
00:44:29,808 --> 00:44:32,100
few message. 
Like, why you think the person. 

965
00:44:32,300 --> 00:44:34,900
But I can understand that giving
it with maybe token of 

966
00:44:34,900 --> 00:44:38,100
appreciation, like chocolate or 
flowers or something tangible. 

967
00:44:38,300 --> 00:44:41,000
At least it also gives some 
meaning for you to actually 

968
00:44:41,000 --> 00:44:44,300
enjoy after that actual message.
So, definitely, I think for 

969
00:44:44,300 --> 00:44:47,300
people, maybe you can try these 
kind of fun activities, giving a

970
00:44:47,308 --> 00:44:50,600
token of appreciation not just 
like oh States or letters. 

971
00:44:50,600 --> 00:44:52,300
That will be a good experiment. 
I guess. 

972
00:44:52,600 --> 00:44:54,900
Another thing is about light 
environment, right? 

973
00:44:54,900 --> 00:44:57,700
I think many people try to make 
retrospective relief. 

974
00:44:57,800 --> 00:44:59,700
Really lightweight, but many 
times. 

975
00:44:59,700 --> 00:45:01,700
Of course, we talk about 
problems, right? 

976
00:45:01,800 --> 00:45:05,200
How to actually be conscious on 
making this more lightweight, 

977
00:45:05,600 --> 00:45:07,800
that's a really good question 
because we will talk about 

978
00:45:07,800 --> 00:45:09,400
promise, right? 
We need to talk about problems 

979
00:45:09,400 --> 00:45:11,500
and respect it. 
Is that when you first talked 

980
00:45:11,500 --> 00:45:13,900
about problems, so how do you 
handle it? 

981
00:45:13,900 --> 00:45:17,700
First the context you have to be
very clear about the conductor. 

982
00:45:17,900 --> 00:45:22,700
If the team is on a sad moment 
like the energy is low, do not 

983
00:45:22,700 --> 00:45:25,100
make a context that invites for 
problem. 

984
00:45:25,200 --> 00:45:28,600
Be cautious about the concept to
respect the Super happy. 

985
00:45:28,600 --> 00:45:31,500
It's achieving cool. 
Let's focus on the problems. 

986
00:45:31,700 --> 00:45:34,500
The team morale is really low. 
Let's have a great respect to 

987
00:45:34,500 --> 00:45:36,600
boost morale. 
So that's part of the contest 

988
00:45:36,800 --> 00:45:39,200
when you decide what is the 
concept of the respect, we need 

989
00:45:39,200 --> 00:45:41,100
to be aware of the moment of the
team. 

990
00:45:41,500 --> 00:45:44,600
Don't choose a context to dig 
further into problems if the 

991
00:45:44,600 --> 00:45:47,500
tomorrow it's really low. 
So first we are with respect to 

992
00:45:47,500 --> 00:45:50,500
boost morale and then the next 
one you did for the into 

993
00:45:50,500 --> 00:45:51,700
problems. 
So, the context is very 

994
00:45:51,700 --> 00:45:54,300
important. 
After the context, do run a 

995
00:45:54,300 --> 00:45:57,700
short Energizer. 
That's a five-minute - to you. 

996
00:45:57,800 --> 00:45:59,800
You need to break the ice 
special. 

997
00:45:59,800 --> 00:46:02,500
Now remote. 
Because before, when we were 

998
00:46:02,500 --> 00:46:05,800
presential, you leave the table,
you leave the desk and then 

999
00:46:05,800 --> 00:46:08,500
together, you walk through a 
room and then as you walk in the

1000
00:46:08,500 --> 00:46:12,100
room, ok, I'm going to respect. 
It's similar to when you walk to

1001
00:46:12,100 --> 00:46:13,900
the psychologists often. 
Like okay. 

1002
00:46:14,200 --> 00:46:16,600
I'm physically walking here to a
place where I'm going to open my

1003
00:46:16,600 --> 00:46:19,600
heart rate with respect for the 
same with work of the room. 

1004
00:46:19,800 --> 00:46:23,500
Now, it's just another meeting. 
So you need to break the ice if 

1005
00:46:23,500 --> 00:46:25,500
possible. 
Then there has to be fast. 

1006
00:46:25,500 --> 00:46:27,700
It's not oh, we're going to have
an activity, which they want to.

1007
00:46:27,900 --> 00:46:28,700
Playing here. 
Now. 

1008
00:46:28,700 --> 00:46:31,100
We cannot do this. 
It needs to be fast like five 

1009
00:46:31,100 --> 00:46:35,000
minutes and if possible for 
subtle message related to what 

1010
00:46:35,000 --> 00:46:37,300
you want to do from it. 
If you're having problems of 

1011
00:46:37,300 --> 00:46:40,600
self-organizing I Energizer that
has a subtle message. 

1012
00:46:40,600 --> 00:46:43,600
From self-organizing teams, you 
have problems with the user 

1013
00:46:43,600 --> 00:46:46,600
stories Energizer that has a 
subtle message about a which 

1014
00:46:46,600 --> 00:46:49,400
communicate not only rely on 
recent documents. 

1015
00:46:49,700 --> 00:46:52,300
So five energized for several 
measures that do help you with 

1016
00:46:52,300 --> 00:46:54,900
the contest. 
So you had the context, you have

1017
00:46:54,900 --> 00:46:57,900
the energizing, the prime 
directive, where your mind Beep.

1018
00:46:57,900 --> 00:47:00,600
Beep about hey, it's not a blind
fast. 

1019
00:47:00,900 --> 00:47:04,000
But the prime directive after I 
energize it gets easier because 

1020
00:47:04,000 --> 00:47:06,200
then Bryce laughs and then you 
read the sentence. 

1021
00:47:06,200 --> 00:47:08,400
Okay, the environment already 
better. 

1022
00:47:08,700 --> 00:47:10,700
Let's get remind about the prime
directive. 

1023
00:47:11,000 --> 00:47:14,600
And then after that a checking, 
what is the checking? 

1024
00:47:14,800 --> 00:47:17,100
It's a quick. 
Let me feel how people are 

1025
00:47:17,100 --> 00:47:20,100
feeling right now in the context
of this retrospective. 

1026
00:47:20,400 --> 00:47:24,000
And then check-ins, like people 
kind of open their heart or how 

1027
00:47:24,000 --> 00:47:27,700
safe they are feeling before you
move on to dig in further. 

1028
00:47:28,400 --> 00:47:32,100
If the checking results show you
yes, move forward because people

1029
00:47:32,100 --> 00:47:35,000
are safe, talk about it. 
Then you go and dig into the 

1030
00:47:35,000 --> 00:47:38,800
problem and then you do your 
filtering and then a check out. 

1031
00:47:39,200 --> 00:47:41,400
But before you dig into the 
problem, have you realized like 

1032
00:47:41,400 --> 00:47:44,500
how many steps you went through 
and as a facilitator? 

1033
00:47:44,600 --> 00:47:48,600
If you have signals very clear. 
No am I guess that context the 

1034
00:47:48,600 --> 00:47:52,100
Energizer explodes group or not?
Laughing at all the checking 

1035
00:47:52,100 --> 00:47:54,900
those people are not safe. 
Don't go in that direction. 

1036
00:47:55,200 --> 00:47:57,600
If we per individual red flags, 
like I cannot talk. 

1037
00:47:57,800 --> 00:47:59,400
About crabs. 
I cannot talk about problems and

1038
00:47:59,400 --> 00:48:01,300
you go talk about problem. 
Guess what's going to happen? 

1039
00:48:01,300 --> 00:48:03,000
They're going to explode, don't 
do it. 

1040
00:48:03,400 --> 00:48:05,400
If there's a red flag, what you 
do? 

1041
00:48:05,600 --> 00:48:09,000
It's like it's a pivot inside 
the retrospective Hoops, safety 

1042
00:48:09,000 --> 00:48:10,300
slow. 
We should talk about. 

1043
00:48:10,300 --> 00:48:13,200
What should you do to increase 
safety and not talk about what's

1044
00:48:13,200 --> 00:48:15,200
the problem with continuous 
integration or whatever? 

1045
00:48:15,400 --> 00:48:18,600
That's the important about 
planning the retrospect and 

1046
00:48:18,600 --> 00:48:20,400
facilitate. 
It facilitates. 

1047
00:48:20,400 --> 00:48:24,100
Not only following a plan is 
like, go through the activities 

1048
00:48:24,100 --> 00:48:26,200
making decisions. 
Yes, they're moving this 

1049
00:48:26,200 --> 00:48:29,700
direction or that you Clamp, 
then you trusted the date, 

1050
00:48:30,100 --> 00:48:31,900
right? 
So, how do you actually do this?

1051
00:48:31,900 --> 00:48:34,500
Checking is that specific 
question that you asked. 

1052
00:48:34,500 --> 00:48:37,300
Are you feeling safe or is there
kind of survey? 

1053
00:48:37,500 --> 00:48:41,000
What's the process like on the 
site from retrospect.com? 

1054
00:48:41,100 --> 00:48:44,900
I organized activities as per 
those steps their activities for

1055
00:48:44,900 --> 00:48:49,600
energizer's directives for the 
prime directive because you have

1056
00:48:49,600 --> 00:48:52,500
two kinds of friend, direct one 
about retrospective one about 

1057
00:48:52,500 --> 00:48:55,500
future spectacle which different
than one of about team building.

1058
00:48:55,900 --> 00:48:59,700
So the prime directive Then 
there are checking activities. 

1059
00:49:00,000 --> 00:49:02,600
Then there are main course 
activities for prospective 

1060
00:49:02,600 --> 00:49:05,300
future expectant in building 
different actors for each. 

1061
00:49:05,300 --> 00:49:07,800
One of those and then checkout 
activities. 

1062
00:49:08,300 --> 00:49:12,600
Oh, and future activities. 
So checking activities the most 

1063
00:49:12,600 --> 00:49:16,100
famous one was safe to check but
people only did the safety check

1064
00:49:16,100 --> 00:49:18,100
and that's it. 
They think about checking like 

1065
00:49:18,100 --> 00:49:21,400
it needs to be fast to verify 
how people are feeling as they 

1066
00:49:21,400 --> 00:49:23,600
enter before they do the main 
course. 

1067
00:49:23,900 --> 00:49:27,300
Another example you can do is 
like one word share with us in 

1068
00:49:27,300 --> 00:49:28,800
one word. 
How you're feeling right now in 

1069
00:49:28,800 --> 00:49:31,800
the context of disrespect. 
Another one is draw your 

1070
00:49:31,800 --> 00:49:34,000
feelings. 
Please draw her feeling right 

1071
00:49:34,000 --> 00:49:37,200
now because of disrespect, or 
happiness. 

1072
00:49:37,200 --> 00:49:39,100
Rater. 
Please share with us on the 

1073
00:49:39,107 --> 00:49:42,400
scale of being really sad. 
Super happy how you're feeling 

1074
00:49:42,400 --> 00:49:45,800
in average during this period, 
how you're feeling in every day.

1075
00:49:45,800 --> 00:49:48,300
During this period, for things 
related to the business for 

1076
00:49:48,300 --> 00:49:51,100
things, relate of technology for
things, reach the process. 

1077
00:49:51,400 --> 00:49:54,900
It's only a headset or medium 
face for each of those 

1078
00:49:54,900 --> 00:49:56,800
categories. 
And then you carry this forward 

1079
00:49:56,800 --> 00:50:01,400
to the next one. 
Okay, so now tell me why you 

1080
00:50:01,400 --> 00:50:03,400
were feeling this way, you draw 
something. 

1081
00:50:03,400 --> 00:50:06,100
Now you need to ask them, why 
you're free to try to gather 

1082
00:50:06,100 --> 00:50:09,000
data. 
But you as a facilitator based 

1083
00:50:09,000 --> 00:50:10,700
on what you get from the 
check-in. 

1084
00:50:10,700 --> 00:50:11,700
Okay? 
Yes. 

1085
00:50:11,700 --> 00:50:15,500
I can move forward safely to 
this next activity or know that 

1086
00:50:15,500 --> 00:50:17,800
we have safe. 
You are about sharing and talk 

1087
00:50:17,800 --> 00:50:20,000
about anything. 
The group's not safe. 

1088
00:50:20,100 --> 00:50:22,400
Why are going to ask now? 
Like hey now, let's talk about 

1089
00:50:22,400 --> 00:50:23,700
anything. 
No, the good to do. 

1090
00:50:23,700 --> 00:50:26,900
They are not safe. 
It seems that the facilitators 

1091
00:50:26,900 --> 00:50:29,600
role is very Important in this 
kind of activity. 

1092
00:50:29,900 --> 00:50:33,600
So what would be some good 
attributes or some good things 

1093
00:50:33,600 --> 00:50:37,100
that facilitator should assess? 
I know that probably is not like

1094
00:50:37,100 --> 00:50:39,200
everyone can do this 
facilitation really? 

1095
00:50:39,200 --> 00:50:41,000
Well. 
So what are some of the key 

1096
00:50:41,000 --> 00:50:42,200
things? 
Do you think? 

1097
00:50:43,300 --> 00:50:46,300
First things, the distinction 
about the facilitator hat and 

1098
00:50:46,300 --> 00:50:49,900
the participant hat, if your 
facilitator is respect for your 

1099
00:50:49,900 --> 00:50:53,900
own team, would even be nice. 
If you drink ahead and talk as a

1100
00:50:53,900 --> 00:50:57,300
facilitator, remove the head and
talk as a participant if you 

1101
00:50:57,308 --> 00:50:59,800
have the A luxury to have an 
external facilitator, even 

1102
00:50:59,800 --> 00:51:02,500
better because then there's no 
hat and everybody participates, 

1103
00:51:02,500 --> 00:51:04,400
right? 
That's the first advice because 

1104
00:51:04,400 --> 00:51:07,200
I know that we need to 
facilitate a lot of respect for 

1105
00:51:07,200 --> 00:51:08,800
teams. 
So, go ahead and say, hey, I'm 

1106
00:51:08,800 --> 00:51:12,800
here is of the data if your talk
is a facilitator, facilitate the

1107
00:51:12,800 --> 00:51:14,900
conversation, don't bring your 
opinion treat. 

1108
00:51:15,200 --> 00:51:17,500
If you want to bring your 
opinion, remove the Hat, raise 

1109
00:51:17,500 --> 00:51:20,800
your hand as anyone else. 
And then talk to know when the 

1110
00:51:20,808 --> 00:51:25,200
moments appropriate. 
That's the first advice, second,

1111
00:51:25,600 --> 00:51:28,900
if you're going to facilitate, 
there is That happens before the

1112
00:51:28,900 --> 00:51:31,800
respects. 
It's like talking to different 

1113
00:51:31,800 --> 00:51:35,400
people, trying to understand the
moment of that team. 

1114
00:51:35,700 --> 00:51:39,000
And then think about the agenda 
to that moment and be careful. 

1115
00:51:39,000 --> 00:51:40,900
Cause sometimes you talk to 
people and they want too many 

1116
00:51:40,900 --> 00:51:45,000
things for one respect. 
You want to be a retrospective? 

1117
00:51:45,000 --> 00:51:47,900
Not, let's lock ourselves for 
one day here. 

1118
00:51:47,900 --> 00:51:50,500
In the room. 
It's like having five hour 

1119
00:51:50,500 --> 00:51:53,100
session for psychologists know 
psychologists. 

1120
00:51:53,100 --> 00:51:55,500
Like they do a lot of one-hour 
sessions at in purpose. 

1121
00:51:55,800 --> 00:51:58,700
Same with respect, others. 
Don't Bring too much in one 

1122
00:51:58,700 --> 00:52:00,300
session is too much for us to 
handle. 

1123
00:52:00,500 --> 00:52:03,400
So when you talk to different 
people, you need to think about 

1124
00:52:03,400 --> 00:52:05,800
the agenda. 
The context detectives you're 

1125
00:52:05,800 --> 00:52:09,900
going to bring, so prepare. 
The agenda for retrospectives 

1126
00:52:09,900 --> 00:52:13,100
can help with that because the 
combination of actives will make

1127
00:52:13,100 --> 00:52:16,400
you think about the agenda that 
checking the main course, the 

1128
00:52:16,400 --> 00:52:19,600
check out the context, the prime
directive, your select is a 

1129
00:52:19,600 --> 00:52:23,200
retrofit respective. 
Once you prepare the agenda, 

1130
00:52:23,200 --> 00:52:26,200
then it's about facilitating 
potential to the results. 

1131
00:52:26,600 --> 00:52:30,000
And how do you Create a good 
environment, then pay attention 

1132
00:52:30,000 --> 00:52:31,900
if it is really good 
environment. 

1133
00:52:31,900 --> 00:52:35,400
And if it is move forward with 
your plan, if something goes off

1134
00:52:35,400 --> 00:52:38,500
track during the focus to the 
people, not sure agenda. 

1135
00:52:38,900 --> 00:52:40,900
That's the thing. 
Like look at the people, see how

1136
00:52:40,900 --> 00:52:43,000
they are feeling. 
Don't move forward in their 

1137
00:52:43,000 --> 00:52:45,100
plan, or dig into a problem or 
something. 

1138
00:52:45,100 --> 00:52:47,300
If someone's not feeling good 
about it. 

1139
00:52:47,900 --> 00:52:49,900
Thanks for sharing all this. 
Unfortunately. 

1140
00:52:49,900 --> 00:52:53,000
We are going to the end of this 
conversation, due to the time. 

1141
00:52:53,300 --> 00:52:55,900
But I have one last question 
that normally I ask for every 

1142
00:52:55,900 --> 00:52:59,200
guest is about 3, technically, 
Leadership wisdom Sao Paulo. 

1143
00:52:59,200 --> 00:53:02,000
Do you have some kind of a 
message of wisdom that you want 

1144
00:53:02,000 --> 00:53:04,300
to share or pass along to the 
audience? 

1145
00:53:04,300 --> 00:53:07,500
Here? 
They're few three reasons for a 

1146
00:53:07,500 --> 00:53:10,600
leader, empathy, put yourself on
everybody's shoes. 

1147
00:53:10,600 --> 00:53:13,700
And now it's a hard thing 
because we cannot give in the 

1148
00:53:13,700 --> 00:53:16,700
context of try to understand 
where people come from, with 

1149
00:53:16,700 --> 00:53:20,900
open, heart be very empathetic 
to understand people the cycle 

1150
00:53:20,900 --> 00:53:23,500
to be openness. 
The moment you want to be 

1151
00:53:23,500 --> 00:53:25,500
empathy. 
You have to be very open to 

1152
00:53:25,500 --> 00:53:27,500
everything. 
Be very open mind. 

1153
00:53:27,600 --> 00:53:31,000
For the difference that we have.
You cannot find two people. 

1154
00:53:31,000 --> 00:53:34,200
Like, so we need to be very open
in order to have that empathy 

1155
00:53:34,200 --> 00:53:38,000
level of connection with people.
And then the third would say 

1156
00:53:38,000 --> 00:53:41,600
servant the world has changed 
and if you want to be a leader, 

1157
00:53:41,600 --> 00:53:45,900
you want to figure out how to be
a servant leader empathy, 

1158
00:53:45,900 --> 00:53:48,300
openness and servant. 
Because the other stuff 

1159
00:53:48,300 --> 00:53:50,100
leadership. 
You have a lot of books and 

1160
00:53:50,100 --> 00:53:53,900
things that you progress have 
covered for like a tea, openness

1161
00:53:53,900 --> 00:53:56,400
and serve active for me. 
Those are the three skills that 

1162
00:53:56,400 --> 00:53:59,400
you need to really work on. 
Want to be a leader for today 

1163
00:53:59,600 --> 00:54:01,000
because we are ready in the 
future. 

1164
00:54:01,100 --> 00:54:04,800
Why has changed drastically. 
Thanks for the beautiful wisdom 

1165
00:54:04,800 --> 00:54:06,400
message. 
I think I agree with that 

1166
00:54:06,400 --> 00:54:08,300
empathy. 
Openness and seven leadership 

1167
00:54:08,300 --> 00:54:11,200
will be like a very rare 
critical skills for leaders in 

1168
00:54:11,200 --> 00:54:13,100
the future. 
So thanks again, follow for your

1169
00:54:13,100 --> 00:54:14,700
time. 
If people want to connect with 

1170
00:54:14,700 --> 00:54:17,300
you or find out more about you. 
Where can they find you? 

1171
00:54:17,800 --> 00:54:20,200
My website? 
I blog, very often like cover 

1172
00:54:20,200 --> 00:54:24,300
all your dot orgy or all dot 
org, or if you want to respect 

1173
00:54:24,300 --> 00:54:27,300
the stuff for with respect 
to.com., You find me. 

1174
00:54:27,300 --> 00:54:29,900
Mike. 
Look for active on the blog's 

1175
00:54:29,900 --> 00:54:33,800
the books to your liquid in but 
go to the website you find me. 

1176
00:54:34,300 --> 00:54:36,200
Thanks Paulo. 
I hope that people listen to 

1177
00:54:36,200 --> 00:54:38,900
this episode and they will try 
some of these things like lean 

1178
00:54:38,900 --> 00:54:40,600
Inception and fund. 
Retrospectives. 

1179
00:54:40,600 --> 00:54:42,700
Thanks again for awesome. 
Thank you so much. 

1180
00:54:42,700 --> 00:54:46,900
Cheers. 
Thank you for listening to this 

1181
00:54:46,900 --> 00:54:49,500
episode and for staying right 
till the end. 

1182
00:54:49,700 --> 00:54:52,700
If you highly enjoyed, please 
share it with your friends and 

1183
00:54:52,700 --> 00:54:56,000
colleagues who you think would 
also benefit from listening to 

1184
00:54:56,000 --> 00:54:58,300
this episode. 
And if you're new to the 

1185
00:54:58,300 --> 00:55:01,600
podcast, make sure to subscribe 
and leave me your valuable 

1186
00:55:01,600 --> 00:55:05,000
review and feedback. 
It really, really helps me a lot

1187
00:55:05,000 --> 00:55:07,500
in order to grow these podcasts 
better. 

1188
00:55:08,000 --> 00:55:11,300
You can also find the full show 
notes of this conversation on 

1189
00:55:11,300 --> 00:55:14,900
the episode page at technology. 
Know the death website including

1190
00:55:15,100 --> 00:55:18,100
The full transcript, interesting
quotes and links to the 

1191
00:55:18,100 --> 00:55:21,000
resources and mentions from the 
conversation. 

1192
00:55:21,500 --> 00:55:24,300
And lastly make sure to 
subscribe to the show's mailing 

1193
00:55:24,300 --> 00:55:27,500
list on technology. 
No, the deaf to get notified for

1194
00:55:27,500 --> 00:55:30,300
any future episodes. 
Stay tuned for the next 

1195
00:55:30,300 --> 00:55:32,800
technique Journal episode. 
And until then. 

1196
00:55:33,000 --> 00:55:33,600
Goodbye.