Day 20 on AffiSpark.
Yesterday I wrote that invisible progress only compounds when you make it legible.
A comment pushed that idea another step.
Writing is not just how you record the insight.
It is how you test whether the insight is actually real.
That matters because in my head, almost everything sounds smarter than it is.
“Users are confused.”
“Onboarding needs work.”
“Conversion is weak.”
Those feel like insights right up until I try to write them as a sentence precise enough to guide the next move.
That is when the weakness shows up.
Because once I try to put the thought into words, one of two things usually happens:
Either the sentence sharpens
Or I realize I do not understand the problem as well as I thought I did.
I think that is useful.
If the sentence is fuzzy, the thinking probably still is too.
For AffiSpark, some of the most useful lines lately have been things like:
setup friction is not proof friction
paid entry is not blind entry
a metric that describes the business is not always a metric that steers the product
Those sentences mattered not just because they were written down somewhere.
They mattered because they survived being written clearly.
They became usable.
They could shape copy.
They could shape onboarding.
They could shape what I measured.
They could shape what I stopped building.
That is why I think founders underrate writing.
We often treat it like documentation after the real work is done.
A lot of the time, writing is the real work.
It is where half-formed beliefs either become decisions or collapse.
And if they collapse there, that is good.
Much cheaper than letting vague thinking turn into a roadmap.
So I am trying to use writing differently now.
Not just:
how do I save the insight?
But:
can this insight survive being written as a clear distinction that narrows the next move?
If it cannot, I probably do not understand it well enough yet.
That has been a more useful standard than “this feels true.”
My current rule is simple:
if I cannot write the lesson as a crisp sentence, I should not trust myself to build on it yet.
Curious how others think about this:
what idea in your product only became real once you tried to write it clearly?