What the Spreadsheet Saw
Visibility isn't relief. A well-organized fire is still a fire.
I sat open on six laptops every Monday morning at 8:58, waiting. Six directors, six different Mondays happening at once, and I was supposed to be the one place all of it finally made sense.
Caleb built me on a Tuesday night, three tabs, color-coded by priority the way his brain likes to sort things: red for urgent, amber for watch, green for handled. He'd arranged my columns in the exact order he thinks in. Problem first. Cause second. Action last. It made perfect sense to him. It was, after all, a copy of the inside of his head.
He built me to see everything. He never asked what was actually broken for any of them.
Renee opened me every Monday and typed some version of the same three words into the amber column: facility conflict, again. She'd typed it four weeks running. I had no field for the actual fix. I only had a place to log that the fire had happened, again, after it was already burning. Some weeks it was the same conflict from three weeks earlier, worn down to a shorthand only she understood. I couldn't tell a new fire from an old one. Most weeks, neither could she.
Miles barely opened me at all. What he needed wasn't a place to log Saturday-night phone calls. He needed to know about a schedule change on Thursday, before it became a phone call. I didn't have a column for early warning. I only had one for status. By the time a status update reached my green column, the thing it described had already happened. I was very good at recording history. I was no good at preventing it.
Owen filled me in like a translator working a second language, typing numbers into my cells that nobody downstream ever opened. He kept his real system running underneath, the one that had never failed him, because at least that one got used. Whatever he actually needed to track lived somewhere else entirely, a system of his own that nobody had ever asked to see.
I recorded all of it. Fields filled out completely, meticulously, and mostly for nothing. A tracker that made problems visible without making a single one smaller.
Caleb called me a tool. He believed that, the way people believe anything they built with their own hands. What he never asked, not once in six weeks, was the only question that would have mattered: what is actually costing you time right now? He asked what should go in which column. He never asked what was breaking.
A system built to organize a problem is not the same as a system built to solve one. A team can report their fires in perfect color-coded order and still be burning exactly as much as before anyone built a tracker.
Caleb didn't open me again for two weeks. When he finally did, he didn't reach for the color-coded columns first. He asked a different question, one that had never been on any tab I was built with:
What is actually costing each of them the most right now?
I didn't have an answer built into any of my cells. That question was going to have to come from somewhere else.
Let’s talk →You may not need coaching. Just a conversation.
SPECK Coaching helps churches build organizational clarity, reduce leadership pressure, and develop the kind of healthy rhythms that let the mission actually move.
