1
00:00:00,000 --> 00:00:01,120
Welcome to the Deep Dive.

2
00:00:01,120 --> 00:00:03,400
This is where we cut through the noise,

3
00:00:03,400 --> 00:00:05,160
unpack interesting topics,

4
00:00:05,160 --> 00:00:07,120
and try to get you the core insights.

5
00:00:07,120 --> 00:00:08,560
And we've all been there, right?

6
00:00:08,560 --> 00:00:10,720
Drowning in chat messages, endless scrolling

7
00:00:10,720 --> 00:00:11,820
to find that one decision.

8
00:00:11,820 --> 00:00:12,660
Oh yeah.

9
00:00:12,660 --> 00:00:15,120
Or just feeling completely swamped by notifications,

10
00:00:15,120 --> 00:00:16,640
just a blur.

11
00:00:16,640 --> 00:00:19,020
Today, we're diving into a tool that, well,

12
00:00:19,020 --> 00:00:21,140
promises to change that, Zulip.

13
00:00:21,140 --> 00:00:23,420
It's an open source team chat app.

14
00:00:23,420 --> 00:00:26,560
And our mission here is to figure out what makes it tick,

15
00:00:26,560 --> 00:00:28,680
what's unique about it, explore the benefits,

16
00:00:28,680 --> 00:00:30,960
and really give you a clear entry point,

17
00:00:30,960 --> 00:00:32,920
especially if you're maybe new to these kinds

18
00:00:32,920 --> 00:00:34,360
of communication tools.

19
00:00:34,360 --> 00:00:36,400
But before we unpack all that, just a quick word

20
00:00:36,400 --> 00:00:38,520
from our supporter, Safe Server.

21
00:00:38,520 --> 00:00:40,200
Safe Server helps with hosting software

22
00:00:40,200 --> 00:00:41,840
and digital transformation,

23
00:00:41,840 --> 00:00:45,040
basically making your digital life easier, more secure.

24
00:00:45,040 --> 00:00:49,320
You can find out more over at www.safeserver.de.

25
00:00:49,320 --> 00:00:50,440
Okay, so let's jump in.

26
00:00:50,440 --> 00:00:52,560
Team communication tools, they're absolutely everywhere.

27
00:00:52,560 --> 00:00:53,760
It feels like a new one every week.

28
00:00:53,760 --> 00:00:54,600
It does, yeah.

29
00:00:54,600 --> 00:00:57,740
All promising more collaboration, more productivity.

30
00:00:57,740 --> 00:01:01,220
But Zulip keeps popping up, it's got some buzz.

31
00:01:01,220 --> 00:01:03,440
So what is Zulip really at its heart?

32
00:01:03,440 --> 00:01:04,880
What's its secret sauce?

33
00:01:04,880 --> 00:01:06,640
How does it stand out?

34
00:01:06,640 --> 00:01:09,460
Well, fundamentally, Zulip is an open source

35
00:01:09,460 --> 00:01:11,240
team collaboration platform.

36
00:01:11,240 --> 00:01:12,560
So think of it as a whole system.

37
00:01:12,560 --> 00:01:14,840
It's got the server part, which you can control,

38
00:01:14,840 --> 00:01:18,200
and then the web and desktop apps for your team to use.

39
00:01:18,200 --> 00:01:20,800
And its main goal is really focused.

40
00:01:20,800 --> 00:01:23,320
Helping teams stay productive, stay focused,

41
00:01:23,320 --> 00:01:26,120
whether they're talking live or asynchronously.

42
00:01:26,120 --> 00:01:28,000
And that secret sauce you mentioned,

43
00:01:28,000 --> 00:01:29,720
that really comes down to how it organizes

44
00:01:29,720 --> 00:01:30,760
all that communication.

45
00:01:30,760 --> 00:01:32,360
OK, productive and focused.

46
00:01:32,360 --> 00:01:34,920
That sounds like the dream for any team.

47
00:01:34,920 --> 00:01:37,160
But honestly, lots of tools say that.

48
00:01:37,160 --> 00:01:39,360
So what's the real differentiator here?

49
00:01:39,360 --> 00:01:42,560
What's the core innovation Zulip has for TeamChat?

50
00:01:42,560 --> 00:01:45,280
Right, the big thing, the defining innovation,

51
00:01:45,280 --> 00:01:48,240
is what they call topic-based threading.

52
00:01:48,240 --> 00:01:50,920
Like, taking the best bits of email,

53
00:01:50,920 --> 00:01:53,160
the organized, focused discussion part,

54
00:01:53,160 --> 00:01:54,680
and combining that with the speed

55
00:01:54,680 --> 00:01:56,880
and the sort of casual feel of chat.

56
00:01:56,880 --> 00:01:58,200
That's kind of Zulip.

57
00:01:58,200 --> 00:02:00,520
It's built specifically for both live chat

58
00:02:00,520 --> 00:02:03,040
and that deeper asynchronous stuff.

59
00:02:03,040 --> 00:02:05,200
That's absolutely key to the productivity side.

60
00:02:05,200 --> 00:02:08,440
Huh, topic-based threading, that's interesting.

61
00:02:08,440 --> 00:02:11,960
So for someone who's only used Slack or Teams,

62
00:02:11,960 --> 00:02:13,720
where it's just one message after another.

63
00:02:13,720 --> 00:02:14,920
Right, linear chat.

64
00:02:14,920 --> 00:02:16,040
Yeah, linear.

65
00:02:16,040 --> 00:02:18,280
How does this topic thing actually work?

66
00:02:18,280 --> 00:02:20,800
Can you give us an analogy, maybe, make it clear?

67
00:02:20,800 --> 00:02:22,600
Does it slow down quick chats,

68
00:02:22,600 --> 00:02:24,200
or does it really help you stay focused

69
00:02:24,200 --> 00:02:25,760
without getting buried?

70
00:02:25,760 --> 00:02:26,920
That's a really good question,

71
00:02:26,920 --> 00:02:28,280
because it gets to the heart of it.

72
00:02:28,280 --> 00:02:29,560
Think of a normal chat app,

73
00:02:29,560 --> 00:02:33,600
like one really long, fast river.

74
00:02:33,600 --> 00:02:36,020
Everything just flows by in that single stream.

75
00:02:36,020 --> 00:02:36,960
Step away for a bit.

76
00:02:36,960 --> 00:02:38,080
You've missed loads.

77
00:02:38,080 --> 00:02:40,400
Exactly, you miss stuff, you struggle to find context,

78
00:02:40,400 --> 00:02:42,840
you get pulled into chats that aren't even relevant to you.

79
00:02:42,840 --> 00:02:43,920
It can be chaos.

80
00:02:43,920 --> 00:02:45,480
Yeah, definitely felt that.

81
00:02:45,480 --> 00:02:48,480
So Zulip, with its streams and topics,

82
00:02:48,480 --> 00:02:51,400
it's more like a well-organized library.

83
00:02:51,400 --> 00:02:52,240
Okay.

84
00:02:52,240 --> 00:02:53,520
Each stream could be a big channel,

85
00:02:53,520 --> 00:02:56,680
maybe marketing or engineering or a specific project.

86
00:02:56,680 --> 00:02:59,920
And within each stream, you create separate topics

87
00:02:59,920 --> 00:03:03,640
for specific discussions, like books on a shelf,

88
00:03:03,640 --> 00:03:04,680
each on one subject.

89
00:03:04,680 --> 00:03:06,800
Ah, okay, so within marketing,

90
00:03:06,800 --> 00:03:09,360
you might have a topic for a Project X campaign.

91
00:03:09,360 --> 00:03:10,400
Precisely.

92
00:03:10,400 --> 00:03:12,780
All the messages about that specific campaign,

93
00:03:12,780 --> 00:03:14,680
they live neatly in that one topic.

94
00:03:14,680 --> 00:03:17,040
So you can easily jump into the budget review topic

95
00:03:17,040 --> 00:03:20,040
for Project X without wading through, I don't know,

96
00:03:20,040 --> 00:03:22,800
team lunch plans or bug reports from engineering.

97
00:03:22,800 --> 00:03:26,120
It keeps discussions focused, context is right there,

98
00:03:26,120 --> 00:03:29,120
and you can catch up only on what matters to you.

99
00:03:29,120 --> 00:03:30,440
You don't feel buried.

100
00:03:30,440 --> 00:03:31,600
And about quick chats, yeah,

101
00:03:31,600 --> 00:03:34,080
you can absolutely have a general stream or social stream

102
00:03:34,080 --> 00:03:35,480
for that water cooler stuff.

103
00:03:35,480 --> 00:03:39,760
The genius is, those casual chats don't bury

104
00:03:39,760 --> 00:03:42,520
your critical project discussions.

105
00:03:42,520 --> 00:03:45,120
Information becomes accessible, searchable,

106
00:03:45,120 --> 00:03:46,680
not just something that scrolls away.

107
00:03:46,680 --> 00:03:48,800
That library analogy really helps it click.

108
00:03:48,800 --> 00:03:51,400
And yeah, the idea of not having important stuff buried

109
00:03:51,400 --> 00:03:53,720
under, I don't know, cat memes.

110
00:03:53,720 --> 00:03:54,740
That's very appealing.

111
00:03:54,740 --> 00:03:56,260
It sounds like it hits a major pain point.

112
00:03:56,260 --> 00:03:58,000
Information overload, context switching.

113
00:03:58,000 --> 00:03:59,240
So who's actually using this?

114
00:03:59,240 --> 00:04:01,260
Who finds this approach valuable?

115
00:04:01,260 --> 00:04:03,160
Is it just for certain kinds of teams?

116
00:04:03,160 --> 00:04:06,260
Actually, its reach is surprisingly broad.

117
00:04:06,260 --> 00:04:07,560
That's one of the compelling things.

118
00:04:07,560 --> 00:04:08,540
It's not just small startups.

119
00:04:08,540 --> 00:04:10,860
We're talking Fortune 500 companies,

120
00:04:10,860 --> 00:04:12,640
major open source projects,

121
00:04:12,640 --> 00:04:15,080
thousands of other organizations using it daily.

122
00:04:15,080 --> 00:04:17,480
That structured approach scales really well.

123
00:04:17,480 --> 00:04:19,160
Fortune 500s, okay, that's interesting.

124
00:04:19,160 --> 00:04:21,960
So we've got the concept, but the real proof is,

125
00:04:21,960 --> 00:04:25,200
in the trenches, can you share some specific examples,

126
00:04:25,200 --> 00:04:27,180
real world cases from the sources

127
00:04:27,180 --> 00:04:29,320
that show the impact of this design

128
00:04:29,320 --> 00:04:30,840
across different types of users?

129
00:04:30,840 --> 00:04:31,920
Yeah, definitely.

130
00:04:31,920 --> 00:04:34,200
Let's look at the business world first.

131
00:04:34,200 --> 00:04:38,160
There's iDrift AS, a company with distributed teams.

132
00:04:38,160 --> 00:04:39,860
They found Zulip enabled

133
00:04:39,860 --> 00:04:42,740
efficient distributed team management.

134
00:04:42,740 --> 00:04:44,920
And their co-founder said something really interesting.

135
00:04:44,920 --> 00:04:48,200
Using Zulip significantly increases the size of the team

136
00:04:48,200 --> 00:04:50,520
for which a manager can meaningfully know what's going on.

137
00:04:50,520 --> 00:04:52,560
Wow, okay, that's a big claim.

138
00:04:52,560 --> 00:04:55,120
Empowering leaders for bigger distributed teams.

139
00:04:55,120 --> 00:04:56,640
Exactly, because the communication

140
00:04:56,640 --> 00:04:58,600
is just so much more organized.

141
00:04:58,600 --> 00:05:00,920
Then you have Semsey, they're an insurance tech.

142
00:05:00,920 --> 00:05:02,440
They flat out said they found Zulip

143
00:05:02,440 --> 00:05:05,600
more efficient than Slack for organizing communication.

144
00:05:05,600 --> 00:05:07,640
Their director of engineering actually said,

145
00:05:07,640 --> 00:05:09,440
I don't like going back to Slack now.

146
00:05:09,440 --> 00:05:12,840
That's quite the statement, suggests a real shift.

147
00:05:12,840 --> 00:05:14,080
It really does.

148
00:05:14,080 --> 00:05:18,020
And Atolio, an AI company, their CEO stressed how

149
00:05:18,020 --> 00:05:20,520
the first class threads are absolutely

150
00:05:20,520 --> 00:05:21,820
critical to how we work.

151
00:05:21,820 --> 00:05:23,280
For them, it's fundamental.

152
00:05:23,280 --> 00:05:26,120
Even Endpoint Dev, managing hundreds of projects,

153
00:05:26,120 --> 00:05:28,840
found the UI easy for that complexity.

154
00:05:28,840 --> 00:05:30,840
Speaks volumes about its design for scale.

155
00:05:30,840 --> 00:05:33,080
Those are strong business cases, especially

156
00:05:33,080 --> 00:05:35,040
that don't like going back to Slack comment.

157
00:05:35,040 --> 00:05:37,240
What about open source and communities?

158
00:05:37,240 --> 00:05:39,480
That's all about distributed async work.

159
00:05:39,480 --> 00:05:41,080
Absolutely essential there.

160
00:05:41,080 --> 00:05:43,180
The rest language community is a prime example.

161
00:05:43,180 --> 00:05:45,720
They saw a huge jump in decision making speed.

162
00:05:45,720 --> 00:05:47,180
The quote is amazing.

163
00:05:47,180 --> 00:05:49,420
Decisions that were blocked for months on GitHub

164
00:05:49,420 --> 00:05:51,520
were resolved within 24 hours on Zulip.

165
00:05:51,520 --> 00:05:54,280
24 hours down from months.

166
00:05:54,280 --> 00:05:54,920
Yeah.

167
00:05:54,920 --> 00:05:57,400
Think about that impact on getting things done.

168
00:05:57,400 --> 00:06:00,520
It's about getting the right people focused on a topic.

169
00:06:00,520 --> 00:06:02,040
Clearly laying out the discussion,

170
00:06:02,040 --> 00:06:04,640
making sure everyone sees the latest without getting lost.

171
00:06:04,640 --> 00:06:06,440
That's huge for project velocity.

172
00:06:06,440 --> 00:06:06,920
Definitely.

173
00:06:06,920 --> 00:06:08,000
And then there's the Recurse Center,

174
00:06:08,000 --> 00:06:08,960
the programmer retreat.

175
00:06:08,960 --> 00:06:11,520
They've used Zulip since way back in 2013

176
00:06:11,520 --> 00:06:14,080
for their global community shows its staying power.

177
00:06:14,080 --> 00:06:16,240
And it's big in education and research too.

178
00:06:16,240 --> 00:06:18,360
Structured communication is vital there.

179
00:06:18,360 --> 00:06:21,320
TUM in Germany uses it for organized chat

180
00:06:21,320 --> 00:06:23,200
for thousands of students.

181
00:06:23,200 --> 00:06:27,640
UCSD uses it as a communication hub across six continents.

182
00:06:27,640 --> 00:06:29,200
Wow, across continents.

183
00:06:29,200 --> 00:06:30,840
Yeah, really global collaboration.

184
00:06:30,840 --> 00:06:32,560
Even the lean mathematical community

185
00:06:32,560 --> 00:06:35,600
uses it for research collaboration at scale.

186
00:06:35,600 --> 00:06:38,360
These are highly technical, precise discussions

187
00:06:38,360 --> 00:06:40,040
where clarity is just paramount.

188
00:06:40,040 --> 00:06:42,680
OK, so we're seeing it used everywhere from businesses

189
00:06:42,680 --> 00:06:45,920
managing huge projects to global research communities.

190
00:06:45,920 --> 00:06:47,760
What does this all boil down to for a listener?

191
00:06:47,760 --> 00:06:50,000
Someone trying to pick a tool, maybe feeling overwhelmed

192
00:06:50,000 --> 00:06:51,160
by information overload?

193
00:06:51,160 --> 00:06:53,660
All right, this is where it gets really interesting for anyone

194
00:06:53,660 --> 00:06:54,760
feeling that pain.

195
00:06:54,760 --> 00:06:57,800
Zulip simplifies knowledge management almost,

196
00:06:57,800 --> 00:06:59,160
automatically.

197
00:06:59,160 --> 00:07:02,240
It creates an organized repository of knowledge

198
00:07:02,240 --> 00:07:03,360
as a side effect.

199
00:07:03,360 --> 00:07:04,240
As a side effect?

200
00:07:04,240 --> 00:07:05,320
How so?

201
00:07:05,320 --> 00:07:07,240
Because conversations are naturally structured

202
00:07:07,240 --> 00:07:08,940
by topic from the start.

203
00:07:08,940 --> 00:07:10,400
You're not just chatting.

204
00:07:10,400 --> 00:07:12,720
You're actively building a searchable history

205
00:07:12,720 --> 00:07:14,800
of discussions and decisions.

206
00:07:14,800 --> 00:07:17,560
Unlike linear chat, where things just vanish upwards.

207
00:07:17,560 --> 00:07:20,200
Yeah, try finding that decision from three weeks ago.

208
00:07:20,200 --> 00:07:21,040
Exactly.

209
00:07:21,040 --> 00:07:23,760
In Zulip, the structure is the organization.

210
00:07:23,760 --> 00:07:25,800
It becomes your team's collective brain, easily

211
00:07:25,800 --> 00:07:26,640
searchable.

212
00:07:26,640 --> 00:07:29,000
You don't need a separate system to file things away.

213
00:07:29,000 --> 00:07:31,160
It directly helps you get the knowledge you need quickly,

214
00:07:31,160 --> 00:07:32,240
without feeling buried.

215
00:07:32,240 --> 00:07:36,240
Imagine never having that, was that in Slack, or email,

216
00:07:36,240 --> 00:07:38,360
or that Google Doc moment again.

217
00:07:38,360 --> 00:07:40,520
That is a huge potential benefit.

218
00:07:40,520 --> 00:07:44,040
Turning chat from noise into an actual asset.

219
00:07:44,040 --> 00:07:46,240
Now you mentioned earlier Zulip is open source.

220
00:07:46,240 --> 00:07:50,240
That term can sound a bit khaki, maybe intimidating for some.

221
00:07:50,240 --> 00:07:53,160
What does being 100% open source actually

222
00:07:53,160 --> 00:07:55,320
mean for how Zulip is developed?

223
00:07:55,320 --> 00:07:57,160
And maybe more importantly for the users,

224
00:07:57,160 --> 00:07:59,080
especially someone without a big IT department.

225
00:07:59,080 --> 00:08:00,480
Yeah, it's a crucial aspect.

226
00:08:00,480 --> 00:08:05,840
So 100% open source means all its code is public, transparent.

227
00:08:05,840 --> 00:08:09,200
It uses the Apache 2.0 license, which is very permissive.

228
00:08:09,200 --> 00:08:11,200
But it's not just about seeing the code.

229
00:08:11,200 --> 00:08:13,960
It creates this amazing community-driven development.

230
00:08:13,960 --> 00:08:16,480
Zulip has a really robust, active community

231
00:08:16,480 --> 00:08:19,120
over 1,000 contributors worldwide.

232
00:08:19,120 --> 00:08:22,200
More than 74 people have made over 100 code contributions

233
00:08:22,200 --> 00:08:22,840
each.

234
00:08:22,840 --> 00:08:24,080
That's a lot of involvement.

235
00:08:24,080 --> 00:08:24,680
Wow.

236
00:08:24,680 --> 00:08:26,560
They merge over 500 contributions

237
00:08:26,560 --> 00:08:27,920
every single month.

238
00:08:27,920 --> 00:08:30,600
It's actually called the largest and fastest growing open source

239
00:08:30,600 --> 00:08:32,720
team chat project.

240
00:08:32,720 --> 00:08:34,520
So what does that mean for you, the user?

241
00:08:34,520 --> 00:08:36,300
First, no vendor lock-in.

242
00:08:36,300 --> 00:08:37,120
You own your data.

243
00:08:37,120 --> 00:08:38,760
You're not stuck with one company changing

244
00:08:38,760 --> 00:08:39,600
prices or direction.

245
00:08:39,600 --> 00:08:40,440
That's important.

246
00:08:40,440 --> 00:08:42,400
Second, security and stability get a boost

247
00:08:42,400 --> 00:08:44,320
from all those eyes reviewing the code.

248
00:08:44,320 --> 00:08:46,200
Bugs get found and fixed fast.

249
00:08:46,200 --> 00:08:48,960
Third, the project tends to be really responsive

250
00:08:48,960 --> 00:08:50,920
because the users are the contributors often.

251
00:08:50,920 --> 00:08:53,300
It gives you confidence it'll be around and keep improving

252
00:08:53,300 --> 00:08:55,000
in ways users actually want.

253
00:08:55,000 --> 00:08:57,280
That community power is impressive.

254
00:08:57,280 --> 00:09:00,480
No lock-in is a big deal for businesses, too.

255
00:09:00,480 --> 00:09:03,560
So for someone listening now, maybe a small business owner,

256
00:09:03,560 --> 00:09:06,400
an educator starting a community,

257
00:09:06,400 --> 00:09:08,000
how do they actually try Zulip?

258
00:09:08,000 --> 00:09:10,880
Is it hard to set up if you're not super technical?

259
00:09:10,880 --> 00:09:12,040
No, not necessarily.

260
00:09:12,040 --> 00:09:14,260
They've made it quite accessible.

261
00:09:14,260 --> 00:09:17,100
There are a few main options depending on your needs.

262
00:09:17,100 --> 00:09:19,960
If you want ultimate control and compliance,

263
00:09:19,960 --> 00:09:22,920
maybe you have strict data rules, you can self-host it.

264
00:09:22,920 --> 00:09:25,640
They've worked hard to make installation and upgrades easy

265
00:09:25,640 --> 00:09:28,660
on standard Linux, like Ubuntu, Debian,

266
00:09:28,660 --> 00:09:31,320
or you can use Docker, which simplifies things a lot.

267
00:09:31,320 --> 00:09:32,320
Docker helps, yeah.

268
00:09:32,320 --> 00:09:33,900
And they even have pre-built images

269
00:09:33,900 --> 00:09:36,520
for places like DigitalOcean or Render.

270
00:09:36,520 --> 00:09:38,640
So you can get it running with just a few clicks,

271
00:09:38,640 --> 00:09:40,280
even without being a Linux guru.

272
00:09:40,280 --> 00:09:42,280
Full data ownership on your own server.

273
00:09:42,280 --> 00:09:44,080
OK, so self-hosting is an option.

274
00:09:44,080 --> 00:09:45,760
Maybe easier than people think.

275
00:09:45,760 --> 00:09:47,800
What if you don't want to manage servers?

276
00:09:47,800 --> 00:09:49,680
Then there's the cloud hosting solution straight

277
00:09:49,680 --> 00:09:51,920
from the Zulip team that's super convenient.

278
00:09:51,920 --> 00:09:52,880
You get all the features.

279
00:09:52,880 --> 00:09:55,840
And importantly, they have tools to import your data

280
00:09:55,840 --> 00:09:57,880
and integrations if you're moving from Slack

281
00:09:57,880 --> 00:09:58,920
or somewhere else.

282
00:09:58,920 --> 00:10:00,120
Makes switching easier.

283
00:10:00,120 --> 00:10:01,880
Ah, import tools are key.

284
00:10:01,880 --> 00:10:02,720
Definitely.

285
00:10:02,720 --> 00:10:04,200
And another big point.

286
00:10:04,200 --> 00:10:09,040
For most non-business uses, think nonprofits, governments,

287
00:10:09,040 --> 00:10:13,480
education, they offer free or heavily discounted plans.

288
00:10:13,480 --> 00:10:15,200
So it's incredibly accessible.

289
00:10:15,200 --> 00:10:16,960
Honestly, the best way to check Zulip out,

290
00:10:16,960 --> 00:10:19,960
just go visit the public Zulip community server itself.

291
00:10:19,960 --> 00:10:22,640
See how they use topics, explore the discussions,

292
00:10:22,640 --> 00:10:23,720
get a real feel for it.

293
00:10:23,720 --> 00:10:24,800
Right, see it in action.

294
00:10:24,800 --> 00:10:25,840
Good tip.

295
00:10:25,840 --> 00:10:28,400
OK, so let's quickly recap this deep dive.

296
00:10:28,400 --> 00:10:30,960
Zulip's unique thing is that topic-based threading.

297
00:10:30,960 --> 00:10:36,160
It turns messy chat into organized async communication,

298
00:10:36,160 --> 00:10:37,960
which makes it useful pretty much everywhere.

299
00:10:37,960 --> 00:10:41,000
Big companies, open source projects, schools, researchers.

300
00:10:41,000 --> 00:10:42,120
Right across the board.

301
00:10:42,120 --> 00:10:44,780
And being open source gives it that community strength,

302
00:10:44,780 --> 00:10:47,180
flexibility, and long-term security.

303
00:10:47,180 --> 00:10:48,840
Which leads to a really important question

304
00:10:48,840 --> 00:10:50,280
for you listening.

305
00:10:50,280 --> 00:10:52,920
How could a tool like this, one designed for structure, one

306
00:10:52,920 --> 00:10:54,760
that builds knowledge automatically,

307
00:10:54,760 --> 00:10:56,840
how could that change your specific workflow,

308
00:10:56,840 --> 00:10:58,440
your team, your community?

309
00:10:58,440 --> 00:11:00,780
What problems might it solve that maybe you haven't even

310
00:11:00,780 --> 00:11:03,000
thought about solving with just a different chat tool?

311
00:11:03,000 --> 00:11:03,640
Exactly.

312
00:11:03,640 --> 00:11:05,100
Here's a final thought to mull over.

313
00:11:05,100 --> 00:11:07,600
How much time, how much clarity, how much focus

314
00:11:07,600 --> 00:11:09,600
could you actually gain by moving away

315
00:11:09,600 --> 00:11:11,960
from those fragmented linear chats

316
00:11:11,960 --> 00:11:14,400
towards something more organized, more context rich,

317
00:11:14,400 --> 00:11:15,480
like Zulip?

318
00:11:15,480 --> 00:11:16,840
What could your team or community

319
00:11:16,840 --> 00:11:19,960
do if its knowledge was just effortlessly structured

320
00:11:19,960 --> 00:11:23,320
and accessible instead of loss scrolling back through history?

321
00:11:23,320 --> 00:11:25,600
Our deep dive today was supported by Safe Server.

322
00:11:25,600 --> 00:11:28,640
For secure software hosting and digital transformation support

323
00:11:28,640 --> 00:11:30,360
helping you simplify your tech life,

324
00:11:30,360 --> 00:11:32,680
do visit www.safeserver.de.