Strategy question
How would you grow Harvey adoption among conservative, risk-averse law firms?
- 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 go to market strategy for winning over a buyer segment defined by caution, liability fear, and slow decision cycles.
How to approach it
- Identify what makes conservative firms slow to adopt: fear of malpractice liability, partners' unfamiliarity with AI, and skepticism from prior legal tech disappointments.
- Segment the target: distinguish large established firms bound by tradition from mid size firms that may be more open but have less budget.
- Propose a low risk entry point: start with a narrow, low stakes use case like internal research support rather than client facing drafting.
- Build trust through proof, not persuasion: published accuracy benchmarks, references from peer firms, and a pilot with clear before and after metrics.
- Address the human factor: target partners and practice group leaders directly, since law firm adoption is driven by senior buy in more than bottom up usage.
- Confirm with the interviewer whether the goal is initial adoption or expansion within firms already using Harvey narrowly, since the tactics differ.
What a strong answer includes
- Leads with a low risk, internal only use case as the wedge, recognizing that client facing trust must be earned incrementally, not assumed on day one.
- Uses peer proof specifically, since law firms move in reference groups and a competitor firm's adoption is more persuasive than a vendor's own claims.
- Targets partners and practice group leads directly, correctly identifying that legal adoption is top down, unlike many consumer or SMB products.
- Proposes a structured pilot with a defined success metric agreed in advance, giving cautious firms a bounded way to say yes.
Common mistakes
- Proposing a broad feature pitch instead of addressing the specific liability and trust fears driving the caution.
- Targeting associates or IT instead of the partners who actually decide on firm wide tools.
- Assuming a free trial alone overcomes caution, when the real blocker is risk perception, not price.
Likely follow-up questions
- How would you handle a firm that wants Harvey but its malpractice insurer raises concerns?
- What would a successful pilot need to prove to convert to a firm wide contract?
- How would this strategy differ for a firm that already had a bad experience with legal tech?
More strategy questions
- How should Harvey price for law firms vs. in-house legal teams?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
- Harvey is being pushed to ship new platform capabilities faster, while enterprise customers are escalating concerns about uptime, latency, and trust. As the PM for Core Platform, how would you build a 12-month infrastructure roadmap that balances reliability, performance, security, and feature velocity? Walk through your prioritization framework, the inputs you would use, and how you would handle tradeoffs when these goals conflict.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