Your expertise is valuable, but only if clients can access it without feeling stupid, excluded, or talked down to. I've seen brilliant consultants alienate clients by making them feel like they were in a lecture hall rather than a collaboration.
The challenge is showing you know your stuff while keeping clients comfortable asking questions, pushing back, and participating as equals in their own project.
Why this matters
Expertise that intimidates creates distance. Clients stop asking questions because they're afraid of looking ignorant. They stop sharing concerns because they don't want to seem unsophisticated. They defer to your judgment on things they should be weighing in on. The relationship becomes hierarchical rather than collaborative, and the work suffers because you're missing their perspective.
Accessible expertise does the opposite. Clients trust your competence, feel comfortable engaging, and become better collaborators. You become a trusted advisor, not a distant authority.
The principles
Share knowledge to empower, not to impress. If you catch yourself explaining something because you want them to know how smart you are, pull back. Explain things because they need to understand.
Welcome questions as signs of engagement. "That's a great question" should be genuine, not a verbal tic. A client who asks questions is a client who's trying to understand. That's exactly what you want.
Acknowledge their expertise. They know their business, their users, their industry. You know the technology. Both are equally important.
Explain your reasoning, not just your conclusions. "I recommend this approach because..." invites understanding and discussion. "Just trust me" shuts it down.
What this looks like
Demonstrating expertise accessibly:
"In my experience with similar e-commerce platforms, checkout conversion typically improves 15-20% when we reduce from four steps to two. I've seen this across about a dozen projects. For your specific case, here's what I'd recommend..."
Why It Works
Shows experience and data. Makes it relevant to their situation. Doesn't talk down.
Welcoming questions:
"That's a good question, and it actually touches on a nuance that even experienced developers sometimes miss. Here's the thing..."
Why It Works
Validates their question. Makes asking feel smart, not dumb. Provides a clear answer.
What bad looks like
"Obviously you need OAuth 2.0 with PKCE flows. Everyone knows that. It's basic security." Condescending, assumes knowledge they don't have, makes them feel stupid.
[Heavy sigh when client asks a question.] "Like I said, this is the only way to do it." Dismissive, discourages future questions, creates hierarchy instead of collaboration.
Getting better at this
- Frame expertise as service: "I've learned this so I can help you avoid these pitfalls."
- Acknowledge their domain: "You know your business better than I do."
- Ask "What questions do you have?" not "Do you understand?"
- Show your reasoning, not just your conclusions.
- When you don't know something, say so. It makes everything else you say more credible.
- Celebrate their insights: "That's a really good point I hadn't considered."
How this connects
This combines explaining complex things without condescension, instilling confidence through competence, asking good questions, the reassuring "I don't know," and building long-term relationships based on mutual respect.
Things to try
- Notice when you're talking about your expertise. Is it to serve or to impress?
- Practice saying "great question" genuinely to every client question.
- After explanations, ask "Does that make sense?" and genuinely want to know.
- Explicitly acknowledge client expertise in their domain.
- Build the habit of explaining your reasoning, not just your conclusions.