This transcript was produced by robots and left as-is. Accuracy and elegance are not guaranteed.

Engineering judgment isn’t that special. It isn’t engineering intuition. It isn’t experience as magic. It’s good judgment applied to engineering decisions, and engineers have made it sound more special than it is, because the alternative is admitting it’s learnable.

Engineering judgment is good decision making folded together with technical knowledge, lived experience, and consideration of who builds, operates, and maintains the design after you’re out of the picture.

Now, three things to land before we go further. First, it’s learnable. Not innate, you weren’t born with engineering judgment. Second, each component matters. None of them alone is enough. Third, the downstream user is part of the input. They’re not an afterthought.

Now let me show you what each of those components does and what happens when one of them is missing.

Technical knowledge, the tool, the code, the calculation. Necessary and at times critical, but not enough on its own. Technical knowledge alone gets you the correct answer, and the correct answer can still be useless. Lived experience. The things the code doesn’t tell you. What operators describe when they’re griping. Lived experience alone gets you a gut call without the rigor the design requires. Consideration of who comes after you, the crew that built it, the people who operate it, the people who maintain it. Consideration of the downstream user alone gets you good intentions without competence. But put all three together, and that’s where judgment gets built.

When one is missing, you get isolated thinking. Solutions that are technically correct, but practically infeasible. Decisions that earn the worst label engineers can earn from people in the field.

Back in episode one, I told the story of a pump. The engineer designed it so the entire line had to be shut down for maintenance. The electrician I worked with pointed at it and said, if the engineer had rotated it 90 degrees, the line could have stayed running. Same equipment, same code, same calculation. Different outcome for everyone downstream.

The engineer had the technical knowledge. He didn’t have the other two, but the electrician did. That was where I learned the lesson to stop and listen. Technical knowledge was what I got in school. Lived experience and downstream consideration, those build over years and reps. So what does it look like when all three are working? In my experience, it can look pretty undramatic.

A while back, I was in a multidisciplinary design review meeting for a new piece of equipment. Operations was at the table. Each one of the disciplines was at the table. The equipment was going underneath a platform and the fit was tight. I’m an electrical engineer, but I made a structural recommendation. I said, why don’t we put a hatch above it so we can access the equipment to clean and maintain it? The code didn’t require it. I’m not in that discipline. But nobody pushed back. Operations recognized the call, mechanical accepted it, and the hatch went in. That’s it. That’s the whole story. And that’s the point. When the three inputs are working, judgment doesn’t show up as heroics. It’s not wearing a cape. It shows up as a hatch nobody argued about. The recommendation didn’t come from a calculation or a code reference. It came from 20 years of listening to operators talk about what poor access costs them. Lived experience doesn’t respect discipline boundaries. The electrical engineer made a structural call because the input was there. Compare the two scenes. Pump from episode one, dramatic, expensive, somebody had to point it out after the fact. The hatch, undramatic, cheap, prevented an entire problem from ever existing.

Now for the part that matters. Bad judgment doesn’t look like incompetence from the outside. It still looks like rigor. The pump engineer ran his calculations. He followed the code. He stamped the drawing. That’s why bad judgment persists. Nobody catches it until the operator is the one paying for it.

In the last episode, I talked about the credibility gap and pointed to the opportunity to learn your way across it. This is what gets built when you do that. Credentials get you the title. Judgment is what you build from there. Lived experience doesn’t accumulate from sitting at your desk. It accumulates from asking, listening, staying curious, and integrating what you can’t calculate.

So here’s one to sit with.

When was the last time you made a call that crossed a discipline line because experience told you to? If you can’t think of one, that’s a data point. The opportunities are usually there. The question is whether you’ve built the inputs to recognize them.

That’s it for this one. We’ll keep going.