Product design question
Design the core dashboard experience for Command Center for a large regulated legal customer. What information should be visible on the default admin view, how would you organize adoption, access, and governance signals, and how would you make the dashboard simple enough to use regularly but trustworthy enough for operational decision-making?
- Harvey
- Product design
- 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 designing an admin dashboard's default view for a regulated customer, balancing everyday usability with operational trustworthiness.
How to approach it
- Organize the default view around the three core jobs: adoption at a glance, access and user status, and governance flags needing attention.
- Lead with governance alerts requiring action, like unusual access patterns or policy violations, at the top, since a regulated legal customer needs to see risk first.
- Show adoption as a simple trend, not a dense analytics panel, since admins check this regularly and need a fast read, not deep analysis.
- Show access management as actionable items, pending approvals or expiring access, rather than a static user list requiring the admin to hunt for issues.
- Keep the default view to a small number of cards or sections, with drill-down available for admins who need audit-level detail on demand.
- Validate the design with actual admins from a regulated firm to confirm the prioritized order matches what they check first in practice.
What a strong answer includes
- Leads with actionable governance alerts rather than burying risk signals under a dense analytics view, matching what a regulated customer actually needs first.
- Makes access management actionable, pending items, not a static list the admin has to interpret.
- Keeps the default view minimal with drill-down for detail, avoiding the trap of cramming every metric onto one screen.
Common mistakes
- Burying governance risk signals below adoption metrics on the default view.
- Designing a dense, information-heavy default view that admins will not check regularly.
Likely follow-up questions
- How would you decide which governance alerts are urgent enough for the default view?
- How would you test whether admins are actually acting on the alerts shown?
More product design questions
- How would you improve Harvey's Vault for bulk document review at large law firms?Harvey · Product design · Hard
- Design a citation system so lawyers can fully trust Harvey's outputs.Harvey · Product design · Hard
- Design a Workflow Builder that lets non-technical lawyers automate recurring tasks.Harvey · Product design · Medium
- A top law firm says Vault’s AI search is promising, but attorneys still avoid using it in high-stakes matters. How would you diagnose whether the trust gap comes from retrieval quality, citation and explanation UX, permissioning concerns, workflow fit, or change management, and how would you prioritize the first product changes?Harvey · Product design · Hard
- Several top law firm customers say they will not expand Harvey without stronger identity and access management. How would you prioritize and scope SSO, SCIM, RBAC, and audit logging for the first two releases of Command Center, and how would you balance enterprise security requirements against implementation complexity and admin usability?Harvey · Product design · Hard
- Lawyers will rarely ask for 'better queuing' or 'stronger isolation,' but they will care deeply about accuracy, latency, reliability, auditability, and security. How would you uncover those needs and translate them into clear infrastructure product requirements and prioritized engineering work? Be specific about discovery methods, requirement framing, and how you would separate must-haves from nice-to-haves.Harvey · Product design · Hard
More questions from Harvey
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovering and Sizing AI Opportunities
- Chapter 7: Designing AI UX and Oversight
- Chapter 14: Interviewing for AI PM Roles