Why do organizations keep fixing symptoms?
The people closest to the problem are usually working the hardest. That's the first clue something else is going on.
Started with a finance director who couldn't explain why the number wouldn't move no matter how hard her team pushed.
A large retailer had too much money tied up in invoices more than 90 days overdue — roughly 10 to 16 percent of receivables, month after month. Everyone agreed on the problem: collections wasn't collecting fast enough. So the answer seemed obvious. Call sooner. Escalate faster. Push harder.
The collections team worked incredibly hard.
The percentage barely moved.
That's the detail worth sitting with. If collections were the problem, better collections should have fixed it. It didn't. Which meant the diagnosis — not the effort — was wrong. And everyone was too busy making calls to notice.
The accounts weren't becoming risky after they reached collections. They were becoming risky weeks earlier — quietly, upstream, while every dashboard said things were fine. Collections wasn't creating the outcome. They were inheriting it.
We built a system that surfaced those accounts while there was still time to act. Aging receivables dropped from that 10–16 percent band to a consistent 5–8 percent. The collections team didn't suddenly become twice as talented. They got visibility while there was still something left to change.
Here's the mechanism. A symptom is what the structure produces. You can suppress a symptom with effort — chase harder, work weekends, add a checklist — and it improves for exactly as long as the extra effort lasts. Then the structure, which never changed, produces the symptom again. The organization concludes the team slipped, and adds more pressure.
Fix the symptom and it comes back. Fix the structure and it doesn't.
Where else this shows up
A $4 billion enterprise had billing scattered across five systems, stitched together by two decades of acquisitions. Monthly billing was slow and error-prone, and everyone called it a people problem. The people were fine. They'd been given a structure that fought them every day. Consolidate the billing logic into one source of truth, and the "people problem" disappears without a single personnel change.
A talented kid dominates practice and disappears in games. Everyone calls it confidence, so they treat confidence — pep talks, sports psychology, more reps. The behavior doesn't change, because confidence was the symptom. Information is arriving too late for the kid to act on it. Fix the timing, and the "choking" disappears.
The pattern is the same in both rooms. The visible struggle is downstream. The generator is one layer above where everyone is looking.
The symptom is the problem. Push harder where it shows up.
The symptom is what the structure produces. Fix the structure, and the symptom stops regenerating.
Carry this into your next meeting: the next time a fix works for a while and then stops working, what structure is still standing that produced the problem in the first place?