No items found.
Achieve IT success
together with Tokyo Techies
We've launched Kotae: The Chat Bot for Small Businesses! Check it out here!
See DetailsAn effective design workflow is crucial for productivity and collaboration, especially within dynamic development environments. As a design team of two, we recently identified a need to restructure our Figma environment and file structure. Our existing system, while initially functional, began to impede our efficiency as our project continued to grow.
This article outlines our transition from a chronologically-driven file organization to a screen-centric model, a strategic shift that has yielded significant improvements in iteration speed, approval processes, and overall clarity for our developers.
Our original method for organizing Figma files involved creating pages named after development sprints—for example, "Sprint 33" or "Sprint 34." While this seemed a logical starting point, its limitations quickly became apparent. The sprint-based nomenclature was arbitrary, making the retrieval of specific screen iterations from previous cycles a cumbersome task. Furthermore, individual sprint pages often evolved into sprawling repositories containing a diverse set of screens from various parts of our platform, alongside numerous iterations of unrelated design elements.
This lack of a granular and intuitive structure led to several operational inefficiencies. Onboarding new designers was difficult, and developers frequently faced difficulties in locating specific designs pertinent to their current tasks. For product managers and designers, the review process was complicated by the scattered nature of designs. Most critically, a clear, sequential history of iterations for individual screens was absent; design evolution was fragmented across disparate Figma pages, hindering our ability to track decision-making or efficiently access prior versions.
To address these fundamental challenges, we implemented a new organizational paradigm within Figma, shifting the focus from the timeline of development (sprints) to the core components of our product (screens and features). This screen-centric methodology comprises several key elements:
The adoption of this screen-centric organization has demonstrably enhanced our design and development operations. A primary benefit is the establishment of a transparent and readily accessible version history for every screen. The dedicated "→ Iterations" page for each screen now functions as a clear, chronological record, simplifying the review of past design choices or the comparison of different versions.
Navigation within our Figma workspace has become significantly more intuitive for all team members. Designers can swiftly locate the precise screen required for their tasks, while developers seeking specifications or assets for a particular feature have a clear path to the necessary information. This has markedly reduced ambiguity and the time previously consumed by searching for design elements.
The overall Figma environment is now more logically structured, promoting a clear top-down understanding from main screens to their iterative developments. This enhanced organization reduces cognitive load, allowing designers to concentrate more effectively on their core responsibilities. The handoff process to developers has also been notably streamlined. Instead of navigating extensive, multi-faceted sprint pages, developers receive direct links to the specific section within an iterations page that contains only the screen relevant to their work. This focused presentation also makes design reviews more efficient for Product Managers and lead designers.
Furthermore, the structure of the iterations pages naturally facilitates the presentation of "Before and After" states, providing essential context for developers and improving their comprehension of the required changes. This clear framework supports faster design iterations, as previous versions are easily accessible for reference and comparison. The improved clarity and ease of understanding for all stakeholders foster more efficient feedback loops, contributing directly to quicker approval cycles.
For our team—a compact design unit within a growing company—this refined Figma structure has proven to be a valuable strategic asset. It underscores the principle that thoughtful organization, leveraging the native capabilities of contemporary design tools, can yield substantial improvements in workflow efficiency and cross-functional collaboration, irrespective of team size. This transition has not only brought order and clarity to our design files but has also empowered our development partners and, ultimately, enabled us to dedicate more time and energy to innovative design solutions rather than administrative overhead. We believe that a screen-centric organizational model offers a robust framework for other teams seeking to optimize their design operations.
