You don't need a company-wide programme to begin.
Start with one product, educate everyone, and build the capability to keep going.
LeSS adoptions succeed when they start narrow and deep rather than broad and shallow: one product, educated thoroughly, with real feature teams and clear ownership — not a top-down rollout across the whole company. The practitioner steps for that first adoption are set out in the LeSS adoption guide: educate everyone, define the product, define done, structure the teams, and let only the Product Owner give them work.
This page is the view from leadership: how to begin, and how to make sure the capability stays in the organization once the first adoption succeeds.
Each step builds on the last. You can begin step 1 today; LAO matters most once a first adoption is working and you want it to spread.
Two shifts make the org-design question urgent: becoming genuinely product-led, and putting AI to real use. Both change what an organization builds and how fast its market moves, and neither is solved by adding a tool or a role on top of the existing structure. They reward the simpler, more adaptive organization LeSS is designed to produce — and the sooner you build that capability, the sooner you can use the change rather than be caught by it.
