How one designer escaped the export-upload abyss | Figma Blog

The post argues that traditional designer-developer handoff creates unnecessary work, outdated files, and communication problems. At Pivotal, designer Colby Sato replaced repeated image exports and uploads with Figma’s browser-based, collaborative workflow. This saved roughly two days per project and made design critiques more focused and efficient.

The Export-and-Upload Problem

• Colby exported design frames as images and uploaded them to Pivotal Tracker engineering cards.
• He repeated this process 15–20 times per project as designs evolved.
• Searching through hundreds of engineering cards was time-consuming.
• Missed updates sometimes caused engineers to implement outdated designs.
• The process wasted developer time and made collaboration frustrating.

Figma as a Shared Source of Truth

• Figma files were accessible in the browser, always current, and shareable through links.
• Colby could add a Figma link when creating an engineering card instead of updating images repeatedly.
• Comments attached directly to design frames provided functional context.
• The workflow eliminated uncertainty about which design version engineers should use.
• Colby estimated it saved him two days of work per project.

More Effective Design Reviews

• Pivotal’s weekly critiques had previously relied on post-it notes and verbal explanations.
• Figma comments stayed attached to the relevant design, making feedback easier to understand.
• Colby could observe where engineers were focusing in the file through their cursor activity.
• He could redirect reviewers toward areas where feedback was most valuable.
• Reviews became faster, more contextual, and more collaborative.

Figma ultimately shifted Pivotal’s focus from tracking files and feedback to improving the product itself. The post recommends using a shared, continuously updated design workspace to reduce handoff friction and enable stronger collaboration between designers and engineers.