Being an intuitive and user-friendly tool and having the possibility of real-time collaboration are some of the main reasons people choose to use Figma. But the migration process to Figma may sometimes be painful or time-consuming.

人們選擇使用Figma是主要原因，它是一種直觀且用戶友好的工具，并且可以進行實時協作。 但是遷移到Figma的過程有時會很痛苦或耗時。

In the past 2 years, I have had the opportunity to lead two migration processes from Sketch/Abstract/Zeplin to Figma. I have faced two different setups: the first one was at C6 Bank with more than 30 designers and the second one has been at Chama App, where currently our design team has 9 people.

在過去的兩年中，我有機會領導了從Sketch / Abstract / Zeplin到Figma的兩個遷移過程。 我遇到了兩種不同的設置：第一種是在C6 Bank擁有30多名設計師，第二種是在Chama App中 ，目前我們的設計團隊有9人。

In both cases, we have faced problems. Some were quite similar, but others were unexpected. Based on that, I would like to share with you some tips I learned in both cases that will definitely help your team in this migration process.

在這兩種情況下，我們都面臨問題。 有些非常相似，但其他卻出乎意料。 基于此，我想與您分享我在這兩種情況下學到的一些技巧，這些技巧必定會在遷移過程中為您的團隊提供幫助。

1.制定計劃 (1. Make a Plan)

You need to set a date to start and finish this process, create steps, and define your team’s priorities. There’s no use creating cover pages for projects in Figma if no one will ever understand how things are organized.

您需要設置一個日期來開始和完成此過程，創建步驟并定義團隊的優先級。 如果沒人能理解事物的組織方式，那么在Figma中為項目創建封面是沒有用的。

It’s about having a goal, not a cover page.

這是關于有目標，而不是封面。

1.1映射當前工作流程 (1.1 Mapping the current workflow)

First of all, observe and map your team’s current workflow. Do not start creating a new workflow or organization directly in Figma, try answering questions like these beforehand:

首先，觀察并繪制團隊當前的工作流程。 不要開始直接在Figma中創建新的工作流程或組織，請嘗試事先回答以下問題：

• How many teams/squads do we have?
  我們有多少支球隊/小隊？
• How many projects/products do we have?
  我們有多少個項目/產品？
• How do we organize the design team?
  我們如何組織設計團隊？
• How is the current workflow for developers/POs?
  開發人員/ PO的當前工作流程如何？
• Which plugins are we using?
  我們正在使用哪些插件？
• How many UI libraries do we have? How are they organized?
  我們有幾個UI庫？ 他們是如何組織的？
• What are our current pains and gaps in this workflow?
  我們目前在此工作流程中遇到的困難和差距是什么？

1.2盤點哪些是必需的 (1.2 Make an inventory of what is essential)

The process change is the best opportunity we have to decide what to keep with us and what to leave behind. Everyone has left a chair or table at the old house in order to buy a better one for the next home.

流程更改是我們必須決定與我們保持什么和留下什么最好的機會。 每個人都在老房子里留下了椅子或桌子，以便為下一個房屋購買更好的椅子或桌子。

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.

拋棄您和您的團隊已將其映射為舊習慣/壞習慣的方式，并借此機會嘗試新方法，例如Figma，了解插件，社區庫等。

This is a simple example of how to create a list of your design files sorted by priority vs effort and get an average. Where 1 it's low priority/effort and 5 it's hight priority/effort.

這是一個簡單的示例，說明如何創建按優先級與工作量排序的設計文件列表并獲得平均值。 其中1是低優先級/工作量，而5是高優先級/工作量。

The goal is that you get a variable of priority and effort for each item. 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.

目標是為每個項目獲得一個優先級和工作量變量。 然后，例如，您可以與團隊一起做一些計劃撲克，以找出將要遷移到Figma的優先事項。

You can use different variables and different ways to separate the file list.

您可以使用不同的變量和不同的方式來分隔文件列表。

1.3創建遷移階段 (1.3 Create migration phases)

A common question I heard in both cases was “Do I need to recreate all the screens in Figma?” and my answer for this is “not exactly”. Everything will depend on your goals and how you plan this migration.

我在這兩種情況下都聽到的一個常見問題是“是否需要在Figma中重新創建所有屏幕？” 我對此的回答是“不完全”。 一切都取決于您的目標以及如何計劃此遷移。

For example, you can try to migrate everything in one month or one week, but in both cases, you will realize that it doesn’t make sense and your team still needs some components, branding assets, icons, etc.

例如，您可以嘗試在一個月或一周內遷移所有內容，但在兩種情況下，您都將意識到這沒有任何意義，并且您的團隊仍然需要一些組件，品牌資產，圖標等。

As a project, this migration needs to have an MVP (minimum valuable product). Getting your priority file list and defining the releases that you can work on is more useful than having a date for all the migration process, so you’d better set a date to these releases instead.

作為一個項目，此遷移需要具有MVP(最低價值的產品)。 獲取優先級文件列表并定義可以使用的發行版比為所有遷移過程指定日期更為有用，因此最好為這些發行版設置一個日期。

2.定義工作流程 (2. Define a workflow)

We have a lot of possibilities of how to organize teams/projects/files in Figma. One of the advantages of that is having everything in one place in a collaborative way.

關于如何在Figma中組織團隊/項目/文件，我們有很多可能性。 優點之一是將所有內容以一種協作的方式放在一個地方。

As I said before, to define the best organization process for your team, you previously need to have mapped your current workflow, found the gaps, and figured out how you can do make this work in a more productive way in Figma.

如前所述，要為團隊定義最佳的組織流程，您以前需要繪制當前的工作流程，找出差距，并弄清楚如何在Figma中以更有效的方式進行這項工作。

2.1工作區 (2.1 Workspaces)

In your workspace on Figma you can have only one team organized per products, then arrange them per feature, flow, or OS for example.

在Figma上的工作區中，每個產品只能組織一個團隊，然后按功能，流程或操作系統進行排列。

We have used this approach at Chama and it has worked well for the current moment we face and the team size we have.

我們在Chama使用了這種方法，并且在當前所面對的時刻以及我們擁有的團隊規模方面都非常有效。

If your design teams are organized according to sub-products or if your company is holding different products in a centralized design management way, this second approach is probably more useful for you.

如果您的設計團隊是根據子產品組織的，或者您的公司以集中式設計管理方式持有不同的產品，則第二種方法可能對您更有用。

As you see in the picture above, you can have multiple teams/products/squads and subdivide them into sub-products/ projects/tracks in Figma. You can also have an entire team for the core design system and link the libraries across the teams/products/squads.

如上圖所示，您可以擁有多個團隊/產品/小組，然后在Figma中將它們細分為子產品/項目/軌道。 您也可以為核心設計系統配備一個完整的團隊，并在團隊/產品/團隊之間鏈接庫。

Spotify has a good example of how to organize the workspace in Figma for a large design team.

Spotify有一個很好的示例，說明了如何為大型設計團隊在Figma中組織工作區。

👉🏾 https://spotify.design/article/how-spotify-organises-work-in-figma-to-improve-collaboration

👉🏾https : //spotify.design/article/how-spotify-organises-work-in-figma-to-improve-collaboration

2.2權限 (2.2 Permissions)

Figma gives us the possibility of sharing a team, a project, and a file.

Figma使我們可以共享一個團隊，一個項目和一個文件。

Creating a list of who needs to have access to your projects and files and defining the levels of these permissions can help you avoid stakeholder’s anxieties and unwanted stalkers 👀.

創建需要訪問您的項目和文件的人員的列表，并定義這些權限的級別，可以幫助您避免利益相關者的焦慮和不必要的纏擾者。

3.計劃-做-測試-調整 (3. Plan — Do — Test — Adjust)

No workflow is forever. You will probably learn new things and change things in your organization by using Figma. So you should talk to as many people as you can, collect feedback, and improve.

沒有工作流是永遠的。 您可能會使用Figma學習新事物并改變組織中的事物。 因此，您應該與盡可能多的人交談，收集反饋并進行改進。

There is no magic formula for a good organization and design workflow. However, collaborative work can make this whole process more fluid and pleasant.

良好的組織和設計工作流程沒有神奇的公式。 但是，協同工作可以使整個過程更加流暢和愉快。

4.創建一個入職流程 (4. Create an onboarding process)

Help your team have a fluid learning process. Create some flyers, offer lectures, or promote talks to explain more about the tool and the new workflow in Figma.

幫助您的團隊擁有流暢的學習過程。 創建一些傳單，提供講座或促進講座，以進一步解釋Figma中的工具和新工作流程。

Some ideas:

一些想法：

• Bot in slack with some tips and tricks;
  懶惰的人有一些技巧和竅門；
• Design Talks;
  設計講座；
• Mandatory onboard for new designers/developers/POs;
  新設計者/開發者/采購員必須攜帶；
• Hackathon: Build our plugin
  Hackathon：構建我們的插件

The most important thing that I took from this process was the collaboration and commitment from my team to make this migration works. Remember isn’t about you or the hype about a design tool. It's about providing a better environment for all.

我從此過程中獲得的最重要的東西是團隊的協作和承諾，以使此遷移有效。 記住與您無關，也不與設計工具有關。 這是為所有人提供更好的環境。

S

小號

Thanks for reading! I appreciate your time.

謝謝閱讀！ 感謝您的寶貴時間。