Bolivia burned while the world watched Brazil.

In August 2019 the world’s eyes were focused on Brazil. The Amazon was on fire and social media was burning up in indignation. The data available at the time told us how many fires there were, but…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




How to Set Your Figma Up for Easy Collaboration with Nondesigners

Think of Figma as your home. Here’s how to show your developer, product management, and marketing guests around

UX designers know that we’d be lost without the help of product managers, software engineers, and other partners. Their feedback on our designs is essential to making products that work for everyone. But when we’re not all using the same tools, that collaboration can get a little rocky. It doesn’t have to be that way.

While Figma has become a natural habitat for our UX team, it’s still unfamiliar territory to many nondesigners. They can easily get lost in a maze of files and frames, with no sense of how or where to comment or extract code. That can make working together more complicated than it needs to be. Here are five ways to welcome other functions into your Figma designs and make collaboration easier and better for everyone.

Most design files hold dozens of frames, iterations, and notes. Finding your way around them can be overwhelming. On top of that, different designers use different methods to say which parts of the files are ready for implementation and which are still in progress.

To make it easier for someone new to get oriented, start by cleaning up your file name and page list. Use names that make it clear which design is current, which ones were explorations, and such.

Figma sidebar showing a file’s page names. Text: Cover, Product walkthrough, a section break made with dashes and the word delivered, JIRA-115 Article Page, JIRA-123 Template, JIRA-134 Swipe Gestures, section break made with the abbreviation WIP, JIRA-208 Landing Page.

It helps to use a consistent style for your page names in Figma. Think about your partners and what will make sense to them. A lot of teams use tools like Jira and Trello to organize tasks and stay connected. Try using the same naming convention across Figma and Jira, Trello, or whatever products you use to organize your tasks.

For example, if you’re all working off of the same ticket in Jira, then you could use the ticket’s tracking number, like JIRA-123. If you’re not sure your collaborators will recognize that number, it’s a good idea to add a short description of the project as well. For example: “JIRA-134 Swipe Gestures.”

If your project has pages from multiple design stages, add dividers to split up files. In the screenshot above, the pages are grouped into sets. It’s helpful to add named dividers between groups.

An emoji like a green checkbox can show partners at a glance what’s ready for attention or implementation. If you use several emojis with different meanings, like a pencil for explorations, or a filing cabinet for archives, use them consistently.

When you invite someone to Figma for the first time, let them know that they can use the page list on the left to move around.

On your pages you’ve got all the frames that make up the parts of your design. Frames have a way of multiplying and it can be hard for a newcomer to know which ones to focus on. You can help collaborators find their way to the right place by collecting them in groups. Give each collection a clear, consistent label that’s easy to spot. Use a large type size — people will likely be zooming out to try to get a sense of what’s where on the page when they first arrive.

Figma modal for commenting. Prompt text reads Add a comment, one button reads Cancel and the other reads Post.

As designers, we want the whole team involved early in the process so that we can get the most out of the designs and have them ready faster.

For more in-depth co-creation, you may want to give your collaborators “can edit” access to your file. If you do, be clear what you’d like them to work on, and where. Better yet, make them a copy of the design you want them to work on, label it, and link them right to it.

Figma modal for sharing a link to a file. The box is checked to link to selected frame.

When you hand off your Figma files to developers, they’ll go right to the code panel to pull your design’s visual specifications so they can begin building it. By clicking on a layer, they’ll be able to see its data in easy-to-copy code and table formats.

To share Figma images with partners who need to use them for development or marketing, define your export settings before handoff. Doing this saves them time and helps you make sure your partners get the right files in the right format and at the right scale.

First, set the export settings for the individual designs you want to share. And remove settings from the designs that your collaborators don’t need. If they want more than one file, direct them to the export list. They can go to the File menu and choose Export. The modal that pops up will only show the designs with export settings. Collaborators can take them all, or just select the ones they need.

I hope these help you next time you invite nondesigners into your Figma designs. If you have more tips that you use with your collaborators, please let me know!

Subscribe to our newsletter to get our latest stories right in your inbox.

Add a comment

Related posts:

Discover the Benefits and Cost Savings Available Through Streamlined KYC Processes

Financial institutions have experienced seismic shifts over the past decade driven largely by technological innovation, the emergence of new FinTech players in the market, and the need to keep up…

Getting started with growth content design

Growth content design is the practice of writing content for product adoption and usage. It prioritizes data, experimentation, and rapid iteration. When Google changed “book a room” to “check…

Diaries From a Different Life Pt. 2

Life with a musician gets pretty hectic. And painful. In the last few weeks, I’ve done nothing but what feels like drinking and staying up all night. Which I know for a fact is what I used to do…