Collaborative Design

47 posts

figmaApr 16, 20202 min readCurated summary

Figma + Lambda School: Where the remote classroom comes together to learn | Figma Blog

Figma’s collaboration features help Lambda School recreate the engagement and hands-on interaction of an in-person design classroom online. Students learn through shared presentations, live design work, peer feedback, and visible iteration rather than passively watching lectures. Because their work remains organized in Figma, the same files also support portfolio creation and continued peer learning. ## Interactive, Collaborative Lessons - Lambda School is a nine-month, live online program offering training in web development, mobile development, data science, and UX design. - Instructors present lessons in Figma during video conferences, allowing students to: - Zoom into designs and examine details. - Scroll through examples independently. - Use visible cursors to follow specific points in a presentation. - Students create and refine designs directly in shared Figma files. - Everyone can observe work in progress, learn from classmates, provide feedback, and remix existing designs. - This mirrors the collaborative workflows students will encounter on professional design teams. ## Real-Time and Asynchronous Feedback - Students and instructors can comment, tap each other for input, and work together in the same file. - Open audio, browser-based editing, and comments let students collaborate without constantly interrupting one another. - Students can work independently while classmates observe, take notes, or leave comments for later review. - When needed, an instructor or peer can join in and directly adjust pixels alongside the student. - Voting tools, such as stars, also encourage students to recognize and respond to one another’s work. ## A Lasting Record for Portfolios - Figma automatically preserves students’ designs, revisions, and project history. - This makes it easier to assemble a professional portfolio without searching through scattered files. - Students can focus more on interviews and career preparation while still presenting their development process. - Classmates’ work remains accessible after lessons, creating an ongoing resource for inspiration and learning. - The approach supports Lambda School’s broader career mission, which includes coaching, mentors, and connections to hiring partners. Figma’s use at Lambda School demonstrates how collaborative design tools can make remote education interactive, social, and career-oriented. Programs teaching practical creative skills can benefit from combining live instruction with shared workspaces that preserve feedback, iteration, and student progress.

Collaborative Design Figma User Experience Web Development+3

figmaDec 17, 20192 min readCurated summary

Made in Figma, 2019: Design by the numbers | Figma Blog

Figma’s 2019 usage data shows design becoming more collaborative, measurable, and broadly practiced. Anonymized data reveals strong preferences for cool colors, widely available sans-serif fonts, bold typography, and desktop and mobile frame presets. It also shows that design files increasingly serve as shared spaces for cross-functional teams rather than isolated work by individual designers. ## Color and Typography Trends - The most popular non-gray color was teal `#009688`, followed by dark blue-gray `#455A64` and `#263238`. - These cool tones contrasted with Pantone’s 2019 Color of the Year, Living Coral (`#FF6F61`). - Montserrat, Open Sans, and Lato were the three most-used fonts. - Google Fonts accounted for six of the top ten fonts, largely because they are readily available in Figma. - SF Pro Text, SF Pro Display, Proxima Nova, and Arial also ranked highly; notably, Arial surpassed Helvetica among system fonts. - Roboto, Figma’s default font, was excluded from the rankings. - Font usage was highly concentrated: 90% of usage came from the top 11 fonts, including Roboto. - Font Awesome ranked 31st, while Times New Roman ranked 55th. The first serif font, Playfair Display, appeared at number 22. - Designers were 13 times more likely to adjust font weight than italicize text, and one-third of files used bold or heavy styles. ## Frame and Device Preferences - Figma offered 36 preset frame options, and 33% of files began with one of them. - The 1440 × 1024 desktop frame was the most popular preset. - iPhone X and iPhone 8 frames followed closely, showing strong interest in both desktop and mobile design. - The ordering was notable given that Windows has much greater global usage than macOS. ## Collaboration Across Teams - Figma’s data reflects its goal of making design an open, collaborative process. - In larger organizations, files averaged six collaborators. - Collaborators could include designers, developers, product managers, writers, and other stakeholders. - A file typically began with one person working independently. - After an average of 19 days, the first collaborator was invited to review, comment, or contribute. ## Overall Direction The data suggests that 2019 design work was shaped by accessible tools, reusable conventions, and increasing teamwork. While designers favored familiar fonts, cool color palettes, and strong type weights, Figma files were also becoming shared product-development spaces involving people beyond design.

Collaborative Design Figma Design Systems Prototyping+2

figmaNov 21, 20192 min readCurated summary

Humanity at work: Gusto brings a new brand to life with Figma | Figma Blog

Gusto used Figma to turn a brand refresh into a company-wide effort centered on the human experience of work. The collaboration brought marketing, brand, product, and non-design teams into the same workspace, helping them align on the new identity and apply it consistently across Gusto’s platform. Figma’s real-time collaboration, commenting, libraries, and components helped translate the brand into a scalable product system. ## Why Gusto Rebranded - Formerly ZenPayroll, Gusto serves more than 100,000 small businesses with payroll, benefits, and HR tools. - Although customers valued the product, Gusto felt its existing brand did not reflect the human way it served them. - The refresh aimed to unify brand awareness, product development, and customer experience. - Gusto viewed its brand as the sum of every user interaction, not something owned solely by marketing or brand design. ## Bringing the Whole Company Into the Process - A major challenge was aligning roughly 1,000 employees around the new brand. - Gusto chose Figma as a shared workspace where employees could: - See work develop in real time - Communicate and share ideas - Comment directly on designs - Take ownership of the rebrand - Figma also helped non-designers understand the design process and appreciate design decisions. ## Connecting Brand and Product Teams - Brand and product design teams worked as equal partners through brainstorming sessions and workshops. - They jointly developed: - Color palettes - Typography - Brand starter templates - Product applications of the new identity - In collaborative sessions such as “Refresca,” designers applied the new brand to different product areas together in Figma. - Early collaboration made it easier to carry the brand consistently through the entire product experience while highlighting meaningful moments in distinctive ways. ## Building a Scalable Design System - Gusto wanted a reliable “system of record” for how its products should look. - The product design team created a UI kit using Figma libraries and components. - The kit was based on the brand team’s guidelines and provided reusable foundations for multiple products. - This system helped designers work consistently and scale the new brand as Gusto grew. Gusto’s experience shows that a successful rebrand requires more than new visual guidelines. Shared tools and close collaboration can align an entire company, connect brand strategy to product design, and create a cohesive customer experience.

Collaborative Design Figma Design Systems User Interface Design+2

figmaOct 29, 20192 min readCurated summary

Let’s create Figma’s first user conference together | Figma Blog

Figma announced its first user conference, scheduled for February 6, 2020, in San Francisco. The event was designed as an in-person extension of Figma’s growing online community, giving users opportunities to learn from one another, share practical experiences, and build connections. Figma invited the community to help shape the program through speaker proposals and attendee applications. ## A conference built around the Figma community - Figma’s user base had grown from a small beta community to hundreds of thousands of active users worldwide. - The company emphasized that users had always learned from one another through inspiration, knowledge-sharing, and collaboration. - Following the launch of Figma Community, the conference would provide an offline space for users to connect and exchange ideas. ## Community-led programming - The event would feature: - Lightning talks - Workshops - Roundtables - A limited number of keynotes - Sessions could range from 15 minutes to one hour. - Users could submit their own ideas or nominate someone else to speak. - Suggested topics included: - Interesting projects built with Figma - Lessons learned through difficult experiences - Peer discussions - Collaborative activities using Figma - Proposal submissions were due by November 20, 2019, at 11:59 p.m. PST. ## Small, diverse attendance - Figma planned to keep the conference relatively small to encourage meaningful conversations. - The company sought diversity across ability, age, education, ethnicity, gender, race, sexual orientation, and socioeconomic status. - Because capacity might be limited, Figma could use a lottery system to help create a representative attendee group. - Applicants would receive notification after the deadline and have one guaranteed week to purchase a pass. ## Cost and scholarships - Tickets cost $299. - Figma offered scholarships so that financial constraints would not prevent participation. - Attendee applications were also due November 20, 2019. Figma’s announcement positioned the conference as a collaborative event shaped by its users. Prospective speakers and attendees were encouraged to apply and help create an inclusive, community-driven gathering.

Collaborative Design Figma Figma Plugins Figma Community+1

figmaMar 20, 20192 min readCurated summary

The power of Figma Drafts | Figma Blog

Figma Drafts provide a private space for experimentation before designs are ready for team-wide visibility. Josh Dunsterville argues that separating rough exploration from polished project files reduces fear of judgment and encourages faster, more creative iteration. The central principle is simple: create first, organize and share later. ## Why Drafts Matter - Traditional design workflows often encourage sharing only polished, “presentable” work. - This can lead designers to prioritize tidy files, perfect pixels, grids, and layer names over exploring solutions. - Drafts act as a private personal folder, independent of broader team or project permissions. - Individual draft files can be shared when appropriate, but drafts cannot be opened globally to an entire team. - The concept resembles a physical notebook: informal, incomplete, and free from pressure to look finished. - This environment can also help overcome designer’s block by removing the need to plan every detail before starting. ## Using Drafts for Exploration - Drafts can hold anything from quick app concepts to experiments with Figma features. - Untitled files, rough shapes, default colors, and messy layouts are acceptable. - The key workflow is: **create first, organize second**. - Designers should use drafts to quickly capture and test ideas without worrying about presentation quality. ## Moving Ideas into Projects - When a draft is ready for further development or team collaboration, it can be moved into a project. - Files can be transferred by: - Dragging them into the desired project. - Selecting the “Drafts” location inside the file and choosing a project. - If an idea may be useful later, duplicate the draft before moving it so the original remains as a snapshot. - Drafts can remain the messy source of truth, while project files are cleaned up for broader use. - File-browser filters such as file name, creation date, and last-modified date help manage drafts as they accumulate. Drafts are most valuable when treated as a low-pressure digital notebook rather than a staging area for finished work. Keep early thinking private and messy, then promote only the ideas that merit organization and collaboration.

Collaborative Design Figma Design Systems Prototyping+2

figmaJan 28, 20193 min readCurated summary

Introducing Figma Organization: Our first enterprise-grade offering | Figma Blog

Figma Organization was introduced as Figma’s first enterprise-grade offering, designed to help large companies manage design collaboratively on the web. It combines administrative controls such as unified billing and audit reports with designer-focused features including unlimited teams, Shared Fonts, and organization-wide design systems. The central argument is that web-based, centralized design enables companies to scale collaboration without losing team autonomy. ## From Startup Tool to Enterprise Platform - Figma describes a shift from serving primarily innovative startups to supporting organizations across industries and sizes. - Companies increasingly wanted to replace isolated design teams, local files, and fragmented workflows with an open, web-based process. - Figma Organization was developed with feedback from companies including Rakuten, Square, Volvo, and Uber. - The offering added: - Unified billing - Audit reports - Enhanced security and privacy controls - Unlimited teams - Shared Fonts - Organization-wide design systems ## Unlimited, Browsable Teams - Organizations can create or join unlimited teams, giving employees a central place to discover: - Prototypes - Design files - Exportable assets - Code handoff materials - Because Figma operates on the web, files remain current and accessible across teams. - Administrators can control team visibility with three privacy levels: - **Open:** Anyone can join. - **Closed:** Anyone can view the team, but joining or editing requires approval. - **Secret:** The team is visible only to invited members. - This structure allows organizations to preserve independent team workflows while maintaining a broader view of company-wide work. - Uber used the model to consolidate previously scattered files across products such as Uber Eats, Uber Freight, and its ridesharing service. After testing the beta, Uber moved most of its product design work to Figma. ## Organization-Wide Design Systems - Figma Organization allows teams to share Component and Style libraries across products and services. - Square used the platform to support more than 100 designers across over 25 products and maintain six design systems for iOS, Android, and the web. - Designers can browse another product’s design system, reuse established patterns, and adapt them to their own branding. - Shared libraries provide a single source of truth: teams work with the same component versions in the same tool. - Designers can update master components or styles centrally, and users of those assets are automatically notified when changes occur. Figma Organization’s practical value lies in combining centralized governance with decentralized team work. For large companies, adopting shared teams, controlled visibility, and reusable design systems can reduce fragmentation while keeping designs consistent and up to date.

Collaborative Design Figma Design Systems Prototyping+2

figmaDec 12, 20182 min readCurated summary

Deliveroo designs in the open with Figma | Figma Blog

Deliveroo adopted Figma to replace a fragmented design workflow that had become difficult to manage as the company and its design team grew. Shared files allowed product designers, content designers, researchers, engineers, and product managers to collaborate directly instead of exchanging screenshots, emails, and Slack messages. The result was a more open design culture, faster feedback, easier onboarding, and better alignment across teams. ## Collaboration Problems as Deliveroo Expanded - Deliveroo’s design organization grew to more than 40 people supporting consumers, riders, and restaurants. - Product groups became siloed as the company expanded rapidly. - Tools such as Sketch, Dropbox, Zeplin, and Abstract created disconnected workflows. - Teams struggled with: - File synchronization and version-control issues - Sending files back and forth by email - Maintaining consistency across app designs - Coordinating product and content design - Product and content designers effectively took turns working on the same file, leading to repeated screenshots, Slack messages, and manual checks. ## Moving to a Shared Figma Workflow - Deliveroo initially had concerns about changing tools but became interested in Figma’s collaborative editing. - A pilot demonstrated that multiple people could work in one document simultaneously. - Product and content designers could develop ideas together rather than maintaining separate files. - After adopting Figma, the team no longer needed to continually manage and synchronize disconnected design documents. ## Building a More Open Design Culture - Figma made the design process visible to a wider group of employees. - Product designers, researchers, engineers, and product managers could inspect work and understand the reasoning behind design decisions. - Engineers could identify edge cases earlier and discuss how to represent them in the product. - Non-design stakeholders felt more comfortable contributing because Figma was accessible beyond specialist design teams. - New designers could learn the organization’s work by exploring existing files instead of being trained across many separate tools. ## Faster Feedback and More Efficient Reviews - Comments and discussions remained attached to the relevant work in a single document. - Stakeholders could review projects without requiring a separate walkthrough. - Designers could ask and answer questions more quickly. - Centralized feedback reduced unnecessary back-and-forth and made team members feel more connected to the work. Deliveroo’s experience suggests that a shared, browser-based design workspace can reduce operational friction while encouraging broader participation. For rapidly growing design teams, consolidating files, feedback, and collaboration in one accessible tool can improve both speed and consistency.

Collaborative Design Figma Design Systems Product Design+4

figmaOct 29, 20183 min readCurated summary

Designers use Figma to bring Uber to the unbanked | Figma Blog

Uber’s expansion into emerging markets required designing for differences in language, literacy, devices, culture, location, and user roles. For its cash-payment initiatives, product designer Femke van Schoonhoven adopted Figma after fragmented tools made collaboration and research iteration difficult. Figma became a shared, web-based source of truth that reduced communication overhead, improved engineer handoff, and enabled distributed teams to work together more effectively. ## Designing for Diverse Markets - Uber serves millions of riders across dozens of countries, requiring experiences that work across very different local contexts. - Designers conduct extensive research, including riding with drivers and testing designs in real-world environments. - Emerging-market design must account for: - Language and literacy - Device limitations - Culture and location - Whether the user is a rider, driver, or another participant - Cash payments were particularly important for reaching users without access to traditional banking. ## Problems with the Previous Workflow - The Cash team used separate tools for design, prototyping, sharing, feedback, and engineering handoff. - Designers had to repeatedly import and export files and communicate project status outside the design tool. - During field research, only one person could edit a design at a time, preventing real-time iteration with teammates. - This made it difficult to respond immediately to feedback from Uber drivers. ## Figma Enables Real-Time Collaboration - Van Schoonhoven moved existing files into Figma through a simple drag-and-drop process. - She could create prototypes using local languages and realistic, in-context materials. - Multiple team members could edit the same design simultaneously, whether working nearby or across countries. - Figma’s file organization made designs easier to locate and maintain. ## A Single Source of Truth - Stakeholders could access the latest designs directly instead of requesting updates by email. - Figma reduced communication overhead by an estimated 75 percent. - Engineers could be invited into design files, view current changes, and comment in context. - Early engineering involvement made handoff faster and less error-prone. - The shared workspace helped replace siloed work with a central design repository. ## Supporting Distributed Projects - Figma provided the collaborative foundation for projects involving designers in Amsterdam, San Francisco, and other locations. - Teams could access shared Uber platform components and work from the same current files. - Because the tool was web-based, stakeholders could share designs and obtain approvals more quickly. Figma helped Uber’s designers adapt payment experiences for unbanked users by combining rapid iteration, shared context, and cross-location collaboration. For distributed product teams working across complex markets, a centralized collaborative design environment can substantially reduce friction from research through engineering handoff.

Collaborative Design Figma Prototyping Product Design+4

figmaAug 9, 20183 min readCurated summary

Why transparent, open design leads to happier clients | Figma Blog

Citrusbyte argues that sharing unfinished design work with clients creates better collaboration, faster workflows, and stronger project outcomes. Using Figma’s cloud-based, real-time environment, clients can observe progress, provide precise feedback, and participate directly instead of waiting for polished presentations. Although transparency can expose messy creative stages, Citrusbyte manages expectations through clear communication and finds that openness ultimately produces happier clients. ## Why Transparency Matters - Citrusbyte, a 90-person strategy, design, and development firm, shares raw, in-progress design files with clients. - The company moved away from traditional siloed design, where designers work privately and present finished deliverables. - Earlier tools such as Sketch and Photoshop made continuous transparency difficult, requiring teams to export and email files or use file-sharing services. - Figma enables: - Always-current cloud files - Link-based sharing - Simultaneous collaboration - Real-time visibility into design changes - Clients gain a stronger sense of security and involvement because the work is not hidden in a “black box.” - Citrusbyte explains that unfinished work is part of the process, comparing it to seeing a bicycle being assembled rather than expecting a finished bike immediately. - Bringing clients directly into the project increases buy-in and improves their understanding of the work. ## Faster Feedback and Fewer Handoffs - Before Figma, clients often reviewed PNGs or PDFs and responded through email or Slack. - Vague feedback created unnecessary back-and-forth because clients could not clearly identify which design element they meant. - Prototype tools such as InVision required designers to save, flatten, and re-upload new versions whenever designs changed. - With Figma: - Prototypes update automatically as the source design changes. - Clients can experiment with content, such as headline copy, themselves. - Designers spend less time handling minor text revisions and file management. - Figma’s observation mode allows clients and teams to follow a presenter’s screen directly during reviews, eliminating the need to prepare specially polished presentation files. - Citrusbyte designer Sam Small estimates that Figma saves him 30–50% of his previous workflow time. ## Business and Client Benefits - Removing repetitive steps allows Citrusbyte to handle more work and meet aggressive deadlines. - Regular reviews—sometimes daily—keep clients closely aligned with project progress. - Faster review cycles and continuous visibility improve trust and collaboration. - The approach helped Citrusbyte grow from primarily serving startups to working with major companies including Apple, Sony, Intel, and AT&T. Citrusbyte’s experience suggests that transparent, collaborative design works best when paired with clear expectations. Teams should expose work early, use tools that support real-time collaboration, and treat clients as active participants rather than occasional reviewers.

Collaborative Design Figma Prototyping Real Time Collaboration+1

figmaMay 30, 20183 min readCurated summary

How one Figma engineer plays to her strengths | Figma Blog

Kathryn Salant’s interests in music, programming, and cycling all reflect her belief in experimentation, iteration, and measurable progress. Her career shows how creative disciplines can reinforce one another, leading her from trumpet performance and interactive media to software engineering at Figma. Across each field, she values collaboration, meaningful expression, and the process more than perfection. ## Figma’s “3 Things” Tradition - New employees present three experiences or interests that shaped them. - Kathryn’s three things—music, programming, and cycling—illustrate the connections between her creative and technical life. - Figma presents these stories to highlight the diverse backgrounds of its employees. ## Music and Creative Expression - Kathryn began playing trumpet in fifth grade and studied at the University of Wisconsin-Madison and the London College of Music. - She became dissatisfied with classical music’s emphasis on technical precision over inspiration and meaning. - In San Francisco, she joined the avant-garde Extra Action Marching Band in 2003. - The band performed with David Byrne and experimented with unconventional material, including Beyoncé and Black Sabbath covers. - These experiences deepened her interest in creativity beyond strict tradition. ## Programming as a Creative Tool - Kathryn first encountered programming in sixth grade on Apple IIe computers, learning Logo and creating a convincing Super Mario demo. - She continued experimenting by taking apart and sometimes breaking her mother’s work computer. - While studying music, she discovered Flash 4 and became fascinated by its combination of motion graphics, interactivity, and web technology. - Flash showed her that programming could enable artists, musicians, and designers to express ideas. - She pursued software engineering so she could help other people bring creative visions to life. - Her respect for design and emphasis on communication between engineers and designers align closely with Figma’s collaborative mission. ## Cycling and Community - Kathryn became an avid cyclist after completing the seven-day AIDS/LifeCycle ride from San Francisco to Los Angeles. - In 2006, she founded Butterlap, a weekly San Francisco bike ride centered on community and inclusiveness. - She later took part in CycloCross, a muddy, social form of bicycle racing. - Her participation in the 2008 Single Speed CycloCross World Championships was as much about encouraging others as competing. - Cycling reinforced her preference for shared experiences, perseverance, and not taking competition too seriously. Together, these three interests show Kathryn’s consistent approach: improve through iteration, stay open to unconventional ideas, and create alongside other people. Her story suggests that technical work can be strongest when it preserves the curiosity, collaboration, and expressive freedom found in the arts.

Collaborative Design Design Tools Motion Graphics Programming+3

figmaJan 31, 20182 min readCurated summary

Figma raises $25MM Series B | Figma Blog

Figma announced a $25 million Series B funding round led by Kleiner Perkins partner Mamoon Hamid. Existing investors from Index, Greylock, and LinkedIn also participated. The funding supports Figma’s broader vision of making design accessible, collaborative, and web-based rather than limited by siloed tools and workflows. ## Series B Funding - The round was led by Kleiner Perkins’ Mamoon Hamid. - Hamid’s previous investments included SaaS companies such as Slack, Box, and Intercom. - Existing investors Danny Rimer of Index, John Lilly of Greylock, and LinkedIn co-founder Jeff Weiner joined the round. - This was Hamid’s first investment at Kleiner Perkins. ## Figma’s Founding Vision - Figma was founded five years earlier by Dylan Field and Evan Wallace. - The founders believed creative tools should empower users rather than constrain them. - Their goal was to make creation: - Accessible to more people - Collaborative instead of siloed - Built for the web - The company emerged from experimentation with browser-based design tools, supported initially by a Thiel Fellowship. ## Adopting a New Way of Working - Figma acknowledged that changing established design workflows is difficult and takes time. - The company credited its users, employees, and early investors for supporting its vision during that transition. - The funding announcement represented both financial growth and continued validation of collaborative, web-based design. Figma intended to use the momentum from its Series B to continue developing tools that make design more open, collaborative, and accessible across teams.

Collaborative Design Figma User Experience Web Design+1

figmaDec 14, 20173 min readCurated summary

18 designers predict UI/UX trends for 2018 | Figma Blog

The article gathers predictions from 18 designers about UI/UX in 2018, emphasizing that the field should improve users’ experiences rather than prioritize novelty or designer ego. Common themes include accessibility, ethical responsibility, collaboration, and closer integration between design and development. It also warns that efficiency and standardized systems can become harmful when adopted without critical thought. ## Accessibility and Inclusive Design - Designers argue that accessibility should become a central responsibility rather than an afterthought. - Common problems include: - Using ultra-light gray text for essential content - Adding unnecessary animation - Making interfaces harder to understand for visual flair - Inclusive design is described as an important trend that the industry needs, even if it is unlikely to attract attention or headlines. - The article suggests that many teams avoid accessibility work because it requires sustained effort rather than producing immediately visible results. ## Design Collaboration Inspired by Engineering - Design teams may begin working more like engineering teams. - Possible developments include: - Formal design reviews similar to code reviews - Design tools that identify inconsistencies like code linters - Open-source design patterns and shared UX standards - This approach could make collaboration more systematic and help establish common practices for user experience and information design. ## Ethics and Designer Responsibility - Designers are encouraged to recognize the influence their work has on people’s behavior and decisions. - UX choices should be evaluated for their ethical consequences, not only their usability or business value. - The broader prediction is that designers will become more accountable for how products affect users and society. ## Risks of Overreliance on Design Systems - Standardized systems such as Material Design and Microsoft’s Fluent Design may become increasingly dominant. - One concern is that designers will adopt these systems automatically without questioning whether they fit a product’s users or context. - Design systems can improve consistency, but they should not replace independent judgment or thoughtful problem-solving. ## Convergence of Design and Development Tools - Design and development tools are expected to become more integrated and centralized. - Technologies such as CSS Grid, custom variables, Vue, and React could make implementation more efficient and flexible. - Greater efficiency should create more time for designers to focus on responsible design and more inclusive experiences. - The article frames technical progress as valuable only when it supports better outcomes for users. Overall, the predictions recommend treating accessibility, ethics, and inclusion as core design requirements—not optional trends—while using collaboration frameworks, design systems, and new development technologies thoughtfully.

Collaborative Design Design Systems User Experience React+4

figmaOct 23, 20173 min readCurated summary

Why Professors at Stanford and UC Berkeley Use Figma to Teach Design | Figma Blog

Figma argues that interface design courses need tools that minimize technical overhead so professors can focus on design principles. Its browser-based, collaborative platform is presented as accessible across devices, free for educational institutions, and easy for beginners to learn. The post concludes that these features make teaching, feedback, sharing, and group work more efficient. ## The Challenge of Teaching Interface Design - Interface design remains uncommon in college curricula, often appearing as isolated interdisciplinary courses. - Professors must teach substantial technical concepts in limited time. - Traditional design tools can be difficult and time-consuming for students to learn. ## Accessible on Any Computer - Figma runs in the browser and supports PCs, Macs, Linux systems, and Chromebooks. - Students can work anywhere with internet access, without downloading large software packages. - This helps students who do not own high-powered personal computers. ## Free for Educational Institutions - Figma’s premium version is offered free to educational institutions. - Schools do not need to negotiate expensive contracts. - The lack of cost reduces barriers for students from lower-income backgrounds. ## Easy to Learn - Figma is designed around the core functionality digital designers need. - Berkeley instructors describe it as lightweight, simple, and intuitive. - Students with no prior design experience can reportedly learn the basics in under an hour. - Professors and TAs can concentrate on design principles rather than tool training. ## Technical Support for Classes - Figma provides in-app chat support for students and instructors. - The company states that it responds within 24–48 hours on weekdays. - This reduces the technical-support burden on professors and TAs, especially in large classes. ## Always-Current, Shareable Designs - Designs are stored online and accessed through a file URL. - Instructors can view the latest version without requiring students to export or email files. - Teachers can review work or watch students design in real time. ## Feedback and Version History - Comments can be pinned directly to specific design frames. - Students can view feedback immediately and iterate without waiting for in-person meetings. - Version history shows how a design developed and helps instructors assess contributions in group projects. ## Real-Time Collaboration - Multiple students can work in the same file simultaneously. - Cloud collaboration eliminates the need to email files, manage conflicting versions, or take turns editing. - The post also introduces seamless developer handoff as another benefit, though the provided excerpt does not elaborate on it. Figma’s combination of low cost, cross-platform access, simple onboarding, collaboration, and built-in feedback makes it a practical classroom tool for teaching design fundamentals rather than software mechanics.

Collaborative Design Figma Cloud Computing Version Control+2

figmaOct 18, 20173 min readCurated summary

How to throw a design-friendly hackathon | Figma Blog

Hackathons have traditionally centered on engineers, but design is now essential to building successful technology products. To attract and retain designers, organizers must deliberately recruit them, communicate the event’s creative value, make applications inclusive, and provide design-focused support. Hack@Brown’s experience shows that these efforts can raise designer participation to roughly one-fifth of attendees. ## Why Hackathons Need Designers - Early hackathons were created around programming and engineering, reinforcing the idea that they were primarily for coders. - As design became a major product differentiator, hackathons began seeking stronger collaboration between designers and engineers. - Hack@Brown, Brown University’s annual event with more than 500 participants, experimented with different approaches and reached about 20% designer participation by 2017. ## Recruit Designers Directly - Designers often do not encounter hackathon promotions through computer-science networks. - Organizers should contact: - University art departments - Campus design clubs and social groups - Local art and design schools - Hack@Brown reached out to institutions including RISD, Parsons, and Northeastern’s design club, Scout. - Organizers with personal connections to design communities have an advantage, but broader outreach is necessary to build awareness. ## Market the Creative Opportunity - Generic messaging such as “24 hours” and “loads of prizes” may not appeal to designers. - Promotional materials should demonstrate strong visual design and involve artists or visual thinkers on the organizing team. - Hack@Brown replaced conventional hacker-focused messaging with “Make, play, learn,” emphasizing creativity, collaboration, and experimentation. - The goal is to show designers that they can make meaningful contributions to hackathon teams. ## Create an Inclusive Application Process - Application systems can unintentionally favor experienced engineers or exclude candidates from nontraditional backgrounds. - Organizers can use: - A lottery system with reserved designer spaces - A separate evaluation process for design applicants - Design experts to help review applications - Hack@Brown received about 3,000 applications for 500 places and used representation targets, including at least 15% designers, 50% women, and 20–30% first-time hackathon participants. - Broader participation produced more varied and innovative projects. ## Build a Design-Friendly Event - Recruiting designers is not enough; the event must also support their needs and make them feel included. - Useful initiatives include: - Design workshops before or during the hackathon - UX/UI introductions for participants unfamiliar with design - Designer mixers to help attendees build community - Design mentors, especially those with coding experience - Design recruiters offering job and internship opportunities - Hack@Brown scheduled its event shortly after Brown and RISD career fairs so recruiters could meet many potential candidates efficiently. ## Recognize Designers - The article begins a section on rewarding designers to encourage them to return and recommend the event to others, but the provided text ends before describing the specific reward strategies. A design-friendly hackathon requires intentional outreach, inclusive selection, relevant programming, and visible support for design participants. Treating designers as equal contributors—not as an afterthought—helps create stronger teams and more innovative projects.

Collaborative Design User Experience Design Thinking Visual Design+2

figmaSep 18, 20172 min readCurated summary

Team Library 1.0 | Figma Blog

Figma’s Team Library 1.0 turns shared components into a centralized foundation for collaborative design systems. Building on feedback from its February beta, the release improves component discovery, documentation, and organization. Figma argues that its centralized, online platform can keep teams synchronized without third-party tools or custom internal systems. ## A Centralized Source of Truth - Teams can share buttons, icons, dialogs, and other components across files and with all team members. - Published components and updates appear immediately in the Team Library. - Users receive notifications when shared components change and can choose whether to apply updates to their local instances. - Centralized storage eliminates manual exporting, syncing, and reliance on tools such as Slack, Google Docs, or custom company software. ## Improved Component Browsing - The beta required repeatedly opening a pop-up that obscured the canvas. - Team components are now available in a dedicated tab in the left sidebar, alongside layers. - Designers can drag components directly from the sidebar into their designs. - A separate local-components tab provides an overview of what will be published. - The sidebar tabs can be switched quickly with `Alt+1`. ## Built-In Component Documentation - The beta provided no place to explain how or when components should be used. - Team Library 1.0 adds documentation fields in the right-hand properties panel. - Teammates can read this guidance while browsing components, keeping usage information attached to the component itself. ## Better Categorization and Organization - The beta organized components only by file, which made larger libraries difficult to navigate. - Components can now also be grouped by frame and group. - For example, button components placed in a group named “Buttons” appear together under that category. - Shared component thumbnails can be visually customized by changing the background color of their containing frame. Figma presents Team Library 1.0 as a practical foundation for building and maintaining living design systems. Teams can adopt shared components with less friction, while documentation and categorization make those systems easier to understand and scale.

Collaborative Design Figma Design Systems Component Library+1