Workflow Lab: Deploying Designs Directly with Figma Make | Figma Blog (opens in new tab)

Figma’s workflow connects design, production code, and team review so designers can handle small, high-impact improvements without waiting for engineering backlog prioritization. Using Figma Make with a real codebase, a designer can identify accessibility issues, implement craft-level fixes, and move the work toward a merged pull request. The approach keeps engineers focused on larger architectural work while preserving design nuance and collaboration.

The Problem with Backlog-Driven Fixes

• Minor accessibility and usability improvements often enter a backlog where they compete with larger engineering priorities.
• Small changes may be too granular to prioritize but too valuable to ignore.
• Written handoffs can lose important nuance, creating clarification cycles between designers and engineers.
• The example organization, the fictional Museum of Speculative Futures, is simultaneously improving accessibility and rewriting its website architecture.

A Shared Ownership Model

• The product manager proposes that engineers continue handling the major rewrite.
• The designer takes end-to-end ownership of lower-risk, craft-level changes.
• Figma Make with production code enables the designer to work directly against the real website implementation.
• The workflow is intended to take changes from the Figma canvas through team review and into a pull request without filing a ticket.

Testing the Existing Experience

• Before making changes, the designer uses the Figma agent to generate synthetic personas, including:
  • A first-time visitor planning a trip
  • A returning member
  • Someone navigating with a screen reader
• These personas explore the site and surface obvious friction early.
• The audit identifies several issues:
  • A confusing exhibition or visit-page label
  • A call-to-action that is easy to miss
  • A date picker that is difficult to understand
  • A blank state when search returns no results
• The article emphasizes that synthetic personas do not replace real user research, but they can identify issues before in-person sessions.

Reviewing Design Improvements

• The designer addresses the findings directly on the canvas.
• The designer, engineer, and product manager review the proposed changes together.
• They agree on improvements such as:
  • Clearer navigation language
  • A more prominent call-to-action
  • A more usable date picker
• The changes support the shared goal of making the site easier to navigate for people with different ways of experiencing the web.

The recommended workflow is to reserve engineers’ time for substantial technical work while enabling designers to directly resolve small, accessibility-focused issues in production code. Figma Make, the Figma agent, GitHub integration, and canvas-based review create a path from design insight to implementation without losing context or waiting indefinitely in the backlog.