Cockpit
    October 26, 2026 · 4 min

    The opposite of End-2-End-Responsibility is... Waste

    LeanMudaWasteEnd-to-EndTeamsTransformation

    End-2-end responsibility, cross-functional teams—we've heard it all so many times before. But why is it actually so important?

    There are several reasons, and today we'll look at one of them.

    Muda written in Japanese calligraphy

    Muda in Japanese - image created by AI

    Waste

    If a team is only responsible for a small part, or if the team is simply a group of people who each work individually and only within their assigned roles, waste automatically arises.

    You only look at your own small area of responsibility and do a really good job of it. Too good. Which usually means you do too much.

    If everyone is only responsible for a small part, you have lots of handoffs. That is waste too, because I could avoid those by drawing team boundaries differently.

    Handoffs between teams often create waiting time. You can't just do nothing while you wait, so you find something to do and get carried away with the details.

    Before AI, if decisions about what to build were made outside the team, the wish list was likely to be pretty long. So, more waste, because by the time everything had been built, it might have been obsolete. Those already building with AI now reverse this effect. You build faster than anyone can decide what is worth building. There is a strong chance that much of what is built with AI will be discarded again if the team is not cross-functional and does not have end-2-end responsibility.

    When there is too much of everything, you spend a long time searching. Another kind of waste.

    More mistakes occur in a team that is only responsible for part of the whole. You might still remember the tree swing. Lean also defines avoidable mistakes as a form of waste.

    The tree swing comic: how a project looks from the perspective of each stakeholder

    a very old comic - this can end now when you use AI in the right team setup

    Last but not least, when you confine a person to a role, you overlook everything else that person can do. I've experienced this often: people on a team who could have contributed so much more but weren't allowed to because of such a fixation on roles and team boundaries. That is the waste of unused potential.

    Lean Thinking

    One aspect of Lean is eliminating waste. In Japanese, this is called Muda. Originally, seven types were defined; the eighth was added later:

    1. Overproduction: Producing more than needed, or too early. The worst form, because it causes all the other types of waste.
    2. Waiting: Idle time because something is missing.
    3. Transportation: Unnecessary movement of products or materials. Any movement that creates no value is waste.
    4. Overprocessing: Doing more than necessary.
    5. Inventory: Storing more than necessary.
    6. Motion: Unnecessary movement. Searching, walking, reaching for something that isn't where it should be.
    7. Defects: Rework, incorrect results. Anything that isn't right the first time.
    8. Unused potential: The eighth type, added later. Not using employees' knowledge, creativity and ideas. Not part of the original Toyota Production System, but widely recognised today.

    AI and organizational debts

    There are huge differences between organisations. Some implemented end-2-end responsibility decades ago and have continuously developed their organisations ever since. Others have teams made up entirely of engineers, with responsibility for all decisions lying outside the team.

    AI amplifies your organizational setup:

    The right structures let you thrive, the wrong structures produce waste at scale.

    AI can take over many tasks, making it much easier to define team boundaries properly.

    If I put teams together the right way, I avoid waste.

    That is one reason, but there are more.

    Keep reading: