HubSpot's analytics team is replacing a legacy reporting dashboard used by 18,000 SMB customers with a new self-serve analytics experience. You are the program manager leading the migration across product, engineering, design, support, and go-to-market. Leadership wants the new dashboard launched before the annual customer conference in 12 weeks because the old system is costly to maintain and has rising reliability issues.
The VP of Product wants a visible conference launch with strong adoption metrics. The Engineering Director wants to avoid destabilizing the core reporting pipeline during peak Q4 usage. Customer Success wants feature parity for top enterprise reports before any migration, while Finance is pushing to retire the legacy vendor contract by quarter end to avoid a $220,000 renewal.
The project has a fixed 12-week timeline, a remaining budget of $160,000, and a team of 11 people: 4 backend engineers, 2 frontend engineers, 1 designer, 1 data engineer, 1 QA lead, 1 PM, and you as program manager. Two critical dependencies are outside your control: a data platform team must deliver a new aggregation API by Week 5, and Legal needs 10 business days to approve updated customer data retention language. Only 6 of the top 10 legacy reports can be rebuilt before launch with current capacity.
Two weeks into planning, the data platform team signals their API may slip by 2 weeks. At the same time, Sales has promised three strategic customers they will be migrated at launch, but one of their must-have reports is not in the top 6 prioritized reports.
