Since 2021, I’ve logged my family child care program’s marketing numbers by hand. Reach, views, referrals — every listing, every month, copied into a spreadsheet. Five years of it.

I was diligent about it. I rarely skipped a month. And being diligent never once made it better. The task on month sixty was exactly the task on month one: open the pages, read the numbers, type them in.

This week the same chore takes one click. About fifteen seconds. That’s not a small gain — it’s five years of a monthly ritual collapsed into the time it takes to read this sentence. And here’s what I want to sit with: none of that improvement came from doing the work. It came from stopping to look at it.

The grind hides its own exits

Robotic work has a way of concealing its own alternatives. When you’re heads-down executing the same steps every month, the steps are the reality. You don’t notice that a fifteen-second version exists, because noticing requires stepping outside the loop long enough to ask a question you never ask while you’re inside it: does this have to be done this way at all?

I didn’t find the better way by doing the chore harder or faster. I found it by putting the chore down and sitting with it as something to be examined and planned around, instead of something to be performed. That afternoon of not-producing was the highest-leverage time I’ve spent on this task in five years. It cost me one session of output and bought back every future one.

You can’t improve work you never stop doing. The daily version is load-bearing — the numbers really did need logging — but the daily version is also the exact thing standing between you and the realization that it could be a script’s job, or gone. The grind doesn’t just cost you the hours. It costs you the vantage point from which you’d see how to stop paying them.

Working with the grain

Once I actually stopped and looked, the better way was almost embarrassingly close. The numbers I’d been reading by eye were already sitting in the page’s own code before the page ever drew them on the screen. I didn’t need a robot to click around the site the way I did by hand — that approach fights the platform the whole way, breaking on every layout change and stalling on every spinner. I just needed to read the values where they already sat and hand them to a spreadsheet through a webhook, a private URL that lets one app drop data into another. I’d only learned that last piece at my day job a couple of days earlier. I plugged it straight in.

None of the three parts — the browser script, the webhook, the spreadsheet — were new. The combination was the whole trick, and I only saw the combination because I’d stepped back far enough to see all three at once. I even taught the write side some manners: re-running a month updates that month’s row instead of stacking a duplicate, and it leaves the columns I still fill by hand — tours, ad spend — alone.

There’s more than one way to do a thing, and the way that works with the grain of what’s already in front of you is usually invisible from inside the grind. You have to be standing still to spot it.

What the pause buys back

Here’s the honest caveat, because it’s easy to mistake. Stopping to build the tool didn’t save me the work of understanding my program. It saved me the gathering. Those are different jobs — the gathering was the minutes; the reading was always the point.

The click buys back the minutes. It doesn’t buy back the attention. A share count still has to be looked at and thought about — is it good, is it drifting, does it track what I spent — and that part is mine no matter how fast the sheet fills. If anything, the pause is the discipline I most want to keep, more than the script it produced. The script will be obsolete someday. The habit of periodically stepping out of the daily motion to ask whether the motion still makes sense is the thing that actually compounds.

The quieter waste

I logged those numbers for five years for one reason: I didn’t want the data to go to waste. That instinct scales past me. The point of collecting anything is that someone can eventually use it — to see a situation clearly and decide well. Data that’s gathered and then left behind a wall, held by whoever won’t share what it shows, hasn’t been saved from waste. It’s just been wasted more quietly.

I run into this constantly in child care. The information that would let a community understand its own needs usually exists somewhere — but it’s behind the scenes, scattered across systems that don’t talk to each other, and often months out of date by the time anyone can stitch it together. The capacity to publish it cleanly and keep it current exists too. It just doesn’t happen — sometimes for ordinary reasons like limited time and staff, and sometimes because the numbers, as they actually are, don’t fit the story someone’s already telling.

So people decide anyway, from whatever they can see. Each of us reaches for our own experience and speaks from it, honestly, as if it were the whole picture — not out of bad faith, but because that’s what anyone does in the dark. The trouble is that a room full of people each arguing from their own corner produces a narrow answer, and usually the loudest corner wins. Put the same current, accurate picture in front of all of them and the tunnel vision eases: the conversation turns to what the situation actually is, everyone starts on the same page, and the decision can be more holistic than any single vantage point could make it. Transparency’s real payoff isn’t only fairness — it’s that a community can see more than any one member can, but only when everyone is looking at the same picture.

That’s why the community version of this is built to publish, not just collect — and to stay current, not backdated. The registry my association runs lets providers report their own openings and keep them fresh, then puts the assembled picture where anyone can see it — as aggregates, never a name or a private number. It doesn’t hand you a directory of which program has a seat; it shows you the shape of the thing — how many openings exist across the city, and in which neighborhoods, age groups, and languages, with the trend over time on Community Insights. It launched this past January and spent the quiet months since collecting openings nobody urgently needed yet. This month they matter: San Francisco’s ELFA subsidy expansion arrives in July, more families qualify for help paying for care, and the old question — is there enough room, and where? — gets sharp again. This time the answer is already gathered, already assembled, and already in the open.

The tool itself stays small and mine — my own program’s numbers, for me to act on, and that’s the right home for it. But the instinct underneath it — gather what matters, don’t let it go to waste — points somewhere bigger the moment the data isn’t just yours. If you’re holding something that could help your community see itself more clearly, the pause worth taking is the one where you ask whether it’s doing any good sitting where it sits. Reach out if you want to compare notes. I don’t have a product to sell you — just five years of a habit that taught me gathering is only half of it. The other half is letting everyone see.