Validate repeat sharing for interface artifacts
A growing behavior can signal momentum without revealing the outcome people are actually pursuing.
Adjacent use cases often look similar in telemetry while asking for different product commitments.
“I’m rebuilding the same story in three places just so different people can follow it.”
Philippe Campbell · Staff Product Designer
Reuses interface work to align product, engineering, and leadership on changing product direction.
What pulls against what
- Growing behavior vs. unclear customer value
- Polished artifacts vs. preserved context
- Visible integration vs. validated outcome
What is at stake
Export behavior is growing, but the desired customer result is unclear. A well-framed learning bet can prevent a costly commitment to the wrong adjacent workflow
Why Figma
At Figma, shared design context often extends into planning, communication, and decisions in ways that are not immediately visible in usage data.
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.