The Expertise Paradox: Why experts hesitate to share their ideas publicly & Why Knowing More Can Make You Less Likely to Speak

There seems to be an unwritten qualification process for having a thought in public.

If you’re unsure, don’t post yet.

If you’re still learning, definitely don’t post yet.

If someone knows more about the subject than you do, perhaps they should be the one talking about it.

If you’re not one of the world’s leading experts, what exactly qualifies you to have an opinion?

So you wait.

You read more, you get another qualification, you do the work for another year, and you gain more experience. And, inconveniently, all that experience introduces you to even more things you don’t know.

So the finish line moves again.

Eventually, you might become one of the people who really does know what they’re talking about.

Except now you’re busy doing the thing.

I get it.

I get why so many smart people aren’t posting.

The problem is that if you follow this logic for long enough, you can spend your entire career becoming more qualified while missing opportunities because nobody knows that you know what you know.

There is something strange about expertise that we don’t talk about enough.

Knowing more doesn’t always make you feel more qualified to speak.

Sometimes, it does exactly the opposite.

I know this because I do it too

I’ve been vibe coding.

I’m building actual products, like this one that's FREE.

I’m spending hours inside the process. I’m learning what works, what breaks, what AI agents are surprisingly good at, what they are terrible at, and how quickly a seemingly simple change can become an entire afternoon.

Which means I have thoughts about vibe coding.

Quite a lot of them, actually. Been tweeting some of them too.

And yet, whenever I think about writing publicly about what I’m learning, another thought arrives almost immediately:

I don’t know enough about this yet.

I’m new.

There are people who understand the AI technology far better than I do.

Some of the things I’m discovering probably became obvious to experienced developers years ago.

And, if I’m being completely truthful, sometimes I’m embarrassed by how long it is taking me to build things I thought would be much faster to build.

So my instinct is to wait.

Learn more first, build more first, become so much better at it first. Then perhaps I’ll have earned the right to talk about it.

Except there is a problem with that logic.

I am learning precisely because I am doing it.

The mistakes are part of the experience. The things I am discovering late are still things I have discovered.

The gap between what I expected building with AI to be like and what actually happens when you try to build a real product is, in itself, something worth thinking about.

And the irony is that when I have shared some of this publicly, other people have started to associate me with technology.

Recently, I even recently found myself included on a list of top African Women using technology.

Seems I hadn't suddenly become more qualified between writing the post and someone reading it.

The experience was already there.

Publishing simply made the experience visible.

Which makes me wonder how often we confuse having something worth contributing with having earned some imaginary permission to contribute it.

Think of it like this: perhaps the qualification doesn't have to be:

I know enough to tell everyone how this works.

Perhaps it can be much simpler:

I have enough experience with this to have thoughts about it.

Knowing more doesn’t necessarily make you feel more qualified

I see this from the other side all the time.

I’ll be scrolling through Instagram and find someone explaining why professionals should post online, how visibility works, or why people need to stop being afraid of sharing their ideas.

Sometimes the point is useful.

Sometimes I find myself thinking: I know this.

In fact, I know considerably more about this than what is being said here.

And then comes the slightly annoying realization:

They said it. I didn’t.

The internet has a strange way of making visibility look like evidence of expertise.

We encounter someone talking confidently about a subject again and again, so we begin to associate that person with the subject.

Meanwhile, someone with ten or twenty years of experience can remain almost completely invisible in the same conversation.

Not because they know less. But, sometimes, precisely because they know more.

Experience has introduced them to the exceptions.

• They know which answer changes depending on the circumstances.

• They have seen the strategy that works beautifully in one organization fail completely in another.

• They know the neat framework leaves something out.

• They know there is usually another question hiding behind the first one.

Ask someone at the beginning of their understanding and you might get an answer. Ask someone who has spent years doing the work and you are much more likely to hear:

“It depends.”

We often mistake that hesitation for a lack of authority when it can be evidence of something much more valuable: context.

This is one of the stranger consequences of becoming good at something.

You don't simply accumulate answers. Nah, you are more privileged than that: you accumulate exceptions, caveats, patterns, contradictions and better questions.

Your knowledge grows and so does your awareness of its edges.

The Expertise Paradox is what happens when growing knowledge makes someone less likely to share their ideas publicly: the more experience they gain, the more aware they become of complexity, exceptions and everything they still don't know.

Which means the feeling of finally knowing enough may never arrive. Perhaps we have been waiting for expertise to feel like certainty when, from the inside, real expertise often feels much more like:

Here is what I’ve learned.

Here is what I’m learning.

We have confused contribution with authority

I think one of the reasons thoughtful people hesitate to publish is that we have made having a thought in public feel like making a declaration.

You are no longer simply saying:

Here’s what I think.

It can feel as though you are saying:

I am an authority on this subject. This is the answer. I am prepared to defend it forever.

Those are very different things.

Personally, when I publish something, what I am actually saying is much closer to:

Here’s my thought. I wonder what you think. Do you agree?

Maybe that comes from studying philosophy.

I spent years learning how to make an argument while sitting comfortably with the possibility that somebody else could make a different one. The interesting part wasn't always arriving at one absolute answer. It was learning to examine a position, defend it, challenge it and change your mind when a better argument appeared.

I think publishing can work the same way.

Having an opinion does not mean you have to die on that hill for the rest of my one short yet long life.

Being wrong publicly does not terrify me either.

For five years on the Yes Girls Podcast, we have tried things, been bad at them, talked about being bad at them, and then talked about what we learned.

If anything, I trust people more when they can say:

I was wrong.

Or:

This is what I’m learning.

Or even:

I used to think this. I don’t anymore.

Changing your mind when the evidence changes doesn't make your thinking less credible.

In fact, it shows me there is actual thinking happening!

But that doesn't mean I believe everyone should confidently say anything about everything.

What bothers me online is almost the opposite.

It's watching someone speak with enormous conviction about something they appear to have very little experience doing.

There is a difference between experiencing something and encountering information about it on a feed. For me, experience doesn't necessarily mean twenty years in an industry, an impressive title or a wall full of qualifications.

It means you did something.

You experimented, you observed what happened, you got a result, and you learned something from it.

A week into trying to build software, I already had legitimate things to say about what it felt like to build software with AI. Not because I had become a software engineer in seven days, but because I now had something I didn't have the week before:

evidence from my own experience.

That is increasingly how I think about thought leadership too.

I don't want a story invented because somebody needed a LinkedIn post on Tuesday.

I want to know:

• Did you see this happen?

• Did you try it?

• What happened?

• What did you notice that somebody outside the work might miss?

• What did the result tell you?

• What changed your mind?

Thought leadership should be experience-first.

The thought should come from somewhere in this thing we call reality.

And perhaps that gives us a much more useful threshold for contributing publicly.

You don't need authority over an entire subject to talk about it.

You need something real underneath what you're saying.

A conversation in which only the most knowledgeable person in the room is allowed to speak isn't much of a conversation at all.

It must be boring as hell, in fact.

And expertise was never supposed to mean having the final word.

Sometimes it simply means having enough experience to add something worth hearing.

Being seen also means being judged

There is another reason smart people stay quiet that has very little to do with whether they have something worth saying.

Being seen means being available to be judged.

I see this constantly in my work with experts.

Some don't want to be on camera. Some don't want their lives turned into content. Some have spent years building serious careers and feel uncomfortable with the idea that they should suddenly start behaving like influencers.

And some simply don't like the feeling of putting something they believe in out into the public and waiting to see what everybody else thinks about it.

I understand that too.

Someone disagreed with something I posted recently.

My first reaction wasn't some enlightened appreciation for intellectual debate.

It felt bad.

Then I thought about their argument, responded to it, and decided I still disagreed.

Nothing catastrophic happened.

Happy to report I didn't die from it either.

My thinking had simply encountered somebody else's thinking.

I suspect my philosophy background has made me unusually comfortable with that part.

You can make an argument without believing yours is the only possible interpretation.

Someone can challenge your position without the disagreement becoming a referendum on your intelligence. You can listen, reconsider, defend your reasoning, change your mind, or simply conclude that the two of you see the issue differently.

But none of that can happen to an idea you never share.

And that is the uncomfortable bargain visibility asks us to make.

If you want your thinking to be available for recognition, you also have to make it available for disagreement.

There is no version of being publicly known for your ideas in which you retain complete control over how every person receives them.

• Someone may misunderstand you.

• Someone may disagree.

• Someone may think the idea is obvious.

• Someone may know more than you do.

• Someone may point out something you hadn't considered.

And they may even be right.

That doesn't automatically make publishing the thought a mistake.

Sometimes it gives you the next thought.

This is also why I don't think the answer is to tell reluctant experts to simply become louder, more exposed or more comfortable performing themselves online.

Visibility does not require turning your entire life into content.

It doesn't require a camera or an entire production team.

It doesn't require an opinion on everything.

And it certainly doesn't require becoming a different kind of person in public.

It requires deciding which parts of your thinking deserve to become visible, and accepting that once they do, other people get to think about them too.

That feels like a much more useful definition of visibility to me.

Not:

Look at me.

But:

Here is something I've seen. Let's think about it.

Invisible expertise cannot create visible opportunity

I see another version of this every time I work on someone’s CV or LinkedIn profile.

I’ll ask a client what they have done. They’ll tell me.

And somewhere in the middle of what they consider a perfectly ordinary description of their job, I’ll stop them.

Wait.

• You did what?

• You built that?

• You managed that?

• You changed that?

• How many people?

• How much money?

• What happened because of it?

The information was always there.

The person just didn't recognise it as remarkable because, to them, it was simply the work.

This happens constantly.

People who have spent years becoming exceptionally good at something are often the worst people to judge which parts of their experience other people will find valuable.

Familiarity makes expertise feel ordinary.

• You have solved that problem twelve times, so you forget that somebody else has never solved it once.

• You know how to make that decision almost instinctively, so you stop noticing that there are ten years of experience underneath your instinct.

• You explain something in five minutes and assume it must be obvious because it is obvious to you.

From inside your own expertise, it can all feel surprisingly unremarkable.

From the outside, it may be the exact reason someone wants to hire you, invite you into a room, ask for your advice, recommend you, collaborate with you, or listen when you speak.

But there is a problem.

Other people cannot recognise expertise they cannot see.

Sometimes I hear a version of this argument:

The right people already know what I do.

And perhaps they do.

• Your colleagues know.

• Your clients know.

• The people who have worked closely with you know.

• Your friends may know.

The people who have already sat in the room with you and watched you solve the problem know.

But what about the people who don't know you yet?

• The future client searching for someone with exactly your experience.

• The person putting together a panel who has never been in one of your meetings.

• The hiring manager outside your existing network.

• The journalist looking for someone who understands your subject.

• The collaborator who would immediately recognise the value of your thinking if they ever encountered it.

• The person who knows someone who needs exactly what you do.

The people who already know you are not the visibility problem.

The opportunity in visibility is allowing your expertise to travel beyond the people who have already experienced it firsthand...otherwise your reputation has a limit.

It travels through introductions, conversations, meetings and word of mouth. All valuable. But all dependent on somebody already knowing enough about you to carry your name into the next room in the right way.

Publishing gives your thinking another way to travel.

Someone who has never met you can encounter an idea, recognise the quality of your thinking and understand something about what you know before anyone makes an introduction.

That is a fundamentally different kind of visibility.

They cannot associate you with an idea they have never heard you articulate. They cannot know that you understand a problem you have never spoken about. They cannot reference thinking that exists only inside your head. And they cannot offer you an opportunity based on information they do not have.

This is why I have become increasingly interested in visibility as something other than attention.

Attention asks: How many people saw me?

Visibility asks: Can the right people see what I know, how I think and what I can do?

Those are very different ambitions.

Making the latter happen deliberately requires more than just posting. It requires a visibility strategy.

The point isn't to become known by everybody.

The point is to be known by the right people.

It is to make enough of your thinking visible that the people who need what you know have a chance of recognising it.

Opportunities rarely arrive with a questionnaire asking you to list every useful thing you've ever learned.

People work with the evidence available to them.

• Your conversations.

• Your work.

• Your reputation.

• Your writing.

• The ideas attached to your name.

• The things they have watched you do.

Which means there can be a very real gap between how qualified you are and how qualified the world knows you to be.

Publishing does not create the expertise.

It creates evidence of the expertise.

And without that evidence, you can spend your entire career becoming more qualified while missing opportunities because nobody knows that you know what you know.

Share unfinished thinking. Don’t share unexamined thinking.

None of this means I think every thought needs to become a post.

I don't.

I think you can speak while you're learning.

You can speak while you're experimenting.

You can speak about something that failed.

You can share an idea before you have reached the end of it.

What matters to me is not whether the thought is finished.

It is whether the thought has been examined.

There is a difference between: This is what I’m learning.

and: This is what I’m feeling right now, so it must be true.

There is a difference between documenting an observation while your understanding is still developing and turning every passing reaction into a public position.

I have a test I use for my own publishing:

Would future me be embarrassed by this?

Not embarrassed because I might eventually learn something that changes my mind. I expect that to happen.

I mean embarrassed because I published something I hadn't actually thought through.

Because I was angry that afternoon, something was getting attention, everyone else seemed to have an opinion, or the sentence sounded good before I had asked whether I actually believed it.

I studied philosophy, so perhaps I think about publishing on an unnecessarily long timeline.

Some of the ideas we still discuss today were written hundreds or thousands of years ago.

I don't expect my LinkedIn posts to be studied in the year 4026.

But I like the principle underneath that kind of intellectual longevity.

Is there something durable underneath what I'm saying?

Would I recognise the reasoning behind this thought years from now, even if experience eventually changes my conclusion? Is it grounded in something I have seen, tested, learned or genuinely thought about?

Would I be comfortable with this remaining attached to my name after today's emotion, conversation or algorithm has disappeared?

That is a very different standard from waiting until your thinking is complete.

Complete thinking may not exist.

Examined thinking always does.

And changing your mind later does not invalidate the thinking you shared earlier.

Sometimes the most interesting thing about a body of work is being able to see where somebody started, what they encountered, and how their thinking changed because of it.

The goal isn't to leave behind a perfect record of always having been right.

The goal here is actually to leave behind an honest record of having thought.

So I don't think the choice is between waiting until you have the definitive answer and publishing every thought that passes through your head. There is a much more useful space between those extremes.

Share unfinished thinking...and... Don't share unexamined thinking.

Mine your life before manufacturing expertise

Something has changed in the way I create content recently.

I used to ask:

What should I post about?

Now I am much more likely to ask:

What happened today that made me think?

• What did a client say that surprised me?

• What did I try that didn't work?

• What did I find myself explaining to someone?

• What annoyed me enough to examine why?

• What happened in a meeting that confirmed something I had suspected for years?

• What did I change my mind about?

• What did I do for the fiftieth time that somebody doing it for the first time might find useful?

The difference seems small.

It isn't.

The first question (What should I post about?) sends you looking for content. The second one (What happened today that made me think?) sends you looking at your life.

And I increasingly think that is where the most interesting thought leadership comes from.

Your work is producing material all the time.

So are your conversations, mistakes, decisions, experiments, disagreements and observations.

The problem is that most of it doesn't arrive looking like or labelled: Important Idea.

It arrives as:

• That was strange.

• Why does this keep happening?

• That didn't work the way I expected.

• I've explained this three times this week.

• Everyone keeps saying this, but that isn't what I'm seeing.

• Oh. That's why that works.

Then we move on.

I have started thinking of this as mining.

The thinking often exists before the content does. Your job is to notice it.

This matters even more now that AI can produce plausible expertise on almost any subject in seconds. Give it a topic and it can generate the lessons, the frameworks, the five mistakes, the contrarian take and the polished story to introduce all of it.

That makes producing something that looks like thought leadership remarkably easy.

But looking like thought leadership and containing someone's thinking are not the same thing.

AI can help me interrogate an experience.

It can help me find the argument inside something I noticed.

It can challenge my reasoning, help me organise it, ask me better questions and help me articulate something I was struggling to articulate.

What I don't want it to do is manufacture the experience underneath the idea, because that is the part that makes the thought mine (pun very much intended!).

This is why I keep coming back to provenance.

Where did this thought come from?

• Did you see something?

• Did you try something?

• Did somebody ask you a question you couldn't stop thinking about?

• Did the data contradict what everybody in the room believed?

• Did ten years of doing the work teach you to notice something the rest of us keep missing?

• Did you fail?

• Did you change your mind?

There should be a trail back to something real.

And perhaps this is particularly useful for experts who think they don't have anything to post.

You do not need more ideas.

You just need to notice the ideas your life is already producing.

• The meeting you had this morning.

• The problem you solved last week.

• The mistake you've stopped making.

• The thing every new client misunderstands.

• The decision that takes you thirty seconds now because it took you ten years to learn how to make it.

What feels like an ordinary Tuesday to you may contain an extraordinary amount of expertise.

Mine that.

In an internet increasingly capable of manufacturing things that sound intelligent, lived experience gives a thought something much harder to manufacture: a human story.

Maybe eXPERTS learned the wrong lesson about visibility: WHY THEY HESITATE TO SHARE THEIR IDEAS PUBLICLY

I think we have accidentally taught people that they are not smart if they post online.

So it's no surprise that experts are hesitating to share their ideas publicly.

Or perhaps more precisely, we've taught them that serious people do the work.

Other people talk about doing the work.

I understand where that instinct comes from.

The internet has made expertise look cheap.

We have watched people turn every experience into a lesson five minutes after having it. We have watched ordinary observations dressed up as profound insights. We have watched people manufacture personal stories because the story makes the post perform better. We have watched confidence become almost indistinguishable from competence.

If you have spent years quietly becoming very good at something, I can understand looking at all of that and thinking: I don't want to be part of this.

So you stay out of it.

You do the work.

You let the work speak for itself.

There is something admirable about that. There is also something limiting about it.

Your work does not literally speak. People speak about your work.

They explain what they learned from it, give language to the patterns they have noticed, tell us what happened, challenge the way their industry has always done something, make their experience useful to people who weren't there to experience it with them.

And when the people with the deepest experience remove themselves from public conversation because public conversation sometimes feels shallow, something strange happens.

The conversation simply continues without them.

The people willing to speak become the people we hear; the people who "own" that conversation.

The ideas made visible become the ideas available to circulate.

The people willing to explain what they know become easier to associate with knowing it.

None of this means visibility proves expertise.

It doesn't.

Someone can publish every day and know very little.

Someone else can publish nothing and be exceptional at what they do.

But perhaps that is precisely the problem.

We have treated doing good work and making good thinking visible as though one somehow compromises the other.

It doesn't have to.

1. You can be serious about your work and talk about it.

2. You can have intellectual humility and still have an opinion.

3. You can be private and still make your thinking public.

4. You can dislike self-promotion and still believe an idea deserves to travel beyond the room where you first had it.

5. You can still be learning and have something to teach.

Maybe the smartest people I know don't need to become louder.

Maybe they don't need to become influencers at all.

Maybe they simply need to stop treating invisibility as evidence of seriousness.

Staying quiet does not make an idea more intelligent. It just makes the idea harder to find.

A different standard for having something to say

So perhaps we need a different standard for deciding when we are qualified to contribute online publicly and in a big way.

Not:

Do I know everything about this?

But:

Do I have enough experience to have a thought about it?

Not:

Can I defend this position forever?

But:

Have I thought carefully enough about why I believe it today?

Not:

Am I the most knowledgeable person who could speak about this?

But:

Is there something my experience allows me to add to the conversation?

And not:

Am I certain?

But perhaps:

Can I be clear about what I have seen, what I have learned and what I am still figuring out?

That feels like a much more honest relationship with expertise.

Expertise never has and never will have a finish line.

There will always be another book you haven't read. Another person who knows more. Another exception you haven't encountered. Another experience that changes the way you understand the ones that came before it.

If complete knowledge is the qualification for speaking, almost nobody qualifies.

But if the qualification is having enough experience to contribute something considered, useful and genuinely yours, many more people do.

Including, probably, some of the people who are currently saying the least.

I don't think we need more people pretending to be experts.

I think we need more people with real experience, allowing the rest of us to encounter their thinking.

Not because every thought deserves an audience, or that everyone needs a personal brand, or that visibility is inherently valuable. But because some ideas are worth spreading (to quote TED) beyond the person who had them.

And perhaps that is the expertise paradox:

The more you learn, the more clearly you can see how much you don't know. That awareness can make you quieter precisely when your experience has given you more to contribute.

The answer isn't to wait until the uncertainty disappears. Maybe it is to understand that the uncertainty was never evidence that you had nothing to say.

“I still have a lot to learn” and “I know something worth sharing” were never opposites.

_______________________

Key ideas: The Expertise Paradox · experience-first thought leadership · professional visibility · unfinished vs. unexamined thinking · visibility without self-promotion