{"id":63592,"date":"2019-04-16T04:22:22","date_gmt":"2019-04-16T11:22:22","guid":{"rendered":"http:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/"},"modified":"2019-04-16T04:22:22","modified_gmt":"2019-04-16T11:22:22","slug":"design-at-scale-one-year-with-figma","status":"publish","type":"post","link":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/","title":{"rendered":"Design At Scale: One Year With Figma"},"content":{"rendered":"<link rel=\"canonical\" href=\"https:\/\/www.smashingmagazine.com\/2019\/04\/design-scale-figma\/\"><title>Design At Scale: One Year With Figma<\/title><\/p>\n<article>\n<header>\n<h1>Design At Scale: One Year With Figma<\/h1>\n<address>Paul Hanaoka<\/address>\n<p>                  <time datetime=\"2019-04-15T13:30:48+02:00\">2019-04-15T13:30:48+02:00<\/time><time datetime=\"2019-04-16T11:17:07+00:00\">2019-04-16T11:17:07+00:00<\/time><\/header>\n<p>This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet, a lot of it will be about Figma and how we succeeded at adopting this design tool in our team.<\/p>\n<p>The intended audience is experienced designers working in larger teams with design systems, developers or product managers looking to improve the way cross-functional teams work in their organization.<\/p>\n<p>I\u2019ve been using design tools in a professional setting for over ten years and am always trying to make teams I\u2019m serving work more efficiently and more effectively. From scripting and actions in Photoshop, to widget libraries in Axure, to Sketch plugins, and now with Figma \u2014 I\u2019ve helped design teams stay on the cutting edge without leaving developers or product managers behind.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/66238d3a-aeed-4e64-8983-80aef42f4cd3\/state-of-design-tools-2016.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/state-of-design-tools-2016.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/66238d3a-aeed-4e64-8983-80aef42f4cd3\/state-of-design-tools-2016.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/66238d3a-aeed-4e64-8983-80aef42f4cd3\/state-of-design-tools-2016.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/66238d3a-aeed-4e64-8983-80aef42f4cd3\/state-of-design-tools-2016.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/66238d3a-aeed-4e64-8983-80aef42f4cd3\/state-of-design-tools-2016.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/state-of-design-tools-2016.png?w=900\" sizes=\"100vw\" alt=\"Logos from products like Sketch, Principle, Invision, and more loosely tied together\"><\/a><figcaption>\n      The State of Design Tools 2015. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/66238d3a-aeed-4e64-8983-80aef42f4cd3\/state-of-design-tools-2016.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>Basic knowledge of design systems and tools will be helpful, but not necessary as I hope to share specific examples and also \u201chigh level\u201d concepts and methods that you can adapt for your team or context.<\/p>\n<div data-component=\"FeaturePanel\" data-audience=\"non-subscriber\" data-remove=\"true\"><\/div>\n<h3>Our Design Workflow Circa 2015<\/h3>\n<p>Our primary tool in 2015 was <a href=\"https:\/\/www.sketch.com\/\">Sketch<\/a>, and that\u2019s pretty much where the commonalities stopped. We all had different methods of prototyping, exporting, and sharing designs with stakeholders (InVision, Axure, Marvel, Google Slides, and even the antiquated Adobe PDF) and developers (Avocode, Zeplin, plugins without standalone apps like Measure). On rare occasions, we could send files directly to the engineers who were lucky enough to have the rare combination of a MacBook and a Sketch license.<\/p>\n<p>When InVision released the <a href=\"https:\/\/www.smashingmagazine.com\/2017\/02\/design-with-real-data-sketch-using-craft-plugin\/\">Craft plugin<\/a>, we were overjoyed \u2014 being able to prototype and upload screens from Sketch into InVision, sharing components and styles in nascent libraries across files \u2014 it was the designer\u2019s dream come true.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/acfcb35b-5fff-4d8d-9079-64a73e329252\/liferay-invision-projects.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/liferay-invision-projects.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/acfcb35b-5fff-4d8d-9079-64a73e329252\/liferay-invision-projects.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/acfcb35b-5fff-4d8d-9079-64a73e329252\/liferay-invision-projects.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/acfcb35b-5fff-4d8d-9079-64a73e329252\/liferay-invision-projects.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/acfcb35b-5fff-4d8d-9079-64a73e329252\/liferay-invision-projects.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/liferay-invision-projects.png?w=900\" sizes=\"100vw\" alt=\"A variety of screens in Liferay\u2019s 'My Projects' InVision dashboard\"><\/a><figcaption>\n      A peek into our InVision projects. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/acfcb35b-5fff-4d8d-9079-64a73e329252\/liferay-invision-projects.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>Eventually, we all converged on the InVision platform. We created and documented the processes that helped reduce much of the friction in stakeholder collaboration and developer handoff. Yet, due to the complex permissions structure, InVision remained a closed ecosystem \u2014 if you weren\u2019t a designer, there was an approval chain that made it difficult to get an InVision account, and once you got an account, you had to be added to the right groups.<\/p>\n<p>Manually managing versions and files, storing and organizing them in a shared drive, and dealing with sync conflicts were just a few of the things that caused us many headaches.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/b6d0ea77-fc93-4900-a07e-7dcfb030e905\/figma-overview-video-screenshot.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-overview-video-screenshot.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/b6d0ea77-fc93-4900-a07e-7dcfb030e905\/figma-overview-video-screenshot.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/b6d0ea77-fc93-4900-a07e-7dcfb030e905\/figma-overview-video-screenshot.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/b6d0ea77-fc93-4900-a07e-7dcfb030e905\/figma-overview-video-screenshot.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/b6d0ea77-fc93-4900-a07e-7dcfb030e905\/figma-overview-video-screenshot.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-overview-video-screenshot.png?w=900\" sizes=\"100vw\" alt=\"A screenshot from Figma\u2019s 'Getting Started' video on YouTube\"><\/a><figcaption><a href=\"https:\/\/www.youtube.com\/watch?v=RFi7wQHUP0c\">Getting Started in Figma<\/a>. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/b6d0ea77-fc93-4900-a07e-7dcfb030e905\/figma-overview-video-screenshot.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>Could we really have an all-in-one tool that had all the best features of Sketch and InVision, with the real-time collaboration and communication features found in Google Docs? In addition to reducing overhead from context switching, we could also potentially simplify from three tool subscriptions (for mockups, prototyping, and developer handoff), to only one.<\/p>\n<h3>The Process<\/h3>\n<p>The first designers from our team to adopt Figma started experimenting with it when the first Figma beta was released in 2016. The features were limited but covered 80% of what we needed. Sketch import was buggy, but we still found immense value in being able to collaborate in real-time and most importantly, we could do 90% of the design work for a project inside a single tool. Stakeholder feedback, revisions, and developer handoff improved exponentially.<\/p>\n<p>By 2017, we had a few designers using it for most of their work, and one of the <a href=\"https:\/\/twitter.com\/emilianogcicero\">Lexicon designers<\/a> (<a href=\"https:\/\/lexicondesign.io\/\">Liferay\u2019s design system<\/a>), Emiliano Cicero, was quickly becoming an evangelist \u2014 which turned out to be a key factor in convincing the rest of the team to make the switch.<\/p>\n<p>When Figma 2.0 debuted in the summer of 2017 with prototyping features added and huge improvements to the developer handoff capabilities, we knew this could be a viable tool for our global team. But how do you convince 20+ designers to abandon tools and workflows they love and have used comfortably for years?<\/p>\n<p>I could write a series on that subject, but I\u2019ll summarize by saying the two biggest things were: <strong>starting small<\/strong>, and creating a <strong>solid infrastructure<\/strong>.<\/p>\n<div><\/div>\n<h4>Starting Small<\/h4>\n<p>In the fall of 2017, we started our first trial of Figma with a product team distributed between the United States and Brazil. We were fortunate to have a week-long kickoff together in our Los Angeles office. Designing flows and wireframes together in Figma was so much faster and more efficient. We were able to divide up tasks and share files and components without having to worry about constantly syncing a folder or a library.<\/p>\n<p>At our <a href=\"ttps:\/\/liferay.design\/articles\/2018\/liferay-design-week-2018\/\">global gathering<\/a> in January 2018, we formulated a plan to slowly adopt Figma, using this team\u2019s experiences to help form the infrastructure we\u2019d need for the rest of the organization so that migration would be as seamless as possible.<\/p>\n<p>The biggest challenge we faced was a tight deadline \u2014 it didn\u2019t make any sense for us to rework our review and handoff process due to the scale of the project with multiple engineering teams and product managers distributed around the world. Even though the end result would have been better, the timing wasn\u2019t right. Another factor was Figma\u2019s lack of a reliable offline design experience <em>(more on that later)<\/em>, and for these reasons, the team decided to use Sketch and Figma for wireframes and mockups, but any prototyping or review had to be done in InVision.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/a90f05c5-b2d2-41b4-9b4d-0078dd41f210\/dam-at-liferay.jpeg?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/dam-at-liferay.jpeg 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/a90f05c5-b2d2-41b4-9b4d-0078dd41f210\/dam-at-liferay.jpeg 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/a90f05c5-b2d2-41b4-9b4d-0078dd41f210\/dam-at-liferay.jpeg 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/a90f05c5-b2d2-41b4-9b4d-0078dd41f210\/dam-at-liferay.jpeg 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/a90f05c5-b2d2-41b4-9b4d-0078dd41f210\/dam-at-liferay.jpeg 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/dam-at-liferay.jpeg?w=900\" sizes=\"100vw\" alt=\" A slide with about Liferay\u2019s Digital Asset Management structure\"><\/a><figcaption>\n      A DAM presentation from Design Week 2018. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/a90f05c5-b2d2-41b4-9b4d-0078dd41f210\/dam-at-liferay.jpeg\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<h4>Creating a solid Figma structure<\/h4>\n<p>One of the first steps was formulating rough guidelines for the project, file, and component organization. The foundation for these things was started by two junior (at the time) designers, <a href=\"http:\/\/twitter.com\/abelfhancock\">Abel Hancock<\/a> and <a href=\"http:\/\/twitter.com\/naokihisamoto\">Naoki Hisamoto<\/a>, who never developed the bad layer-naming habits that seem to come from designers who cut their teeth in Photoshop. This method for organization, coupled with a year spent developing a small library of components for Liferay.com properties, was critical to setting the rest of the global team up for success.<\/p>\n<p>An early organizational improvement created by one of our Liferay.com designers, inspired by <a href=\"https:\/\/twitter.com\/benfryc\/status\/998552146982391809\">Ben\u2019s tweet<\/a>, was our <strong>system of covers<\/strong>.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1f7a9fb5-94b4-4a33-a588-62eaba2e1e25\/figma-covers.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-covers.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1f7a9fb5-94b4-4a33-a588-62eaba2e1e25\/figma-covers.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1f7a9fb5-94b4-4a33-a588-62eaba2e1e25\/figma-covers.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1f7a9fb5-94b4-4a33-a588-62eaba2e1e25\/figma-covers.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1f7a9fb5-94b4-4a33-a588-62eaba2e1e25\/figma-covers.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-covers.png?w=900\" sizes=\"100vw\" alt=\"A screenshot showing Liferay\u2019s system for organizing Figma projects\"><\/a><figcaption>\n      Figma project covers, by <a href=\"https:\/\/twitter.com\/abelfhancock\">Abel Hancock<\/a>. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1f7a9fb5-94b4-4a33-a588-62eaba2e1e25\/figma-covers.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>We\u2019ve made this <a href=\"http:\/\/liferay.design\/resources\/figma\">file available<\/a> if you\u2019d like to copy it, otherwise it\u2019s a pretty straightforward hack:<\/p>\n<ol>\n<li>Create a single frame in the first page of your file that\u2019s 620\u00d7320.<\/li>\n<li>Add your design. If you have text, we found that the minimum size is ~24, the titles in our examples are set at 48.<\/li>\n<li>Enjoy!<\/li>\n<\/ol>\n<p><strong><em>Note:<\/em><\/strong> <em>There will always be a slight margin around your cover, but if you set the page canvas the same color as the card, it will reduce the appearance of this margin.<\/em><\/p>\n<p>This helped transform our library, not just for designers, but for project and product managers and engineers who are trying to find things quickly. The search functionality was already really good, but the covers helped people narrow things down even faster, plus it allowed us to instantly communicate the status of any given file.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-covers-in-action.gif\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-covers-in-action.gif?resize=788%2C502\" width=\"788\" height=\"502\" alt=\"An animated image a Figma project before and after the cover system\"><\/a><figcaption>Sparking Joy with Figma Covers (<a href=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-covers-in-action.gif\">Large preview<\/a>)<br \/>\n<\/figcaption><\/figure>\n<p>Prior to using Figma, in addition to a \u2018Master\u2019 design system Sketch file, most designers had base files they had developed over time with things like wireframing elements and basic components. As we coalesced into a single pattern, we started to combine everything and refined them into a single library. Since we were doing wireframes, mockups, and prototypes in Figma, we also started to abandon flow apps like <a href=\"https:\/\/www.lucidchart.com\/\">Lucidchart<\/a>, instead of making our own task flow components in Figma.<\/p>\n<p>Other utilities that we developed over time were <a href=\"https:\/\/www.figma.com\/file\/6GlUEYKNbmobxSgfW2fRQA\/liferay.design-utilities?node-id=624%3A5566\">redline components<\/a> for making precise handoff specs, <a href=\"https:\/\/www.figma.com\/file\/6GlUEYKNbmobxSgfW2fRQA\/liferay.design-utilities?node-id=1071%3A1313\">sticky notes<\/a> for affinity diagrams (and just about anything), and flow nodes.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/f01f2b47-bb8e-429f-9c05-2b90beedf966\/redlines-flow-affinity.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/redlines-flow-affinity.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/f01f2b47-bb8e-429f-9c05-2b90beedf966\/redlines-flow-affinity.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/f01f2b47-bb8e-429f-9c05-2b90beedf966\/redlines-flow-affinity.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/f01f2b47-bb8e-429f-9c05-2b90beedf966\/redlines-flow-affinity.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/f01f2b47-bb8e-429f-9c05-2b90beedf966\/redlines-flow-affinity.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/redlines-flow-affinity.png?w=900\" sizes=\"100vw\" alt=\"A screenshot showing Liferay\u2019s reusabile utility components for redlining, and creating flows and affinity diagrams\"><\/a><figcaption>\n      Liferay Design\u2019s redline, flow, and affinity components. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/f01f2b47-bb8e-429f-9c05-2b90beedf966\/redlines-flow-affinity.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<\/p>\n<p>One of the biggest benefits of doing this in Figma, was that improvements to any of these components that any designer made could easily be pulled into the library and then pushed out to all instances. Having this in a centralized place also makes maintenance a lot easier, as anyone on the team can contribute to improvements with a relatively simple process.<\/p>\n<p>A <strong>redline document<\/strong> is for <a href=\"https:\/\/www.quora.com\/What-is-redline-document-in-UI-designing\">making it easier for the developer<\/a> to know the dimensions, visual specs, and other properties of a UI component or a set of components. If you\u2019re interested in the topic, you can also check Dmitriy Fabrikant\u2019s article <a href=\"https:\/\/www.smashingmagazine.com\/2014\/10\/front-end-development-ode-to-specifications\/\">about design blueprints<\/a>.<\/p>\n<p> ?<\/p>\n<p>Some recommendations to keep in mind when creating components:<\/p>\n<ol>\n<li>Use of overrides and masters for powerful base components (<a href=\"https:\/\/liferay.design\/articles\/2019\/creating-atomic-components-in-figma\/\">more on that here<\/a>);<\/li>\n<li>Establish a consistent pattern for naming (we use <a href=\"https:\/\/www.smashingmagazine.com\/atomic-design-workflow\/\">the atomic model<\/a>);<\/li>\n<li>Document and label everything \u2014 especially layers.<\/li>\n<\/ol>\n<p>With the advanced styling features released at the beginning of June 2017, the systems team finished a complete version of our Lexicon library in between our big product releases in July and the ramp-up in August. This was the final piece we needed to support the global team. Designers working in Marketing and other departments had already been using Figma for some time, but by last Fall almost all of the other product teams had finalized the move over to Figma.<\/p>\n<p>As of today, most of the product designers are only using Figma, there are also a couple of designers that are working in legacy systems with lots of existing, complicated Sketch prototypes that aren\u2019t worth importing to Figma. Another exception is a few designers that occasionally use apps like <a href=\"https:\/\/www.principleformac.com\/\">Principle<\/a> or Adobe After Effects for more advanced animation that wouldn\u2019t make sense to do in Figma. We even have a few designers exploring <a href=\"https:\/\/www.smashingmagazine.com\/2018\/10\/new-framer-x-initial-impressions\/\">Framer X<\/a> for even more robust prototypes, especially with work that requires leveraging any kind of data at scale. While there are some designers using multiple tools on a semi-regular basis, 80% of our product designers are using Figma for all of their design and prototyping work.<\/p>\n<div><\/div>\n<h3>Continuous Improvements<\/h3>\n<p>We\u2019re always working on ways to work more effectively, and one of the current things we\u2019re iterating is best practices for naming pages. At first, we named pages according to the page name, but that proved problematic, plus, as we improved our libraries, the need for larger files with multiple pages was reduced.<\/p>\n<p>Currently, we\u2019re using a numbering system within files, with the top-most page being what\u2019s delivered to the developers. The next phase we\u2019re discussing nowadays is making the versions more meaningful with explicit labels (wireframes, mockups, breakpoints, etc.) and making better use of Figma\u2019s built-in versioning, establishing best practices for when and how to save versions.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1d7c9b85-e112-4a92-9361-5f4c63532eda\/pages-in-figma.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/pages-in-figma.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1d7c9b85-e112-4a92-9361-5f4c63532eda\/pages-in-figma.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1d7c9b85-e112-4a92-9361-5f4c63532eda\/pages-in-figma.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1d7c9b85-e112-4a92-9361-5f4c63532eda\/pages-in-figma.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1d7c9b85-e112-4a92-9361-5f4c63532eda\/pages-in-figma.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/pages-in-figma.png?w=900\" sizes=\"100vw\" alt=\" Two screenshots showing different ways to name Figma pages\"><\/a><figcaption>\n      The evolution of page organization within a Figma file. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1d7c9b85-e112-4a92-9361-5f4c63532eda\/pages-in-figma.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<h4>Final_Final_Last_2 \u2014 No More!<\/h4>\n<p>I generally hate to use the term \u2018game-changer\u2019, but when Figma released naming\/annotating to the version history last March, it dramatically changed the way we organized our files. Previously, we all had different ways of saving iterations and versions.<\/p>\n<p>Usually we would create new pages within a single file, sometimes with large files we would duplicate them and add a letter at the end of the filename to signal an iteration. If you were going to make drastic changes, then you might create a new file and append a version number. This was very natural, coming from the Photoshop\/Sketch paradigm of managing multiple files for everything.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/ff4f5f3f-90f1-4238-8fd2-2a4304574fbc\/figma-history-timeline-version.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-history-timeline-version.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/ff4f5f3f-90f1-4238-8fd2-2a4304574fbc\/figma-history-timeline-version.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/ff4f5f3f-90f1-4238-8fd2-2a4304574fbc\/figma-history-timeline-version.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/ff4f5f3f-90f1-4238-8fd2-2a4304574fbc\/figma-history-timeline-version.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/ff4f5f3f-90f1-4238-8fd2-2a4304574fbc\/figma-history-timeline-version.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/figma-history-timeline-version.png?w=900\" sizes=\"70vw\" alt=\"A screenshot showing what Figma\u2019s version history timeline looks like\"><\/a><figcaption>\n      Version history timeline view (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/ff4f5f3f-90f1-4238-8fd2-2a4304574fbc\/figma-history-timeline-version.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>The ability to work, periodically pausing to name and annotate a point in time will be very familiar for anyone who has used a <a href=\"https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-About-Version-Control\">version control like Git<\/a> before. You can even look at the whole file history, and go into past snapshots, pick one out and name and annotate it.<\/p>\n<p>If you want to go back and revert to a past version, you can restore it and work on that file from that point in the history. The best part is that you didn\u2019t lose any of the work because the version you \u2018restored\u2019 wasn\u2019t deleting anything; it was simply copying that state and pasting it at the top.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1b257f74-955e-4256-9bd6-29e0d813b834\/version-control.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/version-control.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1b257f74-955e-4256-9bd6-29e0d813b834\/version-control.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1b257f74-955e-4256-9bd6-29e0d813b834\/version-control.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1b257f74-955e-4256-9bd6-29e0d813b834\/version-control.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1b257f74-955e-4256-9bd6-29e0d813b834\/version-control.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/version-control.png?w=900\" sizes=\"100vw\" alt=\"A diagram showing how restoring past versions of a Figma file works\"><\/a><figcaption>\n      Git it? (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/1b257f74-955e-4256-9bd6-29e0d813b834\/version-control.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>In this illustration, the designer arrives at <code>final 3.0<\/code> after restoring <code>final 1.1<\/code>, but the file version history is still completely visible and accessible.<\/p>\n<p>In cases where you\u2019re starting a new project, or want to make some really dramatic changes to the file, it can be necessary for you to \u2018fork\u2019 the file. Figma allows you to duplicate a file at any given point in the history, but it\u2019s important to note that the file history will <strong>not<\/strong> be copied.<\/p>\n<p>We\u2019ve found that a good way to work in this versioned system is to use your file history in a similar way to how a developer uses git \u2014 think of a Figma version as a commit or pull-request, and name and annotate them as such. For more, smarter thoughts on this, I recommend Seth Robertson\u2019s <em><a href=\"http:\/\/sethrobertson.github.com\/GitBestPractices\/\">Commit Often, Perfect Later, Publish Once: Git Best Practices<\/a><\/em> \u2014 this is a good general philosophy for how to work in a version-controlled ecosystem. Also, Chris Beams\u2019s <em><a href=\"https:\/\/chris.beams.io\/posts\/git-commit\/\">How to Write a Git Commit Message<\/a><\/em> is a great guide to writing meaningful and useful notes as you work.<\/p>\n<p>Some practical tips we\u2019ve discovered:<\/p>\n<ol>\n<li><strong>Keep titles to 25 characters or less<\/strong>.<br \/>\nLonger titles are clipped and you have to double-click on the note in the version history to open up the \u2018Edit Version Information\u2019 modal to read it.<\/li>\n<li><strong>Keep your description to 140 characters or less<\/strong>.<br \/>\nThe full description is always shown, so keeping it to the point helps keep the history readable.<\/li>\n<li><strong>Use the imperative mood for the title<\/strong>.<br \/>\nThis gives the future you a clearer idea of what will happen when you click on that point in time, e.g. \u201cchanging button colors to blue\u201d vs. \u201cchange buttons to blue.\u201d<\/li>\n<li><strong>Use the description to explain \u2018what\u2019 and \u2018why\u2019 versus \u2018how\u2019<\/strong>.<br \/>\nAnswering the \u2018why\u2019 is a critical part of any designers job, so this helps you focus on what\u2019s important as you\u2019re working as well as provide better information for you in the future.<\/li>\n<\/ol>\n<h4>Working Offline<\/h4>\n<p><strong><em>Disclaimer:<\/em><\/strong> <em>This is based on our own experience, and a lot of it is our best guess as to how it works.<\/em><\/p>\n<p>As I mentioned before, offline support in Figma is tenuous. If you already have a file open before going offline, you can continue working on the file. It seems like each change you make is timestamped. In the case of someone else working on the <em>same<\/em> <em>file<\/em> while you were offline, then the latest change will be the one rendered once you do come back online.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/3db30ef7-f38d-454b-b5c3-2de1ce7050dd\/working-offline.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/working-offline.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/3db30ef7-f38d-454b-b5c3-2de1ce7050dd\/working-offline.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/3db30ef7-f38d-454b-b5c3-2de1ce7050dd\/working-offline.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/3db30ef7-f38d-454b-b5c3-2de1ce7050dd\/working-offline.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/3db30ef7-f38d-454b-b5c3-2de1ce7050dd\/working-offline.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/working-offline.png?w=900\" sizes=\"100vw\" alt=\"A series of screenshots showing how offline editing works\"><\/a><figcaption>\n       When Cat came back online, her button position change was made, and merged with the Nerd\u2019s color changes. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/3db30ef7-f38d-454b-b5c3-2de1ce7050dd\/working-offline.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>In this simple example, it doesn\u2019t seem like too big of a deal \u2014 but in real life, this can get really messy, really fast. In addition to the high possibility of someone overriding your work, frames and groups could get stacked on top of one another.<\/p>\n<p>Our workflow is to duplicate the page before (or after) going offline, and then do your work in that copy. That way it will be untouched when you come back online, and you can do any necessary merges manually.<\/p>\n<h3>\u201cF\u201d Is For Future<\/h3>\n<p>Adopting a new tool is never easy, but in the end, the benefits may far outweigh the costs.<\/p>\n<p>The biggest areas of improvement our team has experienced are:<\/p>\n<ul>\n<li><strong>Collaboration<\/strong><br \/>\nIt\u2019s much easier to share our work and improvements with the team and community.<\/li>\n<li><strong>Transparency<\/strong><br \/>\nA system that is open by default is naturally more inclusive to people outside of the field of design.<\/li>\n<li><strong>Evolution<\/strong><br \/>\nRemoving the \u201clayers\u201d between designers and engineers, enabling us to take the next step in design maturity.<\/li>\n<li><strong>Operations<\/strong><br \/>\nAdopting a single tool for wireframes, mockups, prototypes, and developer handoffs makes life easier for accounting, IT, and management.<\/li>\n<\/ul>\n<p>Reducing the overall number of subscriptions was really helpful for our team, but as costs can vary from \u2018free\u2019 to over $500 per year this might not make sense for your specific context and needs. For a full breakdown, see <a href=\"https:\/\/www.figma.com\/pricing\/\">Figma\u2019s pricing page<\/a>.<\/p>\n<h4>Grow And Get Better<\/h4>\n<p>Of course, no tool is perfect, and there\u2019s always room for improvements. Some things that were missing from previous tools we used are:<\/p>\n<ol>\n<li><strong>No plugin ecosystem<\/strong>.<br \/>\nSketch\u2019s extensibility was a huge factor in making the switch from Photoshop a no-brainer. Figma does have a <a href=\"https:\/\/www.figma.com\/blog\/introducing-figmas-platform\">web API<\/a>, but currently, there is no \u2018write\u2019 functionality. For now, Sketch remains the market leader with its vibrant community of extensions and plugins. (Of course, things might change in the future in case <a href=\"https:\/\/twitter.com\/figmadesign\/status\/1112831648486379521\">Figma opens the stage<\/a> for plugin development as well.)<\/li>\n<li><strong>Importing web, or JSON data  in prototypes<\/strong>.<br \/>\nIt would be a lot easier for us <a href=\"https:\/\/www.smashingmagazine.com\/2017\/02\/design-with-real-data-sketch-using-craft-plugin\/\">to design with real data<\/a>. Sketch recently introduced a \u201cData\u201d feature in v.52, InVision\u2019s Craft plugin is still very much the gold standard when it comes to easily addxing large amounts of different data \u2014 and for now, we\u2019re stuck manually populating text fields.<\/li>\n<li><strong>More motion<\/strong>.<br \/>\nThe <a href=\"https:\/\/www.figma.com\/blog\/animate-your-figma-designs-with-our-new-principle-integration\/\">Principle integration<\/a> is nice (if you have Principle), but having basic animation and advanced prototyping features in Figma would be a lot better.<\/li>\n<li><strong>A smoother offline experience<\/strong><br \/>\nAs mentioned previously, as long as you have the Figma file open before going offline, you\u2019re fine. This is probably OK for most people \u2014 but if you like to shut down your computer every night, it can be painful when you open it in the morning on a train or airplane and realize you forgot to leave Figma open.<\/li>\n<\/ol>\n<h4>Open-Source Design<\/h4>\n<p>A few months ago, the always controversial <a href=\"http:\/\/twitter.com\/dannpetty\">Dann Petty<\/a> recently tweeted about developers having GitHub, photographers having <a href=\"https:\/\/unsplash.com\/\">Unsplash<\/a> \u2014 but designers not having a platform for sharing things for free. Design Twitter\u2122? swooped in and he deleted his tweet before I could get a screengrab, but one thing I\u2019d like to mention is that what we\u2019re very passionate about at Liferay, is <a href=\"https:\/\/en.wikipedia.org\/wiki\/Open-source_software\">open source<\/a>. To that end, we\u2019ve created a Figma project for resources to share with the design community.<\/p>\n<figure><a href=\"https:\/\/i0.wp.com\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/8d1fe892-9a87-41cf-9c81-6ea1247f2946\/open-source-design.png?ssl=1\"><\/p>\n<p>    <img data-recalc-dims=\"1\" decoding=\"async\" srcset=\"http:\/\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/open-source-design.png 400w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_800\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/8d1fe892-9a87-41cf-9c81-6ea1247f2946\/open-source-design.png 800w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1200\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/8d1fe892-9a87-41cf-9c81-6ea1247f2946\/open-source-design.png 1200w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_1600\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/8d1fe892-9a87-41cf-9c81-6ea1247f2946\/open-source-design.png 1600w,\n\t\t\t        https:\/\/res.cloudinary.com\/indysigner\/image\/fetch\/f_auto,q_auto\/w_2000\/https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/8d1fe892-9a87-41cf-9c81-6ea1247f2946\/open-source-design.png 2000w\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/open-source-design.png?w=900\" sizes=\"100vw\" alt=\"A screenshot of Liferay\u2019s open source Figma project\"><\/a><figcaption>\n      Open sourced files from Liferay.Design. (<a href=\"https:\/\/cloud.netlifyusercontent.com\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/8d1fe892-9a87-41cf-9c81-6ea1247f2946\/open-source-design.png\">Large preview<\/a>)<br \/>\n    <\/figcaption><\/figure>\n<p>To access any of these files, check out <a href=\"https:\/\/liferay.design\/resources\/figma\">liferay.design\/resources\/figma<\/a>, and stay tuned as we grow and share more!<\/p>\n<h4>Further Reading<\/h4>\n<ul>\n<li>\u201c<a href=\"https:\/\/medium.com\/mendesaltaren\/our-first-6-months-with-figma-aef60cae5d89\">Our First 6 Months With Figma<\/a>,\u201d Danny Saltaren<\/li>\n<li>\u201c<a href=\"https:\/\/medium.com\/@willdjthrill\/waiting-for-a-sign-to-start-building-your-design-teams-component-library-c43f4352c764\">Waiting For A Sign To Start Building Your Design Team\u2019s Component Library?<\/a>,\u201d William Newton<\/li>\n<li>\u201c<a href=\"https:\/\/blog.nicolesaidy.com\/how-to-streamline-your-ui-ux-workflow-with-figma-b72c30596435\">How To Streamline Your UI\/UX Workflow With Figma<\/a>,\u201d  Nicole Saidy<\/li>\n<li>\u201c<a href=\"https:\/\/www.figma.com\/blog\/getting-started-with-teams-in-figma-organization\/\">Getting Started With Teams In Figma Organization<\/a>,\u201d  Thomas Lowry<\/li>\n<li>\u201c<a href=\"https:\/\/medium.com\/figma-design\/5-ways-to-structure-your-workflow-with-pages-in-figma-f970efa36141\">5 Ways To Structure Your Workflow With Pages In Figma<\/a>,\u201d Josh Dunsterville<\/li>\n<li>\u201c<a href=\"https:\/\/www.figma.com\/blog\/component-styles-and-shared-library-best-practices\/\">Best Practices: Components, Styles, And Shared Libraries<\/a>,\u201d Thomas Lowry<\/li>\n<li>\u201c<a href=\"https:\/\/insights.papertiger.com\/figma-a-fluid-and-modular-design-approach-to-typography-with-components-a9feef8e84a6\">Figma: A Fluid And Modular Design Approach To Typography With Components<\/a>,\u201d Mirko Santangelo<\/li>\n<\/ul>\n<h4>Other Resources<\/h4>\n<ul>\n<li><a href=\"https:\/\/spectrum.chat\/figma\/\">Figma Community<\/a> on <a href=\"http:\/\/spectrum.chat\/\">Spectrum<\/a><\/li>\n<li><a href=\"https:\/\/medium.com\/figma-africa\/figma-design-handbook-p-t-1-60ff23c918c9\">Figma Design Handbook<\/a> by <a href=\"https:\/\/medium.com\/@dukauwa.du\">David Ukauwa<\/a><\/li>\n<\/ul>\n<div>\n  <img data-recalc-dims=\"1\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/logo-red-11.png?w=900\" alt=\"Smashing Editorial\"><span>(mb, yk, il)<\/span>\n<\/div>\n<\/article>\n<p class=\"wpematico_credit\"><small>Powered by <a href=\"http:\/\/www.wpematico.com\" target=\"_blank\">WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Design At Scale: One Year With Figma Design At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00 This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article&#8230;<a class=\"moretag\" href=\"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/\"> Read the full article&#8230;<\/a><\/p>\n","protected":false},"author":4,"featured_media":63593,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[371],"tags":[],"class_list":["post-63592","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-user-experience"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Guest Contribution\"\/>\n\t<meta name=\"keywords\" content=\"user experience\" \/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Design for Immersive Technologies | User Experience for Games, Virtual Reality (VR) and Augmented\/Mixed Reality (AR\/MR)\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Design At Scale: One Year With Figma | Design for Immersive Technologies\" \/>\n\t\t<meta property=\"og:description\" content=\"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-04-16T11:22:22+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-04-16T11:22:22+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Design At Scale: One Year With Figma | Design for Immersive Technologies\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#article\",\"name\":\"Design At Scale: One Year With Figma | Design for Immersive Technologies\",\"headline\":\"Design At Scale: One Year With Figma\",\"author\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/author\\\/guestcontribution\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/www.taterboy.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/04\\\/state-of-design-tools-2016.png?fit=400%2C250&ssl=1\",\"width\":400,\"height\":250},\"datePublished\":\"2019-04-16T04:22:22-07:00\",\"dateModified\":\"2019-04-16T04:22:22-07:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#webpage\"},\"articleSection\":\"User Experience\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.taterboy.com\\\/blog\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/category\\\/user-experience\\\/#listItem\",\"name\":\"User Experience\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/category\\\/user-experience\\\/#listItem\",\"position\":2,\"name\":\"User Experience\",\"item\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/category\\\/user-experience\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#listItem\",\"name\":\"Design At Scale: One Year With Figma\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#listItem\",\"position\":3,\"name\":\"Design At Scale: One Year With Figma\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/category\\\/user-experience\\\/#listItem\",\"name\":\"User Experience\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/#organization\",\"name\":\"Design for Immersive Technologies\",\"description\":\"User Experience for Games, Virtual Reality (VR) and Augmented\\\/Mixed Reality (AR\\\/MR)\",\"url\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/author\\\/guestcontribution\\\/#author\",\"url\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/author\\\/guestcontribution\\\/\",\"name\":\"Guest Contribution\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d2aad73eb0f48c67b141e9fc978a0e498969791ed623346e361d02d19775b0bb?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Guest Contribution\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#webpage\",\"url\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/\",\"name\":\"Design At Scale: One Year With Figma | Design for Immersive Technologies\",\"description\":\"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\\u2019t guess from the title of the article just yet,\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/author\\\/guestcontribution\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/author\\\/guestcontribution\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/www.taterboy.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/04\\\/state-of-design-tools-2016.png?fit=400%2C250&ssl=1\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#mainImage\",\"width\":400,\"height\":250},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/2019\\\/04\\\/design-at-scale-one-year-with-figma\\\/#mainImage\"},\"datePublished\":\"2019-04-16T04:22:22-07:00\",\"dateModified\":\"2019-04-16T04:22:22-07:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/\",\"name\":\"Design for Immersive Technologies\",\"description\":\"User Experience for Games, Virtual Reality (VR) and Augmented\\\/Mixed Reality (AR\\\/MR)\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.taterboy.com\\\/blog\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Design At Scale: One Year With Figma | Design for Immersive Technologies","description":"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,","canonical_url":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/","robots":"max-image-preview:large","keywords":"user experience","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#article","name":"Design At Scale: One Year With Figma | Design for Immersive Technologies","headline":"Design At Scale: One Year With Figma","author":{"@id":"https:\/\/www.taterboy.com\/blog\/author\/guestcontribution\/#author"},"publisher":{"@id":"https:\/\/www.taterboy.com\/blog\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/state-of-design-tools-2016.png?fit=400%2C250&ssl=1","width":400,"height":250},"datePublished":"2019-04-16T04:22:22-07:00","dateModified":"2019-04-16T04:22:22-07:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#webpage"},"isPartOf":{"@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#webpage"},"articleSection":"User Experience"},{"@type":"BreadcrumbList","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog#listItem","position":1,"name":"Home","item":"https:\/\/www.taterboy.com\/blog","nextItem":{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog\/category\/user-experience\/#listItem","name":"User Experience"}},{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog\/category\/user-experience\/#listItem","position":2,"name":"User Experience","item":"https:\/\/www.taterboy.com\/blog\/category\/user-experience\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#listItem","name":"Design At Scale: One Year With Figma"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#listItem","position":3,"name":"Design At Scale: One Year With Figma","previousItem":{"@type":"ListItem","@id":"https:\/\/www.taterboy.com\/blog\/category\/user-experience\/#listItem","name":"User Experience"}}]},{"@type":"Organization","@id":"https:\/\/www.taterboy.com\/blog\/#organization","name":"Design for Immersive Technologies","description":"User Experience for Games, Virtual Reality (VR) and Augmented\/Mixed Reality (AR\/MR)","url":"https:\/\/www.taterboy.com\/blog\/"},{"@type":"Person","@id":"https:\/\/www.taterboy.com\/blog\/author\/guestcontribution\/#author","url":"https:\/\/www.taterboy.com\/blog\/author\/guestcontribution\/","name":"Guest Contribution","image":{"@type":"ImageObject","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/d2aad73eb0f48c67b141e9fc978a0e498969791ed623346e361d02d19775b0bb?s=96&d=mm&r=g","width":96,"height":96,"caption":"Guest Contribution"}},{"@type":"WebPage","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#webpage","url":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/","name":"Design At Scale: One Year With Figma | Design for Immersive Technologies","description":"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.taterboy.com\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#breadcrumblist"},"author":{"@id":"https:\/\/www.taterboy.com\/blog\/author\/guestcontribution\/#author"},"creator":{"@id":"https:\/\/www.taterboy.com\/blog\/author\/guestcontribution\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/state-of-design-tools-2016.png?fit=400%2C250&ssl=1","@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#mainImage","width":400,"height":250},"primaryImageOfPage":{"@id":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/#mainImage"},"datePublished":"2019-04-16T04:22:22-07:00","dateModified":"2019-04-16T04:22:22-07:00"},{"@type":"WebSite","@id":"https:\/\/www.taterboy.com\/blog\/#website","url":"https:\/\/www.taterboy.com\/blog\/","name":"Design for Immersive Technologies","description":"User Experience for Games, Virtual Reality (VR) and Augmented\/Mixed Reality (AR\/MR)","inLanguage":"en-US","publisher":{"@id":"https:\/\/www.taterboy.com\/blog\/#organization"}}]},"og:locale":"en_US","og:site_name":"Design for Immersive Technologies | User Experience for Games, Virtual Reality (VR) and Augmented\/Mixed Reality (AR\/MR)","og:type":"article","og:title":"Design At Scale: One Year With Figma | Design for Immersive Technologies","og:description":"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,","og:url":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/","article:published_time":"2019-04-16T11:22:22+00:00","article:modified_time":"2019-04-16T11:22:22+00:00","twitter:card":"summary","twitter:title":"Design At Scale: One Year With Figma | Design for Immersive Technologies","twitter:description":"Design At Scale: One Year With FigmaDesign At Scale: One Year With Figma Paul Hanaoka 2019-04-15T13:30:48+02:002019-04-16T11:17:07+00:00This article will be about how large teams can benefit from using more open, collaborative tooling and how to make adoption and migration feasible and pleasant. Also, in case you didn\u2019t guess from the title of the article just yet,"},"aioseo_meta_data":{"post_id":"63592","title":null,"description":null,"keywords":null,"keyphrases":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_custom_url":null,"og_image_custom_fields":null,"og_custom_image_width":null,"og_custom_image_height":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"location":null,"local_seo":null,"created":"2021-02-07 20:58:43","updated":"2026-09-01 08:42:07","focus_keyword":null,"additional_keywords":null,"truseo_locale":null,"primary_term":null,"og_image_url":null,"og_image_width":null,"og_image_height":null,"twitter_image_url":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"limit_modified_date":false,"ai":null,"breadcrumb_settings":null,"seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.taterboy.com\/blog\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.taterboy.com\/blog\/category\/user-experience\/\" title=\"User Experience\">User Experience<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tDesign At Scale: One Year With Figma\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/www.taterboy.com\/blog"},{"label":"User Experience","link":"https:\/\/www.taterboy.com\/blog\/category\/user-experience\/"},{"label":"Design At Scale: One Year With Figma","link":"https:\/\/www.taterboy.com\/blog\/2019\/04\/design-at-scale-one-year-with-figma\/"}],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8wzr5-gxG","jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.taterboy.com\/blog\/wp-content\/uploads\/2019\/04\/state-of-design-tools-2016.png?fit=400%2C250&ssl=1","_links":{"self":[{"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/posts\/63592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/comments?post=63592"}],"version-history":[{"count":0,"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/posts\/63592\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/media\/63593"}],"wp:attachment":[{"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/media?parent=63592"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/categories?post=63592"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.taterboy.com\/blog\/wp-json\/wp\/v2\/tags?post=63592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}