See a system in 5 minutes
Pick one problem that keeps coming back. Then ask five questions.
By Denys Kostin · Updated
- Name the repeat. What keeps happening? Write one sentence.
- Find the loop. What happens just before it, and what does it cause next? See feedback loops.
- Find the reward. Who benefits when it repeats? What gets praised or punished?
- Find the lever. What is the smallest change near the loop? See leverage points.
- Change one thing and watch. Give it two weeks before judging.
Go deeper: How to Read a System, What Is Systems Thinking and the full Start Here guide.
Example: the late report
A weekly report arrives late every Friday. The repeat is the lateness. The loop: the report is late, so reviewers rush, so errors slip through, so the author rewrites on Monday and starts the next report behind. The reward: people who fix errors fast get praised, so nobody changes the start time. The lever: move the data cutoff one day earlier. Change that one thing and watch two Fridays.
Run it with your team in 30 minutes
- 5 minutes: agree on one repeating problem. Write it as a sentence, not a name.
- 10 minutes: each person draws what happens before and after it on a sticky note. Cluster the notes.
- 10 minutes: circle the loop and ask who benefits at each step.
- 5 minutes: pick one small lever and one person to test it for two weeks.
Common mistakes
- Starting too big. "Our culture" is not a problem you can see. "Handoffs from design to dev arrive late" is.
- Hunting for a culprit. The moment a name enters the map, people stop describing and start defending.
- Mapping everything. A map of the whole company is unreadable. Map one loop.
- Changing five things at once. You will not know what worked.
- Judging too soon. Many levers take weeks to show up.
What good looks like
After one round you should be able to say, in two sentences, why the problem repeats and what you will change. If you cannot, the problem was too broad. Narrow it and run the method again. Each round is faster than the last, and after a few you will start seeing loops in meetings, handoffs and budgets without drawing anything.
Common questions
Do I need to know systems thinking first?
No. The five steps use plain questions about one repeating problem. Theory can come later.
What problem should I pick?
Pick one that has come back at least twice, such as late handoffs or repeated rework.
What if I find no loop?
Widen the view. Add the people and rules around it and ask what each one rewards.