Too Perfect, Too Fragile
Share at 60% Readiness
I was writing many notes, but not publishing many essays.
The problem was simple: I still treated publishing as if it required a higher bar than it should.
I had already lowered the bar for capture. I had not lowered it for publishing.
A while ago, I thought the biggest problem in writing was starting.
So I tried to lower the barrier. Capture first. Make it less heavy.
It made expression easier. But writing was still hard.
Writing is reduction. It is convergence.
It is the painful work of turning a cloud into a line.
Now I think writing is one kind of difficulty, and publishing is another.
Writing is hard because thought must be shaped.
Publishing is hard because once the thought leaves my hands, it meets reality.
It meets readers.
It meets misunderstanding.
It meets disagreement.
It meets the world.
Writing shapes the idea. Publishing tests it. And that test is uncomfortable.
It is much easier to stay inside private refinement, where the piece still belongs only to me.
Keep improving. Keep making the piece smoother, tighter, more complete.
But that safety can be deceptive.
Sometimes what feels unfinished is actually alive. And what feels perfect is already brittle.
That is what I have been slowly realizing.
Something shared at 60% readiness is different.
Formed enough to be real, unfinished enough to still change
I often tell engineers not to wait until an RFC feels fully complete before sharing it.
Around 60–70% readiness is usually enough.
Not because quality does not matter, but because waiting too long often closes the document.
The shape hardens. The author is no longer inviting contact, only approval.
Writing works in a similar way.
Not because publishing is the same as asking for outside permission in order to exist.
But the timing logic is similar.
There is a moment when an idea is not finished, but ready.
The thought already has a real shape.
The piece knows what it is trying to say.
This is the harder judgment.
Not fully done. Not unquestionably right. Not polished into self-protection.
Just ready enough.
Waiting for 100% is not rigor. It is latency.
“Share at 60% readiness” is not a case for lower standards.
Some thoughts do not become clearer before they are shared.
They become clearer because they are shared.
That is why 60% is sometimes the right moment to publish.