Figma

532 posts

figmaJun 7, 20212 min readCurated summary

Inside Figma: how our PM team uses FigJam | Figma Blog

Figma’s product management team uses FigJam throughout the product-development lifecycle, not just for early-stage brainstorming. They rely on collaborative templates to shape strategy, generate ideas, plan roadmaps, run retrospectives, and stay aligned in weekly meetings. The broader conclusion is that a flexible visual workspace can strengthen both execution and team rituals, especially for distributed teams. ## Developing a Product Vision - The team uses a product vision board to define short- and long-term priorities. - The board connects user needs, potential features, and business goals. - Visualizing these elements helps validate strategy and show how individual plans support broader objectives. - FigJam makes it easy to capture rough ideas without focusing prematurely on wording or polish. ## Brainstorming Ideas with Crazy 8s - The PM team uses the “Crazy 8s” framework to generate many ideas quickly. - Participants have eight minutes to create eight possible solutions to a problem. - The emphasis is on speed and quantity rather than detailed refinement. - Afterward, the team shares ideas and discusses which concepts are worth pursuing. ## Building and Visualizing Roadmaps - FigJam supports structured planning as well as freeform exploration. - The team uses a Gantt chart to map projects and build product roadmaps. - A visual timeline clarifies each project’s scope, reach, staffing needs, and resource requirements. - It also exposes conflicts and helps the team identify when priorities need to change. ## Running Retrospectives - Product, engineering, and design teams use recurring templates to review product execution. - Marketing, support, and product education teams apply similar retrospectives to go-to-market work. - Sessions focus on what went well and what could improve, creating visibility across teams. - The team also retrospectives its internal processes to ensure they continue working as the organization grows. ## Staying Connected in Weekly Meetings - The PM team meets weekly in a shared FigJam file to exchange updates and maintain alignment. - Prompts cover difficult problems, exciting or concerning developments, and personal updates. - Cursor chats, stickers, and emotes make remote meetings more interactive. - Figma turned this meeting structure into a reusable template for other teams. Figma presents FigJam as a workspace that can support the entire product process. Teams can start with the provided templates and adapt them for strategy, collaboration, planning, reflection, and remote communication.

Figma Figjam Product Management Brainstorming+3

figmaJun 3, 20212 min readCurated summary

Pride 2021: Getting back out there | Figma Blog

Figma’s 2021 Pride post presents Pride as both a celebration of LGBTQ+ identity and a continuation of the community’s history of resistance. Clancy Slack describes how Figma’s Pride Employee Resource Group creates space for authenticity and belonging, especially after the isolation and injustice of 2020. As in-person events began returning, Figma invited the broader design community to express Pride through posters made and shared in Figma Community. ## Figma’s commitment to community and belonging - Figma’s mission of making design accessible extends to building inclusive communities. - Figma Community connects hundreds of thousands of users who collaborate and create together. - Employee Resource Groups help Figmates connect around shared identities and experiences. - The Pride ERG, founded in 2019, provides LGBTQ+ employees with a space to be open, authentic, and supported. - During Maker Week, the group explored Pride iconography and collaboratively designed original artwork. ## Pride’s history and renewed significance - Pride offers LGBTQ+ people a rare opportunity to celebrate openly, feel safe, and connect with their community. - The occasion commemorates the 1969 Stonewall Uprising and the history of resistance to anti-LGBTQ+ discrimination and police raids. - The pandemic and widespread reminders of injustice made community and solidarity especially important in 2020. - With vaccinations increasing and cities preparing for in-person parades, Pride represented a hopeful return to public celebration. ## A call for Pride posters - Figma encouraged designers, artists, and makers to create Pride posters using the platform. - Participants were asked to publish their work to Figma Community with the hashtag **#pride**. - Posters could be printed for local parades or used to celebrate Pride at home. - Figma planned to feature selected designs in a curated Community collection. - The post highlighted employee-created designs, including messages such as “Show your true colors” and “Love is Love.” - A Figma template provided standard sizing and printing guidance. Figma’s central recommendation is to use creative collaboration to strengthen visibility, connection, and LGBTQ+ community celebration—bringing Pride back into public spaces while keeping its history and purpose in view.

Figma Design Systems Collaborative Design Figma Community

figmaMay 31, 20212 min readCurated summary

Embracing the mess at Config 2021 | Figma Blog

Config 2021 emphasized that product development is inherently messy, and setbacks, conflicts, and failures can ultimately improve teams and products. The central recommendation is to treat difficult moments as learning opportunities: step back from failed work, communicate openly, and intentionally preserve what can be learned. ## Learning from Setbacks Shanique Shields of Shopify described discovering that a feature she had worked on for 18 months would be rolled back. Initially, she felt personally responsible, but taking a break helped her recognize the experience’s value. - **Don’t personalize feedback:** Stakeholders may simply have different perspectives or priorities; criticism is not necessarily a judgment of the designer or the work’s quality. - **Document the process:** Preserve design decisions, Figma comments, and personal notes, even when work does not ship. These records help future projects and allow others to learn. - **Be intentional about growth:** Identify the skills, business knowledge, or cross-functional experience gained from each project. - **Start the next project positively:** Use a new workstream as a fresh start and rally the team around a shared goal. ## Addressing Conflict Through Openness Frank Bach of Headspace argued that even strong teams experience communication breakdowns. The best response is to address friction directly rather than allowing problems to grow. - Be transparent about concerns and listen carefully to the other person’s perspective. - Approach difficult conversations candidly and objectively. - Ignoring conflict prevents teams from making progress. - Practice gratitude by recognizing the value of design work, teammates, and collaborative opportunities. The article’s practical message is to embrace the difficult parts of product work. Teams become more resilient when they reflect on failure, communicate courageously, and carry lessons from messy experiences into future projects.

Figma Design Systems Product Development Project Management+2

figmaMay 26, 20212 min readCurated summary

Q&A with Dantley Davis | Figma Blog

Dantley Davis’s Config 2021 Q&A presents design as intentional problem-solving shaped by curiosity, collaboration, and diverse perspectives. He emphasizes using adversity and data to create meaningful impact, while staying humble and avoiding ego-driven design culture. His answers also highlight the importance of cross-disciplinary knowledge, personal creativity, and building inclusive teams. ## Design Philosophy and Creative Practice - Davis describes his creative process as “intentional.” - The best design solves an unrecognized problem so effectively that people cannot imagine life without it. - He defines design as problem-solving through form and function. - His greatest design fear is producing work that receives no reaction. - He dislikes designing primarily for oneself. - He values data as an underused tool for informing design decisions. - His favorite UI font is Montserrat; he prefers Akzidenz-Grotesk for type, hex colors, and specifically `#000000`. ## Collaboration and Team Culture - Good teammates are curious and ego-free. - Teams feel cohesive when members: - Seek feedback because they trust one another. - Inspire each other through their work and perspectives. - Set aside personal ego. - Davis considers building the most diverse team in tech his greatest career accomplishment. - He views mentorship as an important part of his role in the Design Twitter community. ## Leadership and Professional Growth - Davis is skeptical of the emphasis placed on being a “thought leader.” - He encourages young designers to study business, engineering, and finance to become more well-rounded thinkers. - He admires Issa Rae for combining writing, producing, and acting while remaining authentic to her story. - He credits personal time and side projects with helping him do his best creative work. - He regrets that one shipped product remained available too long after it stopped meaningfully benefiting users. ## Design Inspirations and Future Ambitions - Davis would like to design a car interface and would love to shape Porsche’s entire ecosystem, from driving to its app. - He admires designer Clement Mok and would invite him to critique his team’s work. - He praises Roblox for enabling children to play, socialize, and build rather than merely consume content. - He enjoyed Afrotech’s virtual conference, especially its combination of online access and a feeling of presence. - His favorite Figma feature is Observation Mode. Ultimately, Davis advocates for intentional, user-centered design supported by data, interdisciplinary learning, honest feedback, and inclusive collaboration.

Figma Design Systems Web Design User Interface Design+2

figmaMay 24, 20213 min readCurated summary

In the file at Config 2021 | Figma Blog

Config 2021’s breakout sessions emphasized practical systems for building products and teams. Coda’s Helena Jaramillo described how to create a strong product vision without existing user data, while Stripe’s design team shared principles for meeting immediate needs without sacrificing long-term scalability. Both approaches rely on context, shared perspectives, strong foundations, and thoughtful communication. ## Building a Vision from Zero to One - At Coda, Helena Jaramillo worked on a publishing platform designed to help users share best practices and discover documents. - Because the product was new, the team lacked existing user behavior, research participants, and historical data. - Helena built context by studying competitors and adjacent products, annotating screenshots in Figma, and identifying useful or unsuitable patterns. ## Developing a Strong Product Perspective - The team explored what publishing on Coda should feel like: a blog post, a no-code app, or a website. - They used Helena’s publishing experience and internal discussion to form a shared point of view. - Two priorities emerged: - Make publishing interactive documents easy. - Help publishers feel proud of and recognized for their work. - These principles shaped features such as simple publishing flows, photos, subtitles, and bylines. - When user insights are unavailable, a team can rely on collective intuition and expertise—but only by aligning around a clear perspective. ## Communicating the Broader Story - Helena created a “tl;dr page” in Figma to align cross-functional partners. - Rather than documenting every feature, the page used a short flow and several mockups to show the product narrative. - The goal was to make the intended experience understandable without requiring deep project context. ## Designing for Immediate Needs and Long-Term Scale Stripe’s Connie Yang, Tayler Aitken, and their team focus on simplifying complex processes for businesses and end users. Their approach combines urgency with long-term planning. - **Think in long time scales:** Stripe uses a “city planner mentality,” considering how systems connect, handle growth, and respond to future needs—potentially as far ahead as 2030. - **Lay strong foundations:** Teams should invest in fast, accessible products and scalable systems instead of short-term fixes. - Stripe’s design-system color tables, for example, include contrast and accessibility ratings, embedding quality requirements directly into the infrastructure. - **Prioritize rigor and quality:** Because Stripe handles payments and payouts, user trust is essential. The team accepts additional complexity when it produces a more reliable, polished experience. The practical recommendation is to combine strong early judgment with durable systems: build enough context to form a clear vision, communicate that vision simply, and make foundational decisions that continue serving users as the product grows.

Figma Design Systems User Experience Product Design+2

figmaMay 16, 20213 min readCurated summary

Inside Maker Week: more than a hackathon | Figma Blog

Maker Week is Figma’s twice-yearly, company-wide alternative to a traditional hackathon. It gives employees across disciplines, teams, and time zones dedicated time to pursue creative projects without requiring technical expertise. The program has produced hundreds of ideas since 2018, many of which became product features, community tools, or cultural initiatives. ## A Maker Culture Open to Everyone - Figma defines “maker” broadly—not just as an artist, engineer, or craftsperson, but as anyone expressing creativity in an authentic way. - The company reinforces this culture during weekly All Hands meetings, where new employees explain how they are makers. - This inclusive definition allows people who see themselves as curators, organizers, educators, or collaborators to participate. ## Maker Week as a Cross-Functional Festival - Maker Week happens twice a year and pauses normal day-to-day work for a week of experimentation and connection. - Unlike many hackathons, which can favor engineering, product, and design teams, Maker Week invites employees from every function. - Projects have included: - Recruiter-created employee baseball cards for candidates. - An intern-built “Name That Figmate” game. - A chemistry lesson taught through baking by data scientists. - The format encourages cross-pollination, shared ownership, and a better understanding of how different teams contribute to Figma. ## From Experiments to Shipped Work - Figma has held five Maker Weeks since 2018, generating hundreds of projects. - Some projects have become externally released products or features, including: - Auto Layout. - Interactive components. - Figma plugins. - The company suggests that FigJam itself may represent the culmination of multiple Maker Week experiments. - Other projects, such as *Figma in Quarantine: The Musical*, have offered glimpses into Figma’s internal culture. ## Featured Maker Week Projects ### Empathy-Building Cards - Research, sales enablement, and brand design employees created cards combining user personas with different characteristics and situations. - The cards help Figmates better understand users’ perspectives and contextualize the challenges they face. - The project was shared with the broader Figma community. ### Figma in 3D - An engineer and product support employee collaborated to create an extension that projects layers off the canvas. - Users can orbit around the design with a mouse, making Figma feel more like a 3D mapping application. - The project explored new possibilities for spatial software. ### User Collaboration Data Visualization - A data scientist and enterprise sales employee built a Mode-based map showing collaboration between users in different countries within the same domain. - The visualization helps organizations understand how teams collaborate across regions and time zones. Maker Week demonstrates that innovation does not have to come only from formal product teams. Figma’s approach recommends creating structured time for broad participation, experimentation, and cross-functional collaboration—while allowing the most promising ideas to evolve into real products or cultural initiatives.

Figma Figjam Figma Plugins Data Visualization+1

figmaMay 12, 20212 min readCurated summary

Shifting team culture at Config 2021 | Figma Blog

The Config 2021 sessions argued that inclusive, collaborative design depends on building cultures of transparency, trust, and shared participation. Speakers emphasized two complementary practices: acknowledging people’s real emotions and circumstances, and creating accessible spaces where newcomers and diverse perspectives can contribute. The overall conclusion was that teams cannot create inclusive experiences alone; they need intentional routines, open resources, and community support. ## Embracing Vulnerability - Figma researcher Nannearl Brown described how openness about personal struggles can create a more supportive team culture. - Team members were encouraged to share: - How they were feeling - What support they needed - What they were focusing on during the day - Daily Slack stand-ups included non-work activities—such as exercise, hobbies, or family time—to encourage work-life balance and help teammates understand one another. - Support requires more than listening; teammates should make room for each other’s emotions, experiences, and difficult moments. - The central message was that people do not need to appear fine all the time. ## Creating Inclusive Spaces - Bitcoin designers Johns Beharry and Christoph Ono noticed that Bitcoin design resources often excluded people without technical expertise or geographic access. - They responded by building shared spaces where experienced designers could support newcomers, including: - A Slack community - GitHub resources - The Bitcoin Design resource hub - Weekly community calls - The open-source Bitcoin Design Guide - The resources were designed to work across cultures, regions, languages, and levels of technical knowledge. - Their goal was to create a friendly environment that encouraged broader participation and more diverse perspectives. - They argued that inclusive and accessible design requires collaboration with people who bring different experiences. ## Building Collaborative Culture - Design is inherently collaborative and benefits from varied experiences and perspectives. - Inclusive culture helps more team members and collaborators participate in the design process. - Trust and transparency are developed through both interpersonal habits—such as honest check-ins—and structural tools that make knowledge widely accessible. Teams seeking a more inclusive culture should normalize vulnerability, establish supportive communication routines, and create shared resources that invite participation from people with different backgrounds and levels of expertise.

Figma Open Source Github Slack+2

figmaMay 5, 20213 min readCurated summary

Q&A with Robyn Kanner | Figma Blog

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.

Figma User Interface Design Collaboration Typography+4

figmaApr 26, 20212 min readCurated summary

Introducing branching: space to iterate and explore freely | Figma Blog

Figma introduced branching in beta to help large design teams experiment without risking changes to shared files. The feature combines the freedom of isolated exploration with Figma’s multiplayer collaboration, while keeping the main file as the approved source of truth. Branches are auto-saved and can later be merged into the main file by editors. ## The challenge of decentralized design systems - Design systems were spread across teams and tools, creating inconsistencies and forcing designers to switch contexts. - Centralized systems improved reuse and efficiency but introduced governance challenges. - In large systems such as Netflix’s Hawkins, many contributors may update files, even when the latest changes are not approved for production. - Teams needed a way to protect shared libraries while still allowing designers to explore new ideas. ## Branching built around simplicity - Figma considered traditional workflows involving commits and nested branches too complex. - The product adopted two principles: simplicity and consistency. - Branches work within Figma’s existing multiplayer model, retaining real-time collaboration. - Work is automatically saved, eliminating the need for explicit commits. - Designers can create a branch from any file, experiment safely, and merge approved updates into the main file. ## Future plans and availability - Figma planned to expand branching with features such as reviews. - The company was also exploring a unified approach to versioning across branching and multiplayer workflows. - The beta initially launched for Organization-plan customers, with access granted gradually. Branching is intended to let organizations centralize their design systems without limiting experimentation. Teams managing shared libraries should use branches for exploratory work and merge only reviewed, approved changes into the main file.

Figma Design Systems Collaboration Version Control+2

figmaApr 20, 20212 min readCurated summary

Introducing FigJam | Figma Blog

FigJam is Figma’s online whiteboard for collaborative brainstorming and early-stage design. Figma argues that remote work and the shift toward cross-functional collaboration have created a need for more informal, shared online spaces—not just tools for producing finished designs. FigJam addresses this with a lightweight, approachable environment that connects directly to Figma. ## Why Figma Built FigJam - Remote work has reduced in-person collaboration and increased reliance on online tools. - People were already using Figma for activities beyond interface design, including games, icebreakers, meal planning, and brainstorming. - These uses showed that teams wanted a place to share ideas and connect without necessarily designing products. - Figma concluded that these interactions needed a dedicated space where non-designers felt welcome while designers still felt at home. - The product also supports Figma’s broader goal of making design accessible to everyone by involving more people earlier in the design process. ## FigJam’s Role in Early-Stage Design - FigJam is described as a lightweight, easier-to-learn version of Figma for ideation and brainstorming. - Teams can use it to: - Define user problems - Gather inspiration - Explore product ideas - Map user flows - Build and document processes - Multiplayer tools include sticky notes, emojis, drawing tools, stamps, and cursor-based chats. - Shapes, lines, and connectors make diagramming and systems thinking easier. ## Collaboration and Connection - Built-in audio lets teams discuss ideas without switching to a phone or video call. - FigJam integrates seamlessly with Figma, allowing work to move from initial concepts through final prototypes in one ecosystem. - Expressive features such as emojis, stamps, and cursor chats are intended to make collaboration feel warmer, more spontaneous, and more enjoyable. - The product is designed to combine practical functionality with the informal energy of “hanging out” together online. ## Early Users and Pricing - Teams at Stripe, Netflix, Salesforce, Twitch, and Discord tested FigJam during its development. - Discord’s design leadership praised it as a focused, uncomplicated version of Figma suitable for brainstorms, retrospectives, and similar activities. - FigJam was free for everyone through the end of 2021. - Planned 2022 pricing included free and paid plans costing $3 and $5 per editor per month. FigJam’s central promise is to give distributed teams an inviting, collaborative space where product ideas can emerge before formal design work begins.

Figma Figjam Collaboration Design Thinking+3

figmaApr 20, 20212 min readCurated summary

Coming together at Config 2021 | Figma Blog

Figma’s Config 2021 announcements focus on making design more collaborative and accessible to broader teams. The company introduced tools for brainstorming, safe experimentation, mobile review, live discussion, and large-scale participation. Together, these updates reflect Figma’s shift from a specialized interface-design tool toward a broader collaborative workspace. ## FigJam for Brainstorming - FigJam is a new whiteboard space for brainstorming, diagramming user journeys, and exploring ideas. - It includes features such as emotes and chats to recreate some of the spontaneity of in-person collaboration. - Released in open beta, it was initially free through February 2022, with planned free and paid tiers afterward. ## Branching for Safer Iteration - Branching lets users create independent versions of a file to explore ideas without changing the main design. - Teams can collaborate within branches using Figma’s multiplayer tools. - Completed work can be merged back into the main branch. - The feature is available in beta for Organization-plan customers and is intended to support design-system contributions and large-team workflows. ## Mobile Access and Review - New iOS and Android apps make files and prototypes easier to access from anywhere. - The apps improve the mirrored playback experience, helping designers preview how work appears on actual devices. - The mobile app was launched in beta, with a broader release planned. ## Audio Collaboration - Audio allows teammates to start calls directly inside Figma or FigJam. - It supports live design critiques, group brainstorming, and discussions without leaving the editor. - The feature was planned for Professional and Organization plans. ## Larger Multiplayer Sessions - Figma increased its limit to 500 concurrent users: 100 editors and 400 viewers. - The company planned to raise the limit to 1,000 users across Figma and FigJam, with 200 editors and 800 viewers. - These limits support large presentations, workshops, classrooms, and other emerging collaborative uses. ## Publishing to the Figma Community - Everyone can publish files, templates, techniques, and other resources to the Figma Community. - Users can both discover work from others and share their own contributions. - FigJam templates were highlighted as an early example of this expanded community ecosystem. Figma’s Config 2021 updates recommend a broader model of design collaboration: teams can ideate in FigJam, experiment through branching, review work on mobile, communicate through audio, and share results with the wider community.

Figma Design Systems Figjam Collaborative Design+3

figmaApr 6, 20212 min readCurated summary

How Repsol rethinks the way the world interacts with energy | Figma Blog

Repsol is using design to make energy more understandable and encourage consumers to participate in the transition toward sustainable energy. After creating its first internal design team, the company partnered with Mendesaltaren to build the Oxygen design system in Figma. The system unified design across products, improved collaboration, and reduced product implementation work by 30%. ## Making Energy More Tangible - Repsol’s design team aims to “humanize” energy and help people become active participants in how it is produced and consumed. - An electric car-sharing app shows users how much energy they consume while driving and rates their efficiency. - Another app feature lets users see where their electricity comes from, including nearby solar panels and wind turbines, alongside current weather conditions. - These experiences turn energy from an abstract bill into something visual and interactive. ## Building One Design Language - Repsol serves diverse audiences, including drivers, industrial customers, employees, and teams managing refineries and supply chains. - Before the design system, different products taught users different interaction patterns and languages. - The Oxygen design system provides shared patterns, components, interaction guidelines, and developer guidance. - Built in Figma, it creates consistency across products while allowing teams to adapt designs to different purposes and audiences. ## Figma as the Collaboration Hub - Figma became the central workspace for design, communication, feedback, and executive presentations. - Repsol can work simultaneously on more than 15 projects across internal and external teams while maintaining consistency. - Designers replaced tools such as Sketch, InVision, and PowerPoint. - Product owners, technology leads, and executives can review and iterate on designs in parallel. ## Measuring Design’s Impact - Mendesaltaren developed two plugins to help Repsol measure design performance: - **Figmetrics** tracks how components are used across Figma files. - **MSVM** keeps design, product, business, and technology teams aligned around a shared source of truth. - The new system and processes reduced implementation work by 30%. - Repsol can now track savings in time, money, and effort, making design’s business value more visible. Repsol’s experience shows how a centralized design system can improve efficiency while making complex subjects more accessible. By connecting consistent design practices with measurable results, the company is using design as a tool for both digital transformation and its transition toward net-zero energy.

Figma Design Systems User Experience Product Development+3

figmaApr 5, 20212 min readCurated summary

About Figma’s new Starter plan | Figma Blog

Figma’s updated free Starter plan, launched April 21, 2021, prioritizes unrestricted multiplayer collaboration over unlimited shared files. Drafts remain an unlimited personal workspace, while team spaces gain unlimited editors but are limited to three files with three pages each. Figma concluded that removing the arbitrary two-editor cap would better let teams experience real-time collaboration. ## Changes to the Starter Plan - Drafts become a personal workspace: - Unlimited files, pages, and viewers remain available. - Co-editing requires moving a file into a team space. - Team spaces now support: - Unlimited editors. - A maximum of three files. - Up to three pages per file. - Existing files, pages, and projects created before the rollout were not moved or altered. - FigJam was also introduced to all plans with unlimited usage during its beta period. ## Why Figma Removed the Editor Limit - Collaboration is central to Figma’s browser-based product and often the main reason teams choose it. - The previous two-editor limit prevented users from experiencing the full benefits of multiplayer design. - Figma considered simply increasing the editor limit but decided any fixed number would be arbitrary. - The new approach supports teams ranging from two collaborators to dozens of teammates. ## Results from User Testing - 87% of users were excited about unlimited editors in team spaces. - Teams collaborated 29% more after the two-editor restriction was removed. - Users typically worked actively on only two or three files at a time, making the new team-space limits seem reasonable. - Unlimited files remained available in Drafts for personal work. ## Rollout and Additional Options - Figma announced the changes ahead of the April 21, 2021 rollout. - Users received notifications through email and the Figma app. - Students and educators could apply for the Figma for Education plan, which provided Professional-plan features for free. The updated Starter plan was designed to make Figma’s multiplayer experience accessible to teams of any size while reserving broader file capacity for paid plans.

Figma Figjam Collaborative Design Real Time Collaboration+1

figmaMar 30, 20212 min readCurated summary

Behind the feature: building multi-account | Figma Blog

Figma’s account switcher addresses a simple but widespread need: users often move between work, freelance, personal, and hobby projects. The feature lets people switch between separate workspaces while maintaining one public identity in Figma Community. Figma concluded that supporting multi-account use required rethinking the relationship between private creation, workspace boundaries, and public sharing. ## A Growing Need for Multiple Workspaces - Figma had expanded beyond product design into brainstorming, presentations, maps, vector art, wedding planning, and fan art. - Users increasingly relied on Figma both inside and outside their companies. - Many people had distinct roles—employee, freelancer, and hobbyist—but no straightforward way to move between them. - User feedback consistently identified multiple-account support as a major request. ## The Account Switcher - The new account switcher allows users to toggle easily between different Figma accounts and workspaces. - It replaces cumbersome workarounds for separating professional and personal projects. - Users can keep work projects and personal files distinct while remaining within a unified Figma experience. ## Separating Creation from Sharing - Designing and collaborating may require switching freely between accounts. - Sharing work introduces different concerns, including ownership, attribution, comments, and public identity. - Users can maintain a single public Figma Community profile and handle while changing jobs, companies, or creative contexts. - This preserves a consistent public brand without mixing personal work with company projects. Figma’s multi-account design treats account switching as more than a convenience feature: it establishes a foundation for separating workspaces while unifying a user’s public presence.

Figma Collaboration Workspaces Multi Account+2

figmaMar 29, 20212 min readCurated summary

Behind the scenes of creating the official Figma kit for Tailwind UI | Figma Blog

Tailwind Labs created an official Figma kit to meet strong customer demand for Tailwind UI designs. Building it required translating more than 400 responsive code components into over 1,400 Figma components and 10,000 elements, with the final code serving as the pixel-perfect reference. The project showed that a production design kit needs rigorous structure, naming, responsive modeling, and reusable variants—not just visual accuracy. ## Building a Design File as a Product - Unlike exploratory product files, a commercial design kit is itself the final deliverable. - Every decision affects usability, including: - Layer names - Component structure - Page organization - Variant behavior - The team used the finished HTML and Tailwind CSS components as the standard the Figma files needed to match. ## Consistent Layer Naming - Consistent names allow Figma overrides to persist when users swap component instances or variants. - For example, a button’s text layer was always named “Text,” allowing customized text to carry over when changing button sizes. - This becomes especially valuable in complex components containing icons, headings, paragraphs, and links. ## Mirroring HTML Structure in Figma - Auto Layout, layout grids, and constraints let Figma layers approximate HTML structure and browser layout behavior. - Matching design and code architecture helps designers and developers share an understanding of what layouts can support. - It also exposes recurring implementation patterns, such as responsive padding and centered max-width containers, which developers can turn into reusable layout utilities. ## Using Variants to Simplify Components - Instead of maintaining dozens of separate components, the team combined options into configurable variants. - A single Badge component could cover type, size, theme, and optional secondary elements. - Variant properties were named consistently with code component properties, using terms such as: - Type - Size - Theme - Position - Breakpoint - State - Variants made components more discoverable and reduced duplication. - The completed kit contained 1,430 components averaging seven variants each; without variants, it would have exceeded 10,000 components. ## Scale and Quality Control - Over several months, the team built and rebuilt more than 1,400 components and 10,000 distinct elements. - The project emphasized detailed auditing and pixel-level consistency, although the provided article excerpt ends before describing that process. The main recommendation is to treat a shared Figma kit like a carefully engineered product: align it closely with the codebase, establish naming and structural conventions early, and use variants to keep a large responsive system manageable.

Figma Design Systems CSS HTML+3