Project Context
NotionFlow, a B2B workflow SaaS company, has committed to three customer-facing launches in the same quarter: SSO for mid-market customers, a new analytics dashboard, and Salesforce integration improvements. You are the program manager coordinating a 12-person cross-functional team across engineering, design, QA, and go-to-market. The quarter ends in 10 weeks, and leadership has stated that at least two launches must ship before the annual customer conference.
Key Stakeholders
The VP of Product wants all three launches completed this quarter to support roadmap credibility. The Head of Sales is pushing hardest for Salesforce improvements because two $1.2M renewals depend on it. The Security lead considers SSO non-negotiable due to enterprise prospects and audit commitments. Engineering management is concerned about team capacity because two senior engineers are already spending 25% of their time on production support.
Constraints
- Timeline: 10 weeks until quarter close; customer conference is in Week 8
- Team: 6 engineers, 2 designers, 1 QA lead, 1 data analyst, 1 PM, you as program manager
- Capacity: 2 engineers available only 75% due to incident rotation
- Budget: $90,000 remaining, enough for either contract QA support or one external Salesforce consultant, not both
- Dependencies: Security review for SSO takes 2 weeks; Salesforce partner certification takes 3 weeks; analytics dashboard depends on a delayed event-tracking pipeline upgrade due in Week 4
Complications
- In Week 2, the event-tracking pipeline slips by another 2 weeks, putting the analytics dashboard at risk.
- In Week 3, Sales asks for two additional Salesforce workflow features for a strategic account.
- The CEO asks for a conference demo in Week 8, even if one launch is not fully GA-ready.
Deliverables
- Build a 10-week execution plan covering sequencing, owners, and dependencies across all three projects.
- Recommend how to prioritize the launches and what trade-offs or scope cuts you would make.
- Propose a stakeholder communication plan, including how you would handle conflicting executive requests.
- Identify the top execution risks and define mitigation and escalation triggers.
- Define launch success criteria and a fallback plan if only two projects can ship on time.
