In LeSS adoptions, people often work hard on improvement. Teams inspect and adapt. Scrum Masters facilitate retrospectives. Product Owners reorder the Product Backlog. Managers try to remove obstacles. Coaches introduce new practices.

And still, the same organisational patterns return.

When this happens, the problem is rarely a lack of effort. More often, people are trapped in patterns created by the system they work in. That is why systems thinking matters.

Systems thinking is a social activity

Systems thinking is sometimes presented as if it were mainly about drawing diagrams: circles, arrows, variables, feedback loops, and causal relationships.

Those drawings can be useful. But the drawing is not the point.

A model is a conversational object. It gives people something to point at, challenge, correct, rename, remove, and improve. It is not a picture of reality, but a temporary aid for reasoning together about recurring behaviour.

You cannot outsource the modelling

A useful systems model cannot be produced for an organisation from the outside. Not by a consultant. Not by a coach. Not by a manager. Not by an AI tool.

The system is experienced differently by different people.

None of these views is complete. Each may contain something important. Systems modelling becomes useful when these different perspectives are brought into the same conversation.

Where Sisko fits

Wolfgang Steffens created Sisko, a Systems Thinking AI agent, to help people get started when they struggle to identify variables and feedback loops in their own systems.

Sisko is not a replacement for modelling with people. It cannot know the lived reality, local history, informal workarounds, conflicting incentives, power dynamics, or emotional load inside your organisation.

The important step is step three. The output from Sisko is not the model. It is input for a modelling conversation.

The model emerges in the room

Imagine someone enters this prompt into Sisko:

“Our retrospectives identify improvement actions, but nothing really changes.”

Sisko may suggest variables such as:

These suggestions are starting material. The actual modelling starts when the people involved ask each other:

The drawing may be messy. It may change many times. It may never become a polished diagram. That is fine. The value is that people start to see more of the system together.

Why this matters for LeSS

LeSS is not primarily about adding agile practices on top of the existing organisation. It is about simplifying and redesigning the organisation around customer value, learning, and adaptiveness.

That requires seeing beyond individual teams. If the wider system still contains component teams, project funding, overloaded Product Owners, separate business and technology groups, delayed integration, or incentives for local optimisation, then team-level improvement will hit a ceiling.

These are not people problems. They are system conditions. And system conditions are difficult to understand from one perspective.

A better way to use Sisko

Use Sisko before a group conversation, not instead of one.

1. Start with a recurring problem.

   For example: “Our teams are constantly interrupted by urgent stakeholder requests.”

2. Ask Sisko for possible variables and loops.

   Treat the output as prompts, not conclusions.

3. Bring the people in the system together.

   Include people who experience the situation from different positions.

4. Model through conversation.

   Change the words. Remove what does not fit. Add what is missing. Make disagreement visible.

5. Use the model to choose an experiment.

   The model is useful only if it helps people decide what to try, observe, and learn next.

What “good” looks like

A good session does not necessarily end with a beautiful diagram. It may end with:

That is already valuable.

Systems thinking is not about being clever about the system from a distance. It is about helping people see how they are part of the system and how the system shapes their behaviour.

Sisko can support that work when used as Wolfgang describes: as a way to uncover variables, spot possible feedback loops, generate fresh perspectives, and jumpstart the conversation. But the modelling itself happens between people.

Seeing the system together is the first step toward changing it.