You fixed it. You were sure you fixed it. Then, a few months later, the same problem is back. Late orders. Rising complaints. Staff leaving. Missed targets. You've tried new processes, new people and new tools. Nothing sticks. If that sounds familiar, the issue may not be your fix. It may be where you're looking.
You only see what's inside the line
Every time you tackle a problem, you draw an invisible line around it. In systems thinking, this line is called a boundary. It decides what you pay attention to and what you leave out.
Call something 'a customer service problem', and you'll look at customer service. You'll retrain the team. But if the real cause sits in ordering, stock or delivery, none of that will help.
What's inside the line gets managed. What's outside gets ignored. And the cause is often sitting just outside.
What happens when the line is in the wrong place
Management thinker John Seddon and his team analysed 1,200 calls into a council housing call centre (Evaluating Systems Thinking in Housing, 2008). They found that 80% were 'failure demand'. These were calls caused by something going wrong earlier.
The line had been drawn around the call centre. So that's where the effort went. But the cause sat outside the line, earlier in the service. The phone team couldn't fix those calls. They could only answer them.
Why quick fixes keep failing
A tight boundary feels safe. But it usually fixes the symptom, not the cause. So the symptom fades for a while, then comes back.
The opposite mistake is just as unhelpful. Draw the line too wide and everything becomes the cause. 'It's the economy.' That might be true, but you can't act on it.
The right line sits in between. Wide enough to include the real cause. Narrow enough for you to do something about it.
The line is a choice
Someone chose that line. Often nobody chose it deliberately. It came from the org chart, a job title, or whoever first gave the problem a name. Once it's called 'a customer service problem', the line is drawn.
That choice also shapes whose view counts. Warehouse staff, drivers and customers often see causes that managers never hear about.
How to find the real cause
When a problem keeps returning, ask:
- What's just outside the edge of what we're looking at?
- What happens upstream before this problem shows up?
- Who is affected but hasn't been asked?
- If this team did everything perfectly, would the problem really go away?
Go back to those rising complaints. Widen the line to include ordering, stock and delivery. You might find a stock system selling items you don't have. Customer service was never the cause. It was just where the problem landed.
Move the line again as you learn more. That's progress, not failure.
Investigate before you fix
If you ask an AI tool for help, your question draws the line too. Leave out the context, and you get a narrow fix.
The Undercurrent Method turns ChatGPT, Claude or Gemini into an investigator. It asks questions first, maps how the causes connect, then names the root cause. For recurring complaints, start with the Support Escalations edition.
0 comments