Event, Pattern, System

A pothole opens up at the end of your street.

Seen one way, this is a small story with a small ending: a hole, a complaint, a crew, a patch. Event noticed, event handled. Most of life is lived at this depth, and honestly, much of it should be. Not everything deserves an investigation.

But in spring the pothole comes back. Same corner, same shape, like it never left.

Something changes the moment you notice the return. Twice is not an event. Twice is a pattern, and a pattern is a message: whatever produced this is still here. Patching a pattern is like bailing a boat without looking for the leak. You can do it forever. The pattern does not care how good the patches are.

So you look closer, and the third depth opens. The corner sits at a low point where water pools. Water seeps under the asphalt, freezes, expands, and lifts the road from below; every freeze is a tiny crowbar. Heavy trucks cut through this street to dodge a light on the avenue, pressing on the weakened spot. The road was due for full resurfacing years ago, but patches come from this year's small budget while resurfacing waits on next year's big one, and next year keeps receding. Nobody wants the pothole. The arrangement produces it anyway.

That is the system: drainage, weather, traffic, and budget, holding hands where you only saw a hole.

Event, pattern, system. Three depths of seeing, and each one changes what the word fix means. Fix the event and you fill a hole. Fix the pattern and you fill it before it opens, every spring, forever. Fix the system and you regrade the drainage, reroute the trucks, fund the resurfacing, and the hole stops being produced at all.

Once you have the three depths, you start noticing which depth everything around you lives at.

News lives at the event depth almost by definition; a pattern is old news and a system is a lecture, so the cameras point at holes. Blame lives at the event depth too. When something goes wrong we ask who did this, which is an event question, instead of what keeps producing people who do this, which is a system question. Blame is satisfying and cheap. Design is unglamorous and works.

Families run on all three depths, mostly unexamined. One rough Monday morning is an event; anyone can have one. The meltdown that happens every Monday is a pattern wearing a calendar. And behind it there is usually structure: the weekend bedtime drift, the backpack never packed the night before, the one bathroom and the four people who need it at 7:40. You can scold the event every week for a decade, or you can spend one Sunday evening redesigning the system and quietly retire the meltdown.

Two warnings keep this tool honest.

First, do not skip depths in a hurry to sound wise. The person who answers every mishap with well, it's systemic has stopped seeing, just at a fancier altitude. Real system-sight is earned by walking down through the depths: this event, this repetition, this structure, named specifically enough that you could point to the pipe, the budget line, the bedtime. If you cannot name the parts, you have a mood, not an analysis.

Second, do not let the system depth dissolve responsibility. The truck driver still chose the shortcut; the council still deferred the resurfacing. Systems shape choices without erasing them. The mature move is to hold both: be brutal to the arrangements, and kind, but honest, with the people inside them.

The practice is small enough to start today. When something goes wrong twice, say it out loud: twice is a pattern. Then ask the pattern question, what keeps producing this, and see how far down the answer goes. Some days the answer is a leaky gutter. Some days it is the shape of your week. The question does not care about size.

This phrase is carved all over the Atlas, on trail markers and gateways, and now you know why. It is the shortest path out of a life spent reacting.

An event asks for your patch.

A pattern asks for your attention.

A system asks for your imagination.