Organizing 2000 Developers for BFCM in a Remote World

Summary

Shopify organized a cross-company program to prepare its platform for Black Friday and Cyber Monday (BFCM), coordinating more than 2,500 people responsible for over 1,000 deploys across services. Engineering Program Managers absorbed administrative, communication, and reporting work so BFCM leads could focus on technical challenges, while departmental champions assigned preparation tasks. Preparation covered maintenance, game days, load tests, capacity increases, weekly tracking, and a Caution Tape bot requiring risk-to-value assessments for pull requests in critical areas. Deploys were slowed through smaller batches, longer canaries, and a planned weeklong lock while communication used Slack, GitHub, documentation, presentations, emails, and office hours. The effort coincided with $5.1+ billion in BFCM sales and load testing plus resource scaling paid off, but developer productivity declined amid inconsistent messaging; future plans called for a more balanced approach, automation, and reusable communication templates.

Context

Shopify needed to prepare a platform serving more than one million merchants for BFCM while maintaining stability, performance, and quality. Preparation became more complex as sales spread beyond the two main shopping days, more timezones had to be coordinated, and teams needed to test pre-sale and post-sale workflows and areas previously associated with disruptions.

Approach / What changed

Engineering Program Managers took on administrative, communication, and reporting duties from BFCM leads. They created workstreams and a communication calendar, used departmental champions to distribute ownership, tracked progress weekly, and coordinated preparation such as maintenance, game days, load tests, and capacity increases. They also used the Caution Tape bot, smaller deploy batches, longer canaries, and a planned weeklong deploy lock to manage release risk.

Takeaways

• Departmental champions selected by GMs or VPs distributed platform-preparation assignments, while a tracking spreadsheet and weekly reports maintained visibility into ownership and progress.
• Caution Tape required risk-to-value assessments for new pull requests in critical repositories during November and December; merchant-facing features needed director or GM approval to ship.
• The program avoided a complete shipping stoppage and increased review activity, but reduced developer productivity and produced inconsistent guidance about shipping to critical areas.

Related reading