Strategy question
A law firm is enthusiastic about Harvey but hesitant to deploy because of privacy, governance, and reliability concerns. How would you scope the initial deployment, sequence risk-reduction steps, and make tradeoffs between speed, trust, and workflow ambition so the engagement keeps moving?
- Harvey
- Strategy
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests ability to sequence a trust sensitive enterprise deployment, balancing legal industry risk aversion against momentum and workflow ambition.
How to approach it
- Identify the specific concerns behind privacy, governance, and reliability, for example whether client confidential documents ever leave the firm's environment.
- Scope the initial deployment to a narrow, lower risk workflow, for example internal research summarization rather than client facing drafting.
- Sequence risk reduction concretely, such as a security review, a data handling agreement, and a small associate pilot before firm wide rollout.
- Trade off speed against trust explicitly, accepting a slower start in exchange for a security sign off that removes the biggest expansion blocker.
- Define what pilot success unlocks, for example moving to a higher value workflow only after the firm's own risk committee approves.
What a strong answer includes
- Diagnoses the actual concern behind privacy or reliability rather than treating trust as one generic blocker to overcome.
- Picks a genuinely low risk starting workflow, for example internal research rather than anything client facing, to earn trust with real usage before asking for more.
- Sequences concrete risk reduction milestones, such as a security review and a limited pilot, rather than a vague plan to build trust over time.
- Explicitly accepts a slower start as the right tradeoff, since law firms punish a security incident far more than they punish a slow rollout.
Common mistakes
- Pushing for an ambitious first workflow that raises exactly the risk concerns the firm already flagged.
- Treating trust building as soft relationship work instead of concrete, verifiable steps like a security review.
Likely follow-up questions
- What would you do if the firm's risk committee still said no after the pilot succeeded?
- How would you measure whether trust actually improved during the pilot?
More strategy questions
- How should Harvey price for law firms vs. in-house legal teams?Harvey · Strategy · Hard
- How would you grow Harvey adoption among conservative, risk-averse law firms?Harvey · Strategy · Hard
- You inherit Vault with strong customer interest but limited engineering capacity. How would you set Vault’s product vision and a 12-month roadmap across file management, AI search/Q&A, document extraction, secure sharing, and platform investments like permissions, indexing, and integrations? Walk through your prioritization framework, major bets, and what you would explicitly defer.Harvey · Strategy · Hard
- Harvey can fund only one major integration track next: deeper iManage support, broader SharePoint coverage, or cross-platform capabilities like sync, permissions mapping, and admin controls. How would you decide what to build first, and what tradeoffs would you make across customer demand, implementation effort, security risk, and strategic leverage?Harvey · Strategy · Hard
- Harvey’s Command Center needs to serve three jobs for enterprise admins: understanding adoption, managing users and access, and enforcing governance. How would you define the product strategy and first 12-month roadmap for Command Center, and what framework would you use to make trade-offs across those three areas for Harvey’s largest legal customers?Harvey · Strategy · Hard
- You inherit a platform where teams lack visibility into request failures, latency regressions, customer-impacting incidents, and model-quality degradation. How would you define the product scope for observability, decide what to ship first, and ensure the work improves customer outcomes rather than just adding internal tooling?Harvey · Strategy · Hard
More questions from Harvey
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop