Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Design Usability Test for New Feature

EasyProduct Sense00:00
Practice interviewer
In session
5 left
00:00

Your question is Design Usability Test for New Feature. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Company Context

NotionFlow is a B2B productivity SaaS company with 3M monthly active users across startups, mid-market teams, and enterprise customers. Its revenue comes from seat-based subscriptions, and the company competes on ease of use and fast feature adoption rather than deep customization.

Problem

NotionFlow is preparing to launch a new AI-powered meeting summary feature inside its core workspace product. The feature automatically turns meeting notes and transcripts into action items, summaries, and follow-up tasks. Early internal demos are promising, but the team does not know whether users can understand, trust, and successfully use the feature without guidance.

Leadership wants a usability test before launch because previous releases showed a pattern: strong feature interest in surveys, but low activation after release due to confusing setup, unclear value, and weak in-product discoverability. The PM needs a test plan that can identify the biggest usability issues quickly and provide clear launch recommendations.

Deliverables

  1. Design a usability test plan for this new feature, including objective, target users, and methodology.
  2. Define the key tasks participants should complete and what success or failure would look like.
  3. Explain what qualitative and quantitative signals you would collect during the test.
  4. Recommend how many users to test, how you would segment them, and how you would prioritize findings.
  5. Describe how test results would influence launch scope, iteration priorities, or go/no-go decisions.

Constraints

  • MVP must launch within 6 weeks.
  • Research budget is limited to one researcher and one designer for 2 weeks.
  • Engineering can only fix 3-5 major issues before launch.
  • The feature is available only on desktop for the first release.
  • The team cannot run a large-scale beta before this usability study.