Many organisations introduce the matrix to be flexible, responsive and adaptive, but can a matrix be agile? Being both more coordinated and more flexible at the same time is tough.<\/p>\n
Being successful at this depends on being clear about why you have a matrix. If you announce that it is all about synergies, cost savings and centralisation then don’t be surprised if that’s what you end up achieving. Also don’t be surprised if after a few years your people say, \u201cyou know we are not as flexible as we used to be\u201d.<\/p>\n
Similarly, some organizations have pursued an agile transformation with a single-minded focus on autonomous teams, enabling them to make their own decisions and to operate without \u201cinterference\u201d from the rest of the business. Unsurprisingly, these organisations start to notice that they are less connected horizontally, that there is more duplication of effort and that people are now working in silos. That is not surprising because it is effectively what you asked for.<\/p>\n
Agile pioneers like Spotify recognise that autonomous teams can only thrive when they are connected as part of a dynamic matrix made up of chapters, guilds etc. to provide the horizontal connectedness within the organisation.<\/p>\n
I have talked to two CEOs recently who really get it. They very clearly articulated this duality \u201con the one hand I want people to be more connected and to find the synergies in the business. On the other hand, I want my local operations to have autonomy and be able to be flexible to local customer needs\u201d.<\/p>\n
Because of this clear statement of what they are trying to achieve, the nature of their matrixes already encapsulates the need to balance these competing pressures – and that is the whole point of the matrix.<\/p>\n
The reason we have multiple reporting lines is to encompass these competing demands and priorities and to change focus when priorities change. If we could decide for example that the business unit always has priority over the function, then we would not really need a matrix.<\/p>\n
The fact that the matrix is too centralised is not the fault of the matrix. It is usually because of a deliberate decision to implement it to deliver centralisation. This is often accompanied by common global systems implementation and developments in functional excellence. When these things lead to more centralization, the matrix gets the blame.<\/p>\n
As always in strategy and structure, be careful what you wish for. Every choice brings a benefit and extracts a cost. If you set out to achieve centralization don’t be surprised if you pay the price of reduced flexibility, and vice versa<\/p>\n
If we want our matrix to be flexible, we have to have a dynamic balance of power between the different elements of the matrix and an explicit process for deciding how to change this balance over time.<\/p>\n
This starts with a clear articulation of what you are trying to achieve – structure and way of working should always follow strategy.<\/p>\n
It continues with developing the skills, behaviours and way of working that bring agility (you don’t become more agile by adding more reporting lines) it is this “soft wiring” of the matrix that brings true agility. See more in our comprehensive guide to matrix management<\/a> or our book Making the Matrix Work – the agile reset<\/a>.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Many organisations introduce the matrix to be flexible, responsive and adaptive, but can a matrix be agile? Being both more […]<\/p>\n","protected":false},"author":24,"featured_media":25719,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-28268","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","type-blog","training-matrix-management"],"acf":[],"yoast_head":"\n