The One Skill Nobody Teaches You | From the Builder’s Desk

The One Skill Nobody Teaches You

A guy walked into Circle K the other night looking for a phone charger. He was already heading toward the wrong wall when I stopped him.

“What kind of phone do you have?”

Old phone. Micro USB. He was about to grab a USB-C and waste twelve dollars on a cable that wouldn’t fit. One question saved him a trip back to the counter and a receipt he’d have to dig out of his car.

I didn’t know anything about his phone. I didn’t need to. I just needed to know one thing before he spent money on the wrong thing. That’s the skill. Not the answer. The question that gets you to the answer before you waste time, money, or trust going the wrong direction.

Nobody teaches this. Schools teach you to answer questions. Jobs teach you to follow procedures. The internet teaches you to Google symptoms and panic. But nobody sits you down and says, “Before you do anything, figure out what you actually need to know first.”

Where I Learned It

My first real job was at an automotive supplier in 1997. I was eighteen. It taught me a lot about systems. My next factory job I had to learn assembly machines. The lady training me on two-hand assembly did something I’ve never forgotten. Before she showed me anything about the machine, before she explained the process, before she even turned it on, she told me one thing.

“Use both hands.”

She set up the entire workstation based on how I needed to operate it. Parts on the correct side. Tools within reach. The workflow matched how my body actually moves instead of how the manual said it should.

That’s when it clicked. She didn’t teach me the machine first. She diagnosed the operator first. The machine was the same for everybody. The operator was different every time. And if you set up the environment wrong because you didn’t take one second to look at the person in front of you, they struggle with something that should have been easy.

I carried that forward into every job, every industry, every conversation I’ve had for the next twenty-seven years. (I still think about her sometimes. She probably doesn’t know she changed how I think about everything.)

The Diagnostic

Here’s what most people do when someone comes to them with a problem. They start solving it. Immediately. They hear the symptom and reach for the fix. It’s instinct. Somebody says their plant is dying and you say add fertilizer. Somebody says their website isn’t ranking and you say write more content. Somebody says their car is making a noise and you say check the belts.

Wrong. Wrong. Wrong.

What’s the pH of your runoff? What does your Google Search Console actually show? Where exactly is the noise coming from and when does it happen?

The question comes first. Always. Because the symptom is almost never the problem. The symptom is what the problem looks like from the outside. The problem is hiding underneath, and it only comes out when you ask the right thing at the right time.

I grew plants for years. The cannabis community online is full of people posting pictures of yellow leaves asking what’s wrong. And the answer from a hundred commenters is always the same. “Cal-Mag.” Calcium and magnesium supplement. Just add more stuff. Buy another bottle.

But nobody asks about pH. Nobody asks what the water going in measures and what the water coming out measures. Because the answer to yellow leaves is almost never a missing nutrient. It’s a lockout. The nutrients are already in the soil. The plant can’t access them because the pH is wrong. Adding Cal-Mag to a pH problem is like putting premium gas in a car with a clogged fuel filter. The input isn’t the issue. The system is.

One question. “What’s your pH?” That saves someone $40 on a bottle they don’t need and actually fixes the plant.

Getting On Their Level

The question only works if the person is actually listening when you ask it. And they won’t listen if they think you’re talking down to them. I don’t care if you’re the world’s foremost expert on whatever the subject is. If the person in front of you feels like you’re above them, they stop hearing you.

I think about this like approaching an animal. You don’t walk up to a nervous dog standing at full height. You crouch down. Make yourself smaller. Less threatening. Let them come to you. Children are the same way. If you’re towering over a five-year-old trying to explain something, they’re not listening to your words. They’re processing the fact that you’re enormous and scary.

Adults aren’t any different. They just hide it better.

A stranger came into the store recently with a problem. His relative was in her sixties, dehydrated, couldn’t keep anything down. The hospital had her on a cycle. Give her pills, pills cause side effects, give her more pills for the side effects, stabilize her on IV, send her home, she crashes, she comes back. Repeat. The bottle cycle. Same as the Cal-Mag. Same as every system that sells you the next intervention instead of fixing the root cause.

I could have said, “She needs electrolytes and hydration, here’s what to buy.” That’s the answer. But the answer without the delivery doesn’t stick. He’s a stranger in a gas station talking to a clerk. Why would he listen?

So I told him I’m the smartest guy he’s ever met.

He laughed. Of course he laughed. Who says that at a gas station at ten o’clock at night? But while he was laughing, his guard came down. And then I just started talking. Not lecturing. Talking. Giving him ideas. Explaining what dehydration actually does, why the pill cycle doesn’t fix it, what electrolytes are and why they matter, what options exist outside the hospital loop. Not telling him what to do. Making his mind think.

He stayed twenty minutes. He wasn’t laughing anymore by the end. He shook my hand and gave me his name.

That’s the sequence. You meet them where they are. You make them comfortable. You earn the right to give them information by demonstrating that you actually have information worth giving. And you never, ever tell them what to do. You give them enough that they arrive at the answer themselves.

Why “I Don’t Know” Is the Most Powerful Thing You Can Say

I know a lot about a lot of subjects. I’m not being arrogant. That’s just true. Car audio since I was seven. Factory operations across five different industrial companies. Water treatment, chemical handling, electrical systems, welding, machining, paint matching, forklift operation, quality control databases, SEO, WordPress, amplifier engineering, AI architecture. I’ve touched all of it and I learned the system in every single one. Not just my station. The whole system.

But I don’t know everything. And the people who pretend they do are the ones who cause the most damage.

A doctor who doesn’t say “I don’t know” puts a patient on a pill cycle instead of investigating the root cause. A mechanic who doesn’t say “I don’t know” replaces heaters and fans instead of checking the thermocouple. A contractor who doesn’t say “I don’t know” delivers work that costs you more to fix than it cost to produce. An SEO provider who doesn’t say “I don’t know” charges you $665 for a placement you could get for $15.

The right question at the right time sometimes is “do I actually know enough about this to help?” And if the answer is no, the right move is saying so. I haven’t tested this myself. I’ve heard this secondhand. I’m not sure about this part. That honesty is what separates someone worth listening to from someone performing expertise they don’t have.

Actually, let me rephrase that. It’s not just honesty. It’s calibration. Knowing the boundaries of what you know is itself a skill. Most people overestimate their knowledge in areas they’ve read about and underestimate it in areas they’ve lived. The difference between having read about pH lockout and having stood over a dying plant at three in the morning adjusting the water until the runoff numbers finally moved is enormous. Both people might give you the same answer. Only one of them can tell you what it actually looks like when it’s working.

Reading the Room Before You Open Your Mouth

There’s a truck driver who comes into the store. We talked for over half an hour one night. There’s a regular who comes in and I have his lottery ready before he reaches the counter because I’ve memorized his order and his speed. There’s a girl who came in barely able to stand, trying to figure out how to tap her phone on the card reader while staring into space. Three completely different people. Three completely different needs.

The trucker needed conversation. He got half an hour of it.

The lottery guy needs speed and consistency. He gets his tickets without asking.

The girl needed patience without judgment. She got walked through the pin pad one step at a time without anyone making her feel stupid for not knowing how it worked.

Same person behind the counter every time. Different delivery for every customer. Because I run a diagnostic before I open my mouth. Not a conscious checklist. Not a procedure. Just a read. Who is this person right now, what do they need right now, and what’s the fastest way to give it to them without making them feel like they’re being managed?

That read is the skill underneath all the other skills. Everything I know about every industry is useless if I can’t deliver it in a way the person in front of me can actually receive. The knowledge gets them to listen. The delivery gets them to stay.

The Drip Feed

I manage a contractor in Bangladesh. He’s sharp. Former content agency background, knows SEO fundamentals, works hard, fronts his own money on projects before I reimburse him. Good instincts. But when I started working with him, he didn’t know what I know. And the worst thing I could have done was dump everything I know into his lap on day one.

I’ve seen managers do this. They hire someone, sit them down, and fire-hose them with every procedure, every exception, every edge case. By lunch the new person is drowning in information they can’t organize. They remember maybe ten percent. The rest is noise that makes them feel stupid for not retaining it.

Instead I drip-fed. One concept at a time. “Google Search Console is your friend.” That’s it. That was the whole lesson for that phase. Not how to use it, not what every metric means, not the fourteen things you can do with URL inspection. Just go look at it. Poke around. Come back with questions.

He came back with questions. Good ones. And each question got one answer that opened one more door. Over weeks, not hours. The learning stuck because each piece had time to settle before the next one arrived. He didn’t just memorize what I told him. He understood it because his brain did the work of connecting each piece to the one before it.

That’s how you teach without teaching. You don’t hand someone the answer. You hand them the breadcrumb that leads to the question that leads to the answer that they find themselves. The discovery is theirs. The direction was yours. But they’ll never know the difference, and that’s the point. Because knowledge you discover feels different than knowledge you were handed. One creates capability. The other creates dependence.

The hospital tells people what to do. Take this pill. Come back Tuesday. Follow the plan. The patient depends on the hospital because the hospital never gave them the tools to understand their own body. I gave a stranger enough information about electrolytes and dehydration that he doesn’t need me next time. He can think it through himself. One of those approaches generates revenue. The other generates a capable human being.

I know which one I’d rather be doing.

Patterns Across Systems

I worked in a paint factory for seven years. Colwell Industries. My job included running a spectrophotometer for color matching and operating a Dromont paint dispenser. The spectrophotometer measures reflected light wavelengths to determine the exact color composition of a sample. You’d think color matching is simple. It’s paint. How complicated can paint be?

Incredibly complicated. A color that looks right under fluorescent lights looks wrong under sunlight. A formula that works with one pigment base fails with another because the particle size changes how light interacts with the surface. Temperature affects viscosity which affects application thickness which affects the final color. The spectrophotometer gives you numbers. The numbers tell you what’s happening. But you still have to ask why the numbers are what they are, and that question takes you into chemistry, optics, and environmental variables that most people never think about.

Same pattern as the pH lockout. Same pattern as the thermocouple. The surface symptom says one thing. The diagnostic question reveals something deeper. The color is wrong isn’t the problem. Why is the color wrong is the question. And the answer might be the pigment, the base, the lighting, the temperature, the application method, or six things working together in ways the formula didn’t account for.

I see this everywhere now. At the gas station when a customer describes a problem. At my desk when I’m looking at search engine data. In conversations with my wife who can’t describe where a barrel is. In every industry I’ve touched, the pattern repeats. People fixate on what’s happening. The useful question is always why it’s happening. And the useful answer usually isn’t what they expected.

That’s not genius. I want to be clear about that. I’m not a genius and I’ll correct anybody who says I am. I’m someone who knows a lot about a lot of subjects because I’ve worked in a lot of industries and I learned the whole system every time, not just my piece of it. That range is the thing. The guy who knows everything about one thing can solve one kind of problem. The guy who knows enough about twenty things can see the pattern that connects all of them. And the pattern is always the same. Diagnose first. Ask the question. Then fix the thing.

Why I’m Telling You This

Because I spent my whole life knowing this stuff and having no platform to share it from. I was the clerk, the operator, the material handler, the assembly worker. The guy behind the counter, behind the forklift, behind the machine. Nobody asks the overnight gas station clerk for advice on systems thinking. Nobody asks the factory worker how he’d redesign the quality process. They tell you what to do and move on.

But people stay. That’s the part nobody expects. A stranger stays twenty minutes at a gas station because the guy behind the counter knew something useful about his relative’s medical situation. A customer asks my name because I helped her figure out her phone. A truck driver talks for half an hour because I listened and actually responded with something worth hearing. People stay when you give them something real. They leave when you give them a script.

This site is the platform. These articles are me behind the counter, except the counter reaches further than Albion, Indiana. If you’re building something, fixing something, learning something, or stuck on something, I’m probably the kind of person you’d end up talking to at a gas station at midnight. Except now you don’t have to drive to Albion.

I don’t have all the answers. I know that. But I’m very good at questions. And sometimes the right question from someone who’s been inside enough systems to see the pattern is worth more than a bookshelf of answers from people who’ve only been inside one.

What the Answer Costs

I used to think knowing things was the whole game. If I knew enough, I’d be valuable. If I knew more than the person next to me, I’d get ahead. That’s the assumption most people run on. Knowledge equals advantage.

It took me a long time to realize that’s backwards. Knowledge without delivery is a library nobody visits. I had years where I knew exactly what was wrong with a system, a process, a piece of equipment, and nobody asked. Or worse, I’d tell them and they’d ignore it because the information came from the wrong job title. The overnight guy. The temp. The assembly worker. The forklift driver. I diagnosed a malfunctioning food warmer at Circle K as a bad thermocouple. They’ve had two service companies come out, replaced heaters and fans, and the temperature still swings. Nobody checked the thermocouple because the guy who identified the problem runs the register.

I’ve made peace with that. Mostly. The part I haven’t made peace with is how many people walk around with the right answer and no way to get anyone to hear it. Smart people working quiet jobs, carrying knowledge that could save someone time or money or health, and the system never asks them. The hospital doesn’t ask the patient what they’ve noticed about their own body. The mechanic doesn’t ask the owner what the car was doing before the noise started. The manager doesn’t ask the overnight clerk why the warmers aren’t holding temperature.

The cost of not asking the right question isn’t just a wrong answer. It’s a right answer that never gets heard.

So if nothing else sticks from this piece, take this. The next time someone in front of you seems like they might know something, ask them. Not because you think they’re an expert. Not because they have the right title. Just because they’re standing in the room where the problem lives, and they might have been watching it longer than you have.

The best question I ever received was “use both hands.” It didn’t sound important. It changed everything.

The Question Nobody Asks

Here’s what I keep coming back to. People spend their entire lives learning answers. School is answers. Training is answers. Certifications are answers. But the people who actually change outcomes, the ones who fix the plant, diagnose the thermocouple, save the customer twelve dollars on a charger, keep a stranger’s relative out of the hospital bottle cycle, they’re the ones who learned how to ask.

The right question at the right time is worth more than a hundred right answers at the wrong time.

I’m not saying answers don’t matter. They obviously do. But the answer is the easy part. Any search engine gives you answers. Any AI gives you answers. Any person with a smartphone gives you answers. The hard part is knowing which question to ask, when to ask it, and whether the person you’re asking is ready to hear why you’re asking it.

So here’s mine for you. The one question I’d ask before anything else, before any advice, before any recommendation, before any solution.

What are you actually trying to fix?

Not what’s the symptom. Not what’s bothering you. Not what does it look like from the outside. What is the actual thing underneath all of it that needs to change? Because until you answer that honestly, everything else is Cal-Mag.

I don’t have an answer for that one. That’s yours. I’m just trying to get your mind to think.