The Worst Advice I Ever Recieved as a Construction Materials Technician

In 2005, I was a relatively new construction materials technician.

I had only been in the industry a few months and was still trying to understand the job. Like many new technicians, I wanted to do good work, avoid mistakes, and become competent as quickly as possible. I approached the field the same way I approached most things in life: I studied.

Before going to a project site, I would review plans and specifications whenever I could. I wanted to understand what was being built, what work was taking place, and how our testing fit into the larger project. I wasn't always successful, but I genuinely wanted to learn the profession rather than simply go through the motions.

One day, a manager pulled me aside and gave me some advice.

His message, stated somewhat more crudely than I will repeat here, was essentially this:

You should know the plans better than anybody else on the project, and you should walk onto every jobsite like you're the smartest person there and can't wait to show everybody how much you know.

At the time, I understood what he meant.

He was trying to encourage confidence. He wanted technicians to know their projects, be prepared, and not be intimidated by contractors, inspectors, or superintendents.

There was some good advice buried in there.

The problem was that there was also some very bad advice buried in there.

Problem #1: Arrogance Is Not Professionalism

Construction projects are team efforts.

Contractors, inspectors, technicians, engineers, superintendents, project managers, and owners all bring different kinds of expertise to a project. Walking onto a jobsite with the goal of proving that you're the smartest person there is usually counterproductive.

People don't care how much you know until they trust that you're there to help the project succeed.

When a technician approaches a project with arrogance, the result is often friction. When a technician approaches a project with professionalism, curiosity, and respect, the result is usually cooperation.

Over the years I learned that respect isn't earned by trying to demonstrate superiority.

It is earned through competence, consistency, honesty, and reliability.

The technicians I respected most were confident in their abilities but humble enough to listen, ask questions, and learn from the people around them.

Problem #2: You Don't Need Everything Memorized

The second problem with this advice was the assumption that a good technician should know every detail of every plan and specification.

I don't believe that.

A good technician should understand the project and know where to find information when needed. Those are not the same thing.

Our job is to perform testing correctly, document our work accurately, report results honestly, and compare those results against project requirements.

None of that requires memorizing every specification.

There is nothing wrong with opening a set of plans.

There is nothing wrong with reviewing a specification.

There is nothing wrong with asking a contractor:

"Can you remind me what the compaction requirement is in this area?"

In fact, asking that question often demonstrates professionalism rather than weakness.

It shows that you care more about getting the answer right than pretending you already know it.

The best technicians I've worked with weren't the people who had every answer memorized.

They were the people who knew how to find reliable answers and verify information before making decisions.

Problem #3: It Discourages Honesty

Looking back, I think this may have been the biggest problem of all.

Buried within the idea that you should always appear to be the smartest person on the project is the belief that you should always have an answer.

But no one has all the answers.

Projects are too complicated.

Specifications are too detailed.

Conditions change too quickly.

Some of the best technicians, inspectors, managers, and engineers I've ever worked with have been completely comfortable saying:

"I don't know."

The difference is that they never stopped there.

They followed it with:

"Let me find out."

Or:

"Let's check the plans."

Or:

"Let's verify that."

Or:

"Who would know the answer?"

Saying "I don't know" does not make a technician weak.

It does not make a technician unintelligent.

It does not make a technician unprepared.

It makes a technician honest.

And honesty is one of the most important professional traits a technician can possess.

The truly effective technicians aren't the ones pretending to know everything.

They're the ones who know how to navigate a project, locate information, ask the right questions, and find the people who can help solve a problem.

What I Eventually Learned

As my career progressed, I realized that the most effective technicians were not the people trying to look knowledgeable.

They were the people trying to become knowledgeable.

They knew how to read plans.

They knew how to ask questions.

They knew how to verify information.

They knew when something didn't make sense.

Most importantly, they were honest enough to admit when they didn't know something.

Their confidence came from competence, not appearance.

Why This Matters

As a young technician, I often felt pressure to act like I knew more than I actually did.

Looking back, I think many technicians still feel that same pressure today.

New technicians are frequently handed responsibilities they don't fully understand. They're sent to projects they've never seen before. They're expected to answer questions they haven't yet learned to answer.

In many organizations, the unofficial training program can feel like this:

Fake it until you make it.

I never thought that was a very good system.

In fact, it is one of the reasons I started creating training materials early in my career.

I wasn't trying to become a trainer.

I wasn't trying to write manuals.

I was simply trying to document the things I wished someone had explained to me when I started.

I wanted clarity.

I wanted context.

I wanted practical guidance.

I wanted a way for new technicians to learn without feeling like they had to pretend.

Over time those notes grew into checklists, procedures, presentations, reporting standards, training guides, and lessons learned.

Today they form part of the foundation of what I hope CMT Institute can become.

The mission is simple:

To help construction materials professionals develop practical field judgment, technical competence, and professional confidence without feeling like they have to pretend they know things they don't.

It is okay not to know.

It is okay to ask questions.

It is okay to verify information.

It is okay to learn.

What is not okay is allowing pride, ego, or fear of looking inexperienced to get in the way of becoming better.

Our industry does not need more technicians pretending to have all the answers.

It needs more technicians who know how to find the right answers.

Those are the professionals I have always tried to become, and those are the professionals I hope CMT Institute can help develop.