The product you build first is never the product you needed to build

The first version is never the answer.

You know this intellectually, you have read about it, and you have probably said it to someone else. Then you build anyway, in the shape you imagined, because building without knowing exactly what you are building toward feels irresponsible.

The first version is a better question; that is its actual function.

Protocol reminded me of this quickly. I had a clear mental model of how training software should work before I built anything: structured programs, assignment, compliance tracking. The model was logical, but it was also wrong in the ways that matter, which are the ways that only reveal themselves when the product meets the reality it is supposed to serve.

The rework was not a failure. The rework was the product telling me what it was actually for.

This happens at every scale. The founders who suffer most are not the ones who build the wrong first version. Everyone does. They are the ones who refuse to hear what the first version is telling them, then treat the original model as a plan instead of a hypothesis.

A hypothesis that fails is useful because it points you somewhere real.

A plan that fails is expensive, because you spend time defending it instead of listening to it.

The first version of anything is the most honest conversation you will have about what you are actually trying to build.

Build it, listen to it, and build the second thing.