Showing posts with label Organisation design. Show all posts
Showing posts with label Organisation design. Show all posts

Sunday, 10 November 2019

The role of people-centric groups in organisation design



My Different Slant article in HR Magazine is now online.

The article suggests modern organisation design will increasingly involve a mix of traditional functions, horizontal (process, project, product, agile) teams, communities and networks, as well as melds of these.

I've outlined these models in a bit more depth in Linkedin, and you may like to check out those posts there as well:





Alternatively, you'll find even more information in The Social Organization.


Jon Ingham, @joningham, http://linkedin.com/in/joningham 
info@joningham.com, +44 7904 185134

Top 100 HR Tech Influencer - Human Resources Executive
Mover and Shaker - HR magazine

Friday, 18 October 2019

Leading and managing the MOE



This is my fourth and final post on Arthur Yeung and Dave Ulrich’s new book, Reinventing the Organization. I’ve already dealt with Dave’s new organisational logic, the features of a Market Oriented Ecosystem (MOE) and the process for creating a MOE. The rest of the book deals with the consequences of choosing a MOE option.

The HR aspects of the model are dealt with by the book under the governance heading. Personally, I think these aspects provide more than just governance of the structure - many of them are actually a central part of the organisation form. Culture, in particular, is a key aspect of the ecosystem platform.

Arthur and Dave suggest HR activities will need to be tailored to a MOE and I agree. I actually think that we may need to do more tailoring than he or the case studies suggest. Eg Supercell is heavily focused on teams but they still believe “that one exceptional person equals a hundred ordinary people”. Perhaps it depends on what they mean by exceptional, but they certainly would benefit from recruiting people who can fit well within their teams (which many individualistic superstars often struggle to do). I make more suggestions about this in The Social Organization (TSO).

I’d also have liked to read more about the complexities involved in designing a non-MOE / more distributed ecosystem. These include, for example, how to bring partners with different capabilities together to support the overall capabilities of the ecosystem, and how to handle organisations with different cultures. However, in a MOE these difficulties are largely stripped out by the platform.


There are also some good suggestions on leadership, eg I agree that leadership in an ecosystem needs to be much more distributed than in a traditional organisation. But it’s interesting that they single out Lee Kuan Yew as a leader who ensures accountability. And I can see that this type of authoritarian leader might work well in a centralised MOE. Other more distributed ecosystems will need leaders who are much more consultative and democratic than this.

I also think Arthur and Dave begin an interesting point when they suggest that different types of leaders are required by the platform from the cells. Actually, for me, this is about the network and the cells - the platform needs designing and maintaining, but not leading, as opposed to the people and the network between the people which exists on or uses the platform.

And I think in many MOEs and other ecosystems and organisations, we’re going to need even more different types of leaders, including of networks and cells / horizontal teams, and also of communities and as is most commonly the case currently, of individuals working within functions. However, I do disagree that this should have anything to do with age.

I also think that in many cases, it’s going to be the same people working in various combinations of these different roles. So it may be that they are staffed by different people, but it may also be that the same people need to act differently in different capacities, eg when leading horizontal teams as opposed to when they’re leading communities.

Eg one of my recent posts discussed the challenges faced by people moving between project management and project member positions. I think if we’re asking people to shift between team leadership, network leadership, partner leadership and other roles the challenges are going to be much bigger than this.

I may focus on this agenda in my next book…


Also, I sent Dave a copy of the series before posting them, and he sent me this response which you may be interested in too:

"Response to Jon Ingram

Let me begin my response to Jon’s comments with an apology and a thanks.  In our book Reinventing the Organization we wanted to build on and synthesize previous literature on innovating organizations.  We included 12 initiatives to rethink elements of organizations (network, ambidextrous, post hierarchy, holocracy, agile, ameba, team of teams, etc).  Clearly, we did not include all of these studies, and we missed Jon’s “outstanding” (from my foreword) book The Social Organization.  This was my mistake and we should have included a discussion of his work on platforms which is another piece of the broader market oriented ecosystem (MOE) logic we proposed. 

Our goal was not to just do a book on “organization redesign” (or other elements of reinvention) with a focus on platforms and capabilities (2 chapters in book) but to cover the entire organization reinvention logic, including environment, strategy, integrated governance mechanisms, and leadership  (13 chapters).  So, I apologize to Jon for not including his organization design work.  I am sure we missed insights on elements of the reinvented organization as well (as Jon points out).  Again, we see most of the insights Jon points out are elements of the overall organization reinvention logic. I also want to thank Jon for his insights on organization design. 

Jon disagrees with some of our logic, which is fine.  We like to see pivots from one organization logic to another (hierarchy to systems to capability to market oriented ecosystem).  This means that MOE builds on these previous logic, but evolves them.  We did not make this clear and some organizations still operate as hierarchies, systems, or internal capabilities.  But, in an increasingly turbulent environment (chapter 2) and with strategic agility (chapter 3), the MOE organization offers a new logic of organizing. 

There is a good debate about starting organization change from the inside (my book Organization Capability had a subtitle, “competing from the inside out”) to leverage core competencies versus starting from the outside (our book HR from the Outside in) to anticipate and respond to external changes.  In some ways where organization change starts (inside or outside) is less relevant than the 2 are connected. 

Jon dives deep into the role of platforms.  We would agree that the role of platforms in supporting cells is evolving.  Platforms offer support through technology, common enterprise-wide values, shared learning about building capabilities, and creation and distribution of new processes. 

I am/we (arthur and I) are open to debate as this organization reinvention emerges.  One of my concerns with Jon’s comments is that he keeps talking about “Dave” when these ideas are clearly drawn from exceptional work by Arthur Yeung, the first author on this book and originator of most of the ideas.  He has trained many of the leaders of Chinese companies (including Haier) and has been granted first hand access to the ideas he shaped and companies have implemented in our case studies."  


I told Dave there was no need to apologise, and I wasn’t trying to make a thing of  the connections between our books. This blog is a personalised narrative on what I see happening around me, but also on what I’m doing. And therefore a lot of my posts are commenting from a fairly egocentric perspective. Two years after my book, that still often means commenting on, and making links back to that. So I see and have described how the books has advanced thinking from TSO, but I wouldn’t expect Dave to refer to it. (And he's already been very generous in  shout outs at various conferences around the world too.)

And Dave was right about Arthur of course (not saying he was wrong about everything else) and I've tried to give Arthur a stronger billing, at least in the last three posts.


There's also this comment from Dave on his HR Magazine article:

"Jon has done and will continue to do exceptional work. It is a legitimate and great debate to do work from the inside/out or outside/in. My first book Organization Capability (1990) was subtitled, "competing from the inside out" and built on CK Prahalad's idea of leveraging your core competences. More recently, we have focused more outside in (HR Value Proposition; HR From the Outside In). Hopefully, where ever one starts (inside or outside), they create a virtuous cycle (actually spiral) to both win in the marketplace with customers and investors and in he work place with individual competencies and organization capabilities. Jon's note that not all organizations should be MOE's is a very nice addition we should have acknowledged."


My previous posts:


For more information...
  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com

Tuesday, 8 October 2019

Creating a Market Oriented Ecosystem (MOE)



This is my third post on Arthur Yeung and Dave Ulrich’s new book, Reinventing the Organization.

My insights in my last two MOE related posts do create a few issues with Arthur and Dave’s suggested framework or process for designing a Market Oriented Organisation (MOE) which is shown above. (But please note that my posts always criticise rather than endorse, particularly as I use my blog to develop my own thinking, and therefore tend to focus on things I disagree with, or don’t understand, in order to work out what I do believe for myself. So like most of my reviews, this one will read more negatively than it should. Reinventing the Organization a great book, and if you’re interested in new opportunities in organisations reinvention, you should definitely read it.)

I think the first issue arises from studying three digital companies in Silicon Valley and four near equivalents in China (as well as Supercell). There’s a definite opportunity to use network effects to gain a monopolistic advantage in digital technology and the use of digital platforms lie at the heart of these easily scalable exponential organisations. But is that what we really want to recommend? Becoming a monopoly is a sensible commercial objective but it’s not going to provide a wonderful result for the global economy or society as a whole.

A second issue results from extrapolating the above examples to various other sectors and geographies. The extended, non-digital model will still work best for companies with lots of similar operations, eg retail stores like Walgreens. Platforms work best for relatively simple work which can be divided into tasks rather than more complex work which needs to pull people together into organisations. IT is a great example of this of course, which is why digital platforms work best of all.

Network effects also doesn’t work in the quite the same way outside technology. Competitive advantage is not going to automatically follow a MOE strategy, especially if a company’s competitors are also developing as MOEs. Where network effects don’t apply, more boringly traditional competitive advantage comes from choice and differentiation.

Plus there’s not that much room for that many ecosystems to exist. And even if ecosystems become the prevailing economic model, most companies are going to be ecosystem participants rather than orchestrators. There’s going to be a lot of wasted effort if every company now starts to develop their own ecosystem from scratch.

And there is still lots of valid choice:
  • Eg, I still think internal ecosystems can provide a lot of the benefits of their multi-organisation counterparts.
  • Or there are other options for developing more decentralised ecosystems that don’t depend on a platform, or where the orchestrator’s platform is a basis for a distributed ecosystem, but where the orchestrator doesn’t play a role in the ecosystem itself .
  • Or perhaps for becoming a blockchain based digital autonomous organisation (DAO) which if some predictions become true could blow the platform based organisation apart.
  • Or in lots of areas, hierarchical functional organisations can still rule!


For all these reasons, I think an evolved organisation design process needs to enable an organisation to choose the form it should take, rather than starting from the premise that it needs to be a MOE. So, for me, the sequence in any OD framework should read as something like:
  • Environment - all sectors and geographies are different - what is going on that your organisation needs to respond to, and if possible, inform? (“Create the future by anticipating what the market will be”)
  • Strategy and capability - these should both go together still for me. The capabilities need to support the strategy, but ideally needs to inform it too. Eg if you are, or are going to be a MOE, then your existing capabilities will indicate whether you are likely to be most successful as a creative, technology based or efficiency oriented one. This also provides the opportunity for creating value (“Strategy follows people”).
  • These then impact the nature of the potential ecosystem, and of the systems and structure of the ecosystem and your particular organisation.

It’s the selection of the right capabilities and principles, linked to the environment and strategy, which provides basis for choice in organisation design as well as the opportunity for more traditional competitive advantage. And information, customer, innovation and agility are clearly going to be useful capabilities but they may not be the right capabilities for your organisation. (Just as Amazon actually focuses on customer obsession, Tencent on user experience and Google on technology based innovation.)

In addition, these are all capabilities required by the ecosystem rather than capabilities required by the organisations participating in an ecosystem. I’d actually suggest the main capability required by any participant, including the orchestrator, is likely to be cooperation and collaboration. These are partly provided and automated by the platform, but they also always needs to be embedded in the people and their relationships, which is why I focus on social capital in The Social Organization (TSO).

Collaboration and other more human centred capabilities also have an important advantage alongside market orientation or other work based capabilities. Innovation doesn’t just originate through better alignment with external opportunities - it also comes from developing the inherent potential of people working for the business. Together with the two-way links between the environment and the strategy, and the strategy and capability, this also helps the MOE to create value.

For example, another type of ecosystem (perhaps not a market oriented one, and perhaps not even one operating a very technologically based platform) might include communities alongside horizontal teams in order to build relationships and insights and support the people involved.


However, even with these changes I still worry slightly that this MOE creation process looks a bit like strategic planning, whereas Arthur and Dave suggests MOEs need to develop strategic agility instead. I agree, although actually, I think strategic planning can still be performed within organisations, as long as it’s done at a high enough level and with a sufficiently inclusive approach. But I don’t think this will work for a whole ecosystem. Developing this has to be an incremental and emergent approach.

This is about making external connections with other organisations which might become partners later even if you can’t see exactly how. And it’s about preparing your own organisation to be more open to working with others, and more cellular and platform based internally too (through the use of horizontal teams, communities and networks, as in TSO). So designing your organisation and designing potential interfaces with other organisations rather than designing the whole ecosystem. I still think this fits with Arthur and Dave’s suggestion to “see the whole, but get started on only part of the transformation” too. And it works for any organisation, regardless of whether you want to, or are able to become the ecosystem orchestrator or not.



My previous posts:

For more information:
  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com

Monday, 7 October 2019

HR Magazine Different Slant: Modern Organisation Models




It was great being recognised as one of HR Magazine's Movers and Shakers last month (and being included on the cover this month - can you spot me? - and how many other influencers can you name???).

However, it's even more brilliant to have my thoughts on modern, people-centric organisation models included this month too. These summarise some of my insights from chapters 6 and 7 of 'The Social Organization', as well as providing a few slight updates on platform and blockchain based organisations too.

The full magazine is available to view or download here (you'll find my Different Slant article on pages 36-8).

And if you read it (and you should), do let me know what you think.

I'll also be publishing some more thoughts (somewhere between the high level review in the HR Magazine article and the detailed treatment in my book) on Linkedin - do check and follow / connect with me there too.


  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com
 

Wednesday, 25 September 2019

Dave Ulrich: The Market Oriented Ecosystem (MOE)



Yeung and Ulrich - Market Oriented Ecosystem (MOE)

This is my second post reviewing and providing my insights on Arthur Yeung and Dave Ulrich’s new book, Reinventing the Organization.

My last post on this suggested that Dave’s new organisational logic means that we need to think about what happens outside of an organisation before we look at its internal arrangements.

However, for me, my logic from The Social Organization (TSO) still applies, ie we need to understand the capabilities an ecosystem will provide and the principles it uses in doing this in order to identify the most optimal organisational solution for a particular environmental context.

For Dave and Arthur, the key thing about the external environment is that it is uncertain and fast changing - or superdynamic. This means organisations need to be more market oriented, and they suggest the key ecosystem capabilities an ecosystem needs to provide are information, customer, innovation and agility.


Josh Bersin - network of teams


They also suggests some ecosystem principles (which provide a basis for an ecosystem’s common shared values / style) to respond to the new environment:
  • Establish a consistent set of priorities
  • Create the future by anticipating what the market will be
  • Win through a focus on growth
  • Stay a step ahead of the market by anticipating targeted and future customers
  • Effectively use different options to execute a growth pathway: buy, build or borrow
  • Seek and inspire agile employees
  • Use scorecards and data to drive a growth mindset
  • Always reinvent strategy because strategy is never finished.

In this environment, and with these capabilities and principles, they suggests the best organisational solution for any company is a Market Oriented Ecosystem (MOE).

The book reviews seven main case studies of this organisational form - Amazon, Facebook and Google in Silicon Valley and their digital cousins - Alibaba, DiDi, Huawei and Tencent  in China (as well as Supercell in Finland, which is a bit of an outlier, organisationally as well as geographically, as explained below).

The MOE is first of all, an ecosystem (generally defined to mean a network which extends beyond an individual firm). Given the logic reviewed above, a MOE is deliberately designed to involve external allies - partners providing staff, skills, structures and systems and stakes in the ecosystem.


Niels Pflaeging - value creation structure


But the MOE resembles an ecosystem within the orchestrating organisation too, with autonomous teams (cells) working alongside each other through a network rather than as a result of hierarchical coordination. Amazon’s single threaded teams is a great example. And I think this logic works - if an organisation is cellular internally, it also makes it easy to work with cells which are outside. It also provides the customer focus required by the MOE (see TSO on horizontal teams).

The other distinguishing feature of the MOE is that this uses a digital platform to support the operating network. As I noted in TSO, it’s quite hard to scale a network without a common platform, so this makes good sense too. It also provides most of the required information and agility, and together with the cells, innovation. The use of a platform makes the MOE a highly centralised ecosystem though. (Work is done autonomously within the cells, but the leadership of the ecosystem is centralised under the platform owning part of the MOE.)

Note, however, that I don’t think Dave and Arthur are referring to what I would call a platform based organisation where a digital platform enables autonomous groups to work together without hierarchical management or other forms of co-ordination. (I think the best example of a platform based organisation is Haier who also presented at the Drucker Forum last year. If you’ve not seen it, then Gary Hamel has provided a great case study of this company / platform / ecosystem in HBR recently. I particularly like this example because Haier’s platform treats internal and external micro enterprises in just about the same way, so it’s much more similar to a biological ecosystem than a MOE.)


Dave Gray - podular organisation
Instead of this, MOEs just use platforms to support the network (rather than the network being constructed on the platform). For example, Facebook’s internal use of Workplace is included as an example. Workplace as a product is a digital platform as it provides apps through the system, and it’s also an organisational platform as it enables cell based and multi-company networking, but it’s not a platform based organisation platform (!).

My favourite case study is Tencent as I think this makes Dave and Arthur’s ideas about platforms very clear. “Tencent shares its expertise and resources in technology, legal affairs, government affairs, and talent and organisation management with its strategic partners. For instance, Tencent offers technological and service infrastucture through Tencent Cloud…” In addition, Arthur's in-house consulting team “offers consulting, training, and coaching support to help key strategic partners upgrade their leadership, key talent, and organisational capabilities”.

Therefore, although the platform fits mainly within the structure element of an organisational systems model, there can also be an aspect which is more about the style that people work in, within and across their organisations, too.

Of course, none of this that new. That's not a criticism of the idea or the book, in fact it reinforces the suggestion that this is happening, and it is important.

Michael Arena - adaptive space


However, if you've not come across some of these examples of platform enabled organisation, then firstly, it already exists in Dave and Arthur’s case study organisations, even if this is largely limited to two main geographies.

But it’s also not that new in terms of the ideas being articulated as an organisation form. Eg the book's platform enabled organisations are similar to the following models which I have illustrated throughout this post:
  • Josh Bersin's network of teams (though this doesn't demand a platform)
  • Niels Pflaeging's value creation structure (with the informal network formalised through the platform)
  • Dave Gray's podular organisation (with a more formalised version of the technological part of his backbone making up for a less significant cultural aspect) 
  • Michael Arena's entrepreneurial teams and communities (once again, with the adaptive space network formalised through the platform)
  • McKinsey's agile organisation
  • BCG's dynamic platform structure
  • My own melded network organisation, from TSO.

In TSO, I focus internally within organisations so I only touch on external ecosystems. (I also don’t put much focus on internal platforms as I wanted to write about organisational management rather than the use of market mechanisms. In fact, for me, this is the best thing about Dave’s book - it’s packed full of case study evidence about platform enabled organisations and closely linked organisation forms.)

McKinsey - agile organisation


I agree, and do state, that internal and external are becoming more blurred. But for me, the best thing for most organisations to do is sort out their internal organisation - before they grapple with the additional complexity outside. These organisations can still create internal networks of teams, and use internal platforms.
 

In fact, although Dave’s organisational logic suggests we need to look externally, beyond a single organisation, before we look internally, most of the book’s examples focus on their internal networks of teams, not the way their ecosystem involve allies from outside the organisation.

In particular, the book’s other main case study, Supercell in Helsinki, is a great example of a network of teams approach. However, this company doesn’t really do much externally. Yes, it has partners with shared resources, as most organisations do these days, but I don’t see any evidence of an external ecosystem. And the company’s website provides interesting points about its team focus but says nothing to suggest it followed Dave’s new organisational logic in developing this.

Dave also suggests Amazon first created its capabilities within the organisation and only later magnified this throughout its ecosystem.



BCG - dynamic platform structure


Dave’s case studies also demonstrate that the model is fairly flexible in the way it is applied and suggests that it can be extended to other, non digital sectors, including retail, manufacturing, healthcare, finance, consulting and other professional services. For example, Walgreens / WBA’s stores and organisational management systems are seen as MOE cells and platform too. Now I’ve worked with Boots here, which is a great company, but not what I would understand as an ecosystem or even less so, a platform enabled organisation. But then if the model is going to potentially extend to any organisation I think you do need to interpret it quite loosely.

My insights from this are:
  • I do think it will be useful to look externally at potential parters and the opportunities for creating an ecosystem before focusing on internal organisation design (see TSO for how to do this internal piece). I’m fully persuaded of this evolution in organisational thinking.
  • This won’t always result in creating a MOE or even an external ecosystem and that is fine.
  • Regardless of this, creating an internal network of teams is an increasingly good idea. It provides many of the benefits of an MOE with less bother, and provides a great basis to extend externally later on as well (and one again, see TSO for how to create this internal network of teams, or other melded network options).

Jon Ingham - melded network organisation



More on creating a MOE in my next post.

(This is the last one: http://strategic-hcm.blogspot.com/2019/09/dave-ulrich-reinventing-organization-MOE.html.) 

  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com

Monday, 23 September 2019

Dave Ulrich: Reinventing the Organization



I continue to be impressed by Dave Ulrich's ability to articulate the future of HR, leadership and organisation. Since my current focus is on organisational management, that applies in particular to Dave's recent focus on organisations, with the suggestion that organisation has four times the value of talent (in Victory through Organization). So I really appreciate Dave writing the Foreword to The Social Organization (TSO) too.

And now, writing with Arthur Yeung, Dave has once again moved his thinking on a significant notch. Reinventing the Organization deals with the formation of the Market Oriented Ecosystem (MOE) which I referred to when posting on Dave's and other sessions at the Drucker Forum in Vienna last year.

In many ways I see the book as a follow-on from mine. TSO dealt with the opportunity for melding networks, including the use of platforms, internally. MOE is a build on that, extending the ideas internally and developing them externally too. But I still believe that in the majority of cases, the first useful step to create a MOE might be to develop something more like the melded network from TSO. That then provides a great basis to develop this approach outside of the firm too (see more on this later).

Regardless of where you start, Dave’s book is by far the best book you can read to understand the development of platform based ecosystems, particularly over the last five or so years. It's a deep book, and quite hard going (for me, that's not a negative) so although I've been through the book twice, I need to spend quite a bit longer on it too. Therefore, my notes here summarise my early, rather than fully formed, thoughts.

However, I think I have now got my head around why Dave suggests the book provides an evolution in organisational thinking - a reinvention of the organisation rather than just incremental experimentation. Dave explains this as “reinvention means more than just changing people’s reporting relationships, building teams or announcing a new strategy. You must build a fundamentally new organisation, redefining how your organisation works. Besides understanding and shaping your work setting, you need to change how you coordinate the work, the principles that govern it, and your own and others’ leadership actions.”

If I'm correct, then Dave’s organisational reinvention isn’t about the MOE itself, but the way we see organisations which Dave suggests has progressed from a focus on structure (leading to a focus on hierarchy / bureaucracy) to one on more holistic organisations (the systems view of McKinsey’s 7S or Jay Galbraith’s Star model), and mainly through Dave’s own insights, onto the outcomes or capabilities which an organisation provides. I think TSO develops these ideas further too, describing how organisational forms and other options can be selected to provide the capabilities and organisation principles which are required. That logic applies to the selection of a MOE just as it does a functional, team based or other organisational form. So despite the following diagramme, I don’t think the MOE itself is the radically new idea.


The new idea - and I suppose it’s not that new, but as a result of this book, it’s now more strongly articulated, is that we should always think about an organisation’s ecosystem and not just an individual organisation. Eg I liked the suggestion that MOEs focus on stakeholders more than processes.

So actually, the new logic, I think, is to be clear about the external environment and the required capabilities, and then to develop the ecosystem, systems and structures to support them. I think that this is at least a partial reinvention of organisation design. So I’d adapt the diagramme like this:


By the way, the mini-slide I’ve chosen to illustrate capability on the top left in the above diagramme is the one from TSO showing how the different elements of an organisation from the systems perspective can link with the different aspects of capability, ie human, organisation and social capital. I still think that works for an ecosystem too, although the social capital needs to be extended to what I normally call relationships capital, which is the value of the connections and relationships outside of the single organisation.
 
You could argue, and maybe this is what Dave is doing, that the traditional ways of seeing systems and structures needs to be replaced by the key features of the MOE, which I explain in a later post. However, I don’t think that’s so. MOEs still have the 7S’s structures, systems, shared values, style, staff and skills, or the Star model’s people, rewards, processes and structure (see the ecosystem model from IRC4HR below), or whatever other set of elements you pick (eg in TSO I present the Organisation Prioritisation Model which focuses on work, infrastructure, people and connections as well as a largish number of organisation and HR enablers, which might not be a reinvention but is, I think, a bit more suited to today’s organisations, and ecosystems too).




Assuming that a reinvented organisation has got to have a particular feature takes us back to the first step in Dave’s evolution diagramme when we assumed all organisations had to have a hierarchical, functional structure, just with a more modern equivalent replacing this. I don’t see that as helpful and certainly don’t believe it would contribute to more evolved thinking. Much better to start with a set of core elements and then build up from there.

It’s still helpful to have an archetype. Dave’s three legged stool for HR is a good example of this, but that’s different to saying all HR organisations need to have three legs. Or that all organisations need to have a platform.

Dave actually suggests there are three archetypal MOEs but I’m just going to review their basic features - see my next MOE related post over the next few days for more on this.

  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com

Monday, 1 July 2019

How to redesign your organisation for people-centricity




This is the third of my articles on Making HR truly strategic on HR Zone: 
Employee experience and journey mapping are great, but can feel a bit like putting shiny engagement lipstick on a clunky organisational pig!


This was my first article in the series: People centricity vs business support

  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com

Tuesday, 11 June 2019

Overall Reflections on Creating Inspirational Business from WOBI




I really enjoyed WOBI (World of Business Ideas) last week, and it's definitely had me thinking. I don't think I've changed my mind on anything, but I've connected a few things together a bit differently.

So what were my main insights? Firstly, that there wasn't a lot of focus around the conference's non-social media tagline, Exponential. I might go for something like Inspirational. I'm not saying it was, though I wouldn't say it wasn't, but I'm not one of those who look for inspiration from speakers, I look for insight. But there was a lot of focus on running business in a way that will inspire employees (Hamel, David, Sinek and SMR Covey) customers (Lindstrom) and society (Porter).

So how do you create an inspirational business and / or organisation? Well, I think in a number of ways Hamel got very close. I do think becoming more human is the key. I just don't agree that eliminating bureaucracy, especially managers and management layers, is the main way to achieve this. Managers do add costs and layers do make businesses inefficient, but they're not the biggest thing to point at. Using Porter's ideas they're part of operational effectiveness or execution, they don't impact strategy. Using my terminology, they're value for money, not adding or creating value.

Layers are becoming more important with an increasing focus on being more human, and on employee experience, etc. And I accept that if you were to design an organisation just to develop a compelling experience, you probably wouldn't invent hierarchy to do it. But hierarchy doesn't really get in the way of experience that much. I don't agree with Hamel that being 8 layers down in an organisation feels like being buried under the other 7. I accept that organisational life is often awful and we do need to be more ambitious the way we sort that. But do we really need to start with layers to do that. In my view, not so much. For one thing, hierarchy provides some really useful benefits that it's still difficult to provide as easily through other means. Eg I thought Porter made a very good case for a hierarchical aspect to strategy in our interview.

I'm absolutely not saying that we don't need to redesign our organisations. As Hamel says, our business models have changed but our organisation models haven't done so to anything like the same extent. They now need to do so. That's why I think the opportunity of applying Porter's thinking about business strategy to our organisations is so important.

I loved the way he described this in our interview: "Competition is about what you actually do in the marketplace to achieve value for the customer. Then you back up and that’s where the resources are. There is a cause and effect. We can keep on going further and further back up, keep going upstream to look at cause and causes. Supporting every piece of the value chain there’s another value chain like activity which are the steps you take to get there. And as get more about insight about management we have more insight into what some of those things are. What’s helpful is that we’re getting up the causal chain. Business strategy is about what you do in the marketplace but how you get to doing that is a fascinating question. That’s why I’m interested in the dynamic view of strategy."

We need to start thinking about creating unique and differentiated organisational strategies by developing best fit activities in the organisation value chain. These activities then need to provide the right outcomes which will add and create value for the business. Porter seemed to agree with this perspective too, saying: "if they’re good resources they can be an advantage, part of doing it better."
 
But as well as what our organisation needs to provide, we also need to think about how it is going to do this. So Hamel is absolutely right in suggesting that we need to set clear organisation principles. These provide an additional driver for our organisation design.

And because employees are now more important we need to include their expectations as the third main driver, so that we don't just end up trying to make horrible organisations less awful for people through things like journey mapping (putting experience lipstick on a nasty pig). Or, and this may be the one change I have come away with, we introduce more of a shared value perspective by focusing on societal expectations here.

If these three objectives indicate that we need to reduce hierarchy then so be it, but in my experience that's not the main result most of the time. What I think is a more common result is that we align our organisational groups with the business that needs to get done, including through the use of horizontal teams, networks and, as Hamel mentioned, communities. Doing this ensures that people can get their work done easily and provides a much better basis for their engagement than worrying about bureaucracy.

I think the above steps need to take place before we do anything else, but they're not the most important thing. Hierarchical thinking is a bigger problem than hierarchical structure. And sorting this is about developing David's emotional agility, Sinek's infinite game or Covey's trust and inspiration. Which could of course be principles for  the organisation design. Or simply deeply embedded leadership behaviours getting people to act differently and to provide time and attention for themselves and each other. My worry is that this is difficult to achieve unless you've got the right organisation in place first, so again, I think redesigning the organisation is the most urgent thing. But then you can move on to the most important (I admit I was inspired by SMR Covey's father) and ensure people are acting in a human way in the newly human organisation. (In The Social Organization I call this these the organisational society and architecture).


  • Consulting   Research  Speaking  Training  Writing 
  • Strategy  - Talent - Engagement  - Change and OD   
  • Contact me to create more value for your business  
  • jon [dot] ingham [at] strategic [dash] hcm [dot] com