How do you translate field-study findings into user stories and acceptance criteria?

WHAT THIS TESTS: This question tests whether you can bridge the gap between messy, qualitative field data and precise engineering execution. Interviewers want to see that you understand user stories as a collaboration tool rather than a specification document, and that you know how to preserve empirical evidence from user research while making it actionable for developers.

A GOOD ANSWER COVERS: First, synthesize raw field observations into personas based on firsthand knowledge, capturing the goals and problems you observed rather than inventing them. Second, map those validated pain points to epics, which are big sketchy stories that act as headlines for broader themes from the research. Third, break epics into concise user stories using the As-persona-I-want-so-that template, keeping them simple and in active voice so the user goal remains explicit. Fourth, add acceptance criteria that operationalize the qualitative insight by translating observed behaviors into testable conditions. Fifth, embed this work in a conversation by co-creating stories with engineers during backlog refinement, because stories are meant to facilitate discussion, not to be handed off as finished requirements.

COMMON WRONG ANSWERS: A major red flag is treating raw interview quotes or field notes as backlog items without synthesis or persona context. Another is writing speculative stories based on beliefs rather than empirical data, which violates the principle that you should carry out user research first. Candidates also stumble when they present stories as formal specifications to be thrown over the wall to developers, ignoring the collaborative intent of the technique.

LIKELY FOLLOW-UPS: The interviewer might ask how you handle conflicting qualitative findings across user segments, or how you prioritize which epics to decompose first when research surfaces multiple pain points. They may also probe how you validate that the acceptance criteria actually capture the original user intent once the feature is built.

ONE CONCRETE EXAMPLE: Suppose a field study reveals that warehouse workers waste ten minutes per shift hunting for misplaced scanners. You synthesize a persona named Warehouse Wendy whose goal is to locate equipment fast. The epic is reduce equipment search time. This breaks into a story such as As Wendy I want to see the last known location of my scanner so that I can find it within thirty seconds. Acceptance criteria include the system records scanner location every five minutes and the location displays within three taps from the home screen.

Source: romanpichler.com