Series · 5 lessons · 5 October 2026
Systems Thinking: Seeing the Whole Problem Before You Touch Any Part of It
A support team I worked near once fixed their queue problem. Average wait time dropped by half within a month, and the dashboard looked exactly the way…
-
Day 1 · 5 min read
The Obvious Fix That Makes Things Worse
A support team I worked near once fixed their queue problem. Average wait time dropped by half within a month, and the dashboard looked exactly the way…
-
Day 2 · 5 min read
Mapping the Whole System Before You Touch Any Part of It
Process maps show steps in order. A system map shows what pushes back when you change one. How BAs can draw one on a single page, and what to leave off it.
-
Day 3 · 5 min read
Feedback Loops: The Pattern Behind Most "Mystery" Problems
Reinforcing loops feed on their own success; balancing loops quietly resist every fix. Why pushing harder fails on both, and how a BA can tell which is which.
-
Day 4 · 5 min read
Second-Order Effects: What Happens After What Happens
First-order thinking asks if a change solves the problem. Second-order thinking asks what people do once they live inside it. A two-minute BA habit.
-
Day 5 · 5 min read
Thinking in Systems as a Daily BA Habit
You don't need a system map for every requirement. You need one honest question before most changes ship. How to make systems thinking a daily BA habit.