How Braintree Cut Time Spent on Design Critiques by 50% | Figma Blog (opens in new tab)

Braintree redesigned its critique process by replacing static presentations and follow-up meetings with real-time collaboration in Figma. Designers worked together in the same file during Slack audio calls, making and demonstrating changes immediately. This cut critique time by roughly 50% while also improving collaboration and simplifying developer hand-offs.

Challenges with Traditional Critiques

• Designers typically presented work, collected feedback, and worked alone afterward.
• Feedback could be misunderstood or difficult to apply correctly.
• Follow-up meetings were needed to review revisions and address new issues.
• After PayPal acquired Braintree, multiple design teams, style guides, services, and developer groups increased coordination complexity.

Finding Figma

• Braintree’s Developer Experience team experimented with new critique methods.
• Figma’s browser-based, collaborative files allowed designers to work together regardless of device or location.
• Designers joined an audio Slack call and opened the same file instead of scheduling several in-person meetings.
• Figma’s observation mode let one designer follow another’s screen and move through different frames in real time.

Collaborative Work Instead of Static Feedback

• Designers could duplicate an artboard and make changes while discussing the design.
• Feedback became concrete and immediately understandable rather than being recorded as notes for later.
• Team members brainstormed, explored alternatives, and combined the strongest elements of multiple designs.
• Craig Wattrus estimated that critiques took 50% less time because collaborators could demonstrate ideas directly.
• The process often produced better results than one designer working independently and applying feedback later.

Faster Developer Hand-off

• Designers shared a single link with developers instead of repeatedly exporting updated files.
• Designers could explain interactions and demonstrate behavior directly in the shared file.
• Developers received answers immediately, reducing long message exchanges.
• Design and engineering teams needed fewer meetings to clarify how interfaces were intended to work.

Braintree’s experience suggests that real-time, shared design files can turn critiques into productive collaboration sessions. Teams looking to reduce review cycles and improve design-to-development communication should consider working together directly in the design artifact rather than relying on presentation-based feedback.