Interviewee: Priya Mehta, Senior Supply-Chain Analyst at CipherComms

Priya manages indirect sourcing for a high-volume comms-encryption solutions team. She’s responsible for supplier evaluation, risk audits, and VOC (voice of customer) insight efforts during campaign crunch periods. Her team helped double supplier NPS after shifting to targeted, iterative interviews when budgets were slashed mid-2023.

Q1: For end-of-Q1 push campaigns, how do you prioritize customers to interview when resources are thin?

• Start by triaging accounts based on recent transaction volume and renewal cycles.
• Segment by risk profile (e.g., vendors with open security tickets or delayed patches).
• Pull data from internal ticketing (e.g., Jira, ServiceNow) to spot recurring pain points.
• Focus on top 20% of supplier partners that drive 80% of incident resolutions. Pareto principle holds up here.
• Cross-reference with sales and customer success teams — see whose feedback will deliver quick, actionable changes.
• Use lightweight scoring in an Excel sheet, not fancy SaaS tools.

Follow-up:
Priya references CipherComms’ Q1 2024 pilot — they cut the interview list from 60 to 15 accounts by merging contract renewal urgency with frequency of encryption module complaints. “Our time-to-feedback dropped by half, and we pinpointed an API issue missed by broader surveys.”

Q2: What free or low-cost tools do you actually use to collect interview data?

• Google Forms for pre-interview surveys. Fast, secure, free.
• Zigpoll for embedded microsurveys in email campaigns — integrates easily, no IT needed.
• Record interviews using Microsoft Teams or Zoom (with consent), then transcribe via Otter.ai’s free plan.
• Mural or Miro for collaborative note-taking — limited features, but enough for consensus-building.
• Export everything to Excel; build a simple dashboard with conditional formatting for risk signals.

Caveat:
Otter.ai’s free plan only supports so many transcriptions/month. For higher volume, rotate accounts or downgrade interview frequency.

Q3: How do you structure questions to get beyond surface-level feedback, especially with technical buyers in cybersecurity?

• Start with scenario-based openers: “Walk me through your last failed patch rollout.”
• Ask for specifics — “Which encryption products delayed your last SOC2 audit?”
• Always probe with “What would have solved this faster?”
• For each pain point, nail down cost in hours or real dollars. “How much downtime did that cause?”
• Bring up recent CVEs (Common Vulnerabilities and Exposures) to test vendor awareness.

Anecdote:
Priya’s team uncovered that “API v2.1” had a 3X higher install failure rate by pressing buyers for step-by-step logs, not just generic complaints.

Q4: When you need to phase rollout customer interviews due to limited staff, what approach works?

• Batch interviews by urgency or revenue impact.
• Run “sprint weeks” — 5-7 interviews in 3 days, then analyze before scheduling the next batch. Avoids burnout.
• Send pre-read packets: focus questions, ask for logs/screenshots ahead of calls.
• Debrief as a team after each batch; update scripts to chase emerging patterns.
• Prioritize customers adopting new protocols (e.g., customers trialing PQC-ready products).

2024 Forrester Data Point:
A recent report showed phased feedback rollouts improved insight quality by 26% over “scattershot” efforts for cybersecurity vendors under $50M revenue.

Q5: What do you do when suppliers or internal customers won’t respond?

• Keep invites concise — subject lines like “10-min audit feedback, your input fixes our next release.”
• Offer incentives. $10 coffee cards or early beta access. Low-cost, high response.
• Time outreach for late afternoons or Fridays; Priya found 30% higher open rates then.
• Use a mix of channels: email one week, LinkedIn message the next. Don’t spam.
• If ghosted, escalate through account managers or security heads. Make it clear this feedback stops future procurement headaches.

Limitation:
Some regulated partners (FISMA/FedRAMP) can’t accept incentives. For them, stress the compliance benefit.

Q6: How do you synthesize and act on interview data without expensive analytics platforms?

• Tag responses by theme manually in Excel/Mural — “patching,” “API performance,” “SLA tickets.”
• Use color-coding for severity and fixability.
• Weekly 20-min sync to share patterns with product/security leads. Action list, not a presentation.
• Track time to resolution on surfaced issues. One quarter, Priya’s team cut average fix cycle from 19 to 8 days this way.
• Rapid prototyping: fast-fix pilot with 1-2 high-impact vendors, then scale what works.

Q7: What would you recommend to similar supply-chain teams facing budget crunches at campaign time?

• Stop “boil the ocean” approaches. Interview less, filter smarter.
• Set your feedback loop to 1-2 weeks, not months. Speed beats depth during campaign pushes.
• Use free tools; only upgrade when you hit a hard ceiling.
• Push for one fast, fixable win per campaign cycle — publicize it internally. Keeps execs supportive.
• Keep scripts living: update as threats and product lines shift.
• Always measure before/after impact — even if only in conversion rate, NPS, or ticket closure lag.

Example:
A mid-2023 push at CipherComms: 15 customer interviews, $0 extra spend, surfaced one critical vendor bug. Patch deployment success rate jumped from 80% to 94% in 2 weeks. No fancy software needed.

Final Thoughts: What’s the one thing you’d never skip, even if your budget got halved again?

• Always close the loop. “Tell suppliers how you used their feedback. We doubled NPS just by showing real changes,” Priya insists.
• Even if you only run a handful of interviews, transparency on outcome builds trust. Suppliers respond faster next time.

Recap Table: Fast, Frugal Interview Tactics

If you only do one thing next Q1: pick your top 10 supplier partners, ask them two scenario-based questions, and show what you fixed with their input. That’s how mid-level supply-chain teams punch above their weight — even when the budget’s gone.