Collaboration | Techlist.io

figmaJul 17, 20192 min readCurated summary

A step-by-step guide to using Figma for retrospectives | Figma Blog

Figma can make agile retrospectives more inclusive and collaborative than a traditional whiteboard. Its multiplayer editing, comments, components, and remote-friendly workflow let everyone contribute simultaneously and clearly. The article recommends using retrospectives as both a practical meeting format and a low-pressure way to introduce a team to Figma. ## Sharing and Permissions - Create a Figma file or duplicate the provided retrospective template. - Use the blue **Share** button to invite teammates by email or generate a link. - Ensure anyone with the link has editing permission if the whole team should participate. ## Organizing Feedback with Frames - Divide the canvas into three frames: - What should we continue doing - What should we stop doing - What should we start doing - Apply constraints to headers, backgrounds, and other child elements. - When a frame is resized to provide more writing space, constrained elements adjust automatically. ## Using Sticky Note Components - Provide sticky note components so participants can quickly add feedback. - Duplicate notes with **Command + D** or by holding **Option/Alt** while dragging. - Component instances support overrides, allowing users to change text, colors, and effects without altering the master component. - Multiplayer cursors and shared visibility make the process engaging for in-person and remote participants. - Remote teammates can follow the discussion directly in the file instead of relying on a camera pointed at a physical whiteboard. ## Customizing the Template - Add the company logo and customize Figma styles with brand colors. - Create components for common interactions, such as “+1” markers for agreement or items needing further discussion. - Design themed cover pages when creating a new file for each retrospective. - Export completed frames for documentation or sharing. Figma’s collaborative canvas provides a flexible alternative to physical whiteboards, especially for distributed teams. Starting with the template and adapting its frames, components, and visual styling can make retrospectives more accessible while encouraging broader adoption of Figma.

Read original

Collaboration Figma Design Systems Agile+1

figmaFeb 13, 20192 min readCurated summary

Figma Raises $40MM Series C Round led by Sequoia | Figma Blog

Figma announced a $40 million Series C funding round led by Sequoia Capital, with participation from new and existing investors. The funding supports Figma’s mission to make visual design accessible, collaborative, and web-based. The company plans to expand its enterprise offering, improve performance and design-system tools, develop extensibility, and strengthen its global community. ## Funding and Strategic Investors - Sequoia Capital led the round, joined by Coatue, Founders Fund, Jeff Weiner, Mike Krieger, Andrew Wilson, Dan Rose, and existing investors Index, Greylock, and KPCB. - Figma selected investors with experience building enduring companies and communities. - The company highlighted Sequoia’s investments in GitHub and PlanGrid as evidence of relevant expertise. ## Expanding Collaborative Design - Figma argues that productivity software is increasingly becoming collaborative and shared. - Major design teams at Square, Uber, Twitter, and GitHub had adopted Figma. - The new funding will support: - Expansion of Figma Organization, its enterprise offering - Improvements for individual designers and small teams - Continued development of collaborative workflows ## Performance and Design Systems - Despite being viewed as faster than native competitors, Figma sees significant opportunities to improve loading and rendering performance. - With more than one million signups, the company emphasizes delivering a high-quality experience at scale. - A major focus is making Figma the best platform for building and managing design systems. ## Platform Extensibility - Figma is developing platform and extension capabilities to support varied design workflows. - The company is deliberately avoiding a fixed release timeline because extensions must be stable and secure. - Extensibility is presented as essential to making the design process genuinely open. ## Building a Global Community - Around 80% of Figma’s weekly active users were located outside the United States. - The company had 26 user groups in cities ranging from Lagos to Toronto. - Figma planned to improve connections among users worldwide through meetups, local groups, and other community initiatives. - Community is described as a foundation for Figma’s future and a key reason Sequoia was an appealing partner. Figma intended to use the Series C investment not simply to grow the business, but to deepen its collaborative product, improve its technical foundations, and build a global community around accessible design.

Read original

Collaboration Figma Design Systems Design Tools+2

figmaJan 16, 20192 min readCurated summary

Figma's engineering values | Figma Blog

Figma’s engineering values were created to preserve effective collaboration as the team grows without promoting a monoculture. They are intended to describe existing behaviors, guide decisions, and make explicit the tradeoffs behind how the team works. The post focuses on communication, teamwork, feedback, inclusion, and sustainable growth. ## Communicate Early and Often - Share design documents, product specifications, architecture sketches, and works in progress before implementation is complete. - Early communication helps teams: - Identify problems before significant effort is invested. - Solve problems collaboratively rather than in isolation. - Encourage people to ask for help and exchange knowledge. - Feedback must be welcomed as seriously as it is requested; sharing is useful only when people are receptive to changing direction. - Communication is not a rigid process: - Code may be the clearest way to discuss an idea. - Simple bug fixes or obvious changes may not require extensive discussion. - This value rejects the “solo genius” model in favor of using the team’s collective expertise. - The tradeoff is slower decision-making: involving more people can require additional discussion and iteration to ensure diverse voices are heard. ## Lift Your Team - Engineers should help one another grow, prioritize teammates’ success and well-being, and create an inclusive environment. - The emphasis is on lifting the team—not sacrificing individual sustainability for the company’s interests. - The value supports: - Continuous learning and mentorship. - Weekly technical talks. - Formal onboarding mentorship. - Encouragement to develop new skills. - Feedback should focus on ideas and work rather than attacking individuals. - Insults, condescension, and belittling are considered ineffective feedback. - Team members are also expected to receive feedback thoughtfully and remain open to others’ ideas. Figma’s approach is to make collaboration and mutual growth explicit expectations while acknowledging their costs. Teams adopting similar values should define concrete behaviors, ensure feedback is genuinely welcomed, and state the tradeoffs they are willing to accept.

Read original

Collaboration Code Review Software Engineering Software Architecture+2

figmaMar 18, 20182 min readCurated summary

Now you can name and annotate your Figma Version History | Figma Blog

Figma introduced named and annotated Version History to make design changes easier to organize, review, and restore. Because Figma continuously autosaves files in the browser, users can now mark important milestones instead of sorting through a long list of automatic saves. The update aims to reduce export work, improve collaboration, and help teams review designs more efficiently. ## Organizing Design Milestones - Designers can manually flag important versions and give them names and notes. - Autosaves between marked versions are automatically collapsed, making the history easier to scan. - Important milestones can be restored or duplicated into new files. - Version History is available through a file’s name menu and “Show Version History.” ## Page-Specific Version History - Version History can now be viewed for individual pages rather than only for the entire file. - This reduces noise when different pages contain unrelated changes. - To access it, open a page, select the file name, and choose “View Version History.” ## Notes for Faster Design Review - Notes can explain what changed in each revision. - Stakeholders can review design stages and leave feedback directly within Version History. - The feature is intended to reduce meetings and speed up design feedback cycles. ## Keyboard Shortcut - macOS: `⌘ + ⌥ + S` - Windows: `Ctrl + Alt + S` - The shortcut quickly saves and names a selected version. The update builds on Figma’s autosave system by adding deliberate checkpoints and context. Teams can stay in their design workflow while preserving, reviewing, and discussing key stages without exporting files.

Read original

Collaboration Figma Version History Autosave+1

figmaNov 28, 20172 min readCurated summary

Advanced Project Permissions for design systems | Figma Blog

Figma introduced Advanced Project Permissions to give design-system teams finer control over who can edit or access projects. Available to paying Professional Teams, the feature adds view-only and invite-only options alongside the existing team-wide editing model. It is designed to protect systems from accidental changes while allowing maintainers to develop and test privately. ## Why Design Systems Need More Control - Design-system maintainers often need to work privately before releasing components to the broader organization. - Once published, the system should be protected from accidental edits by designers who primarily consume its components. - Figma’s Team Library enabled cross-file and cross-team component sharing, but additional project-level privacy and access controls were needed. ## New Project Permission Options - Professional Team editors can choose one of three access settings when creating a project: - Everyone on the team can edit - Everyone on the team can view - Invite-only access for selected collaborators - Existing projects can be updated by opening the **Share** dialog and changing their permissions. - The feature creates a boundary between design-system “maintainers” and “viewers.” ## Effects on Team Workflows - View-only permissions reduce the risk of well-intentioned team members modifying carefully maintained components. - Invite-only projects allow maintainers to experiment and refine a system before wider deployment. - Larger teams may give individual designers fewer opportunities to directly change the system, depending on the balance between maintainers and viewers. - Figma was exploring pull-request-like workflows so designers could suggest changes while maintainers retained ownership. Overall, the permissions provide a practical foundation for managing robust design systems: restrict editing to maintainers, use view-only access for consumers, and consider structured contribution workflows for future improvements.

Read original

Collaboration Figma Design Systems Access Control+2

figmaFeb 14, 20173 min readCurated summary

Team Libraries in Figma | Figma Blog

Team Libraries bring shared, synchronized components to Figma, addressing the difficulty of maintaining design systems across separate files. The feature builds on Figma’s components, constraints, and web-based collaboration to create a single source of truth that teams can reuse and update efficiently. Its workflow—Publish, Insert, and Update—combines engineering-style structure with an accessible design workflow. ## The Problems with Traditional Design Tools - Many design tools were modeled on print and illustration software rather than interactive applications. - They lack meaningful support for application behavior, platform constraints, and reusable interface structures. - Copying symbols between files creates disconnected versions that must be updated manually. - Large organizations such as Facebook, Google, and Airbnb have had to build custom tools and dedicate staff to maintaining design systems. - Designers need synchronized, compounding component structures to create scalable systems. ## Bridging Design and Dynamic Interfaces - Figma’s earlier features established the foundation for reusable design systems: - Reliable vector editing - Constraints that reflect system behavior - Dynamic, reusable components - Team Libraries extend these capabilities across files and team members. - Because Figma operates online, shared components have effectively no synchronization delay. - Teams can reuse structured components across devices, platforms, layouts, and user flows. ## An Engineering-Inspired Design Workflow - Figma draws on software concepts such as modular composition and frameworks like React. - Structuring interfaces from discrete, clearly defined parts makes products easier to maintain. - The feature adapts engineering principles for designers rather than copying programming workflows directly. ## Publishing Components - Designers select components and choose **Add to Library** in the inspector sidebar. - Multiple components can be collected and reviewed before being published. - Permissions separate the source of truth from its consumers: - Editors of the source file can modify the original components. - Anyone with view access can use the published components. - This lets specialized teams control assets such as icons, colors, or brand guidelines while others reuse them without changing the rules. ## Inserting and Nesting Components - Published components are available in any file for users who can view the source file. - Users insert them through Figma’s components tool. - Components can be nested inside larger components or modules. - Nested structures allow teams to build complex views from reusable source elements while preserving a predictable single source of truth. ## Updating Shared Components - Changes are made to the original component and published again. - Figma provides a confirmation step and a visual diff showing what changed. - Deleting a component from the source file and publishing removes it from the team library. - The update process includes an additional safeguard because changes may affect multiple design explorations and could otherwise cause users to lose work.

Read original

Collaboration Figma Design Systems User Interface+3

figmaDec 14, 20152 min readCurated summary

Slack From the Start | Figma Blog

Figma chose to build its collaboration experience around Slack rather than recreate messaging and notification features. User research showed that Slack was already central to designers’ daily workflows and correlated with more transparent collaboration. By making a Figma team a Slack team and routing notifications through Slack, Figma aimed to reduce tool fragmentation and strengthen its core product. ## Why Slack Mattered to Figma’s Users - Figma interviewed many designers about file storage, specifications, and product decisions. - More than half of the designers surveyed reported using Slack throughout the day. - Slack adoption was associated with more open and transparent design processes. ## Building on Slack Instead of Duplicating It - Figma considered recreating communication features inside its own product. - The team rejected that approach because it would create another inbox and require users to manage teams in two places. - Instead, Figma built its collaboration model on top of Slack: - A Figma team corresponded to a Slack team. - Figma file notifications were delivered through Slack. - Communication about design remained connected to users’ existing workflows. ## A Strategic Platform Bet - Figma viewed Slack as a platform well before Slack formally celebrated its platform launch. - Deep integration was considered a significant product and business bet. - Early results suggested the strategy was working, and Figma expected other companies to adopt similar integrations. The practical lesson is to integrate with tools users already rely on rather than reproducing their functionality. For Figma, treating Slack as foundational reduced friction and made collaboration feel like part of an existing workflow.

Read original

Collaboration Figma Slack Api Integration+2