Product design question

A top law firm is willing to pilot Vault, but attorneys are hesitant to move matter documents into a new system because of security concerns, ethical walls, permissions complexity, and workflow disruption. How would you diagnose the biggest adoption blockers, what evidence would you gather, and how would you prioritize the first product changes to improve rollout success?

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 the ability to diagnose adoption blockers rooted in trust and workflow disruption, gathering real evidence before prioritizing product changes.

Interview the hesitant attorneys directly to distinguish concerns about security policy, ethical walls, permissions complexity, or simple workflow disruption.
Review whether the security concern is about Harvey's actual security posture or a perception gap, since the fix differs, technical hardening versus better communication.
Check if ethical wall and permissions complexity concerns point to a real product gap, such as insufficiently granular permission controls.
Gather evidence on workflow disruption specifically, for example how much extra step the migration adds to an attorney's existing document workflow.
Prioritize fixes that address the most cited and highest severity blocker first, rather than spreading effort evenly across all concerns.
Propose a low friction pilot, such as migrating one matter type first, to let skeptical attorneys build trust incrementally rather than all at once.

Separates a real security or permissions product gap from a perception or communication gap, since the fix is completely different for each.
Gathers evidence directly from the hesitant attorneys rather than assuming what is blocking adoption from secondhand reports.
Proposes an incremental pilot, one matter type first, as a concrete way to build trust rather than asking for full migration upfront.

Assuming the blocker is security without confirming whether it is a real gap or a perception issue.
Prioritizing product changes evenly across all stated concerns instead of focusing on the most cited, highest severity one first.

How would you measure whether the perception gap, if it is one, has actually closed after your changes?
What would you do if the ethical wall concern points to a genuine permissions product gap that takes months to fix?