What Good Problem Interviews Feel Like (Customer Side, B2B)

Most posts about B2B SaaS problem interviews are written from the founder's side. Here is the other side. What does it feel like for the operator being interviewed?

It Feels Like Being Listened To

B2B operators rarely get asked about their actual workflow. They get asked about KPIs, status reports, and budget. A founder who asks "walk me through what happens when X breaks" is asking something nobody else is asking. That is rare and felt as respectful.

It Does Not Feel Like a Sales Call

B2B operators get pitched constantly. They have allergies. The moment they sense pitch incoming, every answer becomes guarded. A good interview never demos and never describes the product. The customer leaves thinking "huh, that was an interesting research call" not "huh, what were they trying to sell me."

It Feels Specific to Their World

Generic interviews bore B2B operators. "Tell me about your team" gets a stock answer. Good interviews ask about specific incidents - last week's migration, last month's campaign, the contract that almost slipped. Specifics jolt operators out of stock-answer mode.

It Asks About the Other Roles

B2B-specific. The operator feels heard not just for their own pain but for the system around them. "How does your manager think about this?" "What does your security team usually want?" The operator has thoughts and is rarely asked.

It Feels Mutual

The founder reacts. Says "huh, that is interesting." Shares an observation. Thanks the operator for an insight that was actually insightful. The operator comes away feeling like they helped someone understand their world, not like they were a research subject.

It Tolerates Honest Criticism of Vendors

B2B operators have strong opinions about the tools they use. A good interview lets them vent. "What is annoying about your current tool?" They will tell you, often with detail. The venting is gold for product positioning.

Why This Affects Your Data

Operators who enjoy the call tell you more. They share the embarrassing tool stack. They name the colleague whose tickets they cover. They describe the procurement workaround. The experience design of the interview is also the data quality.