The Expert Trap: When Being Right Gets in the Way

A client hired me for my Azure expertise. Six weeks in, I realized I was the least knowledgeable person in the room—and that was exactly as it should be.

The Setup

Enterprise client. Large data platform migration to Microsoft Fabric. I came in with patterns, best practices, architecture diagrams.

They had twelve engineers who’d been maintaining this specific system for five years. They knew every edge case, every undocumented quirk, every reason why the previous three attempts failed.

I walked in ready to teach. I should have walked in ready to listen.

The Expert Trap

Expertise creates a bias. You’ve seen the patterns before. You know how it usually goes.

The problem: “usually” isn’t “always.” And client context is irreplaceable.

I caught myself doing it in week two. A data engineer mentioned an approach that seemed wrong based on standard patterns. I started explaining why it wouldn’t work.

Then she showed me the edge case. The specific data characteristics. The business constraint that made the standard approach a liability.

She was right. I was pattern-matching. She was problem-solving.

What Expertise Is Actually For

My job wasn’t to transfer my Azure knowledge into their heads. It was to translate their deep system knowledge into the Azure patterns that would preserve it.

I know the platform. They know the problem.

The best consulting engagements combine both. Neither alone is enough.

Practical Shifts

Ask before advising. “Before I share how I usually approach this—what have you tried before and why did it not work?”

This question alone has saved me from recommending things that had already failed.

Name what you don’t know. “I know Fabric well. I don’t know your business logic. Help me understand it.”

This isn’t weakness. It’s efficiency. It builds trust faster than pretending.

Let them teach you. The domain expert who teaches you something is now invested in the solution. That’s more valuable than being right.

The Counterintuitive Truth

The consultants clients remember aren’t always the smartest. They’re the ones who made the client feel smart.

Not by flattering them. By genuinely drawing out their knowledge and using it.

The Result

That migration was successful. Not because I brought the right architecture. Because we built the right architecture together—combining their domain knowledge with the platform expertise I contributed.

They could have built it without me eventually. I couldn’t have built it without them.

That’s the right outcome.

The Bottom Line

Expert knowledge is a tool, not an identity. Use it to help people solve their problems—not to demonstrate that you know things.

The moment being right matters more than solving the problem, you’ve become the problem.

Stay curious. Stay humble. Know your lane and the limits of it.