Trust Comes Before Technical Skill for Engineers

What matters most for an engineer? Technical skill, design ability, implementation speed, problem-solving, certifications, years of experience — all of these matter. But after years of working across different projects in the IT industry, I’ve landed on one conclusion: delivering real value starts with being honest with the client.

Why honesty matters this much

The reason is simple. No matter how skilled a technologist you are, lying to a client destroys trust — and trust, once lost, doesn’t come back easily.

Technical work is never just the deliverable. It’s built from a daily accumulation of communication: confirming requirements, aligning on shared understanding, consulting, reporting, sharing risk, estimating, explaining progress. Trust is the foundation all of that sits on. With trust, clients tell you what they actually want and raise problems early. Without it, both of those become much harder. Integrity isn’t just a personality trait — it’s a practical skill that feeds directly into the outcome of the work.

Losing trust means losing access to what clients actually want

Clients rarely arrive with everything they need fully articulated. Often they haven’t organized what’s actually bothering them, they’re holding back out of politeness, or past failures have made them cautious.

In moments like that, clients lean on whoever they feel safe being honest with. If they suspect you’d lie — hide something inconvenient, misreport progress, cover up a problem — they stop opening up. And once that happens, you lose access to what they actually need, and the project drifts further from the real target with every step.

Technical skill alone doesn’t build trust

Technical skill matters, obviously. Knowledge, experience, and implementation ability all matter. But they aren’t enough on their own. Pretend you understand something when you don’t, say “it’s fine” when you’re behind schedule, delay reporting a mistake — do any of that, and trust collapses no matter how skilled you are.

The reverse also holds: admit honestly what you don’t yet understand, surface risk early, report mistakes without hiding them, and people tend to trust you over the long run, even through occasional short-term failures. I’ve come to believe trust comes from honesty, not perfection.

”Never lying” sounds easy and isn’t

Staying honest in ordinary, low-stakes moments isn’t hard. The real test comes when you’ve made a mistake, broken a promise, or stand to lose something by telling the truth. That’s exactly when the difficulty spikes — the harder things get, the more tempting it is to hide, downplay, or make excuses. Whether you’re actually honest doesn’t show up when nothing’s wrong. It shows up when something goes wrong.

So what does being honest actually look like in practice? Say “I don’t know” when you don’t. Say “I made a mistake” when you did. Raise a delay before it becomes a surprise. These can look like weakness, but it’s the opposite — the people who can do this are the stronger ones, because they surface problems early, and problems are always cheaper to fix the earlier they’re caught. That’s true of systems and of relationships alike.

This ability to share uncomfortable things without hiding them connects directly to what I wrote in Knowing psychological safety isn’t enough — the four stages: understand, design, implement, reproduce: being able to voice a mistake or a nagging doubt, without being punished disproportionately for saying it, is what makes a team healthy. Integrity isn’t only a personal virtue — it shapes the health of how a team operates. As I explored in “Black Box Thinking” — Life Is Too Short to Experience Every Failure Yourself, teams that can detect, report, and actually use their failures are the ones that stop repeating them.

Defining honesty as small, concrete actions

“Be honest” is important but abstract, and abstract goals are hard to act on day to day. So I want to break it down into something small and concrete:

Don’t pretend to understand something you don’t
Share a mistake the moment it happens
Separate fact from interpretation when you speak
Don’t shade the truth to protect yourself
Pass along inconvenient information when it matters

Made concrete like this, integrity becomes something you can actually act on. It isn’t one big, defining act — it’s the accumulation of small choices, made daily. That accumulation shares its roots with what I wrote in “Words Are Blades” — How a Single Phrase Can Stay with Someone Forever: treating the words you say as something that carries weight, not something to toss out lightly.

Closing thoughts

Lying costs you trust. Losing trust costs you access to what a client actually needs. And without that, delivering real value gets much harder. That’s why I believe honesty with the client sits underneath everything else in this work.

And honesty is tested most, not when things are calm, but exactly when you’ve made a mistake or stand to lose something. Sharpening your technical skill matters. But turning that skill into real value for someone else requires a foundation they can trust — and that foundation is integrity.