Agile organisations are fundamentally learning organisations at all levels; whether small & specific (e.g. this feature didn’t sell well, so let’s change it) or large & systemic (we need to change our governance model based on this new information). Learning is more than just observing. It’s taking the observations, determining its worth, then internalising & making it the new reality for the organisation.
The application of a Learning Mindset results in continuous improvement. Feedback loops, such as “inspect and adapt”, and practices, such as the retrospective, enable teams, divisions and organisations to improve both what they do and (more importantly) how they do it. Like the woodcutter who refuses to sharpen his axe because he has too many trees to cut down, organisations that do not improve both the way they work and their products themselves will ultimately be out-competed in the market.
Central to the Learning Mindset is the ability to experiment, fail fast (with a small “blast radius”) and recover faster. Failure should not be seen as making a mistake, but rather as an opportunity to learn. Organisations can make is “safe to fail” by recognising that failure is part of daily work and not something you blame or judge people for. From a strategic perspective, you should avoid putting yourself or your organisation in a position where if you don't succeed, your business will fail or someone will die? Unless you’re NASA, the ability to fail strategically and learn prevents catastrophic failure.
Failure, when handled right, can be a brilliant learning experience. It can lead to new ideas & the rapid abandonment of bad ideas. When handled well, failure can save an organisation millions of dollars by avoiding compound failure. Compound failure is the problem. That is, not learning from your mistakes and continuing to invest in them. While there are very few statistics on this, I think it is safe to say that this blindness towards failure, or worse, fear of reporting failure, imposes a significant financial burden on companies.
Some organisations go further by introducing formal or informal support mechanisms like Failure KPI’s, parallel experiments (and selecting the highest performing option) or simply providing an environment where failure is easily identified, recognised and rewarded.
Case Studies[edit source]
Further Reading[edit source]
Books & Book Reviews[edit source]
- Kanban - Successful Evolutionary Change for Your Technology Business
- Kaizen - The Key To Japan's Competitive Success
- Toyota Production System - Beyond Large-Scale Production
- Reinventing Organisations
- Out of the Crisis
- Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy
Supporting Frameworks[edit source]
References[edit | edit source]
Join the Mindset & Culture Community[edit | edit source]
If you'd like to continue the conversation with like minded individuals around Business Agility Culture, join the Business Agility slack community. Specifically the #culture-and-mindset channel.
Library Steward[edit | edit source]
This section is currently un-stewarded. If you have a passion for this space and would like to take ownership for the guidance and insights within, please contact Evan Leybourn. The stewards of the Business Agility Library are leaders in their field and we quite literally couldn't create such amazing content without their support. These people & organisations are leaders in the community and, through their actions and insights, continue to expand the horizon of business agility for us all.