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
"I have to triangulate socially because Yorkshire folks are quite reserved; they won't openly admit issues."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Playing politics in UX leadership is about maximizing relationships ethically to advance your agenda, not about being underhanded."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Everything that has been put online, someone like us made and put there; we bake our own biases into it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Transportation must evolve to be more sustainable and accessible for all."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you get a perfect score on your OKRs, it means you didn’t set your sights high enough."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Treat identities as elastic, not as fixed personas, because people’s needs and roles are complex and changing."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Marital status mattered because car buying decisions often involve family members, not just the individual."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Knowledge needs to be thought of as a reusable circular process, not a linear one ending at project completion."
Designing Systems at Scale
November 7, 2018
"Ethics evolve faster than law; just because something is legal doesn’t mean it’s ethical."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
