Expert Q&A · No. 22 / 25
What should we send experts before the interview?
Last updated
Send a compact evidence pack that makes generic answers difficult. The following is a proposed desk workflow, not an established industry standard.
- One named buying decision: a tool purchase, agency pilot, renewal or corrective programme.
- The buyer’s product, target customer and legitimate competitive set.
- A small set of customer-derived questions, with inferred questions labelled separately.
- Saved answers showing a recommendation, an omission and an ambiguous case.
- Dated product facts for accuracy checks.
- A redacted proposal or dashboard export where procurement is the issue.
- A disclosure form covering relevant commercial relationships.
For each substantive claim, ask the expert to supply one supporting artifact, one limitation and one condition that would change their view.
What should the evidence record contain?
Use this proposed minimum record for the material discussed in an interview:
| Record | Required detail |
|---|---|
| Test identity | Prompt ID, exact wording, intent group and provenance. |
| Collection | Surface, access method, date, time zone, location settings and session conditions. |
| Result status | Completed answer, observed no-feature state, refusal, timeout or other failure. |
| Evidence | Saved answer, citation URLs and accessible source checks. |
| Scoring | Brand aliases, mention/citation/recommendation labels, reviewer and disputed cases. |
| Intervention | Changed asset, implementation date, owner and proposed mechanism. |
| Interpretation | What was observed, what is inferred and what remains unknown. |
A collection failure should remain distinguishable from a completed answer in which the brand was absent. Likewise, a successful observation with no recommendation should not disappear from a denominator simply because it is inconvenient.