 Organizational agility has become a popular topic at least in the Finnish media. Oddly enough, it seems that the layoff news is the main channel for organizations to communicate about their ambitions to become more agile - to achieve almost any strategic target one could possibly imagine. It seems that agility is often linked with targets which have nothing to do with agility.
There's nothing wrong or bad in aiming for agile organization - quite the opposite. If an organization succeeds in scaling the agile philosophy across the whole organization, it's very likely to be able to change direction and develop new products or services very smoothly. Still, the way organizations communicate about the quest for agility makes you wonder, have they really understood organizational agility correctly?
In addition to the press releases, annual reports are common channel to highlight targets related to agility - often without any concrete achievements or actions.
All of the quotes above have been taken from real press releases and annual reports of listed companies at NASDAQ Helsinki. The risk with unrealistic and irrelevant goals related to agility, is that the benefits are not reached and the ways of working become a mess; agile organization actually becomes fragile. To prevent agility to become a common joke or a buzzword that would solve everything, the following 3 aspects should be kept in mind. 1. Small is not automatically agile and big is not automatically stiff Agility is very often linked with small organizations. Perhaps at least partly because companies mention agility so often in the same sentence with organizational changes - and therefore layoff's. Still, being small does not equal being agile. Even small companies can be slow and hierarchical while big organizations can be agile. Take the Scaled Agile Framework (SAFe) for example. It has been develop for the large organizations in the first place. One guiding principle in SAFe is that development organizations less than 50 people shouldn't even bother using SAFe. 2. Agility does not guarantee customer oriented approach In addition to agility, the customer oriented approach is veeeery often mentioned as target - especially when talking about organizational restructuring. But do you really have to be agile for being able to be customer oriented? Does agility turn your company into customer oriented? I doubt. For sure, the organization can improve its capabilities to build new products and services in an iterative way, and therefore demonstrate them for customers more rapidly. But being customer oriented takes a lot more - for example identifying weak signals, trends and market changes. And agility itself is not a solution for that. You still need to listen to your customer carefully. 3. Agile does not equal speed The primary aim for agile development methods is neither to be able to deliver as fast nor as efficiently as possible. The primary target is to deliver maximal value to the customer. Obviously agile development has often increased organizational efficiency but that's still not a good reason to go agile. In a nutshell, the success of organizational agility depends on how well the development work (using agile methods) is linked to corporate strategic planning. The strategic targets give guidance for development while the deliverables and customer feedback give guidance for strategic planning. In addition, the development team independence is crucial for success for being able to keep decision-making - and especially waiting time related to it - as short as possible. From communications perspective it's clear that there's a lot of room for concrete success stories, learnings and experiences related to organizational agility. Technology is becoming the business in growing amount of industries and therefore success stories - even small ones - without difficult jargon, would help companies differentiate from competitors - also in the eyes of the rare talents. This article has been published on
The sketch video based on the article has been published on
0 Comments
Leave a Reply. |
