It’s the first week of September, and my calendar looks like a losing game of Tetris. Half-day camp until noon, dance at 1:00, swim team by 4:00, and somewhere in the gaps I’m supposed to be getting actual work done. There just aren’t many camps still running this late in the summer, so I’m stitching together whatever’s left: a morning camp here, an afternoon at home with a tablet and a promise of the pool, a carpool favor I’ll owe back before school starts.

Nobody handed me this plan in June. I built it these last few weeks, day by day, the way you do in the dog days of summer, when everyone’s racing to wrap up everything fun before the bell rings and the schedule resets. Monday’s plan died by Wednesday because dance moved a class. Wednesday’s plan died by Friday because the camp only ran three days that week. August isn’t a schedule. It’s a series of decisions made just in time, using whatever information I had at the moment I had to make them.

That’s not a coincidence. That’s the job I do at Kosmos, five days a week, minus the sunscreen.

An escalation doesn’t arrive with two weeks’ notice either. A customer calls, something is broken, and I’m assembling the plan in real time: who on engineering touched this last, which account team needs to hear about it first, what I can honestly tell the customer in the next ten minutes. Nobody scheduled the war room in June. It shows up on a Tuesday and I build the response on the fly, the same way I built Thursday’s pickup plan.

All August, the contingency lived in my head. Which days the half-day camp actually ran this week. Whether dance and swim team overlapped on Tuesday or Thursday. Which neighbor owed me a pickup and which one I still owed. None of it was written down in one place. It was scattered across texts, sticky notes, and memory, and every single week I had to reconstruct it from scratch before I could make a decision.

Escalations run on the same scattered map. The release notes live in one tool. The ticket history lives in another. The account’s past incidents live in a third. Nobody hands the CSA a single view of what changed and who it’s touching. You reconstruct it, call by call, the same way I reconstructed Thursday’s carpool from three different group chats.

Call it structure in the unknown.

That’s the thing both jobs are actually asking for. Not the absence of surprises. Surprises are the whole job, in August and in a support queue. What both jobs need is somewhere to stand while the surprise is happening. A place that already holds what you know, so the only thing left to figure out is what’s new.

Multiply one scrambled week by an entire August and you start to see what it costs to run without that place to stand. Every week I re-derived the same information: which camp was running, whose turn it was for pickup, what was still open between dance and swim. Multiply one war room by every escalation this quarter and the CSA is doing the same thing, re-deriving what changed and who’s affected, again and again, because nothing kept the answer from last time.

Then school starts, and the dog days end, not because the running around stops, but because it finally has a shape. My daughter still gets sick. Permission slips still go missing. Half days still land on the one day I have back-to-back calls. But now there’s a frame around all of it. Drop-off is 7:50. Pickup is 3:15. The bus stop is the same corner every day, instead of a different pool or studio or camp depending on the week. The surprises don’t stop. They just land inside something instead of floating loose.

That’s what we built Kosmos to be for the CSA. Not a promise that escalations stop happening, they won’t, any more than school stops the occasional sick day. What changes is what’s already assembled when the call comes in: the release connected to the ticket spike, the accounts it’s touching, the pattern that matches something from three weeks ago. We call that a correlation cluster, the shared view that used to live only in someone’s head, now sitting in one place before the CSA ever has to reconstruct it from scratch.

Structure doesn’t mean nothing goes wrong. It means you’re not rebuilding the whole map every single time something does.

Teams whose CSAs are still reconstructing that map call by call, the way I reconstructed camp, dance, and swim team schedules all August, are exactly who we built this for.