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.
Building a New Home for the Atlassian Design System
Summary
Key Insights
-
•
Multiple sources of truth in design systems cause inconsistencies and confusion, as seen with the button component font weight differences across specs, design files, and code.
-
•
Design systems should treat code as the source of truth while making design tools like Figma an integrated extension of that truth.
-
•
The Constellation project aims to create a single, consistent destination for design and development documentation, consolidating 50+ guidelines and 27 out of 60 components.
-
•
Collaboration between designers and engineers early in the process is critical to align priorities, avoid scope creep, and build trust.
-
•
Governance in design systems works best as shared execution through community trust and enabling teams, rather than policing or harsh compliance enforcement.
-
•
Workshops and detailed documentation are essential for onboarding new team members quickly and preserving knowledge amid team changes.
-
•
Live code examples embedded in documentation reduce maintenance burdens and ensure consumers always see current component behavior.
-
•
Versioning pace needs balancing—too frequent releases burden product teams trying to keep up and can hinder adoption.
-
•
Research methods like card sorting and usability testing directly influence information architecture and navigation improvements in the new documentation.
-
•
Buy-in from leadership and stakeholders grew through repeated demos and a unified team vision, highlighting the value and reducing skepticism over time.
Notable Quotes
"We kept feeling the same consistent pain around some truths for our design system."
"Kate said she considers live code to be the source of truth because she can't trust the design site due to inconsistencies."
"Code is definitely considered the source of truth; we're working hard to make Figma an extension of that."
"Governance is not policing; we're here to help you create the best experience and save time."
"Workshops often reveal gaps in documentation, which is a spicy take but true."
"It's really about finding a way to link all the different aspects to bring everything together to tell the story."
"Continuous adaptation is key; you're adapting to the system as much as adopting it."
"If you can't get buy-in for collaboration between engineers and designers, start from the bottom and talk more early and often."
"Updating and adopting design system components is company time, so a slower release schedule helps teams keep up."
"We absolutely need feedback loops so engineers and designers can influence the design system and keep it relevant."
Or choose a question:
More Videos
"An elite athlete doesn’t turn up at the Olympics and do their thing without coaches, physios, nutritionists."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Show them, don’t tell them — involving stakeholders early builds skin in the game and helps control quality."
Amy MarquezINVEST: Discussion
June 15, 2018
"The weakest insight method might win simply because of the relationship to the power structure."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"We covered critical design gaps without waiting for headcount allocation or hiring delays."
Alicia MootyDesign Staffing Models
September 30, 2021
"We may not have tech prowess but our sticky notes, card sorts, and test reports are our real superpowers."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Simply asking stakeholders what success looks like for them in a project is a powerful way to start meaningful conversations."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"The legacy of folders and nested structures causes real problems in finding research and scaling repositories."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Innovation is very much a team sport."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Embedded squads build domain expertise but risk losing knowledge if someone leaves, while centralized teams help reduce duplicated effort."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
