Company Context

NotionFlow is a B2B SaaS project management platform used by 25,000 companies, with 3.5M monthly active users across web and mobile. The product started as a simple task-tracking tool for small teams, but over the past two years it has added automation, reporting, integrations, and AI-assisted workflows to move upmarket.

Problem

As NotionFlow has expanded, user feedback has become more polarized. Power users value the added functionality, but new and mid-market users increasingly describe the product as "harder to learn" and "too cluttered." Over the last 2 quarters, new-user activation has dropped from 62% to 54%, support tickets related to navigation are up 28%, and NPS among teams with fewer than 50 employees has fallen from 41 to 33.

Leadership wants to continue shipping enterprise-grade capabilities without losing the product's reputation for simplicity. You are the PM responsible for the core product experience. Your challenge is to define how you would keep the user experience central as the product evolves.

Deliverables

1. Define how you would identify and prioritize the most important user needs as the product grows more complex.
2. Propose the tools, methods, and operating mechanisms you would use to keep UX central across discovery, roadmap planning, and launch decisions.
3. Recommend how to balance the needs of new users, core SMB customers, and advanced enterprise admins.
4. Define success metrics and decision criteria to know whether the product is evolving without degrading usability.
5. Explain the key trade-offs you would make if business stakeholders push for faster feature delivery.

Constraints

• You have 1 product designer, 6 engineers, and shared access to a user research team.
• The company has already committed to launching 3 enterprise features in the next 2 quarters.
• You cannot redesign the entire product from scratch.
• Any proposed changes must show measurable impact within 6 months.