Your Mistakes Deserve Better PR
You're in a design review. Someone suggests caching the config lookup instead of hitting the database on every request. The room nods. The tech lead says good catch. It goes into the plan with their name on it.
And you're sitting there thinking: I knew that. I've known that for two years. I just didn't think it was worth saying.
If that has happened to you more than once, this post is for you.
The curse of knowledge
There's a name for what stopped you. Economists Colin Camerer, George Loewenstein and Martin Weber called it the curse of knowledge in 1989. Once you know something, you can't remember what it was like not to know it. So you assume everyone else knows it too.
The clearest demonstration came a year later. Elizabeth Newton, a graduate student at Stanford, split people into tappers and listeners. Tappers picked a well-known song like "Happy Birthday" and tapped its rhythm on a table. Listeners had to guess the song. Before starting, tappers predicted listeners would get about half of them right. Listeners got 3 out of 120. That's 2.5%.
The tappers could hear the melody in their heads. The listeners heard knocking.
That's you in the meeting. The idea feels obvious because you're hearing the whole song. Nobody else is. The thing you skipped as too basic was new to half the room.
Developers have this bad. The shell alias you use fifty times a day. The way you structure retries. The reason you stopped using a certain library. You never write it up because everyone knows this already. They don't.
The room remembers who speaks
Groups don't pick leaders by competence. They pick whoever talks.
Psychologists call it the babble hypothesis. The idea goes back to the 1940s, and a 2020 study in The Leadership Quarterly put it to a proper test. Researchers put people into small groups, gave them tasks, and measured who emerged as the leader. The strongest predictor was speaking time. It held up even after they accounted for personality and intelligence.
So the person you've quietly filed as "not that sharp" is winning on airtime. They say the half-formed thing in standup. They post the rough idea in Slack. They volunteer to present. People remember them.
You can be annoyed about that. I was, for a while. Or you can notice that it's a rule anyone can use, including you.
Shipping compounds
This is the part I missed for years. When that person puts out mediocre work, something happens next. People respond. Someone points out the flaw. They fix it. They try again.
Do that for a year and they really are better. They ran a hundred feedback loops while you ran none.
Meanwhile your idea is on its hundredth private review. You're testing it against every objection you can imagine, which is a small fraction of the objections real people would raise and none of the improvements they'd suggest.
Every engineer knows this from code. A PR that sits on your branch for three weeks gets no review. A small, slightly ugly PR opened on day one gets five comments by lunch and merges by Thursday. Ideas work the same way. Feedback only reaches things that exist outside your head.
It's fear
Most of this comes down to fear.
If people think you're smart, you have something to lose. Every time you speak, you risk sounding less smart than they assumed. So you set the bar impossibly high: if I say something, it has to be brilliant. Almost nothing clears that bar, so you say almost nothing.
The confident average person doesn't carry that weight. Nobody expects much from them, so being wrong costs them very little. That freedom is their whole edge.
The pratfall effect
Your reputation is much harder to damage than you think.
In 1966, Elliot Aronson and his colleagues played people tape recordings of a quiz contestant. In one version the contestant was excellent and answered almost every question right. In another he was mediocre. In some versions, at the end, you hear him knock a cup of coffee all over his new suit.
People liked the excellent contestant more after the spill. They liked the mediocre one less.
Aronson called it the pratfall effect. When someone is clearly competent, a mistake makes them look human. The audience has already seen what they can do, and one slip doesn't erase it.
So the fear has it backwards. If you're good, a public mistake will probably help you. You've been guarding a reputation that was never at risk.
What to do with this
Say the obvious thing. If it's in your head during the meeting, it's probably worth saying. Worst case, someone says "yes, we already do that," and you've shown you understand the system.
Publish the rough version. The blog post you've been sitting on for six months is good enough. Write it, ship it, and fix it when someone corrects you. A correction in the comments means someone read it, and it makes the post better.
Open the PR before it feels finished. Ask for early review on the design doc. Share the half-built prototype.
And when the feedback comes, treat it as the point. Feedback is how you get better. It doesn't mean you failed.
Your idea is probably good enough
Most of the people getting ahead of you got comfortable being seen while they were still figuring things out.
You can do that too. Your idea is probably good enough already. It needs to be out where people can see it, poke at it and make it better.
So give your mistakes better PR. Let people see a few of them.