Product design question

You have two weeks on-site with a state agency that has no clear requirements document. How would you structure discovery with frontline staff, managers, IT, and agency leadership to identify the first workflow where Claude should sit in the production path, and what evidence would you require before committing engineering resources?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests discovery skills in an ambiguous public-sector environment, finding the highest-value workflow without a requirements document.

Spend the first days shadowing frontline staff doing the actual work, not just interviewing managers about what they think happens.
Interview IT separately to understand data access, legacy systems, and security constraints that will gate any solution.
Talk to agency leadership last, once you have concrete workflow evidence, to validate priorities and political feasibility.
Look for a workflow that's high-volume, evaluable, and where an error is recoverable, rather than a high-stakes edge case.
Require evidence before committing engineering time, such as hours spent per task today and a willing pilot team.

Prioritizes frontline shadowing over leadership interviews, since stated priorities and daily pain often diverge.
Picks a starter workflow deliberately low-stakes and high-volume, for example document triage rather than a benefits eligibility decision.
Names a concrete evidence threshold, like at least two hours a day spent on the task today, as an illustrative bar.
Plans for IT and security constraints upfront instead of discovering them after committing engineering time.

Starting with the highest-visibility, highest-stakes workflow to impress leadership, which is also the riskiest to launch.
Skipping frontline staff and designing based only on what managers say happens.

Chapters of the AI PM course that teach what this question tests.