Company Context

NotionFlow is a B2B SaaS collaboration platform used by 25,000 small and mid-sized companies for project tracking, internal docs, and lightweight workflow automation. The company has strong adoption among product and operations teams, but expansion revenue has slowed as larger customers ask for more advanced collaboration capabilities.

Problem

The leadership team is considering a new AI meeting-summary feature that would turn call transcripts into action items and project updates inside the product. Early sales feedback is positive, but product leadership is unsure whether the real user problem is meeting overload, poor follow-through, or fragmented documentation. Past launches have suffered because teams moved from anecdotal customer requests directly into development.

You are the PM responsible for defining the research approach before committing roadmap resources. You have 6 weeks to recommend whether the company should build this feature, narrow the scope, or deprioritize it. Engineering can only support a lightweight prototype during this period, and the research budget is limited.

Deliverables

1. Explain which research methods you would use to understand the user problem and why each method fits this case.
2. Describe how you would choose between qualitative and quantitative methods at different stages of the decision.
3. Identify the target user segments you would prioritize for research and what key assumptions you want to validate.
4. Recommend how research findings should translate into product scope, prioritization, and a go/no-go decision.
5. Define success criteria for the research phase itself.

Constraints

• Research budget is capped at $40,000
• Decision needed within 6 weeks for quarterly planning
• Only one designer and one data analyst are available part-time
• No full production build allowed before evidence of user value
• Existing product analytics are incomplete for meeting-related workflows