It relates to LeSS in a surprisingly strong way: the video is funny because both people are stuck in a pattern. One person wants empathy and understanding, the other jumps straight to the obvious fix.
In LeSS, this often shows up when organisations see the visible nail and rush to solve it.
The nail might be:
“Teams are not predictable enough.”
So management adds more planning, reporting, or coordination.
“Dependencies are slowing us down.”
So they add dependency managers, architecture boards, or more alignment meetings.
“Teams are not taking ownership.”
So they create ownership KPIs or accountability dashboards.
But LeSS asks: what is the deeper system condition creating this behaviour? The visible problem is rarely the real problem. The “nail” might be component teams, single-specialist bottlenecks, separate discovery and delivery, project funding, individual performance incentives, or managers making decisions that teams should learn to make themselves.
So the LeSS connection is:
Do not only fix the symptom. First understand the system.
At the same time, LeSS is not saying “never remove the nail.” Sometimes there really is an obvious structural impediment. But if you remove it without understanding the emotional, political, and organisational context, people may experience the change as something done to them rather than something learned with them.
