Rinse, Repeat, Regret: Why Internal Change Keeps Missing the Mark
In this episode of Lessons Not Yet Learnt, host Kiran Kachela is joined by Luke Phillimore and Alex Spencer from the University of Nottingham to unpack one of the most costly patterns in transformation: change teams brought in too late, pushed to deliver too fast, and disbanded too soon.
Drawing on their own experiences in higher education and beyond, Luke and Alex reveal why change so often fails before it’s begun, how leadership behaviours shape outcomes, and why organisations must go and see what’s really happening on the ground. From overlooked waste to leadership blind spots, this conversation shows why lessons still aren’t being learnt and what needs to shift to get change right.
In this episode we cover
- The spectrum of change and why one size never fits all
- Why reactions to change are consistent across sectors, but support is not
- Change done to vs change done with and the power of early involvement
- The importance of go and see and why leaders must leave the boardroom
- Leadership blind spots and the role of vulnerability in driving trust
- The setup to fail pattern of hiring, under-resourcing, and cutting change teams
- The implementation gap between diagnosis and delivery
- Why cross-sector patterns prove these mistakes are everywhere
About Our Guests
Luke Phillimore – Operational Excellence Leader
Luke is a strategic and results-driven Operational Excellence Leader with over 15 years of experience leading transformation and continuous improvement across complex organisations. A certified Lean Six Sigma Black Belt, he has delivered enterprise-wide change initiatives, enhanced operational efficiency, and fostered a culture of innovation. Luke’s leadership has driven measurable outcomes in both higher education and healthcare sectors, including a university-wide change strategy and Lean practices that eliminated thousands of hours of non-value-adding work. He is also a recognised speaker and contributor in Lean, change management, and strategy deployment in Higher Education.
Alex Spencer – Lean Six Sigma Black Belt and Consultant
Alex has over 15 years of experience driving operational excellence and transforming how organisations work. Formerly Associate Director of the CI Lean Team at the University of Nottingham, she has led impactful change across energy, estate agency, and higher education sectors. Now launching into consultancy, Alex brings a collaborative, hands-on approach that empowers teams to solve problems, make smarter decisions, and drive their own success.
Play this episode
Read the transcript
00:00:00:00 – 00:00:35:00
Kiran Kachela
Lessons Not Yet Learned is the podcast that uncovers the costly mistakes that businesses keep making and how to finally move past them through storytelling, candid conversations, and expert perspectives. I’m on a mission to challenge outdated thinking. Bring those overlooked lessons to the surface, and drive meaningful change one story at a time.
00:00:35:00 – 00:00:43:03
Kiran Kachela
Hi. Welcome to Lessons Not Yet Learned. The podcast where we uncover the costly mistakes that businesses keep making so that you don’t have to.
00:00:43:03 – 00:01:02:00
Kiran Kachela
I’m your host, Kiran Kachela. And today I want to tackle a pattern that we’ve seen repeated far too often in the world of transformation. The costly cycle of change teams being brought in too late, being pushed too hard to deliver, and disbanded too soon.
00:01:02:00 – 00:01:10:06
Kiran Kachela
Now, believe me when I say I have seen this from every conceivable angle over the last two decades of my career in transformation.
00:01:10:06 – 00:01:12:10
Kiran Kachela
I’ve been on the receiving end of change.
00:01:12:12 – 00:01:49:20
Kiran Kachela
I’ve led change as an employee. I’ve delivered change as a consultant. And now I lead projects, and we work across industries to drive change. And trust me when I say it doesn’t matter which seat at the table you’re sat on. This is a challenge. And the cruel irony is that in today’s landscape, where businesses are struggling to save costs, the very teams designed to help drive change and efficiency, those change inside teams are often the first to face the axe.
00:01:49:22 – 00:02:16:01
Kiran Kachela
They’re disbanded too soon. Just in the thick of initiatives that were meant to deliver. Now, let me tell you a recent story. My team at CI Projects were called in by a university that was facing a looming crisis. They had a system, a payment system that was due for decommissioning. It was on its last legs and it needed urgent replacement.
00:02:16:03 – 00:02:30:12
Kiran Kachela
Now the university knew about this maybe several months, if not years in advance. Yet it took this burning platform, this undeniable threat of this system being
00:02:30:12 – 00:02:52:05
Kiran Kachela
decommissioned in four months for them to finally act and recognise that they needed resource to help deliver this. So despite the fact that the time was ticking, you know, time was slipping away and every second counted, they still spent a few weeks just confirming resource before they actually went ahead with the project.
00:02:52:07 – 00:03:03:19
Kiran Kachela
So by this point, we were really, really far behind schedule. My team actually, our projects were parachuted in to help turn things around in a very short space of time.
00:03:03:19 – 00:03:22:23
Kiran Kachela
Now, when the team arrived on site, they were met by a utterly overwhelmed but heroic project manager who up until now had single handedly led this project wearing many hats. She was a project manager. She was a change manager. She was a business analyst. She was a subject matter expert.
00:03:23:03 – 00:03:55:02
Kiran Kachela
You name it, she did it. And so by this point, she was absolutely exhausted. And so when she saw the team, there was this sense of relief that just washed over her face and this invisible weight just lifted off her shoulders. She was so, so, so happy that the team had arrived. So the team got stuck in, got embedded, got their hands dirty, rolled their sleeves up, and I’m really pleased to say that collectively with the project manager, they actually did it.
00:03:55:04 – 00:04:25:17
Kiran Kachela
Despite that short space of time, they turned things around. They started to build engagement and momentum. Everyone started to understand this project was happening and what it meant for them. So we were starting to see those first glimmers of hope that this project might actually land. But just as we were hitting our stride, the axe fell. The team was abruptly disbanded.
00:04:25:17 – 00:04:41:06
Kiran Kachela
the university decided to retreat to a very slim team, back to this single project manager who really needed the support. And they prioritised short term cost savings over long term gains.
00:04:41:06 – 00:04:45:16
Kiran Kachela
from their perspective, we’d already done the comms. You know, there wasn’t much more to do.
00:04:45:18 – 00:05:11:15
Kiran Kachela
And little did they recognise that there was so much more to do to help drive this project forward. Now, I’m sad to say this story did not have a happy ending. The university up to today is still having to tackle some of those challenges that have fallen out from the project not being delivered successfully. And it’s just a shame
00:05:11:15 – 00:05:15:12
Kiran Kachela
We don’t recognise that it’s actually going to cost much more in the long run
00:05:15:12 – 00:05:18:03
Kiran Kachela
than just getting it right first time.
00:05:18:03 – 00:05:23:07
Kiran Kachela
This is a classic textbook case of rinse, repeat regret.
00:05:23:07 – 00:05:37:21
Kiran Kachela
Now, I’m really pleased to welcome my guests on today’s podcast. Luke Phillimore and Alex Spencer from the University of Nottingham, who have over 15 years of experience in transformation. And they are the associate Directors of change and CI.
00:05:37:23 – 00:05:49:23
Kiran Kachela
Now, just to confirm, the story I just shared is not in relation to that institution. However, they have their own first hand experience and I’m really looking forward to hearing more.
00:05:49:23 – 00:06:13:20
Kiran Kachela
So welcome, Alex Spencer and Luke Phillimore.
00:05:49:23 – 00:06:13:20
Alex Spencer
Thank you for having us.
00:05:49:23 – 00:06:13:20
Luke Phillimore
Yeah. Thanks, everybody.
00:05:49:23 – 00:06:13:20
Kiran Kachela
So, Alex , you and I have been talking for quite a while now. Probably a couple of years about change and lean. And every time I speak to you, I’m always just so impressed by what you’ve been doing. The journey you’ve been on. So where did the key and change journey start?
00:06:14:13 – 00:06:40:10
Alex Spencer
So probably a bit before, we sort of connected and been a team manager and have worked for a large company. Where McKinsey model. The five lens model was what they brought in. So I went through that as a manager, and then just absolutely it was such a revelation of what an I’ve been making my life so difficult for myself without realising it, and sort of fell in love with it.
00:06:40:10 – 00:06:58:13
Alex Spencer
So I worked that way, you know, with that sort of lean thinking head on for about a year. Still running a team. And then there was an opportunity to move into the operational, excellence area, and that’s when I became a practitioner. And then my journey has gone on from there. And then my next move was into higher education.
00:06:58:13 – 00:07:22:15
Alex Spencer
So that was the first time I’d ever been in higher education. But I think the fact of coming from a very commercial background, of having a slightly different lean approach and coming into thinking actually there’s some real thinking that I can bring forward into this about ways of working.
Kiran Kachela
Okay. And so, so Luke you were already embedded at Nottingham when Alex joined.
00:07:22:17 – 00:07:52:13
Kiran Kachela
So where did this sort of joined up approach around trying to drive this CI and lean and as you say, trying to integrate other models and approaches start.
Luke Phillimore
Yeah. So, the University of Nottingham had been doing bits of lean for a number of years. So our old, boss Mick, he joined the university around 2012, did some lean work, but then and then he was given the go ahead to establish a lean team.
00:07:52:13 – 00:08:20:09
Luke Phillimore
We were called getting in shape, which was always a bit of an interesting name. Some people did actually think we were. Yeah. An exercise, and fitness group. But obviously we’re supposed to be getting the university into shape. We all brought different perspectives on how to do this type of work. I think because I’d been at the university a
number of years already, I, maybe had less of the lean knowledge, but really understood how the university worked.
00:08:20:11 – 00:08:48:05
Luke Phillimore
And so when Alex joined the complementary kind of by that time, I’d really upskilled anyway. But the complementary of someone coming in with all that external experience, plus someone with all of the internal experience, I would say, really supercharged the work that we were able to do.
00:08:20:11 – 00:08:48:05
Kiran Kachela
People can fall into the trap of not enabling that outside perspective and fresh perspective and can become quite institutionalised sometimes.
00:08:48:05 – 00:09:20:05
Kiran Kachela
And actually, you brought something from a commercial background which you saw the value in straightaway, like so. That’s amazing. So, getting in shape, talk to me. What was a what was the landscape at the time that instigated this great initiative?
00:08:48:05 – 00:09:20:05
Luke Phillimore
I think at the time the university was doing well, but it was recognised that, processes could be very, standardised.
00:09:21:06 – 00:09:59:18
Luke Phillimore
There was definitely a lot of waste in the, so it was, it was actually started, from our CFO, and we had financial targets attached to us because of it coming from the CFO. But pretty quickly in 2020, those targets were dropped because it was recognised that, as a an internal team, but helping departments, make their own efficiencies, we couldn’t be held accountable for someone else making that kind of financial savings so that those targets were dropped.
00:10:00:24 – 00:10:21:17
Luke Phillimore
But we always had, three modes of working, and this is where I’m going to forget what we also, you’re going to have to remember, so in fact, I’ve already forgotten why I’m. If I’m wrong, right.
00:10:00:24 – 00:10:21:17
Alex Spencer
Enabling improvement.
00:10:00:24 – 00:10:21:17
Luke Phillimore
Thank you.
00:10:00:24 – 00:10:21:17
Alex Spencer
Building lean capability. And the third one, though, was for that. Yeah. The third thankfully that memorable.
00:10:21:17 – 00:10:53:04
Alex Spencer
Yes. But essentially there’s the long term goal of making lean thinking just the way that you work, which is that really long journey that you go on. And that’s probably what we mostly talked about when we had catch ups around. That’s really what I was pushing for was that long piece, training. So we did we built our own, yellow orange green belt training, and assess those ourselves and deliver those internally.
00:10:54:05 – 00:11:12:01
Alex Spencer
And then we had enabling improvements, which would be people coming to us and just saying, I’ve just need us to help with a thing. I just need to solve this problem. And then we would just go in and help them with, with solving that problem and be those sort of most of the time, expert facilitators is really what they needed.
00:11:12:01 – 00:11:53:07
Alex Spencer
Was that just somebody independent in the room because we weren’t aligned in any where the financial, target had gone. That means you can be really independent when you go into a room and just facilitate what the best route and help them get where they need to be. And that was a real pull for me moving to the university when those financial, targets had been dropped because I had worked in a previous company, had worked somewhere as an internal lean team where you were given a target, and that made it so difficult because the onus when we go into an area became we’ve already had 20% taken out of our budget.
00:11:53:07 – 00:12:21:21 Alex Spencer
How are you going to make that happen? And that just is so, it’s so the opposite. What lean thinking needs to be, which is how do you empower other people to make their own change to deliver it? So straight away as you walked in, it was all on you to to make it happen. And that just felt such, such an uncomfortable place as a lean practitioner to be working in that environment.
00:12:21:21 – 00:12:55:23
Alex Spencer
So that’s been great since that dropped that we could just go in and help people and, and empower them to do make their own change.
00:12:21:21 – 00:12:55:23
Luke Phillimore
Yeah. We did still get work from the top down saying there’s this area and we need to to you guys to go in and have a look at it. But, most of our work was bottom up driven, where people identify problems and contacted us normally through word of mouth that you search for or that colleagues had used as, that independence was so important.
00:12:55:23 – 00:13:18:03
Luke Phillimore
I used to I mean, I still do sometimes just stand there and say, look, I don’t actually care. You can do what you want. It’s up to you to decide. All I’m here to do is facilitate that process.
00:12:55:23 – 00:13:18:03
Kiran Kachela
People align lean. They assume lean is cost cutting, has a negative, reputation for that. And actually I always say lean is value.
00:13:18:04 – 00:13:41:00
Kiran Kachela
Value can be defined as different things. You know, value might be cost, but it could be speed. It could be experience. It could be, you know, in the university case is student experience. That’s value. So in that process, what were some of the challenges you found when you were trying to deliver your value proposition as a team?
00:13:41:02 – 00:14:06:08
Luke Phillimore
Lots. I think, I think as me and Alex have, progressed within the university, the challenges have changed. So when, when we were first working together, we were both seen lean practitioners and almost at the coalface of doing that type of work. Then it’s always the same things that you get that you don’t have time or they don’t have time.
00:14:06:20 – 00:14:36:15
Luke Phillimore
They don’t have the people, or, they don’t really understand the problem that they’re trying to solve. So the, the, the challenge was really all around building that trust and credibility. And I think we both had success in different areas of the University of doing that. But I would say there were other parts of the university that just complete closed book and, didn’t want to play, weren’t interested.
00:14:36:17 – 00:14:58:07
Luke Phillimore
We always, when where the wind was blowing. So, you know, why hammer against a closed door? If there’s somewhere that wants us, we’ll go there. On the premise that, certainly in a university setting, that people talk, and if you do a good job somewhere, then they will tell other people and that will generate the work.
00:14:59:02 – 00:15:27:00
00:14:59:02 – 00:15:27:00
Luke Phillimore
But, yeah, that standard problem of not enough time and not really understanding their own problem,
00:14:59:02 – 00:15:27:00
Alex Spencer
We made that decision to just go, we’re just not going to force our selves. It’s going to be we’ll go where we need to go. Everybody always loved the training, so we picked loads of people up from that. And then especially at the top for, except board, we started doing activities sort of rapid improvement event, a Kaizen event, essentially.
00:15:27:00 – 00:15:48:05
Alex Spencer
That sort of 3 or 4 days in a room and we would have a sponsor, very much in the early days, once one person on the exact board became a sponsor, then everybody else go, well, they’ve been a sponsor. And why have I not been a sponsor? And, so actually we built an awful lot on reputation over that time, and that’s what filled our for our work.
00:15:48:05 – 00:16:05:23
Alex Spencer
But really it enabled us to grow to manage the volume.
00:15:48:05 – 00:16:05:23
Luke Phillimore
It’s interesting as well though, because they all then wanted a rapid improvement and yeah. And going back to that didn’t really understand the problem. So unless you understand the problem, you don’t know whether the rapid improvement of that is actually the what, what you need.
00:16:06:00 – 00:16:35:09
Luke Phillimore
And so we ended up doing lots of work, trying to educate people, go, yeah, okay. You can have one or you can have this. Let’s actually have a conversation instead. Just asking for a think. Can you just ask for our help and we’ll wait.
00:16:06:00 – 00:16:35:09
Kiran Kachela
Yeah, yeah. But so you guys adopted this early adopter approach essentially where you decided rather than pushing, you know, closed door, you’re going to take those early adopters, those light bulbs that you see out across the organisation that really want to embrace this change.
00:16:35:09 – 00:16:55:17
Kiran Kachela
Because essentially lean is a mindset and you can’t force a mindset on somebody, right? What you can do is you can encourage. And I guess one of the ways you did that is
actually by showing, learn by doing. Well, yeah. But people being able to see the things that you’re doing that then attracts them and makes them think, oh, you know, I want to be part of that.
00:16:55:17 – 00:17:31:01
Kiran Kachela
I want to jump on the bus. Yeah. So yeah, that that absolutely sounds like it. It’s worked really well. Have you found examples of lack of investment or or responding to light everywhere.
00:16:55:17 – 00:17:31:01
Alex Spencer
Everywhere. I’ve worked in big UK global companies before, but actually working in university is literally like working in a small town of individual little businesses that work like individual businesses see themselves in that way, and don’t necessarily think, you know, I’ve worked in huge corporations, but they’ll see themselves as one thing.
00:17:31:03 – 00:18:00:06
Alex Spencer
And you don’t get that in HE. I’ll give you an example. Our previous vice chancellor wanted a rapid improvement event. Was huge. It ended up about 40 people. It was a student plus staff crossover. Cross-functional sort of process. Lots of people involved. And that would normally be a ten week run into that to make sure the sponsors know exactly what they’re we’ve really nailed down what the objectives are.
00:18:00:06 – 00:18:17:11
Alex Spencer
We know exactly what we’re getting out of it. We’ve got the right people in the room, of what needs to go. And, I had about three weeks and it was like, well, the vice chancellor wants it, so it’s just got to happen. I ended up having to lead an awful lot of that, which actually isn’t what you want to do.
00:18:17:13 – 00:18:32:16
Alex Spencer
You want the sponsor to come and get set them off, and then you want a team leader that you’ve coach for those ten weeks in to be able to be the front man, and you can just be the voice in the back going, is this activity really getting where we need to be? I’ve got something up my sleeve and I can just stand up and present.
00:18:32:18 – 00:18:59:11
Alex Spencer
If there’s a specific lean tool or technique we’re going to use. But yeah, they’re actually going to own the the event and run. The day is set.
00:18:32:18 – 00:18:59:11
Kiran Kachela
So for you change is how you set it up and yeah, how they own it. Yeah. So for you, you found that the impact of bringing the change team in too late essentially was that actually everyone didn’t own it the way in which they should write.
00:19:00:07 – 00:19:24:18
Kiran Kachela
And, and actually you ended up having to lead a lot of it to get it done in a very short space of time. The consequence was lack of everyone else being involved and owning it.
00:19:00:07 – 00:19:24:18
Alex Spencer
And yeah, I think the what I view as a success after you’ve done those events, is that essentially you don’t see us in the room after the event.
00:19:24:18 – 00:19:43:12
Alex Spencer
Lots of people would come and ask me additional things, or they would refer to it as a getting in shape event. And it’s like, if it’s been successful, I don’t want anybody to think it’s a getting in shape event. It should be seamless on the background. It should be whatever department is running it. Whoever the sponsor is, it’s their event.
00:19:43:12 – 00:20:05:08
Kiran Kachela
Yeah, I love that. Like invisible fairies that come in and wave our one to make it work, but we don’t need the credit because this is about everybody taking ownership of that change and continuous improvement. And Luke Phillimore, do you have any examples of where you’ve seen teams being deployed too late.
0:19:43:12 – 00:20:05:08
Luke Phillimore
Yeah, I’ve rather than from a lean or sales perspective.
00:20:05:13 – 00:20:42:13
Luke Phillimore
And so my more recent role is been supporting the university strategic projects and programs. And I don’t know whether it’s too late. It is one way of looking at it. I would I would probably phrase it more of an undervalued, and, and misunderstanding the, the need to bring people along on the whatever the change is. And so often it’s either under-resourced, from the outset or just not resourced, and then you get towards the end and then they’re all of a sudden, oh, well, no one wants to do this thing.
00:20:42:13 – 00:21:09:14
Luke Phillimore
Can you think, well, no wonder why no one wants to do this thing. It’s not a massive surprise. So, I would I would argue that the majority of the projects and programs that I’ve been, supporting over the last couple of years, that is, that has been the reality that
it has been under-resourced or undervalued. Yeah. And you then you then see it in the, in the aftermath of, of the go live.
00:21:09:16 – 00:21:33:07
Kiran Kachela
Absolutely. The impact is felt. So when we say, undervalued and I know exactly what you mean there, the value is not always recognised. Why do you think that is. What what’s missing from the senior leadership team?
00:21:09:16 – 00:21:33:07
Luke Phillimore
I think it’s a lack of understanding of what it actually takes for people to change their behaviour and do something differently.
00:21:33:08 – 00:22:11:03
Luke Phillimore
So we have, recently implemented a large ERP system and the X, you can look at it two ways. You could look at it successfully because it went live. And people are using it and it’s it controls our payroll. People are getting paid generally. So yeah, all of those things. But then there’s also a lot of, unforeseen or probably should have been foreseen stress that has been caused on people and the, the change team on, on that particular program worked incredibly hard.
00:22:11:05 – 00:22:34:05
Luke Phillimore
But we’re talking 9000 staff. And yet the actual amount of resources put into helping support those staff change their behaviour, it’s been, I think, way too small. So I don’t think I actually answered your question. I just gave you another example of over why I’ve never yet go wrong.
00:22:11:05 – 00:22:34:05
Kiran Kachela
what do you think would help?
00:22:34:05 – 00:22:58:23
Kiran Kachela
What do you think could help leaders to understand better what is really needed and the impact of change, not done right? What what’s needed?
00:22:34:05 – 00:22:58:23
Alex Spencer
I think the, I have so many things in my brain over when I talk about the, I think there’s a couple of things for me, which, again, it’s not just about the university from other places I’ve seen.
00:22:58:23 – 00:23:23:17
Alex Spencer
I’ve seen this sort of pattern through particularly sort of right at the top, is a the element of going out and actually seeing what’s going on. I do definitely see a pattern of being told what’s happening or using data to understand what’s happening. But how often do they actually leave in office, go out there, do those things?
00:23:24:06 – 00:23:49:08
Alex Spencer
I think from a CI or change perspective, one of the other things is actually understanding what we do. And I think this is a really generic thing across, any function, any sector is, the element. And I’ve had this happen in more than one company where they go, we don’t need a change team or we don’t need a continuous improvement team.
00:23:49:08 – 00:24:16:04
Alex Spencer
Everybody can do continuous improvement. And I think if you ask anybody in any company, do you continuously improve? They will say yes. If you say, do you solve problems, they will say yes. So this misconception that it can be done by everybody and everybody will do that starts to happen. And therefore we don’t need to pay for a continuous improvement team because everybody will do it.
00:24:16:06 – 00:24:39:19
Alex Spencer
I think it’s about them understanding actually what we do and changing those questions. If you actually asked people, do you fix things and do you have to fix them more than once? That is a different answer. Do you work in a continuous improvement way and actually use tools and techniques? Do you, do you stand up and talk about performance?
00:24:39:19 – 00:25:15:17
Alex Spencer
Is everybody have do you have things written down that you will get much different answers to just do you continue to improve? And that’s not people trying to hide it. That’s people’s misunderstanding of what we actually mean by continuous improvement. So I think because we’re not frontline, we can then become in danger. And it’s happened to me more than once, where you’re then seen as a nice to have at the point where as a business or an institution, this is absolutely the point where you’re at crunch time where you really need us in this profession to be able to come and help.
00:25:15:21 – 00:25:39:08
Kiran Kachela
Playing devil’s advocate, many people say, well, this is just a nice to have function and continuous improvement as part of everyone’s job. Yes, it is, but there is a skill set there. There is a need to instigate that inspiration and provide people with support and the frameworks she talked about the methodologies. But your question there around, are you continuously improving something?
00:25:39:08 – 00:25:59:23
Kiran Kachela
But then still seeing the same problem reoccur over and over again? It’s a result of sometimes people that either don’t have the capacity or don’t have necessarily the rich toolkit and framework and capability to actually get to the root cause of the problem and solve it once and for all. And I think that’s that’s the value that a CI team can bring.
00:26:00:00 – 00:26:24:00
Kiran Kachela
But actually the CI team is almost leading everybody else with that mindset. It’s a it’s absolutely a mindset. And you need to work hard to get everybody wanting to be on that journey. Yeah. What about on the back end. So you’ve now delivered a project ERP as an example okay. So in in plane sort of have we met this project objective.
00:26:24:00 – 00:26:56:01
Kiran Kachela
Well we went live with the ERP system. What does the backend of that look like. Are we investing in making sure that these changes are sustained and controlled. Are we still keeping resources on there or do we pull them too soon?
0:26:24:00 – 00:26:56:01
Luke Phillimore
Yeah. So the get pulled too soon, particularly on one of the big challenges with funded projects and programs, is that the funding is normally tied to the end date of the project or program, which is typically a couple of weeks after go live.
00:26:56:03 – 00:27:27:04
Luke Phillimore
So if it was a system, for instance, and then it’s just like and then we just hope that everyone is, is going to sustain the change. So it nearly always, well, I would really like to see is for change support to be funded, slightly differently. So still out of the overall budget envelope. But those contract dates or secondments, however it is that you resourcing it to continue for a number of months now.
00:27:27:05 – 00:28:04:09
Luke Phillimore
Obviously it depends on the size, the project and program etcetera. But the again, going back to that RPA wasn’t until quite towards the end of the project that there were suddenly when we’re going to need to team to support this, system, on an ongoing basis as like, of course you all. So I have some sympathy for, for project teams in those situations because you, you’re embedded in the project and your focus is on the deliverable and the next date and the next milestone.
00:28:05:01 – 00:28:27:09
Luke Phillimore
But there really should be some. We need to stand up and have a look around and think about what you know. It’s not just about the next month or the next three months. It’s what’s the next 12 months look like, etc..
00:28:05:01 – 00:28:27:09
Kiran Kachela
Now, I have to say, from my experience too, I’ve seen exactly that. I’ve seen project resources, signed off on a budget, up to maybe a week or two after go live.
00:28:28:01 – 00:28:47:16
Kiran Kachela
And then we assume that magically the benefits are all going to be realised and everyone’s going to have adopted the new way of working, just magically don’t they don’t need support. And actually, I think you’re right. I think we’re too focussed on the deliverable rather than what good looks like. What is the outcome that we are actually trying to achieve?
00:28:47:16 – 00:29:14:14
Kiran Kachela
What does good actually look like? And if we change the goalposts on that, perhaps we think about resourcing slightly differently. Yeah. But you know, in many cases it’s an afterthought. We realise later on that, oh, actually we might need some money to actually support this. So yeah, it’s, just realigning that goalpost.
00:28:47:16 – 00:29:14:14
Luke Phillimore
I think that there’s some there’s a mind set shift that’s needed, which is we’re not looking at what we’ve delivered.
00:29:14:16 – 00:29:41:16
Luke Phillimore
We’re looking at why we’re delivering it, because it’s the why, the benefit that’s actually important. So, we might create a new policy and they go, well, well done that when, we’ve thrown over the ball now there’s a new policy everyone’s going to be I don’t know, accountable for explaining that. And it’s just nonsense. And so what we should be focusing on is, why are we putting that new policy out there?
00:29:41:20 – 00:30:03:21
Luke Phillimore
And what do we need people to do differently as a result? And how do we measure that so that we know we’ve actually achieved the point at which it’s just pointless, isn’t it?
00:29:41:20 – 00:30:03:21
Kiran Kachela
Exactly, exactly. So where are you now? So you’ve obviously been on this great journey of continuous improvement with all the great initiatives that you guys have been leading, where do you sit now?
00:30:03:23 – 00:30:34:07
Luke Phillimore
Okay, so, unfortunately, the university and higher education in general finds itself in a particularly tricky financial situation. And, as we’ve already discussed, sometimes, functions such as ours are the easy targets for, making those cuts because of their lack of on the potential lack of understanding. So where we’re both at the moment is that, the university’s restructuring and within that restructure, our teams don’t exist anymore.
00:30:34:17 – 00:31:04:05
Luke Phillimore
So, we’re both taking the opportunity to take, voluntary redundancy and, move on, on to bigger and better things.
00:30:34:17 – 00:31:04:05
Kiran Kachela
That’s, it’s a shame, but also equally exciting, for both. But yeah, as you say, I’ve seen this play out across higher education sector. We work with a number of higher education institutions. And it is really sad to see that often it’s the CI and the change team that are the first to be axed.
00:31:04:05 – 00:31:29:22
Kiran Kachela
Actually. The irony of that, they’re often the ones that are there to help drive the organisation through some of these turbulent, economically, challenging times. So yeah. Thank you for sharing. What’s your one lesson that you want to share with the audience today? Your one lesson that you feel is not yet learnt.
00:31:04:05 – 00:31:29:22
Alex Spencer
Go and see, get out.
00:31:29:22 – 00:31:50:05
Alex Spencer
The higher up I see people go through organisations, the less and less of that starts to happen. So, and then the company I work for initially, where I learned that we it’s just getting that balance then because they did learn that lesson because we were doing the McKinsey five rounds, they were all encouraged to go out and do things.
00:31:50:07 – 00:32:09:01
Alex Spencer
The balance to that is just they’re making sure they’re not they don’t become reactive to the one thing they happen to have seen when they go out and sit in, because then it was suddenly be we’ve seen this one thing that this customer will change the whole policy across the UK. Like that may never happen again. Yes.
00:32:09:02 – 00:32:28:23
Alex Spencer
No, I’ve never come across that before. It may never happen again for another three years. So but the more they get out and do that and practice, the more you can handle that reactive. And then they become less reactive.
00:32:09:02 – 00:32:28:23
Luke Phillimore
And I think the more that teams get used to it as well, because the first time happened is that in everyone’s mind, what was the big boss?
00:32:28:23 – 00:32:55:23
Luke Phillimore
It kind of reaction, and then the other thing that often happens within a university setting is that, if someone very senior is going to visit a department, it becomes almost an event, a bit like the Queen visiting or something. And I remember, we had a new senior executive join the university and they went on tours around all the schools, and I was working in one of the schools at the time, helping them do some Sally work.
00:32:56:00 – 00:33:13:21
Luke Phillimore
And there was like this big run up and prep event for Friday, we’re going to do this, and I’m going to do this and we’re going to do this. It’s not senior. It’s like will have got absolutely no, reality of what it’s actually like on a day to day basis.
00:32:56:00 – 00:33:13:21
Kiran Kachela
So you’re one lesson not yet learn is go and see.
00:33:13:21 – 00:33:31:01
Kiran Kachela
And as she said, Alex, the higher you get up the chain, the less and less it happens. But then equally, when it does happen, we need to like make sure we’ve got the right balance of understanding what we’re looking at and how we respond. Brilliant. Thank you so much for today’s episode. That was really, really useful and valuable insight for us.
00:33:31:01 – 00:33:32:19
Alex Spencer
Thank you.
00:33:31:01 – 00:33:32:19
Luke Phillimore
Yeah, thank you very much.
00:33:32:23 – 00:33:54:08
Kiran Kachela
So the key facts from today’s episode is go say step away from the screen. Come out of the boardroom and go to the shop floor. Go and get your fingernails dirty. Go and speak
to people and go and see where the real problems lie. Because it’s only then that you truly understand what can be improved and the value of continuous improvement.
00:33:54:10 – 00:34:26:01
Kiran Kachela
Now go see is actually a principle in the lean philosophy, and it’s called gemba in Japanese. And it actually translates to where the real value is created. And it was developed by a Japanese industrial engineer and businessman called Taichi Ono, who is like the epitome of lean and the father of something called the Toyota Production System, which organisations across the world look to to look at what good looks like is the gold standard.
00:34:26:03 – 00:34:34:02
Kiran Kachela
Now, did you know that Jeff Bezos, founder of Amazon, when he was building his tech empire, actually
00:34:34:02 – 00:34:53:05
Kiran Kachela
decided to make all of his executives take shifts on the customer service desk so that they could really understand what was going on, what customers needed, what problems were being faced, what types of questions were being asked. And that is a true example of gemba.
00:34:53:10 – 00:34:56:04
Kiran Kachela
Or go see, in practice.
00:34:56:04 – 00:35:02:02
Kiran Kachela
This is the way to really understand first hand operationally what’s actually going on.
00:35:02:02 – 00:35:15:21
Kiran Kachela
Now I’ll leave you with a quote. The Taichi I know himself once said, he said, don’t look with your eyes. Look with your feet. Thank you very much for joining today’s podcast episode, and we’ll see you on the next one.
00:35:18:24 – 00:35:24:15
Kiran Kachela
This episode was sponsored by Fujitsu, your digital transformation partner in higher education.