Project Background
At AsanaFlow, a B2B workflow software company, the engineering team is replacing a legacy manager dashboard that is slow, hard to maintain, and responsible for a growing share of customer complaints. You are the engineering manager overseeing execution for a 10-person cross-functional team and must deliver a production launch in 12 weeks before the company’s annual customer conference.
The project matters because 38% of enterprise admins use this dashboard weekly, and Sales has tied two renewals worth $1.4M ARR to visible improvements in dashboard speed and reliability. Leadership wants a credible launch, but Engineering also needs to avoid destabilizing the core reporting platform.
Key Stakeholders
The VP of Product wants the full redesigned experience shown at the conference. The Head of Sales wants at least three lighthouse customers live before then. The Director of Engineering wants a stable rollout with no spike in Sev-1 incidents. The Data Platform team owns a dependency for new aggregation APIs, but they are already committed to a separate billing migration.
Constraints
- Timeline: 12 weeks total, with a fixed conference demo in Week 10 and GA target in Week 12
- Budget: $120,000 remaining, including vendor QA and design support
- Team: 6 engineers, 1 designer, 1 PM, 1 QA lead, 1 data engineer shared at 50%
- Dependency: Data Platform must deliver 3 aggregation endpoints by end of Week 4
- Reliability requirement: no more than 0.5% increase in dashboard error rate during rollout
Complications
- Two enterprise customers are asking for custom export features that were not in the original scope.
- The shared data engineer is likely to be pulled for 2 weeks into a billing incident response.
- Early testing shows the new dashboard is 25% faster, but one high-usage report is slower than the legacy version.
Your Task
- Build a 12-week execution plan with milestones, owners, and dependency management.
- Define what good engineering execution looks like for this project and how you would measure it.
- Recommend scope trade-offs for the conference demo, lighthouse rollout, and GA launch.
- Identify the top risks and propose mitigation and escalation triggers.
- Outline your launch, rollback, and stakeholder communication plan.
