<aside>
🎆 “If a picture is worth a thousand words, a replay is worth a thousand pictures” - Zack Rosen, Pantheon CEO
</aside>
Summary
Challenges:
- Growing Engineering team from 60 to 200 with a limited understanding of how to scale platform and address performance issues
- 10-12 second initial load time on new dashboard with no clear path to address issues
- Determining tech stack tradeoffs whilst adding new code on top of an old codebase
Approach/Solutions:
- Adopting Replay to reproduce difficult bugs and performance issues
- Using Replay to see what was happening in the code when performance drags occurred
- CEO and FE Leadership re-prioritized mid-sprint and set clear direction for its dashboard
Why Replay?
- The only developer tool that actually gave a deep understanding of perf bottlenecks
- Enabling CEO and Engineering Leadership to make its Dashboard a more performant site
- Accelerate onboarding of new engineers
Results
- Within 6 months, improved platform load time 500% (10-12 second to 2 second average)
- Higher confidence from C-Suite in understanding performance issues and setting priorities
- Mean time to resolution on bug fixes reduced significantly (weeks → days)
- Engineers can start contributing to bug fixes within days on the job