Conducting Enterprise User Research at Global Conferences

Controlled research environments produce clean data but miss the messy reality of how practitioners actually work. Conference settings capture practitioners in a state of active professional reflection, making them ideal research partners for understanding real-world challenges and aspirations.

VMware's product teams had limited direct exposure to the global design and enterprise IT practitioner communities their tools served. Decisions were being made based on internal assumptions and infrequent customer visits, not ongoing community engagement.

Most enterprise companies use conferences for marketing presence, not research. Transforming that presence into a mutual-value research channel — where practitioners receive mentorship and co-creation in exchange for their insights — was the core opportunity.

Every research activity was designed to deliver value within 30–45 minute windows, the realistic engagement window for conference attendees between sessions. Activities were high-signal, scaffolded, and participant-friendly: participants understood the purpose, felt respected, and left having gained something.

Participant recruitment began 6–8 weeks before each conference through community networks, LinkedIn outreach, and coordination with conference organizers. Scheduling was managed to avoid participant overlap with keynotes and high-demand sessions.

Facilitation guides were designed modularly (a 30-minute version, a 45-minute version, and a 60-minute version of each core activity) so sessions could flex in real time to participant availability without losing research integrity.

One-on-one sessions gave practitioners genuine value — feedback on their work, craft conversations, career perspective — while generating the kind of rich contextual signal that group sessions rarely surface. Because participants came for the conversation, not the research, their candor was unusually high.

Rather than asking about products directly, conversations were framed around practitioners' actual decisions: the tools they relied on, the workarounds they'd normalized, the gaps they'd stopped expecting anyone to fix — exactly the latent needs that structured research questions rarely reach.

Small-group co-creation sessions brought practitioners together to collaboratively define problems, sketch solutions, and react to early design concepts. The group dynamic amplified insight: practitioners challenged each other's assumptions and built on each other's ideas in ways one-on-one sessions never reach.

Workshop outputs (problem maps, opportunity frameworks, sketched concepts) were shared with participants after each session. This reinforced the mutual-value relationship and created advocates who carried VMware's design thinking back into their own organizations.

Research notes, photos, and artifacts were synthesized each evening during conferences, while observations were fresh. This prevented the insight decay that affects post-conference synthesis and allowed facilitation adjustments to be made the following morning.

Findings were integrated across events to track emerging patterns and identify geographic and community-specific variations in practitioner needs.

Research findings were delivered to product and design leadership as narrative readouts anchored in participant quotes, video clips (with permission), and co-creation artifacts.

Each readout included a "so what" section mapping findings to specific product and design decisions. Research influence was tracked over the following quarter to assess how findings shaped actual choices.