Great question—because systems thinking isn’t just something we do in workshops, it’s a way of looking at everyday situations through a wider lens.

Instead of asking, “What’s wrong?”, we start asking “What might be connected?”

 Look beyond the event

When an issue happens (a delay, a bottleneck, a complaint), pause and think before reacting. Ask yourself some questions:

• What else might be contributing to this?
• Who might be impacted in ways that are not immediately visible?
• If we don’t address it, how might it influence other parts of the system over time?

Curiosity helps us step away from quick fixes and start noticing relationships, patterns, and unintended ripple effects.

 Shift from fixing to discovering

In team discussions, try exploring the issue, not just the incident. You could ask:

• How often do we see this?
• Where else might this be showing up?
• When does it seem to intensify or quiet down? Is it during certain seasons, transitions, or workload peaks?

When we look across time and place, we begin to notice patterns, not just problems.

 Use everyday language—not frameworks

You don’t need to introduce formal models to look through a systems lens. You can use everyday language that gently broadens perspective:

• How could we see this more fully?
• What might be underneath what we are seeing?
• What assumptions might we be making without realizing it?

 When these kinds of questions show up in everyday conversations, huddles, and planning, systems thinking becomes less of a workshop technique and more of a natural habit. Teams move from reacting to incidents to understanding what’s shaping them. Instead of asking “Who caused this?”, they begin asking “What is causing this?”. That’s when we stop chasing symptoms and start strengthening the system, which is when systems thinking goes from a concept to a team in action.