1 min lesson
Keep insight and recommendation separate
Talk this through in your own words: "A PM dislikes your proposed fix and starts arguing that the whole study is wrong. How does separating insight from recommendation protect your work?" Finish with the next move.
Step 1 of 2
Keep insight and recommendation separateone is durable, one is a bet
An insight is a durable truth about the user that stays true even if the team picks a different fix. A recommendation is your proposed action and reasonable people can disagree with it. Blur the two and you invite the whole insight to be dismissed when someone dislikes your proposed solution.
"Devs distrust Agent edits they can't see before they land."
True regardless of what we build. Survives a roadmap change.
"Add a diff-preview step before Agent applies changes."
One way to act on the insight. Debatable, swappable, yours to defend.
Last, lead with the pattern and let one vivid moment carry it home. Quantify the pattern so it's countable, then play the ten-second clip of a senior engineer muttering "wait, what did it just change?" The number proves it's real; the clip makes the team feel it.
One articulate participant is not a trend and a panel will catch you generalizing from a single quote. Say how many people showed the behavior before you show the clip. "This came up with 6 of 9" plus a clip lands; a clip alone reads as cherry-picking.