Latest / Tech Journeys Podcast / Andy Perry | From Hands-On Architect to Strategic Advisor | The Tech Journeys Podcasts
Transcript
- Welcome to the Tech Journeys podcast.
- I'm your host, Vincent, and on this podcast, I interview people in tech.
- As always, this show is sponsored by the consulting launch method, where I help experienced tech professionals build their own consulting business without spending years figuring out the business side.
- We've helped clients go from first idea to first client in nine- 90 days, and six figures within a year.
- To learn more, connect with me on LinkedIn and send me a message.
- On today's show, we have Andy Perry, and Andy is a fractional CTO solution architect, uh, freelancing at different places over the last several years.
- You know, and his primary focus are, is around strategy and architecture.
- So Andy, welcome to the show.
- Uh, welcome.
- Uh, and I wanted to ask you the fir- the question that I always love to start with, right? Uh, looking back at your career, what's the decision or project that you're most proud of, and what made it stand out for you? Okay.
- Brilliant.
- Well, yeah, thank- thanks for having me on.
- So, um, yeah, there's, there's probably been a couple I can think of.
- I think the main, um, piece of work, I used to work for a company called Reckitt Benckiser, uh, RB- RB as they're now known.
- Um, and you've probably got lots of their products in your house, from Lemsip to Finish, Calgon, and, and so on.
- And, um, I was probably mid-20s, um, getting on, getting on for 30.
- And, um, Reckitt bought, um, and acquired Boots Healthcare International, um, based in Nottingham.
- So anyone who's ever seen the, the Boots campus in, in Nottingham, it's almost like its own village.
- So this particular section of Boots Healthcare, and, um, they gave me the project of, of integrating all of the, um, end use compute infrastructure.
- And I've done some active directory projects and some kind of office upgrades and stuff, but this was absolutely huge.
- So for, for a year, me and other people who were doing the ERP integrations and the, uh, business application integrations spent a year in and out of Nottingham.
- Bearing in mind, I was, I was living in Hull, which is where I'm from originally, um, at the time, working on this project.
- And between us, we, we, we did it.
- We, we achieved it against transitional service agreements.
- We merged everything.
- Yes, there was glitches, yes, there was blood, sweat and tears and everything, but absolutely kind of pivotal project where you kind of go, "Yeah, you know what? I did that.
- I can do other things like this as well."
- And I think, uh, uh, subsequently I've worked another kind of merger acquisition, divestment style projects, and I always go back to some of the principles I learned from that project.
- So re- really kind of thrown in at the deep end, but came out swimming fortunately.
- So, so what, what principles, uh, are those you put in? I think when I've ever done something like this, it's, it, it almost sounds, like, obvious, but you kind of, you just kind of go back, like, w- what have we got? Where, where are we coming from? And I always just start with a, with a, with an Excel spreadsheet almost, kind of going, "What, what are we dealing with here? Let's, like, list out all of our clients, all of our servers, all of our applications, all of our kind of services, and then run them through a, a kind of kill, keep, migrate principle.
- Are we hanging onto this? Do we need to transform it? Are we, can we get rid of it? How are we merging these things?" And you just start with a really simple kind of model, and then eventually it, it ex- explodes e- even further.
- And, um, RB, um, acquired another company a few years later.
- I, a- a- adopted an almost identical principle.
- I've done it at subsequent places.
- So these aren't specialist models or anything like that, it is just kind of, up to me, it's coming from common sense.
- If you know you've got to get somewhere, you've got to do a merge, you've got to know where you're coming from.
- You've got to know what obstacles you're gonna have to kind of overcome, and just start kind of, like, documenting and come up with the plan of what the challenge is.
- And I think sometimes there's almost a...
- What I was seeing when I've done things like this, certainly a lot of senior stakeholders adopt a, a relatively kind of simplistic approach 'cause they can't get into the, into the weeds, which is, "Well, we've got 1,000 laptops we need to replace.
- We'll just come along, buy another 1,000 laptops, swap those 1,000 laptops out, and then we're done."
- I'm like, "Those 1,000 laptops you're replacing have got user profiles.
- They've got data.
- They've got applications.
- They've probably got peripherals."
- Yeah.
- "We, we can't.
- We've got to think a little bit more nuanced."
- And again, just coming from a f- coming from a technical background but moving into, say, more kind of, like, strategic roles going forward, it's starting to be able to kind of, like, play across those two spaces and, um, just bring that experience to the table.
- So, yeah.
- And, and, and how do you g- um, 'cause obviously w- use a spreadsheet.
- I'm, I'm a spreadsheet person myself, right? So I, I like spreadsheet.
- But, uh, so, so documenting where, where you are at the moment, but then where you, you know, h- how do you kind of determine and, and how do you engage with your clients to figure out where they, where they need to get to? Or, or, or do you advise them on where they need to get to then? Yeah, I mean, with, with, like I said, this M&A or this divestment approach, it would be, you would, you would start off with something even as fundamental as, right, I have an email server.
- Right? Okay.
- What am I doing? I'm going to collapse that email server into another email server, right? Who are the owners? What's the service? Who looks after this? But w- when you get into the business applications, w- with, it becomes a little bit more specialist.
- You might have an HR system.
- You might have, with, with the, with the Boots example, there was manufacturing execution systems.
- There was, um, pharmaceutical, like dispensing systems, things that dispense, um, Nurofen.
- It's ibuprofen.
- If you don't get that right- Yeah you're in a regulatory, um, nightmare.
- So it, w- we kind of like document, say, "I have a system here.
- It dispenses a, a drug."
- Right.
- Who owns the system? Who, who's responsible for the compliance? We can't just pick that up, drop it into a new environment, expect it all to work.
- We might need to transform it.
- We might need to upgrade its operating system.
- We might need to virtualize it.
- We might need to move it to the cloud.
- What's the impact of doing that, and how do we plot that journey? But before we know what that journey is, we've got to know that we have that system in place, so there's almost like this discovery activity.
- And I, and, and I find across multiple places I've worked at, knowing what that baseline is, is, is sometimes something that's either not documented or not maintained, and obviously then you've got the shadow IT problem, where people have gone out and bought their own things- Yeah and so on, that you find out, you know, at the 11th hour.
- So, so I think understanding where we're coming from and then plotting out what the plans are, who the owners are, then you can go and engage them and have that dialogue and go, "Right, what are we doing?" And obviously from there you can start to ascertain what the budget looks like, and probably find that it's gonna cost you 10 times more than what someone predicted it was going to cost to transform so.
- Yeah.
- Understand.
- And, and so, so do you like the technical side or the working with people side, or are you...
- You know, what, how has that sort of evolved? Yeah.
- A bit, a bit, a bit of both really.
- I've done, um...
- A f- a friend of mine's a, um, a, uh, d- does, does kind of coaching and kind of training and so on, and he, um, he...
- I went through the insights, um, personality, and, um, I came out as like a blue and a yellow conflicted, which is basically like an individual like to work in my own space, but equally I need to get energy from others, so it's a bit of a conflicted area.
- Yeah.
- So some- sometimes I've got to sit, work on the problem, solve it myself, then sit down, share it, work at it, then bring it back down and then bounce it back and forward.
- So yeah, I, I need a bit of, uh, I need a bit of both really in my, in my day-to-day life.
- Fair.
- To keep, to keep you sane, I suppose.
- That's right.
- Yeah.
- Fa- fair.
- So, so if you, if you were to start your tech career again tomorrow, knowing what you know now, and, and obviously there's in the last 10, 20, you know, years, obviously lots of technical changes have happened.
- AI's come in, you know, largely, you know, very prominently now.
- You know, all those transitions are happening.
- I mean, what is the, the one thing that you will do differently, you know, that you would tell your younger self to do differently? The one thing is, is, is probably trust, trust my instincts a bit more.
- Um, I think I look at times over the year where I instinctually have known something's right or wrong, and that could be tech, it could be a, a future growth or a strategy, it could be even individuals.
- And, um, and I've had a feeling about it, and I think, and I look back over the years, I've never trusted that.
- I've never thought...
- I've maybe thought, "Yeah, maybe that's not gonna work out right," or something, or, "Maybe this is the way we should be going."
- And, and, and when someone's told me that's not right or I've just kind of gone, "Yeah, okay.
- Fair enough," and, and, and, and, and just I kind of accepted it.
- And I think one of the things I've, I've learned o- over the years is it's not that I'm, I'm always right.
- Absolutely, definitely not.
- But it's, it's more when you have a kind of gut feeling about something based on partly intuition, partly experience is, is really kind of believe in yourself and kind of trust it.
- And- It's not that you necessarily would've been able to change something, but you might have been able to influence something or maybe defended your position a little better.
- Um, instead of kind of looking back and going, "Oh, well, I knew that would happen," is actually have made a tried to maybe be a bit more assertive about making a difference with it.
- So easier said than done.
- Very easy in hindsight, but I think, yeah, certainly, um, trusting, trusting your own judgment and believing in yourself a little bit more.
- Yeah, fair.
- And, and do, do you have an example where you've ignored this and it sort of didn't pan out, or? I think there's, there's been...
- Without getting into all the, all the details, I think I've kind of, there's maybe been individuals that have kind of, I've been involved in, like, kind of recruitment.
- I've been like, "I'm not sure if this is working out," and I've been like, "No, maybe it's, maybe it's me.
- Maybe it needs a bit of time."
- And it- and it's, fundamentally it's probably just been a bad fit, and it's, it's kind of working on that, a- again, a much earlier opportunity and believing it or moving away from people and into tech, kind of seeing how growth of, I don't know, e- even things like the adoption of tablets when everyone started bringing iPads into the organization- Yeah and so on.
- And, and, and a lot of people thought this is quite gimmicky, and to an extent it was at the time, but I was like, y- this is clearly the way people are gonna want to start interacting.
- They don't want a machine that takes 10 minutes to boot up and is quite clunky.
- They want a thing that you just turn on, swipe, and you can get your, get your responses.
- And again, I was kind of shot down a bit and kind of like, "Right, well, this is unlikely to...
- This, this, again, it's a bit of a gimmick.
- People are probably playing kind of solitaire on them and everything."
- But now everyone's got a mobile device, people are working on tablets.
- And again, I'm not sure this would've changed the world, but I think, again, just being a bit more stronger and defended in my position about, like, rationalizing why, um, would've, would, would've, would've been exa- ex- examples of that.
- And I think, again, throughout projects you can sometimes see through experience something's gonna go wrong here.
- Yeah.
- But certainly in a kind of consultive capacity, you can tell somebody you think this is gonna go wrong.
- You can't necessarily sometimes leave in evidence it.
- You might be able to kind of go, "Look, there's these risks.
- These, these might get realized."
- But if fundamentally someone doesn't want to accept your warning or your guidance, or they might think you're kind of scaremongering a bit, they don't have to.
- But it's, it's never good to kind of go, "Right, this has all gone wrong.
- What we're gonna..."
- But, and it's- there's no point in saying, "I told you so."
- It's just a case of, "Right, that's all good.
- We made that decision.
- We move on.
- How do we fix it? How do we kind of, like, get to a better position?" So yeah, there's, there's lots of different examples.
- It's probably across the whole people process technology.
- Um, but, but I, I think, yeah, just look- looking back, there's been times where I maybe should have just said, "No, I maybe need to put my foot down a bit more on this one," and kind of be a bit more assertive about it.
- Fair enough.
- Um, I, I, I sort of recognize it also is, yeah, yeah, sometimes the gut feeling, but it, I think it's sometimes chall- challenging to get your...
- to, to, to figure out why your gut feeling is telling you something and, and rationalize it into an argument that you can convey.
- Um, it's not, it's not always easy.
- Uh, uh.
- No.
- And, and it's fun- I was chat- chatting with a friend, and he was talking to me about how you, you know, s- some might experience some skills, um, how you might start- sharing them or whether it, whether it be through writing a book or running a session or, or, or anything like that.
- And I said, "It's funny," 'cause I've thought about this, and it- I, I likened it to, to almost like playing a musical instrument or something.
- So it's almost like an abstract kind of like sense of intuition.
- I'm gen- I'm fairly intuitive about, like, tech.
- I always have been since as literally as early as I can remember, like two or three years old.
- But I'm not particularly intuitive when it comes to, like, playing instruments.
- So, like, my wife and none of people pick up a guitar and just or any instrument and start playing.
- I can pick up a piece of technology, and within minutes I've probably figured out how to use it or how to, how to do something with it.
- That's probably quite hard thing to teach.
- So you- again, over the years, you'd kind of like learn, um, yeah, I just have a knack for being able to do something like this and, and then rely on that.
- But how you, how you would teach that, I'm not entirely sure.
- May- maybe I'll, I'll figure it out one day.
- Yeah.
- I, I think, um, it- what is, uh, uh, underrated sometimes is, um, the experience you, you have, right, as a, you know, in, in that kind of field that, that builds over years and years and years that, you know, uh, when, when most people only see, you know, 20 years of experience at work- Mm-hmm they haven't seen the, the 20 years beforehand that, that gained you that experience, right? Mm-hmm.
- So, um, now, l- let me ask you the sort of final sort of question, but what does the next chapter of your career, uh, look like for you, right? You know, before we, we started talking, you already mentioned a few things, but, uh, tell me a bit more about that, uh, Andy.
- Yeah, sure.
- So, um, y- yeah, I mean, I've, I've st- uh, uh, my last 10, 15 years kind of freelancing be very much in a, um, solutions architecture, enterprise architecture type space, and I've done bits of project management and business analyst in, in, in between all of that.
- But I think one of the things I've found myself kind of the role evolving into is having more strategic conversations about some, some of the technologies and, and obviously with AI coming in, that's a, that's another thing.
- So I, um, my, my next kind of career trajectory start to move towards like a, a fractional C- CTO space.
- So I've got a couple of areas I'm, like, looking to move into there.
- Um, equally things like board advisory style roles where you can kind of move from a, move from the kind of doing to the advising.
- Think that's probably gonna be a challenge, moving from this relatively, like, hands-on doing problem-solving space to more this, right, how do we start laying out these directions and strategies.
- But I think that's absolutely something I'm, I'm, I'm, I'm looking to move into.
- Um, I've, I've got generally a healthy cynicism when it comes to most technologies, so whether this has been- Virtualization to cloud to obviously now AI.
- But as I've started to kind of embrace some of the areas, I'm seeing right where we have got some kind of gimmicky things to where we've actually got some really value-added stuff.
- So I'm going on, I'm, I'm enrolled on a couple of training programs and doing some self-development about less around the j- the things like the generative AI where you can just say, "Write me a blog," or, "Draw me a picture of a cat," or something.
- About how do we actually take something like an AI capability and actually embed it and solve the problem, and this is probably something you know and other people who've spoken to know is these hype technologies come in.
- It's like, "I need AI.
- That's the answer."
- I don't necessarily know what the problem is, so I think part of the role I wanna move into is, is let's start to understand we've clearly got this amazing capability here, but let's try and map out what it is, where, where your main problems are, and then we can try and solve it.
- Not like, how do I embed AI in my organization? That's fine, but let's try and understand specifically what problems we're trying to address.
- So very much move into more that strategic business change style thinking and coupling that with my tech background.
- That's, um, that's the next step for me, hopefully.
- Fantastic.
- Yeah.
- Yeah, I, I, I sort of resonate with it.
- I mean, a lot, uh, you see a lot, a, a rush to AI and, a- and as consequently most AI deployments are, you know, not living up to the expectations or to the hype, right? Uh, as we know.
- You know, the data and the, and, and the mise is, is often, uh, very, um, well- How shall I say it? Constrained.
- Yes.
- Yeah.
- Not great, not great quality, let's call it that, right? Yeah.
- Um, and, and I think, and I've seen this in, in lots of d- sort of, uh, sort of te- uh, techno- technology transitions is that, uh, what ultimately the objective is to actually replicate what you have.
- It, it...
- When, when you went to, when we went to cloud, right, we did a lot of move, you know, digital transformation and cloud transformation projects.
- You're kind of replicating what you had on-prem into the cloud.
- But if you had, had something messy on-prem, and you go replicate it on cloud, it's still messy, right? Yeah.
- And actually it's more complicated because it's in the cloud, uh, and it's messy.
- Same as with AI.
- So I feel that, uh, you know, there's a, there's a huge opportunity to some extent for consultants and, and, and like people like yourself to, to actually kind of address that sort of, um, chasm almost, right? It's like, well, as you are moving to AI or to cloud or whatever it is, let's sit down.
- Okay, what do you really need to achieve as your business? And figure out if what you have today, if it work, how it works today is actually still the right way to work in, in the new world, right? Mm-hmm.
- And, and how can we leverage the new world in a better way so it, so it actually, you know, has the impact, the impact that you're really looking for.
- Yeah.
- Uh.
- 100%.
- 100%.
- I mean, when we've done cl- cloud migrations or I spoke to companies about it, they kind of said, using your example exactly, "I have a server, it's sat in a corner.
- I will virtualize it, and I'll go and put it in the cloud.
- Wipe my hands, like it's now in the cloud."
- And like, actually, and, uh, this was an exam- a real example.
- We, a company needed to migrate, um, some stuff to the cloud.
- They took a server, and I said, "That server is going to, if you migrate that like for like, it will start costing you something like £7,000 or £8,000 a month to run that in the cloud," because of the, the, the kind of particular, it was like a SQL Server Enterprise with about 48 cores or something like that.
- I said, "So you might have moved it over there, and you might think job done, but now you're gonna get a big bill," and that was just one server.
- So, and I appreciate it's, again, it's looking at the practicalities because if you've got a transitional service agreement you need to exit, you can't spend a year trying to transform that thing, 'cause you've got to get off the TSA.
- But you need to understand there needs to be a trajectory of how you're gonna transform it and move.
- And, and, and absolutely, it becomes more messy because you've got security implications or performance implications.
- And, and, and, and even the same with, with AI, and you're seeing it, you know, com- Microsoft are going in, um, and giving everyone a Copilot license, but no one really knows how to use Copilot.
- And then you're finding that people are utilizing their own ChatGPTs or Claude or something, and your data's, like, leaking out of the organization, 'cause people aren't being told how to use these things, how to, like, leverage the tools.
- And, and I, and I think, again, a lot of the hype always comes, "Well, yeah, but you can create a, a business plan."
- And a friend of mine said...
- So I asked- ChatGPT or Copilot, right, you know, cr- could remember a business plan and it, precisely what you said, the, the data, the context wasn't there, so it produced some fancy graphics and maybe some bar charts, but it was, it was completely irrelevant.
- So it's like, you know, bad data in, bad data out.
- And, but this comes back down to even transformations when I've done, um, you know, data compliance transformations and m- moving from things like, you know, home drives over to SharePoint.
- If you've g- got data in a bad place, if you don't sort it out, it's gonna be bad, and you start asking questions of bad data, you're gonna get bad answers.
- So, and, and some of this is really fundamental.
- It's almost obvious, but everyone's m- almost, like, sleepwalking into exactly the same thing all the time.
- So, you know, some s- you're not gonna fix everything, but some- somehow making small changes and getting some of these messages out, and yes, you can't sit and transform your data for the next five years, but how can we take niche-specific use cases and then start to look at adopting them, whether it be that with, with, with cloud, with AI, with whatever next co- w- whatever's coming next, then we'll- it'll be exactly the same thing.
- Exactly.
- There, there's always a next.
- Yeah.
- History has shown us, so.
- Yes.
- Fantastic.
- Well, appreciate, uh, you being on the call.
- Andy, uh, the best way for people, um, to get in touch with you is through LinkedIn, presumably, or, like I said- Yeah, yeah.
- My, my LinkedIn, yeah.
- In, in the process of getting all that updated, updated and so on, like, but yeah, L- LinkedIn for certain, yeah.
- Fantastic.
- Well, I recommend to people, uh, checking you out.
- Uh, thanks so much for being on, on the show.
- I really appreciate it.
- And, and as a reminder to everyone, this show is sponsored by The Consulting Launch Method, where I help experienced tech professionals build their own consulting business without spending years figuring out the business side.
- We've helped clients go from first idea to first clients in 90 days and six figures in a year.
- To learn more, connect with me on LinkedIn or send me a message.
- Until the next episode, Andy, thank you.
- Thanks very much.