1
00:00:00,000 --> 00:00:02,220
Hey, so your book's been out for like a month, right, Richard?

2
00:00:02,900 --> 00:00:03,460
It has.

3
00:00:03,680 --> 00:00:03,900
Yeah?

4
00:00:04,440 --> 00:00:04,840
Yeah.

5
00:00:05,480 --> 00:00:07,640
Are you five stars all the way?

6
00:00:08,000 --> 00:00:11,720
Are you like circling around that four and a half star and you're like, who are these

7
00:00:11,720 --> 00:00:12,100
people?

8
00:00:12,460 --> 00:00:14,980
Clearly, everyone likes it except this one person.

9
00:00:15,820 --> 00:00:19,500
Yeah, so far it's a pivotal exclusive, so it's just download counts is what I'm checking

10
00:00:19,500 --> 00:00:21,640
out now and listening for random feedback.

11
00:00:22,100 --> 00:00:22,580
Oh, yeah.

12
00:00:22,880 --> 00:00:23,060
Huh.

13
00:00:23,460 --> 00:00:23,660
Huh.

14
00:00:24,080 --> 00:00:28,700
Have you seen, have you found this character, Johnny Legion, who's downloaded it yet?

15
00:00:30,400 --> 00:00:32,140
I love your alternate persona.

16
00:00:32,400 --> 00:00:33,980
He's my favorite character.

17
00:00:34,380 --> 00:00:35,160
I need to look.

18
00:00:35,200 --> 00:00:36,260
I need to look at the raw numbers.

19
00:00:36,340 --> 00:00:39,900
I actually get a physical copy in two weeks at the Gartner show, so that'll be the first

20
00:00:39,900 --> 00:00:41,140
time I get to hold this masterpiece.

21
00:00:41,500 --> 00:00:42,620
You should save one for me.

22
00:00:42,660 --> 00:00:43,140
That's exciting.

23
00:00:43,140 --> 00:00:49,440
I have a copy of Nate Schuda's book here that I haven't read yet, so I could get a copy of

24
00:00:49,440 --> 00:00:52,000
yours and not read it, too, and add it to my collection.

25
00:00:52,920 --> 00:00:53,900
That's when I know I've made it.

26
00:00:54,320 --> 00:00:54,380
Yeah.

27
00:00:54,680 --> 00:00:59,500
I think once we get those books at the booths and tables, they'll just, I don't know why

28
00:00:59,500 --> 00:01:05,320
hot cakes fly, but they'll fly off the shelf like hot cakes, but people will love that.

29
00:01:05,560 --> 00:01:06,860
It'll fill a solid hole.

30
00:01:07,060 --> 00:01:10,380
Now, what image did you pick for the cover?

31
00:01:10,640 --> 00:01:11,200
How does that go?

32
00:01:11,920 --> 00:01:12,480
You know, it's funny.

33
00:01:12,580 --> 00:01:13,820
People have asked me that.

34
00:01:13,900 --> 00:01:17,280
Since I think it's one of these sponsored books, and it's not a giant book.

35
00:01:17,340 --> 00:01:18,100
It's like 100 pages.

36
00:01:18,200 --> 00:01:18,940
I didn't get an animal.

37
00:01:19,060 --> 00:01:19,780
I got like a picture.

38
00:01:20,080 --> 00:01:20,700
Yeah, yeah.

39
00:01:20,940 --> 00:01:24,200
You get like a black and white picture that's like, I wouldn't call it.

40
00:01:24,200 --> 00:01:25,720
It's not like a 40s.

41
00:01:25,800 --> 00:01:31,140
It's more like maybe a early 80s style black and white picture, if I remember all of them,

42
00:01:31,180 --> 00:01:31,380
right?

43
00:01:31,560 --> 00:01:37,580
Like it's kind of pre-smartphone industrial, I think you might.

44
00:01:38,260 --> 00:01:41,580
So at least this one was my suggestion they actually took, which was a building with a

45
00:01:41,580 --> 00:01:43,780
bunch of scaffolding around it, because it's modernization.

46
00:01:44,480 --> 00:01:46,840
So, you know, it was that or get a sea otter.

47
00:01:47,240 --> 00:01:48,640
And I guess I'll take the...

48
00:01:48,640 --> 00:01:49,900
Did you say a sea otter?

49
00:01:50,440 --> 00:01:51,580
Yeah, that could have been my animal.

50
00:01:51,720 --> 00:01:52,400
That would have been my choice.

51
00:01:53,120 --> 00:01:53,940
That would be great.

52
00:01:54,020 --> 00:01:55,680
Like the two sea otters holding hands.

53
00:01:56,080 --> 00:01:56,840
Yeah, sounds good.

54
00:01:58,600 --> 00:01:59,220
All right.

55
00:01:59,580 --> 00:02:00,920
Well, I wasn't expecting that.

56
00:02:00,980 --> 00:02:03,940
Well, also, it's been a while since we recorded, as always.

57
00:02:04,200 --> 00:02:04,880
I don't know.

58
00:02:05,060 --> 00:02:06,280
I have all the usual excuses.

59
00:02:06,820 --> 00:02:08,000
I know none of it's your fault.

60
00:02:08,080 --> 00:02:08,620
It's just me.

61
00:02:08,800 --> 00:02:10,040
I just travel around a lot.

62
00:02:10,120 --> 00:02:12,840
It's great for podcast scheduling.

63
00:02:12,840 --> 00:02:15,780
But there's been some gigantic news.

64
00:02:16,320 --> 00:02:19,240
It looks like IBM is buying our friends over at Red Hat.

65
00:02:19,680 --> 00:02:22,020
That's some exciting consolidation going on.

66
00:02:22,220 --> 00:02:27,160
We recorded a couple episodes ago on my other podcast, Software Defined Talk.

67
00:02:27,280 --> 00:02:31,640
Episode 153, if you've got your pen and paper out and you're writing this down,

68
00:02:32,260 --> 00:02:35,140
there's a lot more babbling commentary from that.

69
00:02:35,260 --> 00:02:38,900
As I think the title of that, it summarizes my commentary.

70
00:02:39,440 --> 00:02:44,160
I don't know anything about this topic, so I'm going to go on and talk for a long time.

71
00:02:44,600 --> 00:02:45,820
It's a much more concise topic.

72
00:02:46,200 --> 00:02:47,380
But there you go.

73
00:02:48,060 --> 00:02:48,580
Consolidation.

74
00:02:48,800 --> 00:02:51,320
I think that's supposed to close like next year sometimes.

75
00:02:51,320 --> 00:02:52,760
So it'll be official.

76
00:02:54,280 --> 00:02:54,640
Right.

77
00:02:54,760 --> 00:02:58,620
And then, yeah, of course, you had VMware declaring they were intent to acquire Heptio.

78
00:02:58,940 --> 00:02:59,320
Oh, yeah.

79
00:02:59,400 --> 00:02:59,880
That's right.

80
00:03:00,100 --> 00:03:01,380
During VMworld a couple weeks back.

81
00:03:01,500 --> 00:03:05,060
And that was so it's kind of Kubernetes land, lots of stuff going on, which would have been

82
00:03:05,060 --> 00:03:09,280
fascinating three years ago if you had said you'd see this massive $34 billion merger

83
00:03:09,280 --> 00:03:15,680
somehow on the backs of Kubernetes or VMware dropping untold millions to acquire a Kubernetes-based startup.

84
00:03:15,900 --> 00:03:18,120
You would have been laughed out of the room a few years ago.

85
00:03:18,200 --> 00:03:21,280
But now, clearly, infrastructure companies get infrastructure.

86
00:03:21,760 --> 00:03:22,080
That's right.

87
00:03:23,680 --> 00:03:24,260
That's right.

88
00:03:24,420 --> 00:03:30,660
And then also, like I just noticed this over the weekend, there's going to be a new CEO at Google Cloud, right?

89
00:03:30,740 --> 00:03:31,520
So Diane Green.

90
00:03:32,100 --> 00:03:36,420
And she had a good, I think a good, I don't know the exact quote.

91
00:03:36,480 --> 00:03:37,680
I'll have to find it for the show notes.

92
00:03:37,680 --> 00:03:43,920
But there was a good summary from herself of what happened during her 10-year and how she helped out,

93
00:03:44,060 --> 00:03:49,800
which I think was, to summarize, it was basically like a handful of sort of like smaller companies and startups.

94
00:03:49,800 --> 00:03:56,160
And now I think they have usage, which is to say penetration across like all the Fortune 500.

95
00:03:56,440 --> 00:04:03,360
So she helped out, I'm sure, along with many other people, like growing a lot of momentum around that business.

96
00:04:03,820 --> 00:04:06,380
And then you have, how do you say his last name?

97
00:04:06,440 --> 00:04:11,640
Thomas Kurian, I think, who had just departed Oracle.

98
00:04:11,780 --> 00:04:14,500
And I think he was the head of what part?

99
00:04:14,620 --> 00:04:18,800
Maybe he was the head of like all the non-application stuff of like cloud.

100
00:04:18,800 --> 00:04:20,800
Maybe not database, but all their cloud stuff.

101
00:04:21,360 --> 00:04:27,420
And then I think they said Diane Green is going to rotate up to the board and I think serve through the end of the year.

102
00:04:27,520 --> 00:04:28,820
And then he becomes the CEO.

103
00:04:29,140 --> 00:04:32,260
It's a very well-planned out transition there.

104
00:04:33,600 --> 00:04:34,000
Yeah.

105
00:04:35,440 --> 00:04:39,180
So that'll be, there's all sorts of changing dynamics.

106
00:04:39,540 --> 00:04:39,980
2019.

107
00:04:40,920 --> 00:04:45,240
I guess you would call that CY 2019 since some people might be in their FY.

108
00:04:45,840 --> 00:04:51,320
But we'll see why all these people are emerging and whatnot in 2019.

109
00:04:52,280 --> 00:04:55,420
That's my really fraught calendar joke right there.

110
00:04:56,020 --> 00:04:56,220
Yeah.

111
00:04:56,440 --> 00:04:59,760
It's just funny how, I mean, next week, so next week I think it's re-invent.

112
00:05:00,020 --> 00:05:01,560
And again, also the Gartner show I'll be at.

113
00:05:01,640 --> 00:05:08,040
But it's just funny how many of these moves have a, you feel like there's the shadow looming of AWS among all of these.

114
00:05:08,820 --> 00:05:09,280
All right.

115
00:05:09,340 --> 00:05:16,640
I mean, Red Hat and IBM is arguably, you know, IBM's kind of waving the white flags and can we really win in cloud, even Red Hat potentially.

116
00:05:16,640 --> 00:05:18,940
And clearly even VMware buying Heptio.

117
00:05:19,080 --> 00:05:24,620
It's continuing to just own this sort of infrastructure layer that might span clouds because that's an important story now.

118
00:05:24,700 --> 00:05:35,600
Even the Google story, you can just wonder if some of this was because Google had a little trouble just kind of breaking over this next chasm of being relevant in the enterprise and you can't wait too long.

119
00:05:35,880 --> 00:05:36,720
So who knows?

120
00:05:36,840 --> 00:05:48,860
We're not sitting in their boardrooms making those decisions, but you can almost see this, you know, I don't know, eye of Sauron staring on all the different sectors that get freaked out and do mergers and acquisitions.

121
00:05:49,260 --> 00:05:52,120
Trying to grow ogres and trolls in a mucky pit.

122
00:05:52,900 --> 00:05:55,780
I think that's the other part of that, if I recall, right?

123
00:05:56,120 --> 00:06:01,960
And lots of dry cleaning and bleaching of white robes, also necessary in that environment.

124
00:06:02,680 --> 00:06:07,380
Well, also the, there's just a couple more things and then we'll bring our guest in.

125
00:06:07,560 --> 00:06:10,280
I sort of rudely forgot to do that at the beginning, but what are you going to do?

126
00:06:10,840 --> 00:06:13,840
Just keep going the course, push through the paper.

127
00:06:15,000 --> 00:06:22,300
Also, I was just, I've had people ask me quite a bit recently for like recordings of the standard talk I give.

128
00:06:22,300 --> 00:06:27,260
So I made a few like talks on my own alone in my little house here.

129
00:06:27,600 --> 00:06:34,860
But there's also, I was at, I was at, this is Monday, I was at DevOps in Antwerp, just the main DevOps thing.

130
00:06:35,000 --> 00:06:39,440
And I finally gave a talk on enterprise architecture that I don't think it was terrible.

131
00:06:40,040 --> 00:06:42,000
And there's a recording of that as well.

132
00:06:42,020 --> 00:06:43,360
And I'll put these all in the show notes.

133
00:06:43,360 --> 00:06:54,720
And then when I was in Singapore that same week, last week, I gave, I gave like a new talk on like, you know, what is culture and DevOps culture?

134
00:06:55,020 --> 00:06:59,180
And more importantly, like, as I like to do, like what are tactics and things you can actually do?

135
00:06:59,920 --> 00:07:04,300
And hopefully, I think the Singapore people said they would put that recording up sometime soon.

136
00:07:04,380 --> 00:07:06,200
But I've organized all of this.

137
00:07:06,280 --> 00:07:10,060
I've used one of my absurd domain names for good, finally.

138
00:07:10,480 --> 00:07:15,500
So if you go to Coté.coffee slash better software, you can find all this stuff.

139
00:07:15,880 --> 00:07:22,040
And there's like, I got a 30 minute version of my little stump speech, and a 50 minute version.

140
00:07:22,040 --> 00:07:30,760
And then I have a 90 minute version, just for like, so you can fill whatever time you have, you know, if you got some empty time, you can fill it out.

141
00:07:30,820 --> 00:07:33,640
You could combine these together, see how they evolve.

142
00:07:33,740 --> 00:07:35,460
You could watch one, just two, three.

143
00:07:35,940 --> 00:07:37,040
There's lots of combinations.

144
00:07:37,540 --> 00:07:38,940
Maybe you could even splice them together.

145
00:07:39,300 --> 00:07:41,740
Anyways, they're available for enjoyment.

146
00:07:42,500 --> 00:07:45,960
Your media empire is continuing to impressively grow.

147
00:07:46,060 --> 00:07:48,800
And no, it's good for Thanksgiving this week if people have some downtime.

148
00:07:49,040 --> 00:07:50,460
Just really flip on their cootay dog.

149
00:07:50,580 --> 00:07:51,120
There you go.

150
00:07:51,180 --> 00:07:56,700
If you don't want to hang out with like Uncle Larry and Aunt Matilda, just be like, oh, I got to work.

151
00:07:58,100 --> 00:07:59,620
So much to be thankful for there.

152
00:08:00,000 --> 00:08:06,020
And then finally, something else came out I haven't had a chance to look at, but you were my notification system for it.

153
00:08:06,080 --> 00:08:07,660
I assume you've looked over a little bit.

154
00:08:08,060 --> 00:08:08,660
What is that?

155
00:08:09,260 --> 00:08:09,640
I don't know.

156
00:08:09,640 --> 00:08:13,080
I have an irrational affection for the ThoughtWorks radar that comes out.

157
00:08:13,140 --> 00:08:18,040
I think it's quarterly, maybe bi-yearly or twice annual, however you're supposed to refer to that time period.

158
00:08:18,720 --> 00:08:25,740
So it's kind of a radar chart of technologies and platforms, tools, languages that you're supposed to care about, right?

159
00:08:25,780 --> 00:08:29,820
And ThoughtWorks is a, hey, smart company, keeps a good eye on the sector.

160
00:08:30,000 --> 00:08:33,800
And a lot of times this is a good way to look at kind of forward-looking tech.

161
00:08:33,900 --> 00:08:38,400
Like, hey, this isn't always stuff that you're going to use right now, but things that you should pay attention to.

162
00:08:38,500 --> 00:08:41,100
So it can be techniques like canary deployments.

163
00:08:41,100 --> 00:08:44,400
It can be things like, you know, how do I do infrastructure as code?

164
00:08:44,520 --> 00:08:46,460
Or what are things you should actually hold on?

165
00:08:46,520 --> 00:08:48,620
Like, hey, stop having microservices envy.

166
00:08:48,920 --> 00:08:53,740
Or, you know, doing complicated things with API gateways that you shouldn't.

167
00:08:53,740 --> 00:08:58,180
And so it's a really good list of, you know, dozens of things that you should pay attention to.

168
00:08:58,360 --> 00:09:09,640
And interestingly enough, even all the public clouds, things like Amazon, Azure, Google, are all even kind of demoted down to a trial mode just because all the competitors are decent right now.

169
00:09:09,700 --> 00:09:14,800
So saying you should just purely adopt one of the clouds as your sole platform isn't their recommendation, which was interesting.

170
00:09:15,000 --> 00:09:20,620
It's weird to see AWS in a trial category in this day and age, but they're doing it for that reason.

171
00:09:20,720 --> 00:09:22,020
But just lots of good things.

172
00:09:22,020 --> 00:09:31,660
So I'd encourage most of our listeners here to take a look at the radar, thoughtworks.com slash radar, and just see, look, these might be things that you want to pay attention to or even just keep an eye on.

173
00:09:31,700 --> 00:09:39,400
Because your customers, if you're a pivotal employee listening or probably looking at this stuff, and if you're in industry, these are things that may help you build better software.

174
00:09:39,600 --> 00:09:42,900
At least you should pay attention to them just in case they turn into something good.

175
00:09:43,440 --> 00:09:43,880
Yeah, it is fun.

176
00:09:43,960 --> 00:09:48,000
And then they have all the historic radars listed there as well.

177
00:09:48,220 --> 00:09:50,920
It's a good ongoing source that I think is free.

178
00:09:51,120 --> 00:09:53,940
I don't know if you've got a Johnny Legion yourself into it.

179
00:09:54,300 --> 00:09:55,780
No, it's a Johnny Legion.

180
00:09:56,020 --> 00:09:57,900
Oh, just Johnny no name.

181
00:09:58,440 --> 00:09:59,540
But it is.

182
00:09:59,880 --> 00:10:02,360
I like their visual, right?

183
00:10:02,400 --> 00:10:06,880
They've taken like a hype cycle or a wave and transformed it into like a vortex of innovation.

184
00:10:07,180 --> 00:10:12,580
Because as you sort of spiral down, I think the outside is basically like, you know, know how to spell it.

185
00:10:12,800 --> 00:10:17,180
And then it's sort of like watch it and then figure it out and maybe trial or POC it.

186
00:10:17,260 --> 00:10:21,280
And then the middle is the adopt it and start using it.

187
00:10:21,640 --> 00:10:23,240
So I like a good vortex.

188
00:10:23,400 --> 00:10:26,580
A vortex is what happens in the southern hemisphere, right?

189
00:10:26,720 --> 00:10:27,540
Am I getting that right?

190
00:10:27,640 --> 00:10:31,320
Or no, that's like a hurricane versus a typhoon?

191
00:10:32,020 --> 00:10:32,320
I don't know.

192
00:10:32,320 --> 00:10:32,760
Yeah, a typhoon.

193
00:10:32,960 --> 00:10:33,300
There you go.

194
00:10:33,320 --> 00:10:34,140
I get it mixed up.

195
00:10:34,660 --> 00:10:36,680
I just love IT-based geometry.

196
00:10:37,020 --> 00:10:40,200
There are more quadrants and vortexes.

197
00:10:40,360 --> 00:10:40,660
It's great.

198
00:10:41,140 --> 00:10:41,420
Yeah.

199
00:10:41,720 --> 00:10:41,900
Great.

200
00:10:42,300 --> 00:10:42,700
Parabola.

201
00:10:43,240 --> 00:10:46,120
Well, why don't you introduce yourself, guest?

202
00:10:47,400 --> 00:10:47,800
Yeah.

203
00:10:47,880 --> 00:10:48,420
Introduce yourself.

204
00:10:48,520 --> 00:10:50,520
So I'm here in Seattle with Carl.

205
00:10:50,640 --> 00:10:51,760
Can you tell us who you are?

206
00:10:51,960 --> 00:10:53,380
Hey, my name is Carl Coriel Martin.

207
00:10:53,780 --> 00:11:02,760
And I'm currently a senior advisor on Josh McKenty's Systems Advisor Group, which is a relatively new formed team here at Pivotal.

208
00:11:05,000 --> 00:11:06,340
But you're a longtime pivot.

209
00:11:06,480 --> 00:11:09,360
You are hardly just recently recruited.

210
00:11:09,360 --> 00:11:13,500
So tell us a little bit about your long, tortured journey through the Pivotal halls.

211
00:11:14,020 --> 00:11:15,700
I would hardly describe it as torture.

212
00:11:15,940 --> 00:11:18,100
It turns out this whole be kind thing is real.

213
00:11:18,500 --> 00:11:18,620
Yeah.

214
00:11:19,180 --> 00:11:28,220
I first ran into Ian McFarland, who was a Pivotal Labs principal in 2009, when he and his partner were on vacation in Singapore.

215
00:11:29,280 --> 00:11:32,100
And a mutual friend introduced us and spent a day with them.

216
00:11:32,100 --> 00:11:38,800
And then in November of 2009, Rob and Ian and actually Elizabeth Hendrickson, who was not at Pivotal at the time, came out to Singapore.

217
00:11:38,800 --> 00:11:48,080
And they were looking at opening their first international office to service some potential Asian customers and spent some time talking with them.

218
00:11:49,300 --> 00:11:52,440
And 2009 joined Pivotal Labs.

219
00:11:53,340 --> 00:11:55,800
And April of – sorry, 2010 joined Labs.

220
00:11:56,000 --> 00:11:57,800
And April opened the Singapore office.

221
00:11:58,760 --> 00:12:05,200
And so I was the director of the Singapore office until we sold it to NEO.

222
00:12:05,720 --> 00:12:06,820
I went with SAIL.

223
00:12:08,060 --> 00:12:17,160
And then in 2014, left NEO and moved back to Seattle and worked again with now the new Pivotal to open the Seattle office.

224
00:12:17,420 --> 00:12:35,880
So I was the director of the Seattle Pivotal Labs office for another two or so years and then got very interested in the travails, the opportunities to help our large, complex enterprise clients change behavior.

225
00:12:37,240 --> 00:12:55,860
And so I was quite happy to take a break from the office director role and focus on driving success, particularly the success that comes from our clients making lots of money by engaging with our tools and processes as patterns and practices.

226
00:12:56,580 --> 00:13:08,260
And a lot of that requires getting the business and the IT to actually collaborate on identifying valuable new opportunities and then building software and teams to exploit those opportunities.

227
00:13:10,080 --> 00:13:12,720
So what's the – so you mentioned the system advisory group.

228
00:13:12,840 --> 00:13:18,020
So you're a collection of superheroes based different parts of the country here in the U.S.

229
00:13:18,040 --> 00:13:19,360
What's the charter?

230
00:13:19,780 --> 00:13:21,780
Like what is that team supposed to accomplish?

231
00:13:24,160 --> 00:13:26,280
Help Josh McKenty scale?

232
00:13:26,580 --> 00:13:26,880
Yeah.

233
00:13:27,400 --> 00:13:32,580
So it was – his original name for the group was the Technosocial Systems Advisory Group.

234
00:13:32,920 --> 00:13:33,660
Rolls off the tongue.

235
00:13:33,720 --> 00:13:34,500
Rolls off the tongue.

236
00:13:34,700 --> 00:13:41,640
And I encouraged him to drop the Technosocial part because I didn't have an adequate supply of pocket protectors at the time.

237
00:13:43,920 --> 00:13:50,780
So there's a huge class of conversations that McKenty has been having with our complex clients.

238
00:13:51,620 --> 00:13:58,460
And a lot of that comes to – he calls himself sometimes the couch to get IT and business to talk together.

239
00:13:59,340 --> 00:14:06,560
And also there's a fair bit of just getting different groups inside Pivotal to talk together and manage escalations.

240
00:14:07,440 --> 00:14:14,600
And he was supporting like 35 accounts, which is a lot for a single human to manage.

241
00:14:15,600 --> 00:14:37,400
And so started building out a team to work with a – let's say the mid and senior leadership of our accounts and help them think about the execution strategy.

242
00:14:37,400 --> 00:14:48,740
We've been really thinking a lot about right now this – calling it the conflicted middle or the middle management bind.

243
00:14:49,860 --> 00:15:02,560
Our engagements with our customers tends to put the middle of the hierarchy in a very stressful position where they're being asked to support the new behaviors that Lab is busy teaching to the delivery teams

244
00:15:02,560 --> 00:15:10,780
and cope with the limitations that Cloud Foundry adoption removes, which is awesome.

245
00:15:12,780 --> 00:15:18,160
And all of that is in service of these sort of larger strategic goals that their senior leadership have changed.

246
00:15:18,260 --> 00:15:21,380
The CEO and the CIO or CTO want new behavior.

247
00:15:22,580 --> 00:15:31,240
But their informal and formal contracts with their bosses and peers and sort of these complex network hierarchies is not changing.

248
00:15:31,240 --> 00:15:38,500
And so they quickly find that they're in conflict with their peers if they want to support these teams or their managers.

249
00:15:39,640 --> 00:15:46,260
And it's very hard to untangle those relationships and figure out what's a viable approach.

250
00:15:47,620 --> 00:15:57,580
And, you know, I've been – we've been doing a lot of strangler pattern conversations on the IT side of how do you sort of build a new system in place

251
00:15:57,580 --> 00:16:03,420
and incrementally move work from a legacy environment onto a new environment?

252
00:16:03,660 --> 00:16:07,800
And I've been really thinking about, like, what is the metaphor for human institutions?

253
00:16:08,440 --> 00:16:21,240
How do we do very small incremental changes from one org structure into a new org structure where we're able to always experiment and then roll back or test hypotheses and deploy

254
00:16:21,240 --> 00:16:31,460
in contrast to, like, big bang org redesigns where it's like, hey, and some of our customers every January, it's just chaos for six weeks

255
00:16:31,460 --> 00:16:33,580
because everybody's changing their managers and their team charter.

256
00:16:36,660 --> 00:16:42,800
And I want there to be less chaos and more just continuous incremental improvement and iterative improvement.

257
00:16:43,940 --> 00:16:48,240
So what do those entwining things look like?

258
00:16:48,340 --> 00:16:53,420
I mean, you're trying to pull apart the spaghetti bowl back into a nice package, so to speak.

259
00:16:54,540 --> 00:16:58,500
But, like – well, and I'll ask it in a more naive way.

260
00:16:58,640 --> 00:17:10,160
It's like, so why don't you just change people's incentives and, like, get a bag of cash like Santa and kind of hand things out to make people change?

261
00:17:11,800 --> 00:17:12,940
That'd be lovely.

262
00:17:15,160 --> 00:17:20,240
It turns out there's a tremendous amount of paperwork that involves, in any organization, to get a bag of cash.

263
00:17:20,760 --> 00:17:22,300
So that is not easy.

264
00:17:23,040 --> 00:17:25,680
It doesn't just come from the frozen north?

265
00:17:26,380 --> 00:17:26,720
Right.

266
00:17:27,720 --> 00:17:33,260
Which I think is part of why cost takeout is a big part of many of our enterprise engagements.

267
00:17:33,740 --> 00:17:39,460
And so they're looking at the cost savings that come from migrating to the cloud and the just much more efficient use of infrastructure

268
00:17:39,840 --> 00:17:42,640
because that pays for the other activities we want to do.

269
00:17:43,360 --> 00:17:46,420
So it's like, okay, you know, where are we going to get this bag of cash?

270
00:17:46,840 --> 00:17:49,860
And then the other question is, change our incentives to what?

271
00:17:51,500 --> 00:18:02,040
And it's easier for a local individual to say, well, if my incentives were such and such, then I could support this behavior.

272
00:18:03,360 --> 00:18:13,400
But if we change that person's incentives, we also have to change the incentives of the people around them and around them.

273
00:18:14,280 --> 00:18:24,180
And so it's, I think, very hard for somebody who's sitting in the C-suite of our customers to say, like, this is how we need to change the incentives of everybody in the organization.

274
00:18:24,640 --> 00:18:27,000
Maybe this happens, and I just haven't seen it.

275
00:18:27,740 --> 00:18:31,800
But my hypothesis is that's a tremendously difficult design problem.

276
00:18:32,700 --> 00:18:41,720
And I suspect that if we spent six months or a year of study to say, we're going to understand your organization and sort of define a new incentive structure,

277
00:18:42,120 --> 00:18:44,920
that that would be out of date by the time we're done.

278
00:18:45,100 --> 00:18:46,420
And it wouldn't have acted to move the ball.

279
00:18:46,560 --> 00:18:48,920
It would have just spent a bunch of money and lost a year of calendar time.

280
00:18:49,260 --> 00:18:55,900
Yeah, I don't think anyone's really come up with a generic, repeatable solution.

281
00:18:56,140 --> 00:19:02,300
Like, I read a lot of stuff, books and whatever else, on basically, like, corporate change management.

282
00:19:03,080 --> 00:19:05,000
And they're very long.

283
00:19:06,220 --> 00:19:10,980
And they have a lot of content and studies of, like, you know, compressed air companies.

284
00:19:11,460 --> 00:19:17,780
And I was reading one recently, and they talk about DEC, you know, D-E-C, which is kind of interesting and slightly relevant.

285
00:19:18,160 --> 00:19:21,720
But it is all of their change programs.

286
00:19:21,780 --> 00:19:31,620
And, of course, they all reference Alcoa, which is like, you know, I'm always pleased as punch to read the Alcoa change story for the 20th time, which is fine.

287
00:19:32,180 --> 00:19:40,940
But, like, yeah, none of them really seem to operate on a speed that sort of people are probably expecting,

288
00:19:40,940 --> 00:19:50,220
which makes me, you know, one of my, like, I always hate it when people reframe what you think the problem is because I just want people to solve my problem.

289
00:19:50,500 --> 00:20:01,220
But to do that, one of the things that I kind of fall back on is, like, maybe you should just have, like, lower expectations of, like, the time it will take, right?

290
00:20:01,240 --> 00:20:08,760
Like, it's not going to happen overnight, and you're not going to, like, transform a $5 billion business in a year and so forth and so on, right?

291
00:20:08,800 --> 00:20:22,280
And so, like, the thing that I've observed is, like, the smaller you start, the not faster, but the better chance you'll have at getting bigger and scaling up rather than just sort of, like, changing everything over.

292
00:20:23,320 --> 00:20:23,680
Yes.

293
00:20:24,640 --> 00:20:25,940
But can you play through for me?

294
00:20:26,020 --> 00:20:30,220
I mean, I know this whole switching from optimizing the cost to maybe optimizing for speed or any of that.

295
00:20:30,620 --> 00:20:32,420
I mean, play through something real life here.

296
00:20:32,420 --> 00:20:35,920
You can protect the names of the innocent with, you know, who companies.

297
00:20:36,040 --> 00:20:38,880
But, I mean, tell me about, talk us through some of these misalignments.

298
00:20:38,880 --> 00:20:46,740
Like, what's the thing that might be happening at the C-suite that then as you get down to some director of IT, they need to try to accomplish to make that thing happen?

299
00:20:46,820 --> 00:20:48,980
And then some managers of dev teams get out of.

300
00:20:49,260 --> 00:20:51,760
So, I mean, talk to me about what starts the ball in the whack.

301
00:20:51,920 --> 00:20:52,120
Sure.

302
00:20:52,120 --> 00:21:05,700
So, one of the things that's really important for us when we talk about the improvements in throughput for a delivery team is they're able to make very fine-grained and high-quality decisions about scope.

303
00:21:06,600 --> 00:21:10,100
And, you know, I'm being sort of asked to implement this feature.

304
00:21:10,360 --> 00:21:12,620
How much gold do I plate onto that feature?

305
00:21:12,940 --> 00:21:14,120
How awesome does it need to be?

306
00:21:14,180 --> 00:21:15,580
How robust does it need to be?

307
00:21:17,080 --> 00:21:34,400
And if I have a really good sense of this is the customer that feature is serving and this is the business outcome that that feature is intended to realize, we as a team are in a very good position to make very good decisions about how much quality, how much scope to put into that feature.

308
00:21:36,400 --> 00:21:53,840
Now, if I am working for a manager who is then preparing reports for her manager, who is then preparing reports for his VP, who is then preparing reports for the board, saying, we funded this program.

309
00:21:53,980 --> 00:21:55,780
We want to know what percent complete it is.

310
00:21:57,360 --> 00:22:02,740
And, you know, I've been working in some of the aerospace sector for a while.

311
00:22:02,940 --> 00:22:06,360
And so there's a long history of government contracting tied into that.

312
00:22:07,060 --> 00:22:15,920
And you have sort of these, like, 4,000-page, like, RFPs with, like, all of the bullet points that this thing needs to implement and execute on.

313
00:22:16,940 --> 00:22:26,260
And so if you have the strong expectation of, I want to be knowing what percent done I am, and so I'll go, well, percent done of what exactly?

314
00:22:26,260 --> 00:22:32,680
How much scope is actually necessary to implement and take that off as done?

315
00:22:34,360 --> 00:22:38,340
It becomes very hard for people to communicate.

316
00:22:38,580 --> 00:22:43,920
It's like, well, you know, I can't tell you what this feature is supposed to do and what the business customer is.

317
00:22:43,980 --> 00:22:46,700
Like, I just got the spec sheet, and I want to know if it's done or not.

318
00:22:47,840 --> 00:22:59,760
And the team is saying, well, I can implement that feature, but I can't help you with the situation of is it done or not, or how much quality should we bake into that unless I can understand who the user is.

319
00:23:02,260 --> 00:23:14,300
So this sort of desire to report, well, when is this thing going to be done and how complete is it, can be very stiff through the entire vertical of the organization.

320
00:23:14,300 --> 00:23:19,800
If everybody above the delivery team is saying, well, I want to know what percent completed is, it's like, well, percent of what?

321
00:23:19,800 --> 00:23:33,880
And that percent of what means that the chain is not thinking very deeply about the outcomes and who the users are and what that need is, and they're not giving the small team the tools they need to make scope decisions.

322
00:23:35,500 --> 00:23:36,680
So that's one example.

323
00:23:37,120 --> 00:23:42,280
I think another example that I run into is very commonly around performance management.

324
00:23:44,480 --> 00:23:46,440
It still surprises me.

325
00:23:46,600 --> 00:23:56,360
There are many companies that are asking their managers to grade people on curves, and that is in direct conflict with healthy team formation.

326
00:23:57,720 --> 00:23:57,860
Why?

327
00:23:58,500 --> 00:24:00,820
Because it means that you're competing with your people on the team.

328
00:24:01,800 --> 00:24:04,920
It's like, okay, Richard, only one of us is going to get the five.

329
00:24:05,840 --> 00:24:06,100
Right.

330
00:24:07,220 --> 00:24:08,840
It's going to be you or it's going to be me.

331
00:24:09,240 --> 00:24:10,420
How does that encourage collaboration?

332
00:24:10,420 --> 00:24:10,760
That's right.

333
00:24:10,840 --> 00:24:11,200
That's right.

334
00:24:11,380 --> 00:24:11,780
That's right.

335
00:24:12,260 --> 00:24:24,700
And I've pushed some really wonderful employees into labs offices that I've hired where they just couldn't get high-quality work because they were in competition with more senior engineers in their teams for high-quality work.

336
00:24:24,840 --> 00:24:25,240
Interesting.

337
00:24:26,020 --> 00:24:35,080
And then it's like, well, you know, this performance management system is designed to work for all of the employees in our 50,000-person organization.

338
00:24:35,660 --> 00:24:41,000
Why are you, little manager of this, like, 30-person org, special and different?

339
00:24:41,000 --> 00:24:44,200
It's like, oh, my goodness, you have to have a lot of conversations to change that.

340
00:24:44,640 --> 00:24:52,800
And yet, to some degree, pivotal, like, our value is we're going to deliver to these radically more effective product development teams.

341
00:24:52,800 --> 00:24:54,200
We have to change that whole.

342
00:24:56,740 --> 00:25:03,300
But as you say, if I'm a senior manager and now I'm not only grading my team differently and I'm redefining what done means.

343
00:25:03,360 --> 00:25:03,700
That's right.

344
00:25:03,800 --> 00:25:09,960
Up to some manager above me who just has a line on a spreadsheet or a project plan or a funding plan, that creates a ton of stress.

345
00:25:09,960 --> 00:25:14,520
As you're saying, on that layer of people who are trying to sincerely introduce change.

346
00:25:14,640 --> 00:25:15,480
But that's a lot of pressure.

347
00:25:15,800 --> 00:25:16,080
Absolutely.

348
00:25:16,440 --> 00:25:31,380
And then it may not even be like, okay, like, I've sold my direct manager, but she now needs to go talk to all of her, like, finance business partners and HR business partners and say, like, these expectations that you're building into your spreadsheets, we need to change them.

349
00:25:31,380 --> 00:25:39,220
Um, I had a lovely conversation with a, um, uh, I think it was a, a shipping, a shipbuilding company.

350
00:25:40,100 --> 00:25:47,780
And, um, this, uh, VP director came up, uh, sorry, IT director came up to me and was like, how do you get your teams to not gold plate things?

351
00:25:48,580 --> 00:25:50,660
I was like, well, do they know who their users are?

352
00:25:50,720 --> 00:25:52,920
It's like, oh no, the business won't let us talk to the users.

353
00:25:54,340 --> 00:26:06,820
I was like, well, if the business needs to own that user relationship so they have control and you can't build a team that is a mix of the business people and the development people, the developers are never going to get good feedback as to who the customer is.

354
00:26:07,260 --> 00:26:12,920
And, um, as a programmer, like building awesome gold plated systems is bananas fun.

355
00:26:13,080 --> 00:26:16,060
Like I'm going to spend the extra two weeks making this thing awesome.

356
00:26:16,060 --> 00:26:17,020
So I'm proud of it.

357
00:26:17,920 --> 00:26:21,220
Um, if I don't have any feedback as to what good means.

358
00:26:21,840 --> 00:26:23,680
Now, those are three great points.

359
00:26:23,760 --> 00:26:24,480
Coté, you next.

360
00:26:24,940 --> 00:26:37,240
Well, I, uh, yeah, I have this uncharitable phrase that to myself is a cliche nowadays, which is like, you know, to put it in the family friendly version of it, like, you know, uh, you know, don't do dumb.

361
00:26:37,260 --> 00:26:38,700
Dumb stuff, right.

362
00:26:38,740 --> 00:26:48,980
Which, which, uh, is sort of like, well, of course, you know, if your developers aren't talking to your end users, you're going to get, I don't know, middling garbage, right?

363
00:26:48,980 --> 00:26:58,220
Like if you, if you're not sort of paying attention to the way people are using your software and feeding that back into the system, then, uh, logically it won't work out very well.

364
00:26:58,220 --> 00:27:03,980
And, and unfortunately, a lot of the dumb stuff that people have to do is because they can't change it.

365
00:27:04,260 --> 00:27:15,340
Or the worst case, like the, um, I don't know, intellectually depressing thing is when the higher level executives are like, we have to transform and change and we're still going to stack rank everyone.

366
00:27:15,340 --> 00:27:22,760
And it's sort of like, uh, it's sort of like, you know, you, you don't think the system you currently have is effective and you want to change the current system.

367
00:27:22,760 --> 00:27:29,140
So the first step is to not change the current system, uh, or, or, you know, figure out how to change things around that much.

368
00:27:29,140 --> 00:27:34,240
Like I remember when I, I, you know, I've unfortunately been a manager several times in my career.

369
00:27:34,240 --> 00:27:39,640
I don't know if that's unfortunate for me or the people who worked for me, but man, stack ranking sessions are ridiculous.

370
00:27:39,760 --> 00:27:48,080
There's like that, there's like that, uh, one person over there with like a pile of paperwork and who used to be like, you know, I don't know, a captain in the army.

371
00:27:48,080 --> 00:27:49,760
And you're like, well, that person's going to win.

372
00:27:50,140 --> 00:27:50,540
Right.

373
00:27:50,580 --> 00:27:54,560
Like whoever's like organized the most and like, is the most aggressive and all that.

374
00:27:54,560 --> 00:27:58,460
Like it's a total like, uh, stuff show, so to speak.

375
00:27:58,920 --> 00:27:59,760
Um, yeah.

376
00:27:59,760 --> 00:28:05,660
And it, and it does, uh, it encourages hero culture, uh, which is not, not what you want in the IT world.

377
00:28:05,660 --> 00:28:29,460
So anyways, you know, Coté, for your example, you know, if, if I'm, if I'm a, a senior leader in this organization and I don't have a good model that describes the inputs and the outputs to the human dynamics of these product teams, which we still don't to say like, I'm going to change everything all at once.

378
00:28:29,960 --> 00:28:31,240
Like that feels bananas.

379
00:28:31,440 --> 00:28:31,720
Yeah.

380
00:28:31,800 --> 00:28:32,080
Yeah.

381
00:28:32,160 --> 00:28:32,600
Exactly.

382
00:28:32,600 --> 00:28:36,160
I want to do incremental experiments and like limit the number of control things.

383
00:28:36,280 --> 00:28:36,680
Yeah.

384
00:28:36,960 --> 00:28:41,660
And, you know, we're in this position of saying, well, stack ranking is obviously one of those things that you want to control.

385
00:28:41,960 --> 00:28:48,440
But on the other side of the table, I can see that that wouldn't be obvious at all because that may have worked and have very positive benefits.

386
00:28:48,620 --> 00:28:48,940
Yeah.

387
00:28:48,940 --> 00:28:55,800
I had a long conversation with Austin Vance, uh, who was the former labs director in Chicago, uh, now at Braintree.

388
00:28:56,300 --> 00:29:00,500
And he's like, well, here are six awesome things that organizations can get from stack ranking.

389
00:29:00,760 --> 00:29:05,300
It encourages strong managers to take their good people and spread them across the organization.

390
00:29:05,300 --> 00:29:07,860
And so you don't get these like hotspots of talent.

391
00:29:07,980 --> 00:29:08,340
Yeah.

392
00:29:08,640 --> 00:29:12,580
And like, that is a, that is a delight design solution.

393
00:29:12,660 --> 00:29:15,260
And we can say like, is that what the organization wants?

394
00:29:15,260 --> 00:29:15,580
Right.

395
00:29:15,580 --> 00:29:20,740
But there, there are, you know, institutionally interesting reasons to, to argue for that.

396
00:29:21,100 --> 00:29:34,380
And so that is like, well, how do we, how do we design experiments or how do we quickly iterate through things to give leaders feedback and signal on this is a change that's going to drive the outcome you want.

397
00:29:34,380 --> 00:29:36,920
And this is not a change that's going to drive the outcome you want.

398
00:29:37,020 --> 00:29:37,500
Right, right.

399
00:29:37,780 --> 00:29:38,140
Exactly.

400
00:29:38,320 --> 00:29:44,100
Like, like you can't, you can't expect to, uh, people to, to intuitively, what's the word prima facie?

401
00:29:44,280 --> 00:29:45,900
They won't just believe the truth.

402
00:29:45,900 --> 00:29:51,060
If you show it in front of them, like some sort of like a Plato's cave, like that's not the way people work.

403
00:29:51,060 --> 00:29:51,300
Right.

404
00:29:51,540 --> 00:30:04,360
You've got to like put some system in place to make them, uh, believe in it and realize it on their own, which I think, I think, I mean, that's, that's over the years, that's been my observation of a huge, or I don't know what my observation means.

405
00:30:05,000 --> 00:30:14,380
Uh, what I've thought about a huge amount of always trying to change it is like, it's not like we have a good history in software development of being trustworthy or reliable, right?

406
00:30:14,380 --> 00:30:18,020
Like, like no matter, like, I don't know whose fault it is.

407
00:30:18,080 --> 00:30:21,680
That's been long lost to compilers and bugs and things like that.

408
00:30:21,680 --> 00:30:29,200
Uh, but it's just like, uh, yeah, we haven't been really great at being a reliable delivery mechanism, so to speak.

409
00:30:29,360 --> 00:30:38,020
And so it's kind of little wonder that the way most people think of it is we need a tremendous amount of process and, uh, I don't know, feelings of controls wrapped around it.

410
00:30:38,020 --> 00:30:54,700
So, yeah, I mean, like you're saying, it's almost like you have to, uh, I don't know, win back the trust by walking people through the system and, and very systematically not changing everything at once, but figuring out a way to win back that trust by having kind of a small series of changes that you walk through.

411
00:30:55,540 --> 00:30:55,980
Yeah.

412
00:30:57,500 --> 00:31:03,140
You sort of touched on the, like, is, is software development ready to be a professional engineering discipline?

413
00:31:04,180 --> 00:31:08,380
And, uh, I think we aspire to be, but we have a long, a long way to go.

414
00:31:08,480 --> 00:31:12,020
And that is because we have inflicted so much harm on our business customers over the last year.

415
00:31:12,340 --> 00:31:13,520
That's, that's right.

416
00:31:13,700 --> 00:31:19,040
I mean, you know, there's a lot of horses that had to die to get electricity put in place, if I remember.

417
00:31:19,300 --> 00:31:23,860
And so, like, we, we got to exit the horse killing phase of, of technology.

418
00:31:23,860 --> 00:31:53,380
But I think, I think what, what, you know, it sounds like you're studying and, and, and you're hitting upon is like, it feels like when it comes to, let's call it professional software development as distinct from hobbyist or maybe even scientific is now the big challenges are not, not only scaling the technology, which is kind of fun, but really scaling the engineering practices and switching it over from something to, to be able to get to the point where you've got all these, as we would call them product teams, uh, sort of developing on their own.

419
00:31:53,640 --> 00:31:56,080
And, and, uh, yeah, that's difficult.

420
00:31:56,320 --> 00:31:58,060
So, so what have you found so far?

421
00:31:58,120 --> 00:31:59,140
Have you solved the problems?

422
00:31:59,540 --> 00:32:00,600
I solved the problems.

423
00:32:00,780 --> 00:32:01,760
Well, I've got some ideas.

424
00:32:02,020 --> 00:32:05,980
Um, I think we're making, I think we're making real strides as a, as a civilization.

425
00:32:06,840 --> 00:32:23,000
Um, you know, I, I feel like the, the data coming out of our experience, building these, these small teams that have a business outcome that they can, they can measure progress against, uh, who are deploying onto reliable, durable pipelines.

426
00:32:23,000 --> 00:32:33,360
So the, the, the cognitive scope that they need to think about, and most importantly, their cycle time, like human scale cycle times and rapid feedback is transformative.

427
00:32:33,960 --> 00:32:47,880
That is transformative, like allowing people to learn and building a context where people can learn, um, and improve and own their destiny a little bit, um, has made, I think a tremendous difference in the success of products that we've worked with.

428
00:32:47,920 --> 00:33:01,840
And, you know, one of the, I think the tremendously rewarding things about being part of our labs practice is we get to see that over and over and over again, where we come in with tremendously fraught environment, uh, relationships between business and IT.

429
00:33:02,360 --> 00:33:14,680
Um, we did a project here last year where the business was out shopping for outside vendors to replace this internal tool for one of our customers.

430
00:33:15,400 --> 00:33:23,160
Um, and, uh, the internal IT people didn't want to lose the business and they were also like very concerned about the loss of strategic IP.

431
00:33:24,440 --> 00:33:30,120
Like when you engage, uh, with outside vendors, they'll want to sell that solution to other customers.

432
00:33:31,560 --> 00:33:45,280
Um, and, uh, we started the discovery and framing process and had, uh, the enterprise customers, uh, paired with labs people out talking to the business users and understanding

433
00:33:45,280 --> 00:33:49,960
what their real needs were like, this is the first time we've actually had this conversation.

434
00:33:51,280 --> 00:33:56,780
Um, and then we started building, uh, demos that they could interact with and play with and give feedback on.

435
00:33:56,840 --> 00:34:05,460
And then we started getting like very minimum, minimum viable products into production that they can interact with that were orders of magnitude quicker than their previous workflow.

436
00:34:06,240 --> 00:34:19,180
Um, and, um, that made a tremendous difference, tremendous difference, um, I think, you know, larger scale building sort of institutional change around these small scale successes.

437
00:34:20,240 --> 00:34:32,240
Um, I've been experimenting with, uh, Toyota improvement Kata as a process improvement pattern that, uh, Toyota has been using to improve performance in their factories for a long time.

438
00:34:33,240 --> 00:34:52,340
Um, and briefly it's this idea of, uh, get alignment on your future vision, use that to set context for alignment on your current reality, set a next target condition, some, some, something that is just out of reach in terms of knowing how to get there, but not tremendously out of reach.

439
00:34:52,340 --> 00:34:57,300
Um, and then run experiments to try to move you from your current reality into that next target condition.

440
00:34:58,940 --> 00:35:20,240
What I find very powerful about this is when we, a lot of that, that exercise of finding some shared vision is a constructive activity that you can use to get diverse stakeholder groups together to at least find, okay, we disagree with many things, but here's a common thing we can all agree on.

441
00:35:20,240 --> 00:35:29,300
Um, and constructively find some common ground and then try to sort of take that common ground and anchor on a current reality.

442
00:35:29,300 --> 00:35:30,900
So we have some strengths to work on.

443
00:35:30,980 --> 00:35:32,340
We have some challenges to overcome.

444
00:35:32,700 --> 00:35:50,620
And then the experimental framing is one that leads to very little judgment and it provides a framework for being wrong about your vision, being wrong about your understanding of today's reality, being wrong about your understanding of the next target condition.

445
00:35:50,940 --> 00:35:54,360
The, the, the, the, the only way to sort of fail an experiment is not to run it.

446
00:35:55,020 --> 00:36:03,540
Like you'll learn from that result and that, that learning teaches you where the defects in your thinking was.

447
00:36:04,400 --> 00:36:18,040
And so, um, um, I've been running this workshops around this for sort of groups of four to 20 people or 25 people, which are small enough that you can get it done in a day or so.

448
00:36:18,040 --> 00:36:32,200
And, um, um, um, big enough that you can get like a cross section and, um, I'm, I'm thinking about this as a, as a mechanism to help people, the organization get clear.

449
00:36:32,200 --> 00:36:38,980
Because like what, what we talked about earlier, like the managers, they all know the problem with their incentive, like how that conflicts with their behavior.

450
00:36:39,180 --> 00:36:47,580
What they don't know is how changing their incentive is as going to ripple out to the next tier and affect their peers and stakeholders.

451
00:36:48,200 --> 00:36:51,940
And we can have that conversation in the context of the improvement kata.

452
00:36:52,200 --> 00:36:56,700
And then as a group, they can try some experiments and see how did this actually ripple out?

453
00:36:57,060 --> 00:37:04,960
And then we can use that to try to continue to ripple that out with more of these, um, or conversations with senior management.

454
00:37:05,800 --> 00:37:06,240
Interesting.

455
00:37:06,580 --> 00:37:10,960
So I wanted to take you through something that you mentioned a couple of times.

456
00:37:11,020 --> 00:37:13,640
It kind of undercurrents a lot of what you talk about.

457
00:37:13,760 --> 00:37:22,920
And I wanted you to maybe first define for us what you think empathy is because it covers in how do you heal that relationship between potentially the engineering and business side?

458
00:37:22,920 --> 00:37:27,640
And how do you understand your customer, how do you actually potentially do these value exercises together?

459
00:37:27,740 --> 00:37:29,400
Do you know where people come from?

460
00:37:29,480 --> 00:37:38,760
But I, I was part of a training class last week where we spent a lot of time on this and different definitions of empathy and how you can mistake that for other things.

461
00:37:38,860 --> 00:37:42,100
So, I mean, when you come in and describe empathy to someone, what is that to you?

462
00:37:44,380 --> 00:37:46,700
Uh, I have not been asked to describe empathy.

463
00:37:47,300 --> 00:37:51,520
Um, so I think about empathy is twofold.

464
00:37:51,520 --> 00:37:55,540
Um, it is, it is feeling what the other person is feeling.

465
00:37:57,340 --> 00:38:06,060
And secondarily, it is the other person feels heard and understood.

466
00:38:06,060 --> 00:38:24,280
And what, what I'm seeing with empathy right now is that, uh, I'm talking with somebody who is wrestling with very challenging problems and I can listen to those problems.

467
00:38:24,280 --> 00:38:27,840
And one, I got a lot of information about their reality, which is wonderful.

468
00:38:28,360 --> 00:38:40,060
Second, they feel heard and then they get to see a different solution out of that same set of inputs.

469
00:38:40,800 --> 00:38:49,200
So if you actually, um, get this, I, I think it's actually this sort of like almost physiological coupling.

470
00:38:49,580 --> 00:38:57,220
It's like, you see that I've heard you and that I have, I'm experiencing the same feelings that you're having.

471
00:38:58,440 --> 00:39:03,680
And then I'm able to sort of broaden or bring alternative outputs.

472
00:39:03,840 --> 00:39:05,880
It's a very broadening experience.

473
00:39:07,000 --> 00:39:14,580
Um, I try to do this with my daughter a lot who's four, like mirror back to her that I'm experiencing, understand how she's feeling.

474
00:39:14,580 --> 00:39:19,380
And then I can model for her a different way of handling and coping with those feelings.

475
00:39:20,540 --> 00:39:22,600
And I think you need, you need both.

476
00:39:22,760 --> 00:39:29,260
Like it's, it doesn't help me if you're like, well, yeah, Carl, you can take this other thing or go in this other direction.

477
00:39:29,300 --> 00:39:36,000
It's like, well, that advice is only valuable if I feel like I've been heard and you actually understand all of the complexity.

478
00:39:36,340 --> 00:39:36,740
Right.

479
00:39:37,120 --> 00:39:55,060
And so with the empathy that we do for me, that's about like, um, trying to understand and, and feel the holistic experience, the person with the other side of the table so that we can craft a better solution together and model for them a different physiological response.

480
00:39:55,220 --> 00:39:55,660
Yeah.

481
00:39:56,140 --> 00:39:56,580
Yeah.

482
00:39:56,580 --> 00:39:57,880
That's, that's, that's interesting.

483
00:39:57,880 --> 00:40:00,080
Like, like I, I haven't thought of empathy in that way.

484
00:40:00,080 --> 00:40:06,080
So I'm glad Richard asked you a confounding question there because we, we found it.

485
00:40:06,140 --> 00:40:07,500
Is that the opposite of confounding?

486
00:40:07,940 --> 00:40:13,320
Uh, and, and it seems like, uh, it's also, I had to front load a lot of like this, this stuff.

487
00:40:13,320 --> 00:40:23,540
Like, I think, uh, I think it's why in like, uh, socialists probably why in social situations, I feel like my head is like, you know, uh, a box of leftover coins being shaken around.

488
00:40:23,620 --> 00:40:30,760
And it's always a strange situation, but like, like I always think of empathy is like understanding people, like being in their shoes, right?

489
00:40:30,760 --> 00:40:32,020
Like to use that, that phrase.

490
00:40:32,260 --> 00:40:34,240
And then, and then there's a third part.

491
00:40:34,300 --> 00:40:43,400
I don't know how to make a snappy little phrase out of, but there is, uh, you know, acknowledging that someone's been heard, which everyone likes that they want to have been heard.

492
00:40:43,400 --> 00:40:44,780
And I don't mean that in a flippant way.

493
00:40:45,040 --> 00:40:47,140
It's a, it's a very kind thing to do to someone.

494
00:40:47,380 --> 00:40:53,600
But then I think, I think the reason, like, I'll speak for myself and then people broadly as, as is my practice.

495
00:40:53,600 --> 00:41:05,000
But like, I think the thing I always find like, uh, frustrating is the wrong word, but just sort of hollow, uh, about empathy talk in the tech industry is like, I don't know what to do with that.

496
00:41:05,060 --> 00:41:06,980
Like, I don't know the utility of it.

497
00:41:06,980 --> 00:41:07,320
Right.

498
00:41:07,440 --> 00:41:23,820
And I, and I think, especially if you're in like a managerial position, I mean, you're basically a bureaucrat in, in a good version of it, which is a bureaucrat is there to make sure in a utilitarian way that the process is, is followed and things are fine and stuff doesn't, you're an engineer of the organization basically.

499
00:41:24,240 --> 00:41:30,120
And so like this idea of just understanding and acknowledging something, it doesn't really tell you what to do.

500
00:41:30,320 --> 00:41:37,240
But I think, I think what, you know, what you've added in that I think is exciting and interesting is like, and it results in an outcome, right?

501
00:41:37,260 --> 00:41:44,960
Like when we say empathy, we don't just mean some sort of like X-Men thing where you can read someone's mind and their feelings like, uh, I don't know, like a beta zoid or whatever.

502
00:41:45,140 --> 00:41:55,920
But it's more like, it also allows you to figure out like what to do to make a situation better and how to actually take actions, which I think is an angle on it that, uh, doesn't always come up.

503
00:41:56,560 --> 00:42:07,020
Well, there was one, I mean, when we were studying this last week, it was, we actually named it that there's emotional empathy in that point of like, literally, if you bang your shin, like my brain actually lights up in a way, like I kind of feel it.

504
00:42:07,080 --> 00:42:07,840
Like it hurts, right?

505
00:42:07,860 --> 00:42:09,740
I understand you're, you're hurt, right?

506
00:42:09,820 --> 00:42:12,020
You console a friend who lost their parents.

507
00:42:12,020 --> 00:42:13,880
Like those are emotional empathy.

508
00:42:13,980 --> 00:42:16,000
I'm really, excuse me, kind of feeling that.

509
00:42:16,060 --> 00:42:22,500
And then there's the cognitive empathy of, I kind of know what you're thinking and I've listened to you enough to now know, I know where you're coming from.

510
00:42:22,560 --> 00:42:24,900
Now this, none of this means that we're going to agree.

511
00:42:25,280 --> 00:42:28,820
None of this means that we're all going to have to say, but it means, right?

512
00:42:28,860 --> 00:42:36,260
It doesn't mean that somehow I build some universal consensus, but I know where you're coming from and we still may disagree on something, but I've truly listened.

513
00:42:36,380 --> 00:42:37,460
I've understood this.

514
00:42:37,820 --> 00:42:43,320
And so maybe based on compassion, I act on it, or maybe I, you know, I'm better at understanding you.

515
00:42:43,440 --> 00:42:46,260
So it's interesting to just see how empathy can be useful.

516
00:42:46,440 --> 00:42:49,220
It doesn't necessarily result in all of us being on the same page.

517
00:42:49,440 --> 00:42:51,940
So there's two stronger aspects that I want to build on what you said, Richard.

518
00:42:52,060 --> 00:42:59,620
The first is that, you know, part of our facilitation practice is often about breaking people into groups of three.

519
00:43:01,000 --> 00:43:08,480
And the reason we want to do groups of three is we're trying to build buy-in and support for a decision.

520
00:43:10,000 --> 00:43:16,460
And I want everybody in the room to feel like they own a piece of the end decision that the room made.

521
00:43:17,400 --> 00:43:28,300
And what we're coming to believe and what is part of our doctrine as a facilitation practice at Pivotal is that you can't get to decision until you feel like you've been understood.

522
00:43:28,960 --> 00:43:35,720
So if I don't feel like I've been heard, I'm not going to be bought into the decision because it's like, well, I was not understood.

523
00:43:35,980 --> 00:43:39,340
And so my point of view is not reflected in this end decision of the group.

524
00:43:40,460 --> 00:43:51,140
And so we build a lot of exercises around making sure that people feel like they've been heard and ideally actually hearing people.

525
00:43:51,480 --> 00:43:52,600
I like to get both.

526
00:43:52,960 --> 00:43:53,060
Sure.

527
00:43:55,140 --> 00:43:59,920
And oftentimes I've had a couple of conversations with business leaders like, why should I do this workshop?

528
00:44:00,120 --> 00:44:01,480
Like, I know what I need to do.

529
00:44:02,100 --> 00:44:07,800
And I say to them, I say, well, you may know what you need to do, but you're going to need your team to execute.

530
00:44:08,140 --> 00:44:10,920
So you want them to feel like this is also the right thing to do.

531
00:44:11,660 --> 00:44:16,480
And it's also possible that people on your team will improve upon your desired plan.

532
00:44:16,940 --> 00:44:22,820
So if we actually have this conversation where we give a chance for everybody in your team to participate in this decision,

533
00:44:23,360 --> 00:44:27,660
I think the worst case scenario, if we do our job right, is we'll execute your plan,

534
00:44:27,820 --> 00:44:32,580
except that now everybody's going to be bought into it because they feel like they were heard and they participated.

535
00:44:33,400 --> 00:44:36,520
And the best thing that we as a group could come up with is what you went in with,

536
00:44:36,720 --> 00:44:38,340
which is a little bit frustrating as a leader sometimes.

537
00:44:38,460 --> 00:44:41,040
It took all that time, but you still need to get that buy-in.

538
00:44:42,100 --> 00:44:49,440
But there's also the opportunity that ideas and contributions from people in that group will sharpen, improve the idea.

539
00:44:49,920 --> 00:44:53,640
And so at the end of this, you're going to get buy-in and it'll be better than what you went in on.

540
00:44:54,340 --> 00:44:55,740
And so I think that that is awesome.

541
00:44:57,080 --> 00:45:03,020
And so I think that hearing aspect and feeling like people are heard is so important to that empathy.

542
00:45:04,000 --> 00:45:06,660
And then I also, I don't think you can separate the cognitive and the emotional.

543
00:45:09,620 --> 00:45:23,740
And I think that the way that I feel heard and understood cognitively is I see that you are able to experience and feel the emotional impact that it has for me.

544
00:45:24,520 --> 00:45:32,080
And so I think that to have a high-quality conversation about the cognitive content of the conversation,

545
00:45:32,600 --> 00:45:37,360
I also need an open line of communication around the emotional, the feelings that comes up.

546
00:45:37,880 --> 00:45:40,600
Because I think we as humans don't separate those well.

547
00:45:40,600 --> 00:45:44,680
And that is one of the ways that we communicate that the signal has been received.

548
00:45:47,640 --> 00:45:48,000
Interesting.

549
00:45:48,180 --> 00:45:54,080
I know some of the point where, again, reading some things last week in this class was sometimes the emotional can be dangerous

550
00:45:54,080 --> 00:45:59,120
because I can be – I can make decisions because I actually feel this sort of pain.

551
00:45:59,280 --> 00:46:05,240
And I actually might over-rotate on that and say, like, look, I see a homeless person coming into the office and I just give them all my money.

552
00:46:05,540 --> 00:46:09,040
And I was like, that wasn't actually a smart choice because I actually need some of that money still.

553
00:46:09,300 --> 00:46:12,180
But I felt so bad and I put myself in that situation.

554
00:46:12,320 --> 00:46:18,480
So, again, it's a challenge, but maybe it's better to over-rotate and have to back off versus just have no feelings in the first place.

555
00:46:18,740 --> 00:46:20,120
But it's just an interesting conversation.

556
00:46:20,300 --> 00:46:21,640
I don't think in tech we've had a ton.

557
00:46:21,640 --> 00:46:26,380
And you've brought up, I think, as we think about inclusion, as we think about bringing teams together,

558
00:46:26,380 --> 00:46:30,320
then we've probably over-rotated on the sort of clinical aspect of engineering.

559
00:46:30,640 --> 00:46:40,980
Well, so I had a lovely conversation with Sarah May who gave this fantastic talk at PearConf a couple of months ago.

560
00:46:41,800 --> 00:46:44,560
And she was looking at the power history inside Agile.

561
00:46:45,040 --> 00:46:51,740
And her point in that talk is XP was written by, sort of signed on by 12 middle-aged white guys.

562
00:46:51,960 --> 00:46:54,840
It works fantastically well for middle-aged white guys.

563
00:46:55,480 --> 00:47:04,700
And most of the critiques that have really been inherited and used to adjust XP have been ones that also apply to middle-aged white guys or guys who will turn into middle-aged white guys.

564
00:47:07,220 --> 00:47:15,560
And so we talked a little bit about this over lunch, and she's been paying very attention to communication skills and teaching communication skills.

565
00:47:15,660 --> 00:47:26,020
And one of the things that she raised with me was like, hey, middle-aged white guys are generally good at communicating with other middle-aged white guys.

566
00:47:26,020 --> 00:47:36,000
And so when I think about the practice of XP as sort of executed in non-diverse teams, we haven't thought about the discipline of internal communication very much.

567
00:47:37,220 --> 00:47:45,740
And when you're looking to build highly diverse teams, and I believe, without evidence, but that diverse teams result in better products.

568
00:47:48,300 --> 00:47:49,640
You have some evidence for that.

569
00:47:50,620 --> 00:47:56,360
But that is something which I believe to be true, is diverse teams are inherently better from a product outcome.

570
00:47:56,800 --> 00:47:56,900
Yeah.

571
00:47:57,040 --> 00:48:07,260
That we're going to need to teach effective communication skills now for diverse people talking to each other, because that is not something that everyone is good at.

572
00:48:07,400 --> 00:48:07,600
Sure.

573
00:48:07,600 --> 00:48:12,520
And that's not part of much of our technical training today.

574
00:48:13,880 --> 00:48:26,960
Do you see that same sort of, you know, as you, when we're talking to our customers, we're helping them have communication between design people and coders and analysts and people who are doing, you know, claims in the business of, you know, whatever.

575
00:48:27,080 --> 00:48:32,200
It's like, are you seeing, I mean, that seems to reach beyond just how the engineering teams work better together.

576
00:48:32,200 --> 00:48:37,800
It's also, how does engineering become, or software development become better in the organization, right?

577
00:48:38,000 --> 00:48:38,180
Yeah.

578
00:48:38,460 --> 00:48:39,280
No, that's a good point.

579
00:48:39,820 --> 00:48:50,440
And I was thinking, one of our most profound experiences with one of our large enterprise customers here was we ran this, it was called the Pandora Workshop, named after the radio station.

580
00:48:52,940 --> 00:49:03,460
And the internal IT organization was trying to prioritize its backlog, and they were serving sort of six different internal stakeholder communities.

581
00:49:04,200 --> 00:49:05,480
And we're like, cool.

582
00:49:06,100 --> 00:49:11,880
So we built this effectively room-scale board game where we got the six stakeholder communities to come in.

583
00:49:13,000 --> 00:49:28,420
Each of the five different IT sort of major group areas had booths, and the stakeholders went around and had conversations with the different booths, and then we gave the stakeholders poker chips, and they collaborated with each other and funded the work that they actually wanted done.

584
00:49:29,660 --> 00:49:40,520
And the IT folks were just like, I actually had to talk with my customers and stakeholders in language they understood because I wanted them to fund the things that I thought were important.

585
00:49:40,680 --> 00:49:45,080
And so I had to articulate the work that I thought was important and cool in a way that they understood.

586
00:49:46,440 --> 00:49:52,580
And the customers were like, oh, like, we actually had to talk with each other because the way we set it up, like, none of the customers could get everything they wanted.

587
00:49:52,680 --> 00:49:58,080
They had to collaborate internally so that they could fund the things that they wanted, and so they had to find shared goals.

588
00:49:59,240 --> 00:50:06,680
And just building those communication bridges was tremendously impactful for that organization and getting them to talk with each other.

589
00:50:06,680 --> 00:50:14,160
It feels, I mean, I think, I think this also comes back to this change from IT being a cost center to IT being a revenue center.

590
00:50:14,680 --> 00:50:21,400
And when you're a cost center, you think a lot about efficiency and high utilization as opposed to throughput.

591
00:50:22,540 --> 00:50:30,900
And so when you start, like, it becomes like, oh, we don't want to have these people talk to their customers because their customers can interrupt them all the time, and that'll be inefficient and expensive.

592
00:50:33,680 --> 00:50:34,740
So, good.

593
00:50:35,560 --> 00:50:36,140
All right.

594
00:50:36,540 --> 00:50:39,260
Well, those were some fine topics there.

595
00:50:39,400 --> 00:50:44,180
I feel like we could talk for forever, or at least I could, if I let myself.

596
00:50:44,660 --> 00:50:46,300
But we should, it would be good.

597
00:50:46,700 --> 00:50:57,440
We should have you back on and definitely talk about something that you've been alluding to a little bit, which I think is interesting, is like how you have the, I don't know, the organizational version of a strangler pattern.

598
00:50:57,440 --> 00:51:06,320
Which is, I don't know, somehow isolating out things that would slow you down from improving, but that you can't change as well.

599
00:51:06,580 --> 00:51:11,820
And sort of like back-burnering, changing them when the time makes sense.

600
00:51:12,240 --> 00:51:12,740
I don't know.

601
00:51:12,920 --> 00:51:15,400
That's my interpretation of it.

602
00:51:15,600 --> 00:51:18,620
But, yeah, it'd be good ongoing here.

603
00:51:18,960 --> 00:51:23,120
Like, just the topics and things that you encounter would be fun.

604
00:51:23,660 --> 00:51:24,380
What you were going to say?

605
00:51:25,020 --> 00:51:25,800
I'm happy to come back.

606
00:51:25,800 --> 00:51:31,900
I realized I had a conversation with Rob Mee the last time he came to, well, two times before he came to Seattle.

607
00:51:32,800 --> 00:51:47,640
And he was talking about a model he was toying with of, boy, maybe instead of trying to change like a 6,000-person IT organization, we should build a side, like, 10-person IT organization and slowly grow the new IT organization.

608
00:51:47,760 --> 00:51:50,480
And they could hire from the old one as they prove things to be successful.

609
00:51:50,620 --> 00:51:51,480
Yeah, yeah, yeah.

610
00:51:51,480 --> 00:51:54,960
Yeah, well, that's actually, like, that's something I mention every now and then.

611
00:51:55,000 --> 00:51:57,940
But when you look at our customers, that's a pattern lots of them follow, right?

612
00:51:58,000 --> 00:51:59,960
Like, at Allstate, you have composed labs.

613
00:52:00,200 --> 00:52:02,900
And they often set up, like, labs in their own things.

614
00:52:03,000 --> 00:52:10,840
And the idea being, like, as you're talking about, like, I think of it as the immutable organization problem.

615
00:52:10,840 --> 00:52:14,760
Which is, once an organization is set up and successful, you can't change it.

616
00:52:14,840 --> 00:52:21,700
It's just, like, it's not that it's impossible, but to use Ferengi Talk to make my second Star Trek reference, it's not profitable, right?

617
00:52:21,760 --> 00:52:23,100
Like, it's very difficult.

618
00:52:23,640 --> 00:52:32,220
And so instead, and exactly as you're saying, you see people setting up a new organization and you take, like, volunteers at first so you don't get, like, the grumpy detractors.

619
00:52:32,420 --> 00:52:35,180
And then slowly you, I don't know what to call it.

620
00:52:35,180 --> 00:52:36,420
It's not, like, a strangler thing.

621
00:52:36,520 --> 00:52:39,920
It's just, like, I don't know, more sunlight.

622
00:52:40,660 --> 00:52:42,060
It's a strangler fig.

623
00:52:43,020 --> 00:52:43,640
Right, right.

624
00:52:44,560 --> 00:52:45,300
Yeah, yeah.

625
00:52:45,440 --> 00:52:50,940
I'd like to find a much better name for that because I'm trying to find nonviolent metaphors for the work that I want to do everywhere.

626
00:52:51,440 --> 00:52:51,660
Yeah, yeah, yeah.

627
00:52:51,840 --> 00:52:52,920
No, that's true.

628
00:52:53,340 --> 00:52:54,900
You're growing a new tree.

629
00:52:55,740 --> 00:52:56,100
Exactly.

630
00:52:56,400 --> 00:52:59,960
And, I mean, it seems to be a way around a lot of these issues.

631
00:52:59,960 --> 00:53:05,260
Now, the problem is, like, it might be, I don't know what you would call it, begging the solution.

632
00:53:05,500 --> 00:53:15,540
It's, like, if you have the corporate authority and wherewithal to do that in the first place, that might have been a solution to the problems that you had.

633
00:53:16,040 --> 00:53:17,020
But I don't know.

634
00:53:17,200 --> 00:53:28,840
Maybe it's easier just to, like, go to, you know, a senior committee of people and be, like, we're going to go down the street to that abandoned red brick building and set up a new organization and just kind of pretend like we don't exist for a while.

635
00:53:29,380 --> 00:53:31,260
And let us operate differently.

636
00:53:31,980 --> 00:53:33,740
Correctly using begging the solution.

637
00:53:36,460 --> 00:53:44,940
I've given up on that in the world, and I just mentally replace begging the question with ask the question.

638
00:53:45,120 --> 00:53:46,260
But that was not what you did.

639
00:53:46,800 --> 00:53:47,200
Exactly.

640
00:53:47,760 --> 00:53:48,940
It's a whole other thing.

641
00:53:49,120 --> 00:53:51,920
Lots of begging to be had, especially if you give your money over to someone.

642
00:53:52,340 --> 00:53:53,520
Then you become a problem.

643
00:53:53,600 --> 00:53:54,820
The office guy who walks into your office.

644
00:53:55,120 --> 00:53:55,640
That's right.

645
00:53:55,880 --> 00:53:56,120
All right.

646
00:53:56,180 --> 00:53:58,440
Well, we'll find some more time to talk to you with you.

647
00:53:58,440 --> 00:54:03,540
It'd be fun to see how your gallivanting pans out and things that you learn.

648
00:54:03,940 --> 00:54:04,860
So thanks for being on.

649
00:54:04,960 --> 00:54:10,980
If people wanted to follow up with you, like, where would they go to in a non-creepy way?

650
00:54:11,980 --> 00:54:16,740
Well, I post to Twitter very occasionally at Carl Coriel.

651
00:54:18,420 --> 00:54:20,420
I work out of the Seattle Labs office.

652
00:54:21,040 --> 00:54:24,240
I suppose you can send me email at carlcm at pivotal.io.

653
00:54:25,360 --> 00:54:29,960
Well, I like that phrase, speaking of phrases, very occasionally.

654
00:54:30,420 --> 00:54:31,140
That's a good one.

655
00:54:31,640 --> 00:54:32,420
I'm going to have to remember that.

656
00:54:32,520 --> 00:54:37,180
I think when I was in high school, I was commenting at one point that I had a small abundance of something.

657
00:54:37,840 --> 00:54:42,420
And I think very occasionally is right there, right next to it there.

658
00:54:42,880 --> 00:54:43,400
That's good.

659
00:54:43,500 --> 00:54:46,140
I think frequently might also be more precise.

660
00:54:46,140 --> 00:54:46,820
No, no, no.

661
00:54:46,900 --> 00:54:50,480
I think very occasionally is much more precise than frequently.

662
00:54:50,640 --> 00:54:56,300
In the same way that, like, a small abundance is, like, a lot of something, but not, like, a lot of something.

663
00:54:56,860 --> 00:55:00,660
It's a significant amount of something, but not an abundance of it.

664
00:55:01,040 --> 00:55:01,580
I don't know.

665
00:55:02,040 --> 00:55:04,340
We can obviously talk about language a lot, too.

666
00:55:04,600 --> 00:55:05,180
That would be fun.

667
00:55:05,560 --> 00:55:08,200
But, as always, this has been Pivotal Conversations.

668
00:55:08,480 --> 00:55:14,720
If you want to find this episode and all the past episodes, you can go to soundcloud.com slash pivotalconversations.

669
00:55:14,820 --> 00:55:17,380
We post the show notes for this about every Thursday or so.

670
00:55:17,920 --> 00:55:26,200
And also, I think sometime in about this month, or it should be happening now, we're actually going to be merging together the two podcasts we have here at Pivotal.

671
00:55:26,260 --> 00:55:28,840
You've got your Pivotal Conversations and your Pivotal Insights.

672
00:55:28,840 --> 00:55:34,380
Now, of course, we have that moment and a few other podcasts that are sort of in their own style of things.

673
00:55:34,500 --> 00:55:41,780
But our sort of weekly, classically styled podcast, People Talking With Each Other podcast, are going to merge together.

674
00:55:42,060 --> 00:55:47,380
And so, if you keep subscribing to this feed, which you should, eventually you'll see those two merge together.

675
00:55:48,100 --> 00:55:53,960
And, I don't know, I think you'll find a lot more satisfaction and frequency in having both of those.

676
00:55:54,020 --> 00:55:56,580
And if you haven't listened to Pivotal Insights, it's fantastic.

677
00:55:56,780 --> 00:56:01,820
They tend to interview customers and end users a lot, definitely a lot more than we do.

678
00:56:02,000 --> 00:56:03,460
And it'll be a good mix there.

679
00:56:03,980 --> 00:56:05,560
So, with that, thanks for listening.

680
00:56:05,880 --> 00:56:07,160
And we'll see everyone next time.

681
00:56:07,380 --> 00:56:07,780
Bye-bye.