Prioritize next file-health reliability objective
Reliability risk often becomes visible before its most useful definition is clear.
Teams may agree that a pattern matters while disagreeing on whether to prevent it or recover from it better.
“This file is where the product lives. I can’t tell when it’s getting risky until it hurts.”
Junko Yang · Principal UX Designer
Owns a multi-quarter product file used by designers, researchers, and engineers across several teams.
What pulls against what
- prevention vs. recovery
- thin evidence vs. meaningful action
- diagnostic detail vs. privacy boundaries
- creative freedom vs. early safeguards
What is at stake
A concentrated cluster of repair events may signal a preventable reliability problem, but the right target is not yet known. The work is to choose a testable outcome rather than simply chase the loudest metric
Why Figma
At Figma, this can matter because complex collaborative work often grows through many small, interacting changes over time.
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.