Strategy question
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
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 building a 12-month product strategy that serves three distinct admin jobs at once, with a real tradeoff framework across them.
How to approach it
- Name the three jobs precisely: adoption visibility (who's using Harvey and how), access and user management, and governance enforcement (policy compliance).
- Sequence based on urgency: governance and access control usually gate deal expansion, so weight them earlier than adoption analytics in the first two quarters.
- Use a framework like risk-adjusted revenue impact per job: which job, if unaddressed, most directly blocks expansion or renewal at large legal customers.
- Build adoption visibility second, once access and governance are trustworthy, since usage data is more valuable once admins already trust the platform's controls.
- Reserve the second half of the year for depth: advanced governance policies, custom reporting, and integrations with firm identity systems.
- Set quarterly checkpoints against expansion and renewal metrics to confirm the sequencing is actually unblocking deals, not just shipping features.
What a strong answer includes
- Sequences governance and access ahead of adoption analytics because they gate deal expansion, a concrete prioritization call, not an equal three-way split.
- Uses a named framework, risk-adjusted revenue impact, to make the tradeoff explicit rather than listing three co-equal priorities.
- Ties the roadmap to expansion and renewal metrics as the real test of whether sequencing worked.
Common mistakes
- Treating all three jobs as equally weighted with no real sequencing logic.
- Building adoption analytics first because it is easier, ignoring what actually blocks expansion.
Likely follow-up questions
- How would you handle a large customer who wants adoption analytics before governance ships?
- What would trigger you to reorder the roadmap mid-year?
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
- 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