For the same accessibility-focused VR product, assume the team can ship only one feature first because engineering capacity is limited: **voice-to-text** or a **voice assistant**. How would you decide which one to prioritize? Explain your decision framework, what factors matter most, which feature you would choose, and what evidence could change your mind. ### Constraints & Assumptions - The product targets VR users who cannot comfortably rely on standard hand controllers. - Voice cannot be the only accessibility path because some users may have speech impairments, noisy environments, privacy concerns, or accent-recognition issues. - Keep the first release narrow enough to ship and measure. - Consider both immediate user value and platform foundations for future accessibility work. ### Clarifying Questions to Ask - What is the main blocker found in user research: system navigation, text entry, social communication, onboarding, or help? - Which surfaces are in scope for the MVP: home environment, settings, search, social apps, or third-party apps? - What speech recognition and on-device privacy capabilities already exist? - Are we optimizing for activation, retention, social engagement, or accessibility coverage? ### Part 1 - Define The Prioritization Framework What framework would you use to compare voice-to-text and voice assistant? #### What This Part Should Cover - Criteria such as core task unlock, reach, impact, confidence, effort, safety, privacy, and strategic reuse. - A focus on the job to be done rather than a generic feature comparison. - Recognition that the decision depends on the current bottleneck. ### Part 2 - Compare The Two Options How do voice-to-text and voice assistant differ in user value and implementation risk? #### What This Part Should Cover - Voice assistant as a way to unlock navigation, setup, app launch, help, and settings. - Voice-to-text as a way to improve chat, search, form entry, and social communication. - Privacy, recognition quality, localization, noise, error recovery, and app integration risks. ### Part 3 - Make A Recommendation Which feature would you prioritize first, and why? #### What This Part Should Cover - A clear recommendation under stated assumptions. - A tight MVP scope and measurable launch criteria. - A plan to reuse foundational speech work for the second feature. ### What a Strong Answer Covers - Prioritizes based on the accessibility job that blocks product use. - Takes a clear position while naming the evidence that could reverse it. - Defines metrics for the chosen feature and guardrails for speech-based accessibility. - Avoids assuming voice works equally well for all users. ### Follow-up Questions - What if research shows users mostly want social communication, not navigation? - How would you design fallback controls when speech fails? - What privacy choices should users control? - How would you measure command success versus perceived trust? - How would you internationalize the feature?