In software development, misunderstanding user needs leads to wasted engineering effort and misaligned products. Yet conducting effective customer interviews remains an underdeveloped muscle in many tech teams. Adrian Howard’s recent guide reframes this critical discovery skill as a collaborative group activity—democratizing research and amplifying its impact.

Article illustration 1

Why Group Practice Transforms Research Outcomes

Solo interviews often surface fragmented insights, but Howard’s method leverages collective intelligence. Teams start by anchoring to a strategic research question (e.g., "How do data engineers troubleshoot pipeline failures?" rather than "Do they want feature X?"). Through facilitated brainstorming in shared editors like Google Docs, members generate diverse questions before grouping them thematically. This process naturally evolves specific queries into open-ended story prompts: "Tell me about your last pipeline debugging experience."

The Rehearsal Imperative

Before facing real users, teams rotate roles in mock interviews:
- Interviewers practice active listening and probing (e.g., "You mentioned X—can you elaborate on that challenge?")
- Observers track thematic coverage and note gaps
- Interviewees simulate user behaviors

Howard stresses that these dry runs refine questioning techniques and technical logistics (consent forms, recording setups). Crucially, they build observer skills: "Assign different observers to different topics," he advises, enabling comprehensive insight capture during actual sessions.

Beyond the Interview: Structural Advantages

Teams adopting this approach discover unexpected benefits:
1. Reduced Bias: Multiple observers cross-verify interpretations
2. Accelerated Alignment: Shared context replaces conflicting assumptions
3. Scalable Skills: Junior developers learn research fundamentals alongside seniors

As Howard notes: "The sneaky thing... is that it’s often better than solo efforts. More brains refine questions; more ears interpret stories."

For tech leaders, this framework offers more than interview efficiency—it fosters a culture where user voices directly inform sprint priorities and architecture decisions. While Howard defers to experts like Indi Young for deeper methodology, his tactical blueprint empowers teams to start today: Block dedicated time, iterate through practice, and transform customer conversations into competitive advantage.

Source: Adapted from Adrian Howard’s guide on group user interviewing practice (adrianhoward.com).