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.