Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP210: Replatforming To A New Headless Stack On BigCommerce and Bloomreach, with MKM Building Supplies
Transcript
- 0:02Thanks for listening to the Re Platform podcast, sponsored by
- 0:05Crown Peak and Elastic Path and hosted by me, James Gadacall
- 0:07Rogers. We bring you interviews of
- 0:09industry thought leaders and the C-Suite of tech companies and
- 0:11leading brands, showcase Ecom Tech and help you decide what's
- 0:14relevant to your business and hopefully discover new solutions
- 0:17and new ideas or ways to do business in return.
- 0:19All we ask is you tell people about the podcast and you share
- 0:22our social posts. And if you're new to the show,
- 0:24give us that rating on Apple, Spotify, YouTube, or wherever
- 0:26else you might be listening. So then we hope you enjoy our
- 0:29latest episodes. The topic today is re platforms,
- 0:31you headless stack on Big Commerce with Bloom Reach or
- 0:35joined by MK and Building Supplies.
- 0:37So I'll let Paul set up an intro guest because he's previously
- 0:40connected to him. Oh, cheerful.
- 0:44Great. Yeah.
- 0:45So, so Craig and I'm at a Big Commerce event in Austin, must
- 0:50have been the year before last, in 2021.
- 0:53And although we didn't spend too much time together sober, Craig
- 0:56gave me a bit of an overview on his project and that he was
- 1:01doing at the time with Big Commerce in migrating the MKM
- 1:04stack over to Big Commerce and a number of other vendors, which I
- 1:08found really interesting. So I asked him to join us.
- 1:11But Craig, maybe if you give us a little bit of an intro to you
- 1:13as well, your background and then also MKM and then I'll ask
- 1:16the first question. Thanks, Paul.
- 1:19Yeah, so I'm Craig and Clan. I am Head of Digital and M Chem
- 1:23being in the company just over 2 1/2 years now.
- 1:27So I joined June 2021. So my background mainly, I mean
- 1:32I've worked for, I think I'm on my 30th year working now.
- 1:35You maybe all think I start, I started when I was 12 but not
- 1:38quite. So I kind of started as a
- 1:41developer a way, way, way back kind of moved into project
- 1:44program management then got into kind of e-commerce re platform
- 1:47projects with with Heineken and did a number of them kind of
- 1:51over 7 years. So taken business to business
- 1:55online for kind of the first time.
- 1:57So that was my kind of 1st 40 into e-commerce and I really,
- 2:01really loved it because I could actually relate to the product
- 2:05and everybody had an opinion on e-commerce because we all use it
- 2:08in our everyday lives. So the opportunity came along
- 2:12with MKM with Andy. I'd worked with Andy Heineken
- 2:16before and we were basically doing a RE platform basically
- 2:19ground up. So the opportunity to do that
- 2:23and actually have a fixed timeline because it was a
- 2:26burning platform, we'll probably come on to some of that later on
- 2:29actually was really appealing to me because it gave us real kind
- 2:33of focus and I really loved that Can Andy's ideas and strategy.
- 2:37Yeah. So I took the decision to leave
- 2:40actually Sky, who I was with for a couple of years, to agile
- 2:42transformation to kind of get more hands on and deliver, you
- 2:46know, composable Colliers solution, which I had never done
- 2:50before, but I really, really wanted to crack it.
- 2:53So that's me. Great.
- 2:55And I guess we've kind of touched on this a little bit,
- 2:57but can you just talk us through like I guess why you were re
- 3:01platforming, what you are migrating away from and and what
- 3:05the kind of overarching goals what are for the project?
- 3:09Yeah. So I think we're to even
- 3:10describe for migrating away from it's quite, quite challenging
- 3:13actually because it was built on I think it was about 11 years
- 3:16worth of different solutions but it was selling an EPI server
- 3:19back end and and we had a mobile Fi can it front end and a lot of
- 3:26these a lot of products were kind of going end of life.
- 3:28Mobafi was we'd have to totally re platform and I think based on
- 3:33the infrastructure they've had in a lot of our back end, we
- 3:36decided that it would be better and more efficient to to strip
- 3:41it out and basically start again.
- 3:44So it was a kind of old monolithic set up, various
- 3:47projects hadn't quite made it over the line, but I'd made it
- 3:50over in the kind of last one. But it it basically had about a
- 3:55year and two months to go before it went into life and that was
- 3:58mainly the kind of the the Mobify side of the stuff.
- 4:03So can you talk us through your selection process?
- 4:05We we showcase loads of different technology at this
- 4:07podcast and I think people listen always interested how you
- 4:10end up with the underlying e-commerce platform you you
- 4:14ended up with big commerce and of course there's lots of other
- 4:16options in in B2B. So what was that selection
- 4:19process and what was the decision criteria that took you
- 4:21to BC? Yeah.
- 4:24So it's a great question. I think the the, I suppose the
- 4:27decision and the process and the strategy probably started
- 4:30earlier in the year even before I had joined.
- 4:33But I was speaking to Andy even in the March, before I joined in
- 4:36the June. But I think we're fairly set on
- 4:39going for a composable commerce. I'm going for kind of best and
- 4:43breed and I think and in a few others already had some good
- 4:46ideas on probably some of the tech and the companies we would
- 4:49maybe consider using. So we actually ended up going
- 4:52into an RFP process and a very structured process.
- 4:55We we defined all the requirements of what we needed
- 5:00and we hit it from our, you'll hear this one, all the tasks was
- 5:03MVP perspective. We know we had a year to do it.
- 5:06So what we didn't want to do was complicate it and add lots of
- 5:09bells and whistles onto the kind of existing functionality.
- 5:12We did a few things. So we wanted to keep it very,
- 5:15very similar functionality wise, but we just wanted it to work
- 5:19and be quicker and be able to check out.
- 5:21The previous system had a lot of kind of errors, things would
- 5:23fall down between systems and sometimes branches wouldn't even
- 5:27receive the orders. So we basically wanted something
- 5:31that did some basic e-commerce functionality but best in breed.
- 5:35So we kind of looked at various platforms we we wanted.
- 5:40We'd made a decision that we wanted to go with a digital
- 5:44experience platform, technology provider, so someone like a
- 5:48Bloomreach or Amplanes or other. So we looked at a few, we landed
- 5:53on Bloomreach because we felt it gave us a lot of the
- 5:56functionality we needed and it also gave us a digital marketing
- 5:59platform for all our SMS, ES and e-mail marketing and so on.
- 6:03So it meant we had one system we could actually join all the data
- 6:06together and that was quite important for us.
- 6:08Looking ahead to the future, we wanted a solid kind of back end
- 6:12or we looked at as a back end kind of functionality.
- 6:15So all you are ordering and checkout functionality wanted a
- 6:19really good solid system. So we looked at commerce tools,
- 6:22we looked at commerce and we looked at a few others and we
- 6:24were impressed the quite a lot over the market.
- 6:28But at the end of the day we looked I'm not sure we wanted to
- 6:31go through in with one of the the real large corporations and
- 6:35we didn't want to go into small. We felt kind of big commerce
- 6:37fitted our profile as well as I can imagine company a wee bit
- 6:42disruptive as NTMR and our industry and Bloom Beach as well
- 6:46And and it's like anything when you meet you meet your people
- 6:50you're trying to work out if you've got similar cultures to
- 6:52you and it's going to work. So culture is quite hard to
- 6:54define, but we looked at that with the people that we met and
- 6:59we insisted that we met the people we would work with.
- 7:01It wasn't just a sales team that turned up and then disappeared,
- 7:04and then a whole set of different people came.
- 7:06We actually met the people we would work with and that was
- 7:09important to us as part of the selection process.
- 7:13So that was Bloom Reach and and Big Commerce and View Storefront
- 7:16actually came to the table just a little bit later in the
- 7:18process and that came through. Obviously we were looking at
- 7:21system integrator as part of this to help us do this because
- 7:24we didn't have a full internal dev team at that point.
- 7:28We had product ownership, we had lead UX with a with a business
- 7:32analyst, we had a Scrum master. So we started to bring in the
- 7:36kind of framework of a team, but we never had anybody to actually
- 7:39do the coding. We wanted to work with a
- 7:42provider or sorry, a system integrator, a partner to help us
- 7:46pull it all together and build it.
- 7:49So as part of the selection process, we looked at technology
- 7:52platform providers and we also looked at system integrators
- 7:55that were partners of these companies.
- 7:58And then we pulled it all together, did all the commercial
- 8:00analysis, did all our scoring, very kind of individual scoring,
- 8:05pulling it all together, challenging each other on all
- 8:07our scoring. So we did it in a kind of proper
- 8:09rigid process and we wanted to do it properly.
- 8:12So that was it. It was basically an RFP process,
- 8:15meet the vendors, meet the partners, meet the people.
- 8:20And then another approach probably Fast forward and
- 8:22slightly the way we were able to structure commercial deals
- 8:25allowed us some flexibility that we spent first six to eight
- 8:29weeks of the project doing proof of concepts and getting all the
- 8:33requirements flushed out to make sure at the end of that phase
- 8:36everybody understood each other and that the three partners
- 8:40including View, Storefront because the way that was kind of
- 8:43presented is that that would get us quicker to market.
- 8:47So at the end of a kind of proof of concept, the discovery phase,
- 8:51we made the decision to progress forward into kind of an agile
- 8:54approach and using sprints. So that was our, that was our
- 8:57approach and you know from June to the end of kind of July into
- 9:02to August we made our decisions and we basically kicked off the
- 9:04project in September and basing from the September to the
- 9:08following August, the 31st of August to I think 536 in the
- 9:12evening we went live. Crown Peak enabling
- 9:16organisations to build meaningful digital experiences
- 9:19for everyone, everywhere. Engage your customers with our
- 9:22content management system, reach your entire audience with our
- 9:26digital accessibility and quality tools, and grow your
- 9:29brand with our product discovery solution.
- 9:32Find out more at crownpeak.com. I think it's sometimes it's
- 9:36quite nice. You said about you had just over
- 9:38a year before end of life. Having a fixed time frame I
- 9:41think can be really helpful with scoping because often when I
- 9:44work with quite a few businesses where they don't have a
- 9:46commercial need to be live on any particular day and trying to
- 9:49get stakeholders to focus on what's important becomes harder
- 9:53because it's like, Oh yeah, but we can, we can do more, we can
- 9:55do more. Now you get this endless creep,
- 9:57creep, creep and people not focusing on what's critical for
- 10:00business. So did you find that that having
- 10:03that date in mind helped sharpen you in terms of project project
- 10:06definition and helped to manage? Yeah, told.
- 10:08Them to be honest, totally agree.
- 10:12Now I kind of mean this slightly flippantly, but would I have
- 10:14taken the job if I didn't have a fixed timeline?
- 10:17I'm not. I would have thought about it a
- 10:18bit more, but I love the idea that we had a fixed timeline
- 10:22because what that meant is it crystallized just thinking and
- 10:25it didn't allow you because I think probably I couldn't tell
- 10:29you the stats on IT of digital project.
- 10:31But I think one of the major reasons projects don't get over
- 10:34the line is that people keep adding scope and all the time
- 10:37and you keep adding scope, you add complexity and you never get
- 10:40live. We had a great mindset and that
- 10:43came from our CEO key downwards as we had empowerment to kind of
- 10:47get on with the project having the right support and our kind
- 10:52of steering committee and our board to give us the right
- 10:55support and guidance. But effectively my Product owner
- 10:59part was empowered to make the decisions.
- 11:01It didn't involve committees of five different people of five
- 11:05different levels. We cracked on if we needed help.
- 11:08We had a governance structure there to escalate to or ask for
- 11:11assistance and it's it's all about empowerment for me.
- 11:15Give the product the owner empowerment.
- 11:17Don't constrain yourself with small budget decisions and with
- 11:21that flexibility that allowed us to get over the line.
- 11:28So yeah, I would definitely put it down to go for an MVP
- 11:31approach. Do not be scared to getting
- 11:33something out there. Now we had a little advantage.
- 11:36Just suppose it's what we had there wasn't it wasn't great.
- 11:40Our whole business is not dependent on on online.
- 11:43We're not pureplay business. We're our people business.
- 11:46Most the majority of our transactions happen in branch
- 11:49and will continue to happen in branch to be honest with you.
- 11:52Our e-commerce is is kind of as a short window, it's it's tools
- 11:55for the trade, it's kind of a little enhancement of of MKM.
- 11:59So we had flexibility to go for The Big Bang approach.
- 12:02We didn't have a multi country deployment.
- 12:05We weren't 70% of our sales on the line.
- 12:08We could actually go for it in a way that you could build.
- 12:11We had the best of both worlds. If we did a little bit of
- 12:13waterfall at the start, then you're into agile sprints.
- 12:16You make your decisions, you test and then you go Big Bang,
- 12:20switch the old one off, put the new one on.
- 12:23We didn't have to worry about double integrations, all of that
- 12:27kind of stuff. We made the decision, it was
- 12:29quite clean, but that came from the right decision making,
- 12:33empowerment, mindset and culture and MKM and department and.
- 12:39I guess with a big comments, you have the option of going down
- 12:42the headless route or using their own kind of framework,
- 12:47unlike at the time commerce tools.
- 12:49If you're evaluating against that, like what was the driver
- 12:52around the headless side? And I guess, you know, there's
- 12:56obviously a lot of noise in the market around pros and cons of
- 13:00headless and I think because there's always going to be
- 13:03overheads, but like what was the driver behind the headless
- 13:06route? Yeah.
- 13:07So I think, I think it was looking at the best in breed
- 13:10mentality and that's not saying I think big commerce has got so
- 13:14much in the system that we that we don't use and there's stuff
- 13:16been added to that platform since we've gone live.
- 13:19But I think we were fairly set that we wanted a separate
- 13:22digital experience platform like a Bloom Reach.
- 13:26So that had kind of search, search and merch, all of CMS all
- 13:30are kind of automated marketing all within that that kind of
- 13:34that system balloon reach and big Commerce are partners.
- 13:38You know I think they've done work before the the API
- 13:41connectors are there, you know, so we we cannot, I mean I would
- 13:45never believe anybody that says to me that that composable
- 13:48commerce is simply like just plug and play in your way.
- 13:51It's all about the plumbing and wiring and the complexity of the
- 13:54business you're working with as well.
- 13:55We we're quite a complex business with regards to our
- 13:58setup. You know, we've got 124
- 14:00websites, 125 websites. It's like a website for each
- 14:04branch. So every branch has, you know,
- 14:06pricing for local markets, but that's what makes MKM
- 14:09successful. But we had to obviously spend a
- 14:12lot of time making sure the plumbing and wiring of all of
- 14:14these systems with our ERP and that was one of the main things
- 14:18that they all talked to each other and the data flows and we
- 14:21feel we've got a really robust architecture with regards to
- 14:24that, that that could allow us to swap if we wanted to.
- 14:28So let's say in the future we wanted to swap out and do
- 14:30something different. We could.
- 14:32Now again, it's not just lift it out and put another one in
- 14:34within three days. I think you're always going to
- 14:37have to undo some of your plumbing and wiring if you're
- 14:39doing composable colors, but it allows you to do that.
- 14:42You're not sucked into one provider that gives you
- 14:45everything and you're stuck to that one road map.
- 14:48And there's pros and cons for both setups.
- 14:50And a monolithic approach is not wrong either, right?
- 14:53It all comes down to the business and what you want.
- 14:57You might just want one system and one supplier that does your
- 15:00business. There's nothing wrong with that
- 15:02and I would never can add. I would advocate if if
- 15:05composable commerce allows is in the mindset of your business and
- 15:10you need some of that complexity and flexibility in your
- 15:13business. It it it's a good thing.
- 15:16It certainly worked for us, but you could do pros and cons till
- 15:19the cows come home on both of these setups.
- 15:22But we we believe it works for us and it was something new.
- 15:26You know, I've done monolithic stuff before and every project
- 15:32you can learn and you build as you go through your careers at I
- 15:35think composable commerce from now where it's at the industry,
- 15:38I mean the the Mac alliance in Amsterdam, the industry's
- 15:41massive on it. You see the partners, you see
- 15:43the relationships there. It's a movement.
- 15:49But yeah, I think it was the. To answer the original point,
- 15:51Paul Beck is allowing you the flexibility to what you believe
- 15:54for your business is best. In breed.
- 15:56Elastic Path is on a mission to breakthrough the barriers that
- 15:59prevent commerce leaders from delivering extraordinary
- 16:02shopping experiences. Both business and tech teams are
- 16:05able to innovate on their own terms, fully embrace
- 16:08composability and in turn never compromise on what's possible.
- 16:13Learn more at www.elasticpath.com.
- 16:17Yeah, absolutely. I think your business is
- 16:20probably better suited to composable than some of the
- 16:23other businesses we've had on the podcast where you've
- 16:26obviously got complexity around pricing and the branches and
- 16:29like different experiences etcetera.
- 16:31Yes. And I guess that kind of takes
- 16:34me on to my next question. See, we've mentioned Bloom Reach
- 16:37a few times and you've talked about that being an important
- 16:40part of the STACK. Can you just talk us through
- 16:42like the impact of their DXP to your kind of operational teams
- 16:47and how they've been able to like that merchandise and
- 16:50personalize and yeah. So I think I would say we have,
- 16:55we're not using it to fuel potential yet.
- 16:58Yeah, we've spent, you know we got live, we've been
- 17:01stabilizing, We've been focusing on some key road map items and
- 17:04some hygiene on our site where we've had some really good
- 17:08sessions with Bloom Reach recently where we've kind of
- 17:10walked through our strategy of what we want.
- 17:14And there's a bunch of actions agreed that we need to can
- 17:17undertake before we really really kind of sweat the asset
- 17:22that we've got. We feel we've really got the
- 17:24fundamentals there for Bloom Leach to allow what we want to
- 17:27do. And it will be personalizing it
- 17:28in a way that allows you to personalize based on the type of
- 17:33person that logs into your website, could be a retail
- 17:35customer, it could be a large, a large building company, could be
- 17:43a kind of four or five man band that you want certain products
- 17:49and certain experiences on the site.
- 17:51We've still got a lot of work to do and that that we believe
- 17:53we've got the fundamentals in place and the foundations in
- 17:57place and that that was our main drive over year one was to make
- 18:01sure we get our data layer, get everything kind of geared up and
- 18:05then start to switch on the different, the different
- 18:07components. But we're already using Blue
- 18:09Reach to Pastelise a lot of our SMSESA lot of our e-mail
- 18:14marketing approaches based on, you know, the customer type, the
- 18:17things that the buy and so on. So we're already using it, but
- 18:20there's a lot more we can use Bloom Reach for that we've not
- 18:23used it for yet. Good.
- 18:28A kind of related question around CRM because it's
- 18:31obviously CRM is a big thing in B2B in account management,
- 18:35whether it's about sales teams, managing pipelines or customers,
- 18:38been able to raise multiple quotes because they've got
- 18:41different projects especially in the building trade.
- 18:44How do you handle CRM? Like what system you know?
- 18:47Is it a mature setup? Are you just starting what
- 18:49systems to use? How they connected?
- 18:54Yeah. So I think you could argue, I
- 18:55would just start, we don't have, we've not justified the need at
- 18:58this point that we need a separate CRM full technology
- 19:02stack at the moment. We've got enough data in our ERP
- 19:07and the way that's set up, the way we bring that data or ERP
- 19:10and how we analyse that internally gives us all our
- 19:12customer data. And actually we're starting to
- 19:15use a bit of Bloom reach, you could argue for a bit of that as
- 19:18well. But we're still, we're still
- 19:20probably on the doors and still maturing through that process.
- 19:23But we feel we've got enough for now.
- 19:25It might be something that we look at in the future as we kind
- 19:28of mature digitally as a business, but we basically rely
- 19:33a lot on our ERP customer data, how that's brought into our
- 19:36internal, it's our own internal systems that we've got for CRM
- 19:41and that kind of mixed in with with Bloom Reach Intelligence
- 19:44that kind of gives us what we need just now Are you?
- 19:48Using any of big commerce's like quote engine because that's
- 19:52something that's one of the their big selling points in the
- 19:55SAS space of B to B. Or is it just not a core part of
- 19:57your model? Not a court.
- 20:00We've not used that functionality yet, but we are.
- 20:02There's various things we're looking at on our site to do
- 20:05with kind of quotes and templates.
- 20:07All of that stuff's on our road map.
- 20:10I mean we've got a road map that's you know that's the
- 20:12freelance of this room of ideas but you know we're we're
- 20:17probably we're still I would still say we're early doors and
- 20:20the maturity of a new system. You know we were the first in
- 20:23the world to put in that combination and we've settled
- 20:26down. I'm not going to go into revenue
- 20:28figures, but you know the revenue going through the the
- 20:31website, it's kind of double trickle since we've kind of gone
- 20:35live and we continue to see growth, but there's so much more
- 20:38that we can probably do on the site.
- 20:41But it's a Germany and you've got to kind of balance that with
- 20:45with the rest of your business priorities as well.
- 20:48You know, we're not a pureplay business.
- 20:50Yeah, yeah, that might make sense.
- 20:52There's only so much you can do, right?
- 20:54And there's that prioritisation is a a big skill set in robots.
- 20:57But so let's that brings us some nice actually because we talked
- 21:00about the the technology stack around Big Commerce and Bloom
- 21:03Reach and why you got to that point.
- 21:05Let's talk about the project piece because this is a bit with
- 21:08my exceptionally dull project and process focused mindset.
- 21:13I love to hear about how people approach you, what issues
- 21:16they've had, you know, what they've learned during it.
- 21:18So I'd love to know because you were going from a legacy stack
- 21:20into a new like composable set up with with a new e-commerce
- 21:24engine and new DXP. What were some of the the the
- 21:27all the key technical challenges that you and the team faced
- 21:30making that transition or anything say around like did you
- 21:33have to pivot resourcing or internal models?
- 21:38Yeah. So no, it's a great, a great
- 21:39question. So I think we went into this
- 21:41with our system integrating our partners with a very clear
- 21:44strategy that we would use RSI to help us build a the solution
- 21:51and get live. But while we were doing that, we
- 21:54were going to start bringing in our own developers as well, in
- 21:57our own time and we did that slowly.
- 21:59We didn't want to just turn up. All of a sudden you've got six
- 22:01of your own developers and you throw them over in the middle of
- 22:04a project. I don't think that's the right
- 22:05way of doing it. You you pick an SI because you
- 22:09trust them and that they can pull things together for you.
- 22:12So we went into that where really open relationship with
- 22:16regards to. They also helped us interview
- 22:18one or two devs as we brought them into the door.
- 22:21So there was a flexibility on the people.
- 22:23So it wasn't a threat to either party.
- 22:25All of a sudden you just turned up with your own days.
- 22:26You didn't tell them about it. We actually went into that with
- 22:29that kind of open open thinking we did.
- 22:34I would definitely encourage people to do a a discovery
- 22:37phase. You know, there's not again not
- 22:40come from, you know, I think we all do if we were kind of
- 22:43working in technology 30 years ago.
- 22:45You know, Agiles existed for over over that amount of time,
- 22:48but only I would say in the last 1015 years of kind of company
- 22:52started to move more towards that.
- 22:54Again, there's nothing wrong with a waterfall process either
- 22:57if it's used for the right type of thing.
- 23:01So I've done some agile transformation.
- 23:03I'm not an agile evangelist, certainly not.
- 23:07It's about picking the right kind of methods and frameworks
- 23:10for what works for you. So I would definitely encourage
- 23:12people to really nail down once you've kind of sight agree as
- 23:16you agree your contracts has really worked through the
- 23:19requirements and flush everything.
- 23:20That's what everybody said on paper they can do is use our use
- 23:25our a month or two to do a bit of a discovery piece proof of
- 23:28concept. The big thing we wanted to prove
- 23:31was could these systems deal with the pricing complexity we
- 23:34have as a business. Yeah.
- 23:36So every branch can have their own pricing.
- 23:39People with customers within that branch can have different
- 23:42pricing as well. You know a hammer that costs £10
- 23:46in Kirkcaldy might be £9.58 and hope it all kind of gives the
- 23:53the business the flexibility to have products and pricing for
- 23:57the local market. That's what makes MKM different,
- 24:01disruptive and successful. So we wanted to test that out to
- 24:06make sure our ERP could talk to the the systems we were looking
- 24:11at big Commerce coming through View Storefront and Bloom Reach.
- 24:16So we did some mini proof of concepts through the 8 weeks and
- 24:19we basically did lots of workshops to really have
- 24:22conversations about your requirements and work them
- 24:24through. And then at the end of that
- 24:26phase you built confidence that you could do it.
- 24:29Then the approach was two weeks sprints and basically we had a
- 24:33say on what we also were influenced or we could influence
- 24:37what we worked on. But you would take the leaf from
- 24:39your SI or your partner. So we kind of went through you
- 24:44know, I can't even remember how many sprints now 1314 sprints
- 24:48and then you go into integration test phase, then you moved into,
- 24:51then you did more into the waterfall world.
- 24:53Now you've kind of done all your your agile building and then you
- 24:56move into an end to end integration and then an end to
- 24:59end UAT making sure the business are involved and safe.
- 25:02So we did all of that. We did have a challenge midway
- 25:05through the project in February. I think we had some optimistic
- 25:08timelines of trying to go live and earlier than than than
- 25:12August. But our our internally at MKM
- 25:15August was the day that was not worst case.
- 25:19It was actually a marriage day that we thought it would take.
- 25:22There was some optimistic views that we could go earlier than
- 25:25that. We did aim for it, but we didn't
- 25:28do it and to be fair, our SI probably February time.
- 25:32I think I basically acknowledged there was an issue with the
- 25:35performance of the back end. The way maybe some of it had
- 25:39been built and architected wasn't quite right, but they
- 25:44put, they put their hands up, they worked with us, we did some
- 25:47refactoring, We worked through it.
- 25:49You could have left it and we could have probably got live,
- 25:52but I think we would have paid the price.
- 25:54Yeah. And they were brilliant enough
- 25:56to kind of say right, this isn't right, we're going to have to
- 25:58work on this and we find. So we probably spent another 4
- 26:01to 8 weeks reworking a bunch of stuff.
- 26:04But because we had built up that collaborative relationship,
- 26:08there wasn't any shouting or screaming or accusations or
- 26:10anything like that. It was right.
- 26:12How do we solve it? How do we work together?
- 26:15And that's what this project allowed the teams to do at
- 26:17plenty FaceTime. Lots of calls.
- 26:21And I mean there was some humbling stuff on this project.
- 26:23Some of these, some of these guys and girls were working in
- 26:26Ukraine. The Ukraine crisis kicked off.
- 26:30We dealt with Russian and Russia invading Ukraine.
- 26:33During the project, you're dealing with people and it was
- 26:36like you're trying to make these, these guys are wanting to
- 26:38work and you're like, wow. And like never did we ever see
- 26:42timelines and we would. Whatever was happening, people
- 26:45were far more important than what we were doing as a project.
- 26:48The partners dealt with the people brilliantly and the
- 26:50people who worked on the project worked through a lot of stuff as
- 26:53well. Move different locations
- 26:55somewhere. Partners help people out.
- 26:57So there was certainly an outside things that influenced
- 27:00the project. But I'm so impressed with the
- 27:02ethics of the companies that we worked with as well.
- 27:06And that for me was far more important than than anything
- 27:09else. And relationships were built
- 27:12else and you know, all rosy. It was hard.
- 27:14It was a hard project but the relationships and trust was
- 27:18there. So to answer your question like
- 27:21mixture of real good due diligence at the start and still
- 27:24we find something wrong in the middle because you usually
- 27:26always do. It was going really well.
- 27:28We were all, I was waiting, I was almost waiting for something
- 27:30to go wrong. It was too perfect for
- 27:33technology project and we faced the challenge and we fixed it.
- 27:38Everybody put their hands up and they collaboratively worked with
- 27:40each other and that's that's the big thing for me.
- 27:43Great. And I guess you've talked about
- 27:46kind of working with the SI and adopting Agile and you know
- 27:50working in Sprint, obviously you're well.
- 27:52Your background is program management and then you've got
- 27:55kind of you've got multiple vendors here, you've got the
- 27:58back office side, the integrations between the
- 28:00systems. Like how did you kind of go
- 28:04about managing this project internally and then what advice
- 28:08would you have for kind of like people that are approaching a
- 28:10large like transformation project?
- 28:12Like, yeah, so I think the the big thing for me is to make sure
- 28:16your governance is clear, roles and responsibilities are clear.
- 28:20You invest a lot of time at that at the start.
- 28:23You never go back to that document to check it.
- 28:25If you have to go back to the document to check people's roles
- 28:27and responsibilities, you've probably got a problem.
- 28:29Yeah, it's like going back to contracts.
- 28:31Once a contracts signed and done, you should never have to
- 28:33go back. If you're pulling out a contract
- 28:35to look at stuff, you've got a problem.
- 28:36Yeah, I don't remember that once in the project, but it was all
- 28:40about getting roles and responsibilities agreed across
- 28:44the team and then the support levels of the project.
- 28:47So we had senior stakeholder, regular calls across Bloom,
- 28:52Reach, Big Commerce, View, Storefront, Brave Bison and Us.
- 28:58We had a regular. I think if we needed it, it was
- 29:01weekly. If it was biweekly and then you
- 29:02maybe have a month and it was all short and sweet.
- 29:04It wasn't. And if we didn't need it, we
- 29:06didn't do it, Yeah, but what we had is we had a formal place to
- 29:10discuss the key issues and risks and senior stakeholders from
- 29:14these organizations in these calls to help unblock the teams.
- 29:19We also had integrated kind of Slack channel for the team
- 29:23members and for senior stakeholders so we could all
- 29:25communicate through Slack if we needed to.
- 29:28So having one platform, you can all actually communicate with
- 29:31each other instead of waiting for a meeting or people sending
- 29:3440 million emails to each other, actually cutting through having
- 29:38some comms channel for people to talk on.
- 29:41So I think that cut through a lot of stuff for us.
- 29:44So roles and responsibilities, communication, have governance
- 29:47out, but don't make it complicated, don't make it
- 29:50bureaucratic is have enough there to support the team.
- 29:54It sounds basic when I talk it out, but some people maybe
- 29:56forget that stuff. So I think good old Steven, old
- 29:59fashioned is just have a good structure in place.
- 30:01If you've got a structure in place, you can break that
- 30:03structure if you want, but at least you're breaking a process
- 30:06in a structure rather than making up as you go.
- 30:10Great. And then I guess this is quite a
- 30:12broad question, particularly all those kind of variables I
- 30:15mentioned a second ago, but what were like your biggest learnings
- 30:19if you were starting the same project again tomorrow, What
- 30:22would you do differently? Yeah, it's a great question.
- 30:27So I think like anything, because you've got a burning
- 30:31platform, you have to go at peace, right?
- 30:35If I had the perfect set up and I had more time, I probably
- 30:41would have invested more time and product data and getting
- 30:43your product data right. Yeah, make sure you've got the
- 30:45right technology for that. I would also invest the time.
- 30:50I'm a believer that it's like outsourcing, insourcing, using
- 30:55UK teams, offshore teams, doing things in house.
- 30:58There's pros and cons to every which we do.
- 31:02I was a firm believer that as MKM we're at people business,
- 31:05that we had ownership of some key robes and that we had a
- 31:08vision that we would build our own end host team eventually
- 31:12like in Fool. So I've got my first, I've kind
- 31:14of got my own development team now, but we also have partners
- 31:19that we can flex up with as well.
- 31:21So I think for me that's the perfect model for us.
- 31:24I'm not saying everybody else has to do that.
- 31:26Building your own teams brings the challenges that people
- 31:28leave. You got to recruit and so on.
- 31:30So there's it doesn't matter which way you do it, there's
- 31:32always challenges. What would they do differently?
- 31:36If I had more time, I maybe would have built some more of my
- 31:39own internal devs as well and done it purely hybrid all the
- 31:43way through. But I didn't have that luxury.
- 31:46We didn't have the luxury of getting a product data.
- 31:48Absolutely so. And if I had that I would have
- 31:51done that first then I would have re platform but it didn't
- 31:55hold us back. You know we had the flexibility.
- 31:57We've added products since we've gone live.
- 31:59We've enriched product data since we've gone live.
- 32:01So it's it's there's more disasters here.
- 32:05I think the other thing is really pay close attention to
- 32:10SEO and moving from one platform to another.
- 32:14We made a few, call them, yeah, I think we made a few errors in
- 32:18in approaches across our teams or SEO, but we recovered it.
- 32:25We didn't get the migration right.
- 32:27So it probably should have been a bit more attention to that.
- 32:31But again, it wasn't dramatic for us based on the the, I
- 32:37suppose the spend on the website and the dependency of a website
- 32:40for our business. Yeah.
- 32:43Also look at how Google core web vitals interrogates your site
- 32:49and how it tells you how you're doing.
- 32:51Yeah, really pay attention and a lot of that and you can't figure
- 32:54out until you've gone live and we've been, we've been looking
- 32:57at that in quite a big way. But I would just look at SEO or
- 33:01look at Google web vitals, look at the surrounded things that
- 33:05help your projects. Not that we weren't looking at
- 33:07them, but I don't think we had the capacity and the focus to
- 33:11really, really look at these areas.
- 33:13We were very focused on getting the technology solution live on
- 33:16time because it's a burning platform.
- 33:19There's not many things I could change or make different
- 33:21decisions on in the time that we had.
- 33:24But having the time to focus you I think really helped us as
- 33:28well. I think if we hadn't had
- 33:31abundant platform, you could spend 2 years doing this stuff
- 33:34and not go live. So there's no perfection, but
- 33:39Lehmann's definitely on SEO for sure.
- 33:45Yeah, it's it's interesting that that whole MVP thing really, it
- 33:49really helps. I've done this with so many
- 33:51clients and the projects where they just you know that they're
- 33:54going to end up taking too long to get live because everyone
- 33:57wants everything in scope and having to get people at at the
- 34:01scene level to to define what MVP is what it means the
- 34:05business operationally and customer facing wise.
- 34:08It helps massively because you then you've got that, as you
- 34:12said, nothing's perfect, right? But then at least you've got
- 34:14criteria to come back to and say does that meet the criteria for
- 34:17MVP? Yes.
- 34:18No. Great.
- 34:18OK, we are sensible decision. I've got one last.
- 34:22Question actually. Oh, sorry.
- 34:24No, I was going to say one last thing and it's, it's what we did
- 34:28well and it's what other businesses among was kind of
- 34:30stating the obvious here. But you have to build a good
- 34:32collaborative effort over your business and especially if
- 34:35you've got a digital team in an IT organization, a lot IT
- 34:38organizations, they own the ERP, they understand the integration
- 34:42that got great people. And that's what what we did is
- 34:44we engaged the IT team right from the start that were
- 34:47involved. That wasn't an afterthought.
- 34:49Oh, by the way, we need to do integration to the ERP six
- 34:52months and project. I've had projects doing that
- 34:54before. Engage your stakeholders right
- 34:57from the start, finance, commercial, IT, procurement,
- 35:02anybody that works with that system is get stakeholders
- 35:06involved at the right time, but as early as possible.
- 35:10And that's what that's what we did because we're at, we're a
- 35:12really good people business and we're a good lien setup that
- 35:16allows that to happen. We're not got layers and layers
- 35:19of bureaucracy, we just cut through stuff and get it done.
- 35:23Yeah, that's so important and the the added benefit of that is
- 35:27you can establish red lines very early on in terms of what far
- 35:30what you can and cannot do from a finance point of view.
- 35:33We've had people had this in other projects where it's well
- 35:35actually you know it is it fixed your payment provider, is there
- 35:40flexibility to change? Are there the red lines that the
- 35:42ECO project has to work within so it doesn't end up presenting
- 35:47something that another state will then just?
- 35:48Bats it away, yeah. Yeah.
- 35:50And we, we did that financial involved from the start.
- 35:53We talked about the payments provider on the site, fraud
- 35:56check and all of that. We renewed a lot of that start
- 35:59the project and the strategy and approach.
- 36:02Yeah, excellent. I got one question coming back
- 36:04to the the you said you're building an internal dev folk
- 36:07show you you led more heavily at the start of the agency and I
- 36:13find this bit fascinating because lots of businesses go
- 36:15down this route. Some want to build out only
- 36:18front end, others want to take whole responses to everything
- 36:21and and hybrid set ups bring additional challenges around
- 36:23release management because you got two different teams managing
- 36:27code branches. I'd love to know however you
- 36:29approach that, are you? Is your dev team focused purely
- 36:31on like view the DXB in the front end piece or are you also
- 36:36taking ownership of like integrations?
- 36:39OK. And what?
- 36:41What was the what was the rationale then?
- 36:43What? What was your desire to own the
- 36:45whole thing in house rather than having an agency to?
- 36:49Yeah. So I think because of our, I
- 36:52suppose of the composable com ourselves, the big important
- 36:54thing for us is the plummet and wire and the plummet and wire
- 36:57and sit in a kind of middle layer back end.
- 37:00So who can all the systems together, the transactional
- 37:02data, I think it's absolutely key that we as MKM understand
- 37:06how that works because we work really closely with our IT team
- 37:10and all the ERP data that feeds that back in the middle layer is
- 37:13very, very well understood by our IT department as well.
- 37:16So it doesn't make much sense to have an agency for us to do
- 37:20that. I think.
- 37:23Not that you've asked me this question, what would it
- 37:24prioritise? Would it take the back end, full
- 37:27stack over the front end? I would rather understand the
- 37:31real nuts and bolts, the back end and how that communicates.
- 37:36The front end's super important for me as well.
- 37:38So because the front end and the UX experienced that has been
- 37:43driven by us, that was our staff.
- 37:45You know, I've got a lead UX and the UX UI resource in my team.
- 37:49The look and feel of that website is ours.
- 37:51It's M Cam's branding. It's our look and feel.
- 37:54We drove a lot of that. So it kind of makes no sense for
- 37:57me to separate them all and just say I want back end, front end
- 38:01or not. So we've decided that we'll
- 38:03split our dev team. The way you work is suppose
- 38:06we've got full stack devs, so a lot of full stack devs, a lot of
- 38:10them are back end focused, but they can do front end.
- 38:14So we've got resources that can do a bit of both but maybe more
- 38:16experienced in the back end. And we've got kind of a couple
- 38:19of front end resources as well that are focused on the front
- 38:22end and we've got lead UX and everything in house as well.
- 38:26So we didn't see a need for separating.
- 38:30We kind of want, we want to have an understanding of it all but
- 38:33we've got an agency that works with us that have done both
- 38:36these bits as well. So if we wanted to flex up front
- 38:39end or the back end or what, we've got that skill set with
- 38:42that partner and SI as well. And we've recently we've
- 38:47obviously we've now moved, we've got through all the CICD
- 38:51pipeline, all our release processes that's all MKM, no,
- 38:56but if somebody we would have a partner that can, we've got the
- 38:59flexibility that a partner could work with in that environment
- 39:02now that we we've now got ownership of all of that.
- 39:07Interesting. Thanks.
- 39:09Yeah, that's that's all the key questions you want to answer.
- 39:11Really interesting to hear that I, I, I love the stories of when
- 39:14people decide to bring in house and how they manage their
- 39:16development teams. Absolutely.
- 39:17Craig really appreciate you taking the time to come on the
- 39:19podcast. Really enjoyed talking to you
- 39:21today and also good luck with everything.
- 39:24Good luck with the ongoing Rd. but releasing and and thanks
- 39:27everyone for listening. Hope you enjoyed the episode as
- 39:30well. Keep you open for the next
- 39:32episode we drop on every week and don't forget to give us that
- 39:34rating before you go. Thanks everybody Until next
- 39:36time. For more information on this
- 39:47topic, head over to Re Platform dot FM for our audio podcasts to
- 39:51discuss a project. Or if you'd like to chat about
- 39:53any of the topics covered in this episode in more detail,
- 39:55please reach out to myself, James Kurd, or my Co host Paul
- 39:58Rogers via LinkedIn and Twitter. Thanks again for listening and
- 40:01keep your ears peeled for the next episode.