Project Context
Notion is considering a new self-serve analytics dashboard for workspace admins, but leadership has only given a broad goal: "launch something useful this quarter to reduce enterprise reporting requests." You are the program manager assigned to turn this ambiguous goal into a structured plan across product, engineering, design, data, and support.
The working team includes 1 PM, 6 engineers, 1 designer, 1 data analyst, and shared support from security and legal. The project matters because enterprise customers generated 1,200 manual reporting tickets last quarter, and Sales believes a lightweight analytics product could improve renewals. Leadership wants a launch decision in 10 weeks, but there is no agreed scope, no success definition, and multiple teams have conflicting assumptions about what "useful" means.
Key Stakeholders
The VP of Product wants a visible Q3 launch. The Head of Enterprise Sales wants customer-facing commitments for top accounts within 6 weeks. The Engineering Manager wants to avoid building a brittle dashboard on top of unreliable event pipelines. The Security Lead requires a privacy review before any admin-facing usage data is exposed.
Constraints
- Timeline: 10 weeks to launch or formally recommend a no-launch decision
- Budget: $180,000 for vendor tooling, contractor QA, and analytics instrumentation
- Team capacity: 6 engineers, but 2 are only available at 50% due to platform migration work
- Dependency: event logging quality for 3 core admin metrics is currently below 92% completeness
- Launch target: US and EU enterprise workspaces only, no mobile support in phase 1
Complications
- Sales has already told 5 strategic customers that advanced analytics is "coming this quarter," but no feature list was approved.
- A data engineer warns that fixing event instrumentation may take 3 weeks, which could consume the MVP timeline.
- Legal raises concern that one proposed metric may expose employee-level activity in the EU.
Deliverables
- Define the MVP scope and explicit non-goals for a 10-week launch.
- Build a phased execution plan with milestones, owners, and dependency management.
- Recommend how to handle the instrumentation gap without derailing the quarter.
- Propose launch criteria, rollback conditions, and stakeholder communication cadence.
- Identify top risks, trade-offs, and whether you would still launch this quarter.
