TRANSCRIÇÃO 🔗
WEBVTT
00:00:00.000 --> 00:00:00.719
What is up, everyone?
00:00:00.800 --> 00:00:02.479
Welcome back to the Higher to Scale Podcast.
00:00:02.560 --> 00:00:06.799
I am your host, JP Forno, and today we have an amazing guest with us, Mark Wormgore.
00:00:06.959 --> 00:00:08.080
How are you doing this morning?
00:00:08.480 --> 00:00:09.199
Hi, JP.
00:00:09.359 --> 00:00:11.519
It's really nice to be here, doing absolutely fine.
00:00:11.679 --> 00:00:12.560
Psyched to be here.
00:00:12.640 --> 00:00:14.160
So thank you for having me.
00:00:14.560 --> 00:00:16.399
No, I'm excited about this episode.
00:00:16.559 --> 00:00:19.519
I think that you have a lot of experience that people can learn from.
00:00:19.760 --> 00:00:30.399
I always have enjoy having conversations with people that, you know, bring a different um sort of like perspective to how manage how teams should be managed.
00:00:30.480 --> 00:00:33.119
And you come from a very technical background.
00:00:33.280 --> 00:00:36.479
And I think that that sort of background we can learn a lot from.
00:00:36.560 --> 00:00:38.159
So I'm excited to have you on the show.
00:00:38.320 --> 00:00:40.000
I'm going to quickly introduce you.
00:00:40.320 --> 00:00:48.079
So Mark here has spent 30 years in technology, consulting for industry leaders and leading large global IT teams at JDE Pete's.
00:00:48.159 --> 00:00:58.880
Today, through his company, uh Tari, he coaches senior IT leaders to become better leaders because he believes leadership is a skill you can learn the same way you learn any other skill like development.
00:00:59.039 --> 00:01:12.719
Uh he hosts the CTO Compass podcast, uh, and he's also building Foranto, which is a place of software where coaches and their clients can see the same goals, notes, and actions so that the actual results of coaching are seeing the light of day.
00:01:12.799 --> 00:01:14.000
Uh so, Mark, welcome.
00:01:14.159 --> 00:01:15.519
So uh welcome for the show.
00:01:15.599 --> 00:01:17.200
I'm so excited uh to have you on.
00:01:17.519 --> 00:01:18.640
Thank you so much.
00:01:19.760 --> 00:01:21.840
So, why don't you give us a little bit of a background?
00:01:22.000 --> 00:01:29.439
You went from managing global IT teams to now doing what you're doing right now with the coaching, building a software uh yourself to help other coaches.
00:01:29.599 --> 00:01:32.079
Tell us a little bit about how that trajectory came to be.
00:01:32.400 --> 00:01:35.280
So I started my career really in in IT.
00:01:35.359 --> 00:01:36.560
Uh, I'm a tech guy.
00:01:36.640 --> 00:01:38.799
This was 30 years ago, as you said.
00:01:38.879 --> 00:01:43.120
Um, and I really started like doing all the basic stuff, systems engineering.
00:01:43.200 --> 00:01:47.040
I went from that to architecture to project management.
00:01:47.200 --> 00:01:56.959
I joined a consulting company, I joined Exchanger, um, and I stayed with Exchanger doing all these really cool projects for multinationals
Load full transcript
for about 10 years.
00:01:57.200 --> 00:02:05.920
After that, I joined JDE, which was then still JDE, later became JD Peats, and it's now merging actually with Curry Coffee in the US as well.
00:02:06.159 --> 00:02:07.920
A really big coffee company.
00:02:08.000 --> 00:02:12.800
Uh, and there I led their global IT operations team, IT operations and security.
00:02:12.879 --> 00:02:20.560
So that's everything from their service desk, their workplace, their application support, um, but also the security side, which was really important.
00:02:20.719 --> 00:02:22.960
I really loved that, did that for six years.
00:02:23.199 --> 00:02:27.599
And then at some point I thought this was nice, but it feels like it's getting repetitive.
00:02:27.680 --> 00:02:29.599
I'm doing the same thing that I did last year.
00:02:29.759 --> 00:02:32.000
We were doing the same transitions that we did before.
00:02:32.080 --> 00:02:35.599
It sort of got repetitive, and I thought, what am I going to do next?
00:02:35.680 --> 00:02:37.520
And that was really, I didn't know.
00:02:37.599 --> 00:02:43.199
I I had a career projection up until there, I just had no idea what I was going to do next.
00:02:43.360 --> 00:02:45.599
So I started talking to different people.
00:02:45.759 --> 00:02:47.120
I started talking to recruiters.
00:02:47.199 --> 00:02:49.199
Like, do I want to become CIO somewhere?
00:02:49.439 --> 00:02:50.879
What is it that I really want?
00:02:51.039 --> 00:02:55.919
And from all those discussions, I figured out I don't want to work for somebody else anymore.
00:02:56.080 --> 00:02:58.319
I actually want to go and do my own thing.
00:02:58.479 --> 00:03:02.400
If I fail miserably, that's fine, but then I can only play myself.
00:03:02.479 --> 00:03:04.639
If it becomes a success, really cool.
00:03:04.800 --> 00:03:07.199
And still I have myself to thanks for that.
00:03:07.360 --> 00:03:10.000
I don't want to go and follow somebody else's instructions anymore.
00:03:10.159 --> 00:03:18.639
So six years ago, I started my own company, and honestly, it's it's been quite a trajectory uh ever since finding out what it is that I want to do.
00:03:18.800 --> 00:03:23.039
I've changed a couple of times, and right now I love coaching.
00:03:23.120 --> 00:03:24.400
I love helping other people.
00:03:24.560 --> 00:03:28.319
I just love the leadership side of the house very, very much.
00:03:29.039 --> 00:03:34.719
The only thing there that I sort of missed is I'm also very technical myself still, and I love the technology.
00:03:34.879 --> 00:03:43.840
So, on top of that, that's why I'm also building this platform, just because I want to do something technical as well, because it's it's what I really like and love doing as well.
00:03:44.000 --> 00:03:46.240
So that's how I got to be here.
00:03:46.560 --> 00:03:49.599
And I think that's a a very, you know, common trajectory.
00:03:49.680 --> 00:03:57.599
I know that that was my same sort of um approach where you
come from you come from corporate, you get a chance to work with all these types of companies.
00:03:57.840 --> 00:04:03.199
And so you can you can always go back to that life, right?
00:04:03.280 --> 00:04:06.159
You always you develop these skills that nobody could take away from you.
00:04:06.319 --> 00:04:11.680
You've developed this experience, you have a network, but you want to do more with those types of things.
00:04:11.759 --> 00:04:14.639
And I think that a lot of the people that are listening are in that same path.
00:04:14.719 --> 00:04:19.600
It's like I came from like being very proficient inside of this company, but I want to build my own things.
00:04:19.920 --> 00:04:27.279
But where you were proficient in those things, there's a lot of things that they probably didn't teach you, like building your own infrastructure and all that stuff.
00:04:27.360 --> 00:04:31.920
And so uh I think that it's good that you you've had that sort of like trajectory.
00:04:32.000 --> 00:04:43.360
And what what I'd love to understand from you is I think that a lot of people are used to like the typical roles that they hire when they build a team, somebody that's admin, somebody that's operational, HR finance.
00:04:43.839 --> 00:04:48.480
But when it comes to like hiring technical teams, it's a little bit different.
00:04:48.639 --> 00:04:49.600
So, what do you think?
00:04:49.680 --> 00:04:58.800
How how is recruiting, training, and managing different when you're thinking about developers or very technical uh type of uh employees?
00:04:59.439 --> 00:05:04.000
So I think on the one side it is very much the same, and I'll get I'll get back to it later.
00:05:04.079 --> 00:05:13.360
But in technology, uh especially when you're hiring remotes, because right now I still have a team of developers remote uh as well working for me.
00:05:13.759 --> 00:05:16.800
And it's a different kind of personality that you're looking for.
00:05:16.959 --> 00:05:19.839
First, you need somebody that really has that experience.
00:05:20.000 --> 00:05:24.160
So I don't hire people that have one or two years of experience that have just gotten started.
00:05:24.240 --> 00:05:28.720
The people that I work with, the people in tech have five, ten years of experience.
00:05:28.879 --> 00:05:34.480
I hire mostly from the Philippines because I'm based in Europe and actually that works quite well in terms of time zones.
00:05:34.720 --> 00:05:39.920
A lot of these people have worked for an exchange there or an IBM there or a KPMG there.
00:05:40.160 --> 00:05:42.000
These are really good and skilled people.
00:05:42.079 --> 00:05:44.319
So I think I look for a couple of different things.
00:05:44.560 --> 00:05:46.399
First, technical experience.
00:05:46.560 --> 00:05:48.720
And this is just a CV test, of course.
00:05:48.959 --> 00:05:50.079
What have they actually done?
00:05:50.160 --> 00:05:51.680
What kind of projects have they worked on?
00:05:51.759 --> 00:05:53.839
Uh that's like my first selector.
00:05:54.160 --> 00:05:56.319
The second one is really personality.
00:05:56.480 --> 00:06:00.240
Um, because if you work remote with people, I trust is everything.
00:06:00.399 --> 00:06:04.319
So, really, I look for people that I can trust to do the work.
00:06:04.399 --> 00:06:09.839
So that I can actually trust if I give them an assignment, they're going to absolutely try and do their best.
00:06:10.000 --> 00:06:16.560
But also, if they don't understand it, they have to come back to me and ask, like, Mark, what is it that I didn't quite get it?
00:06:16.800 --> 00:06:19.920
And and can you help me understand what it really is that I need to do?
00:06:20.079 --> 00:06:25.519
And it's that balance between trying to do everything yourself, but also knowing when I ask for help.
00:06:25.600 --> 00:06:26.480
That's really important.
00:06:26.720 --> 00:06:30.800
Communication when you work remote is just so incredibly important.
00:06:31.040 --> 00:06:35.920
And honestly, not everyone in tech is as good at it as the next person.
00:06:36.160 --> 00:06:38.560
When you work remotely, I don't think that is an option.
00:06:38.639 --> 00:06:42.079
You really need somebody that has that communication skill.
00:06:42.160 --> 00:06:46.319
Um, doesn't matter where they're from, where they work, it's communication is everything.
00:06:46.560 --> 00:06:49.759
So I think those two, and of course, then I go through the whole hiring process.
00:06:49.839 --> 00:06:52.319
Um, we do interviews, we we test them out.
00:06:52.399 --> 00:06:53.920
There, there's a lot there as well.
00:06:54.160 --> 00:07:00.000
But I think it's it's those two the skills and the experience um and just the personality.
00:07:01.680 --> 00:07:04.959
Now, going back to like when you look at their experience, right?
00:07:05.040 --> 00:07:13.600
And when we're talking about somebody that's like technical, I think of if I were to hire a bookkeeper, I care a lot about how many years of experience they've been a bookkeeper for.
00:07:13.680 --> 00:07:16.399
Like they've done it for five years or seven years or 10 years.
00:07:16.560 --> 00:07:19.120
They have seen a lot of things happen in those years.
00:07:19.360 --> 00:07:25.040
But when I look at something like a developer, experience can sometimes be damaging, right?
00:07:25.120 --> 00:07:34.800
Because maybe they have um maybe they don't have up-to-date um tool proficiency, or maybe they haven't had they haven't unlearned how to do that.
00:07:35.040 --> 00:07:42.480
I have a buddy of mine that has a software business, and he's saying, like, man, claude code came and changed a lot of how we think about how we hire.
00:07:42.639 --> 00:07:46.800
Uh, we do want the experience, but we don't want people who are set in their ways.
00:07:47.040 --> 00:08:07.279
So, how do you, in a in a field that is ever changing, not like accounting or law or things like that or HR, those things usually are are less
likely to change, but something so dynamic as to what you're hiring for, how do you make sure that that experience is not counterintuitive or counterproductive to who you want to bring on board?
00:08:08.000 --> 00:08:14.639
I think in 2026, uh in software, everybody's trying to figure out how they work.
00:08:14.879 --> 00:08:20.959
I speak, like you said, I have my own podcast, the CTL Compass, and I speak to so many IT leaders on that podcast.
00:08:21.199 --> 00:08:26.399
Everybody is trying to figure out what they should be doing today, and nobody has the answers.
00:08:26.560 --> 00:08:31.439
So I think that's the good news because software development is changing so rapidly.
00:08:31.600 --> 00:08:40.559
We used to have teams of, well, agile teams, five to seven developers, they work together in a team, you give them a couple of uh user journeys, a couple of epics, they go and develop it.
00:08:40.639 --> 00:08:43.120
Two weeks later it's done, and we just move on like that.
00:08:43.360 --> 00:08:50.320
Right now, one developer can do so much work on their own using cloud that it's the whole world is changing.
00:08:50.399 --> 00:08:53.840
Um, and we're all trying to figure out together how to make that work.
00:08:54.080 --> 00:09:01.919
I think the challenge is, and and this isn't just with remote developers, it's even with a lot of the software developers that are in in the corpus right now.
00:09:02.159 --> 00:09:05.120
A lot of people just haven't had that experience yet.
00:09:05.279 --> 00:09:07.360
And I think that is really, really hard.
00:09:07.519 --> 00:09:16.720
And I think it's the people that we all want to hire uh are those software engineers that have had the two, three, four years experience developing software with cloud.
00:09:17.039 --> 00:09:21.279
Those people are really, really hard to find, and most of the time they're not looking for work.
00:09:21.360 --> 00:09:25.759
Um, so and and if they are, they're probably asking for very serious salaries.
00:09:25.919 --> 00:09:28.480
So it's really hard right now who to hire for.
00:09:28.639 --> 00:09:32.720
I think the best thing you can do right now is look for that technical experience.
00:09:32.879 --> 00:09:37.919
You need somebody that has that knowledge and not just that that coding knowledge, but also that architecture.
00:09:38.080 --> 00:09:39.919
How do we properly structure software?
00:09:40.000 --> 00:09:41.279
How do we build it up?
00:09:41.519 --> 00:09:54.159
The other part though is the ambition, aspiration is maybe the wrong word, but somebody that's really interested to learn and change their ways and really be dynamic and and go along with everything that's happening right now.
00:09:54.320 --> 00:09:58.639
Because it's going so fast, keeping up is is very, very difficult.
00:09:58.799 --> 00:10:01.759
So you really need somebody that that wants to do that.
00:10:01.919 --> 00:10:06.720
I mean, if somebody wants to, you can help them, you can guide them, and you can actually get it done together.
00:10:06.879 --> 00:10:10.320
But somebody needs to have that that aspiration, that ambition to do it.
00:10:10.480 --> 00:10:13.360
I think that's the critical thing to look for right now.
00:10:13.759 --> 00:10:15.519
And how do you look for that ambition?
00:10:15.679 --> 00:10:24.000
Is that something that you do during the recruiting process that will really get you, you know, like a high level of confidence that I know the answer to that question?
00:10:24.159 --> 00:10:29.200
Or is that more something that you start noticing on the first three months of this person working with you?
00:10:29.519 --> 00:10:32.639
I I try to do as much as I can in the recruitment process.
00:10:32.720 --> 00:10:39.440
I've been hiring people also in the corporate world for 20 years, and and I sort of learned the right and the wrong questions to ask.
00:10:39.759 --> 00:10:45.039
Culture for me is like one of the most important aspects that you hire for.
00:10:45.120 --> 00:10:47.039
And you can ask about culture, right?
00:10:47.120 --> 00:10:49.200
And don't ask the hypothetical questions.
00:10:49.360 --> 00:10:52.399
Don't ask people like if you were in this situation, what would you do?
00:10:52.559 --> 00:10:56.960
Or if you're this developer, I give you Claude, are you going to actually use it and do your best?
00:10:57.120 --> 00:10:58.480
Everybody's gonna say yes, right.
00:10:58.720 --> 00:10:59.759
Ask about the past.
00:10:59.919 --> 00:11:02.480
Like ask them about what I often do.
00:11:02.720 --> 00:11:10.639
Ask about a project where they really had to learn a lot of new skills just to fit into the project and meet the bar of the team that they were working in.
00:11:10.799 --> 00:11:11.840
How did they cope?
00:11:12.000 --> 00:11:12.720
How did they go?
00:11:12.879 --> 00:11:14.240
How did they deal with the manager?
00:11:14.399 --> 00:11:16.159
Did they make mistakes along the way?
00:11:16.399 --> 00:11:17.440
How did that happen?
00:11:17.600 --> 00:11:29.360
Ask them about past experiences where they actually had to really step up, raise the bar for themselves, and just step up and learn so much skills uh in a short time.
00:11:29.519 --> 00:11:34.720
If they can talk about that, they've done it before, they have that experience, they'll probably do it again.
00:11:34.879 --> 00:11:44.639
If they can't, and I see a lot of developers that have just been, I'd say, stuck in their ways and stuck in their teams, the ones that you talked about, they're not gonna give you those experiences.
00:11:44.799 --> 00:11:49.519
You can still try and hire them, but my experience, 80% of the time, it's gonna fail.
00:11:49.679 --> 00:11:54.799
If somebody has that in them, that ambition, that aspiration, they've done it before.
00:11:54.960 --> 00:11:58.559
If they've never done it before, it's very unlikely they're gonna show up with you.
00:11:59.840 --> 00:12:07.440
Now, I want to talk to you a
little bit about recruiting because you did mention this about how competitive it is to find people like that are that proficient.
00:12:07.600 --> 00:12:10.399
They're probably not looking, they're comfortable where they are.
00:12:10.639 --> 00:12:16.000
But then you see these dynamics of you know, massive layoffs in the developer world.
00:12:16.159 --> 00:12:24.320
And, you know, it it always seems like there's not a constant environment for like the talent in the tech space.
00:12:24.559 --> 00:12:36.399
And so how do you keep competitive um with available budgets that maybe you don't have unicorn VC-backed budgets, but you still have to develop a competent team?
00:12:36.559 --> 00:12:42.080
And then there's the remote, but then there's like the people who just got laid off from like a good company that you could probably sweep.
00:12:42.320 --> 00:12:53.120
Like, how does uh an IT leader, how should they think about their long-term recruitment strategy, given that this environment is so ever-changing?
00:12:54.000 --> 00:12:57.279
And I I've always believed this, and this was even before AI.
00:12:57.360 --> 00:13:15.919
Um, it's better to hire somebody that meets 75-80% of the skills required for the job, but has ambition and aspiration and really wants to learn and grow into that role, then to hire somebody that's done it before, that's going to be comfortable in the role because they're just not as energized.
00:13:16.000 --> 00:13:20.000
I mean, people want to learn, people want to grow, and those are the kind of people that you want.
00:13:20.159 --> 00:13:21.600
So I think hire for that.
00:13:21.759 --> 00:13:29.200
Hire people that maybe aren't there yet, that aren't like the perfect fit for the role you're hiring for, but that show that ambition to learn.
00:13:29.279 --> 00:13:35.440
I think that's the best way right now, and even before AI, that's always been my way to hire people.
00:13:36.159 --> 00:13:44.159
Yeah, I I've also known a I have a lot of friends um that have like tech companies um in the Southwest.
00:13:44.320 --> 00:13:57.120
And one of the the difficulties about hiring for those types of roles is that you're hiring with a lot of confidence on what your business can become eventually, right?
00:13:57.200 --> 00:14:03.039
It's not like you're hiring somebody from a company that's been here for a hundred years, we have our trajectory, whatever it is.
00:14:03.279 --> 00:14:08.879
Um how do you convince somebody to join your organization when you're like in a startup phase?
00:14:09.039 --> 00:14:12.480
Like we we convinced that this could work, but we don't know.
00:14:12.639 --> 00:14:16.080
We're like even maybe like pre-revenue, like so.
00:14:16.240 --> 00:14:21.200
How do you get somebody who's that talented to go in some place that is that uncertain?
00:14:22.399 --> 00:14:27.600
In my experience, so many technical people want to work for startups.
00:14:27.840 --> 00:14:32.240
I mean, I've worked for the corporates, um, and the money is good, right?
00:14:32.399 --> 00:14:41.440
There's a lot that's possible in those corporate, but everything, I mean, there's bureaucracy, it's going slow, and you definitely don't get to work on the cool stuff most of the time, right?
00:14:41.600 --> 00:14:46.720
If you want to work on the really cool stuff, um, startups are just the place to go.
00:14:46.879 --> 00:14:51.600
And there are so many people in the tech world that just want to work for those startups.
00:14:51.759 --> 00:14:57.200
So I don't even think it's that big a problem if you can sell that vision, right?
00:14:57.360 --> 00:15:12.080
If you sell that vision that you have for not what your company is today, because very few people want to join up, but you sell that vision of what your company is gonna be in three years and where you think it will be, believe it will be, thinking it's not good, where you believe it will be in three years.
00:15:12.240 --> 00:15:15.679
Um if you sell that vision, people will actually join.
00:15:15.759 --> 00:15:17.600
And I think it's a really good test of selling.
00:15:17.679 --> 00:15:23.279
If you know how to sell that vision, your customers are gonna buy, uh, but it's also a great way to hire people.
00:15:23.759 --> 00:15:26.639
I mean, and at the end of the day, corporate is not safe at all.
00:15:26.720 --> 00:15:32.080
In fact, like massive layoffs like happen at the highest levels as well.
00:15:32.320 --> 00:15:41.200
Um, so I think that the part of like this is a cre as as as much as we want to call this a technical role, it's a creative role at the end of the day.
00:15:41.279 --> 00:15:46.399
They're creating, and creators want to be in a place where they can create the coolest stuff.
00:15:46.480 --> 00:15:52.159
Uh, and if you can tell them on why this is a cool stuff, then you know it is a place to be.
00:15:52.320 --> 00:15:55.039
And I was talking about those software development with AI roles.
00:15:55.360 --> 00:15:59.840
Um, finding those kind of roles at corporates is actually quite difficult.
00:16:00.000 --> 00:16:08.159
Most of the corporates, they're running a pilot here, they're running a pilot there, but they haven't converted like their software development teams to be full on with AI.
00:16:08.240 --> 00:16:11.440
They're still like in the beginning of making that transition.
00:16:11.679 --> 00:16:14.720
Whereas these startups and these scale-ups, they're like they're like full on.
00:16:14.799 --> 00:16:19.120
They're moving at such incredible speed, and those are the coolest places to work for.
00:16:19.440 --> 00:16:22.639
Yeah, I always noticed that they're they're way slower.
00:16:22.799 --> 00:16:30.559
It's like the difference between a speeder and like a cruise ship and how like how much time, energy, and effort it takes to turn in a direction.
00:16:30.720 --> 00:16:41.519
I think that what most of these corporate places do is instead of like transitioning their team to
like fully BAI, they just buy a company that already has that team.
00:16:41.679 --> 00:16:46.320
Um, but um, but yeah, to your point, like it's it's it's not where the exciting stuff goes.
00:16:46.559 --> 00:16:54.879
I wanted to ask you something because again, I've I've been exposed to some uh teams, and I it there was this one team that really struck me.
00:16:54.960 --> 00:16:57.360
I don't know if you've ever seen the movie Oceans 11.
00:16:57.519 --> 00:16:58.240
Have you ever seen that?
00:16:58.639 --> 00:16:59.279
I have.
00:16:59.840 --> 00:17:20.240
So I was going into his office and he he has a software company and he had like the back end, the front end, the UIUX, the QA, and the project manager, like that unit of everybody being a specialist and like the way that they met, the way that they organized their work, the way you know, it it was a it seemed like a very high-performing, well-oiled machine.
00:17:20.319 --> 00:17:30.079
So I'd love to hear from you like, what do you think are some of the principles of how you manage those types of teams that other businesses can adopt, even if they don't have a technical team?
00:17:30.160 --> 00:17:46.079
Like if I have a services business or a restaurant or you know, um a roofing company, home services, how can I adopt some of the principles or what principles should I adopt from the way that those teams are managed to make my workload more efficient, I guess?
00:17:47.279 --> 00:17:52.400
I think most of these, and and this is like three years ago, because today the world is different.
00:17:52.480 --> 00:18:07.839
And I think those agile teams that you just described, they still sort of exist, but I think they're they're going out of existence very quickly because everybody's just using AI to develop and QA, the QA role, it still exists, but we're doing so much more QA with AI.
00:18:08.079 --> 00:18:10.480
The same for UX, but the same for software development.
00:18:11.440 --> 00:18:17.759
These five to seven people agile teams that we used to have, they're they're actually going the way of the dinosaur.
00:18:17.920 --> 00:18:22.160
But how that used to work is you have to have this team with the specialist.
00:18:22.400 --> 00:18:31.039
You have to have a senior engineer, um, two junior engineers, like the QA person, the UI UX person, and they really work together in these quick sprints, right?
00:18:31.119 --> 00:18:33.759
They work together in a one-week, a two-week sprint.
00:18:33.920 --> 00:18:38.160
They get a very fixed amount of work to get done in two weeks.
00:18:38.319 --> 00:18:42.400
And actually, it's not about the amount of work that they do, it's really about time box.
00:18:42.559 --> 00:18:48.079
So the interesting way of agile is that the limitation is not the scope.
00:18:48.240 --> 00:18:52.960
So basically, you get this is the amount of work, um, but what's fixed is the amount of time.
00:18:53.119 --> 00:19:05.440
So if you can't make it in two weeks, then there's gonna be some requirements that drop off, you're gonna do it a little less quality or maybe a little less of the work, but you are gonna make it and you're gonna get something delivered in two weeks.
00:19:05.599 --> 00:19:08.000
And that's really the interesting part of agile.
00:19:08.160 --> 00:19:10.079
I don't think that translates to everything.
00:19:10.160 --> 00:19:15.759
Um, like I wouldn't do that in a services business because people expect you to actually deliver that quality.
00:19:15.920 --> 00:19:20.960
And that's also why in other businesses it's actually the the time that shifts.
00:19:21.119 --> 00:19:26.000
If you can't make it in two weeks, then it's gonna be three weeks, um, as long as you actually deliver on quality.
00:19:26.319 --> 00:19:33.759
In IT, we used to have, and this is like 10, 20 years ago, every single project that we used to run in IT would go over time.
00:19:33.920 --> 00:19:39.279
There was never ever a project that, or almost never, I mean, I'm exaggerating, a project that would finish on time.
00:19:39.359 --> 00:19:42.400
If you said six months, it was almost certainly going to be nine months for the project.
00:19:42.480 --> 00:19:44.640
Or if you said nine months, it's gonna be a year and a half.
00:19:44.799 --> 00:19:45.920
That was a given in IT.
00:19:46.000 --> 00:19:49.599
Um, and budget would at least go over 25 or 50 percent.
00:19:49.839 --> 00:20:04.960
That's the reason that they introduced agile because it's so unpredictable what you're building, that you have to have a fixed measure of time in place, and that way you can actually sort of control what you're gonna get at the end and the budget you're gonna get and actually deliver value.
00:20:05.200 --> 00:20:07.440
And I think that's probably the most important lesson.
00:20:07.599 --> 00:20:10.480
The way that they're doing this is to deliver value early.
00:20:10.559 --> 00:20:17.759
So you're not gonna run a six-month or a nine-month program, and only all the way at the end you're gonna get the value of that nine-month program.
00:20:18.160 --> 00:20:32.559
Instead, you're cutting it up into all these very small pieces, the sprints, you're gonna do two-week sprints, you're actually going to deliver something that has real customer value already that you could even release into production, give to a customer to go and use.
00:20:32.720 --> 00:20:41.119
So cutting it up in those really small pieces that a customer can already see and use and enjoy, instead of just these really lengthy projects.
00:20:41.200 --> 00:20:48.640
And I do think that's something, I mean, it doesn't apply to every business, but I think in a lot of different businesses, that is something you could really apply.
00:20:49.039 --> 00:20:54.799
I think so too, because I think, you know, on one side you have things like buyer's remorse, right?
00:20:54.880 --> 00:21:01.519
Like I made a decision I with, you know, my signature and my dollars that I'm gonna
work with this person.
00:21:01.759 --> 00:21:10.160
And then maybe the delivery of said service takes three weeks or four, then in those three weeks, the client is always on this uncertainty period.
00:21:10.400 --> 00:21:16.079
But I think that the the metric, and I learned this from Hormosy, is time to value.
00:21:16.319 --> 00:21:20.400
How soon after I made a decision as a client do I get something of value?
00:21:20.640 --> 00:21:22.319
And I think any business can do that.
00:21:22.400 --> 00:21:27.839
I we used to run into this issue because we we help people with virtual assistants and and remote work.
00:21:28.160 --> 00:21:31.359
Um, but we did a very in-depth recruiting process.
00:21:31.440 --> 00:21:33.920
So it couldn't be like a two-day type of thing.
00:21:34.000 --> 00:21:37.599
It took us three weeks to find like amazing candidates.
00:21:37.759 --> 00:21:42.240
But then they were like these three weeks were like, I felt the uncertainty that our clients were feeling.
00:21:42.400 --> 00:21:51.279
So we did like an onboarding box, we did a kickoff call, we started helping them with their 30, 60, 90 day plan and training plans while they were getting ready to receive this person.
00:21:51.519 --> 00:21:55.599
And that helped a lot because you're getting these like little deliverables and people can learn from that.
00:21:55.680 --> 00:21:59.839
But the second thing that you mentioned also is this this idea of like the partnership.
00:22:00.079 --> 00:22:05.839
Parkinson's Law, I don't know if you see it a lot, but if you give somebody like three weeks, they're gonna take the full three weeks to complete it.
00:22:06.000 --> 00:22:17.200
But if you give yourself a target to shoot at and it's in a long enough time frame or short enough time frame, um then you have always a target to hit and you're pushing to hit it and you're hitting it as a team.
00:22:17.359 --> 00:22:19.759
Um so I think that those things are insightful.
00:22:19.839 --> 00:22:22.960
But I'm curious, like what is what do those teams look like today then?
00:22:23.119 --> 00:22:29.839
If if that was like the way of the past, what what does a tech team look like and how do they manage their work today?
00:22:30.319 --> 00:22:35.519
I think everybody's trying to actually invent how that works, uh, and and nobody really has the answer.
00:22:35.599 --> 00:22:36.960
The teams are becoming a lot smaller.
00:22:37.119 --> 00:22:46.079
So we used to have seven people with we used to have the senior engineer, the two juniors, the senior QA, the junior QA, like a UI UX designer, uh a scrum master.
00:22:46.240 --> 00:22:50.160
I think that team has actually shrunk to maybe three people.
00:22:50.319 --> 00:22:58.720
You have now the software engineer, and this is in most cases, this is one guy using AI and actually delivering so much value.
00:22:58.880 --> 00:23:05.839
Um, they can go one well between 5x and 10x of like what a single software engineer used to be able to
do.
00:23:06.000 --> 00:23:07.920
Um, UI UX still exists.
00:23:08.079 --> 00:23:15.119
You can use um you can use AI to generate screens, to generate designs, uh, to generate text for screens.
00:23:15.359 --> 00:23:22.559
Honestly, you need to review everything because it's going to be otherwise you're gonna get AI slot web designs and AI slot text that we see everywhere.
00:23:22.720 --> 00:23:23.519
You can't do that.
00:23:23.599 --> 00:23:25.359
You need UI UX designers.
00:23:25.680 --> 00:23:26.799
And also QA.
00:23:26.880 --> 00:23:35.200
I mean, we can automate so much testing with AI, and still you need a person to actually go and walk to it because you can't.
00:23:35.680 --> 00:23:40.319
I mean, if it goes to a customer, an outside customer, it has to be really, really that good.
00:23:40.480 --> 00:23:42.480
So you still need these last two people.
00:23:42.720 --> 00:23:44.799
But the team is just that much smaller.
00:23:44.880 --> 00:23:46.319
It's like three, four people.
00:23:46.559 --> 00:23:55.039
The other thing that's changing is that we used to have this IT process where we spent so much time at the front end deciding what we're gonna build.
00:23:55.119 --> 00:24:04.480
Uh like we have all these customer interviews, we do all the designs up front, we look at this entire backlog and we we say for the next month we're gonna build just these three or four things.
00:24:04.640 --> 00:24:06.720
We built them and we're gonna release them to the customer.
00:24:06.960 --> 00:24:07.440
That's it.
00:24:07.599 --> 00:24:09.200
That whole paradigm has changed.
00:24:09.359 --> 00:24:15.279
So instead, we're now actually because software development goes that much faster, we can build all of it.
00:24:15.359 --> 00:24:24.000
So instead of just spending all the time at the front end, we can just build everything, we can release it to the customers and get their feedback or measure their feedback.
00:24:24.160 --> 00:24:25.119
Are they actually using it?
00:24:25.279 --> 00:24:26.160
Are they not using it?
00:24:26.319 --> 00:24:28.000
If they don't use the feature, that's fine.
00:24:28.079 --> 00:24:29.279
We measure it, we kill it.
00:24:29.440 --> 00:24:32.160
If they do use it, great, we can go and improve it.
00:24:32.400 --> 00:24:41.440
So, where it used to be this big funnel of ideas that went into the funnel that we can deliver the production, right now it's almost like a pipeline.
00:24:41.519 --> 00:24:53.519
You can almost every idea you can just move straight through that development pipeline and get it into that customer view and then see if it works, see if they like it, see if they enjoy it, if they use it, and if not, just kill it.
00:24:53.599 --> 00:24:58.000
It's a whole different way of developing software, but it's what's happening right now.
00:24:58.880 --> 00:25:13.200
And so I think that a lot of challenges that people are are facing when they're transitioning from the old way of doing things to the new way of doing things, like you just described, is that AI is making people dumber, for the lack of a better term, right?
00:25:13.279 --> 00:25:18.000
Or it's reducing critical thinking, is reducing the technical capabilities of people.
00:25:18.160 --> 00:25:25.519
Um, and it's not bad for people who have that experience and now they're like super maxing charging with AI.
00:25:25.759 --> 00:25:35.279
I think, you know, like before, the advantage was with the newbies, the people coming out of college that knew the most recent stuff that can manage the tools better.
00:25:35.440 --> 00:25:42.640
But now that advantage is shifted to the seniors, the people that have the context, the experience, and now they're just super charged with this capability.
00:25:42.960 --> 00:25:47.759
For the younger employees, it's it's it's a proxy for critical thinking.
00:25:47.839 --> 00:25:49.119
So they're no longer making decisions.
00:25:49.200 --> 00:25:55.839
They're no longer so that's why like you get AI slob or in the or in copywriting, you get content that looks the same.
00:25:56.000 --> 00:26:02.319
Or in service delivery, you like you get all these things that are like now leading towards averageness.
00:26:02.480 --> 00:26:16.880
And so as a leader, how do you how are you training your your people that you're coaching to implement these technologies, but still make sure that it's not a crutch and that people still are developing their their critical thinking, their technical capabilities alongside with it?
00:26:17.279 --> 00:26:19.599
And I think it's what you said at the end, right?
00:26:19.680 --> 00:26:22.559
It's it's we have to motivate people to keep doing that.
00:26:22.720 --> 00:26:24.160
Um, nobody likes AI slop.
00:26:24.319 --> 00:26:25.039
I don't, you don't.
00:26:25.119 --> 00:26:26.720
I mean, we see it around us everywhere.
00:26:26.799 --> 00:26:28.960
Uh, I see the AI developed websites.
00:26:29.039 --> 00:26:34.640
I can tell in like two seconds if somebody developed a website using AI, or was there proper design behind it?
00:26:34.720 --> 00:26:38.880
And the same with any text that's written, you can just see it everywhere, and everybody knows.
00:26:39.039 --> 00:26:44.880
And still, I get all these interesting sales messages in my inbox, which were personalized using AI.
00:26:44.960 --> 00:26:46.400
I see all the sales tools as well.
00:26:46.559 --> 00:26:51.440
It doesn't work because everybody understands where that message comes from and how it was generated.
00:26:51.599 --> 00:27:00.559
So I think the way to stand out today, if you really want to be different, it is working on understanding what high quality really looks like.
00:27:00.720 --> 00:27:03.839
And a lot of the boring work that we used to have still stays.
00:27:04.000 --> 00:27:10.240
I'm developing, like I said, I'm developing this um coaching tool uh or or this SaaS platform for coaches.
00:27:10.480 --> 00:27:23.920
I spend so much of my time just
looking at screens, um, looking at the text on the screens, like at the designs, making sure that it's absolutely perfect because AI generation is is okay, but it's not good enough.
00:27:24.240 --> 00:27:27.039
And we really need to raise the bar for quality.
00:27:27.200 --> 00:27:28.960
I think that's just the more important thing.
00:27:29.039 --> 00:27:36.160
And um, as leaders, we need to make sure that the people that work for us um raise their bar for what good looks like as well.
00:27:36.319 --> 00:27:49.119
Because with AI, we can actually do better, we can generate better things, we can deliver better quality, but it needs us to review it, to check it, to challenge the AI, to do better, to review it and correct it as well.
00:27:49.359 --> 00:27:50.960
That's the only way that it's gonna work.
00:27:51.039 --> 00:27:53.039
And we need to build our critical thinking.
00:27:54.799 --> 00:27:57.839
Now, I'd love to hear about like coaching.
00:27:58.000 --> 00:28:07.359
Um, because as a leader, you're I think this is such a meta example because you you coach people like you coach other leaders to coach somebody else later on.
00:28:07.519 --> 00:28:11.119
So I think it's such a like an underrated uh skill set.
00:28:11.200 --> 00:28:12.720
I see it with my clients all the time.
00:28:12.799 --> 00:28:20.720
We get them an amazing assistant and they're they never are able to influence behavior or coach through uh challenges.
00:28:20.960 --> 00:28:33.599
It's easy to manage someone when things are going great with the business and everything's moving, but like, so I'd love to understand from what you've learned from your coaching days, um, and specifically how are you coaching leaders?
00:28:34.000 --> 00:28:43.279
How do you make it so that because you're not the one executing the work, how do you help people execute through words that you're saying or the approach that you're having?
00:28:43.440 --> 00:28:48.079
Um, tell us a little bit about your philosophy in coaching and how can people adopt those principles?
00:28:48.400 --> 00:28:53.920
So the nice thing about coaching is that I work with people who actually want to do better.
00:28:54.079 --> 00:28:56.160
Um, and I think, right?
00:28:56.240 --> 00:29:02.960
So that's the nice thing of being a coach is the people that I start to work with have already decided that they want to do better.
00:29:03.039 --> 00:29:06.880
It's not that they're not good enough, it's that they just want to raise that bar for themselves.
00:29:07.039 --> 00:29:09.759
So they're inspired, they're motivated to do better.
00:29:09.920 --> 00:29:14.960
Um, and actually they're paying money to work with the coach to get better.
00:29:15.119 --> 00:29:16.799
So they really have that motivation.
00:29:16.880 --> 00:29:20.000
And I think that that's also what I said at the beginning in hiring.
00:29:20.160 --> 00:29:22.559
You need somebody that has aspiration and ambition.
00:29:22.720 --> 00:29:32.079
If that's not there, if they don't buy into the vision, if they don't have that ambition to grow and be better, I think it's like pulling a dead horse, it's not gonna happen.
00:29:32.160 --> 00:29:35.039
You're not gonna make that change uh and that shift isn't gonna happen.
00:29:35.119 --> 00:29:38.799
And perhaps it's just better to say goodbyes and let that person go.
00:29:38.880 --> 00:29:40.880
And that's why I always hire for ambition.
00:29:41.039 --> 00:29:43.119
So when I coach, that's a starting point.
00:29:43.200 --> 00:29:47.440
And I always work with people, beginning, we said, like, what is that vision?
00:29:47.599 --> 00:29:52.240
Where do you actually want to get to in in six months, a year, three years?
00:29:52.400 --> 00:29:54.559
I mean, we only work together for six or nine months.
00:29:54.720 --> 00:30:02.559
But if you actually understand as a CIO, as a CTO, as a leader, where you want to go to, the rest becomes a lot easier.
00:30:02.720 --> 00:30:06.400
So from there, like your end vision, where do you want to be?
00:30:06.640 --> 00:30:10.559
Also with the world changing, what is it that you actually want to achieve in three years?
00:30:10.720 --> 00:30:13.359
We work on a short plan, like six, nine months.
00:30:13.519 --> 00:30:16.079
What is it that you're going to do to make that happen?
00:30:16.240 --> 00:30:19.759
Um, and this is already, everybody can do this on their own, right?
00:30:19.839 --> 00:30:28.480
But it helps so much to do that with somebody else, to have a sparring partner, to look at it together, to be challenged, to raise the bar far enough, to not make it too easy on yourself.
00:30:28.799 --> 00:30:30.000
I think that really helps.
00:30:30.720 --> 00:30:38.000
After that, these coaching sessions are really about, well, half of it, and and that's I mean, half of it is accountability, right?
00:30:38.160 --> 00:30:49.920
Just the idea that you have a coach that you need to go and speak to in three weeks to tell if you've actually done what you said you would do, if you've actually implemented all those improvements, those changes, it makes a big difference.
00:30:50.079 --> 00:30:59.920
And it sounds stupid because you can do the same with your spouse, with your partner, with somebody else at work, but having that accountability partner is worth an incredible deal.
00:31:00.079 --> 00:31:03.759
And then every session we talk about what is your bottleneck right now?
00:31:03.839 --> 00:31:04.720
What's holding you back?
00:31:04.880 --> 00:31:05.839
Why haven't you done it?
00:31:05.920 --> 00:31:13.279
And a lot of times it's oh, but I got dragband into the operational stuff, I got this issue in this one project that I was working on.
00:31:13.519 --> 00:31:19.039
I have this other issue with, I don't know, my co-founder, but with somebody else that has been holding me back.
00:31:19.200 --> 00:31:28.319
And so every time it is how do we go and take those bottlenecks out so that you can go
and actually do what it is that you need to do to go where you want to go.
00:31:28.480 --> 00:31:30.880
You've set that goal for yourself, you need to get there.
00:31:31.200 --> 00:31:32.480
Stop holding yourself back.
00:31:32.640 --> 00:31:35.119
And we all fall into these traps.
00:31:35.519 --> 00:31:37.920
Um, and and it happens in IT so much.
00:31:38.079 --> 00:31:42.880
All of these people, these CIOs, even the CIOs of multi-billion companies, these are technical people.
00:31:43.039 --> 00:31:46.319
They started their career as a software engineer and infrastructure engineer.
00:31:46.400 --> 00:31:47.359
They know the stuff.
00:31:47.599 --> 00:31:57.839
It is so easy to get dragged back into projects, into programs, into the next big outage that happens, that it's gonna you can let it kill your week easily.
00:31:58.000 --> 00:32:01.039
And that's the trap that so many people fall into.
00:32:01.279 --> 00:32:06.640
Is yeah, like for entrepreneurs, it's like I'm working on the business versus in the business.
00:32:06.799 --> 00:32:08.720
For leaders, it's the exact same thing.
00:32:08.799 --> 00:32:12.160
Like, am I working on on the strategy, on the stakeholder management?
00:32:12.240 --> 00:32:17.279
Am I working with the board to really, really get our IT, our technology to the next level?
00:32:17.599 --> 00:32:23.200
Or do I get dragged back into working in the business on the operational stuff, the projects, the programs?
00:32:23.440 --> 00:32:29.519
So it's it's not too different from entrepreneurs, but it's the same traps that everybody falls into.
00:32:29.920 --> 00:32:32.000
You know, but it's it's very transferable.
00:32:32.079 --> 00:32:35.920
Like everything that you said from first of all, get the right person on the bus.
00:32:36.000 --> 00:32:41.119
You you know, you're not gonna be uh having success if they don't want to put their part in.
00:32:41.200 --> 00:32:46.559
So find somebody that wants to get coach, uh, identify what their vision is, what their roadblocks is, create a plan.
00:32:46.640 --> 00:32:48.640
And then after you have the plan, is those two things.
00:32:48.799 --> 00:32:53.519
You hold them accountable, uh, you know, call them on their bullshit if they're giving you bullshit.
00:32:53.599 --> 00:32:56.160
But the other thing is also helping them remove roadblocks, right?
00:32:56.240 --> 00:32:58.000
It's like, oh, I've seen this before.
00:32:58.240 --> 00:33:00.640
This is how we did it, this is how you could do it.
00:33:00.799 --> 00:33:19.039
Um, and then to your point, I mean, like conceptually, this is not rocket science, it's not open heart surgery, but it is kind of like when you're going to the gym where you do way more when you have a spotter, somebody that lifts you up for the last repetition, gets you, you know, scraping the last bit of energy that you can have.
00:33:19.200 --> 00:33:32.079
Uh, and also it's kind of like boxing in the sense that you have blind spots when you're fighting, like, but a coach can see like more uh can see your self-talk, can see how you're making the wrong decisions.
00:33:32.240 --> 00:33:38.640
And I think that those surgical uh interventions that you guys could do as a coach is what really gets results.
00:33:38.720 --> 00:33:42.559
Uh, not just, oh, here's the plan, go execute and tell me about it, you know.
00:33:43.279 --> 00:33:43.759
I agree.
00:33:43.920 --> 00:33:51.519
And to add to that's um what you see of a lot of CTO CIOs, but a lot of I think the same is true for founders, you're in that position by yourself.
00:33:51.680 --> 00:33:57.759
So a CIO, there's not five other CIOs at the company that he can actually go or she can actually go and speak to.
00:33:57.839 --> 00:34:02.319
Um, Ishii is there by themselves and they're leading that IT organization.
00:34:02.480 --> 00:34:10.559
They can't really go and talk about these important decisions, reorganizations, by the discussion with their team, because I mean that's not the right place.
00:34:10.639 --> 00:34:14.239
And if they have concerns or worries, they can't go talk to the team members.
00:34:14.400 --> 00:34:19.119
They can't go and talk to their boss, who've often did the CEO or the COO or the CFO.
00:34:19.199 --> 00:34:21.360
Like, who are they actually go and talk to?
00:34:21.519 --> 00:34:28.000
And it really helps to have somebody there that's done it before, that has been, has been there, has done it, has seen it all.
00:34:28.159 --> 00:34:34.159
Like an outside independence um sparring partner is really, really valuable if you're in that seat.
00:34:34.880 --> 00:34:41.119
Now let's talk a little bit about international teams because you've had great success with international teams as we spoke about it before.
00:34:41.280 --> 00:34:54.400
And you mentioned that, yeah, like if you're having a remote employee, you have to over-index more on culture, personality, ambition because you just don't have that face-to-face, let's call it lubricant for the relationship, I guess.
00:34:54.639 --> 00:35:03.119
Um, but it's so important because you are no longer limited between the 25-mile radius of where you have your headquarters to hire from.
00:35:03.280 --> 00:35:06.000
You can now open up your doors for the rest of the world.
00:35:06.239 --> 00:35:19.280
Um, so besides like bringing that culture, like how do you what sort of lessons did you learn when managing an international team uh that are different than managing like an in-person one?
00:35:19.519 --> 00:35:24.800
Um, a lot of people that listen to the show have international team members and they struggle with the management portion of it.
00:35:24.880 --> 00:35:30.239
Like, how can I make sure to be an effective leader even if we're outside the the same borders?
00:35:30.400 --> 00:35:34.880
What have you learned from building international teams that you could probably tell these types of people?
00:35:35.519 --> 00:35:41.039
I mean, I've also led
in-person teams, and that is, it is, I would say, so easy, right?
00:35:41.199 --> 00:35:44.719
Um, looking back at it, because you actually get to see 40 hours a week.
00:35:44.800 --> 00:35:46.079
What is somebody working on?
00:35:46.159 --> 00:36:01.840
Um, you get to meet them for lunch, you have coffee together, um, you take them out for dinner once in a while or for drinks, and you get to know them, um, you get to know them on a personal level, and it is yeah, I'm exaggerating, but it's really easy to manage somebody, a person that's sitting next to you in the same office.
00:36:02.239 --> 00:36:06.639
It is so much harder to manage somebody than somewhere else uh for different reasons, right?
00:36:06.800 --> 00:36:09.840
You don't get to see their work, uh how they work.
00:36:09.920 --> 00:36:18.159
So you get to see the end results, and that can be after a day, it can be after three days, it can be after a week, but you don't know how much time it actually took uh to deliver all.
00:36:18.239 --> 00:36:20.239
So trust is really, really important.
00:36:21.519 --> 00:36:25.840
And and you can only do that by uh staring on outputs, right?
00:36:25.920 --> 00:36:32.239
If you're in an office, you can check what they're doing, you can have all these intermediate check-ins, you can walk by their desk and just check on where they're going.
00:36:32.320 --> 00:36:35.119
You can do the same up Slack, of course, but it is so much harder.
00:36:35.360 --> 00:36:41.039
So, really, it's it's steering on outputs in IT, um, and especially in agile developments.
00:36:41.199 --> 00:36:42.239
We've done so much of that.
00:36:42.400 --> 00:36:50.079
We have all these prints, we can see when people check in codes, we can see the PRs that they do, we can actually check output because it's very not tangible.
00:36:50.159 --> 00:36:54.800
Code isn't tangible, but you can actually see what they've done, what they've worked on, and how long they took to get it done.
00:36:54.880 --> 00:36:56.559
So that's that's one.
00:36:56.719 --> 00:36:59.199
The other part is really the relationship.
00:36:59.360 --> 00:37:03.760
Um, if you're in an office, it's really easy to build a personal relationship with somebody.
00:37:03.840 --> 00:37:07.360
Um, like I said, you can go out for drinks, for lunch, you can have coffees, whatever.
00:37:07.519 --> 00:37:08.559
It's it's easy.
00:37:08.719 --> 00:37:10.880
If you work remote, we tend to forget that.
00:37:10.960 --> 00:37:12.480
I mean, we've all seen it during COVID.
00:37:12.639 --> 00:37:16.880
You spend this time on on Google Meet or on Teams or on Zoom or whatever, and that's it.
00:37:16.960 --> 00:37:25.119
You talk for an hour, you talk about the project, you talk about the status, you talk about the next steps, and you hang up and you go and have coffee at your own house.
00:37:25.280 --> 00:37:28.320
Um, there isn't that that casual conversation.
00:37:28.480 --> 00:37:35.119
So I think the most important
thing that you can do and should do is bring the team closer together as people.
00:37:36.000 --> 00:37:42.960
So it's it's ideal if you can actually bring the team on site, uh, even if it's a week amount or a week a year.
00:37:43.039 --> 00:37:43.440
Yeah, right.
00:37:43.519 --> 00:37:44.559
But that's fly them out.
00:37:44.960 --> 00:37:54.719
Yeah, just once uh get to meet or or fly out there, get to meet the people in person, see them in person, just take them to dinner, just just build the relationships, right?
00:37:54.880 --> 00:37:55.679
Just do that once.
00:37:55.840 --> 00:37:59.199
If you can't do that, um do the virtual version of that.
00:37:59.440 --> 00:38:03.840
So one of the founders that I know, uh, he's a CTO, he actually works with his team.
00:38:03.920 --> 00:38:05.840
They're building a health company.
00:38:06.000 --> 00:38:08.960
They actually have these Monday morning conversations.
00:38:09.119 --> 00:38:23.199
Uh, they're not talking about work, they're talking about the weekends, they're talking about all their exercising, they actually do like 10, 15 minutes workouts um together over Google Meeter Teams because that's that's their company, right?
00:38:23.280 --> 00:38:31.440
But that's that is a really good way to just step away from the work a little bit, get to know each other, and talk about everything that is not work.
00:38:31.519 --> 00:38:32.559
And that is just so important.
00:38:32.719 --> 00:38:37.440
Get to know who's their family, where are they from, because it doesn't matter where people live, right?
00:38:37.519 --> 00:38:42.800
I work with teams in the Philippines, but I've worked with teams from from Australia to Brazil, almost everywhere.
00:38:43.039 --> 00:38:44.400
People aren't all that different.
00:38:44.559 --> 00:38:47.119
They all have the same, they have the same family concerns.
00:38:47.199 --> 00:38:51.119
Uh, they have kids that go to school, that do well or don't do well, right?
00:38:51.280 --> 00:38:55.760
Everybody has sort of the same life that we all have together.
00:38:55.840 --> 00:39:05.119
Um, and I think there's so much overlap there, and there's so much more connection and we we just get to talk about the non-work stuff, the personal stuff, or politics, or or anything like that.
00:39:05.280 --> 00:39:09.119
There's so much that we can talk about just building a personal connection.
00:39:09.440 --> 00:39:11.119
But you need those spaces, right?
00:39:11.199 --> 00:39:13.920
And uh, I think I I agree with you.
00:39:14.000 --> 00:39:28.320
I see it here too, like um the clients that make the effort to fly people over there, uh, they come back and it's easier to get stuff done because there's relationships, you can give feedback better because you know somebody cares about your life and not just like the work that you're producing.
00:39:28.719 --> 00:39:31.679
Um and also with the trust, I think you mentioned it.
00:39:31.760 --> 00:39:37.920
Do you treat it as a sort of you're giving more trust as you see results?
00:39:38.000 --> 00:39:46.800
Because you say that they're counterbalanced with results, or you do you default to trust unless they break it, you you add a little bit more manage view or oversight.
00:39:47.039 --> 00:39:53.199
How do you how do you make sure that you have like a decent trust level without like putting the business at risk?
00:39:53.519 --> 00:39:54.480
I guess.
00:39:54.719 --> 00:40:00.079
I mean, as you as you hire a new employee, uh you can't just trust them and let them go, right?
00:40:00.320 --> 00:40:04.800
You have to get them started on the work, you have to make sure that they understand what they're doing, what they're working on.
00:40:04.960 --> 00:40:07.039
So it's it's a gradual process anyway.
00:40:07.119 --> 00:40:14.719
You start with all the introduction sessions with like small assignments, and the assignments can grow over time, become more complex, become bigger.
00:40:14.960 --> 00:40:17.599
So I think it's not ideal to trust.
00:40:17.760 --> 00:40:24.480
Um, but I also want to make sure that the onboarding, the introduction, that getting them up to speed is properly done as well.
00:40:24.639 --> 00:40:34.079
And as part of that process, you very quickly learn if you can trust someone, if they're really gonna take that work, get it done, ask you the right questions along the way, or not.
00:40:34.320 --> 00:40:42.559
Um, so I think it's always there's always, I mean, it's good to do a paid trial up front, but that's usually like a day, two days of work.
00:40:43.519 --> 00:40:49.119
After that, I think in the first month, often after two, three weeks, you know, this is really gonna work out.
00:40:49.199 --> 00:40:50.400
I love working with this person.
00:40:50.559 --> 00:40:54.000
He or she is doing so well picking stuff up or not.
00:40:54.239 --> 00:41:01.840
Um, I've seen too many examples where people are on the, I don't think this is gonna work, and just keep dragging it out for three or six months.
00:41:02.559 --> 00:41:06.480
It's if it doesn't work in the first couple of weeks, you can try and turn it around.
00:41:06.639 --> 00:41:08.800
The chances of that are really, really slim.
00:41:08.960 --> 00:41:15.840
So just I would say just bite the bullet and just say take a loss and just try hiring better or somebody else.
00:41:16.079 --> 00:41:20.480
You'll learn very quickly if somebody is really meeting up to your expectations or not.
00:41:20.639 --> 00:41:23.519
And the first month is a really good period to figure that out.
00:41:24.480 --> 00:41:33.840
Yeah, as we're closing this episode, I always like to ask this question because you've talked a lot about your experience as a leader, or in your case, as a as a coach, and you've coached you know several different people.
00:41:34.000 --> 00:41:44.559
But I'd love to hear from you like who is a coach or a leader that left an imprint on you as you were coming up and maybe an insight
that you still hold on to today that you could share with the listeners.
00:41:45.599 --> 00:41:58.719
I've had, I've been very, very lucky in my my career that I've always had a really good, um, and it's different over time, but I've had really good coaches in my career, um, sometimes provided by my employer as well.
00:41:58.880 --> 00:42:08.400
I've had mentors that have given me some of the best examples uh or have really told me, showed me what to look like, or what what good can really look like.
00:42:08.559 --> 00:42:10.559
So I've been really fortunate.
00:42:10.719 --> 00:42:29.360
Um I think one thing that somebody really, and and I've been challenged as well by by some of my managers and my leaders, I think, and this is a quote that I got from somebody, one of my mentors, that I just love and I repeat um to almost everyone, it's a very simple sentence, and it's you get what you accept.
00:42:29.599 --> 00:42:33.280
It's like those four words I have never forgotten from him.
00:42:33.519 --> 00:42:35.119
Um basically it's very simple.
00:42:35.280 --> 00:42:44.079
If you have a team, you have somebody working for you, they do something that you don't quite like or that you think you should course correct, but you let it go, you've just made that acceptable.
00:42:44.159 --> 00:42:46.079
That behavior has just become acceptable.
00:42:46.159 --> 00:42:58.639
So every time that somebody does something that, or a team does something, or a team delivers something that is not maybe the right quality or not to where you would expect it to be, and you let it go, it's just become acceptable.
00:42:58.800 --> 00:43:07.440
Um, and I, in my career, like 10, 15 years ago, I was not the best person at giving that feedback right then and there on the spot.
00:43:07.519 --> 00:43:12.320
And that actually leads to people working for you that aren't meeting your bar.
00:43:12.400 --> 00:43:14.559
And that's a very frustrating position to be in.
00:43:14.639 --> 00:43:17.920
So that's the one that I've taken to heart and that I will never forget.
00:43:18.079 --> 00:43:19.519
You get what you accept.
00:43:19.840 --> 00:43:20.480
I love that.
00:43:20.639 --> 00:43:25.920
You always fall back to your level of your standards, and um, it's your job as a leader to set that bar.
00:43:26.000 --> 00:43:27.519
Um, so I love that quote.
00:43:27.760 --> 00:43:32.880
Uh so awesome, Martin, thank you so much for being in this um podcast episode with us.
00:43:33.039 --> 00:43:35.280
Where can people find you if they want to learn more about you?
00:43:35.360 --> 00:43:36.559
What do you have going on?
00:43:36.719 --> 00:43:41.760
Um, and then yeah, if someone wants to continue learning from you beyond this episode, uh, how can they do that?
00:43:42.079 --> 00:43:44.960
So if you want to reach out to me personally, best place is LinkedIn.
00:43:45.039 --> 00:43:46.400
Uh look for Mark One Court.
00:43:46.480 --> 00:43:47.440
There's there's one of me.
00:43:47.519 --> 00:43:53.199
Um, I think there's one of me, but anyway, you'll find out the one that's the uh the leadership coach and then the CTO.
00:43:53.360 --> 00:43:57.599
The other place is Tyree, uh the company where I do all this executive coaching.
00:43:57.679 --> 00:44:01.360
It's T-I-R-I.co, uh Tyree.co.
00:44:01.840 --> 00:44:04.559
Um, it's uh where I do all of my work.
00:44:05.360 --> 00:44:08.239
Yeah, and we'll be putting all of that in the show notes.
00:44:08.400 --> 00:44:12.000
And is the is the software company available uh for people?
00:44:12.159 --> 00:44:13.920
I have a lot of people who are coaches and stuff.
00:44:14.000 --> 00:44:15.119
Is that available as well?
00:44:15.199 --> 00:44:17.920
Or or is that just in the wraps and you're gonna launch it soon?
00:44:18.239 --> 00:44:19.920
It is out there, it's available.
00:44:20.079 --> 00:44:30.079
I'm not I'm working on a second release because right now it's the back end only, and it's the back end for managing the sessions and uh booking sessions and all the minutes and the sessions.
00:44:30.320 --> 00:44:36.480
I think growth is an incredibly important part for coach as well, finding new customers, that's the part that we're building right now.
00:44:36.639 --> 00:44:40.880
I actually expect to have it released uh in the next week or in two weeks.
00:44:40.960 --> 00:44:43.280
It's gonna be a big change version two coming out.
00:44:43.440 --> 00:44:44.800
Uh faronto.com.
00:44:45.039 --> 00:44:49.920
Firew actually means lighthouse because I believe coaches are lighthouses for their customers.
00:44:50.079 --> 00:44:54.400
Faronto.com um and the new release should be out in a week or two.
00:44:54.880 --> 00:45:04.559
So if anybody listening has a coaching uh business or capacity, uh, you're just gonna have to like follow Mark and uh see about the releases.
00:45:04.719 --> 00:45:06.320
But I I strongly recommend it.
00:45:06.400 --> 00:45:10.960
Uh that it's fixing an important problem in coaching that you probably are already facing.
00:45:11.119 --> 00:45:15.840
So uh I'll put all the information of Mark uh at the bottom of the show notes.
00:45:16.000 --> 00:45:17.760
Thank you so much, Mark, for being part of this episode.
00:45:17.840 --> 00:45:22.320
And for the listeners, thank you so much for tuning in to another episode of the Higher to Scale Podcast.