March 29, 2026

cout, Strike, Repeat: Why Five Is the Magic Team Number

cout, Strike, Repeat: Why Five Is the Magic Team Number
Apple Podcasts podcast player iconSpotify podcast player iconRSS Feed podcast player icon
Apple Podcasts podcast player iconSpotify podcast player iconRSS Feed podcast player icon

Atlassian just cut 1,600 people — including the teams building their own AI. What does that signal for the rest of us? Stephen and Lauren dig into the hidden coordination tax bleeding most teams dry, why the number five keeps showing up as the sweet spot for high-performing teams, and the emerging scout/strike model that's letting small groups outrun large ones. Plus: uncomfortable leadership truths, and what you can actually do about all of this today.

00:00 Intro

01:35 Coordination Tax

06:15 Team Math

09:40 Magic Five

14:45 Scout & Strike

21:10 Leadership

28:33 Wrap Up

WEBVTT

00:00:00.080 --> 00:00:05.599
Atlassian just laid off sixteen hundred people, including some of the teams that were building their own AI.

00:00:06.080 --> 00:00:10.560
They cut the people closest to this technology they said they couldn't survive without.

00:00:10.880 --> 00:00:15.279
What might that mean for the teams that you're in right now, and what can you do about it?

00:00:15.599 --> 00:00:19.199
I'm Steven, and this is the AI Transition, and with me as always, Lauren.

00:00:19.760 --> 00:00:21.600
Hey Stephen, this is a good one.

00:00:22.000 --> 00:00:23.519
Let's dig into today.

00:00:24.079 --> 00:00:24.719
Yes, yes.

00:00:25.199 --> 00:00:29.519
I'm quite quite close to the bone, and we we know people who've been involved with this as well.

00:00:29.679 --> 00:00:32.880
Um and we're we're seeing this happening in other organizations too.

00:00:32.960 --> 00:00:35.359
So this is a very relevant one.

00:00:36.320 --> 00:00:43.280
We're gonna dive into quite a few interesting things that I think um will be affecting and/or touching on pretty much everyone listening in a moment.

00:00:43.439 --> 00:00:49.920
So uh the hidden tax that's been kind of bleeding organizations' drive for decades, tax, the coordination tax.

00:00:50.079 --> 00:00:50.880
We'll dig into that.

00:00:51.039 --> 00:00:55.200
Um, why the number five keeps showing up as the magic number?

00:00:55.600 --> 00:00:57.359
We're going a bit woo-woo, Stephen.

00:00:57.600 --> 00:00:57.920
Magical.

00:00:58.479 --> 00:00:59.200
No, I'm kidding.

00:00:59.359 --> 00:01:08.959
Um some new archetypes that are appearing in organizations, some new, I guess, mindsets or squad structures that we're seeing emerge, um, some uncomfortable leadership conversations.

00:01:09.040 --> 00:01:13.200
And then as always, we try to give you some practical tips that you can take away.

00:01:13.599 --> 00:01:20.799
Something practical after after this, after we after we scare the bejesus out of most people, then we then we come back and say, hey, look, there is something you can do.

00:01:20.959 --> 00:01:23.200
Maybe just a small thing, but there's still something that we can do.

00:01:25.200 --> 00:01:26.159
So let's dive in.

00:01:26.239 --> 00:01:28.799
So we uh look, you know, don't we love the word tax?

00:01:29.760 --> 00:01:31.599
Um, especially these tired ages.

00:01:31.760 --> 00:01:37.599
So the coordination tax, this is where, you know, uh we've got all the overheads that we we deal with with our day-to-day work.

00:01:37.680 --> 00:01:46.239
So this is meeting preparation, you know, documenting decisions, cross-team ticketing, you know, where we've got all these meetings, we're trying to get all the knowledge.

00:01:46.319 --> 00:01:58.560
Um and some of the interesting ta stats around this one, again, it's not a new problem, but it's growing, is that we've got 60% of our time being spent on coordinating the work and then only about 40% available for execution.

00:01:59.120 --> 00:02:03.599
Can can can I just put some health healthy skepticism on those numbers, right?

00:02:03.680 --> 00:02:07.200
And there's been lots of um lots of different studies that have been showing this.

00:02:07.280 --> 00:02:09.280
I think it's a lot more than 60% of the city.

00:02:09.520 --> 00:02:10.719
I was gonna say, what do you reckon?

00:02:10.879 --> 00:02:12.560
I actually think it's more like 80.

00:02:12.879 --> 00:02:13.199
Yeah.

00:02:13.439 --> 00:02:14.800
But look, look, look seriously.

00:02:14.960 --> 00:02:34.000
But when when you talk to most people, what they end up doing most of the day, it's it's the meetings, it's the chatting to people, it's the sending messages, it's replying to emails, it's having right and all of that, nearly all of that, is all based on coordination about who's doing what, when and and what's going on.

00:02:34.159 --> 00:02:39.680
Um actually doing the stuff, that's really a small part of the for most people's jobs.

00:02:40.080 --> 00:02:40.719
It really is.

00:02:40.879 --> 00:02:50.960
And you know, particularly, dare I say, for people like you and I, where we're trying to help teams, you know, work more efficiently, that's that biggest challenge of breaking that habit of I just need a meeting, I need to talk about this, I need to bring people together.

00:02:51.120 --> 00:02:57.280
Um, and part of the challenge we've got with AI now is that you've got much more output without any of the structural change, right?

00:02:57.439 --> 00:03:09.840
So if we know that even since uh good old 2020, that this meeting load, and it's just a constant pattern for all of us, is increasingly, you know, growing significantly as these teams get bigger, you're losing that shared context.

00:03:09.919 --> 00:03:12.000
And now you've got output growing as well.

00:03:12.159 --> 00:03:15.840
And the rise of um this new phrase of the agentic tar pit.

00:03:16.159 --> 00:03:17.280
Quite like that one, to be honest.

00:03:18.080 --> 00:03:19.280
It's quite a visual, isn't it?

00:03:19.680 --> 00:03:25.120
Because I I I do feel myself um kind of stuck in that tar pit quite a lot these days.

00:03:25.680 --> 00:03:29.039
Beat getting pulled deeper into the tar.

00:03:29.199 --> 00:03:29.280
Yeah.

00:03:29.520 --> 00:03:34.800
You know, where you've got all this activity, not so much the outcomes, like as people starting to figure out how to use these tools.

00:03:34.879 --> 00:03:39.759
And, you know, I've run my meeting with my, you know, AI and tracking all my transcription.

00:03:39.840 --> 00:03:41.280
Now I've got to update all these notes.

00:03:41.360 --> 00:03:48.719
And so you've got this, you know, smart more output and it's reducing some of that manual, but still it's not helping you to coordinate the work.

00:03:48.800 --> 00:03:50.560
You've still got that coordination cost.

00:03:51.039 --> 00:03:58.879
What I'm seeing in a lot of teams these days is that, you know, and these aren't kind of frontier teams that are kind of you know agentic in AI first.

00:03:58.960 --> 00:04:04.319
You know, they're you know kind of like you're standard teams within within within large organizations.

00:04:04.800 --> 00:04:11.919
Any AI usage so far just now is mainly been around to simplify some of the manual tasks that they're already doing.

00:04:12.159 --> 00:04:17.759
So, for example, I'm using Copilot to make a summary of a meeting, right?

00:04:17.839 --> 00:04:34.240
Uh and so instead of taking notes yourself, people are using that and then cutting and pasting it that into a file somewhere, which means that while teams are getting bigger, we're just automating some of that documentation part of it, but not overly fixing a lot of the problems.

00:04:34.639 --> 00:04:37.759
Yeah, are we actually optimizing any anything at the end of the day?

00:04:37.920 --> 00:04:43.519
We're creating a lot more content, but are we actually thinking about how we need to interact with each other more efficiently?

00:04:43.920 --> 00:04:44.160
Yeah.

00:04:44.240 --> 00:04:56.079
Well, whereas teams that are kind of been using this a a bit more, it's not just about automating or AI fying or identifying or whatever words you you want to use there of the existing processes.

00:04:56.160 --> 00:05:00.000
It's actually looking at those and then saying, well, actually, do we need to do that?

00:05:00.319 --> 00:05:05.519
Can we not have, you know, the bots take that part of it, that part of the coordination?

00:05:05.680 --> 00:05:07.040
Do we really need to be doing this?

00:05:07.199 --> 00:05:21.199
One of the other things I I would throw in here is that I've just seen teams getting larger and larger, particularly since the pandemic and since the vast majority of corporate teams are meeting in Microsoft Teams online.

00:05:21.839 --> 00:05:26.959
There's no restriction now about how many people you can have a team in order to physically get in a room anymore.

00:05:27.600 --> 00:05:30.639
So you can have dozens and dozens of people now.

00:05:30.879 --> 00:05:32.000
And that's quite common.

00:05:32.480 --> 00:05:40.319
And we know that we're gonna start to talk about this this uh number of five shortly, but we know the more people we add into that mix, the more lines of communication that you've got.

00:05:40.560 --> 00:05:42.480
And you're creating more and more of that output.

00:05:42.560 --> 00:05:44.639
And how do you actually bring it together to optimize it?

00:05:44.720 --> 00:05:49.040
So hence this agentic tar pit, because it's kind of pulling you in.

00:05:49.199 --> 00:05:58.079
So we're not yet seeing those um uh I guess benefits of introducing these tools if we're not looking at the broader picture of how we actually coordinate.

00:05:58.480 --> 00:06:05.360
Well, why don't we kind of move on to that and that kind of that mathematics of the number five thing we see popping up quite a lot?

00:06:05.519 --> 00:06:15.600
But before we get to the number five, um, what I've been seeing, as I was saying in the previous section there, is just the number of people that are getting added into teams just now.

00:06:15.839 --> 00:06:23.920
So the so the overheads that go is when you've got eight people, twelve people, fifteen people, twenty-five people, right?

00:06:24.160 --> 00:06:32.879
The communication paths that trying to coordinate all of them, if you try and draw that out in a diagram of where the communication is going, it's completely crazy.

00:06:33.199 --> 00:06:33.839
Oh, it is.

00:06:33.920 --> 00:06:38.000
And like just for the simple maths, like if you've got five, it's 10 pathways, right?

00:06:38.240 --> 00:06:42.160
Once you hit 20, it's rapidly growing to around 190, 200.

00:06:42.480 --> 00:06:44.720
You're hitting 50, we're talking 1200.

00:06:44.879 --> 00:06:49.439
And you and I regularly work in, I'm working, well, maybe we will keep names out of it.

00:06:49.600 --> 00:06:51.360
But where people, how big is this team getting?

00:06:51.439 --> 00:06:52.959
Oh, yeah, it's gonna get up to about 50.

00:06:53.120 --> 00:06:58.560
And you're like, okay, well, maybe it's time to scale into some streams and teach, oh, I'm not sure about that.

00:06:58.720 --> 00:07:00.079
Like, we want to make sure.

00:07:00.319 --> 00:07:07.199
So once you think about how inefficient hundred lines of communications, which is crazy.

00:07:07.600 --> 00:07:13.279
So it's either overwhelmed by the number of passive communications or there's just no communication going on.

00:07:13.439 --> 00:07:26.079
And what I mean by that is so there's a there was a couple of meetings I that I attended um earlier this week and went on, and there was, I think there was 18 people in this one team who were uh uh having this discussion.

00:07:26.160 --> 00:07:29.519
But the reality was there was three people in that meeting having the discussion.

00:07:29.680 --> 00:07:30.560
Only three, right?

00:07:30.720 --> 00:07:36.399
The other, the other 14, 15 of them were cameras off, not really saying anything.

00:07:36.560 --> 00:07:40.879
I'm just not part of any conversation, probably not even listening.

00:07:41.040 --> 00:07:49.040
Um when we say multitasking, it means they're reading the paper or they're you know arranging their calendar to pick up their child later that day or whatever.

00:07:49.680 --> 00:07:50.000
That's true.

00:07:50.079 --> 00:07:53.360
And or look at bears trying to be less any cool, but let's be real.

00:07:53.439 --> 00:08:05.680
And look, we're all juggling a lot at the moment, but often where you've got these overloaded organizations with specialists that are being pulled from pillar to post, some of them are actually doing their other project, they're keeping one ear in the conversation and really how effective can you be?

00:08:06.000 --> 00:08:27.360
But what can change, and what we've seen with some uh both both ourselves and also reading a lot more about what's happening out in the wider world, as the capabilities of AI improves and what you can do on your own and the scale of what you can do improves, having that that many people in a team, you probably don't need as many now.

00:08:27.519 --> 00:08:40.000
Um and you know, I'll I'll share some personal anecdotes in in in in a minute of you know how I've found that the the kind of work that I'm able to do now on my own, which normally would have had like three, four, five people.

00:08:40.799 --> 00:08:45.200
It's it's you can do a lot more now if you're using these tools, right?

00:08:45.279 --> 00:08:57.120
Which means that you probably only need four or five you know generalists who are able to span that whole knowledge base for whatever it is that you're doing, but they've got those agents working with them.

00:08:57.200 --> 00:09:03.039
And so now the communication is yes, among those individual agents, but that's you know easier because it's computer to computer.

00:09:03.279 --> 00:09:06.399
You've got four or five people that you're coordinating now.

00:09:06.960 --> 00:09:08.799
And that starts to change things.

00:09:09.120 --> 00:09:09.600
Oh, exactly.

00:09:09.679 --> 00:09:12.559
And you know, where did that number five come from, Stephen?

00:09:12.799 --> 00:09:15.039
Um is it five fingers on a hand?

00:09:15.120 --> 00:09:15.440
Is that it?

00:09:15.679 --> 00:09:16.960
Yeah, I mean totally, totally.

00:09:17.120 --> 00:09:19.039
I know I've done a harsh left turn there.

00:09:19.120 --> 00:09:27.360
But when we think about this number five, it's pretty much how many um, I guess, meaningful communications and connections you can make with a group of people at once.

00:09:27.600 --> 00:09:31.440
So when you start to go out wildly, you can't have that connection anymore.

00:09:31.600 --> 00:09:34.000
So we're starting to see organizations use this.

00:09:34.159 --> 00:09:35.759
Okay, we're more efficient with these tools now.

00:09:35.840 --> 00:09:37.600
We use it as an excuse to let people go.

00:09:37.840 --> 00:09:41.919
But really, the ambition could be there to actually, you know, deliver more value.

00:09:42.080 --> 00:09:43.360
Let's do more strategy work.

00:09:43.440 --> 00:09:50.799
What can we actually do when we unlock our people and and pull them into those smaller team sizes, which isn't really a new concept, right?

00:09:51.679 --> 00:10:01.600
Yeah, well, I do what was coming up from there as you were saying this, you know, and I'm really showing my age here, but I remember when Facebook first came out, like you know, 15, 20 years ago, you know, et cetera.

00:10:02.639 --> 00:10:08.480
And right, and uh, and at the time I remember people saying, How many friends do you have?

00:10:09.519 --> 00:10:14.320
And I would say, I think I've got about three or four, maybe five at a push.

00:10:14.399 --> 00:10:16.879
And they're going, Oh, I've got 163.

00:10:17.039 --> 00:10:18.240
And it's like, what?

00:10:18.399 --> 00:10:18.879
No, you don't.

00:10:19.200 --> 00:10:20.480
They're not your real friends.

00:10:20.559 --> 00:10:22.159
So not your friends.

00:10:22.399 --> 00:10:30.240
Right, but that is a that's a good illustration of I I do have four or five good friends, and and I can't cognitively cope with any more of that.

00:10:30.480 --> 00:10:37.360
Um, so if there's anyone out there who actually wants to be my friend just now, actually, all the places are are filled at this moment in time.

00:10:37.600 --> 00:10:47.039
Um, but it that's just human human nature that there's only so much for most people um of you know what what you can cope with.

00:10:47.440 --> 00:10:49.440
And it's the five kind of people that you've got in your mind.

00:10:49.519 --> 00:10:51.600
Like it was funny when we were getting ready for this.

00:10:51.679 --> 00:10:55.759
I was thinking, oh, you really like those close interpersonal relationships you've got.

00:10:55.840 --> 00:11:01.519
And when you think about forming the chemistry of a team, so you're kind of looking for for those natural handoffs and connections.

00:11:01.600 --> 00:11:09.120
So if you're over overwhelming them with all these 1200 odd interactions, how can you possibly get that nice rhythm and flow and connection?

00:11:09.279 --> 00:11:13.279
So we're going back to, you know, it was a bit of a classic and we whisper the word adja.

00:11:13.840 --> 00:11:20.799
Um team structures where we talk about the concept of a perfect size team being, you know, seven plus or minus two, five or nine.

00:11:21.279 --> 00:11:27.759
And um, I was interested to know uh uh the fun bit of trivia here, and maybe everyone else uh, you know, knew this.

00:11:27.919 --> 00:11:30.000
The the phrase two pizza teams.

00:11:30.159 --> 00:11:32.320
Do you know where that came from, Stephen?

00:11:32.960 --> 00:11:42.559
I saw it was it was Google or Facebook or something like that, but basically um the the amount of food that you needed in order to feed feed a development team.

00:11:42.879 --> 00:11:46.240
Jeffrey Bezos, my friend, he coined this phrase apparently.

00:11:48.159 --> 00:11:49.360
Yes, and an off-site, right?

00:11:49.519 --> 00:11:51.759
Where he's like, oh, you know, we teams need to communicate more.

00:11:51.840 --> 00:11:55.120
And Bezos stood up and said, no, communication is terrible.

00:11:55.519 --> 00:12:01.039
Many wanted to talk about, you know, decentralizing a company where small teams innovate independently.

00:12:01.279 --> 00:12:03.600
So that's where that two pizza phrase came from.

00:12:03.919 --> 00:12:08.080
You just need a team um, you know, small enough that you can feed them with two pizzas.

00:12:08.240 --> 00:12:15.759
So this is a concept that's been around for a little while, but now we can really see how we can actually empower these teams of tools.

00:12:16.399 --> 00:12:17.759
Are they family-sized pizzas?

00:12:17.840 --> 00:12:20.000
I mean, are we we're talking the big ones here, do you think?

00:12:20.320 --> 00:12:21.679
Uh surely, right?

00:12:21.759 --> 00:12:23.200
With thin crust, would you go to thin crust?

00:12:23.360 --> 00:12:24.240
You would you you would think so.

00:12:24.320 --> 00:12:29.120
Yeah, it would have to it'd have to be the big ones because like two small ones, I don't think would I don't think that would do it.

00:12:29.759 --> 00:12:30.080
You're right.

00:12:30.159 --> 00:12:32.320
You'd be pretty you're gonna eat some appetizers there.

00:12:32.720 --> 00:12:33.679
Some garlic bread.

00:12:33.919 --> 00:12:35.840
Two pizzas garley bread.

00:12:36.399 --> 00:12:37.759
We've really gone ridiculous.

00:12:39.360 --> 00:12:40.879
Getting back on track.

00:12:41.440 --> 00:12:48.480
That's what we're seeing as well, is that these smaller teams, because you can do more within these teams now.

00:12:48.720 --> 00:12:57.039
My experience over the last couple of weeks, I mean, we w we've been developing some systems that in the past would have maybe taken, I don't know, three, six months to pull together.

00:12:57.200 --> 00:13:04.080
That we've literally been able to do part-time in a week or two, using kind of you know the latest tools within Claude and Cloud Code and co-working.

00:13:04.240 --> 00:13:06.159
Uh, and that's been quite jarring to be honest.

00:13:06.639 --> 00:13:19.039
There's been times where we've been creating some of that, and I was remembering back 10, 15, 20 years ago when what we were doing there would literally be taking a whole weekend or you know, that's two weeks worth of work and the rest of it.

00:13:19.200 --> 00:13:23.200
And it was a it was a couple of sentences of vibe coding and suddenly it was there.

00:13:23.360 --> 00:13:25.919
I and and that's a bit shocking, to be honest.

00:13:26.159 --> 00:13:31.679
That that's and when you think about the different kinds of skills that used to be used, and that's what this really is about, right?

00:13:31.759 --> 00:13:39.919
You're reducing those external dependencies, you can do more yourself with these tools, you know, cover more of that surface area versus pulling in these separate specialists.

00:13:40.000 --> 00:13:46.000
So that's what it is quite mind-blowing when you actually get inside these tools and see what you can do just personally yourself.

00:13:46.399 --> 00:13:52.399
So it's it's not about kind of replacing the humans, it's actually just being, you know, uh delivering more value.

00:13:52.480 --> 00:13:53.840
We'll use the V-word here.

00:13:54.320 --> 00:13:55.759
Uh with these smaller teams.

00:13:56.480 --> 00:13:57.919
Yes, and quicker as well.

00:13:58.159 --> 00:14:03.679
So you you came up with you're finding some analogies around different ways of structuring these teams.

00:14:04.080 --> 00:14:08.559
Yeah, well that's what I found interesting too, because we're we're still like we're talking about some of these older concepts here.

00:14:08.720 --> 00:14:17.360
You've got the two pizza teams, we've just already talked about how you've got this uh coordination tax across the top, because you've still got many of these smaller teams.

00:14:17.440 --> 00:14:30.320
But we're starting to see these um uh new phrases coming out where we've got these concepts of scouts and strike teams, which I don't know, Stephen, did this made me think a little bit about we've all heard tiger teams before, right?

00:14:30.559 --> 00:14:34.320
Um the the tiger team thing doesn't really work for me, but okay, okay.

00:14:34.799 --> 00:14:35.360
But I don't know.

00:14:35.440 --> 00:14:45.360
But it feels a bit like that, but where you would, you know, someone who came along and go, We needed, we need a tiger team for this, and we'll get our five or six best people, um, you know, pull them out of a team and that other team doesn't matter what they're doing now.

00:14:45.600 --> 00:14:47.440
We've got our guns in this strike team.

00:14:47.600 --> 00:14:48.879
So, well, tiger team.

00:14:48.960 --> 00:14:52.480
Anyway, I've already I've segue, but you know, when you start to see these new phrases.

00:14:52.559 --> 00:15:08.080
Um, when we talk about these scout and strike teams, we're talking about the whole concept of exploration versus execution, you know, good old, you know, investing in some good quality discovery, which some organizations are hesitant to invest in because it's like, hang on, we just we know what the problem is, let's just fix it.

00:15:08.240 --> 00:15:19.919
So you've got this concept of these two operating modes, a scout and a strike team, which is pretty much as the name suggests, you've got a scout, but this time they're running solo and they've got a full AI toolkit, right?

00:15:20.000 --> 00:15:21.679
So they don't have to coordinate with anyone.

00:15:21.759 --> 00:15:27.440
Um, and they're gonna produce, you know, get those initial findings and produce, you know, something viable to work with.

00:15:27.519 --> 00:15:31.279
And then you've got the output coming back into the strike team.

00:15:31.440 --> 00:15:38.799
So what you can do is if you're fully kidding someone out, and then you're your leading person running out and scouting the environment, it's quite a good analogy.

00:15:39.200 --> 00:15:43.360
Um, they can do this within days and months with the right toolkit, right?

00:15:43.440 --> 00:15:44.799
Because they haven't got dependencies.

00:15:44.879 --> 00:15:49.360
They've got, you know, they're unto themselves, they've got a clear field to run.

00:15:49.600 --> 00:15:53.759
So when you've got that nice cheap, that's an interesting word, isn't it?

00:15:53.919 --> 00:15:59.919
Cheap exploration, you're gonna get more experiments and you know, more um volume to actually look at.

00:16:00.000 --> 00:16:02.879
And your cost actually reduces dramatically.

00:16:02.960 --> 00:16:07.440
And like you haven't got a team of people exploring for weeks and months.

00:16:07.840 --> 00:16:10.960
And that's that's what came up for me as you as you were talking through that there.

00:16:11.120 --> 00:16:17.759
You know, because previous language that we've used a lot, um, is it kind of common within the industry, you'd be doing a design spike, right?

00:16:17.840 --> 00:16:19.840
So you you you'd be off to doing a spike.

00:16:20.000 --> 00:16:22.399
But it's usually for a whole team.

00:16:22.559 --> 00:16:25.039
We'll take a sprint, as in you know, a couple of weeks.

00:16:25.279 --> 00:16:32.399
They will go off and do a design sprint for for a couple of weeks and and spike that and do a proof of concept and blah blah.

00:16:32.639 --> 00:16:37.600
But you do have you know a number of people doing it over, you know, probably a couple of weeks.

00:16:37.759 --> 00:16:38.799
Whereas this is different.

00:16:38.960 --> 00:16:45.919
This is somebody who's going off for a couple of days to scout ahead but with a full toolkit, as you were saying.

00:16:46.399 --> 00:16:46.720
Exactly.

00:16:46.799 --> 00:16:54.960
And if you think about the effort that's often involved where you're doing any kind of design or discovery work, you might be interviewing dozens of people, pulling all that doco back.

00:16:55.039 --> 00:17:01.600
But if you've got a fully catered um solo scout out there, the amount that can actually pull in using these tools is quite incredible.

00:17:01.840 --> 00:17:06.559
Again, it doesn't reduce the need to interact with humans, but it just helps you to cut through some of that processing.

00:17:06.720 --> 00:17:15.200
So the idea is you've got your scout running out, bringing it back with their findings, and then handing this over or working with the strike team, Stephen.

00:17:15.359 --> 00:17:16.640
The strike team.

00:17:16.880 --> 00:17:19.440
Um, this is where the number five reappears, right?

00:17:19.519 --> 00:17:29.440
So you've got your five uh generalists, which is, you know, uh when you think about generalists, sometimes we think, oh, hang on, we're not experts, but that's not the idea here, right?

00:17:29.519 --> 00:17:39.039
You've now got this really strong AI fluency and you can scale the outcomes from your scout because they've got those skills that you can actually drive that value on.

00:17:39.680 --> 00:17:45.920
So the whole idea being that you can actually scale your output using these tools and automation.

00:17:46.160 --> 00:17:49.440
So you can reduce the risk of loss.

00:17:49.759 --> 00:17:54.880
Oh, like look, look the face and the arms across what's coming up for you, Stephen, what's coming up?

00:17:56.000 --> 00:17:57.599
So I've got a question for you.

00:17:57.759 --> 00:18:07.839
So are you are you more are you more of a scout or are you more of a strike team person, or are you standing beside the sidelines, you know, coaching the scouts and the strike?

00:18:08.240 --> 00:18:09.039
Where would you like to be?

00:18:09.359 --> 00:18:10.960
Oh, it's an interesting one, isn't it?

00:18:11.119 --> 00:18:12.480
Look, I don't mind a bit of scouting.

00:18:12.559 --> 00:18:18.400
It's nice when you can kind of dig into a problem, like it probably leans into my old analyst um days.

00:18:18.559 --> 00:18:21.200
But you can also see if you're part of that strike team too.

00:18:21.279 --> 00:18:25.920
I'm thinking of the chemistry, like in a band of people, dare I say, where you're all coming together.

00:18:26.480 --> 00:18:28.160
The band of the solar singer, right?

00:18:28.400 --> 00:18:29.119
Okay, yeah.

00:18:29.359 --> 00:18:31.839
Um, but I think it would also, you know, be very exciting.

00:18:32.000 --> 00:18:34.559
Look at me, I'm like, all of the things everywhere all at once.

00:18:34.799 --> 00:18:43.279
It would be also really exciting if you can, you know, work with the team in these structures to see what you can really do in such a short period of time.

00:18:43.839 --> 00:18:46.400
I think for me it's overwhelmingly the scout.

00:18:46.559 --> 00:18:47.519
I would want to be the scout.

00:18:47.839 --> 00:18:48.799
Shock, Stephen.

00:18:49.119 --> 00:18:49.839
You shocked?

00:18:50.160 --> 00:18:50.640
Shocked.

00:18:50.880 --> 00:18:52.319
It's not like you at all.

00:18:52.880 --> 00:19:02.240
That that idea of of just on your own being able to go off and investigate and explore and play with stuff and pull it together and and then come back.

00:19:02.480 --> 00:19:13.920
Is this an introvert-extrovert type thing that you're going to be, you know, you're sending the scouts off or a bit more of the kind of introvert talking to their AI buddies and you know leaving the extroverts to have the party with the pizzas behind?

00:19:14.079 --> 00:19:14.400
I don't know.

00:19:14.640 --> 00:19:15.759
I mean, I think it could be.

00:19:15.839 --> 00:19:17.440
So you're not having any pizza, Steven?

00:19:18.000 --> 00:19:19.119
No pizza for Steven.

00:19:19.599 --> 00:19:23.839
I I've probably t stolen a couple of slices before I go off my scouting mission, I think.

00:19:24.000 --> 00:19:24.720
Probably.

00:19:26.400 --> 00:19:28.720
Oh, look, the the scouting is so appealing too.

00:19:28.799 --> 00:19:41.599
When you think about, you know, sometimes at the end of your working week now, because you're just doing so much context switching, covering so much ground when you've got these scaled organizations with complex problems, the exhaustion alone is is huge.

00:19:41.759 --> 00:19:43.119
But even this strike team, right?

00:19:43.200 --> 00:19:45.440
If you think about five is still a really nice number.

00:19:45.599 --> 00:19:48.960
Like you still could lean into some of your introverted ways.

00:19:49.119 --> 00:20:03.200
But really, what we're talking about here is trying to think about uh the the types of people that you're hiring as well, like thinking about what you're being able to do with these tools now that you you look, my dev friends, not to suggest that you're out of a job at all, dear God.

00:20:03.279 --> 00:20:08.160
Um, but now you've got vibe coding more people who can actually solve some of these problems themselves.

00:20:08.319 --> 00:20:14.160
So now you're looking for more people with that ability to actually evaluate quality and understand those outcomes.

00:20:14.319 --> 00:20:25.359
Um, and you you can actually do more with your people that you're not requiring five or six different specialists, you're getting more of that generalist skill set and being able to use these tools to drive that out.

00:20:25.519 --> 00:20:26.240
What do you think?

00:20:26.559 --> 00:20:28.480
Well, so what does this mean for leadership?

00:20:29.279 --> 00:20:30.720
This is always the hot one, isn't it?

00:20:30.799 --> 00:20:32.000
Leadership, the L-word.

00:20:32.160 --> 00:20:40.559
So you know, again, this is that whole challenge around structural change, not that, you know, incremental change where you just keep adding more and more people in.

00:20:40.640 --> 00:20:44.400
Like, how do you actually mobilize these new types of teams?

00:20:44.880 --> 00:20:49.039
So this is this is your this is your classic, and everyone's eyes will just roll in this.

00:20:49.119 --> 00:20:54.000
You know, this this is the big re-org that comes every couple of years and shakes up the whole area, right?

00:20:54.319 --> 00:20:55.519
Trailblazing stuff.

00:20:56.079 --> 00:20:59.920
And look, let's lead back to what we were saying right at the beginning of the of the episode today.

00:21:00.079 --> 00:21:04.640
You know, um, what Adlassen have done is they they've done this massive re-org.

00:21:04.720 --> 00:21:08.799
Like you know, 1600 people, something like 10% of their organization.

00:21:09.119 --> 00:21:15.839
Um, that's that's big, and they and they did it quite quickly, quite brutally, from what I've been hearing as well.

00:21:15.920 --> 00:21:18.160
It was a definite rip-the-band-aid moment off.

00:21:18.319 --> 00:21:29.359
You know, there was a number of you know, very senior people who just found out that morning and were told that they'd a couple of hours left on their laptop and then their laptop would stop working and they had to hand it in and they didn't need to come back in for the next couple of weeks.

00:21:29.599 --> 00:21:31.680
So that's you know, it's one way of doing it.

00:21:31.839 --> 00:21:39.440
With something like this, do you think that it is more kind of that revolution rather than evolution change?

00:21:39.599 --> 00:21:41.279
Is is this is it better?

00:21:41.680 --> 00:21:43.200
Can you or can you bubble this up?

00:21:43.440 --> 00:21:44.960
Can but we all know how long it takes.

00:21:45.039 --> 00:21:48.240
Like I feel like we're still solving similar problems over the last 20 or 30 years.

00:21:48.400 --> 00:21:49.680
It takes a while to get that mindset.

00:21:49.759 --> 00:21:59.759
You know, Accenture came out this week and said, Hey, we're actually no, we're not looking to cut costs, we're actually gonna send our consultants out with you know, half a dozen or so agents that can actually make them much.

00:22:00.160 --> 00:22:00.720
More efficient.

00:22:00.799 --> 00:22:03.279
We want to tap into their talent, which is what you want to see.

00:22:03.440 --> 00:22:15.039
So that's where you kind of got to read between the lines of what's actually going on here when you see these, like I said, revolution of letting a bunch of people go versus trying to actually lean into these new tools.

00:22:16.799 --> 00:22:21.839
The two kind of news stories that kind of went with that was how their profit margins had greatly increased.

00:22:22.160 --> 00:22:30.240
Um they're still charging the same amount of money to their clients, um, but they're using a lot less people in order to be able to do it.

00:22:30.400 --> 00:22:34.000
So they've got their profit margins are are a lot bigger there.

00:22:34.319 --> 00:22:56.640
Um and the other one was that there was um uh a team last last year involved in the last six months or so, um, that uh a team of five again um with I think they said they had 18 agents working with them and was able to do what previously would have taken you know six months with a team of 40, they were able to do three months with with a team of five.

00:22:57.119 --> 00:23:00.400
So significant shift there.

00:23:01.039 --> 00:23:01.279
Huge.

00:23:01.440 --> 00:23:16.000
And like you're saying with leadership, this means like how do you obtain that current workforce, how do you actually reorganize them so you can tap into that existing talent rather than just go, oh bugger it, we'll let 30, 30,000 people go or something like that and and massively improve our our profit ratio.

00:23:16.160 --> 00:23:22.559
So it's it's needless to say, interesting to see how this is moving through different organizations, particularly in this environment.

00:23:22.640 --> 00:23:26.000
And it's hard, the whole cost-cutting conversation.

00:23:26.480 --> 00:23:30.319
Yeah, and especially with everything else that's going on in the world just now as well, right?

00:23:30.400 --> 00:23:33.200
So none of this exists exists in a vacuum.

00:23:33.359 --> 00:23:45.599
So there are opportunities here for, and in horrible big quotes, efficiencies within the organization, which you know, AI has been used a lot just now, and there's an element of truth in there as well that's really challenging.

00:23:46.000 --> 00:23:46.319
Absolutely.

00:23:46.480 --> 00:23:53.279
And look, you know, if we think positively, we're trying to do a bit of positive thinking with Stephen, you can use some of these new patterns to reduce your risk, right?

00:23:53.359 --> 00:23:54.799
Like, can you do more scout missions?

00:23:54.960 --> 00:23:58.880
Like, can you introduce, you know, a bit of that, dare I say, good old-fashioned design thinking?

00:23:58.960 --> 00:23:59.920
Like, can we send something out?

00:24:00.079 --> 00:24:06.720
Can we do some experiments, do some more scout missions to reduce our delivery risk in the meantime while we're evolving?

00:24:07.119 --> 00:24:25.759
What came up for me as we were prepping for this was if you aren't able to do a scout mission mission on your own organization within your own team just now, you can view what you're doing outside playing with the likes of, you know, I'm ChatGPT and Codex or Claude and Coworking Code.

00:24:25.839 --> 00:24:27.200
That's your Scout mission, right?

00:24:27.279 --> 00:24:30.240
Because you actually do have all the tools there to go off and do something.

00:24:30.319 --> 00:24:33.599
It's coming up with a mission there and and go and do it.

00:24:33.680 --> 00:24:40.559
But maybe doing it in a way that is similar-ish to what you're actually doing within your within your existing organization just now.

00:24:40.640 --> 00:24:54.799
So whether that's you're trying to be more efficient of how you're pulling together different sorts of briefs or um uh your how how you're planning things, or and it could literally be, you know, do a Scout mission of how you could plan your holiday differently the next time.

00:24:54.880 --> 00:24:56.480
And it's much more than just a single prompt.

00:24:56.559 --> 00:24:57.759
You know, what are all the other things?

00:24:57.920 --> 00:24:59.519
What are the things you could create?

00:24:59.759 --> 00:25:02.480
What's the the deep research you could do, you know, et cetera?

00:25:02.559 --> 00:25:04.319
It's finding those opportunities.

00:25:04.400 --> 00:25:14.880
Because I know we know how difficult it is to in quotes get away with this within existing organizations, because a lot of those organizations are a bit like the rabbits in the headlights just now.

00:25:15.359 --> 00:25:15.680
Absolutely.

00:25:15.920 --> 00:25:33.359
And even just challenging your own mindset, like you're saying, we we've been playing around a little bit with Claude Cowork and just thinking all the different tools that usually touch and tap into, how could I, you know, use a co-work tool instead of you jumping in and out four or five different systems and thinking, well, here's where I might need a dev, how can I work with an agent?

00:25:33.519 --> 00:25:39.279
So run your own little experiments to see, you know, get your head in the game around what it looks like to work in this way.

00:25:39.440 --> 00:25:46.079
So if you're in delivery and you would think, okay, I've got this opportunity to do a scout mission, what might that look like and bring back?

00:25:47.200 --> 00:25:59.200
There was one thing you said to me last week, which can really kind of got me, was um when you were saying, well, you could play around with your using the the researcher agents thing we've got going.

00:25:59.279 --> 00:26:00.799
Well, why do you delegate more there?

00:26:00.880 --> 00:26:03.680
I think I said something along the well, but I I I really like doing that.

00:26:03.839 --> 00:26:05.599
And I was like, Yeah, but that's the point.

00:26:05.839 --> 00:26:09.519
You might like doing it, but they can actually do it better just now.

00:26:10.079 --> 00:26:14.559
So, and it's getting over that mental barrier internally.

00:26:14.640 --> 00:26:15.920
I I found that difficult.

00:26:16.079 --> 00:26:18.240
Um I and we're using these all the time.

00:26:18.559 --> 00:26:34.000
It definitely, and and you've got to you've got to think, all right, well, I can still scratch that itch, but I can get a lot of the grunt work taken away from me because you've got your scouts going out and bringing all this high-quality research, cutting through the top layer of it for you, and then you can spend more efficient time versus some weeks gathering it.

00:26:34.400 --> 00:26:34.799
Exactly.

00:26:34.880 --> 00:26:37.680
And that's probably where I ended up as well, that it was doing it.

00:26:37.839 --> 00:26:44.640
I realized that a lot of the stuff I was enjoying doing was there's a a lot of that just kind of manual, I knew what to do, et cetera.

00:26:44.799 --> 00:26:56.880
But actually the difficult bit was the real thinking bit once you've got all of that, and that's where the effort should really be is it is using your own views and opinions to go over that once that kind of the basic stuff is there.

00:26:57.200 --> 00:27:04.240
Stephen, it looks like we've gone, we've spent nearly a half an hour digging into this, and there's so much more we could actually go into as well.

00:27:04.640 --> 00:27:08.400
Well, well, maybe in order to cleanse the palate a bit, we we need one of your jokes again, Lauren.

00:27:08.720 --> 00:27:09.759
It's difficult, Stephen.

00:27:09.839 --> 00:27:19.839
Um I'm having to lean more into puns these days, but thinking thinking about the the theme today, and I think we were kind of you know riffing on team sizes and the concept of a shrink ray came up.

00:27:20.000 --> 00:27:21.599
So I dug into that.

00:27:22.000 --> 00:27:22.880
Are you ready?

00:27:23.119 --> 00:27:23.680
I'm ready.

00:27:23.920 --> 00:27:24.960
That's pretty bad.

00:27:25.519 --> 00:27:28.960
A person goes into a hospital and says, Doctor, help me! I'm shrinking.

00:27:29.119 --> 00:27:32.880
And the doctor says, now now, you're just gonna have to be a little patient.

00:27:33.200 --> 00:27:34.799
Dear, yes, brutal.

00:27:34.880 --> 00:27:35.440
It's brutal.

00:27:35.680 --> 00:27:35.839
Yes.

00:27:36.960 --> 00:27:40.960
I won't even ask whether that was one of your own or whether that was one of your robot friends.

00:27:41.680 --> 00:27:43.039
Give me all the robot credit.

00:27:43.359 --> 00:27:44.720
I I did laugh at that one.

00:27:44.799 --> 00:27:47.279
So I don't know if that says more about me than you, to be honest, but yes.

00:27:50.960 --> 00:27:53.119
Um thank you, Laura.

00:27:53.519 --> 00:28:08.000
A bit of a recap, you know, it's it's not just about changing what teams can do, you know, it's it's it's about changing what teams should look like now and those smaller, higher context, high trust teams, you know, potentially with scouts for exploration.

00:28:08.240 --> 00:28:11.359
I think that's that's becoming more normal.

00:28:11.519 --> 00:28:14.160
What's your overall take for the episode we've just done learned?

00:28:14.480 --> 00:28:17.200
Yeah, I think it's like really thinking about what you can do now yourself.

00:28:17.359 --> 00:28:23.599
So, like if you're an analyst and used to rely on going off to a UX designer to do some sketching, maybe you can do some of this yourself too.

00:28:23.759 --> 00:28:27.279
And um, what kind of agents can run off and bring that research back for you?

00:28:27.440 --> 00:28:30.240
So it's really thinking outside the box of where we used to hand off.

00:28:30.319 --> 00:28:37.519
That's what's exciting about it, the empowering side of it, where maybe you're frustrated, oh, I wish I'd learnt to cut some code and now it's within your reach.

00:28:37.680 --> 00:28:45.680
Maybe not to the point of some of your, you know, badass dev friends, but it's there and you can actually, you know, um scrape some surface of it at least.

00:28:45.759 --> 00:28:47.039
So it's it's it's exciting.

00:28:47.119 --> 00:28:50.079
It's that mindset set shift around what you can do yourself.

00:28:50.319 --> 00:28:51.039
Amazing, Lauren.

00:28:51.279 --> 00:28:51.759
Thanks everyone.

00:28:51.839 --> 00:28:56.559
If this got you thinking, please share it with someone wrestling with these questions themselves.

00:28:56.720 --> 00:28:58.799
And subscribe and comment wherever you're listening.

00:28:58.880 --> 00:29:00.480
It really genuinely helps.

00:29:00.640 --> 00:29:01.920
And we'll see you next time.

00:29:02.000 --> 00:29:05.680
But remember, you still matter, at least for just now.

00:29:06.000 --> 00:29:06.960
Thanks, Lauren.