So since we are creating an ecommerce site, we have projects called "Catalog" which would contain search, PDP, PLP, etc or "Ordering" which would include the Cart, or Checkout flow. We use this to organize our files based on the structure of the site we build. So marketing designers would be on a different 'team' than the UX Designers. This basically represents the different design teams within our org. Also our devs didn't like seeing 'everything' for a project on a figma page.Īfter a discovery session with the team, we decided the best way for us to move forward was to structure our files as follows: Figma Teams We needed more structure after switching from Sketch/Invision to Figma. This is something that we're still working on. It's all about communication and collaboration. This is what has worked for us so far, btw we are a small team so maybe it can't work for teams of +20 people. It could be said that the master page is Prototype because it is what we present once we reach the solution but our development team takes more as a reference the Flows / UI Screens page. We do not have a master file because we try to ensure that our developers are also in the process of designing/solving the problem.
for example, we have a Figma file called "Profile" inside this file, we put everything that has to do with the user's profile, the same for mobile.Įach file is organized according to our process on different pages: Then each project is separated into "Features".
Internal is where all the libraries we use to design are, that is, our Design System, Flows, personas, etc. We have almost the same process but with some differences: In our case, we design for both Web and Mobile platforms, we have only 3 main projects for this.
0 kommentar(er)
