How to Organize Projects in Figma: Part 2
Continuing our series — find points 1–5 in our first part. Let’s dive into more!
6. Comments for Designers, Analysts, and Developers
Sometimes, interfaces include complex solutions that aren’t immediately clear from a static image. It’s crucial to annotate these elements with stickers. Consider a color-coding system for clarity: yellow stickers for designer notes, blue for client queries, etc.
7. Naming Prototypes for Testing
For hallway or moderated testing, multiple starting points in a prototype are often necessary. Typically, these are blandly named Flow 1, Flow 2, Flow 3, and so forth. As you might guess, these names aren’t very informative, leaving the purpose of each prototype ambiguous.
8. Consistency in the UI Kit
Interfaces should be built from components, typically organized on a separate page titled ‘UI-kit’. Components should feature variants that display different states. Like previous points, variant properties should be renamed from nondescript labels like Property 1 or Variant 1 to more descriptive names.
9. Guidance for Other Designers
If you’re not the only designer on a product, it’s vital to leave behind information for colleagues. Use comments to note your name and the status of your work (e.g., “complete,” “in progress,” “draft”) so others know who to contact with questions about a specific screen.
10. Project Presentation in Video Format
If you link to a Figma file in your portfolio, consider creating a short five-minute screencast. Narrate the logic behind the screens and discuss key decisions. Place the screencast link near the first screen for immediate accessibility, bringing your project to life.
Understanding and implementing these practices not only elevates your professionalism but also boosts your hiring potential. That’s the rundown!
