First customer feedback: what to record before rebuilding the product

First customer feedback should be recorded as evidence about the buyer, the job, the blocker, and the promised outcome before the product is rebuilt.

Early feedback feels urgent because every customer seems important. A founder may hear one complaint and immediately add a feature, change pricing, rewrite onboarding, or pivot the landing page. That may be right, but the first step should be a structured note that preserves what actually happened.

Record four fields. First, who was the customer and what context did they bring? Second, what job were they trying to complete? Third, where did they get blocked: before signup, during setup, at import, at the first output, at payment, or after sharing? Fourth, what wording did they use to describe the missing value? The customer’s words can reveal a positioning problem that analytics alone hides.

Then separate request from root cause. “Add Slack integration” may mean the product needs collaboration. It may also mean the user wants a notification, audit trail, approval step, or easier handoff. Building the literal request too quickly can solve the wrong job.

A good feedback note ends with a decision: ship a small fix, ask two more similar users, update onboarding, clarify pricing, or reject the request for now. The note keeps the founder from turning one loud signal into an unexamined roadmap.

First customer feedback: what to record before rebuilding the product

// COMMENTS

ON THIS PAGE