CSE Roadmap

Common tier · about 3 hours · 12 parts

Part 9 of 12 · 2 min read

Mistakes that turn feedback against the product

Common mistakes, and what the example does not do.

Mistakes that turn feedback against the product

  • Reading thumbs as satisfaction.
  • Fine-tuning or prompt-tuning directly on raw feedback.
  • Ignoring non-responders.
  • Declaring a winner on few votes.
  • No trace id on feedback, so you cannot reproduce the failure.
  • Engagement as quality: longer sessions can mean the agent is failing.
  • Letting one loud category fill the eval set.
  • Storing feedback with personal data and no retention policy.

What the example does not do

About this example What the example does not do
  • No real feedback data; every rate is assumed.
  • Independent users and no segments; real feedback varies by user type, time and UI.
  • Inverse-propensity weighting assumes known rates, which is the hard part in practice.
  • The agreeableness trade-off is built in, so the 59 to 66 percent figure shows the mechanism, not a measured effect.
  • No actual prompt-tuning or learning algorithm; only selection among fixed variants.
  • Optional real experiment: take a real product's thumbs data, have two experts label 200 random and 200 downvoted traces, and measure the precision and recall of downvotes against the expert labels.

Check yourself

Only 2.4 percent of users leave feedback and the raw thumbs-up share is 50 percent, but true satisfaction is 80 percent. Why the gap?

Show answer

Unhappy users give feedback more often, so the raw share is biased. Re-weighting by the inverse of the response rate corrects it.

For the curious The winner of ten prompts looks better than it is

Choosing the best of 10 prompts by thumbs on 100 votes each, the winner looked like 78.1 percent but was truly 72.6 percent. With 1,000 votes each the gap was 75.0 against 74.2. Selecting on noisy data overstates the gain, and selecting on thumbs alone can pick agreeable answers over correct ones. All rates here are assumed.

What you will use daily at work

Practice What it looks like
Log feedback with trace id and version A signal then links to the run and the rollout arm.
Sample for expert labels Include random non-flagged traces to estimate recall.
Cap each complaint category One noisy type should not fill the eval set.
Test for sycophancy Include cases where the right answer disagrees with the user.