2 min lesson
Show the decision tree
Give a practical answer to this: "Midway through your panel presentation, a senior researcher says your five-session usability plan is too small to be trustworthy. How do you handle it without losing the room?"
Step 1 of 2
Show the decision treeevery finding maps to an action
The strongest signal you can send is connecting findings to decisions before you've gathered the data. Walk the panel through what each plausible result would mean for the team. This proves the study is designed to drive a decision, not to generate a report nobody reads.
Build it this quarter
Use the verbatims to scope the v1
Findings double as launch narrative
Build for the one segment that hurts
Defer the broad version
Size it with a follow-up survey
Kill the feature, save the quarter
Redirect effort to the next bet
The “no” is a high-value finding
Collaboration is part of the score. When a researcher pushes back, don't defend reflexively. Steelman their point, fold it in if it's right and explain your reasoning if you disagree. “That's a fair risk and you're right that five sessions won't catch rare issues. For this decision I'd accept that, but if we were de-risking a launch I'd push the sample up. Where would you land?” Adapting live shows them what it's like to work with you.
Don't collapse the moment you're challenged and don't dig in on a point you can't support. Both fail the round. The panel is testing for intellectual humility paired with a real point of view, so change your mind for a good reason and hold your ground for a better one.