User Research in Enterprise B2B: A Practical Guide
User research works differently in enterprise. Users are busy, access is limited, and you're often learning from proxies. Here's what I've figured out.
Enterprise user research is hard mode. Your users are busy professionals. Sales teams gatekeep access. Customers aren't always the users. Everything takes longer.
But doing it right is even more important, because enterprise mistakes are expensive.
What's different in enterprise
1. Access is scarce: You can't just post on Twitter asking for feedback. Getting 15 minutes with an enterprise customer requires coordination with sales, CS, and sometimes legal.
2. Users ≠ Buyers: The person who chose your software might not be the one using it daily. Research both—they have different needs.
3. Context is complex: An HR manager at a 50-person startup uses software differently than one at a 5000-person enterprise. Sample diversity matters.
4. Bias is everywhere: Customers who agree to research calls are often the happiest ones. Unhappy customers are too frustrated or have already churned.
Practical tactics that work
Piggyback on existing touchpoints: CS calls, sales demos, support tickets, QBRs. These are happening anyway—ask if you can listen in or add questions.
Build a research panel: Identify 10-15 engaged customers willing to give regular feedback. Incentivize them (early access, executive attention, swag). This is your ongoing research group.
Study the shadows: Look at support tickets for what's broken. Watch session recordings. Analyze where users drop off. Sometimes indirect data beats direct conversation.
Create low-friction feedback loops: In-app surveys (1-2 questions max), post-task ratings, NPS with follow-up. Make giving feedback effortless.
Schedule research weeks: Block out one week per month for focused research—interviews, observations, synthesis. This prevents research becoming perpetual "nice to have."
Synthesizing what you learn
Enterprise research generates messy data. My synthesis approach:
1. Take verbatim notes during calls (don't summarize on the fly) 2. Tag recurring themes within 24 hours while memory is fresh 3. Monthly: cluster themes into "problems worth solving" vs "feature requests" 4. Quarterly: share a research report with broader team
The goal isn't to research constantly—it's to research regularly enough that customer insight is a living thing, not a quarterly report.