You’ve held back an idea because it felt too obvious. That was probably your best one.

Last week, I almost kept my mouth shut.

We were in a conceptual design meeting with a client. Their PM and Operations Manager were on the call. So were my civil, structural, and mechanical engineers. We were reviewing a platform design above some equipment, and I mentioned — almost as an aside — that we should add a hatch.

Simple enough. A hatch in the platform above the equipment so maintenance crews could actually access it for cleaning and servicing without tearing the whole thing apart later. Better to build it in now than retrofit it as an afterthought after the project is done and the plant staff are grumbling.

I nearly didn’t say it because it felt too obvious. Plus, I’m an electrical engineer by training, so what do I know?

Here’s what happened: the client’s PM and Operations Manager lit up. The engineers in the room — my own engineers — had the same reaction. Nobody had thought of it. To them, it was a revelation. To me, it felt like pointing out that doors are useful.

That gap has a name, and it’s costing you.

The Big Picture

There’s a specific way engineers discount their own value, and it’s not imposter syndrome. It’s something quieter than that.

We assume that if an answer came quickly, it can’t be worth much. Fast thinking feels cheap. Slow, painful, agonizing thinking feels like real expertise. So we hold back the fast stuff, throw it out as an aside, or call it “common sense” and move on without claiming credit for it.

But fast thinking isn’t cheap. It’s the output of years of pattern recognition compressed and internalized until it runs automatically. The speed isn’t a sign that the answer was easy. It’s a sign that you’ve solved this problem so many times your brain stopped keeping score.

I’ve been on projects where platforms were designed without maintenance access because nobody asked the right question early. I’ve seen the consequences: equipment that can’t be cleaned properly, maintenance crews improvising dangerous workarounds, retrofit costs that dwarf what a simple design consideration would have cost at the start. That history lives in my head. It informed a two-second suggestion in a meeting. The client doesn’t see the history. They just see the hatch.

Core Insight

The insight that costs you nothing to produce can be worth everything to someone who doesn’t have your years of experience.

This is the trap. The skills that took the longest to develop feel the most automatic, which makes them feel the least valuable. You’ve internalized so much through experience that the output looks effortless. And effortless reads as obvious. And obvious reads as not worth charging for, not worth claiming, not worth saying out loud.

But nobody else in that room is carrying your history. Your client is thinking about budget and schedule. Your structural engineer is thinking about load paths. Your operations manager is thinking about next quarter. Nobody else has the specific, accumulated pattern recognition to know what gets missed at this stage and what it costs to fix later. That knowledge feels like background noise to you. To everyone else in the room, it’s the signal they’ve been missing.

That’s not common sense. That’s compressed expertise wearing common sense as a disguise.

Why This Matters To You

If you’re giving away your best thinking because it feels obvious, the problem isn’t your technical ability. It’s that nobody in the room is discounting your expertise harder than you are.

Your clients aren’t evaluating your ideas based on how long they took to produce. They’re evaluating impact. When you open with “this is probably obvious, but…” or “it might just be common sense…” you’re discounting the invoice before they’ve even seen it. And they’ll take that discount every time.

The early-stage insight you almost held back is worth more than the late-stage fix you’ll get paid to implement. Raising your hand in a conceptual design meeting costs you nothing. Staying quiet costs your client a retrofit, a budget conversation they didn’t see coming, and a nagging suspicion that their engineering team missed something basic. That suspicion has a way of showing up at contract renewal time.

Your pattern recognition is a deliverable. Start treating it like one.

Practical Steps

Today: Think back over your last few client meetings or project reviews. What did you almost not say because it felt too obvious? Write it down. Not as a journal exercise — as an inventory. That list is the beginning of understanding what your experience is actually worth.

This Week: Catch yourself before you use the qualifier. “This is probably obvious, but…” and “it might just be common sense…” are the two phrases that cost you the most credibility in the room. Drop them. State the observation, full stop, and let the room tell you whether it was obvious. Spoiler: it usually isn’t.

This Month: Look at where your fast insights are showing up in your work and where they aren’t priced in. Are they in your proposals? Your scope documents? Your discovery conversations with clients? If the thinking that feels automatic to you is landing as revelations to the people across the table, that gap is a pricing problem, not a confidence problem. Start closing it.