500 Episodes Later: Why Consistency is a Lie (and What Actually Works)

1
00:00:00,000 --> 00:00:05,300
Hello, my name is Mirko Peters and I translate how technology actually shapes business reality.

2
00:00:05,300 --> 00:00:09,320
After hitting the 500 episode mark, I need to tell you something that sounds completely wrong

3
00:00:09,320 --> 00:00:10,320
at first.

4
00:00:10,320 --> 00:00:11,760
Consistency is not the reason this worked.

5
00:00:11,760 --> 00:00:14,680
In fact, the original reason I started this podcast failed.

6
00:00:14,680 --> 00:00:16,560
It didn't just stumble, it failed completely.

7
00:00:16,560 --> 00:00:20,880
I did not build this show because I had some grand media strategy or a vision for a digital

8
00:00:20,880 --> 00:00:21,880
empire.

9
00:00:21,880 --> 00:00:24,680
I built it because I was out of work and needed a job.

10
00:00:24,680 --> 00:00:28,000
And I thought daily public output would function as undeniable proof of my value.

11
00:00:28,000 --> 00:00:32,280
It didn't work out that way, but that failure revealed something much more useful about

12
00:00:32,280 --> 00:00:33,880
how systems actually behave.

13
00:00:33,880 --> 00:00:36,720
So let me take one step back and explain the original design.

14
00:00:36,720 --> 00:00:38,520
Original design, the portfolio machine.

15
00:00:38,520 --> 00:00:41,800
At the beginning, this was not a brand play or a clever content strategy.

16
00:00:41,800 --> 00:00:47,160
It was not some polished creator vision where I had a five year plan, a monetization map,

17
00:00:47,160 --> 00:00:49,600
and a clean audience model ready to go.

18
00:00:49,600 --> 00:00:51,280
The reality was much simpler than that.

19
00:00:51,280 --> 00:00:53,640
And if I'm being honest, it was much more desperate.

20
00:00:53,640 --> 00:00:54,640
I was unemployed.

21
00:00:54,640 --> 00:00:58,080
And when you find yourself in that position, your thinking changes very quickly.

22
00:00:58,080 --> 00:01:02,000
You start asking a very specific question about how to make your value visible in a market

23
00:01:02,000 --> 00:01:06,760
that does not know you, does not trust you, and has no reason to believe you can create

24
00:01:06,760 --> 00:01:08,240
business impact.

25
00:01:08,240 --> 00:01:10,080
That was the actual problem I was trying to solve.

26
00:01:10,080 --> 00:01:13,840
So I designed what I thought was a rational answer, a daily podcast.

27
00:01:13,840 --> 00:01:17,120
The logic seemed sound at the time because I figured if I published every day, people would

28
00:01:17,120 --> 00:01:18,320
see that I was serious.

29
00:01:18,320 --> 00:01:21,800
I believed that by talking through technical topics in public, people would hear that I

30
00:01:21,800 --> 00:01:22,800
knew my field.

31
00:01:22,800 --> 00:01:27,920
I kept going long enough, hiring managers would assume discipline, depth, and reliability.

32
00:01:27,920 --> 00:01:31,640
If all of that was visible, I told myself the system would eventually convert.

33
00:01:31,640 --> 00:01:33,000
This wasn't content as art.

34
00:01:33,000 --> 00:01:35,560
It was content as employability infrastructure.

35
00:01:35,560 --> 00:01:39,760
The podcast was supposed to act like a public portfolio machine where every episode served

36
00:01:39,760 --> 00:01:41,320
as a signal or a visible asset.

37
00:01:41,320 --> 00:01:45,400
It was my way of saying that I could think, explain, and show up while staying consistent

38
00:01:45,400 --> 00:01:46,400
under pressure.

39
00:01:46,400 --> 00:01:49,920
From a system perspective, that belief was built on four specific assumptions that I now

40
00:01:49,920 --> 00:01:51,440
see were quite fragile.

41
00:01:51,440 --> 00:01:54,920
But I assumed that consistency would be interpreted as competence.

42
00:01:54,920 --> 00:01:57,920
Second, I thought volume would signal seriousness to the market.

43
00:01:57,920 --> 00:02:01,840
Third, I believed public proof would reduce the perceived risk of hiring me.

44
00:02:01,840 --> 00:02:05,320
Finally, I assumed the people consuming the content would either be decision makers or

45
00:02:05,320 --> 00:02:06,680
people who could influence them.

46
00:02:06,680 --> 00:02:10,560
Now, if you say all of that quickly, it sounds reasonable and this is exactly why so many

47
00:02:10,560 --> 00:02:12,400
people fall into the same trap.

48
00:02:12,400 --> 00:02:15,960
The system feels productive because you are shipping, you are visible, and you are building

49
00:02:15,960 --> 00:02:17,800
an archive of work in public.

50
00:02:17,800 --> 00:02:20,080
You feel a sense of momentum, but here is the thing.

51
00:02:20,080 --> 00:02:21,760
And conversion are not the same thing.

52
00:02:21,760 --> 00:02:26,400
At that stage, I had built a production system rather than a distribution system and that distinction

53
00:02:26,400 --> 00:02:27,680
changes everything.

54
00:02:27,680 --> 00:02:31,720
Because I was optimizing for output, I focused on daily episodes, topic coverage, and technical

55
00:02:31,720 --> 00:02:35,160
depth, but I was not really optimizing for reach or role relevance.

56
00:02:35,160 --> 00:02:39,080
I had a publishing engine, but I did not have a narrative engine and I definitely did not

57
00:02:39,080 --> 00:02:40,880
have a hiring conversion engine.

58
00:02:40,880 --> 00:02:43,880
That matters because employers do not hire content volume.

59
00:02:43,880 --> 00:02:47,360
They hire for reduced risk inside a specific business context.

60
00:02:47,360 --> 00:02:50,440
They hire when they can map what you do to what they actually need.

61
00:02:50,440 --> 00:02:53,520
And my early system assumed this mapping would happen automatically.

62
00:02:53,520 --> 00:02:57,200
I thought if I just produced enough proof, the market would do the translation for me, but

63
00:02:57,200 --> 00:02:58,360
it simply would not.

64
00:02:58,360 --> 00:02:59,520
And why is that important?

65
00:02:59,520 --> 00:03:01,800
Because this is where a lot of technical people get stuck.

66
00:03:01,800 --> 00:03:05,680
We think evidence speaks for itself and we believe if the work is good enough, the market

67
00:03:05,680 --> 00:03:06,760
will eventually notice.

68
00:03:06,760 --> 00:03:10,860
We think if we demonstrate enough expertise, opportunity will naturally follow, but business

69
00:03:10,860 --> 00:03:12,640
reality is harsher than that.

70
00:03:12,640 --> 00:03:15,840
Evidence without context is just noise to the wrong audience, effort without positioning

71
00:03:15,840 --> 00:03:16,840
is invisible.

72
00:03:16,840 --> 00:03:19,720
And consistency by itself is often just unrewarded labor.

73
00:03:19,720 --> 00:03:23,600
I remember how strong that belief was at the time and I genuinely thought I was building

74
00:03:23,600 --> 00:03:26,120
the shortest path to trust one episode at a time.

75
00:03:26,120 --> 00:03:29,720
To be fair, the system did produce something, including discipline and a public record of

76
00:03:29,720 --> 00:03:30,720
my thoughts.

77
00:03:30,720 --> 00:03:32,840
So the machine was not entirely useless.

78
00:03:32,840 --> 00:03:34,800
It was just pointed at the wrong outcome.

79
00:03:34,800 --> 00:03:38,520
The original design expected the podcast to function like a job magnet.

80
00:03:38,520 --> 00:03:42,240
But what it actually became was a thinking machine and a relationship surface.

81
00:03:42,240 --> 00:03:45,200
It was a way to sharpen my language through repetition.

82
00:03:45,200 --> 00:03:47,600
But none of that was the original goal.

83
00:03:47,600 --> 00:03:51,320
The goal was employment and that expected conversion never really came.

84
00:03:51,320 --> 00:03:55,040
So before we talk about what this process gave me, we need to be honest about where it failed

85
00:03:55,040 --> 00:03:56,040
first.

86
00:03:56,040 --> 00:03:58,720
Failure one, content as a job portfolio.

87
00:03:58,720 --> 00:04:01,080
So let's make the first failure very plain.

88
00:04:01,080 --> 00:04:04,240
The podcast as a job portfolio did not work the way I thought it would.

89
00:04:04,240 --> 00:04:08,400
I put in all the necessary inputs from daily episodes and technical depth to a public

90
00:04:08,400 --> 00:04:10,160
archive, but the results didn't follow.

91
00:04:10,160 --> 00:04:13,800
I had created proof that I could think in structure, show up consistently and explain

92
00:04:13,800 --> 00:04:17,800
complicated Microsoft topics in a way people could follow on paper that should have been

93
00:04:17,800 --> 00:04:23,000
useful and in a very narrow sense it was, but it did not create the outcome I built it for.

94
00:04:23,000 --> 00:04:24,880
It did not reliably generate interviews.

95
00:04:24,880 --> 00:04:29,120
It did not create a flow of job offers and it definitely did not remove the uncertainty

96
00:04:29,120 --> 00:04:31,200
that exists inside hiring decisions.

97
00:04:31,200 --> 00:04:33,920
That is the part I think many people don't want to say out loud.

98
00:04:33,920 --> 00:04:37,600
Because if you invest that much effort into public work, you want to believe the market

99
00:04:37,600 --> 00:04:39,240
will reward it directly.

100
00:04:39,240 --> 00:04:42,400
You want to believe effort compounds into opportunity and that if people can see the

101
00:04:42,400 --> 00:04:44,400
work, they will understand the value.

102
00:04:44,400 --> 00:04:46,280
But employers do not buy visible effort.

103
00:04:46,280 --> 00:04:50,120
Instead, they buy fit, timing, role alignment and reduced risk.

104
00:04:50,120 --> 00:04:51,240
And those are not the same thing.

105
00:04:51,240 --> 00:04:54,880
From a systems perspective, the problem was not that the podcast lacked quality.

106
00:04:54,880 --> 00:04:58,760
The problem was that the signal was too open, too broad and far too interpretive for

107
00:04:58,760 --> 00:05:00,040
a standard business process.

108
00:05:00,040 --> 00:05:05,680
A hiring manager does not sit there thinking that because this person has 200 or 500 episodes,

109
00:05:05,680 --> 00:05:10,200
they must be the right person for this exact business problem in this exact team at

110
00:05:10,200 --> 00:05:11,200
this exact moment.

111
00:05:11,200 --> 00:05:12,960
That is not how those systems work.

112
00:05:12,960 --> 00:05:16,080
Hiring systems are filters, not open-ended appreciation engines.

113
00:05:16,080 --> 00:05:18,280
They don't reward output in the abstract.

114
00:05:18,280 --> 00:05:19,520
They look for relevance.

115
00:05:19,520 --> 00:05:21,280
Can this person solve our problem?

116
00:05:21,280 --> 00:05:22,880
Can they operate in our environment?

117
00:05:22,880 --> 00:05:24,080
Can they speak our language?

118
00:05:24,080 --> 00:05:26,760
Can they reduce the cost of making the wrong hire?

119
00:05:26,760 --> 00:05:30,560
That last one matters more than most people think because hiring is rarely about finding the

120
00:05:30,560 --> 00:05:31,880
most interesting person.

121
00:05:31,880 --> 00:05:33,680
It is usually about reducing downside.

122
00:05:33,680 --> 00:05:38,280
So if your content proves that you are smart, disciplined and technically capable, that

123
00:05:38,280 --> 00:05:39,360
helps a little.

124
00:05:39,360 --> 00:05:43,480
But if it does not also make your business value easy to map, then the content stays informative

125
00:05:43,480 --> 00:05:45,080
without becoming decisive.

126
00:05:45,080 --> 00:05:46,360
And that is exactly what happened.

127
00:05:46,360 --> 00:05:50,960
The podcast created visibility, but visibility is not the same as decision confidence.

128
00:05:50,960 --> 00:05:53,720
People could see me and hear me and they could probably tell that I knew what I was talking

129
00:05:53,720 --> 00:05:55,760
about, but that still left a massive gap.

130
00:05:55,760 --> 00:05:58,160
What problem do I solve inside an organization?

131
00:05:58,160 --> 00:05:59,760
Where do I fit in a leadership structure?

132
00:05:59,760 --> 00:06:03,880
How do I influence delivery, adoption, governance, architecture or business outcomes?

133
00:06:03,880 --> 00:06:07,800
That translation layer was weak and if the translation layer is weak, the portfolio

134
00:06:07,800 --> 00:06:09,800
stays trapped at the level of activity.

135
00:06:09,800 --> 00:06:10,800
This is the trap.

136
00:06:10,800 --> 00:06:14,760
A lot of technical people assume that public proof automatically becomes professional leverage,

137
00:06:14,760 --> 00:06:15,960
but it doesn't.

138
00:06:15,960 --> 00:06:19,560
Public proof only works when the audience can attach it to a business narrative.

139
00:06:19,560 --> 00:06:22,920
Without that, your content may build respect, awareness or even admiration.

140
00:06:22,920 --> 00:06:24,560
But admiration does not sign contracts.

141
00:06:24,560 --> 00:06:29,200
It does not open headcount and it does not force a recruiter to move you to the next stage.

142
00:06:29,200 --> 00:06:30,920
And here's where it gets even more uncomfortable.

143
00:06:30,920 --> 00:06:35,240
A lot of the people who consume technical content are not hiring decision makers anyway.

144
00:06:35,240 --> 00:06:38,960
They are peers, learners and practitioners who are interested but are not in a position

145
00:06:38,960 --> 00:06:41,160
to convert that interest into employment.

146
00:06:41,160 --> 00:06:45,480
So the system was producing attention in places that did not naturally lead to the result

147
00:06:45,480 --> 00:06:46,480
I wanted.

148
00:06:46,480 --> 00:06:49,040
Again, the system was doing exactly what it was built to do.

149
00:06:49,040 --> 00:06:53,280
It created output, public proof and technical credibility, but it just was not built with a

150
00:06:53,280 --> 00:06:55,280
strong conversion path to employment.

151
00:06:55,280 --> 00:06:56,280
That is the difference.

152
00:06:56,280 --> 00:06:59,760
And once you see that, the emotional part becomes easier to understand too.

153
00:06:59,760 --> 00:07:03,400
Because then you stop asking why this didn't work, as if the market somehow ignored something

154
00:07:03,400 --> 00:07:08,200
obvious and you start asking the better question, what outcome was this system actually optimized

155
00:07:08,200 --> 00:07:09,200
for?

156
00:07:09,200 --> 00:07:12,320
The reason is I had confused proof of work with proof of fit and those are very different

157
00:07:12,320 --> 00:07:13,320
assets.

158
00:07:13,320 --> 00:07:17,520
Proof of work says, I can do things while proof of fit says, I can do the specific things

159
00:07:17,520 --> 00:07:22,280
that matter here in this role for this organization under these constraints.

160
00:07:22,280 --> 00:07:25,680
My podcast gave the first signal, but the market was buying the second.

161
00:07:25,680 --> 00:07:29,280
Once you understand that gap, the next false promise becomes obvious.

162
00:07:29,280 --> 00:07:31,240
Why visibility didn't convert?

163
00:07:31,240 --> 00:07:35,160
So let's go one level deeper because this is where the real misunderstanding sits.

164
00:07:35,160 --> 00:07:38,160
The podcast created visibility and that part is true.

165
00:07:38,160 --> 00:07:41,440
People could find me, they could listen and they could see that I had put in the work,

166
00:07:41,440 --> 00:07:45,480
but awareness is not the same thing as relevance and relevance is not the same thing as commercial

167
00:07:45,480 --> 00:07:46,480
confidence.

168
00:07:46,480 --> 00:07:49,160
That is the gap and most people never really audit that gap.

169
00:07:49,160 --> 00:07:53,080
They just keep publishing and hope the market will eventually reward the effort, but hope

170
00:07:53,080 --> 00:07:54,240
is not a strategy.

171
00:07:54,240 --> 00:07:58,120
From a system perspective, visibility failed to convert because the content answered the

172
00:07:58,120 --> 00:07:59,120
wrong question.

173
00:07:59,120 --> 00:08:01,220
It answered, do I know something?

174
00:08:01,220 --> 00:08:02,980
It did not answer clearly enough.

175
00:08:02,980 --> 00:08:05,840
What changes for a business if I am inside the room?

176
00:08:05,840 --> 00:08:09,240
That difference matters a lot because organizations are not buying information.

177
00:08:09,240 --> 00:08:12,340
They are buying risk reduction, speed, clarity and better decisions.

178
00:08:12,340 --> 00:08:16,580
And if your content proves technical depth without connecting that depth to business outcomes,

179
00:08:16,580 --> 00:08:19,280
then people may respect you, but they still won't know where to place you.

180
00:08:19,280 --> 00:08:23,140
You become interesting, not necessary and interesting is a weak commercial position.

181
00:08:23,140 --> 00:08:25,900
I think this is where many technical creators get trapped.

182
00:08:25,900 --> 00:08:28,500
We assume the market will do the final translation.

183
00:08:28,500 --> 00:08:32,860
We explain the feature, the update and the architecture and we think the audience will automatically

184
00:08:32,860 --> 00:08:38,460
infer the impact on adoption, governance, cost, execution or leadership.

185
00:08:38,460 --> 00:08:42,160
But most people don't do that extra work, especially not inside hiring systems or busy

186
00:08:42,160 --> 00:08:44,680
organizations when they are trying to fill a role quickly.

187
00:08:44,680 --> 00:08:46,280
They need narrative compression.

188
00:08:46,280 --> 00:08:48,380
They need to understand fast why you matter.

189
00:08:48,380 --> 00:08:50,820
And in my case, that compression was missing for too long.

190
00:08:50,820 --> 00:08:53,620
There was a lot of technical proof, but not enough business framing.

191
00:08:53,620 --> 00:08:57,100
There was a lot of knowledge, but not enough context around organizational value.

192
00:08:57,100 --> 00:08:59,620
There was a lot of explanation, but not enough positioning.

193
00:08:59,620 --> 00:09:03,900
So the content showed that I was active, it showed discipline and it showed endurance.

194
00:09:03,900 --> 00:09:08,340
But activity is not a role, effort is not a use case and endurance is not by itself a commercial

195
00:09:08,340 --> 00:09:09,340
argument.

196
00:09:09,340 --> 00:09:12,260
Now map that to how hiring systems actually work today.

197
00:09:12,260 --> 00:09:16,380
Most of them are built around filters like role titles, keywords, industry language, problem

198
00:09:16,380 --> 00:09:18,700
framing, budget ownership and decision scope.

199
00:09:18,700 --> 00:09:22,980
That means your public work has to be legible inside those filters, not just impressive outside

200
00:09:22,980 --> 00:09:23,980
them.

201
00:09:23,980 --> 00:09:27,740
And the manager is looking for someone who can improve decision flow, reduce governance chaos

202
00:09:27,740 --> 00:09:31,860
or connect Microsoft 365 architecture to measurable business outcomes.

203
00:09:31,860 --> 00:09:34,380
They need to hear that language from you directly.

204
00:09:34,380 --> 00:09:36,500
They shouldn't have to guess it from your consistency.

205
00:09:36,500 --> 00:09:37,500
And that was the issue.

206
00:09:37,500 --> 00:09:41,260
The podcast often lived at the level of technical credibility, but hiring and commercial

207
00:09:41,260 --> 00:09:43,740
systems often evaluate business utility.

208
00:09:43,740 --> 00:09:45,740
Those are connected, but they are not identical.

209
00:09:45,740 --> 00:09:47,900
And this is where another uncomfortable truth shows up.

210
00:09:47,900 --> 00:09:51,100
A content audience is not automatically a buyer audience.

211
00:09:51,100 --> 00:09:54,660
A listener may trust your thinking, a peer may appreciate your depth and a practitioner

212
00:09:54,660 --> 00:09:58,940
may learn from your episodes, but none of that guarantees access to a hiring budget,

213
00:09:58,940 --> 00:10:01,460
a project budget or a leadership conversation.

214
00:10:01,460 --> 00:10:04,860
The attention can be real and still have low conversion value.

215
00:10:04,860 --> 00:10:08,900
That's important because otherwise we romanticize audience growth as if every view carries

216
00:10:08,900 --> 00:10:09,900
the same weight.

217
00:10:09,900 --> 00:10:10,900
It doesn't.

218
00:10:10,900 --> 00:10:15,460
10,000 passive listeners are not the same as 10 operators who control strategy, spend or execution.

219
00:10:15,460 --> 00:10:16,940
This changes everything.

220
00:10:16,940 --> 00:10:21,020
Because once you stop measuring attention as one flat thing, you start seeing why visibility

221
00:10:21,020 --> 00:10:22,540
alone was insufficient.

222
00:10:22,540 --> 00:10:24,540
I did not have a distribution problem only.

223
00:10:24,540 --> 00:10:26,380
I had a contextual relevance problem.

224
00:10:26,380 --> 00:10:29,940
The people who found the work were often not the people who could act on the work in

225
00:10:29,940 --> 00:10:31,500
the way I originally wanted.

226
00:10:31,500 --> 00:10:34,820
And even when the right people were nearby, the content still needed stronger translation

227
00:10:34,820 --> 00:10:35,820
into business reality.

228
00:10:35,820 --> 00:10:38,180
So the failure was not that visibility had no value.

229
00:10:38,180 --> 00:10:39,180
It did.

230
00:10:39,180 --> 00:10:41,660
The failure was expecting visibility to do the work of positioning.

231
00:10:41,660 --> 00:10:42,660
It can't.

232
00:10:42,660 --> 00:10:46,220
Visibility gets you seen, but positioning tells people what to do with what they see.

233
00:10:46,220 --> 00:10:49,220
And if that second layer is weak, awareness just floats.

234
00:10:49,220 --> 00:10:54,140
It creates motion without direction, which brings me to the path I did not take.

235
00:10:54,140 --> 00:10:56,460
Failure 2, the certification trap.

236
00:10:56,460 --> 00:10:59,580
Now from there, the obvious next move would have been certifications.

237
00:10:59,580 --> 00:11:03,580
To be clear, I'm not against certifications because they can be useful for creating structure

238
00:11:03,580 --> 00:11:06,740
and helping people enter a field to build their confidence.

239
00:11:06,740 --> 00:11:10,420
This is not one of those lazy takes where I pretend credentials have no value, but in

240
00:11:10,420 --> 00:11:14,500
my situation doubling down on them would have looked rational on the surface while remaining

241
00:11:14,500 --> 00:11:16,000
fragile underneath.

242
00:11:16,000 --> 00:11:18,120
Because what problem would that actually have solved?

243
00:11:18,120 --> 00:11:22,080
If the podcast had already shown that I was serious, that I could learn and that I could

244
00:11:22,080 --> 00:11:26,280
explain technical topics in public, then another certificate would not have fixed the deeper

245
00:11:26,280 --> 00:11:27,280
issue.

246
00:11:27,280 --> 00:11:29,440
It would have added more evidence of knowledge.

247
00:11:29,440 --> 00:11:32,880
Yet the market was not rejecting me because it lacked proof that I could pass an exam.

248
00:11:32,880 --> 00:11:36,640
The market was failing to convert because the business relevance of my work was not framed

249
00:11:36,640 --> 00:11:40,200
clearly enough and different problems require different interventions.

250
00:11:40,200 --> 00:11:44,960
From a systems perspective, another certification would have increased inventory rather than leverage.

251
00:11:44,960 --> 00:11:48,840
Distinction matters because inventory is just more of the same asset, whereas leverage is

252
00:11:48,840 --> 00:11:52,340
the thing that changes the outcome of multiple assets at once.

253
00:11:52,340 --> 00:11:56,600
A certification can tell people you understand the platform, but it does not automatically tell

254
00:11:56,600 --> 00:12:02,280
them you can create movement inside an organization or show how you think through ambiguity.

255
00:12:02,280 --> 00:12:06,520
It does not prove that you can map tools to outcomes and it definitely does not guarantee

256
00:12:06,520 --> 00:12:08,360
better communication with decision makers.

257
00:12:08,360 --> 00:12:12,120
So yes, I could have stacked more credentials and many people would have advised exactly

258
00:12:12,120 --> 00:12:16,120
that to become more official and validated by the platform, but I had started to notice

259
00:12:16,120 --> 00:12:20,400
something uncomfortable about very credentialed people who still struggle to position their

260
00:12:20,400 --> 00:12:21,400
value.

261
00:12:21,400 --> 00:12:24,960
They knew the tools and the configuration paths, but when it came time to explain why any

262
00:12:24,960 --> 00:12:28,360
of it mattered for the business, the message got weak very quickly.

263
00:12:28,360 --> 00:12:32,000
And why is that because credentials prove memorized structure rather than translation or

264
00:12:32,000 --> 00:12:33,000
judgment?

265
00:12:33,000 --> 00:12:36,320
They do not prove that you can stand between technology and leadership to make the connection

266
00:12:36,320 --> 00:12:40,440
usable, which is a skill that business reality rewards far more than most technical people

267
00:12:40,440 --> 00:12:41,640
expect.

268
00:12:41,640 --> 00:12:45,360
I remember being close to that decision point and wondering if I should keep collecting external

269
00:12:45,360 --> 00:12:50,120
proof or improve the thing that kept getting exposed every time proof failed to convert.

270
00:12:50,120 --> 00:12:53,640
That was the real fork in the road because if I had chosen the certification path harder,

271
00:12:53,640 --> 00:12:58,120
I think I would have felt productive and busy, but it would have been structural compensation

272
00:12:58,120 --> 00:13:02,080
using a familiar technical mechanism to avoid a harder strategic truth.

273
00:13:02,080 --> 00:13:06,440
The truth was not that I lacked more information, but that I needed better articulation and message

274
00:13:06,440 --> 00:13:10,080
control to become easier to understand in terms of business value.

275
00:13:10,080 --> 00:13:14,120
As you see the gap clearly, the credential path starts to look like a local optimization

276
00:13:14,120 --> 00:13:18,680
that is useful in a narrow layer, but weak in the layer that actually determines outcomes.

277
00:13:18,680 --> 00:13:21,560
That's why I didn't double down on it, not because credentials are bad, but because

278
00:13:21,560 --> 00:13:24,940
they weren't the bottleneck or the constraint inside the system.

279
00:13:24,940 --> 00:13:29,000
If you optimize the wrong constraint, you can work very hard while staying structurally

280
00:13:29,000 --> 00:13:31,240
stuck, which is how a lot of careers work today.

281
00:13:31,240 --> 00:13:35,360
People add more proof to the wrong layer by chasing more courses and badges, yet none of

282
00:13:35,360 --> 00:13:37,400
it moves the actual conversion point.

283
00:13:37,400 --> 00:13:41,360
Because the issue isn't knowledge, it's market legibility, and whether people can quickly

284
00:13:41,360 --> 00:13:43,920
understand what changes when you are involved.

285
00:13:43,920 --> 00:13:45,200
That is the business test.

286
00:13:45,200 --> 00:13:49,480
And once I stopped pretending another certification would solve that, I had to choose a different

287
00:13:49,480 --> 00:13:51,520
kind of skill entirely.

288
00:13:51,520 --> 00:13:55,160
Rejecting one path only matters if you choose another.

289
00:13:55,160 --> 00:13:57,360
The skill shift that changed the system.

290
00:13:57,360 --> 00:14:01,920
So I made a different bet, not on another certification or more technical inventory, but

291
00:14:01,920 --> 00:14:02,920
on script writing.

292
00:14:02,920 --> 00:14:05,760
At first that probably sounds smaller than it is because when people hear writing, they

293
00:14:05,760 --> 00:14:08,200
often think about style or content polish.

294
00:14:08,200 --> 00:14:11,360
But that was not the shift and the real change was actually forced structure.

295
00:14:11,360 --> 00:14:15,360
When you write for spoken delivery, weak thinking gets exposed very fast.

296
00:14:15,360 --> 00:14:19,920
You can hide bad logic in slides or vague ideas in jargon, and you can certainly hide confusion

297
00:14:19,920 --> 00:14:21,720
in long documents that sound important.

298
00:14:21,720 --> 00:14:25,800
You cannot hide it very long in a spoken script because the moment a sentence becomes hard

299
00:14:25,800 --> 00:14:30,000
to say there is usually a deeper problem with the thought or the sequence.

300
00:14:30,000 --> 00:14:33,640
Writing scripts changed the system because it forced a different standard of thinking where

301
00:14:33,640 --> 00:14:37,680
I had to ask what the actual point was and why it mattered to the listener.

302
00:14:37,680 --> 00:14:41,560
That discipline is different from technical knowledge because it is architectural, meaning

303
00:14:41,560 --> 00:14:44,440
you are not just collecting facts but designing comprehension.

304
00:14:44,440 --> 00:14:45,960
That changed me more than I expected.

305
00:14:45,960 --> 00:14:50,100
And once you start doing that repeatedly, your thinking becomes more ordered, you stop

306
00:14:50,100 --> 00:14:54,160
dumping information and start building arguments, selecting only what moves the listener toward

307
00:14:54,160 --> 00:14:56,960
clarity, rather than explaining everything you know.

308
00:14:56,960 --> 00:15:01,240
That is a business skill and maybe one of the most underrated ones because value is often

309
00:15:01,240 --> 00:15:04,480
lost in translation long before it is lost in execution.

310
00:15:04,480 --> 00:15:08,740
A good idea explained badly will usually lose to a simple idea explained clearly not because

311
00:15:08,740 --> 00:15:12,160
it is weaker but because it is easier to act on.

312
00:15:12,160 --> 00:15:15,920
This writing shift improved three things at the same time, starting with my thinking as

313
00:15:15,920 --> 00:15:20,160
I had to sequence ideas with intent and stop confusing complexity with depth.

314
00:15:20,160 --> 00:15:24,120
Second it improved my communication because if a point could not survive spoken delivery,

315
00:15:24,120 --> 00:15:28,600
it was not ready, which meant less fluff and less hiding behind terms that sound smart

316
00:15:28,600 --> 00:15:30,520
but don't help anyone decide.

317
00:15:30,520 --> 00:15:35,160
Third it improved my positioning because once you learn to write clearly, you also learn

318
00:15:35,160 --> 00:15:36,640
to frame clearly.

319
00:15:36,640 --> 00:15:40,160
Framing is where technology starts becoming business reality and you stop saying here is

320
00:15:40,160 --> 00:15:43,760
the feature and start saying here is the organizational consequence.

321
00:15:43,760 --> 00:15:48,160
You stop describing tools in isolation and start mapping them to risk, speed, governance

322
00:15:48,160 --> 00:15:49,680
and decision quality.

323
00:15:49,680 --> 00:15:54,080
That shift is huge because now the value is not locked inside technical explanation and it

324
00:15:54,080 --> 00:15:57,240
becomes usable for leaders and people responsible for outcomes.

325
00:15:57,240 --> 00:16:01,320
This is where the system began to produce a different kind of return that was more durable

326
00:16:01,320 --> 00:16:03,360
than a direct job conversion.

327
00:16:03,360 --> 00:16:06,800
Script writing started acting like a force multiplier across everything else, making the

328
00:16:06,800 --> 00:16:10,400
podcast better because the arguments became tighter and the live streams better because

329
00:16:10,400 --> 00:16:12,440
the message had structure.

330
00:16:12,440 --> 00:16:16,960
Partnerships and events improved because communication is coordination and coordination is execution.

331
00:16:16,960 --> 00:16:21,320
Even strategy conversations changed because when you can translate complexity into a decision

332
00:16:21,320 --> 00:16:23,360
path, people experience you differently.

333
00:16:23,360 --> 00:16:27,040
You are no longer just the technical person who knows things but the person who helps make

334
00:16:27,040 --> 00:16:29,600
things legible which is a high value role in any business.

335
00:16:29,600 --> 00:16:35,400
I remember noticing that this skill was compounding in places where certifications never could.

336
00:16:35,400 --> 00:16:38,960
Not because writing replaced technical depths but because it gave that depth a delivery

337
00:16:38,960 --> 00:16:40,040
mechanism.

338
00:16:40,040 --> 00:16:43,800
Once that bridge exists, the whole asset stack changes and your knowledge becomes easier

339
00:16:43,800 --> 00:16:45,160
to trust and repeat.

340
00:16:45,160 --> 00:16:48,840
Your value becomes easier to position and this was the real pivot away from technical

341
00:16:48,840 --> 00:16:50,680
expression without business framing.

342
00:16:50,680 --> 00:16:54,760
That is what changed the system and this is where the consistency myth starts to break.

343
00:16:54,760 --> 00:16:55,760
Failure 3.

344
00:16:55,760 --> 00:16:57,000
The pure consistency model.

345
00:16:57,000 --> 00:17:00,840
This brings us to the third failure and it is probably the most uncomfortable one to discuss

346
00:17:00,840 --> 00:17:03,840
because it attacks a belief the internet repeats like a religion.

347
00:17:03,840 --> 00:17:07,560
You've heard the commandments before just stay consistent, keep showing up, publish every

348
00:17:07,560 --> 00:17:11,160
day and do the reps until the market finally responds.

349
00:17:11,160 --> 00:17:15,680
Now to be fair, consistency does matter because without it, most systems never survive long

350
00:17:15,680 --> 00:17:19,640
enough to teach you anything valuable about your audience or your product.

351
00:17:19,640 --> 00:17:21,160
But here is the problem.

352
00:17:21,160 --> 00:17:25,320
Consistency is not the same thing as leverage and confusing the two wasted a massive amount

353
00:17:25,320 --> 00:17:26,320
of my energy.

354
00:17:26,320 --> 00:17:30,880
A long time I believe that output would compound automatically and that authority would emerge

355
00:17:30,880 --> 00:17:33,400
as a natural side effect of simply staying in the game.

356
00:17:33,400 --> 00:17:37,360
I convinced myself that the archive itself would start pulling opportunities toward me

357
00:17:37,360 --> 00:17:41,000
and that sheer frequency would eventually turn into real market traction.

358
00:17:41,000 --> 00:17:43,960
Sometimes it actually looked like that was happening which is the most dangerous part

359
00:17:43,960 --> 00:17:44,960
of this entire mindset.

360
00:17:44,960 --> 00:17:48,720
There is a phase in these systems where the activity feels so productive that you stop

361
00:17:48,720 --> 00:17:52,200
questioning whether it is actually effective for your business.

362
00:17:52,200 --> 00:17:56,000
You have momentum, you have a solid routine and you have proof that you are disciplined

363
00:17:56,000 --> 00:17:57,960
enough to outwork the competition.

364
00:17:57,960 --> 00:18:01,880
Because most people struggle to stay consistent at all, you start to view your daily output

365
00:18:01,880 --> 00:18:03,720
as a primary competitive advantage.

366
00:18:03,720 --> 00:18:07,560
But an activity advantage is not always a market advantage and often it is just a very

367
00:18:07,560 --> 00:18:10,280
efficient way to stay busy without moving the needle.

368
00:18:10,280 --> 00:18:11,280
That was the trap I fell into.

369
00:18:11,280 --> 00:18:15,040
I had built a machine that was excellent at producing but I had not yet built a machine

370
00:18:15,040 --> 00:18:18,520
that could direct that production toward a specific business outcome.

371
00:18:18,520 --> 00:18:22,320
When that link is weak, consistency becomes a form of structural compensation where you

372
00:18:22,320 --> 00:18:25,640
keep moving because movement feels safer than actual strategy.

373
00:18:25,640 --> 00:18:29,320
You keep publishing because those numbers are measurable telling yourself that the next

374
00:18:29,320 --> 00:18:33,160
hundred pieces of content will unlock something the first few hundred did not.

375
00:18:33,160 --> 00:18:36,840
If the architecture underneath the work is weak, more output just scales that weakness

376
00:18:36,840 --> 00:18:38,440
across a larger surface area.

377
00:18:38,440 --> 00:18:42,560
That is the part people don't like to hear because consistency has a moral quality in our

378
00:18:42,560 --> 00:18:45,280
online culture that makes it feel beyond reproach.

379
00:18:45,280 --> 00:18:49,720
It sounds disciplined and admirable like the kind of honest hard work that should be rewarded

380
00:18:49,720 --> 00:18:50,720
by default.

381
00:18:50,720 --> 00:18:53,760
However markets do not reward effort just because it is admirable.

382
00:18:53,760 --> 00:18:57,960
They reward effort when it reduces friction, solves a specific problem and reaches the

383
00:18:57,960 --> 00:18:59,400
right people in the right frame.

384
00:18:59,400 --> 00:19:01,720
That is a completely different standard than just showing up.

385
00:19:01,720 --> 00:19:06,520
So while I became very consistent, that volume alone did not create any meaningful lift

386
00:19:06,520 --> 00:19:08,520
or automatically improve my distribution.

387
00:19:08,520 --> 00:19:12,640
It created a massive archive and while an archive has value for long tail discovery, it

388
00:19:12,640 --> 00:19:14,600
is not a substitute for leverage.

389
00:19:14,600 --> 00:19:18,480
Leverage is what changes the outcome per unit of effort and once I started looking at my

390
00:19:18,480 --> 00:19:21,920
work through that business lens, the consistency myth began to crack.

391
00:19:21,920 --> 00:19:25,800
I could finally see the mismatch between my high input and my low conversion rates.

392
00:19:25,800 --> 00:19:30,080
I had a strong routine but weak compounding which meant I was putting in a lot of effort

393
00:19:30,080 --> 00:19:33,800
without enough directional force to change my reality.

394
00:19:33,800 --> 00:19:37,440
Consistency fills the pipe but it does not decide where that pipe actually leads.

395
00:19:37,440 --> 00:19:41,320
It keeps the engine running without defining whether that engine is connected to demand,

396
00:19:41,320 --> 00:19:44,640
to decision makers or to an actual growth mechanism.

397
00:19:44,640 --> 00:19:48,680
This is exactly why so many digital initiatives disappoint the people funding them.

398
00:19:48,680 --> 00:19:53,160
The teams are active and the dashboards are moving but the system was optimized for motion

399
00:19:53,160 --> 00:19:54,640
rather than consequence.

400
00:19:54,640 --> 00:19:58,240
I had to admit to myself that daily publishing was not proof the model was working.

401
00:19:58,240 --> 00:20:00,440
It was only proof that I could sustain the model.

402
00:20:00,440 --> 00:20:04,520
One of those measures endurance while the other measures system design and in the business

403
00:20:04,520 --> 00:20:08,760
context endurance without design is just a slow path to burnout.

404
00:20:08,760 --> 00:20:12,240
Consistency is a lie when people present it as the only thing that creates outcomes because

405
00:20:12,240 --> 00:20:16,360
it still needs distribution, positioning and narrative fit to succeed.

406
00:20:16,360 --> 00:20:19,800
Not those layers you are just repeating effort inside an under optimized system that isn't

407
00:20:19,800 --> 00:20:21,040
built to scale.

408
00:20:21,040 --> 00:20:22,360
So the question eventually changed from here.

409
00:20:22,360 --> 00:20:26,280
I stopped asking if I could keep going and started asking what inside this whole machine

410
00:20:26,280 --> 00:20:29,160
was actually creating movement.

411
00:20:29,160 --> 00:20:30,440
Output versus leverage.

412
00:20:30,440 --> 00:20:32,000
So let's answer that directly.

413
00:20:32,000 --> 00:20:33,400
What actually creates movement?

414
00:20:33,400 --> 00:20:36,840
This is the point where a lot of people keep doing more of the same when what they really

415
00:20:36,840 --> 00:20:39,680
need is a completely different architecture for their work.

416
00:20:39,680 --> 00:20:43,480
There is a massive structural difference between producing content and building leverage

417
00:20:43,480 --> 00:20:46,000
even though they often look the same from the outside.

418
00:20:46,000 --> 00:20:50,320
Having content creates assets like episodes, posts and videos that live in an archive.

419
00:20:50,320 --> 00:20:54,920
That archive is certainly useful for sharpening your thinking and proving you are a serious professional

420
00:20:54,920 --> 00:20:57,440
but leverage is something else entirely.

421
00:20:57,440 --> 00:21:01,280
Leverage means that the same unit of effort starts producing more downstream effect whether

422
00:21:01,280 --> 00:21:04,880
that is more reach, more trust or higher density of opportunities.

423
00:21:04,880 --> 00:21:08,520
I treated output like it was automatically leveraged for a long time assuming the archive

424
00:21:08,520 --> 00:21:11,600
would eventually become a self-sustaining growth engine.

425
00:21:11,600 --> 00:21:15,520
But an archive is passive unless it is connected to a distribution infrastructure that carries

426
00:21:15,520 --> 00:21:18,320
value to the people who can actually act on it.

427
00:21:18,320 --> 00:21:21,880
Distribution is not just posting to a platform and hoping the algorithm is in a good mood.

428
00:21:21,880 --> 00:21:25,480
It is a mechanism built on own channels and audience habits.

429
00:21:25,480 --> 00:21:29,680
This mistake happens constantly inside large companies where teams optimize for output instead

430
00:21:29,680 --> 00:21:30,680
of outcomes.

431
00:21:30,680 --> 00:21:34,480
They build more dashboards, more apps and more documents and everyone feels productive because

432
00:21:34,480 --> 00:21:37,040
the volume of work is visible to the leadership.

433
00:21:37,040 --> 00:21:41,240
But if none of that changes decision speed or customer value, then the system is producing

434
00:21:41,240 --> 00:21:42,760
activity rather than leverage.

435
00:21:42,760 --> 00:21:45,040
It isn't a motivational problem for the employees.

436
00:21:45,040 --> 00:21:47,760
It is a design problem at the structural level.

437
00:21:47,760 --> 00:21:51,680
Output is simply easier to count than influence because it is local and you can control the schedule

438
00:21:51,680 --> 00:21:53,360
and the measurements immediately.

439
00:21:53,360 --> 00:21:56,840
Leverage is slower and more structural, often sitting one or two layers downstream from

440
00:21:56,840 --> 00:22:00,280
the initial action so people default to the thing that feels manageable.

441
00:22:00,280 --> 00:22:03,800
They produce more and talk more but if the packaging and audience mapping are weak,

442
00:22:03,800 --> 00:22:06,280
they are just filling a warehouse that nobody ever visits.

443
00:22:06,280 --> 00:22:09,880
When you work hard, you want that work to mean something on its own but the market is

444
00:22:09,880 --> 00:22:12,560
not grading you on your discipline or your effort.

445
00:22:12,560 --> 00:22:14,680
The market is responding to transfer.

446
00:22:14,680 --> 00:22:15,800
Can your value travel?

447
00:22:15,800 --> 00:22:17,320
Can it reach the right people?

448
00:22:17,320 --> 00:22:20,760
And can they understand it quickly enough to repeat it to someone else?

449
00:22:20,760 --> 00:22:22,320
That is what real leverage looks like.

450
00:22:22,320 --> 00:22:25,600
Once I saw that clearly, I stopped viewing an episode as the product and started seeing

451
00:22:25,600 --> 00:22:27,480
it as one node in a larger system.

452
00:22:27,480 --> 00:22:31,240
The content needs a relationship layer around it and a clear path into trust otherwise those

453
00:22:31,240 --> 00:22:33,800
assets stay isolated and fail to compound.

454
00:22:33,800 --> 00:22:37,880
This is why some people can publish less frequently and still create a much larger impact than

455
00:22:37,880 --> 00:22:39,960
those posting every single day.

456
00:22:39,960 --> 00:22:44,000
The system carries the value further through better packaging and stronger network effects

457
00:22:44,000 --> 00:22:47,160
meaning their output does not die the moment it is published.

458
00:22:47,160 --> 00:22:52,080
More activity does not mean more impact and in many cases high activity is just what people

459
00:22:52,080 --> 00:22:54,680
use when they haven't solved the leverage question yet.

460
00:22:54,680 --> 00:22:58,520
Once you understand that you stop admiring volume for its own sake and you start asking

461
00:22:58,520 --> 00:23:01,360
better questions about where your work actually travels.

462
00:23:01,360 --> 00:23:05,400
You begin to look for the doors it opens and the system behaviors it changes because

463
00:23:05,400 --> 00:23:08,400
that is the only lens that matters for long term growth.

464
00:23:08,400 --> 00:23:12,280
When I applied that lens honestly to my own work I finally realized that the real growth

465
00:23:12,280 --> 00:23:15,120
engine was not the podcast alone.

466
00:23:15,120 --> 00:23:19,560
What actually worked one, distribution leverage, the real growth engine behind everything

467
00:23:19,560 --> 00:23:21,880
wasn't the podcast alone, it was distribution.

468
00:23:21,880 --> 00:23:25,440
I need to say that very clearly because this is where the whole story changes and for a

469
00:23:25,440 --> 00:23:28,600
long time I mistakenly thought the hard part was just production.

470
00:23:28,600 --> 00:23:32,480
I kept asking myself if I could stay disciplined enough to keep publishing and if I could make

471
00:23:32,480 --> 00:23:35,160
enough things for the market to actually notice me.

472
00:23:35,160 --> 00:23:38,520
The production was only the visible part of the machine while the invisible part that

473
00:23:38,520 --> 00:23:41,120
actually changed my outcomes was audience access.

474
00:23:41,120 --> 00:23:46,040
That access came much more through the M365 show through live streams linked in and the

475
00:23:46,040 --> 00:23:48,840
newsletter than it ever did through the podcast by itself.

476
00:23:48,840 --> 00:23:53,040
This isn't a criticism of the podcast, it's a systems observation because the podcast

477
00:23:53,040 --> 00:23:57,280
helped build my capability while distribution helped create the consequence and the measurable

478
00:23:57,280 --> 00:23:58,800
signal here really matters.

479
00:23:58,800 --> 00:24:03,600
We are talking about more than 100,000 followers and around 30,000 newsletter subscribers.

480
00:24:03,600 --> 00:24:07,720
Now those numbers are not there to impress anyone, they matter because they represent reachable

481
00:24:07,720 --> 00:24:11,560
attention rather than abstract potential or algorithmic hope.

482
00:24:11,560 --> 00:24:15,640
Reachable attention means that when something matters there is a clear path for it to travel,

483
00:24:15,640 --> 00:24:19,200
whether that is a new idea, a new event, a collaboration or a new offer.

484
00:24:19,200 --> 00:24:23,240
That changes the economics of effort because once distribution exists one single piece of

485
00:24:23,240 --> 00:24:28,480
thinking can move across multiple surfaces like linked in the newsletter and partner conversations

486
00:24:28,480 --> 00:24:29,880
and why is that so important?

487
00:24:29,880 --> 00:24:34,960
That's because owned channels behave very differently from borrowed visibility which is inherently fragile

488
00:24:34,960 --> 00:24:35,960
and unreliable.

489
00:24:35,960 --> 00:24:40,080
You post something and maybe the platform shows it or maybe it doesn't but there is no real

490
00:24:40,080 --> 00:24:42,840
continuity or structural resilience in that model.

491
00:24:42,840 --> 00:24:47,480
Own reach is different because a newsletter subscriber is a repeat access path and a live stream

492
00:24:47,480 --> 00:24:50,720
audience is a recurring proximity layer that changes trust.

493
00:24:50,720 --> 00:24:54,400
This doesn't happen because people become emotionally attached in some vague creator economy

494
00:24:54,400 --> 00:24:58,960
way but because repeated exposure reduces the cost of interpretation.

495
00:24:58,960 --> 00:25:02,640
People start to understand how you think, they know what you focus on and they learn your

496
00:25:02,640 --> 00:25:06,440
language until they can place you accurately in their own mental model.

497
00:25:06,440 --> 00:25:07,440
That is a business asset.

498
00:25:07,440 --> 00:25:11,680
This is also why I say distribution beats production when outcomes matter because production

499
00:25:11,680 --> 00:25:16,080
fills the pipe but distribution decides whether value actually travels through it.

500
00:25:16,080 --> 00:25:20,040
Without distribution even the best work can stay structurally trapped but with it the same

501
00:25:20,040 --> 00:25:23,280
work starts building feedback loops that improve the whole system.

502
00:25:23,280 --> 00:25:27,920
You hear what resonates, you see where people lean in and you notice what creates real demand

503
00:25:27,920 --> 00:25:31,120
which makes your positioning clearer and your content sharper.

504
00:25:31,120 --> 00:25:34,720
This is not about becoming an influencer, a label I don't actually care about.

505
00:25:34,720 --> 00:25:39,080
It's about building audience infrastructure that can carry useful ideas into real business

506
00:25:39,080 --> 00:25:40,080
environments.

507
00:25:40,080 --> 00:25:43,760
Once I saw that clearly I stopped treating the podcast as the center of gravity and started

508
00:25:43,760 --> 00:25:48,400
seeing it as one part of a wider system where distribution did the compounding.

509
00:25:48,400 --> 00:25:53,520
That changed how I evaluated my progress so instead of asking if I published today I asked

510
00:25:53,520 --> 00:25:56,640
if I reached the right people and if I made the next move easier.

511
00:25:56,640 --> 00:25:57,840
That is the real test.

512
00:25:57,840 --> 00:26:01,320
A lot of professionals still underestimate what they are building because they think an

513
00:26:01,320 --> 00:26:03,360
audience is just a vanity metric.

514
00:26:03,360 --> 00:26:07,920
But when that audience is reachable and the channels are owned it becomes an asset.

515
00:26:07,920 --> 00:26:09,960
Why distribution beats consistency?

516
00:26:09,960 --> 00:26:12,000
So why does distribution beat consistency?

517
00:26:12,000 --> 00:26:16,440
It's because consistency is internal while distribution is relational meaning consistency

518
00:26:16,440 --> 00:26:20,080
says you can keep producing while distribution says the value can keep moving.

519
00:26:20,080 --> 00:26:21,160
That difference is everything.

520
00:26:21,160 --> 00:26:25,360
If you publish every day but the work never reaches the right people in the right context

521
00:26:25,360 --> 00:26:29,200
then all you have built is a private discipline ritual with public storage.

522
00:26:29,200 --> 00:26:32,600
Distribution changes that because it alters the feedback loop around the work so the content

523
00:26:32,600 --> 00:26:33,600
isn't just leaving you.

524
00:26:33,600 --> 00:26:36,080
It's returning signals about who is paying attention.

525
00:26:36,080 --> 00:26:40,200
You see who shares it, who replies and who starts mapping your thinking to a real business

526
00:26:40,200 --> 00:26:43,440
problem which is the part that actually matters for growth.

527
00:26:43,440 --> 00:26:46,200
Opportunities are rarely created by one piece of content in isolation.

528
00:26:46,200 --> 00:26:50,200
They are created by repeated contact across trusted channels like a weekly newsletter or

529
00:26:50,200 --> 00:26:51,440
a recurring livestream.

530
00:26:51,440 --> 00:26:53,000
This is not just audience growth.

531
00:26:53,000 --> 00:26:54,600
It is relationship design.

532
00:26:54,600 --> 00:26:58,040
In relationship design compounds differently than linear output.

533
00:26:58,040 --> 00:27:01,600
You don't just make one thing after another you create non-linear effects where one idea

534
00:27:01,600 --> 00:27:07,120
can travel further and create several downstream conversations from one original thought.

535
00:27:07,120 --> 00:27:10,400
That is a very different economic model and once you see it you notice how many people

536
00:27:10,400 --> 00:27:14,640
confuse the act of publishing with actual market penetration.

537
00:27:14,640 --> 00:27:18,400
Existence is not distribution and publication is not proximity because awareness without repeated

538
00:27:18,400 --> 00:27:20,440
access usually fades away very fast.

539
00:27:20,440 --> 00:27:25,120
That is why owned channels matter so much since a newsletter is permissioned attention that

540
00:27:25,120 --> 00:27:29,600
reduces your dependency on platform volatility and gives you a direct path into someone's

541
00:27:29,600 --> 00:27:30,800
working week.

542
00:27:30,800 --> 00:27:35,360
The same applies to live streams because they create a recurring presence and trust compounds

543
00:27:35,360 --> 00:27:39,520
through repeated exposure to coherent thinking rather than one off discovery.

544
00:27:39,520 --> 00:27:41,480
Now map that to business reality.

545
00:27:41,480 --> 00:27:45,600
If you are trying to create partnerships or market awareness consistency only helps if

546
00:27:45,600 --> 00:27:48,480
there is already a path for your value to circulate.

547
00:27:48,480 --> 00:27:53,160
If that path is weak, more consistency just feeds a weak channel which is why so many

548
00:27:53,160 --> 00:27:58,120
organizations misread their own digital initiatives and wonder why the effect stays thin.

549
00:27:58,120 --> 00:28:01,960
The reason is that the system is optimized to generate output not to carry outcomes through

550
00:28:01,960 --> 00:28:06,640
the organization leaving it with no distribution logic or reinforcement loop.

551
00:28:06,640 --> 00:28:10,960
From a system perspective that is fragile because borrowed reach can disappear overnight when

552
00:28:10,960 --> 00:28:13,680
algorithms change or platform incentives shift.

553
00:28:13,680 --> 00:28:17,320
Owned distribution is more resilient because it creates repeat pathways back to the people

554
00:28:17,320 --> 00:28:21,240
who already understand your frame and your way of working.

555
00:28:21,240 --> 00:28:24,480
This is also where community starts to matter in a structural sense because when people

556
00:28:24,480 --> 00:28:28,480
return repeatedly and interact across formats the system becomes connection first rather

557
00:28:28,480 --> 00:28:29,920
than content first.

558
00:28:29,920 --> 00:28:33,920
That changes the business value completely because you are no longer just broadcasting,

559
00:28:33,920 --> 00:28:39,000
you are hosting an environment that creates faster feedback and higher trust density.

560
00:28:39,000 --> 00:28:42,560
Environments create different outcomes than archives offering more chances for the right

561
00:28:42,560 --> 00:28:45,040
people to meet each other around the work you are doing.

562
00:28:45,040 --> 00:28:49,600
So yes, consistency helped me stay in motion but distribution created the compounding

563
00:28:49,600 --> 00:28:53,760
layer and a much more resilient path from thinking to opportunity.

564
00:28:53,760 --> 00:28:58,360
What actually worked to event execution and then the system got tested in the place where

565
00:28:58,360 --> 00:29:03,320
content alone cannot hide which was the world of live execution because content lets you

566
00:29:03,320 --> 00:29:07,600
describe reality but events force you to coordinate it and that creates a very different

567
00:29:07,600 --> 00:29:08,600
kind of pressure.

568
00:29:08,600 --> 00:29:13,080
When M365.net started becoming real something changed in how people perceived the work not

569
00:29:13,080 --> 00:29:16,920
because there was suddenly more opinion but because there was more orchestration.

570
00:29:16,920 --> 00:29:18,920
An orchestration is visible in a different way.

571
00:29:18,920 --> 00:29:22,680
You cannot fake an event with thousands of attendees and you certainly cannot bluff

572
00:29:22,680 --> 00:29:26,040
your way through speaker coordination scheduling and promotion at that scale.

573
00:29:26,040 --> 00:29:30,200
The market sees very quickly whether you can actually carry complexity and that is why

574
00:29:30,200 --> 00:29:32,360
this mattered so much for the business.

575
00:29:32,360 --> 00:29:38,160
At the event level the signal was clear with around 5,470 speakers joining the platform.

576
00:29:38,160 --> 00:29:42,000
Now again those numbers are not there for ego but they matter because they show something

577
00:29:42,000 --> 00:29:44,120
content by itself cannot show very well.

578
00:29:44,120 --> 00:29:48,040
They represent operational capacity, trust density and execution under pressure and event

579
00:29:48,040 --> 00:29:49,480
is a live systems test.

580
00:29:49,480 --> 00:29:53,480
It reveals whether your audience is passive or mobilizable and it shows whether your network

581
00:29:53,480 --> 00:29:55,920
is shallow or truly committed to the outcome.

582
00:29:55,920 --> 00:29:59,520
It reveals whether your communication is good enough to coordinate real people around

583
00:29:59,520 --> 00:30:04,160
a shared goal and that changes authority very fast because once you move from commenting

584
00:30:04,160 --> 00:30:08,160
on an ecosystem to organizing one people update their model of who you are.

585
00:30:08,160 --> 00:30:11,760
You are no longer just the person with ideas but the person who can make moving parts

586
00:30:11,760 --> 00:30:14,480
align and that is a different category of credibility.

587
00:30:14,480 --> 00:30:15,480
And why is that?

588
00:30:15,480 --> 00:30:17,080
Because execution reduces speculation.

589
00:30:17,080 --> 00:30:21,040
A lot of content lives in hypothetical territory where people talk about what should happen

590
00:30:21,040 --> 00:30:22,600
or what companies should do.

591
00:30:22,600 --> 00:30:26,480
That has value but theory always leaves room for doubt whereas execution closes that gap

592
00:30:26,480 --> 00:30:27,480
entirely.

593
00:30:27,480 --> 00:30:31,280
It says this did happen people showed up and the system carried real load.

594
00:30:31,280 --> 00:30:33,800
That is a much stronger signal than opinion alone.

595
00:30:33,800 --> 00:30:36,920
I noticed this shift very clearly as the project moved forward.

596
00:30:36,920 --> 00:30:40,520
Before the podcast proved I could think but the event proved I could coordinate.

597
00:30:40,520 --> 00:30:44,720
Before I could explain ecosystems but now I was helping build one and that difference matters

598
00:30:44,720 --> 00:30:48,520
in business reality because organizations trust people who can carry consequence.

599
00:30:48,520 --> 00:30:53,640
It is easy to underestimate how much authority changes when you move from publishing into orchestration.

600
00:30:53,640 --> 00:30:55,040
But here is what actually happens.

601
00:30:55,040 --> 00:30:57,680
The event forces better standards everywhere.

602
00:30:57,680 --> 00:31:01,320
Messaging has to get sharper because confusion scales and processes have to get clearer

603
00:31:01,320 --> 00:31:03,240
because handoffs multiply.

604
00:31:03,240 --> 00:31:07,360
Partnerships have to become more concrete because dependency becomes real which means time,

605
00:31:07,360 --> 00:31:09,240
sequence and responsibility matter more.

606
00:31:09,240 --> 00:31:11,720
In other words the whole system has to grow up.

607
00:31:11,720 --> 00:31:15,520
And that is why event execution became such a powerful part of the overall story.

608
00:31:15,520 --> 00:31:18,560
It created a new kind of proof that I could help create an environment where other people

609
00:31:18,560 --> 00:31:19,720
could succeed too.

610
00:31:19,720 --> 00:31:23,560
That is an executive signal because leaders are not measured by how much they personally

611
00:31:23,560 --> 00:31:29,160
know but by whether they can create conditions where coordinated outcomes become possible.

612
00:31:29,160 --> 00:31:33,520
That is what events train and once you have done that your voice changes a little and

613
00:31:33,520 --> 00:31:35,360
your judgement changes too.

614
00:31:35,360 --> 00:31:39,200
Because now you are not just asking if an idea is interesting but if it can actually hold

615
00:31:39,200 --> 00:31:41,680
when multiple people and expectations collide.

616
00:31:41,680 --> 00:31:43,080
That is a much better business question.

617
00:31:43,080 --> 00:31:47,040
This is also why I say execution creates authority faster than content.

618
00:31:47,040 --> 00:31:49,640
Content can open the door but execution changes the room.

619
00:31:49,640 --> 00:31:53,760
It creates evidence that you can operate not just analyse and in markets full of people

620
00:31:53,760 --> 00:31:57,960
explaining what should happen, the people who can carry complexity into a real outcome stand

621
00:31:57,960 --> 00:31:59,360
out very quickly.

622
00:31:59,360 --> 00:32:04,120
So for me M365.net was not just another project but a structural shift.

623
00:32:04,120 --> 00:32:09,440
It was a move from media as proof of knowledge toward execution as proof of capacity and once

624
00:32:09,440 --> 00:32:13,760
that happened the podcast itself started looking different, not smaller but more grounded

625
00:32:13,760 --> 00:32:18,120
because now the ideas were connected to something that had survived contact with reality.

626
00:32:18,120 --> 00:32:19,800
Why events rewire authority?

627
00:32:19,800 --> 00:32:21,920
So why do events rewire authority so fast?

628
00:32:21,920 --> 00:32:25,440
Because they expose something content can protect you from.

629
00:32:25,440 --> 00:32:26,680
Which is operational truth.

630
00:32:26,680 --> 00:32:29,760
When you publish an episode you control the frame and the pacing and you choose what

631
00:32:29,760 --> 00:32:31,760
gets included and what stays out.

632
00:32:31,760 --> 00:32:35,080
Even when you are being honest the format still protects you a little.

633
00:32:35,080 --> 00:32:36,080
An event does not.

634
00:32:36,080 --> 00:32:40,440
An event reveals whether trust is portable, can speakers trust you with their time and can

635
00:32:40,440 --> 00:32:42,520
attend these trust you with their attention.

636
00:32:42,520 --> 00:32:46,040
Can the whole thing hold together when many people depend on the same outcome at the same

637
00:32:46,040 --> 00:32:47,040
time?

638
00:32:47,040 --> 00:32:48,040
That is the real test.

639
00:32:48,040 --> 00:32:49,040
And why is that important?

640
00:32:49,040 --> 00:32:51,800
Because business authority is rarely built on ideas alone.

641
00:32:51,800 --> 00:32:53,640
It is built on carried consequence.

642
00:32:53,640 --> 00:32:58,080
People start trusting you differently when they see that you can move from concept to coordination

643
00:32:58,080 --> 00:33:00,880
and from theory to an environment that actually works.

644
00:33:00,880 --> 00:33:03,840
This is where events become very different from content output.

645
00:33:03,840 --> 00:33:07,320
They are not just communication assets but orchestration assets and orchestration is one

646
00:33:07,320 --> 00:33:10,200
of the clearest signals of executive capability.

647
00:33:10,200 --> 00:33:15,080
Think about what an event actually requires from speaker management and audience communication

648
00:33:15,080 --> 00:33:17,720
to scheduling logic and technical delivery.

649
00:33:17,720 --> 00:33:20,680
None of that is glamorous but all of it is visible in the outcome.

650
00:33:20,680 --> 00:33:23,880
If one part fails badly the whole thing feels unstable.

651
00:33:23,880 --> 00:33:28,280
So when an event works what people are really seeing is not a nice brand moment but coordinated

652
00:33:28,280 --> 00:33:32,040
reliability across many moving parts that changes perception quickly.

653
00:33:32,040 --> 00:33:34,960
Because from a system perspective events compress trust.

654
00:33:34,960 --> 00:33:38,720
Normally people would need multiple projects and many meetings to understand whether you

655
00:33:38,720 --> 00:33:40,200
can handle complexity.

656
00:33:40,200 --> 00:33:44,920
An event accelerates that judgment by giving the market a live demonstration of how you operate.

657
00:33:44,920 --> 00:33:47,440
That is why I say events rewire authority.

658
00:33:47,440 --> 00:33:50,480
They shift you from commentator to carrier and carriers are rare.

659
00:33:50,480 --> 00:33:53,760
A lot of people can explain a market but far fewer can convene one.

660
00:33:53,760 --> 00:33:57,480
Far fewer can create enough confidence that dozens of speakers say yes and the thing

661
00:33:57,480 --> 00:33:59,480
survives contact with reality.

662
00:33:59,480 --> 00:34:02,000
That is not a soft signal it is operational proof.

663
00:34:02,000 --> 00:34:04,640
And this creates a deeper business implication.

664
00:34:04,640 --> 00:34:07,880
Execution changes how people estimate your future capacity.

665
00:34:07,880 --> 00:34:11,880
Before an event someone might think you have interesting ideas but after an event they

666
00:34:11,880 --> 00:34:14,960
start thinking you can probably run more things than they assumed.

667
00:34:14,960 --> 00:34:19,840
That is a huge shift because markets often make decisions based on inferred capacity.

668
00:34:19,840 --> 00:34:24,080
Can this person handle complexity carry risk and align people in bigger rooms?

669
00:34:24,080 --> 00:34:26,440
Events answer those questions much faster than content usually can.

670
00:34:26,440 --> 00:34:30,080
This is also why execution often beats expertise in shaping perception.

671
00:34:30,080 --> 00:34:35,280
Not because expertise does not matter but because expertise without delivery stays theoretical.

672
00:34:35,280 --> 00:34:39,160
Execution proves that the expertise can survive constrained time pressure and reputation

673
00:34:39,160 --> 00:34:40,160
pressure.

674
00:34:40,160 --> 00:34:43,440
And once people see that they stop hearing your ideas as isolated opinions.

675
00:34:43,440 --> 00:34:48,040
They hear them as informed by operational contact and that is a different authority layer.

676
00:34:48,040 --> 00:34:50,000
Now map that to leadership more broadly.

677
00:34:50,000 --> 00:34:53,920
Inside companies the people who rise are rarely the ones with the most isolated knowledge.

678
00:34:53,920 --> 00:34:56,040
They are the ones who reduce coordination costs.

679
00:34:56,040 --> 00:34:59,800
They make hand-offs clearer, risk more manageable and complexity easier to carry.

680
00:34:59,800 --> 00:35:02,160
That is exactly what event execution trains.

681
00:35:02,160 --> 00:35:04,960
So the return from an event is never just attendance.

682
00:35:04,960 --> 00:35:08,880
Attendance is the visible metric but the deeper return is credibility under load.

683
00:35:08,880 --> 00:35:11,280
And once you have that your content changes too.

684
00:35:11,280 --> 00:35:14,640
Not because you become louder but because you become more believable.

685
00:35:14,640 --> 00:35:19,240
The ideas carry more weight because people have seen the system behind them operate in public.

686
00:35:19,240 --> 00:35:22,560
And the most important return still was not attendance.

687
00:35:22,560 --> 00:35:25,160
What actually worked three network density.

688
00:35:25,160 --> 00:35:29,120
And this is where the story becomes even more important for how we understand growth.

689
00:35:29,120 --> 00:35:32,560
Because if you look closely at the last few years the biggest return on this entire investment

690
00:35:32,560 --> 00:35:34,520
wasn't the download count or the views.

691
00:35:34,520 --> 00:35:38,000
It wasn't even the attendance at our live events but rather it was the direct access to

692
00:35:38,000 --> 00:35:39,240
a specific group of people.

693
00:35:39,240 --> 00:35:43,320
I'm talking about the builders who were testing things, failing in public and feeding those

694
00:35:43,320 --> 00:35:46,240
hard one lessons back into the wider ecosystem.

695
00:35:46,240 --> 00:35:49,800
That changed everything for me because network density is not just a soft benefit or a nice

696
00:35:49,800 --> 00:35:50,800
social extra.

697
00:35:50,800 --> 00:35:55,120
It functions as an acceleration layer that fundamentally changes how fast you can learn and

698
00:35:55,120 --> 00:35:56,800
how quickly you see around corners.

699
00:35:56,800 --> 00:36:01,360
For a long time I think I underestimated that reality because I saw audience as scale

700
00:36:01,360 --> 00:36:02,840
and content as proof.

701
00:36:02,840 --> 00:36:06,200
While those things are true the highest value assets sitting underneath the whole structure

702
00:36:06,200 --> 00:36:08,720
was proximity to operators and experts.

703
00:36:08,720 --> 00:36:12,960
These were the people actually carrying responsibility inside complex projects, communities

704
00:36:12,960 --> 00:36:14,120
and collaborations.

705
00:36:14,120 --> 00:36:15,800
And why is that so powerful for a business?

706
00:36:15,800 --> 00:36:19,920
Because while a passive audience size can make you visible network density is what makes

707
00:36:19,920 --> 00:36:20,920
you adaptive.

708
00:36:20,920 --> 00:36:24,000
If you know a lot of people loosely you might have reached but if you know the right people

709
00:36:24,000 --> 00:36:27,840
well enough to exchange trust and context you have a system that can move.

710
00:36:27,840 --> 00:36:31,960
I started to see this play out through our various collaborations, academy work and live

711
00:36:31,960 --> 00:36:32,960
streams.

712
00:36:32,960 --> 00:36:36,600
Conversations that began casually often turned into partnerships, invitations and entirely

713
00:36:36,600 --> 00:36:39,120
new formats that I couldn't have invented alone.

714
00:36:39,120 --> 00:36:43,320
None of that came from broadcasting into a void but instead it came from repeated interaction

715
00:36:43,320 --> 00:36:45,080
with people who were also building.

716
00:36:45,080 --> 00:36:48,680
Builders talk differently to each other because they skip the performance layer and get

717
00:36:48,680 --> 00:36:50,000
straight to the constraints.

718
00:36:50,000 --> 00:36:53,160
They want to know what is working, what is failing and where the actual bottlenecks

719
00:36:53,160 --> 00:36:54,160
are hiding.

720
00:36:54,160 --> 00:36:58,000
That kind of exchange is incredibly valuable not just because it feels good socially but

721
00:36:58,000 --> 00:37:01,720
because it shortens the distance between observation and correction.

722
00:37:01,720 --> 00:37:06,200
You make better decisions when you are close to real operators and you waste much less time

723
00:37:06,200 --> 00:37:08,800
on theories that sound good but break under pressure.

724
00:37:08,800 --> 00:37:12,800
In a market that changes as quickly as ours, getting a signal early is a major competitive

725
00:37:12,800 --> 00:37:13,800
advantage.

726
00:37:13,800 --> 00:37:17,920
This is also why I think many people overestimate their audience size while completely underestimating

727
00:37:17,920 --> 00:37:19,320
their trust density.

728
00:37:19,320 --> 00:37:23,880
A large passive audience can provide social proof and awareness but awareness is a weak asset

729
00:37:23,880 --> 00:37:26,880
if it isn't connected to people who will actually build with you.

730
00:37:26,880 --> 00:37:30,640
Network density wins because it creates optionality rather than just vanity.

731
00:37:30,640 --> 00:37:34,800
Once you are inside a trusted network, new paths appear faster and while they aren't guaranteed

732
00:37:34,800 --> 00:37:38,520
outcomes they are lower friction paths into collaboration and execution.

733
00:37:38,520 --> 00:37:43,120
This is a very different operating model from trying to force everything through solo output.

734
00:37:43,120 --> 00:37:48,280
From a systems perspective this creates structural resilience because if one project slows down

735
00:37:48,280 --> 00:37:50,120
the network still carries the motion.

736
00:37:50,120 --> 00:37:54,920
If one format loses energy, the relationships you've built will naturally create new channels

737
00:37:54,920 --> 00:37:55,920
for growth.

738
00:37:55,920 --> 00:37:59,760
If one part of the business becomes uncertain, trusted people can help create other paths

739
00:37:59,760 --> 00:38:02,800
forward which is the definition of redundancy.

740
00:38:02,800 --> 00:38:06,560
Redundancy matters when you are building in public and trying to turn ideas into real business

741
00:38:06,560 --> 00:38:07,560
infrastructure.

742
00:38:07,560 --> 00:38:11,280
When I look back at what actually worked, I cannot honestly say the biggest return was

743
00:38:11,280 --> 00:38:12,480
the content performance.

744
00:38:12,480 --> 00:38:16,320
The real return was that the work kept putting me in proximity to people I would not have

745
00:38:16,320 --> 00:38:17,640
reached otherwise.

746
00:38:17,640 --> 00:38:21,640
These were people who were further ahead in certain areas, people who opened doors and people

747
00:38:21,640 --> 00:38:23,960
who challenged my deepest assumptions.

748
00:38:23,960 --> 00:38:27,640
That is where the compounding really came from, not from the archive itself but from the

749
00:38:27,640 --> 00:38:29,720
human graph forming around it.

750
00:38:29,720 --> 00:38:33,000
Relationships aren't just a side effect of the work, they are the core infrastructure.

751
00:38:33,000 --> 00:38:37,320
If content builds awareness and events build authority, then network density is what builds

752
00:38:37,320 --> 00:38:38,360
true capability.

753
00:38:38,360 --> 00:38:43,720
It gives the whole system more intelligence and more paths forward than any solo archive

754
00:38:43,720 --> 00:38:44,880
ever could.

755
00:38:44,880 --> 00:38:46,400
The people inside the system.

756
00:38:46,400 --> 00:38:50,520
Now we get to the part that matters most, which is the part people in tech still tend to undermodel

757
00:38:50,520 --> 00:38:51,520
in their spreadsheets.

758
00:38:51,520 --> 00:38:54,160
And I am talking about the people inside the system.

759
00:38:54,160 --> 00:38:57,640
Once you understand network density, the next question is obvious.

760
00:38:57,640 --> 00:38:59,360
Who actually made the system stronger?

761
00:38:59,360 --> 00:39:03,560
Who increased the resilience of the project and prevented it from becoming another fragile

762
00:39:03,560 --> 00:39:04,560
solo endeavor.

763
00:39:04,560 --> 00:39:09,680
This is where the story stops being about content and starts becoming about human infrastructure.

764
00:39:09,680 --> 00:39:13,800
Human infrastructure matters because no serious system scales on output alone.

765
00:39:13,800 --> 00:39:15,400
It scales on trusted nodes.

766
00:39:15,400 --> 00:39:19,600
These are the people who bring capability, correction and momentum when one part of the

767
00:39:19,600 --> 00:39:21,120
structure starts to weaken.

768
00:39:21,120 --> 00:39:24,720
For me one of those people is Marcel Brosk and I say that very deliberately.

769
00:39:24,720 --> 00:39:28,240
When people look at a visible project, they usually only see the front layer like the

770
00:39:28,240 --> 00:39:30,040
episode or the announcement.

771
00:39:30,040 --> 00:39:34,320
They do not always see the builder energy behind the scenes that turns a scattered opportunity

772
00:39:34,320 --> 00:39:35,720
into actual movement.

773
00:39:35,720 --> 00:39:39,000
Marcel brought that energy and it wasn't just about effort or enthusiasm but the ability

774
00:39:39,000 --> 00:39:41,200
to connect governance and execution.

775
00:39:41,200 --> 00:39:43,400
Good collaborators do not just add output.

776
00:39:43,400 --> 00:39:45,640
They increase the total system capacity.

777
00:39:45,640 --> 00:39:49,360
They make larger moves possible than you could have ever carried on your own, which makes

778
00:39:49,360 --> 00:39:52,440
their contribution structural rather than just helpful.

779
00:39:52,440 --> 00:39:56,400
Then there is Marcel Lehmann who's role sits in a different but equally important place

780
00:39:56,400 --> 00:39:57,400
in the system.

781
00:39:57,400 --> 00:40:01,920
There are moments in any long cycle of work where your internal confidence is actually lower

782
00:40:01,920 --> 00:40:03,720
than your external activity suggests.

783
00:40:03,720 --> 00:40:08,240
You keep shipping and you keep building but internally the model still feels uncertain.

784
00:40:08,240 --> 00:40:11,600
In those moments, belief from the right person matters more than most professionals want

785
00:40:11,600 --> 00:40:12,600
to admit.

786
00:40:12,600 --> 00:40:16,920
It isn't about needing an emotional rescue but rather about how borrowed confidence can

787
00:40:16,920 --> 00:40:20,440
stabilize execution long enough for reality to catch up.

788
00:40:20,440 --> 00:40:24,120
That is a system outcome too and Marcel Lehmann brought that kind of energy at moments

789
00:40:24,120 --> 00:40:27,400
where myself trust wasn't operating at full strength.

790
00:40:27,400 --> 00:40:31,200
If you have ever built something for a long time without immediate validation, you know exactly

791
00:40:31,200 --> 00:40:32,640
how important that is.

792
00:40:32,640 --> 00:40:34,800
Sometimes people do not just support your work.

793
00:40:34,800 --> 00:40:38,600
They support your ability to continue interpreting your own work correctly.

794
00:40:38,600 --> 00:40:42,560
That prevents distortion and keeps you from making a premature retreat when things

795
00:40:42,560 --> 00:40:43,560
get difficult.

796
00:40:43,560 --> 00:40:47,800
Then there is the wider circle including people like 42 NATO and others who have been around

797
00:40:47,800 --> 00:40:48,800
the work over time.

798
00:40:48,800 --> 00:40:53,320
They aren't always in the centre or visible in a headline but they are present and responsive.

799
00:40:53,320 --> 00:40:57,200
Resilient human systems are not built from one heroic relationship but are instead built

800
00:40:57,200 --> 00:41:00,440
from redundancy and multiple trusted points of support.

801
00:41:00,440 --> 00:41:04,640
We use the same logic in architecture because if too much load sits on one node you create

802
00:41:04,640 --> 00:41:06,000
a single point of failure.

803
00:41:06,000 --> 00:41:09,880
Unfortunately a lot of careers are built exactly like that with too much identity in one

804
00:41:09,880 --> 00:41:12,920
employer or too much confidence in one income source.

805
00:41:12,920 --> 00:41:16,120
That is not strength, it is concentration risk.

806
00:41:16,120 --> 00:41:19,800
One of the biggest lessons in all of this is that trusted people are not a nice extra

807
00:41:19,800 --> 00:41:22,480
around the work but are actually part of the work itself.

808
00:41:22,480 --> 00:41:26,520
They are the infrastructure that allows the work to survive, adapt and eventually expand

809
00:41:26,520 --> 00:41:27,520
into new areas.

810
00:41:27,520 --> 00:41:32,000
Once you see that you stop talking about relationships like they are separate from business reality.

811
00:41:32,000 --> 00:41:36,560
They are business reality because resilient careers are carried by trusted nodes that absorb

812
00:41:36,560 --> 00:41:39,120
instability before it becomes a total collapse.

813
00:41:39,120 --> 00:41:42,480
That is what I was really building even before I had the right language to describe it.

814
00:41:42,480 --> 00:41:45,680
It wasn't just content or an audience but a more redundant human system.

815
00:41:45,680 --> 00:41:49,560
And once you understand that the entire podcast starts looking very different.

816
00:41:49,560 --> 00:41:52,080
The unexpected product of 500 episodes.

817
00:41:52,080 --> 00:41:56,320
Once you look at the data honestly the podcast starts changing shape in your mind.

818
00:41:56,320 --> 00:41:59,600
It isn't just about the archive or the list of guests anymore because the meaning of

819
00:41:59,600 --> 00:42:02,760
the work shifts when the original design fails to hit the mark.

820
00:42:02,760 --> 00:42:06,480
If the plan was simply to build a public portfolio and get hired then that specific part

821
00:42:06,480 --> 00:42:08,720
of the system didn't deliver the expected results.

822
00:42:08,720 --> 00:42:12,960
But the process kept producing something else entirely, something I didn't fully grasp when

823
00:42:12,960 --> 00:42:15,080
I hit record on episode one.

824
00:42:15,080 --> 00:42:19,080
The podcast never actually became a job machine but it evolved into a thinking machine and

825
00:42:19,080 --> 00:42:22,160
that has become a far more durable asset for my business.

826
00:42:22,160 --> 00:42:26,400
Long form audio does something specific to your brain when you show up week after week because

827
00:42:26,400 --> 00:42:31,080
it forces a level of endurance in your arguments that short form content just can't match.

828
00:42:31,080 --> 00:42:35,160
You have to hold a line of thought long enough for it to become useful to someone else.

829
00:42:35,160 --> 00:42:39,760
You have to map out where an idea starts, what evidence supports it, what logic weakens it,

830
00:42:39,760 --> 00:42:42,480
and exactly where that thought needs to land to make sense.

831
00:42:42,480 --> 00:42:46,480
This isn't just content creation or building a brand, it's high level judgment training

832
00:42:46,480 --> 00:42:48,000
that happens in real time.

833
00:42:48,000 --> 00:42:52,040
At the beginning of this journey I mostly saw episodes as individual outputs or things

834
00:42:52,040 --> 00:42:53,600
I had made to prove I was active.

835
00:42:53,600 --> 00:42:57,160
I wanted to show the world I was learning and that I had the discipline to show up.

836
00:42:57,160 --> 00:43:00,320
But over time the most important result wasn't what sat in the archive.

837
00:43:00,320 --> 00:43:04,640
The real value was what the process was doing to my own internal operating system because

838
00:43:04,640 --> 00:43:09,120
it sharpened my ability to sequence ideas and synthesize complex information.

839
00:43:09,120 --> 00:43:12,640
When you have to speak clearly across hundreds of episodes the system eventually punishes

840
00:43:12,640 --> 00:43:13,800
you for being confused.

841
00:43:13,800 --> 00:43:17,640
You start to hear your own weak points and notice exactly where your logic slips.

842
00:43:17,640 --> 00:43:21,440
Feeling that friction when an idea is technically correct but structurally incomplete.

843
00:43:21,440 --> 00:43:24,760
That feedback is brutal when you're listening back to your own voice but it's the only way

844
00:43:24,760 --> 00:43:27,000
to find where your thinking still leaks.

845
00:43:27,000 --> 00:43:30,480
The real product of 500 episodes wasn't a media library at all but rather the mental

846
00:43:30,480 --> 00:43:32,960
compression that only happens through disciplined repetition.

847
00:43:32,960 --> 00:43:37,080
I wasn't just repeating the same words I was practicing the discipline of taking complexity

848
00:43:37,080 --> 00:43:41,240
reducing the distortion and making the truth transferable to another person.

849
00:43:41,240 --> 00:43:45,680
This is where my identity started to shift from a technical explainer into something else.

850
00:43:45,680 --> 00:43:50,400
I started out focused on tools, updates and implementation details which are all still useful

851
00:43:50,400 --> 00:43:53,280
but I realized the real value wasn't in the feature layer.

852
00:43:53,280 --> 00:43:57,680
The value was sitting in the translation asking what a specific change actually does to

853
00:43:57,680 --> 00:44:00,920
a business or what new risks it creates for the organization.

854
00:44:00,920 --> 00:44:04,240
The podcast was no longer just training me to explain how technology works.

855
00:44:04,240 --> 00:44:07,080
It was training me to locate the consequence of that technology.

856
00:44:07,080 --> 00:44:10,720
Once you can do that consistently people stop seeing you as just another technical voice

857
00:44:10,720 --> 00:44:13,880
and start hearing you as someone who can connect the layers.

858
00:44:13,880 --> 00:44:17,920
You begin to bridge the gap between a tool and a workflow and then connect that workflow

859
00:44:17,920 --> 00:44:19,720
to a specific business outcome.

860
00:44:19,720 --> 00:44:23,560
From a systems perspective this is the most important return on the entire project.

861
00:44:23,560 --> 00:44:27,480
The archive and the audience certainly matter but the deepest asset is the person the

862
00:44:27,480 --> 00:44:32,120
process produced. I became someone with better endurance in thinking and sharper instincts

863
00:44:32,120 --> 00:44:36,920
for what matters in business reality versus what only sounds impressive in technical circles.

864
00:44:36,920 --> 00:44:41,560
Platforms, formats and algorithms will always shift but if a process turns you into a clearer

865
00:44:41,560 --> 00:44:44,960
thinker then the output was never the only product.

866
00:44:44,960 --> 00:44:48,560
You were the product too and I say that because some systems fail at their stated goal

867
00:44:48,560 --> 00:44:51,960
while building a much more durable capability underneath.

868
00:44:51,960 --> 00:44:55,480
The podcast didn't deliver the job I expected but it delivered a stronger operator which

869
00:44:55,480 --> 00:44:59,000
changes how you measure the success of the entire system.

870
00:44:59,000 --> 00:45:03,200
The shift from tech to business reality, this evolution in my own thinking meant the content

871
00:45:03,200 --> 00:45:07,520
itself had to change because keeping the old centre of gravity would have been a form

872
00:45:07,520 --> 00:45:09,400
of structural dishonesty.

873
00:45:09,400 --> 00:45:13,640
For years the focus stayed on features and whatever Microsoft happened to release in teams,

874
00:45:13,640 --> 00:45:15,400
SharePoint or the Power Platform.

875
00:45:15,400 --> 00:45:19,200
I tracked what worked and what broke and while technical detail always matters the feature

876
00:45:19,200 --> 00:45:20,880
is rarely the actual business problem.

877
00:45:20,880 --> 00:45:25,080
A new feature is usually just the visible surface of a much deeper design question about

878
00:45:25,080 --> 00:45:27,800
whether an organization can actually absorb the change.

879
00:45:27,800 --> 00:45:32,320
We have to ask if the workflow improves if decision quality goes up or if accountability

880
00:45:32,320 --> 00:45:34,760
becomes more blurred when we flip a switch.

881
00:45:34,760 --> 00:45:38,440
This realization shifted my attention away from what a tool can do in theory toward what

882
00:45:38,440 --> 00:45:41,080
an organization can actually carry in practice.

883
00:45:41,080 --> 00:45:45,360
The business reality of technology isn't defined by a shiny product page but by operating

884
00:45:45,360 --> 00:45:48,880
friction, adoption behaviour and management attention.

885
00:45:48,880 --> 00:45:52,640
These are the messy human variables that technical people often want to skip because

886
00:45:52,640 --> 00:45:54,640
they are harder to put into a diagram.

887
00:45:54,640 --> 00:45:59,200
However those are the exact factors that determine whether a new system creates value or just

888
00:45:59,200 --> 00:46:00,200
stalls out.

889
00:46:00,200 --> 00:46:04,280
The channel started moving away from feature gravity and toward consequence gravity to

890
00:46:04,280 --> 00:46:07,640
provide better translation for the people doing the work.

891
00:46:07,640 --> 00:46:11,160
Most companies aren't suffering from a lack of features, they are suffering from a lack

892
00:46:11,160 --> 00:46:14,000
of integration between their tools and their operating logic.

893
00:46:14,000 --> 00:46:17,600
They already own more capability than they can absorb and more licenses than they can

894
00:46:17,600 --> 00:46:19,040
explain to their board.

895
00:46:19,040 --> 00:46:22,720
Adding another layer of technical explanation without business framing just creates more

896
00:46:22,720 --> 00:46:25,960
informational load for leaders who are already overwhelmed.

897
00:46:25,960 --> 00:46:30,000
What these people actually need is consequence mapping to understand what happens to their

898
00:46:30,000 --> 00:46:32,280
risk profile if they automate a bad process.

899
00:46:32,280 --> 00:46:36,680
If you roll AI into an unclear workflow, the value will disappear and that is a business

900
00:46:36,680 --> 00:46:38,640
failure, not a technical one.

901
00:46:38,640 --> 00:46:43,360
Once I started taking those structural questions seriously the audience widened to include architects,

902
00:46:43,360 --> 00:46:44,720
consultants and founders.

903
00:46:44,720 --> 00:46:48,760
These are the people responsible for making sure an implementation survives its first contact

904
00:46:48,760 --> 00:46:50,360
with the actual organization.

905
00:46:50,360 --> 00:46:54,840
I wasn't abandoning the technical depth but I was repositioning it inside the layer where

906
00:46:54,840 --> 00:46:57,160
it actually creates a business consequence.

907
00:46:57,160 --> 00:47:00,800
Technical depth without context creates specialists who can only explain parts but technical

908
00:47:00,800 --> 00:47:04,680
depth inside a business context creates translation that people can actually use.

909
00:47:04,680 --> 00:47:09,600
My own language changed to focus less on roadmap theatre and more on operational reality, looking

910
00:47:09,600 --> 00:47:12,840
at how a tool rewires decision flow and governance.

911
00:47:12,840 --> 00:47:17,600
The market is currently full of technology messaging that confuses a possibility with actual

912
00:47:17,600 --> 00:47:18,600
readiness.

913
00:47:18,600 --> 00:47:22,320
Because a platform like co-pilot can summarize data doesn't mean the surrounding system is

914
00:47:22,320 --> 00:47:23,920
ready for that behavior to take place.

915
00:47:23,920 --> 00:47:27,240
Just because the power platform allows you to move fast doesn't mean your company can

916
00:47:27,240 --> 00:47:29,400
govern the speed you've just created.

917
00:47:29,400 --> 00:47:32,360
Business reality lives in absorbability, not just capability.

918
00:47:32,360 --> 00:47:35,560
Once you anchor your thinking there the channel becomes more valuable to people who aren't

919
00:47:35,560 --> 00:47:38,880
asking where to click but are asking what they are building and what it will cost if the

920
00:47:38,880 --> 00:47:40,200
design is wrong.

921
00:47:40,200 --> 00:47:44,240
We moved from tech as information to tech as operating leverage and that's when I noticed

922
00:47:44,240 --> 00:47:47,360
a pattern that shows up in almost every failing system.

923
00:47:47,360 --> 00:47:51,640
Please keep blaming their people for behaviors that the environment itself is producing.

924
00:47:51,640 --> 00:47:55,280
Executive angle one shadow is a design outcome and this is where it becomes relevant for

925
00:47:55,280 --> 00:47:59,560
anyone responsible for systems because the same pattern I saw in my own work shows up inside

926
00:47:59,560 --> 00:48:00,880
companies all the time.

927
00:48:00,880 --> 00:48:04,560
People blame users, they blame culture or they blame a lack of discipline and compliance

928
00:48:04,560 --> 00:48:09,240
but when you look closely a lot of what gets labeled as bad behavior is not random at

929
00:48:09,240 --> 00:48:10,240
all.

930
00:48:10,240 --> 00:48:11,240
It's a system outcome.

931
00:48:11,240 --> 00:48:13,600
Take shadow IT as a primary example.

932
00:48:13,600 --> 00:48:18,200
Most organizations talk about shadow IT like it's a moral failure where people are intentionally

933
00:48:18,200 --> 00:48:20,120
bypassing the official stack.

934
00:48:20,120 --> 00:48:24,440
This employee is using unsanctioned apps, exporting data and building little islands outside

935
00:48:24,440 --> 00:48:27,560
the governed environment and the standard reaction is to tighten control.

936
00:48:27,560 --> 00:48:30,320
The result is more policy and more lockdowns.

937
00:48:30,320 --> 00:48:33,840
Leadership adds more warnings in central reviews but here's the thing shadow IT usually doesn't

938
00:48:33,840 --> 00:48:37,280
appear because people woke up and decided governance was annoying.

939
00:48:37,280 --> 00:48:41,640
It appears because the official path became too slow, too unclear or too painful to carry

940
00:48:41,640 --> 00:48:43,800
the actual work and that distinction matters.

941
00:48:43,800 --> 00:48:47,760
If the sanctioned environment cannot absorb the speed and practical needs of the people inside

942
00:48:47,760 --> 00:48:50,200
it, they will root around it every single time.

943
00:48:50,200 --> 00:48:52,400
The reason is simple work has to continue.

944
00:48:52,400 --> 00:48:56,880
When the approved path becomes a bottleneck bypass behavior becomes the only rational choice

945
00:48:56,880 --> 00:48:58,400
for a productive employee.

946
00:48:58,400 --> 00:49:00,680
Now map that logic to Microsoft 365.

947
00:49:00,680 --> 00:49:04,360
If teams governance is too confusing, people spin up alternative channels and if sharepoint

948
00:49:04,360 --> 00:49:09,000
structures are too hard to understand, they dump files into whatever folder feels easiest.

949
00:49:09,000 --> 00:49:13,880
When power platform requests take weeks to process, someone builds a solution in the default environment

950
00:49:13,880 --> 00:49:17,160
or outside the tenant entirely just to get the job done.

951
00:49:17,160 --> 00:49:21,800
If the official process requires 10 approvals to solve a same day problem, then the unofficial

952
00:49:21,800 --> 00:49:24,120
process becomes the real operating model.

953
00:49:24,120 --> 00:49:26,680
That isn't just rebellion, it's structural compensation.

954
00:49:26,680 --> 00:49:30,280
The system is doing exactly what it was set up to do, but it just wasn't designed for

955
00:49:30,280 --> 00:49:33,160
what the organization actually needs at the edge.

956
00:49:33,160 --> 00:49:37,280
This is why I think the phrase shadow IT often hides the real diagnosis by making the problem

957
00:49:37,280 --> 00:49:38,960
sound like user disobedience.

958
00:49:38,960 --> 00:49:43,800
Structurally, it's usually a usability failure or a governance design failure because control

959
00:49:43,800 --> 00:49:47,200
without usability will always produce bypass behavior.

960
00:49:47,200 --> 00:49:50,440
Once you see that, you stop asking how to stop people from using the wrong tools and you

961
00:49:50,440 --> 00:49:51,880
start asking better questions.

962
00:49:51,880 --> 00:49:56,160
You look for where the friction is too high or where the decision path is too slow and

963
00:49:56,160 --> 00:50:00,160
you find where governance is creating delay without creating any real clarity.

964
00:50:00,160 --> 00:50:03,600
That's the business conversation most companies still avoid because it's easier to demand

965
00:50:03,600 --> 00:50:05,480
compliance than to redesign the environment.

966
00:50:05,480 --> 00:50:09,960
I've seen this pattern so many times where a platform gets rolled out and leadership expects

967
00:50:09,960 --> 00:50:13,280
adoption to follow, but the real working conditions never change.

968
00:50:13,280 --> 00:50:17,520
There is no simplification, no better information architecture, and no clear ownership of the

969
00:50:17,520 --> 00:50:18,520
new tools.

970
00:50:18,520 --> 00:50:22,960
Without usable pathways for common needs, people are forced to improvise and then that improvisation

971
00:50:22,960 --> 00:50:24,600
gets labeled as a security risk.

972
00:50:24,600 --> 00:50:28,600
And yes, it is a risk, but it's usually a downstream risk caused by an upstream problem.

973
00:50:28,600 --> 00:50:32,720
The system made unofficial behavior more functional than the official behavior, and from

974
00:50:32,720 --> 00:50:35,440
an executive perspective, that changes what you do next.

975
00:50:35,440 --> 00:50:40,440
If shadow ET is a design outcome, then the solution is structural redesign rather than just enforcement.

976
00:50:40,440 --> 00:50:44,080
You reduce bypass behavior by making the governed path more usable and more proportional

977
00:50:44,080 --> 00:50:45,680
to the actual speed of the work.

978
00:50:45,680 --> 00:50:49,160
That means fewer dead ends, clearer ownership, and faster workflows.

979
00:50:49,160 --> 00:50:53,200
You need better defaults and smarter templates to remove the ambiguity around where work

980
00:50:53,200 --> 00:50:55,280
should live and how decisions should move.

981
00:50:55,280 --> 00:50:58,960
This is also why technology projects fail when they get framed too narrowly.

982
00:50:58,960 --> 00:51:00,160
The tool is not the environment.

983
00:51:00,160 --> 00:51:04,320
The environment includes permissions, process design, and the emotional cost of asking for help.

984
00:51:04,320 --> 00:51:08,760
If those layers are weak, people don't experience the platform as a helpful operating system,

985
00:51:08,760 --> 00:51:10,360
but rather as constant friction.

986
00:51:10,360 --> 00:51:12,120
Friction always creates workarounds.

987
00:51:12,120 --> 00:51:14,640
So shadow ET is rarely the first failure in the chain.

988
00:51:14,640 --> 00:51:18,640
It's just the visible symptom of an official system that was too hard to use at the speed

989
00:51:18,640 --> 00:51:20,720
reality demanded.

990
00:51:20,720 --> 00:51:23,440
Executive angle too, flow of decision speeds tool count.

991
00:51:23,440 --> 00:51:27,000
And this is the next mistake companies make when they confuse having more tools with having

992
00:51:27,000 --> 00:51:28,320
more speed.

993
00:51:28,320 --> 00:51:31,560
Speed is not created by tool count, it is created by decision flow.

994
00:51:31,560 --> 00:51:34,800
It's the part a lot of digital transformation work still gets wrong today.

995
00:51:34,800 --> 00:51:38,920
A company adds another app or another automation layer, and leadership assumes progress is

996
00:51:38,920 --> 00:51:41,280
happening because the stack is getting richer.

997
00:51:41,280 --> 00:51:45,520
But if decisions still stall and handoffs remain unclear, then nothing fundamental has

998
00:51:45,520 --> 00:51:46,720
actually improved.

999
00:51:46,720 --> 00:51:49,960
The interface changed, but the delay did not.

1000
00:51:49,960 --> 00:51:54,280
Tools do not create operational speed, clarity, and role definition do.

1001
00:51:54,280 --> 00:51:57,920
Most organizational drag isn't caused by a lack of software, but by the ambiguity of who

1002
00:51:57,920 --> 00:52:00,000
decides and who owns the next step.

1003
00:52:00,000 --> 00:52:03,600
If you don't know what information is needed before a step can happen, the tool just becomes

1004
00:52:03,600 --> 00:52:04,960
a pretty awaiting room.

1005
00:52:04,960 --> 00:52:08,600
Now map that to power platform for a second, because people often talk about it like it's

1006
00:52:08,600 --> 00:52:09,600
magic speed.

1007
00:52:09,600 --> 00:52:13,360
They build a flow or an app and assume the problem is solved, but those things only help

1008
00:52:13,360 --> 00:52:16,360
if the underlying decision path is already coherent.

1009
00:52:16,360 --> 00:52:21,160
If the business logic is messy and responsibilities are vague, then all you really do is scale confusion

1010
00:52:21,160 --> 00:52:22,160
faster.

1011
00:52:22,160 --> 00:52:23,760
That isn't transformation, it's just structured chaos.

1012
00:52:23,760 --> 00:52:27,560
I've seen teams say they need automation when what they really need is a better map

1013
00:52:27,560 --> 00:52:30,040
of how work actually moves through the office.

1014
00:52:30,040 --> 00:52:34,040
They need to know who actually talks to whom and where requests actually pause for days

1015
00:52:34,040 --> 00:52:35,040
at a time.

1016
00:52:35,040 --> 00:52:38,280
You have to find which approvals are real and which ones are just legacy theatre.

1017
00:52:38,280 --> 00:52:42,760
You have to see where data gets re-typed because trust is low or where people ask for help

1018
00:52:42,760 --> 00:52:45,480
in teams because the official form is too slow.

1019
00:52:45,480 --> 00:52:49,240
That is the work that matters first, because once you make the flow of decisions visible,

1020
00:52:49,240 --> 00:52:51,160
then automation starts making sense.

1021
00:52:51,160 --> 00:52:56,000
Then power automate becomes an orchestration layer rather than a disguise for process confusion.

1022
00:52:56,000 --> 00:53:00,320
From a system perspective, a lot of companies are not under-tooled, they are under clarified.

1023
00:53:00,320 --> 00:53:03,680
They already have enough software to move faster, but they lack a clean decision architecture

1024
00:53:03,680 --> 00:53:04,680
to support it.

1025
00:53:04,680 --> 00:53:09,040
Without that architecture, every additional tool just creates another surface where confusion

1026
00:53:09,040 --> 00:53:12,560
can hide behind more notifications and more dashboards.

1027
00:53:12,560 --> 00:53:16,360
If you want speed, do not start by asking what tool is missing, but start by asking where

1028
00:53:16,360 --> 00:53:18,240
the decision path is breaking.

1029
00:53:18,240 --> 00:53:23,160
Find where ownership becomes fuzzy or where approval sit without a real decision standard.

1030
00:53:23,160 --> 00:53:25,360
Bad communication doesn't stay small.

1031
00:53:25,360 --> 00:53:29,680
It scales the same way a bad data model or weak governance scales.

1032
00:53:29,680 --> 00:53:33,400
Once confusion enters a repeated workflow, it multiplies every time that workflow runs

1033
00:53:33,400 --> 00:53:35,080
and that becomes incredibly expensive.

1034
00:53:35,080 --> 00:53:37,240
It costs your time, but it also costs your trust.

1035
00:53:37,240 --> 00:53:40,280
People start believing the system will help them, so they create manual workarounds just

1036
00:53:40,280 --> 00:53:41,760
to keep things moving.

1037
00:53:41,760 --> 00:53:46,120
Once that happens, your organisation is no longer running on the platform, but on compensations

1038
00:53:46,120 --> 00:53:47,320
around the platform.

1039
00:53:47,320 --> 00:53:49,080
That is a fragile way to do business.

1040
00:53:49,080 --> 00:53:50,880
Automation and integration matter.

1041
00:53:50,880 --> 00:53:53,480
But only after you have decision clarity.

1042
00:53:53,480 --> 00:53:57,600
It is not a licensing outcome, it's a systems property, and nowhere is that misunderstanding

1043
00:53:57,600 --> 00:54:00,880
louder right now than in the world of AI.

1044
00:54:00,880 --> 00:54:03,680
Executive angle 3 - the co-pilot value gap.

1045
00:54:03,680 --> 00:54:07,880
This brings us directly to AI and specifically to Microsoft co-pilot because this is where

1046
00:54:07,880 --> 00:54:12,000
the same fundamental misunderstanding gets wrapped in much better marketing.

1047
00:54:12,000 --> 00:54:16,040
Right now, a lot of companies are investing in AI as if the value sits entirely inside

1048
00:54:16,040 --> 00:54:19,800
the license itself, which is a bit like buying a high performance engine and expecting

1049
00:54:19,800 --> 00:54:22,520
it to win a race while it's still sitting in the crate.

1050
00:54:22,520 --> 00:54:26,600
They buy the seats, turn the service on, run a few basic training sessions to show people

1051
00:54:26,600 --> 00:54:30,800
where the buttons are, and then they collect some excited first impressions from the early

1052
00:54:30,800 --> 00:54:32,040
adopters.

1053
00:54:32,040 --> 00:54:35,720
After that, leadership expects productivity to spike simply because a digital assistant

1054
00:54:35,720 --> 00:54:37,280
is now present in the sidebar.

1055
00:54:37,280 --> 00:54:39,680
But here is what actually happens once the novelty wears off.

1056
00:54:39,680 --> 00:54:44,320
The workflows stay messy, ownership of tasks remains unclear, and information stays scattered

1057
00:54:44,320 --> 00:54:48,000
across a dozen different platforms that don't talk to each other.

1058
00:54:48,000 --> 00:54:52,440
When decision standards stay vague and the underlying process is broken, leaders are inevitably

1059
00:54:52,440 --> 00:54:55,800
surprised when the actual return on that investment feels thin.

1060
00:54:55,800 --> 00:54:59,840
That is the co-pilot value gap where the tool enters the organization, but the operating

1061
00:54:59,840 --> 00:55:04,920
model doesn't change to accommodate it because the AI is being added to a weak context.

1062
00:55:04,920 --> 00:55:08,200
That weak context produces weak business value every single time.

1063
00:55:08,200 --> 00:55:11,520
This matters because AI does not remove the need for structure.

1064
00:55:11,520 --> 00:55:13,400
In reality, it actually increases it.

1065
00:55:13,400 --> 00:55:17,600
The better your surrounding environment is, the more useful co-pilot becomes, but the

1066
00:55:17,600 --> 00:55:21,400
worse that environment is, the more expensive your disappointment will be.

1067
00:55:21,400 --> 00:55:25,280
If your documents are scattered, your permissions are a mess, and your meeting culture is chaotic,

1068
00:55:25,280 --> 00:55:26,520
AI will not fix the system.

1069
00:55:26,520 --> 00:55:30,480
It will simply interact with your existing confusion much faster than a human could.

1070
00:55:30,480 --> 00:55:34,600
That isn't a failure of the AI model itself, but rather a predictable system outcome.

1071
00:55:34,600 --> 00:55:35,600
And why is that?

1072
00:55:35,600 --> 00:55:39,280
Because co-pilot isn't some magic layer floating above your business reality.

1073
00:55:39,280 --> 00:55:40,720
It is grounded directly in it.

1074
00:55:40,720 --> 00:55:45,040
It works with the data, the permissions, the habits, and the process logic that already

1075
00:55:45,040 --> 00:55:47,120
exist inside your digital environment.

1076
00:55:47,120 --> 00:55:50,840
If that environment is fragmented, the outputs you get will reflect that fragmentation

1077
00:55:50,840 --> 00:55:55,960
and if your source material is noisy, the answers the AI gives you will carry that same noise.

1078
00:55:55,960 --> 00:56:00,040
When responsibility is vague, a generated next step might still land in a process that has

1079
00:56:00,040 --> 00:56:01,560
no structural way to handle it.

1080
00:56:01,560 --> 00:56:06,520
This is exactly why so many AI rollouts feel incredibly impressive during a control demo,

1081
00:56:06,520 --> 00:56:09,280
but end up feeling underwhelming in daily operations.

1082
00:56:09,280 --> 00:56:14,560
A demo isolates a single task to show you what's possible, but real work includes interruptions,

1083
00:56:14,560 --> 00:56:19,360
office politics, outdated files, and all the invisible friction that sits between having

1084
00:56:19,360 --> 00:56:21,680
information and taking action.

1085
00:56:21,680 --> 00:56:26,600
If none of those structural issues get redesigned, co-pilot just becomes another layer of assistance

1086
00:56:26,600 --> 00:56:28,200
inside a low clarity system.

1087
00:56:28,200 --> 00:56:31,360
It might be helpful in small moments, but it rarely becomes transformational.

1088
00:56:31,360 --> 00:56:33,920
Now let's map that reality to your ROI.

1089
00:56:33,920 --> 00:56:38,240
A lot of organizations are still asking the wrong question when they focus on what co-pilot

1090
00:56:38,240 --> 00:56:40,760
can do, which is really just a feature question.

1091
00:56:40,760 --> 00:56:45,160
The more important thing to ask is what kind of work environment lets co-pilot create durable

1092
00:56:45,160 --> 00:56:47,200
value, because that is an operating question.

1093
00:56:47,200 --> 00:56:51,800
The answer usually involves the very things companies tend to postpone, like better information

1094
00:56:51,800 --> 00:56:55,520
architecture, cleaner permissions, and more explicit accountability.

1095
00:56:55,520 --> 00:57:00,480
Without those foundations, AI adoption easily turns into a form of corporate theatre.

1096
00:57:00,480 --> 00:57:03,640
People use the tool and they might even like parts of it, while leaders mention it in

1097
00:57:03,640 --> 00:57:09,040
strategy decks to look forward thinking, but the core system underneath remains untouched.

1098
00:57:09,040 --> 00:57:13,240
Technology amplifies the quality of your context, but it never replaces the need for operating

1099
00:57:13,240 --> 00:57:14,240
clarity.

1100
00:57:14,240 --> 00:57:18,400
In text is strong, AI helps you scale judgement and coordination, but if it's weak, you're

1101
00:57:18,400 --> 00:57:21,200
just scaling motion without solving the problem.

1102
00:57:21,200 --> 00:57:25,560
When I look at co-pilot, I don't see a disappointing tool, I see a revealing one that shows whether

1103
00:57:25,560 --> 00:57:29,120
an organization has done the hard design work first.

1104
00:57:29,120 --> 00:57:31,560
The freelancer irony and the stealth project.

1105
00:57:31,560 --> 00:57:35,160
This is where the story gets a little uncomfortable in a way I actually appreciate.

1106
00:57:35,160 --> 00:57:36,920
Surviving as a freelancer is entirely possible.

1107
00:57:36,920 --> 00:57:40,840
I'm doing it right now, so I'm not suggesting the model is broken in a simple way.

1108
00:57:40,840 --> 00:57:45,480
To build real businesses, create personal freedom and develop massive leverage outside of traditional

1109
00:57:45,480 --> 00:57:46,560
employment every day.

1110
00:57:46,560 --> 00:57:50,080
But here's the thing, I've never fully identified with the freelancer label, not because

1111
00:57:50,080 --> 00:57:53,800
there's anything wrong with it, but because it doesn't accurately describe how I think

1112
00:57:53,800 --> 00:57:54,800
about work.

1113
00:57:54,800 --> 00:57:58,760
Freelancing is often framed as independent execution where a person sells their time or

1114
00:57:58,760 --> 00:58:02,400
a specific skill, but my instinct has always leaned closer to architecture.

1115
00:58:02,400 --> 00:58:06,320
I find myself constantly asking how things connect, where capability compounds, and what

1116
00:58:06,320 --> 00:58:10,280
moves an activity away from a one off task and into permanent infrastructure.

1117
00:58:10,280 --> 00:58:15,120
That difference is vital because a lot of freelance work operates inside a very fragile design.

1118
00:58:15,120 --> 00:58:18,880
When you have one person, one calendar, and one delivery engine, you have created a system

1119
00:58:18,880 --> 00:58:23,240
with a dangerous single point of failure, even if the money is great, and the freedom feels

1120
00:58:23,240 --> 00:58:27,120
real, putting that much load on one person creates a structure that doesn't scale.

1121
00:58:27,120 --> 00:58:30,760
Your identity gets wrapped up in being constantly available, which is a system's observation

1122
00:58:30,760 --> 00:58:32,560
rather than a personal criticism.

1123
00:58:32,560 --> 00:58:36,520
This is exactly why my current project is so interesting to me, even though I'm helping

1124
00:58:36,520 --> 00:58:38,840
build an AI platform for freelancers.

1125
00:58:38,840 --> 00:58:43,440
There is a real irony in building for a category where I don't naturally feel at home, but that

1126
00:58:43,440 --> 00:58:47,800
distance might be exactly why I can see the structural problem so clearly.

1127
00:58:47,800 --> 00:58:52,160
Sometimes being an outsider helps you notice the instability that insiders have just learned

1128
00:58:52,160 --> 00:58:53,320
to normalize.

1129
00:58:53,320 --> 00:58:57,520
You see the friction in proposals, the drag of administrative work, and the way too much

1130
00:58:57,520 --> 00:59:01,240
time is spent proving value instead of building reusable leverage.

1131
00:59:01,240 --> 00:59:05,520
When AI enters this conversation, it's usually framed as a way to write or research faster,

1132
00:59:05,520 --> 00:59:08,320
which is useful, but it doesn't change the underlying model.

1133
00:59:08,320 --> 00:59:12,720
If you add a stronger tool to a weak design, you're just using structural compensation to

1134
00:59:12,720 --> 00:59:15,160
help a fragile system run at a higher speed.

1135
00:59:15,160 --> 00:59:19,880
The real question isn't how freelancers can use AI to work more, but what kind of operating

1136
00:59:19,880 --> 00:59:24,440
model AI makes possible for professionals who want to escape permanent volatility?

1137
00:59:24,440 --> 00:59:28,600
The goal shouldn't be to turn an exhausted person into a slightly faster exhausted person.

1138
00:59:28,600 --> 00:59:31,880
We should be looking for ways to reduce the dependence on manual effort through better

1139
00:59:31,880 --> 00:59:34,920
context reuse and more resilient systems around delivery.

1140
00:59:34,920 --> 00:59:38,280
That is what makes this project worth the effort, especially as independent work face

1141
00:59:38,280 --> 00:59:42,440
is increasing pressure from platforms and rising client expectations.

1142
00:59:42,440 --> 00:59:46,280
If we are going to build a better model, it has to be more than just productivity theatre.

1143
00:59:46,280 --> 00:59:49,520
It has to redesign how capability is packaged and sustained over time.

1144
00:59:49,520 --> 00:59:53,440
I'm not going too deep into the specifics today because this is still a stealth project,

1145
00:59:53,440 --> 00:59:57,440
though more details will likely surface around the German M365 con.

1146
00:59:57,440 --> 00:59:58,440
Net event soon.

1147
00:59:58,440 --> 01:00:01,880
I wanted to mention it here because the irony matters, and sometimes the most useful work

1148
01:00:01,880 --> 01:00:04,440
happens at the edge of your own identity.

1149
01:00:04,440 --> 01:00:07,520
Distance gives you the perspective to see when a market is solving the wrong problem

1150
01:00:07,520 --> 01:00:11,520
and right now the design beneath the label is what needs our attention.

1151
01:00:11,520 --> 01:00:13,560
What 500 episodes actually proved?

1152
01:00:13,560 --> 01:00:16,640
So after all of that, what did 500 episodes actually prove?

1153
01:00:16,640 --> 01:00:21,160
To start with, they proved that my original plan was a total failure because the podcast

1154
01:00:21,160 --> 01:00:23,560
as a job hunting machine simply didn't work.

1155
01:00:23,560 --> 01:00:25,280
That is just the reality of the situation.

1156
01:00:25,280 --> 01:00:30,280
I found out the hard way that consistency by itself does not create interviews at the

1157
01:00:30,280 --> 01:00:35,000
rate I expected, nor does it create a clean conversion from public effort into professional

1158
01:00:35,000 --> 01:00:36,000
security.

1159
01:00:36,000 --> 01:00:39,320
I think it is important to say that out loud because so many people stay trapped in activity

1160
01:00:39,320 --> 01:00:41,720
long after the expected outcome has stopped appearing.

1161
01:00:41,720 --> 01:00:45,600
They keep feeding a system that is no longer proving itself and for a long time I was doing

1162
01:00:45,600 --> 01:00:49,560
the exact same thing, but here is the more important part of the story.

1163
01:00:49,560 --> 01:00:53,120
While the failure was real, it wasn't total because the podcast succeeded at producing

1164
01:00:53,120 --> 01:00:56,320
several outcomes I didn't even know how to value when I started.

1165
01:00:56,320 --> 01:01:00,160
It brought me into contact with incredible people and expanded my world far beyond the

1166
01:01:00,160 --> 01:01:02,560
narrow frame of technical explanations.

1167
01:01:02,560 --> 01:01:06,040
My thinking sharpened until I could translate technology into business consequences much

1168
01:01:06,040 --> 01:01:08,840
more clearly and that alone made the effort worth it.

1169
01:01:08,840 --> 01:01:13,120
The show created entry points into live streams, newsletters and collaborations that became

1170
01:01:13,120 --> 01:01:16,920
far more valuable than the audio archive could ever be on its own.

1171
01:01:16,920 --> 01:01:21,120
The right conclusion here isn't that consistency is useless but rather that consistency is insufficient

1172
01:01:21,120 --> 01:01:22,960
for the goals most of us have.

1173
01:01:22,960 --> 01:01:26,680
Consistency fills the pipe and creates repetition which builds the endurance you need to survive

1174
01:01:26,680 --> 01:01:28,320
the early days of any project.

1175
01:01:28,320 --> 01:01:32,160
It gives you enough surface area for feedback and serendipity to happen.

1176
01:01:32,160 --> 01:01:36,960
But if you build that repetition without distribution the value never travels far enough to matter.

1177
01:01:36,960 --> 01:01:41,680
If you build it without positioning people won't know what box to put you in and without execution

1178
01:01:41,680 --> 01:01:44,440
the market has no proof that you can actually carry weight.

1179
01:01:44,440 --> 01:01:48,280
What 500 episodes really showed me is that the winning stack was never just about showing

1180
01:01:48,280 --> 01:01:49,440
up every day.

1181
01:01:49,440 --> 01:01:54,760
It was consistency plus distribution, consistency plus positioning and consistency plus real world

1182
01:01:54,760 --> 01:01:56,320
execution and relationships.

1183
01:01:56,320 --> 01:02:00,720
That is the fundamental difference between just producing output and building actual infrastructure.

1184
01:02:00,720 --> 01:02:04,680
Once you see that distinction a lot of modern business activity starts looking like output

1185
01:02:04,680 --> 01:02:09,640
theatre where teams produce dashboards and AI demos that offer plenty of motion but very

1186
01:02:09,640 --> 01:02:10,880
little leverage.

1187
01:02:10,880 --> 01:02:14,600
The reason this milestone matters to me is that it gave me a way to see my own work with

1188
01:02:14,600 --> 01:02:15,880
much more honesty.

1189
01:02:15,880 --> 01:02:20,000
The podcast failed to get me a job but it worked as a tool to meet great people and grow

1190
01:02:20,000 --> 01:02:22,040
beyond the feature layer of technologies.

1191
01:02:22,040 --> 01:02:26,160
It worked as a way to become a better thinker and helped me create a more resilient business

1192
01:02:26,160 --> 01:02:28,200
infrastructure which is the biggest shift of all.

1193
01:02:28,200 --> 01:02:31,840
If you had asked me early on what I was building I probably would have said a portfolio but

1194
01:02:31,840 --> 01:02:35,920
now I realize I was building a platform for thought and trust to accumulate across different

1195
01:02:35,920 --> 01:02:36,920
formats.

1196
01:02:36,920 --> 01:02:42,040
That is a much stronger asset because it is structurally less fragile than a simple collection

1197
01:02:42,040 --> 01:02:43,040
of past work.

1198
01:02:43,040 --> 01:02:46,840
A portfolio depends entirely on someone else evaluating your past whereas infrastructure

1199
01:02:46,840 --> 01:02:49,240
keeps creating new options for your future.

1200
01:02:49,240 --> 01:02:53,760
This is why I am less interested now in talking about the grind or heroic consistency because

1201
01:02:53,760 --> 01:02:58,600
those stories are too shallow and make it sound like effort is the only hidden key.

1202
01:02:58,600 --> 01:03:02,200
Effort and discipline matter but if that effort is pointed into a weak structure all you

1203
01:03:02,200 --> 01:03:05,240
get is a very well maintained version of disappointment.

1204
01:03:05,240 --> 01:03:09,480
Once you stop romanticizing the idea of just showing up you can finally start asking better

1205
01:03:09,480 --> 01:03:12,640
design questions about your career and your systems.

1206
01:03:12,640 --> 01:03:16,280
You start asking where the distribution is, how you are positioned and where the execution

1207
01:03:16,280 --> 01:03:17,880
proof lives within your workflow.

1208
01:03:17,880 --> 01:03:21,760
You look for the people inside the system who make it more resilient than your own individual

1209
01:03:21,760 --> 01:03:23,120
output could ever be.

1210
01:03:23,120 --> 01:03:26,600
Those are the questions that actually change outcomes and they are far more useful than

1211
01:03:26,600 --> 01:03:28,920
just counting how many days in a row you've worked.

1212
01:03:28,920 --> 01:03:33,880
So no, 500 episodes did not prove that consistency wins but they proved something much better.

1213
01:03:33,880 --> 01:03:37,640
They proved that repeated action becomes valuable only when it is embedded in the right

1214
01:03:37,640 --> 01:03:38,640
structure.

1215
01:03:38,640 --> 01:03:42,440
This means you don't necessarily need to do less work but you do need to stop asking

1216
01:03:42,440 --> 01:03:43,440
the work to do jobs.

1217
01:03:43,440 --> 01:03:47,120
It was never structurally set up to do in the first place.

1218
01:03:47,120 --> 01:03:50,680
If I leave you with one thing today it is this.

1219
01:03:50,680 --> 01:03:54,720
consistency is overrated when it becomes a substitute for distribution, positioning and trusted

1220
01:03:54,720 --> 01:03:55,960
relationships.

1221
01:03:55,960 --> 01:04:00,160
If this episode helped you audit your own work more honestly I'd love for you to leave

1222
01:04:00,160 --> 01:04:04,400
a review, connect with me on LinkedIn and tell me what topic we should break down next.

1223
01:04:04,400 --> 01:04:07,000
If you are building something right now please start.

1224
01:04:07,000 --> 01:04:08,400
But start with the right question.

1225
01:04:08,400 --> 01:04:12,200
Don't just ask what outcome you want, ask what kind of person and what kind of system

1226
01:04:12,200 --> 01:04:13,640
this process is actually producing.