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 – a retired agility warrior from a major Swiss bank, beyond agile explorer, lean thinker, former rugby player, and wishful golfer. What frustrates me most? Poor agile adoption, illusionary scaling, and the lack of true business agility. I believe agility should fit purpose, context, and practice – and continuously evolve. Active in the agile space since 2008, my consulting journey began in 2012, helping a digital identity unit adopt Scrum at team level. That work led to the design of an Agile Operating System for the entire organization. Today, as an independent consultant, I help organizations unlock sustainable agility – guided by adaptive intelligence: sensing challenges, learning fast, and adapting with purpose.