Prioritize public contribution among design-system practitioners
High participation can mean several different kinds of value, not one obvious community outcome.
Visible contribution, quiet learning, and peer recognition can each point toward different choices.
“I don’t need another place to post updates—I need to know which peers have already solved the messy parts.”
Alvaro Alvarez · Design Systems Lead
She maintains shared interface foundations across several product teams and reads community discussions for practical patterns.
What pulls against what
- visible contribution vs. quiet learning
- speed of definition vs. quality of evidence
- external benchmarks vs. local member reality
- expert recognition vs. practical usefulness
What is at stake
A growing expert cohort is valuable, but its needs are not yet clear. The wrong success metric could reward activity without creating useful peer learning
Why Figma
At Figma, design-system practice often spans teams and benefits from community spaces that reveal how practitioners actually learn from one another.
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.