The AOS adoption pattern

The Agile Operating System  (AOS) life span consists of three moments: learn and adapt; try and adopt; reflect and improve.

At first the organisation in general, and the teams in particular, learn the mechanisms of the AOS and the possible agile frameworks to use through a descriptive rather than a prescriptive approach. The teams try out and decide what agile approach to adopt: use it, understand it, and adapt it to their needs.

Then, as the organisation and its teams get comfortable with the AOS flows, outcomes, and feedback loops, it begins to be agile. Agile/lean values and principles get adopted and internalised as a new way of work emerges.

Later, when the organisation becomes independent and self coaching, the operating system specifics become less important and it creates its own agile/lean ecosystem through continuous improvement.

Unknown's avatar

Author: Mario Aiello

Hi, I’m Mario – retired agility warrior from a major Swiss bank, beyond agile explorer, lean thinker, former rugby player, and wishful golfer. I’ve been in the agile space since 2008. I began consulting in 2012 with a Scrum adoption in a digital identity unit — and that path eventually led me to design an Agile Operating System at organisational scale. What pushed me further was frustration: poor adoption, illusionary scaling, and “agile” that looks busy but doesn’t improve business outcomes. That’s why I developed the Adaptive Fitness System (AFS) — an approach that treats agility as fitness for change: fit for purpose, fit for context, fit for execution, and fit for continuous improvement. Today, I use AFS to help organisations sense what’s real, learn fast, and adapt with intent.