Distinguish healthy cross-file reuse from sprawl
Visible reuse can signal either disciplined systems work or accumulating dependency debt.
The same collaborative pattern may look healthy from one workflow and costly from another.
“References save us time until nobody knows what’s safe to change.”
Bruna Aguilar · Staff Product Designer
Maintains patterns across several product areas and depends on linked design work staying understandable as teams change.
What pulls against what
- Reusable simplicity vs. workflow truth
- Consistency gains vs. dependency debt
- Fast proxy metrics vs. valid long-term signals
What is at stake
The same reference behavior may represent design-system discipline or hidden maintenance cost. A useful data model must reveal the difference before teams optimize it
Why Figma
At Figma, shared interface work can make the quality of relationships between files as important as activity within them.
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.