The Pool That Made Me Feel Stupid: A Diagnostic Framework for Every Pool Problem That Doesn't Make Sense

I have a master's degree in nuclear engineering. I graduated from one of the most rigorous training programs the United States military has ever produced. I have five professional certifications from the leading professional body in the pool and spa industry. I've been managing pool chemistry for longer than some of my clients have been alive. And a swimming pool made me feel like a complete idiot. Not just once.

Real Chemistry, Real Answers. Every Tuesday. Let's start with something I want to say directly to every pool owner and every service technician listening right now. The WTF moment, that specific, deeply personal experience of staring at a pool that's doing something your chemistry says it absolutely shouldn't be doing is not a sign of incompetence. It's not a sign that you need better products or a different test kit or a serious conversation with yourself about your career choices. It's a sign that you're operating under an assumption that isn't true. And the pool is trying to tell you something you just haven't asked about yet. Every pool owner has been there, every service technician has been there.

The guy running thirty pools a week in the heat, doing what he has to do with the knowledge he has, has been there. I've been there more times than is probably good for my professional reputation, and I'm going to tell you about some of them today anyway. The gap between any of us and the right answer is not intelligence or character. It's access to information. That's all it ever is. Not because I enjoy public humiliation, though I've apparently made my peace with it, but because I think the stories are more useful than the credentials. Credentials tell you what someone knows. Stories tell you how they think when what they know isn't working.

And also, in retrospect, some of these are genuinely funny. At the time they weren't funny at all. But that's what retrospect is for. Let me tell you about a moment that has nothing to do with pools, except that it has everything to do with pools. I'm going to make a standard rate turn here and I promise we'll come back around exactly where we need to be. When I was eighteen years old, I was learning to fly at Columbia Regional Airport in Columbia, Missouri, sitting on the apron with sixty five hundred feet of runway two in front of me. It's one of my very first takeoffs, and my flight instructor told me I was going to need some right rudder on the roll to counteract engine torque and P factor, so I'd stay straight down the stenter line.

I asked him how much rudder I would need. He said just enough. I've carried that answer for my entire adult life. Not because it was frustrating, though it was briefly until I understood it, but because it's the only honest answer anyone has ever given me about managing a dynamic system. There is no fixed number. The conditions change on every takeoff. Density altitude, wind, aircraft loading. The system tells you what it needs. Your job is to develop enough feel for the airplane to hear it. You can't manage a takeoff from a predetermined rudder input any more than you can fly an instrument approach by closing your eyes and following a script.

The instrument panel gives you the data. The airplane gives you the truth. Your job is to read both. Just enough rudder, not more and not less. Just enough. Nuclear training sharpened the instinct. It didn't create it, and that's a different story for a different Tuesday. A pool is the same thing. Here's the assumption that causes most of the WTF moments, including mine. When you take a water sample and test it, your brain does something sneaky. It takes one cup of water from one location at one moment in time, runs a few tests, writes down some numbers, and then quietly, without asking your permission, decides that those numbers represent the entire swimming pool.

20,000 gallons of dynamic, non-homogenous, temperature varying, circulation dependent water extrapolated from a single cup pulled from elbow depth near the skimmer. A cockpit instrument gives you one reading from one sensor at one moment. A pilot who flies solely by instruments without ever looking out the window is missing information the gauges can't capture. Your water test from near the skimmer is the same thing. One instrument, one location, one moment. Useful data, but not the whole picture. Here's why it's never the whole picture. A pool has thermal zones. The south facing wall baking in direct afternoon sun is running meaningfully higher temperature than the shaded north corner. That temperature difference affects the saturation index locally, which affects how the water behaves at that specific surface, which explains things you'll see there that the bulk water test will never capture.

A pool has circulation dead zones. Places the water genuinely never reach with any consistency. Places where the water is essentially sitting still, developing its own independent chemistry, completely disconnected from whatever you're doing at the equipment pad. You can have a pool running perfect chemistry by every test result you take and have a corner that looks like a science experiment because the return jet has never pointed in that direction in its life. A pool has chemical concentration zones. The oils and sunscreen and whatever else your swimmers contribute to the water don't distribute evenly. They ride the surface currents to wherever the pool's circulation pattern consistently deposits them.

Same spot every time. Which is always somehow the spot that makes the least sense until you understand why it's always the spot. So when something doesn't make sense, when the chemistry looks right but the pool doesn't look right, my first move now isn't to add a chemical. My first move is to test more locations. Pull a sample from a problem area, pull one from the middle, pull one near a return and one away from a return. Work elbow depth, not surface. If the numbers agree across all those locations, you have a bulk water problem, and chemistry is probably the right conversation. If they don't agree, that disagreement is the most useful piece of information you have.

The pool is telling you something specific. All you have to do is stop adding chemicals long enough to hear it. Just enough rudder. Not more, not less. Just enough. I promised humility, so here you go. One of my clients, a genuinely patient man who I owe a debt of gratitude to for not firing me, called to let me know that his sun shelf had dirt on it. Every single week. Dirt resting on the shelf, a clean pool everywhere else. Like the sun shelf had specifically opted out of the service agreement. He was starting to wonder whether my technicians were actually vacuuming. He even asked me if they were.

That's the kind of phone call that focuses the mind considerably. So I paid a visit to his pool. I looked at the chemistry, perfectly fine. Looked at the filtration, running beautifully. I looked at the return jet installed directly above the sun shelf, the one positioned specifically to sweep that surface clean. Right there, pointed at the shelf, doing its job. Except it wasn't doing its job. Because I'd assumed it was doing its job without ever checking whether it was actually doing its job. There was a valve on the equipment pad behind the filter. Tucked way back there, not labeled, not obvious, the kind of valve you walk past forty times without registering that it even exists.

Of course it was closed. It had apparently been closed for some time. That return jet had never run. The sun shelf had been a perfectly engineered circulation dead zone since the day the pool was built, and I'd been walking past that valve that proved it on every single service visit. I opened the valve. The dirt stopped appearing on the shelf. My client stopped questioning my team's work ethic. And I stood at that equipment pad for a moment longer than strictly necessary, having a quiet, private conversation with myself about the difference between seeing something and actually looking at it. The valve was right there. Every visit. Okay, here's another one.

Different pool, different client, same theme. The pH kept rising faster than any reasonable alkaline level could explain. I adjusted the chemistry. I came back. The pH had climbed again. I adjusted it again. Started doing mental math that was getting increasingly creative. Started composing a detailed explanation in my head for a chemistry professor I went to school with, about a phenomenon I was beginning to suspect might be new to science. Then I noticed the fountain. Decorative fountain running twenty four hours a day, aimed directly at one corner of the pool, creating a permanent, dedicated, enthusiastic aeration zone that was driving CO2 out of the water faster than any amount of alkalinity management was ever going to compensate for.

Pulling the entire pool's pH ceiling upward constantly. Every minute of every day. I'd been treating the symptom of a fountain for two visits, walking past the fountain twice per visit. When I explained it to my client, she said, and I quote, Oh, I never turned that off. It's so pretty. She looked genuinely puzzled when I sat down on the pool deck for a moment. I just needed a minute.

One more. Algae on one half of a pool and not the other half. A clean diagonal line of demarcation running roughly through the middle. Algae on one side, crystal clear water on the other, as if someone had drawn it with a ruler. I tested the clear side. Perfect. I tested the algae side. Also somehow perfect. Stood there doing calculations that weren't producing useful answers. Started to develop a working theory that this particular pool existed in two separate chemical universes occupying the same physical space, which I wasn't aware was a real thing, but which at that moment felt like the most plausible explanation available. The ball in the return jet was twisted sideways.

Ninety degrees from where it should have been pointing. Half the pool had been receiving consistent circulation and sanitation for an indeterminate period of time. The other half had been receiving essentially nothing. And the algae, being algae, had done exactly what algae does when it finds an underserved neighborhood. It moved in and set up shop, made itself comfortable. I redirected the return jet. The algae cleared up within a week. Half of that pool had been running at essentially zero effective chlorine for however long that jet had been pointing to itself. The algae didn't care what the other side tested at, it just moved into the neighborhood that wasn't protected.

It took me forty-five minutes to find a problem that had very likely been there since the day the pool was opened that spring. Not because it was hard to find, because I wasn't looking for it. Okay, how about this one? A scum line that would not go away. Same spot every week. Right side of the pool, maybe three feet from the waterfall. I cleaned it on Monday. It was back by our next visit. I adjusted the chemistry. Still there on our next visit. Tried a different enzyme product in the following week. Still there on our next visit. I started to feel like this section of tile had developed a personal grievance against me and was committed to expressing it indefinitely.

Frustrated and not really wanting to hear the customer complain about it again, I spent twenty minutes one afternoon just watching the pool. Watching where the surface moved, watching how the skimmer pulled the film, watching what happened when the wind came through that backyard from the southeast, which it does every afternoon. The scum line was exactly where the pool's circulation pattern and the afternoon wind were meeting to deposit every surface contaminant from the entire pool. Every day. Right on schedule. Predictable as sunrise. I redirected the jets. I'd been cleaning up after a completely predictable physical process for weeks without once asking why it was always that same spot.

That one I actually laughed about once I got back to the truck. I want you to notice the pattern because it's the same pattern every time. Problem appears, I apply chemistry knowledge. Problem persists, I apply more chemistry knowledge. Problem continues to persist. I question the chemistry. I question the equipment, I question my test kit, I question my life decisions and my career choices. And eventually, somewhere in there, I stop treating and actually start looking at the pool. Then I find the actual cause in about ten minutes. Every single time.

Here's what gets me about this, and I mean this genuinely, not rhetorically. Nuclear training gave me a framework that's specifically designed to prevent this exact failure mode. Find the root cause or you haven't fixed anything. Don't treat symptoms. Trace the problem back to its source. Every system is connected to every other system. A single data point from a single location is not a diagnosis. I know all of this. I could recite it in my sleep. I've said versions of it on this podcast. I said it just now. And I still walked past a fountain twice a visit for two weeks. That's not stupidity. That's the natural human tendency to trust expertise over fresh observation, to pattern match against what you already know instead of actually seeing what's in front of you.

And it happens to everyone, especially, I'd argue, to people who are good at their jobs. Because the better you are, the more you trust your framework, and the more you trust your framework, the less you look at the actual system. The instrument panel looks good so you stop looking out the window. And the system keeps doing exactly what it does, governed by laws that do not care about your hours logged or your certifications or your five professional designations waiting patiently for you to look up from the gauges. The antidote is simple. It's just not instinctive. It requires a deliberate choice every single time you walk up to a pool that isn't behaving the way you'd expect.

Stop, look, then think, then test, then treat in that order. When a pool is misbehaving and the obvious chemistry fix isn't working, here are the four questions that'll get you to the answer faster than anything else I know. Where exactly is the problem? Not what's the problem where location first. Scaling on one wall is a completely different diagnosis from scaling everywhere. Algae in one corner is a different problem from algae across the whole pool. A dirty sun shelf is a different problem from a dirty pool. The location of the symptom contains information about the mechanism. Start there every time.

Is this a bulk water problem or a local condition? Test multiple locations before you do anything else. The problem area specifically. The middle of the pool, near a return, away from returns, elbow depth, not on the surface. If the numbers agree across all those locations, you have a bulk water problem and chemistry is probably the right conversation. If the numbers disagree, you've got a local condition, and the disagreement itself is pointing you toward the cause. That disagreement isn't a complication. It's the answer trying to introduce itself to you.

What's physically different about that spot? Sun exposure, circulation pattern, equipment proximity, wind, bather habits. Something's different about where the problem is showing up. There's always something different. Find it before you add anything to the water. It's there. It's usually obvious once you're actually looking at it. And yes, it's occasionally a valve behind the filter that you walk past on every service visit for an indeterminate period of time that may or may not have been over a year.

What does the history tell you? Same problem every summer, you're looking at a seasonal local condition. Same problem since a new feature was installed? That feature is probably involved. Problem that appeared out of nowhere when nothing changed? Something changed, and you haven't found what changed yet. The history is a diagnostic tool. Use it before you open a chemical container. Then test, then treat, in that order, not before.

Here's something I've learned about myself over a long career of being occasionally humbled by bodies of water. The times I got it wrong fastest are the times I trust my expertise more than I trust my observation. I know what pool problems look like, so I look for pool problems. I stop actually seeing the thing in front of me and start pattern matching against everything I already know. And the pool, being a physical system governed by laws that do not care even slightly about my certifications, just keeps doing what it's doing, patiently, waiting for me to stop being an expert for a minute and start being an observer.

The habit of watching carefully before concluding anything didn't start with pool chemistry. It didn't start with nuclear training either, though nuclear training sharpened it into something precise and disciplined. It started earlier, in a place I knew better than anywhere else I'd ever lived. It started with a sound I grew up around that I've come to understand only as an adult, was a man going somewhere inside himself that nothing else in his life could reach. Looking for the thing underneath the surface reading and going deeper than the obvious answer. Because the obvious answer was never the one that mattered. He applied that same attention to everything he touched, not just the music, but everything.

I learned to watch before I learned to test. I learned to listen before I learned to measure. That story is coming. It's one I think you'll find worth hearing. For now, watch before you test. Observe before you treat. Ask what the system is telling you before you decide what it needs.

The pool that makes you feel stupid is trying to teach you something. The ones that taught me the most are the ones I'm most grateful for now. Even the one with the valve behind the filter. We meet every Tuesday.

Thank you for listening. If this episode reminded you of a pool that made you feel stupid, I'd genuinely love to hear about it. Hit the Ask John page at poolsscientific.com and tell me your story. Also, before I go, I've been building something on the side of all this. Something for the people who hear these episodes and want more than what fits on a Tuesday release. I'll tell you what it is soon. For now, just know that it exists and it's almost ready. Next Tuesday, we go deep. Until then, take care of your water.

Find us at poolsscientific.com. If this show has been useful to you, share it with someone who takes our pool seriously. New episodes every Tuesday.