#ZEPLIN FIGMA HOW TO#

You can use different variables and different ways to separate the file list. Then you can do, for example, some planning poker with your team to find out what are the priority things that will be migrated to Figma. The goal is that you get a variable of priority and effort for each item. Where 1 it's low priority/effort and 5 it's hight priority/effort.

#ZEPLIN FIGMA HOW TO#

This is a simple example of how to create a list of your design files sorted by priority vs effort and get an average. Leave behind what you and your team have mapped as an old/bad habit and take this opportunity to try new approaches, in the case of Figma, learn about plugins, community libraries, etc. Everyone has left a chair or table at the old house in order to buy a better one for the next home. The process change is the best opportunity we have to decide what to keep with us and what to leave behind. What are our current pains and gaps in this workflow?ġ.2 Make an inventory of what is essential.How many UI libraries do we have? How are they organized?.How is the current workflow for developers/POs?.Do not start creating a new workflow or organization directly in Figma, try answering questions like these beforehand: 1.1 Mapping the current workflowįirst of all, observe and map your team’s current workflow. It’s about having a goal, not a cover page.

There’s no use creating cover pages for projects in Figma if no one will ever understand how things are organized.

You need to set a date to start and finish this process, create steps, and define your team’s priorities.

Zeplin figma