How does continuous discovery change the researcher's role with engineering?

What's really being asked

This question tests whether you view UX research as a shared team capability rather than a centralized service. In continuous discovery, the product trio of product manager, designer, and engineer collaborates weekly on customer interviews and assumption testing. The interviewer wants to know if you understand that the researcher shifts from being the person who runs all studies to the coach who builds the trio's discovery skills. They are looking for operational specifics on how you would safely and sustainably get engineers talking directly to customers without compromising research quality.

The full answer

A good answer hits four things in order. First, role redefinition: the researcher moves from study owner to facilitator and coach, ensuring the trio uses an opportunity solution tree to visualize outcomes, opportunities, and solutions together. Second, scaffolding participation: you pair engineers with experienced interviewers, start with shadowing, then co-leading, then solo leading with structured debriefs. Third, lowering activation energy: you create lightweight rituals like weekly interview rotations where each trio member talks to at least one customer per week, and you prep concise discussion guides focused on past behavior rather than hypotheticals. Fourth, assumption testing: you teach engineers to design and run small experiments or prototype tests so they see discovery as engineering work, not extra work.

The mistakes people make

The biggest red flag is saying engineers are too busy or too blunt for customer conversations so the researcher should synthesize findings and hand off reports. Another red flag is suggesting discovery is only for product managers and designers while engineers wait for requirements. A third error is proposing heavy research training programs before anyone talks to a customer; continuous discovery starts immediately with coaching in the field, not classroom certification.

What usually comes next

Interviewers often ask how you would handle an engineer who dominates interviews with solution language, how you measure the health of continuous discovery on a team, or what you do when leadership blocks engineers from customer contact. They may also ask how this model changes headcount planning for research.

A concrete example

At a B2B SaaS company, a researcher stopped owning all user interviews and instead set up a trio rotation where the engineer shadowed two calls, co-led two calls with a backup question set, then led one call solo while the researcher took notes. After each call, the trio spent ten minutes updating their opportunity solution tree with new opportunities. Within six weeks, the engineer was identifying upstream workflow constraints that the team had previously missed because they only saw support tickets, not live customer context.