Remote Collaboration | Techlist.io

figmaApr 21, 20192 min readCurated summary

GitHub takes its collaborative culture to a new level | Figma Blog

GitHub adopted Figma to make its design system more collaborative, scalable, and accessible—especially for its distributed workforce. What began as a grassroots effort to standardize design evolved into a dedicated seven-person team and a largely Figma-based workflow. Figma’s browser-based collaboration and API helped GitHub remove tooling barriers, streamline contributions, and bring designers and engineers closer together. ## Building a Dedicated Design Systems Team - In 2015, GitHub lacked staff dedicated full-time to its design system. - Designers repeatedly recreated components, worked with outdated patterns, and lacked consistent documentation. - A grassroots initiative began improving the process and documented workflow. - Within six months, GitHub formed a permanent design systems team. - By 2019, seven of the company’s 25 product designers focused on reusable, interchangeable components. ## Removing Friction from the Design Workflow - Maintaining the design system initially required specialized software and knowledge of complex tools. - Contributors found it difficult to update shared assets such as GitHub’s Octicons SVG icon library. - GitHub tested Figma because it eliminated the need to install desktop software. - Combining Figma with its API enabled an automated, platform-independent contribution workflow. - The design systems team subsequently migrated UI components into Figma, making most design and development resources available in one place. ## Turning Figma into a Remote Collaboration Hub - Figma’s web-based workspace helped GitHub’s remote employees collaborate despite being in different locations. - Designers could work simultaneously in the same file, effectively replacing the physical whiteboard. - Shared design sessions and “design jams” helped ideas gain momentum and encouraged experimentation. - Prototyping became easier because designers could create and adjust flows without switching tools. - GitHub viewed Figma as a natural fit because both products emphasize collaboration between designers and engineers. ## Faster Feedback and More Connected Teams - Figma lowered the barrier for people outside design to participate in the feedback process. - Real-time collaboration helped distributed teams communicate more directly. - By consolidating components, prototypes, and design discussions, GitHub could support more efficient and consistent delivery. GitHub’s experience suggests that a design system works best when its tools make contribution as easy as consumption. For distributed organizations, a browser-based, collaborative platform such as Figma can turn design-system maintenance into a shared engineering and product activity rather than a specialized, isolated process.

Read original

Remote Collaboration Figma Design Systems Prototyping+3

figmaMar 26, 20192 min readCurated summary

Dribbble Scores with Live Design Collaboration for its Remote Team | Figma Blog

Dribbble adopted Figma to make collaboration feel more like working together in the same room despite its fully remote, globally distributed team. Figma replaced a fragmented collection of tools with a shared, real-time workspace and a single source of truth for designs. The result was faster iteration, clearer feedback, and less time spent managing files and communication. ## Remote Collaboration Challenges - Dribbble’s design team included seven product designers and developers working across multiple time zones. - Remote work helped attract talent and offered flexibility, but made spontaneous collaboration more difficult. - The team relied on video conferencing and several disconnected tools, without a seamless way to work together. - Designers lacked visibility into one another’s work, while file management and multiple feedback channels reduced time available for design. ## Figma as a Shared Design Workspace - Figma allowed multiple people to work in the same file simultaneously, recreating the experience of brainstorming in a room or on a whiteboard. - Online files were easier to find and access, eliminating the need to ask colleagues for the latest version. - Designers could stay within one tool instead of repeatedly switching between applications. - Figma’s handling of vectors, images, and copy-paste attributes also appealed to Dribbble’s designers. - The team eased adoption by importing existing design files and recreating familiar interface components in Figma. ## Faster Pairing and Feedback - Figma supported Dribbble’s practice of using design pairs to solve problems and deliver products quickly. - A single, current file reduced communication friction and kept designers aligned on the latest changes. - Multiplayer editing made it easier to hold frequent critiques, duplicate frames, explore alternatives, and comment in real time. - The team could solve design problems in minutes rather than days; in one example, five people collaboratively produced an approved profile design in about 20 minutes. ## Integration with Dribbble - Dribbble used Figma’s API to build an integration for publishing work directly to Dribbble. - Users can select a layer in Figma and choose **Integrations → Dribbble** to begin the Dribbble desktop upload flow. For fully remote design teams, a shared real-time workspace can replace fragmented collaboration processes. Dribbble’s experience suggests that adopting a single source of truth helps teams communicate more clearly, iterate faster, and spend more time designing.

Read original

Remote Collaboration Figma Design Systems Real Time Collaboration+3

figmaSep 20, 20183 min readCurated summary

Aisle Rocket Studios, the agency behind Whirlpool, masters collaboration | Figma Blog

Aisle Rocket Studios (ARS), a multi-office agency serving brands such as Whirlpool and Maytag, adopted Figma to solve the challenges of remote collaboration and fragmented workflows. By making Figma the shared source of truth, ARS brought designers, writers, developers, and clients into the same browser-based workspace. The result was faster iteration, more inclusive collaboration, and a more efficient creative process. ## Fragmented Files and Remote Collaboration - ARS had more than 250 employees, four offices, and remote associates supporting over 25 brands. - Creative work was scattered across native files in Sketch, Photoshop, and other tools. - When Creative Director Matt Carson joined the Whirlpool account remotely under a tight deadline, the lack of a centralized process became especially apparent. - Figma’s multiplayer functionality offered a real-time workspace for collaboration across locations and time zones. ## Figma as the Shared Source of Truth - The Whirlpool team quickly replaced disconnected workflows with a centralized Figma process. - Team members designed and iterated together in a single file. - They used Figma for internal meetings, stakeholder feedback, and client prototypes. - Clients could review interactive concepts without logging in or waiting for developers to build the experience, shortening review cycles. ## More Inclusive Creative Work - Figma enabled ARS to conduct roughly 80% of its creative process in the browser. - Writers could edit copy directly within designs instead of working separately and handing it off later. - This made copy an active design element and gave non-designers more influence over the final product. - Developers could review designs early, helping identify technical constraints before handoff and reducing back-and-forth. ## A Leaner, More Effective Team - The Whirlpool account team became faster and more collaborative after consolidating its tools and files. - Its success attracted attention across ARS, prompting other teams to adopt the same workflow. - Both ARS and Whirlpool reported savings in time and money without sacrificing creativity. - Open, collaborative design became a standard the agency wanted to apply more broadly. ## Building a Shared Design System - ARS’s next step was to create greater consistency across Whirlpool’s digital brand. - Following atomic design principles, the team planned to build standardized “atoms” in Figma. - These components would be stored in a team library as a central source of truth. ARS’s experience suggests that browser-based collaborative tools can unify distributed teams and make the creative process more democratic. Centralizing design, copy, development input, prototypes, and reusable components in one shared workspace can improve speed, communication, and consistency.

Read original

Remote Collaboration Figma Design Systems Prototyping+3