Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
Having a design system is a de facto necessity when building cohesive enterprise software. The challenge is how does it all come together with a single location, a source of truth, a website? How does a cross-functional team marshal the resources with political and technical willpower to achieve this goal? It’s no easy feat as Jennie Yip, Atlassian design systems lead, explains in this Medium essay. This fireside chat will dig deeper into the problems addressed and lessons learned, with Jennie and also Charles Lee, the engineering lead. Hearing their stories will inspire and inform all of us in our design system journeys. We hope you will join us!
Key Insights
-
•
Inconsistencies between design specs, Figma, Sketch, and code caused user confusion and mistrust of documentation.
-
•
Atlassian’s Constellation project aims to create a single source of truth unifying designer and developer documentation.
-
•
Live code examples embedded in documentation replace static images, ensuring up-to-date and interactive component previews.
-
•
Collaboration and early involvement between designers and engineers are critical to successful design system evolution.
-
•
The project spanned multiple years and team changes, requiring extensive documentation and ‘run books’ for onboarding.
-
•
Governance is framed as shared execution rather than policing, fostering buy-in instead of compliance tension.
-
•
Design tokens improve handoff accuracy, although integration with Figma is still partly manual and evolving.
-
•
Multiple local design systems coexist alongside the central system, typically as downstream consumers of core components.
-
•
Roadmap alignment between platform teams and product teams remains one of the biggest operational challenges.
-
•
Extensive user research including usability tests and tree card sorts informed navigation, IA, and content strategy.
Notable Quotes
"Kate considers live code to be the source of truth because she can’t trust the design site due to inconsistencies."
"If engineers don’t like what we’re doing, they absolutely will not adopt our design system."
"Governance shouldn’t be policing; we’re here to help create the best experience and save time."
"This project has a lot of history and required synthesizing findings from many people over years."
"Design systems reflect organizational structure – if designers and engineers are siloed, no tooling will fix that."
"Updating and adopting design system components requires company time and planning—for some teams, fast release cycles were too frequent to keep up."
"Docs as code is a philosophy that keeps documentation in workflows familiar to content designers and engineers alike."
"Prior prototypes and documentation of pain points helped pave the way and garner stakeholder buy-in for Constellation."
"We use MDX and markdown so designers can edit documentation directly through pull requests."
"Empathy on both sides is key—engineers need scoped work, designers need to understand engineering constraints."
Or choose a question:
More Videos
"Organizations don’t always need external training; they can facilitate internal learning and mentorship."
Shaping design, designers and teams
November 8, 2018
"The purpose of a design operating model is to place the customer at the centre of everything the whole organisation does."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"The later you consider accessibility, the more complicated and costly the solutions become."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"You can’t just throw another tool at accessibility problems; training and culture are just as important."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility (Videoconference)
May 26, 2022
"Michael became our farmer maintaining a steady flow of the team; Dana was our gardener cultivating quality work."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"You need strong regional players with negotiation skills to navigate the split loyalties in global teams."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"There’s a lot of tools that can do everything, but they can’t do one thing really, really well."
Operationalizing DesignOps
November 7, 2018
"You cannot be emotionally attached to whether or not anyone implements your advice — it’s out of your control once given."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"The most important value delivered to customers is always the qualitative value—the emotional and experiential impact."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020