figmaMay 6, 2025

Figma Buzz Is Where Design and Marketing Teams Co-create | Figma Blog (opens in new tab)

Figma Buzz is a new open-beta workspace designed to help brand designers and marketers create on-brand assets together. It addresses fragmented tools and workflows by combining Figma’s design precision with approachable editing and reusable templates. The product aims to speed up production while letting marketing teams create independently within brand guidelines. ## A Shared Space for Design and Marketing - Product launches require extensive marketing materials beyond the original design work. - Designers often need control and precision, while marketers need simple tools for adapting content quickly. - Figma Buzz brings both groups into one collaborative environment. - Designers can copy existing Figma designs into Buzz, build templates, or create assets directly with Figma Design functionality. - Marketers can customize materials without worrying about departing from brand standards. ## Types of Assets Figma Buzz supports a broad range of branded content, including: - Social media posts in multiple platform-specific sizes - Digital display and social advertisements - Flyers, email headers, and promotional announcements - Event invitations, schedules, and badges - Internal communications such as signage, infographics, and one-pagers - Personalized cards and other celebration materials ## Flexible Ways to Start Users can begin creating assets in several ways: - Choose from pre-made templates. - Start with a blank design. - Create images using OpenAI’s `gpt-image-1` or Gemini. - Copy and paste designs from Figma Design. - Use an intuitive inline toolbar for editing. The examples highlighted include Instagram feed and story ads, Pinterest and Twitter/X promotional posts, event invitations, and thank-you cards. Figma Buzz is intended to reduce repetitive executional work, allowing creative teams to focus more on brand strategy and larger ideas while giving marketers the tools to produce high-quality content quickly and consistently.

design-collaborationfigmagen-aigemini+2

figmaJun 25, 2024

Stack the deck with Figma Slides | Figma Blog (opens in new tab)

Figma Slides is introduced as an open-beta presentation tool combining Figma’s high-fidelity design capabilities with FigJam’s collaborative feedback features. It aims to help designers and non-designers create more engaging presentations without exporting work into separate tools. Figma positions it as a way to turn product reviews, sales decks, and pitches into clearer visual stories and collaborative conversations. ## Why Figma Built Slides - Presenters commonly struggle with: - Designing creative layouts - Finding effective visuals - Spending more than eight hours creating a deck - Figma users created approximately 3.5 million presentations in the previous year. - Designers often had to move Figma work into other presentation tools or distribute prototypes and pre-reads to non-designers. - Figma Slides brings presentation creation into the same environment as design and collaboration. ## High-Fidelity Design Features - Slides includes core presentation features such as: - Speaker notes - Slide transitions - Presentation-focused editing tools - Design mode provides access to Figma Design capabilities, including: - Auto Layout - Advanced properties - Precise alignment and snapping - Interactive components and states - Interactive components, such as hover states, can remain functional during presentations. ## Shared Libraries and Assets - Existing Figma text styles, color styles, and design assets are available directly in Slides. - Designers can reuse established libraries instead of recreating presentation elements. - Copy-and-paste workflows work across Figma products, reducing the need to export interface designs individually. ## Grid View for Structuring Narratives - Users can edit individual slides or switch to grid view for an overview of the entire deck. - Grid view organizes slides into rows, making it easier to: - Rearrange sections - Review the overall story - Refine the narrative arc - This bird’s-eye perspective is particularly useful for long presentations where restructuring becomes difficult. ## From Presentations to Conversations - Figma’s experience with FigJam revealed the limitations of one-way presentations. - FigJam became a regular tool for meetings such as team kickoffs, bug bashes, executive reviews, all-hands meetings, and Q&A sessions. - Figma Slides is intended to combine polished visual storytelling with collaborative participation, helping more people contribute to and influence the discussion. Figma Slides’ central promise is to make presentations both visually sophisticated and easier to build collaboratively, allowing teams to design, organize, and discuss their ideas in one shared space.

design-collaborationfigmafigjamui-ux-design+3

figmaFeb 1, 2024

An Insider’s Guide to a Seamless Figma Migration | Figma Blog (opens in new tab)

Migrating to Figma is presented as an organizational change—not merely a software switch. Success depends on careful planning, cross-functional communication, advocacy, training, and adaptation of existing workflows and cultural norms. The article argues that treating migration as a strategic investment can produce long-term gains in collaboration, transparency, and productivity. ## Planning the Migration - Begin by identifying the reasons for adopting Figma, such as: - Better collaboration - Greater transparency - Streamlined processes - Treat migration as a change-management initiative involving the entire organization. - Plan around team commitments and existing tool-expiration dates. - Use resources such as Figma’s Migration Toolkit for guidance when moving from other design platforms. ## Building a Cross-Functional Advocacy Team - Create a core team with representatives from design, development, product management, and stakeholder groups. - Give the team responsibility for: - Gathering balanced feedback - Configuring the Figma workspace - Managing communications - Coordinating library transfers - Successful examples include: - Wells Fargo’s “Figma Jedis,” combining experts and enthusiastic users - Uber’s integration of Figma training with an existing design-system workshop - JPMorgan Chase’s advocates, nominated by leadership and cross-functional groups - The strongest advocates are engaged, representative of different departments, and connected to existing initiatives. ## Securing Organization-Wide Support - Obtain buy-in from developers, product managers, leadership, and other stakeholders—not only designers. - Present a clear proposal outlining the benefits and drawbacks of migration. - Build support through: - Workshops and demonstrations - Best-practice sharing - Early access to libraries and components - Training and practical guidance - Dropbox’s migration shows the value of sustained outreach and creative engagement, including extensive internal promotion and Figma-themed incentives. ## Learning from Other Organizations - Contact teams that have already completed large-scale migrations. - Their experience can provide: - Training plans - Deployment playbooks - Cover pages and workspace conventions - Warnings about common mistakes - Examples from Wells Fargo, Uber, and Dropbox demonstrate how peer advice can improve rollout planning and reduce avoidable problems. - Large migrations benefit from studying proven approaches rather than designing every process from scratch. ## Establishing a Migration Timeline - Build a schedule that accounts for: - Team availability - Existing project commitments - Expiration dates for current tools - A defined timeline helps coordinate the transition and gives teams a clear path from planning to adoption. The practical recommendation is to manage a Figma migration as a coordinated organizational program: assemble advocates, involve every relevant function, learn from experienced teams, and create a realistic timeline before moving work and libraries.

design-collaborationfigmadesign-systemsdesign-tools+2

figmaMay 17, 2023

Four years in, here’s what Config tells us about the state of design | Figma Blog (opens in new tab)

Config 2023 submissions suggest that the design industry is emerging from pandemic-era uncertainty with renewed optimism. Figma analyzed more than 1,000 conference proposals and found increasing interest in accessibility, creativity enabled by design systems, and broader collaboration. Overall, the submissions portray designers as focused on turning recent challenges into opportunities for more scalable, inclusive, and effective product development. ## A More Optimistic Design Community - Config submissions increased from 420 in 2021 to 520 in 2022 and more than 1,000 in 2023. - Positive sentiment rose from 63% of submissions in 2021 to 72% in 2023. - Submissions increasingly emphasized possibilities and ways teams had “thrived,” rather than focusing on outdated practices or persistent problems. - References to the pandemic fell to one-sixth of their 2021 level. - Mentions of “remote” declined by roughly 20%, suggesting that teams are adapting to changed work patterns. ## Design Systems as Creative Infrastructure - The perceived divide between creative freedom and systematic processes is narrowing. - Designers increasingly view design systems as tools that reduce repetitive work and create more space for creative thinking. - Teams operating at scale are investing in design tokens and reusable systems to maintain speed and consistency. - In 2021, design-system discussions focused mainly on foundational tasks such as auditing, scaling, and establishing basic infrastructure. - By 2023, submissions connected design systems more directly with creativity and visual expression, using terms such as “art,” “transition,” “color,” and “creating.” The emerging view is that systems do not suppress creativity; they can provide the structure and efficiency needed to support it.

design-collaborationfigmaaidesign-systems+3

figmaFeb 27, 2022

What’s new in Figma: February 2022 | Figma Blog (opens in new tab)

Figma’s February 2022 updates focus on making design collaboration easier, from finding files to brainstorming in FigJam. Search now offers previews and file-type filters, while FigJam—now out of beta—adds more flexible editing and clearer collaboration tools. Overall, the release aims to keep teams aligned and help ideas move smoothly from brainstorming to implementation. ## Updated Search and Discoverability - Search results now include file previews, making it easier to identify the correct design. - Users can filter recents, team pages, and search results by Figma or FigJam file type. - These changes reduce the time spent locating current designs and resources. ## FigJam Collaboration Improvements With FigJam available to all teams, Figma added several refinements for brainstorming and diagramming: - **Centralized resource menu:** Components, templates, widgets, and other resources are now accessible from one simplified toolbar menu. - **Flexible font sizing:** Text can be resized to any size by dragging the corners of a text box, supporting clearer hierarchy and emphasis. - **Persistent stamps and highlights:** Reactions and highlights stay attached to the objects they reference when content is moved. - **Faster color and shape changes:** Updated toolbar icons make it easier to swap colors and shapes while building diagrams. - **Image borders:** Users can add borders to images to draw attention to selected visuals. - **Simpler selection borders:** Thinner borders and larger selection corners make objects easier to select and resize. Figma’s release reinforces its broader goal of bringing more people into the design process while keeping collaboration organized, discoverable, and visually clear.

design-collaborationfigmafigjamui-design+2

figmaJan 31, 2022

Design needs everyone: new plans for companies that design together | Figma Blog (opens in new tab)

Figma’s 2022 plan updates aim to make design a company-wide activity while reducing the organizational complexity that comes with more participants. FigJam is leaving beta with expanded collaboration features and new pricing, while Figma Enterprise adds structure, controls, security, and administrative support for larger organizations. The central goal is to help teams collaborate from brainstorming through implementation without overwhelming users or administrators. ## FigJam Becomes a Full Collaboration Product - FigJam was launched in beta to support brainstorming, diagramming, planning, meetings, and informal collaboration. - Teams adopted it for varied uses, including: - Dwell’s company-wide idea “swarms” - Square’s employee onboarding - Twitter’s cross-functional bug-bashing sessions - Figma expanded FigJam with plugins, widgets, and ready-to-use templates. - FigJam is free on the Starter plan, including: - Unlimited personal whiteboards - Three shared whiteboards - Unlimited collaborators - Unlimited shared whiteboards for an organization start at $3 per editor per month. ## Figma Enterprise for Larger Organizations - As more departments joined the design process, companies faced: - More files and projects to navigate - Less flexibility for individual teams - Greater administrative responsibility - The Enterprise plan is designed for organizations needing more structure, granular controls, advanced security, and support. - Pricing begins at: - $75 per editor per month for Figma - $5 per editor per month for FigJam - Features were being released immediately or planned for the following months. ## Workspaces Reflect Company Structure - Enterprise workspaces let organizations create dedicated areas for departments, product groups, or functions. - Workspaces help users focus on relevant content while preserving access to company-wide resources. - Administrators can define default teams and libraries for each workspace. - Users can limit searches to a particular workspace to find files, people, and components more quickly. ## Administration at Company Scale - Enterprise tools are intended to manage large numbers of files, users, and permissions more efficiently. - Workspace administration can be delegated to people familiar with each group’s users. - Delegated responsibilities include membership, roles, and true-ups. - Role-setting through SCIM is also introduced to automate administrative workflows. Figma’s broader recommendation is that companies should invite more people into design while using FigJam for inclusive collaboration and Enterprise workspaces and controls for organization-wide scale.

design-collaborationfigmafigjamscim+2

figmaDec 15, 2021

Frame 2021: design by the numbers | Figma Blog (opens in new tab)

Figma’s 2021 data shows how remote and hybrid work reshaped design collaboration. Teams increasingly worked across borders and included product managers and developers earlier, using FigJam for ideation and Figma for interface design and handoff. The overall trend was toward a more open, continuous design process spanning idea to implementation. ## Building Across Borders - Figma users represented 235 countries and territories. - Collaboration activity grew across regions and time zones as organizations adopted virtual-first and hybrid work. - In the U.S., New York and California remained major collaboration hubs, while Washington and Texas gained activity. - Globally, the U.S. and Russia were established hubs, with India, Brazil, and Indonesia increasingly active. - Nearly 14% of collaboration occurred between different continents, up from 8% in early 2020. - Examples included teams collaborating between Madrid and Wellington, and between Beijing and Buenos Aires. ## From Ideas to Shipped Products - About 52% of users collaborated with others in 2021. - Shared files had a median of four invited collaborators. - Product managers and developers were the largest groups of Figma users outside designers. - FigJam supported early-stage brainstorming and freeform exploration before teams moved into Figma to build interfaces. - Around 15% of active FigJam users began with templates, with brainstorming templates the most popular. ## A More Open Design Process - The first collaborator viewed a Figma file an average of 10 days after creation, compared with 19 days in 2019. - This suggests cross-functional partners were being involved earlier in design. - Developers participated in 40% of collaborative files. - When developers joined, handoff typically began 33 days after design creation and continued for 45 days after the first code inspection. - Handoff activity often continued well after the final design edit. ## Collaboration Beyond Design - Teams increasingly used digital tools for activities traditionally held in person. - FigJam supported stand-ups, icebreakers, roadmapping, retrospectives, and other team exercises. - The shift reflects a broader move toward virtual-friendly collaboration across the entire product development process. Figma’s findings recommend treating design as a shared, end-to-end process rather than an isolated stage. Bringing cross-functional partners into FigJam and Figma early can improve collaboration across locations, disciplines, and the full path from concept to code.

design-collaborationfigmafigjamremote-work+2

figmaNov 15, 2021

Stay in the flow with redesigned comments | Figma Blog (opens in new tab)

Figma redesigned comments in Figma and FigJam to make feedback easier to discover, understand, and act on without interrupting design work. The updates encourage more collaborators to participate, promote shorter and more contextual feedback, and provide better tools for managing large volumes of comments. Overall, the redesign aims to keep teams in the flow while incorporating feedback. ## Inviting More Collaborators - The comment sidebar is now easier to find for viewers opening a file. - Comments are also more visible in prototype presentation mode. - These changes help unfamiliar collaborators discover where to leave and review feedback. - Figma hopes increased visibility will encourage more contextual input instead of feedback through separate tools—or no feedback at all. ## Encouraging Clearer Feedback - The comment composer was made smaller to encourage concise, easier-to-follow responses. - Reactions let users quickly express opinions, keep threads shorter, and lower the barrier to participation. - Collaborators can select an area of the canvas to leave broader feedback about multiple designs, groups of stickies, or a general concept. - Area-based comments preserve the context of feedback, whether it concerns a broad layout or a small design detail. ## Managing Feedback During Design Work - Comment pins are visible by default, making feedback harder to overlook. - Designers can keep comments open while editing the canvas, allowing them to reference feedback without leaving their workflow. - A simplified canvas view makes it easier to see where feedback is concentrated. - Comment pins display avatars and provide previews on hover. - Comments in the same area are grouped into clusters to reduce visual clutter. - Users can search comments by keyword or person and sort them by date. - Comments can be marked as “unread” as a reminder to return to them later. Figma’s redesigned comments make collaboration more accessible and structured, particularly during design critiques, sprints, and iterative review. The practical recommendation is to use concise, contextual comments and the new search, clustering, and unread features to keep feedback manageable.

design-collaborationfigmaprototypingfigjam+2

figmaAug 25, 2021

Figma for students and educators | Figma Blog (opens in new tab)

Figma’s Education plan gives students and educators free access to Professional features and unlimited collaboration. The platform supports virtual and hybrid classrooms by combining teaching materials, activities, critiques, and community in one shared space. It also helps students build practical design skills, portfolios, and professional connections. ## Figma for Educators - Figma enables real-time and asynchronous participation, making it useful for in-person, remote, and hybrid teaching. - Educators can consolidate lectures, assignments, activities, and critiques into a single file with multiple pages. - Shared files encourage iteration and feedback, helping quieter students participate more actively. - Visual collaboration can create a more inclusive classroom environment, including for deaf and hard-of-hearing students. - Teachers can use Figma to build community, such as creating collaborative class yearbooks with comments, stickers, and student profiles. - Figma offers group demos and shared teaching resources to help educators adopt the platform. ## Figma for Students - Working collaboratively in Figma exposes students to modern, cross-functional design workflows used in professional settings. - Students can preserve research, iterations, and design process—not just final visuals—for portfolio reviews and interviews. - Figma Community files allow students to learn through duplication, remixing, and studying other designers’ work. - Student groups, hackathons, and other community programs provide opportunities to build relationships and gain experience. - Education newsletters highlight career-related topics such as hiring preparation, portfolio reviews, and internships. Figma recommends that students and educators use the free Education plan to create collaborative classrooms, document design processes, and connect with the wider design community.

design-collaborationfigmaux-designui-design+2

figmaAug 15, 2021

Inside Figma: a Q&A with our 2021 interns and new grads | Figma Blog (opens in new tab)

The article shares career advice from four 2021 Figma interns and new graduates: Emily Jia, Langston Dziko, Daniela Velez, and Jago Pang. Their experiences show that early-career candidates should evaluate company culture, mentorship, ownership, growth opportunities, and alignment with a product’s mission—not just the role itself. Figma attracted them through its collaborative culture, enthusiasm for design, and opportunities to make meaningful contributions. ## Choosing an Early-Career Role - Emily looked for: - Data science roles matching her technical background and goals. - Fast-paced, product-focused work at growing startups. - An empathetic culture centered on communication and connection. - Daniela prioritized authenticity, community, and coworkers who cared deeply about Figma’s mission of making design more accessible. - Langston focused on career growth, asking: - Whether young engineers receive meaningful ownership. - Whether their work contributes to broader company goals. - Whether employees see opportunities to develop and stay long term. ## Using Internships and Conversations to Explore Options - Emily explored different companies through summer and off-cycle internships. - Conversations with alumni and interviewers helped her understand less obvious tradeoffs between roles. - She considered not only people’s day-to-day responsibilities, but also how they had grown in their positions—and whether she wanted a similar trajectory. - Langston used internships to identify the types of work he enjoyed and those he did not. - He also spoke with many engineers, repeatedly hearing that a supportive manager and team can matter as much as the specific project. ## Why They Chose Figma - Emily was influenced by a Figma blog post written by a software engineering new graduate. She valued that Figma gave early-career employees a platform to share their experiences. - She was especially interested in joining a growing data team making its first new-grad hires and deliberately developing its culture. - Langston was impressed by how enthusiastically Figma engineers spoke about the product. Their enthusiasm suggested he would own innovative projects while developing as an engineer. - Daniela first encountered Figma through a collaborative side project. She enjoyed the product’s collaborative design experience and connected with the company’s emphasis on individuality and community. - Jago credited Figma with helping launch his design career and wanted to support its mission of democratizing design, particularly through Figma for Education and the Figma Community team. The interview suggests that students and new graduates should use internships, informational conversations, and employee perspectives to assess both the work and the environment. The strongest early-career choice is likely to be a role offering supportive mentorship, genuine ownership, meaningful growth, and a mission the candidate cares about.

design-collaborationfigmadesign-systemsproduct-design+2

figmaJul 19, 2021

Inside Figma: a Q&A with our global sales team | Figma Blog (opens in new tab)

Figma’s global sales team operates as a product-led, consultative partner rather than a traditional vendor. Sales employees work closely with users, designers, product teams, and internal advocates to expand Figma’s impact across organizations. The team emphasizes collaboration, user empathy, continuous learning, and personal growth. ## Sales as a Partnership - Figma’s users are central to product development, community engagement, and internal operations. - Sales teams help organizations improve product development and scale creative processes. - Internal customer champions often become advocates for Figma, creating partnerships based on shared goals rather than transactional selling. - Sales involves more than designers; decision-makers include product, engineering, and other supporting roles. ## The Growing Importance of Design - Distributed work has increased the need for effective collaboration and accessible design tools. - Figma argues that design is moving to the center of product development. - Stronger design improves user experiences and can help businesses perform better. - The sales team helps organizations understand how Figma can connect designers and collaborators. ## Learning the Design Landscape - New sales employees receive structured onboarding, including a five-week program. - Team members learn from sales colleagues, designer advocates, and direct exposure to customer pain points. - Senior leaders may shadow support teams to better understand users’ challenges and product needs. - Continuous learning is treated as essential, even for employees without prior design experience. ## Product-Led Growth - Many prospective customers already use Figma, reducing reliance on conventional SaaS sales tactics. - Sales representatives can focus on helping existing users expand Figma’s role within their organizations. - Employees are drawn to the model because it feels more like advising and partnering than following a rigid sales cycle. - Figma’s strong product affinity and brand loyalty support this approach. ## A Collaborative Sales Culture - The team describes its culture as supportive, consultative, and low-ego rather than aggressively competitive. - Figma’s motto, “people over pipeline,” reflects its emphasis on personal development and employee well-being. - Success is recognized across the team instead of treated solely as an individual achievement. - Sales works cross-functionally with product and other departments, building relationships that support long-term growth. ## Career Growth - Joining Figma early offered employees the opportunity to help build sales processes from the ground up. - The organization’s rapid growth created opportunities for learning, leadership, and increased responsibility. - Employees were attracted by the chance to take risks, work in a scrappy environment, and develop alongside the company. Figma presents sales as an extension of its product-led philosophy: understand users deeply, collaborate across teams, and help customer advocates bring the product to more people.

design-collaborationfigmaproduct-designsaas+1

figmaMay 5, 2021

Q&A with Robyn Kanner | Figma Blog (opens in new tab)

Robyn Kanner’s Config 2021 interview presents design as an active, collaborative practice rather than a fixed professional identity. Alongside her work as Creative Director for the Biden-Harris campaign, her answers emphasize persistence, teamwork, cultural awareness, and making things without being constrained by titles or tools. Her central advice is to stay present, keep creating, and define success through meaningful impact. ## Designing the Biden-Harris Campaign - Kanner led the Biden-Harris design team during the 2020 U.S. presidential election. - The team created a wide range of campaign materials, from JoeBiden.com to the campaign plane, working together in one Figma file. - She identifies helping elect Joe Biden as the greatest accomplishment of her career. - Her Config 2021 keynote provides a deeper account of the campaign and its creative process. ## A Relentless and Unrestricted Creative Practice - Kanner describes her creative process as “relentless.” - She does her best work early in the morning and late at night. - She rejects the idea of perfect design, saying there is “nothing perfect.” - Her advice to young designers is not to limit themselves to a job title—or even think of themselves primarily as designers—but simply to make things and let the rest develop naturally. - Her definition of design is immediate and action-oriented: “‘NOW.’” ## Collaboration and Team Culture - Good collaborators create space for the people around them. - Teams become genuine teams by “going through shit together.” - Kanner’s answers suggest that shared pressure, trust, and mutual support matter more than formal processes. - When asked whom she would want in a design critique, she chooses Michael Jordan, reflecting an interest in high-performance perspectives beyond design. ## Influences, Tastes, and Perspective - Her favorite UI typefaces are Decimal and Mercury, and she values type, color, and multiple color systems equally. - She admires her parents for shaping who she is. - She considers sociology underrated and code overrated within the design world. - Outside design, she highlights Jeff Buckley, BROCKHAMPTON’s “BUZZCUT,” and the video game Madden as sources of enjoyment and decompression. - She dismisses comparisons with other designers, emphasizing that everyone has their own path. ## Tools, Constraints, and Figma - Kanner dislikes being limited by tools, particularly Safari’s handling of animations. - She praises Figma as having “revolutionized creating.” - Her favorite Figma feature is Shift+H, though she jokingly says she likes all of them. - Her ambition to “put gradients on Mars” captures her playful, expansive approach to design. The interview ultimately recommends a broad and practical view of creativity: make meaningful work, support the people around you, resist restrictive labels, and focus on the present rather than chasing perfection or comparison.

design-collaborationfigmaui-designtypography+4

figmaSep 23, 2020

Six integrations to help your product team collaborate in Figma | Figma Blog (opens in new tab)

Figma argues that its open platform and API help product teams connect design work with the tools used for documentation, development, feedback, and production. The integrations described keep designs current across workflows, reduce handoff friction, and help teams validate ideas with users before investing heavily in implementation. ## Confluence: Keep Documentation and Designs in Sync - Live Figma files and prototypes can be embedded in Confluence pages. - Product specifications and requirements remain connected to the latest designs. - Teams no longer need to manually replace screenshots whenever designs change. - Developers can review current designs directly within the documentation they use as a source of truth. ## GitLab: Connect Designs to Development Tasks - The GitLab plugin lets teams upload Figma designs directly into GitLab issues. - Developers can review designs alongside tasks, issues, and code changes. - Designs can be versioned and discussed in context, improving collaboration during sprints. - The integration reduces the need to move manually between tools. ## Avocode: Simplify Design Handoff - The Avocode plugin syncs finished Figma designs to Avocode projects. - Developers can inspect layers, export assets, and retrieve measurements and color values. - It supports copying code snippets in languages including CSS, CSS-in-JS, and React Native. - Designers can continue exploring in Figma while developers work from a stable, production-ready version. ## Pendo: Gather Feedback from Real Users - Pendo can embed live Figma wireframes and prototypes into targeted areas of a product. - Product teams can expose proposed features to specific user segments before development. - Feedback can be collected through surveys, open-text responses, and scheduled user interviews. - Early testing helps teams identify customer needs and problems before launch. ## Bubble: Turn Designs into Web Apps - Bubble allows teams to import Figma designs into a no-code web app workflow. - Each Figma frame becomes a page in the Bubble application. - Vectors are uploaded as images during the import process. - The integration shortens the path from visual design to implementation without requiring traditional coding. Overall, these integrations extend Figma beyond design by connecting it to documentation, issue tracking, developer handoff, user research, and no-code development. Teams can use them to maintain a shared source of truth and move more efficiently from concept to shipped product.

design-collaborationfigmagitlabreact-native+3

figmaSep 21, 2020

The many dimensions of trust in design | Figma Blog (opens in new tab)

Trust is presented as the foundation of open, inclusive design collaboration. Insights from Figma’s Config Europe show that trust grows through human relationships, clear communication, transparent processes, and space for honest disagreement. Teams that invest in these practices can give better feedback, collaborate more effectively with clients, and consider the broader impact of their work. ## Building Strong Relationships - Trust starts with understanding teammates and everyone involved in product development. - Informal conversations, quick calls, and regular check-ins can build connections more effectively than relying solely on email. - A foundation of trust makes design critiques more constructive because feedback is interpreted as supportive rather than threatening. - Teams should assume positive intent and develop empathy by learning about one another’s working styles and challenges. ## Embracing In-Progress Work - Clear communication and agreed-upon operating processes help build trust with both clients and colleagues. - Real-time collaboration in Figma exposes early design work, which can make designers uncomfortable when ideas are still evolving. - Teams should establish rules for shared files, including: - Clearly marking the stage of the design process with status annotations - Indicating whether feedback is currently welcome - Specifying the level or type of feedback needed - Project documents should reflect the current state of the work so clients and internal teams remain aligned. ## Opening the Dialogue - Trust also requires conversations about design ethics, technology, and the broader consequences of products. - Rakuten Viki designer Shirley Lai created “The Designated Dissenter,” a card game that encourages people of any role or seniority to challenge team assumptions. - The game assigns one participant to object to proposed ideas and structures discussion around stakeholders, values, and ethical questions. - Deliberately making room for dissent helps teams develop an open feedback culture and consider consequences beyond immediate project goals. Building trust takes time, but teams can make steady progress by getting to know one another, defining collaboration norms, keeping work transparent, and encouraging thoughtful disagreement.

design-collaborationfigmaproduct-designreal-time-collaboration+1

figmaAug 12, 2020

How we use Figma templates to facilitate collaboration at Shopify | Figma Blog (opens in new tab)

Shopify developed a standardized Figma template to make project files easier for designers, product managers, engineers, and other collaborators to navigate. The template applies Shopify’s lightweight “Get Sh*t Done” framework—Think, Explore, and Build—while presenting build-ready work first. Consistent file structure, clear status indicators, dates, links, and annotations reduce confusion about a project’s current state and next steps. ## The Problem: Collaboration Creates File Complexity - Figma makes collaboration easy, but projects accumulate designs, prototypes, feedback, and multiple versions over time. - Teams were using different file-organization methods, making it difficult to find: - The latest designs - Approved layouts - Prototypes intended for user testing - Relevant project context and contacts - Shopify’s template provides a predictable structure across files and helps teams start projects faster. ## The Template’s Project Structure - The template is based on Shopify’s “Get Sh*t Done” framework: - **Think:** Understand the problem space. - **Explore:** Investigate and test possible solutions. - **Build:** Finalize the chosen direction for implementation. - Pages appear in reverse process order, with build-ready work placed first so collaborators see the most important information immediately. - Teams should create the cover and project overview first, then begin documenting the Think phase before moving into exploration. ## Cover and Project Overview - The cover communicates: - Project name - Owning team - Current project status - A cover also makes files easier to identify in Figma’s grid view. - The status indicator should be updated as the project progresses. - The project overview provides: - Additional context - Links to briefs, research, and related documents - Contact information for questions and feedback - Links to documents or Slack profiles can be added directly to the Figma file for quick access. ## Think: Establish the Foundation - The Think section collects the information needed to understand the project and begin design work. - Useful content includes: - User flows and journey maps - Job stories - Design sprint explorations - Screenshots and previous designs - Inspiration and links to external documents - Its purpose is to preserve the project’s background and problem space before solutions are explored. ## Explore: Investigate Possible Solutions - Explore is the flexible collaboration area where teams diverge, test ideas, and converge on promising approaches. - Recommended practices include: - Create separate pages for different devices or form factors. - Add titles to explorations and flows. - Use badges to show the state of each exploration. - Add a date to every new page to indicate freshness. - Keep user-testing prototypes on separate pages. - Use sticky notes for commentary, ideas, and feedback. - This section is expected to contain substantial collaboration, comments, and alternative layouts. ## Build: Prepare the Chosen Direction - Once a solution is selected, move the relevant pages or layouts from Explore into Build. - This keeps finalized work separate from experimentation and makes implementation-ready designs easier to find. - The structure supports a clear transition from exploration to delivery while preserving earlier thinking and feedback. Using a shared template like Shopify’s gives every collaborator the same mental model for navigating Figma files. Teams should adapt the sections as needed, while consistently maintaining project status, dates, ownership, context, and a clear separation between exploratory and implementation-ready work.

design-collaborationfigmadesign-systemsprototyping+2