Lead a New Analytics Dashboard Launch

Project Context

NotionFlow, a B2B workflow SaaS company, wants to launch a new customer analytics dashboard for its mid-market clients before the annual customer conference in 10 weeks. The feature is expected to improve retention and support expansion revenue, and the CEO has already mentioned it in a keynote teaser. You are the program manager coordinating a 9-person cross-functional team across product, engineering, design, data, and go-to-market.

Key Stakeholders

The VP of Product wants a polished launch at the conference with strong adoption metrics in the first month. The Engineering Manager is concerned about technical debt in the reporting pipeline and wants to limit scope. The Head of Sales wants advanced export and custom reporting included because two large renewals depend on them. Customer Success wants a stable rollout to 20 pilot accounts first to avoid support escalations.

Constraints

The launch deadline is fixed: 10 weeks from today, with a live demo required at the conference in Week 10. Budget for external contractors and tooling is capped at $85,000. The team includes 4 engineers, 1 designer, 1 data analyst, 1 PM, 1 QA lead, and you as program manager; no additional headcount is approved. The dashboard depends on a data pipeline upgrade scheduled to finish by the end of Week 4, and legal review for customer-level benchmarking requires 7 business days.

Complications

1. One senior frontend engineer is allocated only 50% because they are also supporting a critical billing migration.
2. Early pilot customers are asking for CSV export, but that work would likely push out benchmarking visualizations.
3. The conference demo environment must be production-like, but the infrastructure team can only support one rehearsal window in Week 9.

Deliverables

1. Build a 10-week execution plan with milestones, owners, and dependencies.
2. Recommend launch scope, including what to ship at conference, what to defer, and why.
3. Define stakeholder communication and escalation points for competing priorities.
4. Propose launch success metrics for pilot and general availability.
5. Identify the top risks, mitigation actions, and rollback or contingency plans.