Connecting production design system code directly to the design editor — one of the key reasons UXPin was acquired.
Founder, CEO & VP of Design
Lack of a single source of truth leads to a suboptimal product development process. Lack of a common language between designers and developers results in suboptimal products.
We researched this through Customer Development interviews, ongoing conversations with the community, and industry analysis.
Build technology enabling connection and synchronization between production design system code and the UXPin design editor. Attract 2,000 companies to the beta program, reach a 90% satisfaction score in beta, and generate $100k in Annual Recurring Revenue by the end of 2019.
I had been developing the underlying concepts since 2017: a model of the software development process where the design system sits between design and development as shared governance, and a linguistic model treating a design system as a private dictionary — syntax, pragmatics and semantics mapping onto design, code and documentation.
Forming and leading the team — 2 to 7 engineers, 1 PM, 1 designer. Teaching the team the Customer Development research method. Helping them build a long-term product strategy. Integrating design systems. And teaching non-coding designers, sales and CS enough React.js to be dangerous.
91% satisfaction rate during the beta program.
$100k in ARR in the first quarter.
One of the key reasons UXPin was acquired in 2020.
Lessons learned
