Identify trustworthy layer-naming value outcome
Messy structure can be either a sign of creative flexibility or a source of repeated navigation cost.
Consistency may help retrieval, while overly visible guidance can make exploratory work feel constrained.
“I can find my own work, but opening someone else’s file is a scavenger hunt.”
Bilal Bitar · Senior Product Designer
Inherits shared files from multiple contributors and spends time locating the right layers before making changes.
What pulls against what
- creative flexibility versus shared findability
- behavioral correlation versus causal need
- broad suggestions versus calibrated abstention
- fast feature delivery versus validated outcome
What is at stake
Naming behavior signals real friction, but not every inconsistency needs correction. The goal is to identify an assistive outcome worth testing without narrowing how teams design
Why Figma
At Figma, file structure often carries both the history of design exploration and the practical needs of collaboration.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.