Building for the user you imagined

A founder finishes a product and notices that the people they had in mind never showed up. The people who did show up wanted something a little different and weren't patient about it. Half the early-stage product-market fit story is this gap — between who the team was building for and who was in the room.

The named pitfalls (building in a vacuum, picking the wrong segment, stuffing in features, skipping validation) are all the same pitfall in different clothes. Each one is a way of substituting an imagined user for a real one.

The four pitfalls are one pitfall

Building in a vacuum is building from your own assumptions about what users need. Picking the wrong market segment is picking the segment you understand instead of the segment that wants the thing. Feature stuffing is solving every problem your imagined user might have, instead of the one a real user has. Skipping validation is choosing not to find out.

Every named failure mode in the standard product-market-fit literature comes down to the same substitution. The user you have in your head isn't the user in front of you. The fit is between your product and them, not between your product and your idea of them.

The imagined user is always more reasonable

The user in your head listens to your pitch. They patiently work through onboarding. They understand the unique angle. They forgive the rough edges because they get what you're doing. They never object to the price.

The user in front of you does none of these things. They click away when something looks confusing. They don't read your value proposition; they look at the field labels and decide. They want refunds. They use your product in ways you didn't intend, and they get angry when the unintended way breaks.

The work of finding fit is mostly the work of staying close enough to the real user that they overrule the imagined one. The gap between the two is where every named pitfall lives.

Shortening the distance

The fix is the same for all four pitfalls. Make a real user impossible to ignore.

Five conversations a week, with real users, recorded and re-read. One new signup watched all the way through onboarding, in the same week they did it. Support tickets read by the founder, not just the support lead. A standing weekly slot where someone shows the team a user who did a thing nobody expected — and the team has to decide what that means.

None of this is a process. It's a measurement of distance. If the team can go a week without anyone watching a real user try the product, the imagined user has taken over. The pitfalls follow.

Most pivots are re-picks

Famous startup pivots are usually told as product stories — the team noticed the market was wrong, changed the product, found their fit. Slack from a game studio's internal chat. Segment from a classroom analytics tool. Instagram from a check-in app.

Read carefully, these aren't pivots in the dramatic sense. The teams kept doing roughly the same kind of work. What changed was who they were paying attention to. Slack started listening to the small handful of teams using its internal chat instead of the players who never showed. Segment listened to developers complaining about analytics integration instead of the students who weren't using the classroom product.

The change that mattered was a re-picking of the cohort. The product change followed.

Most product-market fit pivots that look heroic in retrospect are quieter than that. The founders just stopped pretending the original user was going to arrive, looked at the user already in front of them, and built for them.

The pitfall is always the same shape. So is the fix.