SCALING DESIGN PRODUCTION AT BEST BUY
Migrating a Digital Design Team from Photoshop to Figma
Overview​​​
Best Buy Canada’s digital design team supports high-volume production across e-commerce, marketing, and advertising channels. As production demands increased, the team’s Photoshop-based workflow began to create friction around collaboration, version control, and feedback. I led the transition to Figma to improve efficiency, consistency, and cross-team collaboration—while maintaining ongoing production output.
​​
Problem​
While Photoshop worked well for individual tasks, it became increasingly limiting at team scale. Designers worked in isolated files, making real-time collaboration difficult. Version control issues led to duplicated work and rework, while feedback was often shared through screenshots and email, slowing iteration. As output demands increased, these inefficiencies began to impact turnaround time and team velocity.
​
My Role​
As a Product / Digital Designer, I helped lead the transition from Photoshop to Figma. My role included identifying workflow pain points, defining new collaborative design processes, creating shared file structures and standards, and supporting team onboarding and adoption.
​
Constraints​​
The transition needed to happen alongside ongoing production work, with no opportunity for downtime. Designers had varying levels of comfort adopting new tools, and existing workflows were deeply tied to Photoshop. Maintaining quality and speed throughout the transition was critical, which required a careful, incremental approach.
​
Strategy & Process
I began by reviewing how the team created, shared, and revised design files to understand where friction occurred. The most significant issues were versioning, fragmented feedback, and limited visibility into work in progress. Rather than positioning Figma as a replacement tool, I framed it as a solution to these specific problems.
​
To reduce risk, I introduced Figma gradually. I set up a shared team space with clear project organization and established file, page, and naming conventions. Early projects were chosen intentionally to allow designers to adopt the tool without disrupting critical production work.
​
Adoption focused on enablement rather than enforcement. I created lightweight documentation for common workflows, walked designers through relevant Figma features tied to their daily tasks, and provided ongoing support during live projects. This approach helped designers see immediate benefits and encouraged organic adoption.​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

Outcomes & Impact
​​
The transition to Figma resulted in meaningful improvements across the team:
-
Real-time collaboration replaced isolated file workflows
-
Version control issues were significantly reduced
-
Feedback became faster, clearer, and more centralized
-
Designers gained better visibility into active work
-
A shared foundation was established for future design systems and libraries
​
Most importantly, these improvements were achieved while maintaining production output and quality.​​​​​​

What I Learned
​​
This project reinforced that tool changes require thoughtful change management. Adoption improves when teams experience clear, immediate benefits, and shared systems play a critical role in reducing friction and improving design quality at scale. Design operations can have as much impact as individual design output.
​
Looking Ahead
​
This migration laid the groundwork for building a shared Figma design library, improving UI consistency, and enabling more scalable design systems across teams.
