Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP337:What Role Should An Ecommerce Consultant Play in Website Migrations & How Do You Ensure They Add Value?
Transcript
- 0:05You listen to Inside Commerce, the weekly ecom strategy,
- 0:07technology and CX Focus podcast hosted by experienced digital
- 0:10consultants and re platform specialist James Get and Paul
- 0:12Rogers. Get insights into ecom strategy,
- 0:14leading brands, hear from industry thought leaders and
- 0:17leading tech vendors with practical advice to help you
- 0:19improve your online CX. This podcast is sponsored by
- 0:24Worldpay and we've got a really useful topic that we're going to
- 0:28talk about today. And I'll introduce the guests in
- 0:30a moment and let them introduce themselves.
- 0:32But looking at what role Necom Consultant plays in website
- 0:35migrations and where they add value out.
- 0:36I'm an independent consultant. I've been doing this for years.
- 0:38Paul, who's not the podcast today, and I've worked on many
- 0:42projects together and hence why I've brought into the senior
- 0:44people from his team who do this role across a wide range of
- 0:48clients. Because what we wanted to talk
- 0:50about is why, Why we do consultants exist and when do
- 0:53you need them when you don't? But more importantly, what the
- 0:56things that can go wrong in projects if you don't have
- 0:58somebody who's got the expertise.
- 1:00So a warm welcome to Sham and Frankie today.
- 1:03How are you ladies? Good.
- 1:05Thank you. First podcast.
- 1:08I know this is exciting and you're going to love it.
- 1:10You're going to want to do more podcast stuff as Frankie, I
- 1:12guarantee it. We finally got our spanking
- 1:15about work, so it's just taking a while.
- 1:16But don't worry, we've got our. Yes, so for this Shamela, I've
- 1:20talked about this many, many times and I never got around to
- 1:23organising it because I'm useless.
- 1:25So now we're actually talking about this.
- 1:26So let before we get into the, the, the questions for those
- 1:30listening, what we're going to talk about, say things about the
- 1:31classic issues people face in teams, the mortgage gaps and how
- 1:35like a consultant can help the teams work better.
- 1:37The skills you need from a consultant.
- 1:39Because if you are planning to spend money on a consultant, you
- 1:41need to know you've got the right skill set and not just
- 1:43bringing somebody in for the sake of it.
- 1:45So we've got a lot of really valuable things.
- 1:47Well, let's go first in terms of institution, who you are and
- 1:50what you do and your sort of brand you've worked with.
- 1:52I'll, I'll start. Yeah, I'm Sham, Operations
- 1:56Director at Revant, although that title is not really true.
- 2:00I've been here since the start, so I've just been given a label.
- 2:03Yeah, we I work on the E com side of the business and we do a
- 2:08variety of services on our side including migrations, which is
- 2:12probably the biggest service that we do or at least like most
- 2:15commonly known one that we do. So yeah, full managed service,
- 2:18end to end of re platforming projects and I've now stepped
- 2:23down from delivery only last year, but although we do get
- 2:29dragged into into some of them. And then, yeah, I've got Frankie
- 2:31on my team, but I'll let Frankie introduce herself.
- 2:34I'm Frankie, Econ consultant on the Vivant team.
- 2:38I've been here for just over 4 years so my role really crosses
- 2:42over all of our services. So from audits to retainers,
- 2:48redesigns and RE platforms as well.
- 2:52Some of the clients that we work with include Timex, Stucie, Oka,
- 2:59Frankie Shop, so it really goes across loads of different
- 3:03verticals but predominantly the premium fashion, beauty and
- 3:07lifestyle space. Yeah, This is why I think
- 3:10today's going to be a really fun conversation because we I work
- 3:12in in slightly different client bases, although there is some
- 3:16cross saver. I have worked with Ivan on on a
- 3:18few projects over the years, but I think that breadth across
- 3:20different business types is really useful for people to
- 3:23understand. But let's let's, I think, let's
- 3:27set the scene first. I think it'd be useful because
- 3:29how do you approach RE platform? Because I know the one of the
- 3:33one of the things I really like about Vivonne is it's point of
- 3:35difference in the market and the skills that it brings rather a
- 3:38traditional agency. So do you want to talk about
- 3:41what is your viewpoint and approach to re platforming
- 3:44projects? On we platforms as well, I think
- 3:48the thing that we speak about a lot is, you know, agencies try
- 3:51to do this structured and standardised approach, right?
- 3:54And there's general 8020 rule when it comes to any project
- 3:59because we have to allow for scaling, right?
- 4:01But what we often find end up happening is every project is
- 4:05probably more like 2080, and like 80% of it is custom just
- 4:10because of the wants, needs, goals and requirements from
- 4:13every customer. And the different verticals
- 4:16might also add in another layer of complexity that we also need
- 4:18to consider. So yeah, every project is so
- 4:21different that we can't actually cut and paste anything.
- 4:23So you're starting from like zero.
- 4:25Well, yeah, not starting from far from zero anyway, for every
- 4:29project that we end up taking on.
- 4:32But yeah, Frankie's probably got a bit more like detail on our
- 4:36approach once we've actually engaged with the customer.
- 4:40Yes, I think one of the key ways that we definitely do stand out
- 4:43is that we really try to get a true understanding of the
- 4:47clients end goal so that we can really shape the project end to
- 4:52end. So that for us that means
- 4:55actually really getting a clearview of the team, exactly
- 4:59who we're working with, their strengths, their weaknesses and
- 5:03the internal challenges as well. So we do actually spend quite a
- 5:05long time getting to know the team, really understanding
- 5:09actually the challenges that each department has as well,
- 5:13because that will also help us to consult in a lot more
- 5:17transparent way. One of the ways that we do that
- 5:21is by doing a detailed requirements gathering at the
- 5:25beginning. So that actually goes beyond
- 5:27just doing a Moscow document. It's really actually in person
- 5:32sessions sitting with the teams to establish exactly what
- 5:35they're trying to achieve across the different departments, why
- 5:39different teams actually see the value in a migration.
- 5:44And that way we can give an accurate, an accurate and
- 5:48transparent view in terms of timeline and budget.
- 5:54And actually one of the things I missed is that we are really
- 5:57transparent with the client in terms of what they are going to
- 5:59get and what they're not going to get for their budget as well.
- 6:03So we're quite clear on what the scope allows and we will
- 6:08definitely try to to give them a realistic assessment of that.
- 6:13Yeah. I think what I always find
- 6:15interesting with re platforming projects is is when people go
- 6:20direct to an agency, but they haven't done what I call the pre
- 6:22discovery, which is basically what you've just articulated is
- 6:26the speed and time it takes for an agency to catch up with
- 6:30understanding the, the, the framing of a project in order to
- 6:33be able to then do proper technical discovery, which is
- 6:36the functional specification work.
- 6:38That there's that pre bit where you actually refining and you
- 6:42get the customer, the client in the right headspace to
- 6:45understand what the project is to them, what their framing is
- 6:48and what's driving it and how they're going to measure the
- 6:50success. Because I'm sure I know that you
- 6:52guys see us as well. And I've seen a lot of projects
- 6:54where there isn't an internal consensus and that would just
- 6:57create a muddled discovery, technical discovery of an
- 7:00agency. And that for me is one of the
- 7:01most critical parts before any discovery starts.
- 7:05The thing is like customers don't know what they don't know.
- 7:09And I think this is where the value is of using a consultancy
- 7:12or an agency. And I don't mean agency dev
- 7:15side. I mean an independent, you know,
- 7:17um, managed service agency because, um, it makes teams
- 7:22think about things in detail. And only once that thoughts on
- 7:26paper can you understand like a timeline for that specific area.
- 7:30And I think this is, this is the big things, the education piece,
- 7:32like what we usually get from a customer and when we first speak
- 7:36to them is a timeline and a budget.
- 7:38How can you give me a timeline on something that we don't have
- 7:40sight of? So this is what we are kind of
- 7:43doing is like educating them through like, right, you want
- 7:46this, let's work back from lunch day.
- 7:48These are the things that we need as a part of this delivery.
- 7:50This is what it realistically looks like.
- 7:53If you need that to be delivered faster, fine.
- 7:55But this is then what a version of that looks like that's
- 7:58getting them to agree on what that picture looks like end to
- 8:00end up front. And that pre discovery is so, so
- 8:03important because again, where they don't know what they don't
- 8:07know, it's usually after something's been signed.
- 8:11So proposals then agreed. You then go into a tech
- 8:13discovery with a dev agency, but only then are you having your
- 8:16first conversation. But you've already signed a
- 8:17proposal. So what have you signed?
- 8:19I don't think that is right out there in this sphere as a as a
- 8:25point. And you know, then that's where
- 8:27the the expectation, sorry, or the lack of expectation and
- 8:33understanding kind of comes into play and people get
- 8:35disappointed, right? Because they've signed off a
- 8:37project delivery And, you know, sometimes I don't even think
- 8:39they know that they're not getting the content loaded for
- 8:41them. Like that's what you'd expect,
- 8:43right? You've paid an agency to build
- 8:45your website. You think they're building a
- 8:46website. But I think what well, honestly
- 8:48is that they're building a theme.
- 8:50And I think that like lack of understanding and lack of
- 8:54education to a customer really like starts creating friction
- 8:57from day one. Ready to grow your business
- 8:59online? With World Pay e-commerce you
- 9:02can deliver fast, secure payments your customers love,
- 9:06backed by global reach and real people powered support.
- 9:10Scale with confidence and enhance your customers
- 9:13experience with World Pay E-commerce.
- 9:16Yeah, I think that's such a key point here is that is that so
- 9:20many people are moving from legacy tech into modern stacks.
- 9:26And, you know, regardless of what that may be, and I know you
- 9:29do a lot of work with shop fiber.
- 9:30You've worked with other platforms as well, whether it's
- 9:32a Shop Fi sensor, yeah, or a commerce, whoever it might be.
- 9:37And they take historical thinking into a new one.
- 9:40And you're right, if you don't have that expectation set, you
- 9:43get to the point where fragmented relationships occur
- 9:46because the expectation is completely out of line.
- 9:49And then also people get pissed off because they go, why are you
- 9:51charging me for this? Surely that should have been
- 9:54part of the core project and it's critical to nail that down.
- 9:57Yeah. Also often there's a line item
- 10:00for PM. I'm completely derailing this,
- 10:03aren't I? But there's a line item for PM
- 10:05from a dev agency side of AP NS actually took Selfer and their
- 10:08dev resource and they're a client facing person, yes, but
- 10:12they're not here to PM your internal team and your
- 10:15management of your deliverables. They're there to manage the web
- 10:18teams, deliver goals. And I think that lack of clarity
- 10:21already, you know, from the offset again creates that
- 10:22friction. And the full point of having
- 10:24like a managed service team and consultancy is to be able to
- 10:27like minimize that friction, create more of a seamless
- 10:30process end to end. And yeah, it's just, again, like
- 10:33I said, it's lack of education. We do migrations like in our
- 10:37sleep now, but it's taken a while to get here.
- 10:39And even then, like I said, it's 8020.
- 10:41There's there's times that we're even thrown in some projects
- 10:44because of a big gap, but we find like after scoping,
- 10:47scoping, scoping, you still find like little Evers of when
- 10:52something's too broad or too open in terms of scope, that's
- 10:55when it obviously just creates more noise.
- 10:57But yeah, we've had issues, I guess, across.
- 11:00There's not a seamless project we've had, and there'll be
- 11:03something that's happened alongside a project that takes,
- 11:05you know, a couple of weeks to like, unpick.
- 11:08Yeah, you. I don't think a seamless project
- 11:10exists. I think This is why it's so
- 11:13important to have that, that frame of the start and every
- 11:16conversation. I start with a new client,
- 11:17whether I'm doing an end to end like you guys or whether I'm
- 11:19just doing some consultancy around text selection and agency
- 11:22selection is is you're going to have problems.
- 11:25The platform won't be perfect. You're not going to fix all your
- 11:27problems. You're going to discover new
- 11:28ones. What are you willing to
- 11:30compromise and not because you have to have that conversation.
- 11:34Otherwise people go in thinking switching tech solves problems.
- 11:37And then other stakeholders in the business, whether it's
- 11:39customer service or retail, get really pissed off because the
- 11:42tech hasn't done what somebody is has told them would.
- 11:45And we all know that the vendors, you know, love, love
- 11:48them because they add a lot of value in many ways.
- 11:50But there's a lot of overzealous sales people out there who will
- 11:52tell you it will do everything. Yeah.
- 11:55From an agency perspective though as well, it feels from
- 11:59the dev agency perspective, obviously their goal is to read
- 12:05a spec and to make sure that they deliver against the spec.
- 12:08So where we come in is to make sure that actually we are
- 12:11picking holes in that and actually really trying to
- 12:13understand why someone is trying to do a particular feature or
- 12:17particular functionality. Is it actually going to be
- 12:19beneficial to the business. So that's why we do sit in the
- 12:22discovery sessions as well with the agency.
- 12:25And it does personally, I find it does take us a little bit of
- 12:30time to actually get the whole team of a client on board to how
- 12:35we add the value. And when they've seen us in a
- 12:37couple of sessions, they don't fully understand how we add the
- 12:40value. And obviously we've bridged the
- 12:41gap between the two. Yeah, I think, I think that's
- 12:45the the most selling point here is, is plug in gaps because we
- 12:48all know it. These projects are complex.
- 12:50They involve people and technology and people and
- 12:52technology are screwed. That's if we all are.
- 12:55The question is how do you minimise that screwiness so that
- 12:58you you minimise disruption and you keep projects on time and on
- 13:01budget. And as you did, this expanded on
- 13:04the classic issues clients face because sham you touched on one
- 13:07of the most same ones where I keep on these conversations with
- 13:10people about their budgets and PM and the expectation that or
- 13:14just actually general, we're going to give it to to Jane,
- 13:17she's going to look after the project, but she's not APM,
- 13:20she's not to ecom PM and she hasn't done a re platform in.
- 13:23You've now added a massive risk to your business.
- 13:26You need to budget. If you don't have an internal
- 13:27PMO, you need to budget for an A specialist, a contractor to come
- 13:31in for a period of time. And people underestimated, they
- 13:34get given the TCO model from somebody that's totally
- 13:37undercooked and then that creates an efficiency.
- 13:39So that is one of the others. What else are you both seeing in
- 13:43terms of issues client teams face?
- 13:46I mean, just to re re emphasize this like, again, they don't
- 13:50know what they don't know. So it's like not having true
- 13:52clarity on what they have to do versus what they need is a
- 13:57really big point. Again, we've done this a number
- 14:00of times. So we've seen we can figure out
- 14:03immediately based on the the initial requirements that they
- 14:06might have in play or the goals that they want to do.
- 14:08The first thing we ask is what size is your team?
- 14:11But I'll let like Frankie, maybe like speak more on this just in
- 14:15the day-to-day pulling. But yeah, they don't, they don't
- 14:17have true clarity what it is that they have, never mind what
- 14:20they need. And I think internal teams will
- 14:24not have the end to end view of the levers to pull.
- 14:28And I think that's definitely where we would add the value.
- 14:32The the other issue which you mentioned is that most teams
- 14:37have not actually managed immigration before.
- 14:39So they actually have no idea what is to come and all of the
- 14:43dependencies, the workload involved.
- 14:47And we more often than not get a team who has an ecom manager
- 14:52leading the project internally and that is obviously really
- 14:56challenging. They've got their day-to-day job
- 14:57to do as well. So it is also our role to
- 15:00educate on that. Another thing which kind of
- 15:04plays into that is stakeholder management.
- 15:07So a lot of people leading the project internally will not have
- 15:12the authority to tell people what to do.
- 15:15So for example, as an internal leader of this project, you will
- 15:20have to manage upwards and you might actually have to pull in
- 15:23your head of IT, you're head of finance and it's quite difficult
- 15:28for those people and often to tell people what to do to meet
- 15:32strict deadlines, etcetera. So we can often be that person
- 15:35till we want to be the the person who shouts in a meeting
- 15:41essentially. Carrot.
- 15:42And stick. Yes, Anthony.
- 15:45Neither you're going to call it Karen, but yes, that's that as
- 15:47well. Just on top of that as well that
- 15:51you know, what issues do they face?
- 15:53I think it's not necessarily again, something that they know
- 15:56they face that accountability. It is like the number one thing
- 15:59that I try and force from the first meeting.
- 16:02So everyone has to be in the meeting who's involved in either
- 16:05decision making or executing together.
- 16:08All cameras have to be on for that initial meet.
- 16:10Like I need to, I need to eyeball people, make sure that
- 16:13they're engaged. But that accountability piece is
- 16:16huge. And like we run different like
- 16:18weeklies and then monthly stereo calls.
- 16:20And again, that pulls in that accountability or reinforces
- 16:23that accountability in a project.
- 16:25But again, back to that budget piece, the lack of understanding
- 16:29and knowing how far that budget can actually take them and what
- 16:34they can get for it is a huge thing as well.
- 16:35So yeah, again, people will usually lean on us to allocate
- 16:38the budget accordingly and just to make sure that all the
- 16:42requirements or like launch critical launch critical
- 16:45requirements are met. And like often the none, you
- 16:48know, JGTM tracking SEO to massive, massive deliverables in
- 16:54any migration are usually not on on the table and they are a
- 16:57separate cost. We often like try to the
- 17:01outsource that is we don't have the skill set in the team to
- 17:03handle the even if they're not like SEO project might not
- 17:07necessarily be big, but the issues that can happen with SEO
- 17:10if you don't do it correctly, we can't take on that
- 17:13accountability with what our timings like are like finally as
- 17:17well. So we usually outsource that,
- 17:19but things like that aren't uneven, aren't even on people's
- 17:21radars. So yeah, we kind of force that
- 17:23kind of true end to end safe risk free delivery as a part of
- 17:29this as well. But they don't know the issues
- 17:30until they go live, right. So we just bring that forward.
- 17:34Yeah, the the the word that the word is governance basically.
- 17:37And Paul and I laugh at us a lot because I'm I'm quite dull.
- 17:40I love governance. Whereas he's obviously, yeah, we
- 17:45could be dull. See, that's why I paused on the
- 17:47podcast. He would have fallen the sleek
- 17:48when we talk about the governance side.
- 17:50So, but this to me is a critical bit.
- 17:52And I think this is where a lot of client teams do not have the
- 17:55understanding because you're right, the, the, the ownership
- 17:57there, there needs to be a senior decision maker who's at
- 18:00the C-Suite at the top table, who has the authority to make
- 18:04decisions and make people dedicated to project delivery.
- 18:08Because without that, people won't because their priorities
- 18:12are elsewhere. That is critical.
- 18:14But it's the, it's the classic racy stuff, isn't it?
- 18:16Is he, you know that every project, regardless of size, has
- 18:19specific roles that have to be satisfied.
- 18:22It just depends how big the stakeholder set is and who gets
- 18:24a sign and whether one person has three roles or each role is
- 18:27a different person. And then how you manage it.
- 18:30And if that's not defined up front and it and people aren't
- 18:33briefed on it and have bought into it and have been told they
- 18:35need to follow this, that's when it unravels later on.
- 18:39Yeah, yeah, it's. Good to be dull.
- 18:45Do you know what like that, Frankie, is like an exceptional
- 18:47level of compliant and like we need it.
- 18:49It's like in our team we've got like scrappy and really like
- 18:54strict in terms of like governance and process.
- 18:56And I think the mix is really valuable to us.
- 18:58However, obviously we lean towards a more documented side
- 19:01of things. But yeah, not every client's the
- 19:03same, not every team structure is the same, and not every team
- 19:06needs that level of like governance.
- 19:08But I guess that the stuff that we've been seeing over the last
- 19:11couple of years, it's just more stakeholder management.
- 19:14So we do need that kind of like level of like care and due
- 19:19diligence. Sweet.
- 19:23There's a balance as well between following a racy and
- 19:26following. You must do this and you must do
- 19:28that with a bit of hand holding and having empathy for the fact
- 19:34that most people wouldn't have done this before and they need
- 19:36that kind of pre step to actually educate them into why.
- 19:42And we found that actually to be the most effective because just
- 19:45dictating obviously a viral racy, it is important.
- 19:49But the hand holding bit is also, you know, really key to
- 19:53make sure you get the buy in because that is the hardest part
- 19:56I think. We're humans and there are
- 19:59humans and yeah, these you have to allow space for that
- 20:03conversation as well. Yeah, I completely agree that I
- 20:05guess I always come back to the point that I think, I think the
- 20:08the, the level of governments should never be compromised in
- 20:11any project. How you execute it and how you
- 20:14manage people and how you communicate.
- 20:15Obviously 100%, yeah, it varies massively depending on style and
- 20:19structure. But also what I think one of the
- 20:21hard challenges for consultants is you're coming into an
- 20:24existing culture. You've got to work.
- 20:27You said at the start, both of you, that you've got to work
- 20:29within an existing team. You've got to understand you've
- 20:31got to fit in seamlessly so you don't disrupt it, but inequally,
- 20:34you've got to counter negative behaviour that will disrupt a
- 20:38project by pointing out and that that won't work and why it won't
- 20:40work. And you've got to do it in a
- 20:42collaborative way so that people don't feel like you're saying
- 20:45you're rubbish. It's going to be very much like,
- 20:47let me help you succeed here, but this is going to cause this
- 20:50problem. Here's why.
- 20:52How do you find that? Because I think that's the
- 20:54delicate balancing act. Do you think we're paid enough,
- 20:57James? Comment Your honor, maybe I'll
- 21:02be a little bit of self promotional if I answer that
- 21:04question. Just from my perspective, I
- 21:08think it's about again showing the evidence of why someone
- 21:16needs to be accountable for certain things.
- 21:19So that would come from having a very clear layout of the
- 21:23milestones. So I'm just thinking for
- 21:25example, integrations. So on migration, obviously that
- 21:30is a high risk area, particularly if they're bringing
- 21:32in a new middleware. For example, usually without
- 21:37stereotyping the IT teams of A of a brand are not super well
- 21:44connected to the E com teams. So there might be a kind of a
- 21:50little bit of a breakdown in communication there where two
- 21:52teams are kind of working in silo.
- 21:55I guess our role is to make sure that we're bringing the evidence
- 21:59as to why it's important for teams to collaborate and work
- 22:02together and that would come from the milestones and making
- 22:08sure that they are aware that if certain deadlines aren't met,
- 22:12then the the rest of them essentially won't happen.
- 22:15So. And just to kind to reinforce
- 22:18that we then force them into a steer call and make them give an
- 22:21update on their area so that, you know, they can't build to
- 22:24pieces brought back in. So it's a bit of A2 pronged
- 22:26approach because yeah, I guess the the the communication piece,
- 22:32it can always be blamed on that. But you have to be in the room
- 22:35and be present as a part of a project.
- 22:36That's what you're committed to when you're using US, basically.
- 22:39Yeah. And I, I think one of the, one
- 22:41of the skills a consultant needs to bring into a project is it
- 22:45comes back to that project management and governance, but
- 22:47is, is knowing when somebody, it hasn't got the strength to do
- 22:52what is expected to them in the project.
- 22:54And instead of basically hanging them out to dry, trying to
- 22:58support them and get them up to speed.
- 23:00But also from a steering point of view with the project lead,
- 23:05not the sponsor, but the project lead internally explaining to
- 23:08them what, what the problem is and what the impact's going to
- 23:10be so that they can make a decision on whether that person
- 23:13needs their role pushed to somebody else or they need
- 23:16somebody helping them. Because you will find that you
- 23:18will find people who just it's not about age or junior or
- 23:23senior, it's about capability. And not everyone has the
- 23:25capability to execute in these projects.
- 23:27Yeah. And I also think actually it's
- 23:29about understanding how your area impacts everyone else as
- 23:35well, because a lot of departments do work in silo and
- 23:38brands. It is quite shocking, but a lot
- 23:40of teams do don't actually talk to each other internally.
- 23:44And I think it's quite easy if you're doing a day-to-day job to
- 23:49just think I'll get to that, you know, when I can.
- 23:52And so I think it's about us at the beginning helping to educate
- 23:56the whole team and that's why we do sit with every single
- 23:59stakeholder and talk to them on like a personal level and then
- 24:04also about the project. One thing whereas I wanted to to
- 24:08chat about is, is areas that surprise clients in terms of how
- 24:13much they've got to do and actually how long it takes to
- 24:16get it delivered in a project and how that can screw up
- 24:19development milestones. Because you touched on it
- 24:23earlier, I think you said about people surprised.
- 24:25We've got to do the content migration, the product data.
- 24:28So I'm not talking about like two data migration, customers
- 24:31orders, but it's at content in content audits, what we put in,
- 24:35what's fit for purpose. Oh, we're updating designs.
- 24:37Look, we've got to reposition images.
- 24:39All that lifestyle stuff's no longer fit or we need new mobile
- 24:42cuts. And then it's product data.
- 24:44We've got to redo our product model because it's not fit for
- 24:47purpose in the new platform. And we've got to, we've got to
- 24:49improve all of the structured data because we're trying to
- 24:51make it fit for future search and discovery.
- 24:54You suddenly put that on someone's table and that's like
- 24:57mind blown. How do you how do you guys
- 25:00approach that and how would you help and support?
- 25:02Because that is a big piece of work if you if you're in like
- 25:05thousands of products territory. Shall I start?
- 25:09Yeah. So depending on where we picked
- 25:13up the client project because it could be a various stages,
- 25:16right. So they're only just assessing
- 25:18what they need and they've come to us very early on.
- 25:20So we can plan from very early on.
- 25:22But just say the proposal has been signed with the agency and
- 25:25we're we're in full flight mode and they've agreed to do a
- 25:28project with us. We have like maybe a 200 line
- 25:32item, a sign aboard of tasks and that needs to be done for
- 25:36building a base project end to end.
- 25:38Now that board keeps us in check and for, you know, things to
- 25:43happen in a logical order in a, in a series.
- 25:46And obviously projects vary right in terms of complexity.
- 25:49So we'll take like a kind of like at least a kind of a semi
- 25:54complex international project here.
- 25:55So 2 in July items, what we do is kind of run through our ways
- 25:59of working with the client and very early on.
- 26:01So as soon as we start on boarding, it's a part of that
- 26:03process and we show them the depth of things that are needed.
- 26:06And I think that initial call, yes, it might scare them a
- 26:09little bit, it might throw them, but it's like don't get
- 26:11overwhelmed by what you're seeing.
- 26:12It is just that I need you all to understand the breadth of
- 26:15war, what I'm going to need from you across the whole project.
- 26:18And I'll explain as we go along and as we on board as well, the
- 26:22level of input that I'm going to need from each teams.
- 26:24But it kind of gives them a bit of a painting of a picture at
- 26:27that stage. So I think from the offset, they
- 26:29know like these guys are serious, there's quite a bit to
- 26:32do. And this isn't just you can drop
- 26:34me a line, you know, towards the end of the project and I'll just
- 26:37jump in. It's, it's from the, the offset
- 26:40of a of a project. And so our ways of working will
- 26:43cover various high risk items as well.
- 26:44So that's just covering the project.
- 26:47We'll then pull in specific teams.
- 26:49So we as a team of Refon, we focus and Love Actually managing
- 26:54like the product migration, for example, because we will fully
- 26:56optimize it for a client. So you'll end up having like
- 27:00loads of stuff from there in the back end that you don't want.
- 27:02You've just you've gained it's all legacy product, legacy
- 27:05collections and people haven't redirected stuff to the right
- 27:07places having got rid of discontinued products.
- 27:10So we will do like a big data cleanse project on any on our
- 27:13usual projects and then support a client to kind of do that data
- 27:17cleanse, really understand their product, optimize our filters
- 27:21and optimize our metafield structure, you know, all these
- 27:23things that will work on. So that's that's one type of a
- 27:25project. Another one would be like for us
- 27:27to really work backwards from delivery.
- 27:29So the content plan that is we start that as early as possible
- 27:34as well in a project and we will separate out the content team
- 27:38essentially. And so that's asset copy
- 27:41metadata and make sure that every single URL on the site is
- 27:45accounted for working with the SEO team that this company will
- 27:48have. And then like, we'll basically
- 27:51focus on making sure that that content team are owning every
- 27:55single URL that's about to go live at the end of the deadline
- 27:58and telling basically painting the picture internally about
- 28:01what it is that they want. That automatically allows them
- 28:04to start thinking of the design phase in a completely different
- 28:07approach. Because they're like, right, I'm
- 28:08actually accountable to fill every single gap or every single
- 28:12bit of that design of that design phase.
- 28:15Because usually the content teams are like, they'll might
- 28:17see a Figma file, but like in within months after it's been
- 28:21built. And it's like, you should really
- 28:22bring them along the journey because it helps them also
- 28:24create that kind of creative view of like what we actually
- 28:27want for launch. And it's a good way to kind of
- 28:29create that accountability. That's two big areas that I can
- 28:31just think of off the top of my head.
- 28:32But yeah, I'll let like, frankly, maybe jump in because I
- 28:34can see you nodding along. No, no.
- 28:36I think the two big things are a planning and I guess taking the
- 28:42thinking away from a, a client in a way.
- 28:45So we have a lot of documentation that is has been
- 28:51kind of tweaked and finessed over time from doing loads of
- 28:55these projects, understanding where the downfalls are.
- 28:58So now we do bring the content conversation, as Shan mentioned
- 29:03to the beginning of the project. So even before we started the
- 29:06design phase, teams are a little bit confused kind of saying, but
- 29:10I don't know what the designs are going to be.
- 29:12So how can I plan the content? I guess the biggest thing there
- 29:15is actually look at the content you already have.
- 29:19Do you will you need to redo everything?
- 29:21Are you planning on refreshing certain assets?
- 29:24Are you already planning on redoing your copy by getting
- 29:29them to start thinking about that stuff initially?
- 29:32When they do go into the the design phase, like Sham
- 29:35mentioned, they already know that they need to then go back
- 29:40and understand, OK, do I need to redo all of my product images,
- 29:43for example? And yeah, the product
- 29:47architecture as well is something we talk about at the
- 29:50very, very first session. So I guess for us, it really all
- 29:55it's about planning and making sure that the team is aware from
- 29:59the start so that every single discovery session we have loops
- 30:03back to those key high risk areas like the product, like the
- 30:07contents integrations for example.
- 30:11Yeah. There are two other areas I want
- 30:14to get into specifically around like knowledge gaps and ability
- 30:18to execute it to high standards and get the right outputs.
- 30:22So the first is tech discovery and 2nd is UAT.
- 30:24So let's focus on tech discovery first, because one of the one of
- 30:28the risks to a client is if they don't have the ability to
- 30:32scrutinise solution design being passed back, that they could
- 30:36accept a solution design that isn't optimal.
- 30:38That's going to maybe make their ways of working more complex
- 30:42than they'd ideally it. Or they're having to buy in
- 30:44additional third parties and apps that they don't actually
- 30:46need to do because there's a cleaner way of doing it.
- 30:48So how, where? Where do you think, from a
- 30:52consultancy point of view, that responsibility sits in order to
- 30:55get clients to get the best out of a discovery, rather than just
- 30:58accepting what's given to them? That is super interesting
- 31:02because again really depends on what has come in.
- 31:06So, yeah, what stage are clients come in the pipeline for us, I
- 31:10guess because some we also have a potentially like a CTO sitting
- 31:14in there are somebody quite technical who has created a bit
- 31:17of a framework of requirements that they think they're going to
- 31:20need for this project. And it's our job to basically go
- 31:23in there and still do our evaluation and our pre discovery
- 31:26if, if, if it's possible within the timeline so that we can
- 31:28validate exactly we can validate their approach and validate our
- 31:33version of approach. And I think like it is, it is
- 31:38interesting when again, a client is paying a dev agency usually
- 31:45to build a website, which would include all of the apps and all
- 31:47the tech usually, right. And just from an assumption
- 31:50perspective. So like it's our job then to go
- 31:52in and make sure that the client is really aware of what they're
- 31:56getting when they're when they're doing the migration.
- 31:59And to be fair, there's, I think no, not I'm, I'm saying
- 32:03nowadays, but you know, Shopify for example, is one of our like
- 32:07larger, I guess platforms of use within the company.
- 32:11Maybe about 60% of our clients already on it are moving to it
- 32:14and it comes up more often than none.
- 32:16And that one's super interesting specifically because I guess the
- 32:22there's people that just understand the wider ecosystem
- 32:25and they'll understand apps in the way that Shopify is
- 32:28configured versus like the Magenta world where you don't
- 32:31really understand how this website's put together, right?
- 32:33It's not as friendly for like the normal person to hack away
- 32:38at the back end and kind of deliver something on the front
- 32:41end, right? So I think I've completely lost
- 32:45my train of thought. What was your actual question on
- 32:46this? We're going to have to spy again
- 32:48on that one. We'll go back.
- 32:51It so the, the question when I was coming out on this is, is
- 32:55that if you haven't been through lots of brew platformings, you
- 32:59don't know how to run technical, just technical discovery
- 33:03workshops. So they didn't see, you don't
- 33:05know how to make sure the agency has covered all the important
- 33:07questions. And you see it's around like
- 33:09product data, for example, not scrutinizing specific parts of
- 33:12APDP. They're actually have really
- 33:13complexity to the, the schemers and actually to sit behind it.
- 33:17And then when looking at solution design, not knowing
- 33:20whether that is optimal, right? You know, you're telling us we
- 33:23need to use this custom middleware and you've got
- 33:25telling us those 3 apps, but I doubt it, you know, is that the
- 33:28best way did it or there are other better ways that will make
- 33:30our day-to-day processes easier? I think it's a, that's where I
- 33:33was coming from on that question is, is how do you, what is the
- 33:37role of the consultant in advising, guiding and helping
- 33:39clients get better decisions? Well.
- 33:41I think like the whole point that they've got consultant and
- 33:44are an agency and is to be able to lean on their technical
- 33:49expertise, right, to be able to give them the answers.
- 33:51So I think what we would often do, even if there was I guess a
- 33:55framework or like an intentional apps list or technical scope put
- 33:59together, we would still go in and validate it and try and
- 34:01break it down. So the thing that we tried to do
- 34:04is like, I would review a tech stack or an apps list and
- 34:09essentially try and find them the most agile or I guess most
- 34:13popular or say popular by usage. Because we, we, we do a lot of
- 34:16tech discovery and play about a lot of apps.
- 34:20We know a lot of emerging tech. And when we see like certain
- 34:23products that are being used or certain customization route for
- 34:26a bit of tech, I think we can pretty much between our team,
- 34:30like summarize whether that's a good fit or not.
- 34:32And again, like I said, the whole Shopify world, that, that
- 34:35ecosystem, if somebody's choosing platform as Shopify,
- 34:38we'd be like, right, I'd rather you use a product that's within
- 34:41the ecosystem because it's, you know, it's tried and tested,
- 34:43it's a community. It, it will be better for you in
- 34:46the long run. Unless they're a complex
- 34:48business, right? And again, it comes down to this
- 34:50pre discovery and us really being in like in and on the
- 34:53ground in the business to fully understand it and knowing where
- 34:56they're trying to get to as well in like 3 years time.
- 34:58Like I had a client recently that didn't necessarily need a
- 35:03return solution because of the way that their set up was, but I
- 35:06was like, look, you don't need it today.
- 35:08Just do demos with these three. So you kind of have an
- 35:11understanding of landscape because in time, as you grow and
- 35:14you might, you know, expand eventually, I kind of want you
- 35:16to understand it now so that you have that idea pictured in your
- 35:19head about where what that looks like going forward and what the
- 35:22complexity would be. And also, if you're doing a
- 35:23migration, you're probably better doing it now than later
- 35:26on anyway. It'll cost you more.
- 35:28So yeah, there's I guess it just varies so much, but we would
- 35:32always scrutinize like an apps list or the the tech approach to
- 35:36something and trying to bait it a little bit currently.
- 35:38But the whole goal is like do it so it's scalable, do it so it's
- 35:42agile and simple for the customer to use.
- 35:44Is that. Yeah.
- 35:48And I was also just going to add, I think it kind of goes
- 35:50back to the first point of understanding the client and the
- 35:54team in detail. Because if you're operating with
- 35:58a small team and a complex merchandising tool is on the
- 36:04table, for example, it might have all the bells and whistles.
- 36:07It might actually, you know, a deliver the end goal eventually.
- 36:12But actually our role is to go in and say, but actually your
- 36:15team is 2 people. You are not going to have the
- 36:18resource asking internally to utilise or justify spending, you
- 36:24know, a premium on this Marshall, a entry point, you
- 36:31know, could be this alternative tool which was still really
- 36:34powerful. And then in a few years time,
- 36:36you know, let's see how much we're using it and the data
- 36:38you're getting out of it, etcetera.
- 36:39So I'm not a few years, sorry, a few goods time.
- 36:42But so for us, I think that's where we have an advantage as
- 36:45well is that because we've done the pre discovery and we've got
- 36:49to know the client. We can confidently sit in the
- 36:52room with the dev agency, for example, in the discovery
- 36:55sessions and really be an extension of the team, but with
- 36:59more knowledge, an extension of the client team, but with more
- 37:02technical and e-commerce knowledge as well.
- 37:07I think it's really important to I, I always say, so the
- 37:09consultant should be the devil's advocate in the room is, is our
- 37:13role is to help clients and agencies have the best possible
- 37:16outcome to projects, long term partnership, working together,
- 37:19not to get in the way and go, oh, look, don't I know
- 37:21everything. And part of that is if an agency
- 37:24has only worked with a particular product discovery
- 37:26engine and that's the one they like because it's and they, I
- 37:29get this, it happens. You find something that works
- 37:31and you like it, you recommend other clients.
- 37:34But if you know that, that's overkill.
- 37:35I had this recently with ones where it was an enterprise level
- 37:39broad discovery where search was the dominant part of the engine,
- 37:43but the client had such basic search queries, it was complete
- 37:46overkill. There's no need there.
- 37:48And it's the implementation is, is fine, you're doing it.
- 37:52But the actual tool configuration set up for
- 37:54management is it's a really complex tool in the back end.
- 37:57It's and it's having those conversations say guys, I'm not
- 38:00entirely sure that's going to be right, but in a collaborative
- 38:03way so that everyone comes out and making decision together.
- 38:06Yeah, yeah, yeah. And just to add to that as well,
- 38:09I think it's we are agnostic in terms of obviously platforms and
- 38:14partners. So we are open to assessing
- 38:17other options as well, which I think is the important one.
- 38:20A role that I played recently was actually to do an evaluation
- 38:24for a client from a shop, sorry, a Shopify perspective.
- 38:32So a new tool has come into the ecosystem.
- 38:35I won't say because it will be too obvious, obvious, I won't
- 38:39say what it is, but and it was our role to essentially do the
- 38:44assessment for the client in the readiness for Shopify.
- 38:49And I guess from a client perspective, they not used
- 38:52Shopify before, so they're not familiar with all the nuances.
- 38:56So in this case, it was our role to go in and actually unpick
- 39:00exactly whether this would work. And yeah, I think that's the
- 39:03advantage as well, that the client actually wouldn't have
- 39:06been able to do that internally and they might have chosen that
- 39:09tool when actually it's definitely not the right choice.
- 39:13Yeah, we can cut. Through the noise a lot, I think
- 39:15that's the is given the experience and where we sit in
- 39:17the ecosystem as well. We do this, we do demos day in,
- 39:21day out for different things as well.
- 39:23And again, it's the way that something's being built could be
- 39:26differ, like differ between projects as well.
- 39:28So there's like an enormous amount of experience on this
- 39:31side. So we can confidently give
- 39:33option A, option B and the Y. And like, I love going into
- 39:37projects and seeing like big expensive text accessing, you
- 39:40can strip this out, put this in, it's going to do the same job.
- 39:43Or here's your compromise. I think you're absolutely fine
- 39:45with that compromise because you're doing XY and Z anyway.
- 39:48And so the goal is obviously let's make the client money, but
- 39:51let's just have the most simplified agile back end
- 39:55possible. That's still going to allow them
- 39:57to grow, but they can use it and they know how to use it.
- 40:00And it's like that, that kind of variation of a text stack and or
- 40:03like apps, let's for example, it's just like perfect.
- 40:06And yeah, it's all about simplifying it.
- 40:08And unifying stuff where we can as well, like you want a, you
- 40:11largely want A1 size fits all right.
- 40:13But it's just not possible. But like where we can try, try
- 40:16and do that. That's what we try to get to the
- 40:17end of the day. Yeah, at least you want to to
- 40:21UAT. Well, in my head, it led me on
- 40:23to UAT anyway, because I'm just doing, I'm planning on a on a
- 40:26big launch, a moment on for getting the business aligned.
- 40:30And I see this scenario where very few businesses know how to
- 40:34properly do testing because they don't have testing managers that
- 40:39mean how many businesses have an internal testing manager?
- 40:42They don't have a consultant who is a testing specialist and the
- 40:45agencies very can be very good at QA unit testing and all that
- 40:49piece they're visual testing their end, but they are not UAT
- 40:53specialist. And then got there is so much to
- 40:55test, but then the bit, the critical bit, which gets
- 40:59massively underestimated is systems testing process end to
- 41:03end order testing and data flow testing.
- 41:07And that to me is an area where I think independent consultants
- 41:11should be adding a massive amount of value.
- 41:13And I know can of, of getting things organised to, to just
- 41:18coming back to your point rag about soft skills is it's no
- 41:22good telling people to test. You've got to bring them on a
- 41:24journey and they've got to feel motivated and they've got to
- 41:26feel it's manageable and they've got to understand the process.
- 41:29So what I guess what are your viewpoints in terms of where
- 41:33where the consultant role should be adding value in the UAT
- 41:36process and what goes wrong if it's not done properly?
- 41:44I can start this one was to say again another Shanky sizeable
- 41:51upfront discussion to have in ways of working and we bring
- 41:54this up early doors because you will find AUAT phase in a
- 41:59design, sorry in a dev agency timeline is essentially 5 days.
- 42:03So they delivered a theme and you get AUAT period of very
- 42:06minimal days to launch the theme and be able to deliver it.
- 42:10You've just mentioned and UAT across different systems and you
- 42:16know, data flows, etcetera. UAT is huge.
- 42:18It's not just about testing the front end of the theme, which is
- 42:21what you'll see in a line item from a dev agency.
- 42:24So I think again, it's an education piece upfront to the
- 42:26customer to say, you know, UAT is a massive focus point.
- 42:30We need to make sure that we've got the right team available to
- 42:33be around for UAT when the time comes.
- 42:38Generally with UT like what did we used to have before and those
- 42:40like like front end sheets, like again, another 200 line item
- 42:44scenario planning for front end. Then like for admin side, we'll
- 42:49have another like test case piece.
- 42:52But the one that we can do upfront, for example, is like
- 42:55some like finance reconciliation testing.
- 42:57So we'll force teams who can test as early as possible to
- 43:01test as early as possible. So systems being set up, any of
- 43:05those connectors will will encourage basically early
- 43:08adoption of testing. And as as soon as we get the
- 43:11back end of a theme for a back end of Shopify or platform, for
- 43:14example, you know, any of those connections can be tested, API
- 43:17calls can be tested. Let's just get the the
- 43:20integrations team to like set up as early as possible to give
- 43:23them the longest stretch of time to be able to test what they
- 43:25need to test end to end. And then like finance teams as
- 43:29well, bring them up early because again, you can be
- 43:31testing order files, you can be testing payments and in a non
- 43:36live production staging theme. And when it comes to on site
- 43:42testing, I mean that's really where people I guess know that
- 43:46there's testing to be done and really focus on just like front
- 43:49end when it's nothing. It's not all just about front
- 43:52end testing the and how to articulate this one, but the
- 43:58whole end to end testing is it's usually basically the the back
- 44:01end and integration system testing that will block anything
- 44:04to do with the front end anyway. So we encourage that kind of
- 44:07education piece and upfront end to end web flows to happen as
- 44:12early as possible with those teams.
- 44:13And then when we do the monthly steer go, you know, UAT is one
- 44:16of our high risk areas and it is again making sure that every
- 44:19team is doing their testing as upfront and as early as possible
- 44:22within those scenarios. Can I just add that the way that
- 44:26we, I guess, organise all of this is by getting the timelines
- 44:30as soon as possible. So obviously you'll have your
- 44:32timeline from the dev agency. You also need the timeline from
- 44:36the middleware or the systems integrator, whoever is leading
- 44:40the operations and integrations piece.
- 44:43If I have the timelines as early as possible, then I can support
- 44:46and actually making sure that they link up.
- 44:47So for example, a project that we have at the moment, we've
- 44:52actually had to ask the systems integrator to make sure that the
- 44:55product part of the integration is built first because theirs
- 44:59was actually a little bit later in the process.
- 45:04And as a result, we then ask the dev agency to make sure that the
- 45:06PDP and the product is built first, just to start by telling
- 45:10them like Sham said, as early as possible.
- 45:12So from a boring organization documentation view, it's really
- 45:17important to make sure that you're getting the timelines as
- 45:20as soon as possible and making sure that they line up as well.
- 45:24Back to you as well, James, because obviously we're A-Team
- 45:26here and it takes an army to do a full migration.
- 45:30How, how, how do you manage it? What's your kind of, I guess
- 45:33intended approach and what generally happens when you're
- 45:35actually actioning it in live? On UAC specifically, so yeah.
- 45:40So the worry that I do is I've got a the standardised process
- 45:44that I go through which involves early communication like you're
- 45:48saying, briefing people. So I've just gone through it
- 45:51with my big project. At the moment we are two months
- 45:55from launch. Wait is due to kick off
- 45:58meaningfully in two to three weeks.
- 46:00I don't go too early because people forget, but an internal
- 46:04kick off with all the key people who are involved to tell them
- 46:06what UAT is, what it stands for, what the purpose is, what their
- 46:09role will be, how we'll manage it, how, where they need to
- 46:12document stuff and how we'll take the heavy lifting away all
- 46:15that stuff. So they go, oh, it's a clear
- 46:17process. I know what I'm doing.
- 46:19Then it's weekly comms to update them on the timeline because we
- 46:22all know that that the Durham pipeline shifts and all of a
- 46:25sudden actually you're on about to test that to the week after
- 46:28fine. And then each week I, I just
- 46:30update and brief people who go right, next week's testing focus
- 46:33is X. This is your responsibilities.
- 46:35I need the sheet up the the issue log updated by end of the
- 46:39week. And then I have a mini, the work
- 46:41task group, which will be a couple of stakeholders
- 46:44internally with me to triage and we all do the right, is this
- 46:49data content issue, we've fixed it done back to retest or is it
- 46:53a dev ticket now we prioritise it based on criteria and that
- 46:57goes into the the usual dev ticketing process.
- 47:00But the bit you touched upon is the critical bit.
- 47:02It's the end to end order testing.
- 47:04And I have a again, I've got a, I've got a working group
- 47:07separate to the UAT team who are all core systems from ERP down
- 47:12to WMS. Any other pies? The the analytics bit CS where
- 47:17we map out every single order scenario we've got to test and
- 47:20all the system checks and then pass fails.
- 47:23And any order scenario that fails, there has to be a
- 47:26resolution to it and then has to be retested.
- 47:29And it it. I mean, this is the dole bit.
- 47:31But it's so bloody important because you're right.
- 47:33Testing the front end again. Doesn't the work side look
- 47:35great? Yeah, but you can't ship made to
- 47:37order products. Oh.
- 47:38Oh, it's a shame. Yeah, I think it's also just
- 47:44again because a day of timeline usually gets given up front and
- 47:48unknown. You just see that line item of
- 47:50like 3 to 5 days for testing typically and like I'm seeing as
- 47:54typical 24 or 26 week timeline. I think that is again, a
- 48:00customer doesn't know what they don't know.
- 48:01They've never done this before. And I think the UAT can be
- 48:05hectic unless you know, you do have that education piece at
- 48:08front and explain the different breakdowns between the different
- 48:11departments and how they can do this.
- 48:13And they're kind of more like, I guess the earlier flow, some
- 48:16more simplified flow. And the thing that is as well
- 48:19that's usually frustrating. It's like 1, one team could do
- 48:22the majority of the order scenario testing and everyone
- 48:25else could use that order file to largely validate their
- 48:27section. But you just, no matter how many
- 48:30times you say, you usually find like everyone does their own
- 48:32second testing. So that same order could be
- 48:34placed like 5 times. And it's just like just use the
- 48:37one batch of order scenarios and you'll probably like 3 of you
- 48:42guys will probably be able to validate your scenarios.
- 48:45But I'm just happy when I see again for accountability to make
- 48:50sure that like order tests are getting done.
- 48:52We made them document in one place so that then you can see,
- 48:56you know, activity is happening. And when it's not, it's called
- 48:59out as a as a risk on our weekly anyway.
- 49:01Yeah, it's just it's it's, it's forcing people to going to do
- 49:04stuff upfront and that will really high time.
- 49:07Yeah, and it's for me, UAT is successful when when it's clear
- 49:11what the process is, when you divide and conquer.
- 49:13Because if you get everyone to do everything, it's a mess.
- 49:17And, and the, the other thing I think is really important is to
- 49:20be transparent, to be back and go look, if you're expecting a
- 49:22pixel perfect website with every bit of data in there and every,
- 49:25it's not going to be your, your AT site is about you breaking
- 49:30stuff. Do not worry about the visual
- 49:32side that's been handled by like the, the brand of the design
- 49:35team. Do not worry about the product
- 49:37data. That is still an ongoing basis.
- 49:39You've got to be very clear to people about what isn't
- 49:42currently done because otherwise you get it.
- 49:45Clients go and go. It looks shit is off brand.
- 49:47This doesn't and you've just ruined it because they're in the
- 49:50wrong mental space. I could carry on asking you
- 49:57questions all afternoon because I love this topic and I know how
- 49:59much experience you both got, but I'm worried that you both
- 50:02got lives to lead. So I'm going to finish with a
- 50:05question for you both for you to answer, which is it's this
- 50:08right? You know, you're you're you're
- 50:10an e-commerce business, you're a senior decision maker or a head
- 50:13of E Comm, whatever it is. I'm not making a re platform
- 50:15project and you're thinking it's going to be expensive.
- 50:19If you're considering an exultant, you've got to be get
- 50:22better guarantee that they are delivering value.
- 50:24What are the core skills that a an E Comm person should be
- 50:28demanding and expecting from a consultant in order to be able
- 50:32to evaluate that they're going to be adding value?
- 50:37Should I go? Let's go for it.
- 50:41They sound like a broken record, but I think this is a really
- 50:44important one and it's actually a personal one for me because I
- 50:47feel like this is where I have got the most clout with clients,
- 50:52so it's probably he's got fan. Clubs out there.
- 50:57Probably empathy and understanding is like, and those
- 51:01softer skills are really important.
- 51:03So whether that's from understanding a client's
- 51:08internal challenges, there are individual workloads, how they
- 51:13might actually struggle throughout the project and
- 51:16phasing calls and information so that it kind of suits the time
- 51:22of year that they're going through.
- 51:23So for example, what I mean if a project obviously doesn't allow
- 51:26for this, then it's unfortunate, but usually what I will try and
- 51:29do is, is actually phase the information to who I'm giving it
- 51:32to based on the understanding I have of them and the team.
- 51:37And I think that's really important.
- 51:39The next thing from that is definitely the ability to
- 51:42interpret a client's needs versus their wants.
- 51:47So more often than not, a client will say we need this, we need
- 51:53this as a department or as a company.
- 51:56And it is our role to be intuitive and actually decipher
- 52:02whether that is a true need and whether it's going to move the
- 52:04needle for them or whether it's just a want because it's
- 52:08something that they've been fighting for internally for ages
- 52:11and this is finding an opportunity for them to get it.
- 52:13So we will usually and again you know the requirements gathering
- 52:18phase, the pre discovery is where we would pick this out.
- 52:21But being able to understand the difference between those two and
- 52:26listen to the client is super important rather than just going
- 52:31in all guns blazing and do like a cookie cutter approach as to
- 52:34how it should. Be I do just want to say off the
- 52:37back of that, like as simple as that science, it's really I
- 52:39think that's one of our like magic skill sets.
- 52:43You know, they're paying us to cut through the noise as well,
- 52:46right? And I think it takes an enormous
- 52:49amount of trust from their side to allow us to, you know, give
- 52:52option A and option B based on our experience.
- 52:55I think that's quite it's quite telling from both sides.
- 52:58But yeah, I think that's probably one of the, the biggest
- 53:00value add areas that we've on hold I, I like.
- 53:04That though, because I think it's really important that that
- 53:07you have to have commercial, I mean, you've got to have the
- 53:10gravitas to be able to influence across all the different levels.
- 53:13And you've got to have that depth of understanding of, of an
- 53:16end to end project and what are the risks and what goes wrong
- 53:18and how to minimise that. But you've fundamentally it's
- 53:22about people. People deliver projects, the
- 53:24text there to be used. But if you don't have people,
- 53:26you don't get any outcomes. And if you can't bring people on
- 53:29journeys, if you can't motivate people to care about the project
- 53:32and deliver, you're, you're going to fail.
- 53:35So I, I fully agree. I think that's so but, and, and
- 53:37it is a real skill set. You're right, because not
- 53:39everyone could do it. People can be amazingly smart,
- 53:41but not great at articulate and communicating.
- 53:43You probably have the communication.
- 53:45You've got to know what triggers each person, as some people are
- 53:49very defensive and very insular and need different ways of
- 53:54management than somebody who's naturally like, oh God, that's
- 53:56wrong, let's fix it. Also just not being constant,
- 54:00yes, people on our side, right, We have to be able to pinpoint
- 54:03decisions and do the best version of a choice based on all
- 54:08the knowledge that we have and the goal that they're trying to
- 54:10get to, right. There's decisions that we're,
- 54:13the reason that you're hiring us as well is to be able to again,
- 54:15cut through the noise, make those make those decisions for
- 54:18you to not delay timeline and to not increase budget.
- 54:20You know, we're, we're there to deliver something and it's, it's
- 54:23based on our experience. We we're able to kind of drive
- 54:25that the speeds that we do drive it because we do complete
- 54:28complex projects and like what was Oka nine months like, yeah,
- 54:35in if you go on that Oka website, insane that the
- 54:38complexity behind that project, insane the quality of delivery
- 54:41in the scene and it was delivered in nine months like
- 54:43that. I dread to think if you took
- 54:45that to, I don't know if I'm allowed to say this an external,
- 54:49like an external kind of bigger consultant group.
- 54:52I don't know how long that would have taken, but yeah, it just,
- 54:55it's insane how much you can actually get delivered with the
- 54:58right team and the right kind of accountability and the right and
- 55:01trust in a team to be able to build something and get it out
- 55:04the door. And I also think it's not just
- 55:07about, sorry James, you're going to say something.
- 55:11It's not just about the internal team as well.
- 55:14It's actually for third parties that you could be working with.
- 55:17So for example, your analytics agency, SEO, etcetera is also
- 55:24about being able to pull people in at the right time, having
- 55:29those relationships with those people.
- 55:31Sometimes you're on a call, I'm an all agency call and there's
- 55:34like, I don't know, 20 stakeholders who all have their
- 55:38own individual needs and requirements and goals,
- 55:42etcetera. And I think it is a skill to be
- 55:45able to hold a room there and actually get the information
- 55:48that you need out of a specific people.
- 55:53And as you get to the end of a project, obviously you're
- 55:55preparing for launch, etcetera, those calls actually, you know,
- 55:58get more frequent. And if you have iron from the
- 56:00beginning of the project, so much smoother to be able to ask,
- 56:04you know, the SEO agency to hop on a quick call because we need
- 56:07to variate something. If you don't actually engage and
- 56:10communicate from the start, then that just becomes very, very
- 56:13tricky. And then that's where certain
- 56:14things can start to fall down. Yeah, I, I, I think that's it.
- 56:18I, I often, for anyone who's watched Hitchhiker's Guide to
- 56:21the Galaxy, there's the the Babel fish, which is, excuse me,
- 56:26you're not as old as me. That's why the, the barrier fish
- 56:30is this thing that you put in your ear.
- 56:32It can instantly translate every language in the Galaxy.
- 56:35And that to me, that is what a consultant is, because you have
- 56:38to be able to talk to ACEO as CFO and you've got to be able to
- 56:43give them credible evidence and you've got to be honest with
- 56:45them if things are going wrong, why they're going, what the
- 56:47impact is, answer their questions, deal with them.
- 56:50When there's, hey, you've got to manage the project lead, you've
- 56:53got to manage the stakeholders, you've got to talk to an SEO
- 56:55agency, an analytics agency, third party technology
- 56:59companies, developers, business development people.
- 57:02You've got all these different things.
- 57:04And that requires different types of communication,
- 57:07different frequencies and different formats.
- 57:10And that to me is the is the art.
- 57:11It's you've got to be able to get on with people and you've
- 57:14got to be able to smooth through problems when there are
- 57:17conflicts rather than getting uppity and making it all about
- 57:21politics. Yeah.
- 57:23And just one last one, which is of course I'm going to say this.
- 57:27I think attention to detail is something which is kind of
- 57:33overlooked, I guess or joked about sometimes, but it is super
- 57:37important. And the reason why I say that is
- 57:38because again, you are across like hundreds of documents and
- 57:43one small mistake on one can ricochet and actually be, you
- 57:49know, a huge impact in the end. So not being overwhelmed by
- 57:55reading through, you know, a lot of information, picking out, you
- 57:59know, where the gaps are, etcetera.
- 58:00I think that does take a certain kind of person as well.
- 58:03And yeah, I think luckily we do have a a team of those here.
- 58:10Yeah, 100%. At the end of the day, we
- 58:12brought it back to we need to have an element of dullness in
- 58:14you in order to make these projects work.
- 58:17Exciting. But yes, I'd love this.
- 58:22I could carry on discussing this for hours.
- 58:23I think we all know we can do that.
- 58:25But. I've got one last question for
- 58:26you though. It's not.
- 58:28All about. You.
- 58:28No, I've got one last question for you.
- 58:31When do you think you don't need a consultant?
- 58:34So I like that question. When you are so I think if if
- 58:39the project is really simple and it's just a theme, what
- 58:42regardless of when you're a shopified big commerce and if
- 58:44they're on as I had a client actually who would move into
- 58:47Shopify from a custom build on on Woo several years back and
- 58:54there was 0 integration. They have no ERP, no WMS. They
- 58:58literally manually manage the orders and have somebody in a
- 59:02small warehouse who who basically logs in, takes an
- 59:05order and processes and updates it.
- 59:08The main, the projects that you've been doing that now
- 59:09there's no simple projects anymore.
- 59:11I'm. Saying there are some projects
- 59:13when you I mean you should. There's no.
- 59:16The value they had for me was advise and guide them on on what
- 59:19they need to think about how they need to run a project and
- 59:21decisions decision. Well, they didn't need a
- 59:23consultant in there because I found them the right agency,
- 59:27which was GPMD Mark cycle container, really good who
- 59:31really good at doing because they're a build agency, but
- 59:34they're very collaborative in the process.
- 59:36They have, they had the skills they needed and the the the
- 59:39capabilities in the project without a consultant and now you
- 59:42better spending the money on the development side.
- 59:45So that's one scenario. I think in a more complex
- 59:49project it would be if they are a business and I've worked with
- 59:54some large businesses like House of Fraser who have a fully
- 59:57resourced PMO office in there where they have BASPMS and true
- 1:00:02program managers who've experienced of running multi
- 1:00:05threaded projects. And managing the project office
- 1:00:09and managing stakeholders and doing all the documentation.
- 1:00:12And so they have the expertise of project delivery and they
- 1:00:15have e-commerce expertise within that.
- 1:00:17And if they have strong E com leaders across the core parts of
- 1:00:20the business, like there was a very strong director for E com,
- 1:00:23very strong, the head of merchandising have very strong
- 1:00:26head of digital marketing that actually, yes, you can help, but
- 1:00:32sometimes you don't need that external person anymore because
- 1:00:34you've got the coordination in there.
- 1:00:36It's, it's, it's hard. I mean, the, the one thing that
- 1:00:39you don't get then is you only get the challenge.
- 1:00:41You don't get the, but you're doing it like that.
- 1:00:44But why that's probably not the right way of doing it.
- 1:00:46So you, the risk you get is you repeat some of the, this is how
- 1:00:50we do it now, but within a new ecosystem.
- 1:00:52So I, I think you can get a warrior with it.
- 1:00:55It doesn't mean that you do it perfectly by getting away with
- 1:00:57it. Yeah, Yeah.
- 1:00:59I mean just thinking about our ICP and the types of clients
- 1:01:03that we generally tend to work with, the size of brand that we
- 1:01:06tend to work with. I honestly find it mind boggling
- 1:01:10that somebody, you know, some of these teams, they might not
- 1:01:14necessarily have the budget for us, right.
- 1:01:16And they know they need to do the projects.
- 1:01:17So they might try and wing it internally.
- 1:01:19And the thought of that is just considering the complexities in
- 1:01:24it, it's just a bit, it's crazy to think that somebody would be
- 1:01:27able to take that on and deliver, deliver something to
- 1:01:31spec. But then I guess this is where
- 1:01:33our value comes in, right? It's the intentional delivery of
- 1:01:38something that's actually not MVP.
- 1:01:40And I think, you know, when, when a lot of brands deliver a
- 1:01:43version of their site, it's very much in my opinion, like an 80%
- 1:01:48site. Whereas like I think what we end
- 1:01:50up doing is launching a site with like bells and a number of
- 1:01:53whistles. But it'll be at least like,
- 1:01:55like, you know, 92% complete. And you know, all that's missing
- 1:01:58on the front end is maybe a bit of content and like less
- 1:02:01priority content. But I would like, I don't feel
- 1:02:05comfortable launching a site without even having the blogs on
- 1:02:08and that's how ready kind of we pair A-Team to launch and launch
- 1:02:12for. So yeah, as hectic as our
- 1:02:14projects boards might feel and be, I guess in the whole
- 1:02:18process, I think our customers end up launching with a a
- 1:02:21version of a site that's really ready to trade.
- 1:02:23And you know, there's not this ongoing 3 month retainer just to
- 1:02:28Polish off the site. We tend to, yeah, leave it at a
- 1:02:30very, very polished version for launch, which is quite nice.
- 1:02:36Yeah, I that's always my ambition.
- 1:02:39But there are sometimes when it can't happen because the climb
- 1:02:41was to get live at a point where you cannot deliver that level.
- 1:02:44And it's yeah as well. It is hard because I'm with you,
- 1:02:46that that conversation happens up front of, OK, if you've got
- 1:02:50to go live by month X and this is the likely compromises you
- 1:02:54are going to have to make for launch, are you willing to
- 1:02:56expect yes or no? And often people go, yeah, yeah.
- 1:02:59And when it gets to it, they don't really want to have made
- 1:03:01those compromises, but they've made a decision.
- 1:03:03So. OK.
- 1:03:08Thanks Joe for having us. And I've just, I loved it.
- 1:03:10And for anyone listening, I highly recommend if you aren't
- 1:03:14already connected to and don't already follow up that Frankie
- 1:03:17and Sham are up to you should do connect with them.
- 1:03:20Their contact details are on the landing page.
- 1:03:22They are brilliant people to know in the industry.
- 1:03:24January. And obviously make sure you're
- 1:03:26going to the Pulse event in May, isn't it?
- 1:03:29Yeah, it is. But God is next month because
- 1:03:31that would be there. As for the Rep of the wrong team
- 1:03:34and you can chat them a lot more.
- 1:03:36Yeah, please do. And definitely sign up for Pulse
- 1:03:38in the background. I think people forget to
- 1:03:40actually register and then we find a heap of new people on the
- 1:03:42day off. But yeah, no.
- 1:03:44Thank you for having us, James. Yeah, we could talk about this
- 1:03:47for hours, and I'm not sure how helpful this is for anyone else,
- 1:03:50but reach out if you have any other questions.
- 1:03:53Thanks, James. You're listening to the Inside
- 1:03:56Commerce podcast, hosted by experienced consultants James
- 1:03:59Gert and Paul Rogers. Inside Commerce is your fast
- 1:04:02track to digital knowledge, featuring interviews with
- 1:04:04leading e-commerce retailers, industry thought leads and the
- 1:04:07C-Suite, key tech companies to explore the latest digital
- 1:04:10strategy, customer experience and tech.
- 1:04:12Discover what the latest trends really mean and get practical
- 1:04:15advice based on the experience to help fine tune your E com
- 1:04:18strategy and tech stack. Follow us on LinkedIn and reach
- 1:04:21out to James and Paul if you'd like to discuss an e-commerce
- 1:04:24project. We hope you enjoy the latest
- 1:04:26episode.