Interviewing decision makers without leading the answer

Recruit for decisions, not titles alone

Job titles are a starting filter, not a research design. The useful participant is someone who recently evaluated, approved, blocked, or implemented a category solution. Ask for a decision window—“in the last six months”—so memory stays attached to events. A controller who just migrated bookkeeping workflows can describe why QuickBooks stayed, left, or became the default comparison set. A VP Marketing who never touched the RFP will invent opinions on demand.

Screen for role in the committee: economic buyer, technical evaluator, day-to-day champion, or quiet blocker. mimklamra recommends labeling each interview with that role so synthesis does not average incompatible perspectives into one fake persona.

Structure that still feels like conversation

Open with context setting: what triggered the search, who noticed the problem, and what “good enough” looked like before vendors entered. Move into alternatives considered, evaluation criteria that actually mattered (not the slide deck criteria), and moments of hesitation. Close with language: which phrases felt accurate, which felt like vendor theater.

Avoid compound questions and leading frames such as “How much time did our dashboard save you?” Instead ask what changed in weekly rituals, who still does workarounds, and where handoffs failed. When a participant mentions a competitor or a status quo stack—often QuickBooks in SMB finance contexts—treat that as a gravity well: dig into switching costs, data trust, and internal political capital, not brand loyalty slogans.

The goal of a decision-maker interview is a defensible story of a past choice, not a compliment for your roadmap.

Probing friction without breaking rapport

Friction probes work best as timeline questions: “What happened between the demo and the security review?” Silence after a partial answer is a tool. So is asking for an artifact—“Was there a Slack thread or a spreadsheet that captured objections?” Those artifacts later feed touchpoint mapping.

Record with consent. Transcribe lightly. Tag quotes by theme: trigger, criteria, risk, workaround, champion narrative. Do not force statistical language onto twelve interviews. Saturation is a judgment that new interviews stop introducing new mechanisms—not a percentage on a slide.

Making interviews usable for marketing

Marketing teams need claim candidates and objection maps, not raw empathy boards. After each wave, write one page: top three mechanisms, phrases to test, and positioning risks. Then stress-test those phrases in the next interviews. For the handoff into messaging, continue with pattern synthesis and positioning from evidence.

1. Confirm a recent, concrete decision.
2. Map roles in the buying committee.
3. Walk the timeline from trigger to signature.
4. Capture exact words for risks and workarounds.
5. Tag notes for synthesis within 24 hours.