BẢN CHÉP ÂM THANH 🔗
Perry Timms: up to recently what HR's been really good at is fixing. So it's been less of an architect and it's been more of a handyman, interior designer, whatever. But it hasn't completely fundamentally re-architected the house for what it needs to be in a modern world. So we've got to go from fixer to designer. We've got to say actually, what do you want this dwelling to do? And how do you want the flow of the rooms and the heating and the infrastructure and so on. And that's a very big departure from fixing things to designing things because you are literally going, we we we can continue fixing things if you want, but at some point in time it's just going to be completely null and void and not fit for purpose. So therefore, if we go further left and redesign it, then we're likely to have a future sustainable model. So so it moves from responding to the system that somehow the organisation has evolved into or the top team insist to going th this is how we need to be in order to perform and be innovative and an employer of choice and so on. So I think they're gonna have to get a bit braver in challenging the sort of orthodox structural conformity that most C suite leaders seem to want and come in with some alternatives. But they need it back by by evidence and data. So the the kind of calling in this is to go, don't just expect because it's morally sound or humanly right that a board is going to go, yeah, let's do that then. Cause they're well, what's that mean to the bottom line in efficiency? You've got to have all of those things running in in that sort of argument. But but instead of being waiting to be told by the organisation, you are sensing what the organisation could become. And you're saying, here's how we design for that. And that is systems, that is in the science that you use. It's the processes that underpin it, but it's also the products you lead with, the products that HR builds, that its people consume, that create value. That that we've got to get much better at what we put on the table as a product, not just here's a policy because it's compliant with the law. It's like here's a policy that inspires people to be good corporate citizens and not be nasty to customers or steal from us. It's like move that doll a lot higher and we could find an organisation that actually becomes what it could be. So that's what I mean by architect. We stop fixing things, we stop doing a bit of interior decorating, and we actually go, what is this dwelling for? How do we make the best of it? How is it modern and sustainable? And that means we've got to redesign and or design new.
Riddhika Khoosal: Hello Perry. Welcome to the Systemic Talent Management Podcast. It's an absolute delight and honor to have you with us today.
Perry Timms: Thank you, Ridica. I'm I'm so looking forward to this. I I get the very fortunate honour of being on quite a few podcasts and I often say that they are just a little snapshot of of thinking and time. So each one of them I think stands on its own feet, but I'm really looking forward to this one.
Riddhika Khoosal: think it's safe to say so are we. Many people know you as one of the leading thinkers in HR and OD. You've been named by HR magazine as one of the most influential thinkers, and you've been inducted in their Hall of Fame. these are only just some of many accomplishments that you've achieved. Today, though, to kick off our podcast, I thought it might be nice for us to start off. Learning a little bit more about you and your story and
Perry Timms: Mm-hmm. Mm-hmm.
Riddhika Khoosal: if there was a particular moment or a turning point that had you, I guess, head down this path of reimagining the world of work which you have so brilliantly
Perry Timms: Mm-hmm. Hmm. Yeah.
Riddhika Khoosal: done.
Perry Timms: Thank you. yes, I mean it's one of those things, isn't it, where there are a couple of pin points in the map that you can go, now that was a crucial turning point. And then there's all these aggregated small things that come together, and you don't really notice them until you have one of those moments, and then you kinda go, Well, that's what that's been leading me towards. So it'll be a mixture of the two, ridiculous. So I think the first thing is I I've always found in in the work I've been doing. So I started in the UK civil service. I didn't go to university. I joined the UK Civil Service. Which is a terrific ground actually for finding out who you are and what you're all about because it it it offers so many options to you. So I started in administration, I went into team leadership, but I got into projects. And I think it was at the time of starting to work on projects. But I really loved it because of the start, middle and end nature of a project, the the variables and the people you brought together. And I think that was at the time something I just took, that's what you do for projects. But now I know projects are this beautiful little microcosm of everything work is about and the systems of work are about. You just don't realise at the time that you could potentially be creating at the start of something very different and very new and very lasting. So Yeah, that that was a realization of mine that I was actually made for projects. And I didn't know that until I got into them. Then during the course of working on those projects, I got to work with some technologists. So it was in the early days when government departments were converting paper records into digitized versions of them. So we're going right back to mainframes and then desktop computer rollouts and then internet services. And and there was a really big program that I was part of. And some consultant advisor was brought in by my program manager at the time who'd been developing a new way to to build software in iterative creative bursts. We'd now call it agile, but it was before agile was a thing. And so he called it rapid, responsive and predictable incremental development. And
Load full transcript
and and the responsive and
David Clutterbuck: Hmm.
Perry Timms: and and and predictive were the two really nice, almost like energies around it. So he was saying, look, you can predict some of this stuff and and build it based on what you know the specification is, but you have to then be alive to the fact that you're almost probing a system to change it. So therefore you have to be responsive to what it tells you is now needed that the specification either hadn't done or didn't do very well. That really opened my mind to thinking projects really are those two energies, what you know and want to improve, and what emerges. And what you have to respond to. So I think those two moments of realizing projects were this beautiful little microcosm vessel of change, and that there was a methodology within it that gave you both determinable outcomes and then really adaptive responsive change. But I suddenly thought, what what have I what have I found here? And and it's been that ever since. I've been on this quest to go, how else does this work? And where does its tentacles spread? And what does it require of us as people to behave, think and do things differently? And I just finish off this by saying there's one big realization I've had. We tend to get really obsessed about what we think and do, and that is important. But what I found is it's how are you being with it all? How do you combine it all and make you the essence of what it is all about? That's my kind of fascination as a result of all of this. So somebody once said to me that my work is about work. And I thought, Wow, it is. My work is about work. You know, I don't build cars, I don't create buildings, but my work is about work. And I'm very happy to sit in that space.
David Clutterbuck: Thank you, Puri. This doing versus being has been one of the big outcomes from the coach maturity research group, which I'm part of, looking at what do mature coaches look like. And it's not what they do, it's about developing who they are. So there's a lot of similarity here. So much of this science is coming together
Perry Timms: Mm.
David Clutterbuck: coherently. as we begin to see the same themes recurring in different contexts. So thank
Perry Timms: Mm.
David Clutterbuck: you for that explanation. So we've talked particularly, or you've talked particularly about this lovely idea of the polymorphic organisation. We've
Perry Timms: Mm. Yeah.
David Clutterbuck: talked about Agile organizations and this, and I can recall writing decades ago about different structures of organizations, but they were all static. So you produce the organisation
Perry Timms: Yeah.
David Clutterbuck: and you hoped it was going to stay like this. What you're
Perry Timms: Mm.
David Clutterbuck: proposing is something that's much more dynamic. please, how did you come to that concept and what does it actually look like from day to day?
Perry Timms: Hmm. Yeah. So it it was the start of the process, I guess, the agile thing, because I'd come across that methodology in my projects, that rapid thing, when agile actually came into being. So we're going the manifesto was about two thousand and one, wasn't it? And so I came across it around about two thousand and three or four, working with software developers who were doing it that way. And I'm like, this sounds like what I did in nineteen ninety eight, but much more dynamic. And it got me really intrigued by it. So I remember getting a book. It was the early days of Amazon. So that came through the post and I read the book and got really into scrums and sprints and so on. And thought, wow, this is almost disassembling that structural rigidity that you just talked about, David, but actually allowing you to operate within it in a very fluid and and adaptive way really appealed to me because I think by then I'd realized how bureaucracy and lumbering projects could create so much unnecessary work. That frustrated me. And I thought, can't we just go more straight lines? Or if we go squiggly, it it's to erase the the the thick lines that are slowing us down. And and Agile gave me that. That then led me to start looking at organisations that broke all the rules and changed their structure radically. So Ricardo Semler's Maverick book you see behind me on the bookcase there was a self managed organisation that just abandoned all those orthodox things that I mean that completely got me excited. So I started to research that and and so that's the long tail of it. I just wanted to acquire as much insight research and case studies of these alternatives who perhaps kept the outer layer of the organisation solid, but inside could adapt it. And I thought this is this is the change I've been looking for. And I think we've seen little episodic bursts of it, but it hasn't quite completely become the norm. And and that was a realization I had last year when I thought, What why hasn't that stuff been around for twenty years but not taken over? When it clearly makes a ton of sense and is more effective and efficient and human and everything else. And I suddenly thought, well, actually the system doesn't have a persuasive enough argument for it. Because it says, I'm not going to abandon this really safe stuff that helps us keep strong and and brings our heritage into play and makes sure we're compliant and and and do all the things that regulators like and that that people need just because it's trendy to disassemble it all. It's it almost said, I'm not going to do that. And I thought, well, how can I persuade it that there's a different way to do it? And that's when I came up with this concept that an organisation doesn't have to abandon things. It can just change shape and form according to what's best. And that might be a little bit tight and structured for a certain period of time or for a certain function. But then it might go completely unrecognizable because the system or the demands are saying, you can't do that, because that that'll just
completely negate any progress or any value you want to create. So I suddenly thought, how is that possible? Again, I went to computing and found object oriented design or object oriented programming, which has this term polymorphism in it, and it says an object can do different things depending on the data it received. And I was like, Eureka. That's what I want an organisation to do. And then I've
David Clutterbuck: Mmm.
Perry Timms: just been playing with that concept ever since.
David Clutterbuck: That's one of this is is miles away from what we see historically happening in organizations where they they have a new chief executors and they decentralized and then that guy gets
Perry Timms: Yeah.
David Clutterbuck: leaves and they centralized again and they go backwards and forwards like a swing and or a pendulum
Perry Timms: Yeah. Mm-hmm.
David Clutterbuck: and it's that's that but that's not really That's
Perry Timms: Yeah. No.
David Clutterbuck: not really reacting to the environment in any sensible way
Perry Timms: No, no. That that's almost yeah, painful restorative or retrograde and an illusion that you are actually being adaptive when all you're doing is like you say, you're just flitting between two very polarized disciplines. And what I'm suggesting is in order to stop that from happening, you you don't even have to find a middle ground. You can have it reform and reshape according to what's needed. So a lot of people have said. Great conceptually, but how on earth do people navigate that when they're used to anchoring in jobs and teams and structures and verticals and divisions? I'm like, you just have to re-architect it. Either you layer it underneath differently or wrap around it differently. And I've given people some quite convincing arguments when I've said, when chaos happens, when there's a real crisis in the organisation, what happens? Do you follow rigidity and structures and committed? And they're like, no. We just get on with it and we form tiger teams and we go off and do things and we somehow communicate when we need to. I'm like, I'm just talking about that without the stress and without it only being a kind of wow, let's just fix it now before we get back to stability. I'm saying that can be a learnt discipline that you can do all the time. And so people then go, Maybe it could. So yeah, that's kind of where I am with it.
Riddhika Khoosal: It's amazing. And I think what really I really love about this is that we're almost developing the skill of noticing what's emerging. you started off with with that pattern of being able to respond, but then to also notice what's emerging to then be able to respond
Perry Timms: yeah.
Riddhika Khoosal: back to. And what you're suggesting really is a huge departure from where we've been. And so
Perry Timms: Yeah.
Riddhika Khoosal: just for our listeners, Perry, I'd love to just go a little bit more into I guess basic definitions, if you don't mind for a moment.
Perry Timms: So
Riddhika Khoosal: So we've spoken about agile. We also know complex adaptive systems is a term that is floating around a lot in this space. And
Perry Timms: Yeah, yeah.
Riddhika Khoosal: also now we're bringing into the conversation polymorphism. So to begin with, can you help
Perry Timms: Mm.
Riddhika Khoosal: us distinguish between these? And then
Perry Timms: Mm.
Riddhika Khoosal: as we start to move the conversation into what a polymorphic organisation looks like, we
Perry Timms: Yeah.
Riddhika Khoosal: can then start to, I guess, paint the picture a little bit more clearly.
Perry Timms: Yeah. It's a really good way to frame it actually. And there's a pun there, ridiculous as well. Because if we think about it as art, what we've currently got in organizations is paint by numbers. Quite literally, that's what it is. Somebody sketches the outline and puts the color code in and and then people come and fill it in. And and dare anybody paint over the lines or do something neon and not really sort of quite boring. Because they go, no, that's not what I meant. It's like But but that's my interpretation of what I think art might look like. So there's a little bit of that going on in here, but I'll try and get it more realistic for you. It is where the form of an organisation follows the work. What I think has been for a long, long time, the human response to how do we organise at scale is to to create workers boxed in to fit something we've built as possible. That's how we've asserted control. over indeterminable variable efficiencies and so on. And I think work now, so we're talking about work that's much more complex and requires that sensing that you talked about. Work now is saying that's not the game I want to play. So I want you to wrap around me, not me fit in your constructs. Customer queries, customer complaints, customer issues are a great example. Because the customer doesn't care what your value chain and structure of command is, the customer wants an answer to a problem they've got. And the organisation ought to be why do we inflict our structure on them to get to a decision? Why don't we push the decision to where the customer is? That's almost the sort of principle behind it. So it does require us to to to shift and recombine according to what the work is. And that's where I think we've got a real challenge because everybody's used to these separated divisions, which are divisive, of of of work being handed over by us internally. And one of the concepts I'm suggesting is why don't you create spaces where the work lives and you just bring people to it? So they could be analysts, technologists, and so on. Now, there is an example in the world right now of this happening. It's a a a an electronics and white goods manufacturer in China called Hire, who run on the concept of micro enterprises. So if they have a new customer need and a new product, guess what? That doesn't start in R and D and get handed over to to supply to then go into production
to go into sales. They have small teams who do the stages of that, who almost converge together in a space to form like a super team. That's the sort of thing I'm saying, and a lot of organizations could do much more of. So they're almost anchored in their professional discipline, but they assemble with other professionals to get something built or solve a problem or create value. So it's where we have stabilizing elements at the heart of it. So strategy, finance, regulatory, but then they're supporting teams who are doing all the creative things where where the work lives. so so I guess that's the sort of concept of it really is that we find ourselves going to the work more than trying to squeeze work into what we've created. And that shift is perhaps the biggest indicator that you are more polymorphic if you can do that almost without pain and just as a normative state for people to be in. So yeah, and and I'm seeing a lot of that pop up now with AI coming in, where
David Clutterbuck: Hmm.
Perry Timms: people are going, wow, AI's taking away so much of what we've done in administrative work, let's say, or intelligence and data anal analysis. where what where do we get our bit and what do we do? It's like, well, you don't just do what you do now plus AI, you just start again almost. so I think that's that's almost like the double calling here, which is the realization of decades of us trying to squeeze work into us. And the fact that now AI say, well work's just all over the place now. So yeah, there's that.
David Clutterbuck: Well, I did see a report last week that over that 50 % plus of what AI produces actually creates more work.
Perry Timms: Yeah. Because
David Clutterbuck: You
Perry Timms: almost now what we're trying to do is convert like twentieth century thinking into modern technology and it's almost like how on earth is that going to work? You really do have to start again because you're right, it will just create almost like work about work that's completely unnecessary and negate all the benefits you're trying to get from it. Yeah.
David Clutterbuck: I'm curious in this context, about the the whole issue of purpose.
Perry Timms: Yeah.
David Clutterbuck: But when you organize, should presumably organizing around a purpose. But it would seem that when you get down into the nitty gritty of an organisation, purpose gets diluted and purpose within within functions of teams gets inward focusing. rather than focusing on what the hell is the organisation here for?
Perry Timms: So true. I don't know how many times I've done this in teams, going, what are you here for? And they'll give you the corporate list of priorities, including profit, if they're in. I'm like, no, no, no, profit is an outcome. That's not what what that's not why you exist. You exist to do so I did some work with a a famous newspaper I won't name, and I got I got that question on the table and they said, Well, we've got to be a profitable thing because I'm like, that is an
outcome, but why do you exist? And then they talked about pioneering journalist standards, investigative journalism for the better for the world. I'm like, that's why you exist. You just happen to need to make money in order to do that. So, David, you're so right. Purpose gets diluted, squashed, and completely morphed. Almost sadly, the nearer it gets to the people who perhaps were drawn to it in the first place to want to do the work there. Why have we done that? There's so many layers. The purpose that that that it started with just becomes corporate ease in language. And then people think that's the purpose. I'm like, no, that's your operational sense. That's not why you exist. So again, it comes back to being and and the being thing is, why do I exist? But also why does this thing I'm connected to to do stuff and I get paid in? Why does that exist? That question needs to be a lot more fluid and responsive and straight at people.
David Clutterbuck: It's certainly, it's an area that I'd love to research. We've done it informally. We've asked HR, what do you think finance is there for and finance, what do you think HR is there for? And of course there's no agreement whatsoever. They're
Perry Timms: Yeah.
David Clutterbuck: completely different. And what's the impact of having this narrow function
Perry Timms: Yeah. Mm.
David Clutterbuck: encompassed view of what we're there for as opposed to the whole
Perry Timms: Yeah. Yeah. Yeah.
David Clutterbuck: systemic view.
Perry Timms: Yeah. I mean, let's take Patagonia as a kind of poster child of purpose led companies. And and really if you if you talk to Yvonne Schwinard, he would just say, look, I wanted to do a a an organisation that had commercial viability, i.e. producing outdoor apparel and so on. However, I wanted to do it in a way that I could symbolise what a business could be like. So really their lead purpose was a business that's good for the world. Who just happens to make sports apparel. But if they're not very good at making sports apparel, guess what? They won't be a very successful company. So they've shown the beautiful combination of a commercial purpose and a higher sense of what you could do for the world. Now, not enough people set that higher one and they just try and almost fake a purpose that's good on top of I want to make a load of money and look good and get a Ferrari or something. Do you know what I mean? So So there's there's something about how how how can we align the two? And the answer is, Well you can. Simple as that, you can.
Riddhika Khoosal: Perry, I'd love to circle back to this concept of spaces that you touched on because
Perry Timms: yeah. Yeah.
Riddhika Khoosal: it's an area that you've spent quite a bit of time developing some thought leadership around. And in I I'll let you explain it rather than me try and do my interpretation of of what you've said, but you know, briefly
Perry Timms: Mm.
Riddhika Khoosal: speaking There has been
Perry Timms: Mm.
Riddhika
Khoosal: a departure from your traditional functions into the world of spaces. And you've also spoken
Perry Timms: Yeah.
Riddhika Khoosal: about pulling away from traditional job descriptions and fixed roles into
Perry Timms: Mm. Yeah.
Riddhika Khoosal: proficiency stacks. So for our listeners that are hearing these terms for the first time, they might be thinking, What
Perry Timms: Yeah.
Riddhika Khoosal: what is she really talking about here? Do you mind Perry helping us walk through this? Because it's it's quite a
Perry Timms: Yeah, yeah. Not at all. I'll happy do that. Hmm.
Riddhika Khoosal: you know. different way of thinking about work.
Perry Timms: Yeah. And and before I get into more of the intricacies of spaces, if if I just tag it to the work I know you and David are doing, looking at almost more open systems for work and and and how complex adaptive systems and agile are more open versions of a sort of fixed hierarchical kind of model. That that gives us almost like the founding principles for what spaces is all about, because a complex adaptive system describes the behaviour that's going on both in people and the system together. Then the agile sense is, well, what can we do with those combining energies of sensing our way through things and being very responsive to the environment? And then I think what polymorphism and spaces in particular does is how do we actually design that? How do we be very deliberate about that? So so what a space is Is a way of saying how how you could re-architect an organisation without completely erasing all of its existing architecture. So for example, let's say you're in pharmaceuticals and you're small and nimble and you're getting going with a particular research line and you're looking at all the big guns who've got tons of resource and lots of reach and reputation, you're thinking, how can I emulate what they do? How do I structure myself like they do? The answer is you don't really. You need to have your rigorous structure in perhaps a division to show you're compliant and hit standards and so on. But then you want you might want to do RD in a very, very different way. You might want to set up a space where people are exploring the latest in protein folding and all the research that's coming through in in various ways. Because you haven't got a drug line that you want to particularly build, but you want to see what's coming through that could spark your interest into it. Now that doesn't sit neatly in a division. Because it's got research, it's got tests, it's got all sorts of things going on. So you create a space a around that venture. And it comes back to what I said about projects. If you want, projects are a little tiny microcosm space within a very big organizational superstructure. We just don't think of it like that. We think it's just got the same boxes, but just slightly adjacent to a a division or a piece of work. I'm saying just be more deliberate and maybe even bigger about that. Because If you want to obsess about customers, guess what? You don't do it if you're splitting the customer journey across these verticals. You go, here's the customer space. If we want to do something brilliant for customers, we have to go there. Because that's where they are, that's where the work is. So you take people from marketing and you take people from analytics and you take people from finance and you say, come together to obsess about what a customer needs, wants, and deserves. And if you get good at that, you can do it for more than just customers and projects. You could do it on the principles of ESG, inclusion, culture. Culture doesn't live anywhere, it lives everywhere. But if you create a space, at least
David Clutterbuck: Yeah.
Perry Timms: you might be able to get the right people to talk about it to get something going on. So that's what I mean. It's like a complementary structure change. It could become your normative state, but the system will tell you whether it will or not. But you'll only know if you start experimenting and probing by by creating alternatives to the verticals and the rigidity that you've built and inherited and and look and looked for for forever. So that's what we mean by spaces, deliberately set to be very specific about value, focus, purpose. And the people who come to it might be the ones with expertise and capability, but also just curiosity and intelligence and and brilliance and and and spark. So yeah, it's a different way to assemble a unit of people. Now that then gives us a chance to question the construct of a job. Because people will well, that's not in my job description to go to that space. I've got to do this. It's like, man, what have we done? We've literally robotized people by a series of prompts that we want them to conform to and don't do anything else. Yet then we moan about lack of engagement and no discretionary effort. It's like, well, you told them that's all you wanted them to do. So I'm suggesting that we could have a job architecture, but people say, This is my stack of capabilities and skills. I'm good at these. How can you use them organisation, not just in a job, but in a project and in a research piece and in this problem solving or whatever? And then here's some things I want to learn and I want to acquire. how do I get them? Because they're not in a conventional career path, but I just want to bolt on all these brilliant things so that I can be more useful and versatile. no organisation really lets that happen. I think it's a real shame because people then go. All I'm going to do is follow this pattern of job and then job promotion up a ladder or if I'm lucky diagonally, I'm thinking, what have we done? We've created such a predictable path that it's taken all the creativity and and pizzazz out of people. When actually what we want now is more of that to come through with AI looking at the algorithmic work. So I'm saying don't replace jobs with some modern trendy version.
Give people the agency to build what they're good at. And find out the best way to use it.
David Clutterbuck: Thank you, Perry. Can I build on this with another analogy? Although, what, pretty six decades ago, Stafford Beer, the brain of the firm, got us thinking about
Perry Timms: yeah. Yeah.
David Clutterbuck: systems in organizations. And
Perry Timms: Mm.
David Clutterbuck: modern neuroscience now tells us that we used to think there was a bit in the brain that was solely devoted to hearing or to interpreting particular types of experience. now we realize that it's that that these little areas exist, but they only function because they've got all these multiple linkages to other bits of the brain. So when something happens, or when a thought happens, it's it may
Perry Timms: Yeah, yeah, yeah.
David Clutterbuck: be started or centered in this point, but it's actually distributed across the organisation. So the analogy there is how do we replicate this brain architecture in
Perry Timms: Mm.
David Clutterbuck: a modern organisation?
Perry Timms: Mm. Mm. Such a good point because so I'm going to drop in Gareth Morgan's metaphors because that applies and you know, I sort of lean towards the organism, but the brain bit is also so important because an organisation is a is a is a thinking organism, isn't it? It by its own nature, it brings together human intelligence and and what the system's kind of putting in the mix and it it kind of combines them to to do what you've just talked about there. so there's definitely something in that. And then I'll go to Henry Minzberg's nine parameters and his lateral linkages and stuff. That's such an underplayed part of org design. We tend to think that it just follows bureaucratic chains. It's like, no, this is about how people kind of bond and bind and trust each other and join forces and and can can either accentuate and accelerate the value they're creating or or almost dumb it down and mute it by having these bureaucratic linkages. So so I love the the metaphor of the brain in that respect because I think that's what we want an organisation to be and have neuroplasticity, I suppose, now, because
David Clutterbuck: Yeah.
Perry Timms: at the minute it's a very formulaic ba way of thinking in organisations. And I think the world's kind of going I'm not sure that's right anymore and and that's where I think we need to create those new neural pathways. Now, you only do that, like you said, when when you understand how the linkages combine to create value. productivity and GDP and all those kind of equations are are are I think far too simplistic for the world that we're in now. So we need some more advanced thinking on the economic side of things. Because I think if we can create a more rich tapestry of inputs that create value, we can then draw that back and say this is how we organize around that form of value. So so I look to economists. Who are trying to change our thinking in this. So people like Mariana Matsuccato, as an example, is really saying, like, the whole thing's stilted towards machine production, and it's not that anymore. So we've got to think about mission and relationships and so on, as you say. So this is where it's so much more than just organizational design and structure. It is ecosystem, economics, push and pull forces. and and it comes back to what Ridica said about sensing. It's like we we we have dumbed down our sensing capability in an organisation that's machine replicable. Now I think the world is saying that era's kind of gone because the machines are literally going to do that for you. So we've got to amplify all these other things. But we've we've not learnt them strongly enough. So we've got to get into that sort of cycle. Learning in work is considered to be almost like, you know, sort of an intellectual vacation. It's like, no, like learning is the work. Like why why do we think it's not work? Just because we're not
David Clutterbuck: Yes.
Perry Timms: producing outputs. So those kind of mindsets, those mentalities have got to change. And I love that brain metaphor 'cause I think that could help people detach from their current mechanistic to more systemic and thinking and organic. And I think that's what we've got to.
David Clutterbuck: So what's the role of HR in all this? mean, poor old HR, they do
Perry Timms: Mm.
David Clutterbuck: get a lot of stick.
Perry Timms: Yeah. Yeah. And I understand why, because let's just say through the various guises of personnel into HR as we know it, and even the strategic business partnering type of thing, guess what? It it's it's been a a human as possible response to the machine is is really what it is. So it's it's replicated some of the machine things with, you know, kind of functional policies that are very instructional and and enforceable. And actually it's taken not very much of the human spirit into work. It's almost tried to nullify that to create replicant humans. It's like that's the easiest way to avoid tribunals and disputes, is that if everybody behaves the same and does exactly what they're told, we're all right. I'm like, yeah, okay, well, welcome to that kind of dystopia. So so it's fallen into that trap. And I understand why. And what it's now starting to realize through people science and and system science. is that actually it it's Mr. Trick and it's way more complex than that. So its role now is changing from administrator and almost like purifier to being something that channels that creative judgment and sparkiness in humans. Because people have slowly become less alive at work because of this. And now they're thinking they're going to be even more less alive in technology coming in. So therefore what they've got to do is is flip completely the other way. And what does human differentiation do? Well you talk to a customer and they'll never say, I love your website menus. They'll say, I love that person who solved that problem for me. So that's the
difference I think we're going to see is that human, relational, creative judgment, you know, empathy, compassion, care, diligence, whatever, that they'll become the things that where cust consumers will choose to buy. Because it isn't a robotic experience, it's an added value thing that comes from human relational skills. So what HR's got to do is recalibrate itself to go, how do I find that? How do I curate that? How do I organise that? How do I sustain that? That's what it's got, it's real calling to do. And it doesn't do it by being an administrative machine, it does it by being a sensing and adaptive system in itself.
David Clutterbuck: So one of the phrases that we that the idea of HR's primary role being there to create the connections enable people to add value.
Perry Timms: Boom. That's it. Exactly that. And and and I think the connections piece is more important going back to your conversation about brain linkages and so on, because what we've done so far is the opposite. We've almost isolated and caged them in their own disciplines, in their own domains. I get people who work in organizations that aren't that big, you have no idea what somebody does, who's about twenty five feet away from them. Like, what do you mean you don't know what they're doing? Well, they work in that and I work in this. I'm like, Yeah, but you're doing the same thing for the customer and the supplier and They just it's almost like how have we created almost like this you know, kind of crated existence for humans, both intellectually and physically. And what you're talking about there is totally the opposite. It becomes an enormously connected brain where the intelligence is shared. And and data and intelligence and knowledge, I think, at the minute in organizations are far too boxed in. They're like a supermarket with lots of different aisles and nobody knows what their weekly shop looks like. We've got to get better at the weekly shop when it comes to intelligence.
David Clutterbuck: Love the analogy. We have this phrase, people only belong in boxes when they're dead.
Perry Timms: Ha, definitely that. Yeah. Yeah.
David Clutterbuck: Ridiculous.
Riddhika Khoosal: In your book, Perry, the HR operating model, you
Perry Timms: Hmm. Yeah.
Riddhika Khoosal: talk about this evolution which you've just touched on from HR moving away from being an administrator and then into a business partner. So you call it 1.0, 2.0, and then there's a 3.0 where
Perry Timms: Mm. Yeah.
Riddhika Khoosal: HR really needs to step into the role of an architect.
Perry Timms: Yeah.
Riddhika Khoosal: And I'd love to get into what you really mean by that, because I feel this is the role that we really need to be able to help evolve. So can you say a little bit more about what does
Perry Timms: Yeah.
Riddhika Khoosal: HR look like when it takes the role of the architect?
Perry Timms: Hmm. I've introduced the phrase lately because it it just seems to capture it in a short, pithy burst, is that up to recently what HR's been really good at is fixing. So it's been less of an architect and it's been more of a handyman, interior designer, whatever. But it hasn't completely fundamentally re-architected the house for what it needs to be in a modern world. So we've got to go from fixer to designer. We've got to say actually, what do you want this dwelling to do? And how do you want the flow of the rooms and the heating and the infrastructure and so on. And that's a very big departure from fixing things to designing things because you are literally going, we we we can continue fixing things if you want, but at some point in time it's just going to be completely null and void and not fit for purpose. So therefore, if we go further left and redesign it, then we're likely to have a future sustainable model. So so it moves from responding to the system that somehow the organisation has evolved into or the top team insist to going th this is how we need to be in order to perform and be innovative and an employer of choice and so on. So I think they're gonna have to get a bit braver in challenging the sort of orthodox structural conformity that most C suite leaders seem to want and come in with some alternatives. But they need it back by by evidence and data. So the the kind of calling in this is to go, don't just expect because it's morally sound or humanly right that a board is going to go, yeah, let's do that then. Cause they're well, what's that mean to the bottom line in efficiency? You've got to have all of those things running in in that sort of argument. But but instead of being waiting to be told by the organisation, you are sensing what the organisation could become. And you're saying, here's how we design for that. And that is systems, that is in the science that you use. It's the processes that underpin it, but it's also the products you lead with, the products that HR builds, that its people consume, that create value. That that we've got to get much better at what we put on the table as a product, not just here's a policy because it's compliant with the law. It's like here's a policy that inspires people to be good corporate citizens and not be nasty to customers or steal from us. It's like move that doll a lot higher and we could find an organisation that actually becomes what it could be. So that's what I mean by architect. We stop fixing things, we stop doing a bit of interior decorating, and we actually go, what is this dwelling for? How do we make the best of it? How is it modern and sustainable? And that means we've got to redesign and or design new.
David Clutterbuck: In a way, I'm just interpreting what you're saying. HR has set its sights too low.
Perry Timms: Yeah. Yeah. And and that's partly because the organisation's almost like said, stay in your lane, don't get ideas above your station. People stuff's complex, keep us out of court, whatever. They've given them a very low baseline to start with. And and it's had little
flirtations with something a bit more adventurous. So when engagement came knocking on the door, it felt like, we've now got this opinion that makes a difference. And now people are saying, All that is is just chasing numbers, because it kind of has become that. So we we we try with good intent and it gets corrupted by the machine and then we back away a bit. But we've always had secret weapons within it, like talent is just the thing that organisations can't get right. And we should be able to help them get it nearer to right as possible. and then O D. O D and systems are things that I see as a real deficiency in the C suite as as a general sort of discipline. because their they're their field of vision is slightly different. what's that profit look like? How do I get in my budget envelope? How do I look good and keep the reputation going? And da da da not what's the real sense of what this system is that I'm part of and that I'm steward in and that I could create here. So we can, I think, earn ourselves the right to get a little bit more influence by getting that systems OD thing so strong it's irresistible. That leaders feel that they are under serviced themselves in that area and we can help them, then I think we we can unlock all sorts of doors. So you're right, we've we've pitched too low.
Riddhika Khoosal: So if if we were to start to raise the bar for HR and say we're in the role of the architect, we're systems thinkers, we're sensors, we
Perry Timms: Yeah. Yeah.
Riddhika Khoosal: are bringing new ideas and thought leadership to the table. We are completely diverting from staying in our lane to creating new lanes that the business didn't even know we need to actually create. Can you build on what else? Like what What else should we be thinking
David Clutterbuck: you
Perry Timms: Yeah.
Riddhika Khoosal: about?
Perry Timms: So to the point we mentioned earlier on, and the fact that it you know we've practiced pitched a bit too low. So, you know, we're we're we're still continually dragged into administration. If if we don't smartly automate the best administration possibilities, we're never going to escape that trap. And we're always going to get dragged down into administrative personnel type work. So we have to seriously say, How can we create bandwidth? So that we don't have to service down anymore in the nicest possible way. We can service up and out and across. Then it requires a big capability shift in HR to go from I'm taking orders from the business to I'm ahead of the business telling it what its needs are and that I can service them. Now that's a big leap, but I've seen it work. I've seen very commercial, very system savvy HR leaders who literally pitch back to their business going. I'm not just doing what you tell me to do, but here's where we need to pay some attention. And if you don't, we're in trouble and I can help you get there. So we've got to get a bit more into that future back type of thinking.
David Clutterbuck: Hmm.
Perry Timms: and I think there's no better moment than now, because I don't think any CEO has any prediction worth any salt in the world. Because it it's just far too unpredictable and volatile. So the best you can do is go, here's where we should be heading for future readiness, even if we can't predict it, and I can help you do that. And and and I don't think there are many others in the corporate world who who could and should own that kind of agenda. So I think that's where we recalibrate our pitch. It's going to ask a lot of people in HR, but it's almost what they've always wished for. So therefore it's like, go fill your boots.
David Clutterbuck: In one way, HR would seem to be the ideal function to give AI all the admin jobs so they can concentrate
Perry Timms: Yep.
David Clutterbuck: on the people.
Perry Timms: Yep. Completely. And and work redesign has to be the frontier that we go, look, we've been telling you for ages, we know what this looks like, and you've insisted we do it in this vertical thing. But now AI is going, I don't care about that. I'm just going to rip it all up. So if HM is smart enough, it can go, I I'll I'll help Steward andor do all the work redesign so that you ops are efficient, finance you're more effective. And therefore then the reputation is, well what comes next then? Because I think that's what we need to see. So I'm seeing AI implementation still a technical discipline and it isn't. It's a work designed systems and behavioural change that's needed. and we're the ones best to do that, not the technologists with the greatest respect, because we'll we'll see where the technologists take behaviours into scrolling and addiction and so on. So so we we need to play our people science card really strongly on that by saying things like people's identity is so attached to their jobs, if you take away some of that, there's a fear and a reticence. So therefore say to them, Your job is changing to this. What do you want it to be? And what would you like it to be? And then people are like, really? I can do some choice, can I? And I can leave that stuff behind. If they don't see that and don't feel that, they won't they won't join that parade and they'll try and sabotage it. I saw a clip online yesterday. Where somebody is deliberately stepping in front of a robo taxi to stop its progress. They're literally jumping in the road to stop it because they obviously don't like the thought of a driverless car. We will get that kind of sabotage in organizations on AI if we don't give people the trust and incentive to move away from it and let that happen. So yet we are the ones to do that.
David Clutterbuck: So if you could sum up your vision of really effective HR systems in the future, what would they look
Perry Timms: Hmm. Hmm.
David Clutterbuck: like?
Perry Timms: So they would be practitioners and people who are very nomadic. They don't have a centre, they are going where the energy calls them to adapt the system, design
things, fix problems, listen to people, engineer stewardship, whatever it might be. So so it'll be unrecognisable. It won't be a department, it'll be a very responsive group of people. Who kind of pop up almost without notice and business leaders will be like, what are you doing here? Am I in trouble? That won't it be you're d what you're doing here, there must be something exciting on the horizon. So that's part of the vision that that we are the the absolute mainstays of polymorphism in that we we just go wherever the energy, the work, and the need is. So I think that's the first part of the vision. The second one is we get so good at creating the stronger connection between what humans do And what value is created by an organisation, that people don't get so obsessed about technology creating value anymore. They're like, but what what else can we do with the human value? How else can we be a better business because of the human value? And nobody's sitting on that one right now. So that's an unclaimed territory. Difficult, I know, but I think we're going to have machinery, ironically, that will help us get better at that computation. So that so there's the fixed things nomadically, there's the Create new lines of value. And ultimately, David, it loops back to what you said about purpose, that we become the meaning makers in organizations. We help people
David Clutterbuck: Yes.
Perry Timms: say, this is the meaning of it all. People go, wow. We don't own that, but we make sure that is such a strong currency in the organisation, that becomes your employer of choice, not just perks and benefits. So that's my vision, nomadic, economic and purposeful.
David Clutterbuck: I think that that phrase becoming the meaning makers in the organisation, probably that's the thing of everything we've said, I think that sort of lands with me so strongly. And
Perry Timms: Good.
David Clutterbuck: you've talked about the architect and I'm making the comparison with the various models of personal maturity. And in some of those models, architect is the person, is the top. It's the one that thinks systemically.
Perry Timms: It is. It is. Mm.
David Clutterbuck: If we want to take HR seriously, then maybe
Perry Timms: Mm.
David Clutterbuck: it's about maturing to that level.
Perry Timms: Yeah, I th I think it's been threatened for a few times, but I don't think the system and work was ready for it, David. So I think we could beat ourselves up and go, we've missed some opportunities. I'm like, I think they were just calling us to to understand when it's right that we're ready to mobilize. I still think we're behind the curve on mobilization, but I see more of it switching almost by the month that I'm kind of thinking, I I've got a bit of hope here. I've got a few clients right now in very different industries. The VP of HR and the CHR role, I can tell, is the chief execs like right hand ear, whisperer, coach, guide, whatever. And I'm thinking that I want to see more of that. So I'm I'm happy to say that's on the way, but I don't think it's been possible until now.
David Clutterbuck: Brilliant. Well on that message of hope. Thank you, Perry. That's
Perry Timms: Mm-hmm.
David Clutterbuck: been fascinating. Radhika, last words?
Perry Timms: Thank you, David.
Riddhika Khoosal: Just thank you. It's been such a stimulating conversation and
Perry Timms: thank you.
Riddhika Khoosal: and for anyone, Perry, who wants to get a little more connected to your thinking and some of these
Perry Timms: Hmm. Yep.
Riddhika Khoosal: ideas, what's the best way for them to connect in with your work?
Perry Timms: Sure. Thank you. So I'm on LinkedIn, so I'm quite easy to find there. the website is pthr.co.uk. That's just about to be relaunched with a with a chat bot on there to help us make sense of all this. and I write on Substack. So pthr.substack.com is where I put all my thinking. a few YouTube clips and so on, but yeah, you can you can find me normally reasonably easy. But I'm gonna have to listen back to this one 'cause I got so lost in the conversation I can't remember what I said and I need to re re watch it. But it's been a joy to to dive into this with you both, so thank
David Clutterbuck: Thank you, Perry.
Riddhika Khoosal: Thanks, Perry.