Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP276: From Monolith To Composable: SportsShoes CTO On Delivering Digital Transformation & Managing Operational Change At Scale
Transcript
- 0:00What if I show you how I can replace the top banner on the
- 0:03site? Let's just do that one thing
- 0:04because that's the thing you change most often.
- 0:06That's the thing that frustrates you the most.
- 0:08Let's just do that one change and then let's see how that
- 0:10goes. All you like that great.
- 0:12Should we do the mega menu next? That's great.
- 0:14And I think that that's kind of the path through to incremental
- 0:16delivery that gets people excited.
- 0:19You're listening to Inside Commerce, a weekly ecom
- 0:21strategy, technology and CX focus podcast hosted by
- 0:24experienced digital consultants and re platform specialist
- 0:26James. Go to Paul Rogers, get insights
- 0:28into ecom strategy, leading brands, hear from industry
- 0:31thought leaders and leading tech vendors with practical advice to
- 0:33help you improve your online CX. This episode is sponsored by
- 0:37Shopify. And another interesting topic,
- 0:40say we're back on to the area of digital transformation,
- 0:43technology change. And we're talking to a, a, a
- 0:47well known sports brand in sports shoes.
- 0:49And we're looking at their strategic approach to digital
- 0:52transformation, how they've managed operational technical
- 0:54change. And sports shoes has has
- 0:57experienced a lot of change recently, but it's also a large,
- 0:59large business. For those you don't know, in
- 1:02last year, it was about 90 million revenue.
- 1:03It's not just UK, it's international.
- 1:06So there's a lot of complexity within the tech stack, which is
- 1:09why we're really looking forward to the episode today.
- 1:11So warm welcome to John Cleaver, who's the CTO.
- 1:14Hey, John. Hi, nice to meet you.
- 1:16How are you doing? Yeah, I'm good.
- 1:18Thanks. Really appreciate you taking
- 1:19time, especially as I know you're just recovering from an
- 1:22illness. I really appreciate that.
- 1:24And before we get into the the digital transformation theme,
- 1:27let's start with an instruction. It'd be really good for people
- 1:29to hear about you and your background because I've I really
- 1:32enjoyed your back story as an avid runner is really relevant
- 1:35obviously to the story you're going to tell today from a
- 1:37technology point of view. Yeah, sure.
- 1:39So my background apart from probably a few years where I
- 1:44worked in legal services was, has been in, been in retail.
- 1:48So I've, I've done a number of years probably out of my 24
- 1:52years working, I think probably 20 of them have have been in
- 1:55retail. So I've always, always loved
- 1:56retail. I've always loved the, the cut
- 1:58and thrust of retail, the, the dynamic changes that go on in
- 2:02those marketplaces. And I think I'm very, very
- 2:05driven from a sort of a KPI and results orientation.
- 2:12Those businesses started from very early on my career with Tam
- 2:16computers, one of the first PC mail order retailers who then
- 2:20went into retail stores very early in the infancy of of
- 2:24e-commerce and the Internet. And then through to working for
- 2:27Carcraft to use U KS largest car hypermarket.
- 2:31Well, we grew that to a 200,000,000 LB business across
- 2:35multiple sites. And then more recently working
- 2:38for Sophology where we had 4040 odd stores up and down the
- 2:45country selling home furnishings.
- 2:48Again, probably 200 + 1,000,000 turn out the business and then
- 2:51into fast fashion with within the style, which was really my
- 2:56first sort of pure player business that I'd I'd worked
- 2:59for. And then I found myself here.
- 3:01So during that time I've been dedicated to not only my job, my
- 3:08family, but also also running. Love it.
- 3:12Real passion of mine. And it's, I'm very, very
- 3:15fortunate where I get to work in a business where my passion for
- 3:19running and what we do combine. So I think I can bring a, a
- 3:23different view on, on things and look at it through a runner's
- 3:27eyes, through the consumer's eyes because I'm, I'm that, that
- 3:30consumer. So yeah, I do walk distances
- 3:34from 3000 metres through to through to marathon.
- 3:38And again during the using this sort of obsessive goal
- 3:41orientation and task orientation, it kind of lends
- 3:43itself to, to both, to both jobs and breaking things down and,
- 3:47and managing things in small chunks and making what seems
- 3:52impossible possible through through chunking things up.
- 3:56I think both philosophies can be applied in transformation
- 3:59projects and in running. Yeah, and there is a real like
- 4:04mental battle side to both of these, isn't there Like the the
- 4:06ability to to overcome challenges because if we take
- 4:10the digital translation lens, we both know we've been for enough
- 4:13projects. Nothing runs 100% smoothly.
- 4:15No matter how experienced you are and how well you plan.
- 4:18There are bumps and there are there are like unexpected
- 4:21surprises and delights on route. And I imagine that that that
- 4:25mentality in running in terms of coping with, you know,
- 4:28difficulty of races probably lends itself quite well to that
- 4:31project environment. Yeah, I think, I think what you
- 4:33do is you develop one of the most important characteristics
- 4:37you've you've got to have is resiliency and be pragmatic
- 4:44because things come along which you don't foresee.
- 4:47And that that could be, that could be during the race or it
- 4:50could be more likely probably during them the many, many weeks
- 4:53you you spend in training out there.
- 4:55Sometimes the the weather isn't cooperative.
- 4:57We've just been through ice and snow.
- 5:00I've, I've been unwell for a number of weeks.
- 5:02I've had to adapt and, and, and respond to that.
- 5:06You look at some of the projects and, and difficulties we get,
- 5:09you know, sometimes until you get right under the weeds or
- 5:11something, you don't realise quite what the, the challenges
- 5:13are going to unfold. I suppose the only thing you do
- 5:15definitely know is when you start on a marathon block or you
- 5:18start on a new transformation project, 100% you will get
- 5:23challenges. You'll get things which, which
- 5:25come along and things which train and derail you.
- 5:28And I suppose you've got to do your best through your
- 5:31experience to maybe try and predict where those could occur.
- 5:35And if you do manage to predict those successfully, whether it
- 5:38be navigating some more complex internal politics maybe or, or
- 5:45issues which might occur or, or characters you might need to
- 5:48manage slightly differently. You know, you, you can, you can
- 5:51sort of prepare those things because the more you do, I think
- 5:54the more you learn about, about that sort of thing.
- 5:56And you you hopefully what you do is keep keep a calm head
- 6:01while others around you're losing theirs.
- 6:03That's kind of part, part of the job, certainly to be the, you
- 6:08know, to be that secure anchoring in the.
- 6:09Project indeed and our focus today is not so much on on the
- 6:15tech itself and how you set it up and do that.
- 6:17It's more about that whole project discipline and how would
- 6:20you manage and deliver these programs through a business and
- 6:24handle the change because it is lots of like stakeholders,
- 6:27internal, external. So I guess the first, the
- 6:29starting point for this conversation is you, you came
- 6:32into sport shoes, you know, at CTO level, one of the key
- 6:37responsibilities is to look at where you're at, look at how the
- 6:40business is currently function from technical point of view and
- 6:43and you know, what challenges are.
- 6:44So can you give us all that Ground Zero view?
- 6:46What were the key ecommerce or tech like challenges that you
- 6:50saw when you joined? So, yeah, we, we, there was a
- 6:55number of factors really. And I suppose what I'll probably
- 7:00do is segment them. If we look first of all at
- 7:03people you look at internally in the team, I think there was
- 7:11issues that needed picking up there in terms of people feeling
- 7:16loved in their roles, like they're making a difference,
- 7:18didn't really see the impact on what they're working on.
- 7:21But much like they were, they were in the sort of the the
- 7:23washing machine or some more dryer, you know, just just doing
- 7:26work continually. I think they need a lot of work
- 7:29on building the morale and also the capabilities of those people
- 7:33actually getting someone they could trust in because there was
- 7:36never ACTO in my role before. So we had that, there was
- 7:44external to that. We had external stakeholders in
- 7:49the business which bit a bit like maybe the, the technology
- 7:54team that was there then felt disenfranchised.
- 7:56I think they felt disenfranchised in terms of what
- 7:59service they're getting from technology as well.
- 8:01So it was, it was quid pro quo. There's obviously communication
- 8:04difficulties there that needed eye in and out and if and if
- 8:06we're going to move forward in any positive way that had to be
- 8:09dealt with. The technology itself, sport
- 8:15shoes, you know, it probably was an advantage for some period of
- 8:19time had built a lot of their all of their platforms in house
- 8:25and bespoke everything from clocking in, clocking out
- 8:29systems through to the the fulfilment systems inventory,
- 8:33the website, everything. There was an an enormous estate
- 8:37of bespoke technology which as you can imagine something gets
- 8:42built on and built on and built on and built on and built on.
- 8:44Can you change this? Can you change that?
- 8:45Can you change the other it, it, it was, it was in a, it was in a
- 8:48bit of a, a bit of a mess really that needed untangling.
- 8:53And you know, to be perfectly frank, a lot of us, quite a few
- 8:56of those elements are still around that we still need to
- 8:58tackle because it's, I have to look at this as a been then
- 9:01three years now. But you've got to look at this
- 9:03as a maybe A5 to 6-7 year project to basically be able to
- 9:09refresh all that technology stack is really hard where the
- 9:11where the business is has got to operate and and and run.
- 9:16I think we've done phenomenal what we have changed so far, but
- 9:18there's still a lot of hard work to do.
- 9:21So yeah, we look so the technology wasn't great.
- 9:25We had more bespoke work or projects than what we could ever
- 9:31possibly handle. And I've seen this in a couple
- 9:34of organization I've been to is that there was a constant cycle
- 9:39of failure where projects have been picked up, they'll be
- 9:42perceived to take too long and then dropped.
- 9:45And then the next project will be picked up, the proceeds take
- 9:48too long and then get dropped and then the next new Shiner new
- 9:51thing will be picked up again. So that was a habit where it's
- 9:53getting happy of starting and finishing and almost if you get
- 9:56that flywheel turning, morale goes up in the team, you get
- 10:01more save than buying from the stakeholders and everyone feels
- 10:05a bit more positive about, about about what they're doing.
- 10:09So yeah, that kind of gives you a a bit of an idea of of of what
- 10:13I was walking into. What do Mattel, Victoria
- 10:18Beckham, Sennheiser and Glossier all have in common?
- 10:23They power their businesses with Shopify.
- 10:27Shopify is the most innovative and scaled commerce platform on
- 10:30the planet. It also happens to have the best
- 10:34converting check out on the planet Shopify, Powering the
- 10:39future of Enterprise commerce. Find out more at
- 10:42shopify.com/enterprise. Yeah, it's interesting.
- 10:46Years ago I worked with House of Fraser and at the point they
- 10:50were evaluating their ecom stack and did they go bespoke, did
- 10:54they go platform? But what do that mean?
- 10:56And there was so much custom coding built on top of the old
- 11:00demand Ware and so much in the back office stuff in the retail
- 11:03side that any change an ecom level had a down or up straight
- 11:08impact. It's like spaghetti.
- 11:10And you're right, it's, you can't do that all at once
- 11:13because it's, it's chaos. So, so let's get into the, the
- 11:16related questions. That is, it's a, you know, you
- 11:19when we talked about this episode, you said that your
- 11:21strategic focus was on fixing pain points and finding benefits
- 11:24because that's where you start by demonstrating value.
- 11:27But how did you identify what really mattered?
- 11:29Because there are, with that, that set up you described,
- 11:32there's an exponential number of things you can do.
- 11:33So what criteria do you use to pinpoint what's actually having
- 11:37a material impact and should get fixed?
- 11:43There's no, I love to say there was some sort of rocket science
- 11:47to this, but there really isn't in terms of the practical way of
- 11:50of approaching this was to talk to people in the, in the various
- 11:58teams, in the marketing teams or in the operational teams and,
- 12:02and my peers and understand where they were frustrated and
- 12:05what things were were blocking them from getting their getting
- 12:08their job done And then hooking into some of those projects in
- 12:13which you think that actually I've seen something like that
- 12:16before. That sounds to me like something
- 12:18which which could be a that which could be a quick win
- 12:21because what we didn't want to do is just keep on adding on and
- 12:24adding on and adding on to what was already something which we
- 12:26knew wasn't going to last the last the, you know, standards
- 12:30for a lot of time. But also I couldn't reinvent the
- 12:34world in a really short space of time.
- 12:38So I think just from having those conversation became quite
- 12:41evident that as a multi brand retailer, we we are launching
- 12:47products continually. You know, we got we got 3 1/2
- 12:50thousand running shoes for instance at anyone particular
- 12:53period in time. So you can imagine there's
- 12:55probably 34567 launches of every, every single day of the
- 12:59week. And a lot of them are quite high
- 13:01profile launches. And when you're dealing with
- 13:04brands such as Nike or Adidas or ASICS and so on, we've got to
- 13:11make sure that when we do launch this project, sorry, these
- 13:14products that we do that at a high degree of, how would you
- 13:18put it, digital excellence, I would suppose has to be across
- 13:24all channels, social, the, the website, it has to look great
- 13:29because we have to elevate ourselves some other people
- 13:31who've got, who've got the same product.
- 13:34So, but that the nature of that beast is that before we had to
- 13:40do a, a website release for every single time we needed to
- 13:44change a banner on the homepage. And bearing in mind these
- 13:48website releases will take us two days to Q even just QA
- 13:52release for, for the website. So we can only release once a
- 13:55week on a Thursday. And typically what happens in,
- 14:00in, in this is marketing teams the world over is that brand
- 14:05assets always come in late, copy comes in late and everyone ends
- 14:10up in a world of frustration when they actually can't get
- 14:13then they can't get the work done.
- 14:14So people end up working long evenings.
- 14:19Things fail because you, you get them wrong.
- 14:21We miss a deadline, blah, blah, blah.
- 14:23And it just, it just looks pretty embarrassing.
- 14:25So we, we had to, I, I, I looked at that and I thought that's,
- 14:29that's, that's quite an interesting challenge.
- 14:31I bet we can solve that problem and I bet we can solve that
- 14:34problem quite quickly because we done things like this before
- 14:38with my team and in the style. So if you want me to move on to
- 14:44exactly how we kind of went about, but I can.
- 14:48Yeah. I think that's really, I think
- 14:49it's a really nice example actually, because taking away
- 14:53barriers to people executing is such a such a critical role of a
- 14:57technology department. Yeah, exactly.
- 15:00I think the key thing I'd like to think that we, we should be
- 15:05here to get out of people's way really and enable them to to do
- 15:09their jobs, not be a not be a a point of frustration.
- 15:13So and then that that frees them up to get on with get on with
- 15:16their work. So we we use ACMS platform
- 15:20called Prismic dot IO. It's, it's a headless CMS.
- 15:25Again, we have had used this before.
- 15:28So we had experience of how, how we could use it.
- 15:30And then we took this headless CNS and then we looked to see
- 15:36how we could integrate that with the, the PHP website that we
- 15:39had. And the first areas that we
- 15:42picked off were around the managing the volatile areas of
- 15:46the site, which would change a lot, the mega menu, the landing
- 15:49pages, the home page and so on. And just doing that small thing,
- 15:54pardon me, which might have taken us a couple of weeks to,
- 15:57to roll out straight away. We're out of that chaos.
- 16:00So if things do come in later or whatever, then that's with the
- 16:04marketing team because they're no longer having to rely on us
- 16:07to, to deliver that service to them.
- 16:10And it also got the team thinking more in terms of
- 16:15products and tools as opposed to web pages.
- 16:18So you got to you got to take a step back when you're looking at
- 16:21at building Acms in terms of building tools for people to
- 16:24use. So if a home page banner might
- 16:28be a wrench, a ticker that goes at the top of the page might be
- 16:31a hammer. And you build your toolbox over
- 16:34time so that when and the next time you need something that
- 16:38looks like this or behaves like this, you don't.
- 16:41But you don't build it for that specific use case.
- 16:43You build the monkey wrench forge.
- 16:46Argument's sake, if that's, if that's the particular tool
- 16:49that's needed for that, for that job, so it killed a few birds,
- 16:52that's on and you start building a flexible tool set.
- 16:56So that really got our, our marketing colleagues really
- 17:00engaged with us. We're working very closely with
- 17:02them. The collaboration went up.
- 17:04The developers in our team were, were thrilled that they were
- 17:06working on some more modern technologies.
- 17:08And then seeing how that, how that could make a difference to
- 17:11both the marketing teams, the business and, and, and their
- 17:13particularly and their work as well.
- 17:16So that that was that was quite a good example of getting that
- 17:21motivation up like enthusiasm and actually making getting a
- 17:24bit of a result or quite something which would be, you
- 17:27know, pretty straightforward from most businesses.
- 17:29Yeah. Well, I really like the approach
- 17:31though, because we talked about that you need to bring people on
- 17:34the journey when you're going in embarking on a transformation
- 17:36project that's going to take years and not everything's going
- 17:40to land in the in the first couple of years.
- 17:43And you've touched upon about how you get people to buy in to
- 17:46these change because you're delivering tangible benefit
- 17:49early on. I, I guess the question I've got
- 17:52is what have you learned through this process?
- 17:54So what worked in terms of stakeholder engagement, apart
- 17:57from delivering stuff, what worked to get them to buy into
- 18:00it, to get them to contribute to the process?
- 18:06Somehow you've got, you've got, you've got to actually be quite
- 18:12good at telling stories I suppose.
- 18:14And it helps if you, it helps if you can pay a picture of what,
- 18:18of what that outcome could look like.
- 18:21And then I think once you've, you've kind of opened the door,
- 18:26then I think rapid succession of delivery also helped.
- 18:29So let's say for argument's sake, you want to do a whole CMS
- 18:32transformation of the site. That's fine.
- 18:35But maybe what if I show you how I can just change how, how you
- 18:40can replace the, the top banner on the site?
- 18:43Let's just do that one thing because that's the thing you
- 18:46change most often. That's the thing that frustrates
- 18:47you the most. Let's just do that one change
- 18:49and then let's see how that goes.
- 18:51Oh, you like that? Great.
- 18:52Should we do the mega menu next? That's great.
- 18:55And I think that that's kind of the path through to incremental
- 18:57delivery that gets people excited.
- 19:00And I think always when, when I'm approaching a project, I'll
- 19:03always look to say, OK, what, what is the, what is almost the
- 19:06minimum I can get away with to solve 80% of the, or the problem
- 19:13or create or satisfy 80% of the opportunity.
- 19:17Just to, because often times, as we know, the, that 20% that's
- 19:21left is often the hardest part of the project and probably
- 19:24takes you 80% of the time. And they're all the education,
- 19:26the exceptions and, and all the other things that come along
- 19:29with it. So I think that doing things
- 19:32incrementally, lowering the risk, bringing people on the
- 19:37journey, I think is the the approach, the approach I like to
- 19:40take anyway. Well, when we're approaching,
- 19:43you know, projects and products, really.
- 19:46Yeah. And it makes a lot of sense
- 19:47because you touched on this earlier.
- 19:49If you do, if you implemented an entire CMS site wide, the the QA
- 19:54work that you have in your technical delivery team, visual
- 19:57QA, technical QA, then the UAT work the business teams have.
- 20:03It's really hard actually to, to, to do that around day-to-day
- 20:06work. So I like, you know, packaging
- 20:08up the whole MVP approach and that like, you know, sequential
- 20:12approach, I think makes a lot of sense.
- 20:14And I'm sure the business teams probably enjoyed not having to
- 20:17spend like 3 weeks of UAT as well.
- 20:20Yeah, it is. It's a real challenge, you know,
- 20:22especially we, we are, we are, we have, you know, really
- 20:25modestly quite small teams. For what?
- 20:27For what we, what we, what we have to deliver, you know, we
- 20:31got, we got a back end team of five engineers, we got a front
- 20:34end team of five engineers and then the the rest are, are, are
- 20:38in our operational and support stuff.
- 20:40So use it. So it's not, not, not a great
- 20:42deal of capacity to, to, to, to do all that work.
- 20:46So I think that working in small in small chunks makes makes a
- 20:50lot of sense like that and just get some wins out there.
- 20:54Yeah. And and something that I, I see
- 20:56a lot in projects because I guess I'm, I'm on a different
- 20:59side of the project to you. I'm not delivering the technical
- 21:02side, but I'm working with all of the technical teams in a kind
- 21:05of customer leading E com consultant capacity.
- 21:08And what I see in, in larger organisations like sports shoes,
- 21:13when you're at that scale, is that change can be disruptive.
- 21:16And you can, you can manage change, but you can't, you can't
- 21:20dictate how people will respond to it.
- 21:22You can only then react. So what is your approach to
- 21:25handling people? Because some people are
- 21:26resistant to change, it threatens them, it to stabilize
- 21:29them. And how I guess what have you
- 21:31learnt now? How do you how do you approach
- 21:33that if people won't adapt? The I think when let's let's
- 21:42Fast forward. So we, we got, we got the, we
- 21:44got some quick wins out there. We won some confidence with the
- 21:46business. And I said, guess what guys, I
- 21:48think we need to change the we need to redo our e-commerce
- 21:52stack, right? So suddenly we got the biggest
- 21:54ticket project that the that the business has ever worked on,
- 21:57investing in multiple headless platforms and building our own
- 22:02front end. It's where it was.
- 22:03It was a really ambitious project.
- 22:07Now the, the background to that is that Dan, my opposite number
- 22:11in our, in our marketing function, he was, he was quite
- 22:16fed up with because there's so much work going on just to keep
- 22:19the site branded correctly and and so on that we could never
- 22:25actually move forward. And, and he wanted, he wanted a
- 22:27new PDP, he wanted a new PLP, he wanted a new home page design,
- 22:31he wanted a new car, he wanted a new check out.
- 22:35And then, and I said, well, you need a new website really, don't
- 22:37you? And then right, OK, so if we're,
- 22:39if we're going to need a new website, well, what we don't
- 22:41want to do is we don't want to build it in what we've already
- 22:44got because we both agree that that really isn't sustainable.
- 22:46Going forward though, let's look at how we can do things properly
- 22:50at scale and then and then come out with something at the other
- 22:53end of it, which is better for all of us and, and most
- 22:58importantly our, our customers. And Dan and Dan bought into
- 23:02that, that vision to, to do a whole new implementation.
- 23:07So I never really had any push back from the market team,
- 23:10marketing team. And they were very good in that.
- 23:12What they weren't doing is they were happy to sort of mothball
- 23:15any development on the current site whilst we're working on, on
- 23:18the new site. We worked with, with an agency
- 23:21at the time and we went through a whole, whole discovery process
- 23:25where we involved cross functional teams to go through
- 23:29every single area of the website and then try and learn about
- 23:34what each function did, where he got his data from, how it
- 23:36operate, how important it is, and then challenge each one of
- 23:39those areas. And then we, we, we use the sort
- 23:42of Moscow approach to figure out what things were really, really
- 23:44important to us and our special source and actually what things
- 23:47we we could ditch. And then, and then we did that
- 23:49very much as a team to understand going back to the
- 23:52sort of premise of a, a minimum viable product, what, what we
- 23:56could deliver. But they were involved in that
- 23:58journey, you know, cross functionally.
- 24:00So they, they all had a vote, they all had a say.
- 24:02And then it ended out we could say, OK, well, this is what we
- 24:05think the new website could, the functions could look like.
- 24:09And then we also validated that through talking to customers
- 24:13directly, good, good and bad thing with me being a runner, I
- 24:19could be drinking my own kool-aid and just bully whatever
- 24:21I think, well, I'm the runner so I must know what I'm doing.
- 24:23Whereas it's not always, it's not always the case.
- 24:26So most time it is. But the is we, we did speak to
- 24:32our customers and we did interviews in and labs with them
- 24:35where we got their feedback and we showed them, we got them to
- 24:41do various challenges on the, the current website.
- 24:44And we got them to to evaluate some mocks that we designed
- 24:48using Envision stick a click through Clicky prototypes got
- 24:52their feedback. We asked them to evaluate some
- 24:55of our competitive sites as well and give us feedback of what
- 25:00they like. And we managed to meld all that
- 25:02feedback into what was what was a whole series of of clickable
- 25:08user user interfaces. And again, that was another area
- 25:12where suddenly the project comes to life and suddenly people see
- 25:17the possibilities of, of this new world.
- 25:20And then everyone gets a bit excited.
- 25:21Rather than talking about abstract concepts and and, and
- 25:25and and words and specs or whatever, Then suddenly people
- 25:28think, oh, great, that's actually what that could look
- 25:30like. And oh, what, what do we think
- 25:32about this and what do we think about you got something to get
- 25:34around the table together with and kick ideas around and see
- 25:38what will won't work. So that, so that were really
- 25:42well, I was saying then everyone kind of knew then what, what we
- 25:46were, what we were shooting for. And that was internally and
- 25:49externally. I'm dealing with partners such
- 25:51as the commerce knew what we were working towards, the agents
- 25:54who were working with at the time, they knew what we were
- 25:56working towards and so on. And then also it helped us
- 25:59divide up the, the projects in terms of which teams were the
- 26:03best to take which parts of the of the project over as well.
- 26:08And going back to what we discussed before about neither
- 26:14thing going to plan more certainly that that was
- 26:16definitely the case. I mean, what we found as we as
- 26:19we were going along the project never always works out this.
- 26:24But always I think that whilst when you're trying to win a lot
- 26:27of confidence, getting quick wins in quick easy wins in first
- 26:30makes a lot of sense. But when you're starting these
- 26:32larger projects, there are certain areas in that project
- 26:35which make you really, really nervous.
- 26:37So there might be areas, complex areas that you've got, I don't
- 26:40know, let's say payment services just for argument, say, let's
- 26:45say that that's the most complex part of your stack.
- 26:48Or it could be we have really complex different shipping rules
- 26:53to different zones. And I think it's always a
- 26:56mistake really to try and all worry about those problems at
- 27:00the end of the project because they're the always the things
- 27:02that derail your sort of thing. Unearthing those things during
- 27:05discovering, pulling those things or, and then deep diving
- 27:08in those areas, I think really helps.
- 27:10And using those stakeholders to help you dig under the hood
- 27:15helps lessen the, the, the risk of the projects as well.
- 27:18Because you know, you've not got a load of skeletons in the
- 27:21closet that you just waved to open a door and, and then they,
- 27:23and then they fall on you, fall on your face really.
- 27:26So that, that works, that works quite well.
- 27:32And then we did have points where we had to pivot.
- 27:34I mean, ideally we'd, we'd have delivered the first UK website
- 27:38in the August of 2023, but we were running way too close to
- 27:45that deadline and we're going to run into peak if we messed it
- 27:50up. So we decided to just park where
- 27:55we were in terms of the UK stored get through that peak
- 27:58period. But I managed to negotiate to be
- 28:01able to deliver our international stores, which were
- 28:04like, so our international stores is four of them and they
- 28:08do about 20% of the business ish, let's just say that
- 28:12broadly. And those were the smaller train
- 28:15sets that I could put out there. I could observe each one of
- 28:22those when we released them, make all the mistakes.
- 28:25And there was a number on, on those on those sites.
- 28:28And then each time we'd, we'd roll out.
- 28:30So the first one my had taken us six weeks to stabilise in Spain.
- 28:34And then we've got, OK, we're pretty confident now.
- 28:37We, we've gone through that. We fixed it, we fixed it, we
- 28:38fixed, we fixed it, we fixed it. We got better.
- 28:40And then we, and then we did our Italian store, then our French
- 28:43store, then our German store. So using that iterative approach
- 28:47again, it, it built confidence. And that meant actually when
- 28:49the, when the UK store went live, it wasn't really a drama.
- 28:54No one was really worried that it was going to be a disaster
- 28:57because we, we've been trading on all the new stack for best
- 29:00part of five months before that. And we got a warning shot
- 29:04actually, which was, which was interesting.
- 29:06And I remember this very clearly because on a holiday at a time
- 29:08as typically would happen. So I just got off a gondola in
- 29:12Venice and the current website we're on completely imploded.
- 29:17And we and it took us a, a good period of time to rescue that
- 29:22website to get it back up and running.
- 29:24So having had that warning shot, that kind of walk everyone up to
- 29:30say, hang on a minute, we need to get this now rolled out
- 29:32really, really quickly. Because what we don't want to
- 29:34happen is, is that occurring again?
- 29:36Because really we didn't know why it had blown up.
- 29:39We just knew it had blown up and it took us a long time to
- 29:43diagnose why that that that incident had happened.
- 29:46So that did me a favour in some regards because that put the,
- 29:51the more risk averse stakeholders, it put a fire
- 29:54right up underneath them to think actually it's really
- 29:56serious. Now we need to, we need to push
- 30:00forward because before that there might have been a reason
- 30:04every week for why we shouldn't do it, you know?
- 30:07It's, it's interesting because you never want your site to go
- 30:09down like that, do you? Because I know the pain it
- 30:11creates in the, in the IT department, but also in the
- 30:16stakeholders trying to manage the customer expectations.
- 30:19But it's funny how sometimes that sharpens the resolve.
- 30:21And it was, it was really nice to hear actually about the
- 30:24approach to, to factoring the customer feedback loops.
- 30:27Because I, I remember doing a project a while back with, with
- 30:31Selfridges and it was, it was on a micro level.
- 30:34It was more about like on site changes and there was real
- 30:37resistance to what we saw in the data and to to making changes
- 30:42because of such tight brand and customer experience controls.
- 30:46And then we did, I just basically got them to to invest
- 30:49500 lbs of remote video sessions with customers to get the
- 30:53customers to video their experience of that user journey
- 30:56and comment on it and show what was the problem.
- 30:58And five customer videos played in a boardroom and amongst
- 31:03senior group that suddenly everyone changed their viewpoint
- 31:05and that barrier goes. So yeah, it's interesting to
- 31:08hear there's different levers, aren't there to tackle
- 31:10different, I guess, personality. Types yeah, I think that's is
- 31:15very, very powerful and sometimes you're sitting there
- 31:18watching those videos back like you know, but it's great to have
- 31:23that feedback and it and it does getting that and on the board
- 31:28boardroom table, if you will, like you said, then I think it's
- 31:30a really powerful motivator. It isn't.
- 31:35I, I really like that incremental approach you talked
- 31:38about, about launching your lowest risk stores first, doing
- 31:41that with a, a pet care client at the moment.
- 31:43And the UK is their main business and they just launched
- 31:47into Europe and the trial site was Germany.
- 31:50And that went live without any marketing activation just to get
- 31:53it live and see what we'd missed.
- 31:56Because you're right, it doesn't matter how good your team is,
- 31:58how good the tech is. There is so many moving parts in
- 32:01a re platform in it or a new launch.
- 32:03There are so many integration points, so many data points.
- 32:07There's always something that you've missed that you don't see
- 32:10until it's in the wild. And that's exactly what it has a
- 32:14period of fine tuning so that then when you get to the next
- 32:17launch, you've ironed out all the the things.
- 32:20So interesting. Yeah.
- 32:22So that brings you onto my next. Just one thing which is which is
- 32:25just linking into that a SEC. One top tip I suppose is that
- 32:30when we did our launch, you might have you might have done
- 32:32the same in your experience is that we shot all the, the new
- 32:37store we we put live had no exposure to to Google either.
- 32:43So any of those because there is massive SEO concerns when you
- 32:47when you when you're re platforming a site as well.
- 32:50It was not crawlable. It was not visible.
- 32:53And then we did some shenanigans in the background so that that
- 32:56even though customers weren't shopping on the old site that
- 32:58Google would would be redirected and would crawl the old site.
- 33:02So that, that, that again, bought us time because I can
- 33:08tell you now people start panicking when organic
- 33:11visibility drops. And it's unfortunately, it's
- 33:17inevitable that it's going to, that it's going to, it's never
- 33:21going to, you're not going to put a new website and then
- 33:23switch it and it's going to, it's going to go, oh, that's,
- 33:25that's gone through the roof. It's never going to happen in
- 33:28the million. It's always going to go down
- 33:29before it goes up. I suppose what you're trying to
- 33:32do is you're trying to shorten that that curve back up again,
- 33:36which is tricky. Yeah.
- 33:37Well, unless the current site is so royally screwed up for SEO
- 33:42that impossible to make it worse, which does sometimes, but
- 33:47you would hope obviously where our businesses of your stature,
- 33:49you would hope that the SEO is in a rudimentary health anyway
- 33:52so. Yeah, yeah, what?
- 33:55To be fair, there'd been a lot of work done on that and it was
- 33:57a very, very deep site, too deep even where Google could only
- 34:01crawl, I think 20% of it before it give up.
- 34:05Now that inhibit itself is a problem because he's missing
- 34:09loads and loads of pages that we do want indexed.
- 34:13So whilst it was really fat, fat side in, in, in, in terms of
- 34:16content that was there, a lot of it, he wasn't, he wasn't getting
- 34:19anywhere near the edges of it. So yeah, that, that, that that's
- 34:22a, that's an important thing. Yeah, it is.
- 34:24And it's, I was having a conversation with another client
- 34:26of mine recently about this, about technical SEO skills are
- 34:29undervalued in large repack forming projects.
- 34:33If you don't have it in house, you fundamentally need somebody
- 34:36who's got that architectural understanding as well.
- 34:39We we worked with an agency on that propelling it and they were
- 34:44very, very good, very, very good and held our hand all along that
- 34:49approach to to launch in the UK store.
- 34:52They they, they were, they were, they were more on the on the
- 34:55risk averse camp, but they were, they were sort of they were,
- 35:00they were the one, they were the one of the parties which once
- 35:03the web, that old website had gone down.
- 35:05We're like more than happy to say the shelf just to say, you
- 35:08know, we this can't happen again.
- 35:11So yeah, that that was, yeah, having that, having those
- 35:15advisors there, if you don't have them internally is is
- 35:17really, really, really important because you can make a right
- 35:20mess. And I'm sure the Propeller net
- 35:23are delighted that the plug on the podcast as well.
- 35:25They'll they'll be happy that their name's been mentioned.
- 35:28Yeah, I've heard other people speak highly of them too.
- 35:31Let's get onto the E Comm stack because I'm keen, I'm keen on
- 35:34this. I've worked on a few big
- 35:35commerce projects and you built so big commerce is the commerce
- 35:40engine. But you said you've gone through
- 35:43more of like a headless approach with other tech as well.
- 35:46Can you talk? I guess I've got 2 questions.
- 35:48First one is how did you get to big commerce?
- 35:50Because the market's big, there's loads of platforms and
- 35:52everyone's shouting at, at merchants like yourselves for,
- 35:55for, for like migrations. So how did you get to big
- 35:58commerce as the right fit? And then what is the wider stack
- 36:01that you've built out? We what was important to us at
- 36:08the beginning going back to one of really I mean we, we sell, we
- 36:13sell running shoes and running related products primarily, but
- 36:20anyone can can do that to an extent.
- 36:22Where we differentiate ourselves is pretty much we are a content
- 36:27and experience driven brand really.
- 36:30And then we just happen to sell, sell ring shoes.
- 36:33What that, what that means really is that you that in terms
- 36:36of what we do, we, we don't really want just a generic
- 36:39run-of-the-mill cookie cutter website.
- 36:41So we want something which we can take a higher degree of
- 36:45control and fidelity over how we, how we want to present that
- 36:48to our, our customers is really, really, really important to us.
- 36:52That lent itself to, to, to headless.
- 36:54We didn't want to have any restrictions in terms of the
- 36:56template and engine or, or, or anything like that.
- 36:59So we we knew we landed on that and and we knew which front end
- 37:03technologies we we wanted to to use because they're the skill
- 37:06sets that we already had in had in the team.
- 37:07We knew we wanted to use for sale, we wanted to use next JS.
- 37:12So they they, they were pillars that we that we knew we wanted.
- 37:16And then we what we didn't want to have is again, another,
- 37:19another bispo com grown platform that we build ourselves.
- 37:23So we're going to lean on a third party platform.
- 37:26And then we looked at the usual, usual suspects.
- 37:28I think the easiest way of of getting to where we got to with
- 37:31big commerce was the V what will be the technologies ultimate
- 37:38approach, which might be, I don't know, something on the
- 37:42lines of a commerce tools maybe where you get a very, very
- 37:46flexible set of building blocks. You can do whatever you want
- 37:51with. But literally anything you
- 37:53build, anything you do with those building blocks, you need
- 37:56to kind of do yourself, which, which involves quite a heavy
- 37:59lift from an engineering effort. And as you can imagine, time and
- 38:04budget when it comes to that. But you could compose something
- 38:10fantastic given given unlimited resources, time and budget, you
- 38:14could you could do something from that perspective.
- 38:16And I think that that that sort of platform really works well
- 38:20for those companies which are maybe double the size of ours.
- 38:25If you're 200 million turnover of e-commerce business, I think
- 38:28you can probably afford to do a transformation project that's
- 38:32going to cost you £2,000,000 to build a new website, right.
- 38:37We weren't fortunate to do that. We, we felt like at the time,
- 38:41I'm sure it's, it's changed all this time of these things too.
- 38:44We, there was more generic offerings, you know, top off the
- 38:47shelf type offerings, which we, we didn't feel was quite right.
- 38:51Was it was too, too rigid and big commerce was kind of sit
- 38:54somewhere in the middle where in terms of we could use the
- 38:58headless nature of their their product build, have the
- 39:01flexibility of building our own interfaces, but hook in some of
- 39:04the more commoditised areas of that platform which were already
- 39:07pre built. So you kind of got like a a bit
- 39:08of a halfway house. And we could build that within
- 39:11the the modest budget that that we had that we had available to
- 39:15us to, to tackle that, to tackle that project.
- 39:18And we also wanted to, we knew we wanted to bring alongside
- 39:22that a mobile app as well, bring that to market.
- 39:25So we needed something we shouldn't have a flexible
- 39:27platform for us, for us to be able to do both the, the website
- 39:30and, and the mobile app over over time.
- 39:32So that, that's where we got there.
- 39:33So it worked. It worked for us, right?
- 39:35I think for our size of business, we're not a small
- 39:40business. We're kind of in that awkward
- 39:41place where we're not a big business either.
- 39:43So we're probably small medium in terms of what we do it it
- 39:49felt like a a good fit and and the project team we got given
- 39:53and helped people that helped us deliver the project from big
- 39:55commerce were very, very good and supportive all the way
- 39:57through that, through that project through the a lot of ups
- 39:59and downs because we found that the that we were wonder their
- 40:05very first headless implementations.
- 40:07And we really pushed the boundaries and the capabilities
- 40:10of that platform in a number of areas in which they had to
- 40:13respond to and help us help us resolve.
- 40:16So yeah, it wasn't. There was a lot of ups and
- 40:20downs, a lot of emotions, but yeah, we, we, we got there in
- 40:25the end and. And broader to how did you then
- 40:29branch out? I'm assuming the starting point
- 40:31was, was big commerce platform then then what else have you
- 40:36built around there? What are the key other
- 40:37technology stacks? We mentioned Bloom Rage and I
- 40:40mentioned your front ends. Yeah, so bloom rage has bloom
- 40:44rage has been great for search. So that, that, that, that does
- 40:46a, a great job. Anything would have done a much
- 40:50better job than the than what we had before, which is which would
- 40:53be a bonus. So blue meat.
- 40:54Yeah, that's our, that's our search platform.
- 40:57We've got Stripe for payments. I've already mentioned Prism and
- 41:01IO, IO for the, the CMS. And in our, we, we very much
- 41:06built the website ground up from CMS.
- 41:10So all elements of that site are pretty much all CMS driven.
- 41:15So anything our creative team want to change, they can pretty
- 41:20much change any part of content on on on that site, which we
- 41:25works really well from. Then again, I'd I'd have to
- 41:27worry about they could complete the website could look
- 41:29completely different tomorrow without any any engineer being
- 41:33involved. That's from building their own
- 41:35bespoke store pages, building bespoke PDPS, completely
- 41:41reimagining the home page and also using them extensible
- 41:44frameworks when it comes to when it came alongside as building
- 41:49our mobile app that again hooks into the same, the same
- 41:52technologies. So our content editors and
- 41:54content creators are using Prismic and then they can choose
- 41:57whether they're going to publish that particular article to both
- 42:00the app and the website or one or the other.
- 42:03And, and they can they've got reuse there.
- 42:05There's banner might go on the website, there's banner might
- 42:07not. This competition is going to go
- 42:08on the app, it's not going to go on the website.
- 42:10So because we've built them a whole toolbox full of full of
- 42:13tools, they can really the walls are oyster in terms of being
- 42:16able to build out. So that that's been out.
- 42:19We've really managed to be able to leverage on that, on that
- 42:22reusability from that perspective and have a familiar
- 42:25way of working to increase the, the throughput of those teams.
- 42:29I mean, before we published maybe one or two articles every
- 42:33every couple of weeks. And then they'd need to be
- 42:34internationally translated. And then it would take another
- 42:37two weeks for them to be published because they'd have to
- 42:39go for a development pipeline. Whereas now we're publishing an
- 42:41article that gets translated and it can be out within, you know,
- 42:43two hours of it being written, you know, which has been
- 42:46transformational to people who do that as a, as a, as a job.
- 42:49Yeah, the I'm a big fan of for headless CMS where people have
- 42:54any significant workflows and publishing control needs because
- 42:57native page bills just don't do it.
- 42:59And then you get into customisation land and actually
- 43:01that becomes really messy as opposed to using a tool that's
- 43:06intended and to find to do that. You've talked a lot about
- 43:11obviously building out from principle of of headless
- 43:13architecture. I'd love to know what impact
- 43:16that had in your engineering team because you said you're
- 43:17relatively lean engineering team for a business of the size
- 43:20you're at. How did the engineering, how can
- 43:23you say it, engineering team structure have to change?
- 43:26And also linked to that was I think you mentioned that you'd
- 43:29reunited some of the team you previously worked at in the
- 43:31style what what benefits your project delivery did that have?
- 43:35Yeah. So there's a, there's a, there's
- 43:37a couple of guys who I've worked with for, for a, for a number of
- 43:40years. I'll give them a plug.
- 43:42We've got got Lee Witherington and Imran Sawa, who our lead
- 43:46engineers, brilliant, brilliant people, brilliant brains and
- 43:51much smarter than me. And you need people that are
- 43:54smarter than you and the team, right.
- 43:55So bringing, bringing them on board.
- 43:58I think if you thought much enough to do that.
- 44:01We're all comfortable working with each other.
- 44:03We under, we all understand our, our strengths, our weaknesses,
- 44:05our foibles, because we've known each other for so long and also
- 44:09we've gone through the ups and downs and emotions together.
- 44:11And also we've delivered some brilliant projects over the
- 44:13years. So I suppose what that comes
- 44:15down to is we trust each other and, and we all trust what we're
- 44:20all going to do our, our jobs. And you know, Imran looks after
- 44:24the, the web and the front end team and, and Lee looks after a
- 44:27lot of the back end services and those engineering teams, though.
- 44:31And and, and then I then I then I just do the I was just a
- 44:35mouthpiece. So yeah, that that that were and
- 44:39I accelerated. Not everything without those
- 44:44guys, you know, would have been really struggling because not
- 44:48only did we have to transform the technology, we had to take a
- 44:54lot of the team on the journey. Now, to be frank, not everyone
- 44:58made it. There were there were some
- 45:01people who just don't want to really adapt or change or
- 45:04improve. And sometimes it baffles me
- 45:06really, but but it's not for everyone, you know?
- 45:10And we tried really, really hard mentoring people, coaching
- 45:15people, putting people on training courses.
- 45:19But at the end of the day, you know, take a horse to walk, but
- 45:22he he ain't always going to drink.
- 45:23But there have been some absolute shining stars which
- 45:26were in that original team. And if you'd have asked me at
- 45:28the beginning how many out of this list are going to last the
- 45:33duration, I wouldn't have thought I'd I'd been amazed that
- 45:38I picked one or two out, to be honest.
- 45:39But I've been really, really impressed with the vast majority
- 45:45that have that have that have got on the bus and committed to,
- 45:50to the change, committed to improving their skills,
- 45:53committed to doing the learning. And I think everyone's benefited
- 45:58from that because the technologies we're they're
- 46:02working on then are just not marketable anymore.
- 46:04They're, they're almost redundant.
- 46:05They're, they're irrelevant. You, you'll be borderline
- 46:08unemployable right now. So we've helped them guys build
- 46:13their careers. They've helped us, you know,
- 46:14just as much and, you know, we've all gone on a bit of a
- 46:18journey together. So that's, that's, that's been
- 46:20great. So yeah, from, from, from those.
- 46:23So bringing the guys on board, I knew and trusted accelerated
- 46:26that. They've done a great job of
- 46:28bringing a lot of those guys on board.
- 46:29And the people they've brought along with them are now levels
- 46:33above where where they were before, from the effort they've
- 46:36put in and the mentoring they've had from both Lee and Inram.
- 46:40Yeah, it's at that point about like your future career paths as
- 46:45well. And when technology changes in
- 46:48terms of what's what's important and what's valued and where
- 46:51employability lies, it's so critical.
- 46:53I, I worked with another business and last year and one
- 46:57of the big issues that the team internally are having is the
- 46:59stack they're on was not one A they're excited about, but B
- 47:03also, it's a stack that lots of brands are moving away from to
- 47:06more modern, whether it's SAS or composable.
- 47:09And for them to then get to the next stage without that
- 47:13expertise, it's so much harder for them.
- 47:16So yeah, it's a really interesting point and it brings
- 47:20me on to my final question, which is you go, these projects
- 47:23are intense. We all know they're fun.
- 47:25It's basically it's like this vortex you get pulled into.
- 47:29But then once you've once you've done your initial launch and
- 47:32you're now live on a new stack based on big commerce with Bloom
- 47:36Ridge for your new front and etcetera, you then have to as
- 47:39well as continue to deliver the rest of the project
- 47:42functionality. You've then also got to do a bit
- 47:44of a pivot because you're into product management world as well
- 47:47and it's a new product. How have you found that?
- 47:50Like how have you found adapting to the disciplines and the team,
- 47:52getting to adapt to to running a product, not just a project?
- 48:01Maybe I'm not, I'm not sure the lot of the philosophies change
- 48:05much. I'm not sure really because we,
- 48:07we still very much work in that sort of incrementality approach.
- 48:12We don't have bike, we don't have, we don't.
- 48:14The great thing is once you've got, once you've got a foothold
- 48:16and you've delivered that project, you then can really,
- 48:19you can then start to rapidly improve things, especially the
- 48:24new technology we got. You know, if I mentioned before
- 48:26we've done, we did one release a year week, sorry.
- 48:29So that'll be 52 releases a year.
- 48:32I'm sure one of the team told me the other day that, that over
- 48:35the last 12 months there've been something like 5000 releases
- 48:40that we've done from that team. That's how incremental they are.
- 48:42They're delivering constantly to production.
- 48:45So we're quite, we're quite fleet.
- 48:47But in terms of what we do, we will often engage with our some,
- 48:54some requirement might come from our marketing team, it might
- 48:57come from a brand, it might come from a partner.
- 49:00We will, we will look at that. We will speak to our our UX
- 49:05design guys that we've got. They will go away.
- 49:08They will, they will design that product, we'll bring it back in.
- 49:10We'll look at how we can build it.
- 49:12Then we go through building it and then obviously once we've
- 49:15built it, we need to make sure we go through a a cycle where we
- 49:18test, test it, make sure it works and then put it out to
- 49:21production. Now, in an ideal world, it
- 49:22doesn't always work like this. You put it out to production
- 49:25with some, some how would you, how would you describe it?
- 49:30Being able to measure the outcome of what that what that
- 49:34what that did. Now this is supposed is a key
- 49:36difference from a massive project.
- 49:37I mean, like we can, we can change the website from A to B,
- 49:41but when things, when trading ain't great, what, what one
- 49:46thing do you point out that's gone wrong?
- 49:47You've you've delivered a whole new new website.
- 49:50So but once you, once you're delivering small incremental
- 49:54gains, they can be very measurable.
- 49:56You can understand how many people are interacting with
- 49:58something. You can understand how what
- 50:00conversions and features have given you.
- 50:04And I suppose that's a key difference in how you think for
- 50:06a product management lens than necessarily what you would do
- 50:09for a project lens. It becomes more more BAU I
- 50:12suppose. Yeah, indeed.
- 50:15And it's interesting when you're running the two concurrently
- 50:18basically because it, I think sometimes people struggle to
- 50:21separate road map of product from the delivery cadence of a
- 50:26project. And it takes good discipline to
- 50:28bid and fundamentally you're working in sprints.
- 50:31So therefore there are different streams within the sprints and
- 50:33it takes good discipline to manage those together.
- 50:36It can get quite stressful though, you know, it can get
- 50:38trying to, trying to trying to land projects, doing the small
- 50:43BAU type stuff, you know, the hygiene stuff that just needs
- 50:46doing and then another project comes along and so on.
- 50:48You know the when you've got a small team that can become, that
- 50:51can become quite, quite stressful.
- 50:53It needs a high degree of of coordination really as well.
- 50:57Yeah, indeed. Let John that that I could sit
- 51:01and ask you questions all day. But I know that we both got
- 51:04school runs as well, so I really appreciate you taking the time
- 51:07to come. I found that really interesting.
- 51:08I love hearing from from digital leaders like yourself about how
- 51:12you approach these complex projects and how you manage to
- 51:15deliver it. So really enjoyed it.
- 51:17Thanks for coming on and I hope everyone listening has enjoyed
- 51:20it as well. Yeah.
- 51:22Thank you very much. I enjoyed that conversation.
- 51:24Somewhat cathartic, I think. Yeah.
- 51:26Yeah, it's, it's confessions of of project leaders, right.
- 51:30Yeah, just have to our parents had anything.
- 51:32The boss is going to find me for now, but hopefully, hopefully
- 51:34I'm on stage. Excellent.
- 51:37Well, thanks so much again and thanks everyone for listening.
- 51:39And until next week, everybody. Thank you.
- 51:42See you in a bit. You're listening to the
- 51:45Insidecommerce podcast hosted by experienced consultants James
- 51:48Gert and Paul Rogers. Insidecommerce is your fast
- 51:51tracked additional knowledge featuring interviews with
- 51:53leading e-commerce retailers, industry thought leads and the
- 51:56C-Suite key tech companies to explore the latest digital
- 51:59strategy, customer experience and tech.
- 52:02Discover what the latest trends really mean and get practical
- 52:04advice based on experience to help fine tune your ecom
- 52:07strategy and take stack. Follow us on LinkedIn and reach
- 52:11out to James and Paul if you'd like to discuss an Ecom's
- 52:13project. We hope you enjoy the latest
- 52:15episode.