[ BETTER TECH LEADERSHIP ]

From Sports to Success: Unveiling Leadership Strategies

[ THE SPEAKERS ]

Meet our hosts & guests

Matt Warcholinski
CO-FOUNDER, BRAINHUB

Co-founder of Brainhub, Matt describes himself as a “serial entrepreneur”. Throughout his career, Matt has developed several startups in Germany, wearing many hats- from a marketer to an IT Engineer and customer support specialist. As a host of the Better Tech Leadership podcast, Matt talks about growing successful businesses and the challenges of being a startup founder and investor.

David Gebhardt
Chief Technology Officer (CTO)

David Gebhardt is the Chief Technology Officer (CTO) at mobile.de, where he leads the technology, data, business systems, and organizational development teams. With a robust career spanning over two decades, David has made significant impacts in various roles at IBM, Ernst & Young (EY), eBay, and Adevinta. Recognized in Capital's "Top 40 Under 40" in 2022, David is known for his strategic thinking and pragmatic approach, thriving in trust-based and cross-functional team environments.

Transcript

00:22 - 00:24
David, I'm really happy to have you here.

00:24 - 00:29
It's always a pleasure to, talk with people who are so experienced in the tech.

00:30 - 00:37
And you are super experienced, I would say, because you have the background, so the business background.

00:37 - 00:41
And currently you're connecting the role of the CTO, CPO.

00:41 - 00:47
For many years, you worked on the eBay, the so, like, one of the, I think, the biggest marketplaces

00:48 - 00:50
in, in in in Germany.

00:51 - 00:52
Now we are involved in Mobila.

00:53 - 00:57
And while I was living in Germany, it was, like, huge thing.

00:57 - 01:00
So if you look for a car, you you know the website.

01:01 - 01:04
And you made so many different things.

01:04 - 01:11
So I'm just wondering, after so many experiences, what is the next role for you?

01:12 - 01:17
Yeah. I I actually, stopped thinking about the next role.

01:18 - 01:22
It's more, trying to do it in the here and now, a little bit.

01:23 - 01:27
I think it's more additions to the wall.

01:27 - 01:34
I think as you stated, I gained a lot of experience through consulting through my, current role

01:34 - 01:42
in in Mobilia and and, being happy about delivering valuable products, to millions of users every month.

01:42 - 01:48
So it's more looking into what of this experience and knowledge can I give back to the community?

01:48 - 01:51
Maybe this is also one reason, why we're talking here.

01:53 - 02:01
So, I'm thinking about, advisory roles, for example, to really help, also early stage startups,

02:02 - 02:08
in a way in in going faster or, trying to prevent from making the same mistakes over and over

02:08 - 02:10
again that we did in the past.

02:11 - 02:16
So I'm looking into advisory roles, but at the same time, there are just so many things that

02:16 - 02:20
are still, worthwhile to do in Mobina.

02:21 - 02:24
I mean, there's a lot of change in the automotive industry.

02:25 - 02:31
Only looking at electric vehicles, the whole change to greener mobility, all the uncertainties

02:31 - 02:40
that are out there in that space, but also other changes like, people actually trying to buy

02:40 - 02:49
cars fully online, where the car industry was kind of the last resort where actually people

02:50 - 02:54
went to the dealership and, did a test drive and so on.

02:54 - 03:01
But you see this kind of deemotionalization of cars a little bit, also in Germany, where this

03:01 - 03:10
is a real big thing, where people tend to, subscribe to cars, or, basically buy online.

03:10 - 03:17
And this is introducing another level of complexity that we try to make simple, as a platform.

03:19 - 03:25
So let's talk about the mobile that, I'm just wondering what is your current, team structure?

03:25 - 03:28
In house, outsource, how do you structure it?

03:29 - 03:33
Yeah. We have a mix of in house and external.

03:34 - 03:39
So, Product Technomobile is roughly 350, 400 people.

03:40 - 03:47
The majority is still internal, and I think there needs to be a healthy mix in that.

03:48 - 03:52
If you lean into something too much, you will see the downsides quite heavily.

03:54 - 04:01
So when we work with externals, it's, mainly to speed things up, when we scale up new businesses

04:01 - 04:11
or, if we decide that a certain product is maybe, nothing we wanna have as the core of our business

04:11 - 04:19
anymore and kind of phase it out a little bit, that we handed over, to excellent parties to

04:19 - 04:21
to run it, in a way for us.

04:23 - 04:32
But what we want, to avoid is, kind of being too dependent on external parties when it comes

04:32 - 04:39
to core aspects of our business because this is not healthy, and risk in itself.

04:41 - 04:45
So we believe in in in managing that quite consciously.

04:46 - 04:54
At the same time, external parties, and this is, I think, the the second aspect of it, do bring

04:55 - 04:58
in new ideas, new energies to teams.

04:58 - 05:05
So we see it as a valuable addition to our teams, also bringing subject matter experts, in certain

05:05 - 05:14
fields to actually, immerse ourselves with this knowledge, where it's maybe harder to hire someone,

05:15 - 05:22
if you then have this lone fighter in your in your organization, where then the question will

05:22 - 05:26
become, how do you develop these these people functionally?

05:27 - 05:33
How can they grow also in terms of career if they're maybe the only person doing, doing a certain thing.

05:34 - 05:36
So that's where excellence come in.

05:37 - 05:42
A strong belief we have is externals shouldn't be just, treated as yeah.

05:42 - 05:47
They are this is a separate team, and they don't really belong to us.

05:47 - 05:55
For us, externals are actually part, a real part of our teams of the rituals, and so on, so

05:55 - 06:02
that they really understand, like, what is our business direction, how we are working, how we

06:02 - 06:12
are dealing with with stuff, also our culture to, to really have this belonging, kind of thinking in there.

06:14 - 06:19
Okay. And regarding the team structure and what you said, I'm just wondering who is your partner

06:19 - 06:23
in crime with whom you work the most?

06:24 - 06:29
Yeah. So maybe there are 2 or 3 answers to that.

06:30 - 06:39
I'm as I'm leading product and technology in Mobila, so my teams are basically product in the

06:39 - 06:46
sense of product managers, head of products, then technology, all the engineers, data engineers,

06:46 - 06:48
data scientists, and so on.

06:48 - 06:57
And then it's also UX, and in my case, also organizational development, which is kind of a special case, in a way.

06:59 - 07:04
So the people I'm working most with is my direct team, that consists of head of technologies,

07:04 - 07:06
head of product, head of UX, head of data.

07:08 - 07:18
And, we work kind of in in an org structure that is based on the customer journey, then structured in groups and teams.

07:19 - 07:28
So maybe different naming for a couple of things, but, you may see some similarities, to other

07:28 - 07:32
companies out there, who published a little bit, about that.

07:33 - 07:39
So we believe in autonomous teams, end to end accountability, and ownership for certain parts

07:39 - 07:45
of the customer journey, a certain domain, and in true cross function work, and this doesn't

07:45 - 07:47
end with product and tech.

07:47 - 07:53
It's really like if you look at the consumer upper funnel, you will have marketing in there.

07:53 - 07:59
You will have, analyst in there, and so on to really understand, like, user acquisition, user

07:59 - 08:01
retention, and these kind of things.

08:02 - 08:04
So that's the first part of the answer.

08:04 - 08:13
The second part of the answer, I'm part of the Mobilia management team, which, then is basically overlooking the company holistically.

08:14 - 08:22
And, when it comes to that, my biggest partner in crime is potentially the COO, so the chief

08:22 - 08:29
operating officer, where it's really talking about what are the priorities, what is the strategy

08:29 - 08:36
of our business, and subsequently of our product? So, he's called Johan.

08:36 - 08:43
I'm called David, and we get this cool mixed up name, Jovid, when we are together on stage.

08:43 - 08:45
So I think that says a lot.

08:48 - 08:57
That's a great answer. And regarding the challenges that you are having, combining the CTO and

08:57 - 09:00
CPO, I I've seen this is kind of, like, getting really popular.

09:00 - 09:02
So you have this concept of CTPO.

09:02 - 09:09
And I'm wondering, in your case, what are the biggest challenges that you face, being in this role?

09:09 - 09:20
Yeah. Next to being asked the question about a CPTO or CTO and CPO, which is always nice, and, answering that shortly.

09:21 - 09:28
I think there's a good time for a CPTO and a good context for CPTO, and and there's also good

09:29 - 09:34
time maturity of a company and context for having both worlds, separately.

09:35 - 09:37
So there's no white or wrong there, I guess.

09:39 - 09:49
In looking at challenges in my role, I think, one of the biggest evergreens is how do we actually

09:49 - 09:56
balance creating user value and, putting in time and functional excellence or reducing technical

09:56 - 10:00
depth, however you wanna, you wanna call it.

10:02 - 10:08
And that's not easy. And in a way, it really comes together where product and tech meet.

10:09 - 10:13
So it comes together in this kind of wall, in a way.

10:13 - 10:26
And you could can put worlds around that, but then still it's not that, it's like, a thing that just solves itself. Right?

10:27 - 10:37
And I guess the second aspect is, and maybe also an evergreen, it's creating the organization

10:38 - 10:43
and the processes and the environment, to actually enable productive work.

10:43 - 10:52
And, if I'm thinking about, like, what's actually my role in this organization, it's basically

10:52 - 10:53
that together with my team.

10:55 - 11:04
And maybe last comment on that, and I think that it's nothing that is reserved for the CPT overall,

11:04 - 11:08
but for every c level wall in a way or every leadership wall actually.

11:09 - 11:13
And one mentor of me put it quite nicely.

11:14 - 11:23
He said, as a leader, you need to decide the undecidable, and this will always be a challenge to do that.

11:25 - 11:27
That's a that's a good good answer.

11:30 - 11:32
And I have one common problem.

11:32 - 11:39
As I mentioned to you before, I talked with my colleague who is c p CPO, and he he asked me,

11:39 - 11:41
like, could you ask David this question?

11:42 - 11:48
And I just wanted to ask you because I think it's a huge challenge, especially in in your role too.

11:48 - 11:54
So how do you decide, and what is it, like, maybe the process behind it?

11:54 - 12:00
Do you, if you want to build the feature, or do you need to terminate the feature?

12:00 - 12:02
Because sometimes you have the features that needs to be terminated.

12:03 - 12:06
Like, what is the decision making process behind this?

12:07 - 12:15
Yep. And as history shows, it's always easier to start building stuff than to say goodbye to stuff.

12:16 - 12:23
So maybe that as a first comment, building stuff is quite straightforward.

12:24 - 12:32
I mean, a lot of companies evolved around the ideas of business cases, to actually start something big and new.

12:32 - 12:36
Like looking at starting from, hey. There's a user problem.

12:37 - 12:41
We kind of are in a position to actually tackle that problem.

12:41 - 12:46
And we have ideas how you can solve it with a product, in a way.

12:46 - 12:53
And then of course, you ask yourself the questions like, how big is the audience?

12:54 - 13:05
How confident are you that you can solve the problem and is there actually, also a good business reason to do it. Right?

13:05 - 13:15
Because what we do is actually we wanna, solve user problems or customer problems, and By that,

13:15 - 13:18
also having a sustainable business.

13:19 - 13:27
So that's kind of straightforward because, everybody knows there are different metrics you can use for that.

13:27 - 13:29
We know how to measure a successful business.

13:29 - 13:35
At least, there is, measures that are used worldwide, for that.

13:36 - 13:39
But when it comes to terminating products,

13:42 - 13:47
it's for me a lot more emotional also from an organizational perspective.

13:47 - 13:55
I mean, people invested potentially years of their professional life building a certain product or product suite.

13:56 - 14:04
And, and it really needs a lot of diligence, to actually ask the question.

14:04 - 14:07
Should we actually stop a product?

14:08 - 14:14
And, I think there are a couple of signals or indicators, that you can use.

14:15 - 14:19
I talked about a little bit of function excellence, technical depth, and so on.

14:20 - 14:28
And if your team doesn't go every year, you will, kind of experience that when you build and

14:28 - 14:33
build and build new products and features, the complexity of platform grows.

14:33 - 14:41
The artifact ownership per person or per team is increasing, which kind of sends a couple of

14:41 - 14:43
small signals, you should listen to.

14:45 - 14:51
So if your product development life cycle is not also looking at terminating products, you will

14:52 - 14:55
see effects of that in terms of platform health and so on.

14:57 - 15:08
So we do not have, like, a review cycle where we look through all of our products on a quarterly or yearly basis. That's not worth reviewing.

15:09 - 15:13
But everyone is free to kind of come up with, hey.

15:14 - 15:19
This piece of product, there's not so much business value anymore.

15:19 - 15:25
Can we please look at how much effort it is to actually keeping it afloat in a way?

15:26 - 15:32
And, these kinds of kind of conversations we have for a couple of products each year, where

15:32 - 15:36
we then decide, like, what's the right way to go forward with that.

15:36 - 15:42
Because, at the end of the product development life cycle, it doesn't necessarily need to be

15:42 - 15:44
you just shut it down.

15:44 - 15:50
And sometimes you have legal obligations to have a product for a certain period of time because

15:50 - 15:52
you handed out contracts for it.

15:53 - 15:54
So this plays a role.

15:54 - 16:01
And then also, maybe it's a conscious decision to evolve the product or we factor the product

16:01 - 16:05
in a way to make it relevant again. Right?

16:06 - 16:09
So that's kind of the basic thinking.

16:11 - 16:18
And let's discuss a bit more the market trends and how do you approach following the market trends.

16:18 - 16:21
Because what you said about the EVs, this is not the hot topic.

16:22 - 16:28
And I have a feeling based on my experience as a leader, you always look how you could lead

16:28 - 16:32
people better, how you can help them to communicate and deliver the value.

16:32 - 16:38
But on the on the other hand, you're trying to help those guys and find the right trends and,

16:38 - 16:44
like, set up the long term strategy based on your market research and based, I don't know, on

16:44 - 16:45
the market trends that are there.

16:45 - 16:49
And I'm just wondering how do you approach it. Maybe you read something.

16:49 - 16:52
Maybe you go to some conferences that are really important for for yourself.

16:54 - 16:56
What is your what what is your process here?

16:57 - 17:01
Yep. That's maybe the one challenge I forgot, on your question earlier.

17:02 - 17:12
The constant learning aspect, in a world where your day job, takes a little bit of time, and

17:12 - 17:15
then your family, friends, hobbies, hopefully, hobbies.

17:16 - 17:24
So, it's also it's not only the question of are you still willing to learn, but it's also a

17:24 - 17:27
question of being efficient, around that.

17:29 - 17:34
So for me, it's really trying to combine a couple of things.

17:35 - 17:38
I'm active part of a couple of CTO groups.

17:38 - 17:43
So getting insights and knowledge from from these other leaders in the industry.

17:45 - 17:53
Throughout my whole career, I had mentors and coaches, to actually have someone to talk to, about certain things.

17:54 - 17:58
And then it's also learning through podcasts and books.

17:58 - 18:01
In my case, more audio audiobooks.

18:02 - 18:04
And I touched on being efficient around that.

18:06 - 18:18
Usually, I listen to podcasts and audiobooks while commuting on my bike, or while training, basically, running, biking.

18:18 - 18:23
It's a little bit harder in swimming, but, you can also do that.

18:24 - 18:27
And then, I have a couple of newsletters.

18:28 - 18:37
I read, like, TLDR and these kind of things, to at least, understand, like, what are the key

18:37 - 18:44
themes out there and then dig deeper, if I feel, that's valuable, in the end.

18:45 - 18:53
But, this is still one of the biggest challenge, especially if you if you kind of as a profile,

18:53 - 18:58
I consider myself a generalist. It's technology. It's product.

18:58 - 19:02
It's general management, in a lot of, ways.

19:03 - 19:10
So there are just a lot of topics that you could lose yourself into, basically.

19:11 - 19:18
So it's really also a question of, how deep do you go into certain things?

19:18 - 19:24
Like, and then lastly, it's, also by visiting conferences.

19:25 - 19:34
And it spans from, automotive conferences to kind of, tech, gatherings and so on.

19:35 - 19:37
So really meeting a lot of people.

19:39 - 19:48
And I think, like, especially in area, like, of the the the new market, especially in attack,

19:48 - 19:55
I I see there's a lot of, like, new tools each day, new libraries, new approaches to build the

19:55 - 19:58
products, and it's really tempting and it's really hard to decide.

19:59 - 20:04
Like, should we go this way, or should we, like, rewrite our product?

20:04 - 20:13
And I'm just wondering how do you identify and decide on your tools because I because those influence the whole teams. Right?

20:13 - 20:18
It's like you have a huge huge team, and I could imagine, like, based on my experience that

20:18 - 20:24
that the developers, for instance, they are going with, like, a bunch of new different things

20:24 - 20:25
each day, and I say, like, hey.

20:25 - 20:26
We should go this way.

20:27 - 20:33
But at the same point, you need to make the decision and probably, it's really tough to find

20:33 - 20:36
yourself within all those tools.

20:37 - 20:43
So how do you decide if you go this way or that way, regarding the new tools that influence the whole teams?

20:43 - 20:48
Yep. That's the beauty of a kind of big organization, in a way.

20:48 - 20:50
So you don't have to do this all on your own.

20:50 - 20:57
So, for collaboration tools, I touched upon, the organizational development team.

20:57 - 21:01
So a lot of, these kind of insights come from them.

21:01 - 21:09
And usually, we do one test, with small user group first, trying to figure out, like, does it really fit our needs?

21:10 - 21:14
Is it, really better than the tools we use so far?

21:15 - 21:21
And also for develop experience, we have a platform team figuring some of the things out.

21:22 - 21:24
We're part of a bigger portfolio of companies.

21:24 - 21:31
So you also have, like, Adevinda or parent company, defining kind of a golden pass and path

21:31 - 21:39
of the develop develop experience, where they really, also gather insights from all the portfolio

21:39 - 21:47
companies, like, what worked, what didn't work so well, to kind of, not find the perfect solution

21:47 - 21:56
because I think there is no perfect, especially if you have, like, a diverse set of, of companies and needs.

21:57 - 22:04
But actually trying to gather, this insight and then test, evaluate, and and and bring it to the people.

22:05 - 22:14
And, for for mobile, we, also won innovation days, once a quarter for 3 to 4 days where basically

22:14 - 22:17
people are free to just test things out.

22:18 - 22:26
And this is, this is kind of interesting because a lot of, the things that are done there, like,

22:26 - 22:32
I would say, like, 60% of the things, are really, like, trying to build new product ideas.

22:33 - 22:35
MVP is trying to test something out.

22:36 - 22:41
The other part is is about developer experience, and tools, and new frameworks.

22:42 - 22:46
Like, figuring out, could this be something we should pick up in a way?

22:47 - 22:54
And, when it comes to additions to our tech stack, then obviously, this go through, like, architecture

22:56 - 22:59
decision records to actually put it on our tech radar and adopt it.

23:00 - 23:06
But the innovation days are really like this safe space in a way, to really test, like, is there

23:06 - 23:09
a reason to adopt certain things?

23:10 - 23:17
Are there any tools, trends, ideas, or concept that you are really passionate about recently

23:17 - 23:21
and you are, you know, getting in into the detail of it? I

23:22 - 23:25
mean, it's it's potentially not only me.

23:26 - 23:28
It's the whole world right now. Right?

23:29 - 23:38
It's I mean, the the the opportunities and challenges with AI is, what has been the, dominant

23:38 - 23:42
theme for last couple of innovation days, actually.

23:43 - 23:49
And, I mean, it's it's a lot of playing with the opportunities and trying to understand, like,

23:49 - 23:52
where does actually add user value.

23:52 - 23:59
Because I think there are a lot of things out there that are done for the purpose of doing stuff with AI, right now.

24:00 - 24:06
Not too much that is actually providing sustainable user value.

24:07 - 24:14
And I think finding this sweet spot, where it's actually helpful and how do you, productionize

24:14 - 24:20
it in a way is where a lot of our attention is in those innovation days.

24:21 - 24:23
And the next one is actually early December.

24:24 - 24:25
So really looking forward to that.

24:26 - 24:28
How often do you do do those?

24:28 - 24:30
Quarterly. Quarterly.

24:30 - 24:37
Okay. Okay. Okay. And, I have another question that I wanted to ask you about, like, organizing

24:38 - 24:44
the the the the teams, and maybe you could have some advices or tips for other leaders.

24:45 - 24:51
How do you successfully deliver the product and especially in the teams that are so like, you

24:51 - 24:55
have in house, you have outsource, maybe you have different time zones.

24:57 - 24:59
Some of the peoples are remote. I don't know.

24:59 - 25:05
Do you have any advices or tips what worked, in your case, in such a highly distributed teams

25:05 - 25:08
to make the delivery of the product successful.

25:08 - 25:21
Yeah. I mean, the good thing for mobile is, we're kind of, all, located in roughly the same time zone.

25:23 - 25:28
So a lot of our, people are located in Germany, especially, like, all the people that are working

25:28 - 25:30
internally for us are located in Germany.

25:33 - 25:45
So that's fairly easy in terms of time zone, but we're not an real office first company anymore.

25:45 - 25:52
I mean, there was this major incident worldwide, that led to us being a remote company for quite some time.

25:53 - 25:57
Now we're back with, at least the office option, I would say.

25:59 - 26:02
And, but we are holding that quite flexibly.

26:03 - 26:08
So there's no, no pressure for you to be in the office, for example.

26:09 - 26:15
I think our policy says something like, a minimum of 4 days a quarter, or something you need

26:15 - 26:18
to be in the office, and nobody checks.

26:18 - 26:21
So that's, that's kind of the policy right now.

26:22 - 26:25
But what we're saying as Mobila, is, hey.

26:26 - 26:27
We wanna have these moments.

26:29 - 26:35
The moments where teams come together because we believe that, magic happens when actually people

26:35 - 26:37
come together to create stuff.

26:38 - 26:45
So innovation days is a good example where we try to kind of also provide a couple of things

26:45 - 26:48
that make people come to the office and do magic.

26:49 - 26:57
And it's, the the these moments are, of course, best case celebrations and stuff like that.

26:58 - 27:06
Or when it comes to, creative work, like people in the room white boarding and trying to figure out something.

27:07 - 27:16
And the last aspect that is pretty important, from my point of view is, that you, as a leader,

27:16 - 27:21
for your team reflect, like, are we maybe a team that is in the forming or storming phase?

27:21 - 27:26
Because there, I believe, like, coming together as a team and doesn't necessarily have to be

27:26 - 27:34
in the office, is worthwhile to actually come to this performing stage at at a certain point.

27:36 - 27:39
And, for us, that works quite well.

27:39 - 27:47
If the reflection is there and the teams really understand like where they're at, I think that that works quite well.

27:49 - 27:56
And for working with externals, as I said before, it's really making them part of the rituals.

27:56 - 28:03
Making them part of the teams To actually have them experience exactly the same.

28:05 - 28:07
And that works quite well.

28:08 - 28:15
And then, of course, we're working with a couple of, of partners, more like in the near showing

28:15 - 28:22
space, for example, where it's not so easy to just meet in person, tomorrow, maybe.

28:23 - 28:30
And, I think the one learning also and also that is basically true in every hybrid or remote

28:30 - 28:37
setup is, the additional investment you need to do in proper communication

28:39 - 28:45
can't be overestimated. So it's really a lot you'd need to do additionally.

28:46 - 28:52
And it doesn't really like, communication doesn't end when you just put a post somewhere in

28:52 - 28:54
a Slack channel with 400 people.

28:55 - 29:00
You will see it in the reactions, not 400 people will will read it.

29:01 - 29:12
So kind of, transporting strategy or transporting a key decision is not done by just one post in a Slack channel.

29:12 - 29:19
It really takes more, and it takes more effort than in the office days.

29:21 - 29:25
The over communication is the key, I think, in this case. Right? Yeah.

29:25 - 29:29
So you you think you think it's already clear, but it's not.

29:29 - 29:34
You need to do it in a couple different ways, maybe in different meetings, on a different occasion.

29:34 - 29:37
So, that makes a lot of sense.

29:39 - 29:44
And, David, based on your experience, I'm just wondering, and I'm asking, like, each of our

29:44 - 29:49
guests about the most important lessons learned that you have have had as a technology or a

29:49 - 29:55
product leader that changed maybe something that changed your mindset or some some lessons learned

29:55 - 29:57
here, if you could share something like that.

29:58 - 30:07
Yeah. I think there are couple there, and, I I think we could spend, like, 2 days talking about any discussion.

30:08 - 30:17
I think on on my leadership journey, one of the hardest things was getting used to delegating,

30:17 - 30:20
and I think I'm not alone with that.

30:20 - 30:27
But when you're coming from from worlds and positions where you did a lot yourself, and we're

30:27 - 30:35
also confident about doing things yourself, then it's, feels kind of strange, in a way to kind

30:35 - 30:41
of delegate and kind of lose your grip a little bit.

30:42 - 30:51
And I think, for me, it needed that moment, in a way where I couldn't handle anymore doing all the things myself.

30:52 - 31:01
So, really learning it and also experience, like, people will do things much better than I did. So, that's great.

31:02 - 31:08
And now I'm fortunate enough to have a team where, where I can, where I can delegate freely

31:08 - 31:16
and, and, it's it's also a matter of trust of knowing each other and so on. So, that's that's great.

31:18 - 31:25
The other piece, and that's this in a way is it's 2 pieces connected in a way.

31:26 - 31:34
When I, became CPTO, another mentor, said to me, yeah.

31:34 - 31:38
Get used to not seeing the impact of your work, anymore, like, directly.

31:39 - 31:47
It will take months, years for you to actually realize if something worked well or did not.

31:48 - 31:50
And I was like, yeah. Yeah. Yeah. Of course.

31:51 - 31:53
And, there's a lot of truth to that.

31:54 - 32:01
This kind of self efficiency that you actually see I'm doing that and this is the impact of that.

32:02 - 32:05
When it's so diluted and so far away,

32:08 - 32:12
it can have the effect that you question if you actually have impact at all.

32:13 - 32:22
And then we're talking about often the imposter syndrome, in a way. So, that's real.

32:23 - 32:30
Especially, like, giving you're in a more or less generalist type of wall.

32:31 - 32:36
The impact of your actions can't be really measured, in the day to day.

32:37 - 32:43
And then, you really ask yourself the question, like, what the heck am I doing here? I like it.

32:43 - 32:45
That is is it really valuable?

32:47 - 32:54
And, I think one big realization over time was you're not alone with asking this question.

32:54 - 33:03
I talked to so many leaders, and basically everyone experienced these kind of, these kind of

33:04 - 33:10
phases where you really doubt, like, really having an impact what I'm doing.

33:11 - 33:16
And, also, like, can I actually do something?

33:16 - 33:18
Do I know something and these kind of things?

33:19 - 33:26
I think that's normal in a way, but normal doesn't mean that it's always easy to deal with.

33:28 - 33:31
Man, I I cannot agree more with that.

33:31 - 33:34
So it's so hard to get any kind of gratification.

33:34 - 33:41
And in most cases, those high leadership role roles, you get you are getting heated by so many

33:41 - 33:44
problems, and nobody is saying, like, great job.

33:45 - 33:47
And and, like, mostly are heated by the problems.

33:48 - 33:53
So plus the long term vision that you have and to have some kind of, like, idea about it. Yeah. Yeah.

33:53 - 33:55
I I fully agree with that.

33:55 - 33:59
It's so it's so difficult. It's so difficult.

34:00 - 34:07
And the last question that I wanted to ask you because you mentioned the audiobooks, you mentioned some conferences, some podcasts.

34:09 - 34:12
Maybe was there something particular helpful for you?

34:12 - 34:18
Or maybe you could share some podcast that or audiobooks that you are racing listened to recently. It would be great.

34:19 - 34:27
Yeah. Sure. I think that there's also one evergreen, I always, I always mention, in this kind

34:27 - 34:36
of question, coming from having been in different worlds in global organizations, I think, the

34:36 - 34:44
culture map, by Aaron Meyer is, is a foundation everyone, should have, read, in a way.

34:45 - 34:53
So it's really trying to make you understand that the way you function, the way, you've been

34:53 - 34:59
going up and, you've been accustomed to in in dealing with people and with conversations and

34:59 - 35:08
so on is not the way everyone else in the world is is is is is going up to.

35:09 - 35:15
And, on the website, there's also a cool test where you can, where you can basically test yourself

35:15 - 35:20
and, see, like, what kind of communication profile you have and and these kind of things.

35:20 - 35:28
So I've I found it really helpful to also understand why, you've been perceived in a in a in

35:28 - 35:36
in a way, and and, how certain interactions work or may not work in global organizations.

35:38 - 35:44
And then, lately, I've been reading the diary of a CEO.

35:47 - 35:54
Not that I wanna become CEO, today or tomorrow, but, I think the subtitle is something like,

35:54 - 35:56
laws of business and life.

35:57 - 36:06
And it's taking you through, I think, 30, 40, 50 kind of rules or, or laws, that are true for

36:06 - 36:13
life and for business and, and making you hopefully a better leader, if you understand them.

36:13 - 36:17
And there were a couple of refreshing things in there, that I liked.

36:17 - 36:23
And the last one maybe, totally different, category of book.

36:24 - 36:28
The limit is just me, from Jonas Eichmann.

36:29 - 36:34
He's a, adventure, extreme, sports person.

36:35 - 36:42
And, I mean, I'm considered considering myself sporty. I did milestones.

36:42 - 36:44
I did an iron man and these kind of things.

36:45 - 36:47
But this guy did an iron man around the world.

36:48 - 36:57
So 120 times the swimming leg, then 120 times the bike leg through Siberia, and so on, and then

36:57 - 37:06
120 times marathon, through Mexico in consecutive days, all of that. Right? In the pandemic.

37:07 - 37:09
And this book is about his journey.

37:10 - 37:13
You can also watch it on Netflix. That's easy easier.

37:14 - 37:20
But it's, really and it still can teach you a lot, about stuff.

37:21 - 37:29
Like, when it comes to having this project, Ironman around the world, it's too big to grasp, actually.

37:30 - 37:35
And he's talking a lot like what are the mental models, you actually need to make it still work

37:35 - 37:44
if you cycle day in minus 35 degrees with Iberia, with frozen foods and stuff like that. Right?

37:45 - 37:51
And, I think it just gives a different, perspective on a lot of things.

37:52 - 37:56
And also, even if, maybe this does not sound,

38:00 - 38:07
like fun all the time, he's really much about, yes, but this is what I want to do, and this

38:07 - 38:13
is why it's best to be here in this moment even if this moment right now is a little bit, interesting.

38:15 - 38:19
And I really like to get exposed to these kind of mental models I'm thinking.

38:20 - 38:23
Look. Nice one. I I will check it out for sure.

38:23 - 38:28
I think the sports is really helpful, in running the business or being a leader.

38:28 - 38:30
It's like to have the sport.

38:30 - 38:36
It's and and then to have the the sport that you like and you do a lot, it's really helpful for your mind.

38:37 - 38:40
So this, I'll I'll check it out.

38:41 - 38:47
So, David, thanks so thank you so much for all those insights and really interesting conversation.

38:47 - 38:51
I really appreciate your time and that you have shared all of that here.

38:53 - 38:54
Thank you for for everything.

38:55 - 38:57
Thank you for having me. It was a pleasure.

38:58 - 39:03
Follow Matt on LinkedIn and subscribe to the Better Tech Leadership newsletter.

Explore similar episodes

Ady Levy: Tech Leadership Chronicles: Challenges and Strategies

In this episode, Matt interviews Ady Levy about managing tech teams through uncertainty, leveraging skills from Ady’s military background, and the importance of data-driven approaches to resolve team disagreements. The episode also explores emotional management challenges, the thoughtful use of AI, and Ady’s recommended readings for balancing innovation and personal fulfillment.

listen now
Oleksandr Taran: From Idea to Implementation - Lessons in Startup Leadership Search

In this episode, Leszek interviews Oleksandr Taran, CTO of Frienton, who delves into his career journey from a software engineer to a startup co-founder and CTO. Taran emphasizes leveraging his math and computer science background in product development and highlights his current mission to help startups streamline business and financial administration. Oleksandr discusses the challenges of communicating complex technical concepts to business professionals, stressing the importance of translating these ideas into accessible language through analogies and clear explanations.

listen now
Alain Denzler: The Evolution of AI - A Journey Towards Human Interaction

In this episode, Matt interviews Alain Denzler, who is pioneering human-centric AI for sales with a focus on cultural nuances. Alain outlines the strategic shift from targeting large corporations to smaller, agile firms to foster creativity and innovation, and reflects on founding the company during a recession, facing financial challenges but still attracting investments from Silicon Valley figures by showing tangible progress.

listen now
Valeriy Zamaraiev: Navigating the Crypto Landscape - A CTO's Perspective on Web3 and Beyond

In this episode, Leszek and Valeriy Zamaraiev discuss the evolving landscape of Web3 and cryptocurrency networks, underscoring the importance of a results-oriented mindset. The conversation highlights strategies for learning and innovation in technology, such as internal hackathons and informal communications with startups. It discusses the challenges of scaling organizational structures, using YouTube and Google as examples, and addresses the complexities startups face during layoffs, emphasizing the balance between growth and operational stability.

listen now