Correct duplicate token-insertion event counts
Shared metrics often become unreliable before the workflow itself visibly changes.
Fast instrumentation changes can improve coverage while quietly creating conflicting counts.
“I can’t tell whether the library is growing or the dashboard is just louder.”
Eka Htwe · Design Systems Lead
Owns a shared library used by several product squads and relies on adoption reporting to prioritize maintenance.
What pulls against what
- Fast dashboard repair vs. durable source correction
- Retry preservation vs. duplicate suppression
- Historical continuity vs. accurate restatement
What is at stake
Teams are using token-adoption data to guide library investment. Accurate counts restore confidence in where reuse is actually happening
Why Figma
At Figma, trusted design-system signals often shape how teams understand reusable interface work.
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.