A presentation at Patterns Day in in Brighton, UK by Inayaili León
5 things that aren’t true about design systems @yaili Patterns Day, Brighton, June 2019
Photo by Rick Mason on Unsplash
Photo by mlhradio on Flickr
Photo by Milivoj Kuhar on Unsplash
Untruth #1 “Everyone loves and understands our work.”
Untruth #1 “Everyone loves and understands our work.” “Some people hate us, and many don’t know what we’re trying to do.”
#1 “Everyone loves and understands our work.” “Material?”
#1 “Everyone loves and understands our work.” Photo by You X Ventures on Unsplash
#1 “Everyone loves and understands our work.” Photo by You X Ventures on Unsplash
Untruth #2 “Our documentation is always up to date.”
Untruth #2 “Our documentation is always up to date.” “We don’t always have time to document things.”
#2 “Our documentation is always up to date.” Photo by Ben White on Unsplash
#2 “Our documentation is always up to date.” Buster Keaton in “The General”, 1926. GIF from r/silentmoviegifs
#2 “Our documentation is always up to date.” Photo by Filip Bunkens on Unsplash
#2 “Our documentation is always up to date.” Usage Do • Keep the content of a card related to a • • • • • Example Usage Anatomy Developer guidance API single concept • Keep content inside cards aligned, even in cases where dividers extend to the edge of the card • Avoid scrolling inside cards; rely on scrolling of the parent container instead • Avoid placing a card on a background lighter than $neutral-2 Don’t N E M I C E P S • Place cards within cards • Include many calls to action within a single card • Use card to replace similar components, such as dialog
Untruth #3 “Everyone works together in harmony.”
Untruth #3 “Everyone works together in harmony.” “We block each other all the time.”
#3 “Everyone works together in harmony.”
#3 “Everyone works together in harmony.” Photo by Luke Brugger on Unsplash
Untruth #4 “No one ever needs custom components.”
Untruth #4 “No one ever needs custom components.” “Someone needs a custom component every day.”
#4 “No one ever needs custom components.” Photo by Brendan Church on Unsplash
#4 “No one ever needs custom components.” Seinfeld, “The Soup Nazi”, 1995
#4 “No one ever needs custom components.” Photo by Vidar Nordli-Mathisen on Unsplash
#4 “No one ever needs custom components.” Photo by DorkyMum on Flickr
Untruth #5 “We validate everything.”
Untruth #5 “We validate everything.” “Most times we push to the system without testing.”
#5 “We validate everything.” Photo by Kai Pilger on Unsplash
#5 “We validate everything.” Photo by Annie Spratt on Unsplash
#5 “We validate everything.” Photo by Annie Spratt on Unsplash
#5 “We validate everything.” Photo by Mimi Thian on Unsplash
(I’m nearly done!)
Thank you! @yaili, references bit.ly/patternsday
The following resources were mentioned during the presentation or are useful additional information.
Here’s what was said about this presentation on social media.
Enjoyed @yaili ‘s - 5 things that aren’t true about design systems - There’s not enough time to do everything. It doesn’t have to be just the Design System team. “Entrust others or become a blocker” #PatternsDay #InteractionDesign pic.twitter.com/MkihppNgGQ
— Richard Flick (@richardflick) June 28, 2019
Solidarity from @yaili - you’re not alone in having a broken incomplete or difficult system. She’s about to share 5 untruths about #designsystems
— Clearleft (@clearleft) June 28, 2019
Untruth #1 everyone loves and understands our work #patternsday pic.twitter.com/4L9KJPt8XU
Such a relatable talk by @yaili on the myths and truths that come with building and maintaining a design system #patternsday pic.twitter.com/1NfGgQvCNs
— Vincent Navetat (@vincentnavetat) June 28, 2019
#PatternsDay @craftui @yaili giving away great tips on your way to making a design system! pic.twitter.com/GwkHRzoPU0
— Nasia Makrygianni (@nasiamakryg) June 28, 2019
The first 2 talks at #PatternsDay (by @craftui and @yaili) were really great - pragmatic, honest and full of good advice. Feels like the field is maturing. Up next, @Amy_Hupe 👏👏
— Tim Paul (@timpaul) June 28, 2019
Beautiful design systems for teams are the same as Instagram is for life. @yaili telling the truth at #patternsday
— Joke de Winter (@jokedewinter) June 28, 2019
@yaili thanks for the un-truths, learning to say "no" is probably the hardest skill to learn #patternsday pic.twitter.com/eNY2rhLNKn
— Patrick🤦♂️Laubner (@superfine_de) June 28, 2019
“Beautiful design systems are for teams what Instagram is for life — it’s a facade. You’re not alone in having an imperfect system.” @yaili
— Anwen Williams (@hello_anwen) June 28, 2019
Reassuring honesty at #PatternsDay! 👏 pic.twitter.com/v6YoQgRNT6
“Beautiful design systems are for teams like Instagram is for life - it’s a facade” a refreshing and forgiving take on the pressures design systems place on us by @yaili #PatternsDay
— Giles Airey (@Giles_Airey) June 28, 2019
Nice heads up talk by @yaili. It’s comforting to see that we all are struggling and solving similar issues and face the same challenges. Thanks! #patternsday
— Jan Toman (@HonzaTmn) June 28, 2019
“Feature teams will inherently push the boundaries of a design system and design systems teams will inherently push back against some of these changes. That’s normal! Be prepared to have awkward conversations; they help your design system grow.” @yaili #PatternsDay pic.twitter.com/McszQ7QQuI
— Frederic Marx (@fredericmarx) June 28, 2019
“If every single request and change is accepted by the system, it will lead to mess. It makes system complicated, hard to use and maintain, unstable and with a lot of breaking changes.” @yaili #patternsday
— Jan Toman (@HonzaTmn) June 28, 2019
“Someone needs a custom component every day.” - @yaili #PatternsDay pic.twitter.com/sxmWULLvxd
— Andy Bell (@andybelldesign) June 28, 2019
Design systems shouldn't block feature work, creating standards takes time, says @yaili. (I agree and recommend having a process defined for evaulating the feature work.) #PatternsDay
— Kimberly Blessing (@obiwankimberly) June 28, 2019
Great idea for documentation outlines from @yaili #patternsday pic.twitter.com/w7j9Cesbau
— Matt Chapman (@Chapabu) June 28, 2019
“Any new component is adding to a complexity of the whole system. Defining standards isn’t something you can rush.” @yaili #PatternsDay
— Jan Toman (@HonzaTmn) June 28, 2019
“No design system is perfect. There will always be things that are messy or inconsistent or undocumented, and that’s okay.” @yaili #PatternsDay pic.twitter.com/U1jpsp4sIT
— Frederic Marx (@fredericmarx) June 28, 2019
Don’t assume your stakeholders understand the potential for design systems. Take them from “Why are we doing this?” To “When can I have it and what can I do to help?” #patternsday @yaili pic.twitter.com/2QwN5fEj8g
— Luke (@lukedarbs) June 28, 2019
“Design systems are for design teams what Instagram is for life — a facade” @yaili at #PatternsDay
— Paul Davison (@actino) June 28, 2019
Design systems are for teams what Instagram is to life /@yaili #patternsday
— David Roessli (@roessli) June 28, 2019
Ooh, intriguing. @yaili says "beautiful design systems for teams are like Instagram is an accurate representation of life." It's not unusual to have a broken, messy, imperfect design system / process. TRUTH! #PatternsDay
— Kimberly Blessing (@obiwankimberly) June 28, 2019
“Beatiful design systems are for teams the same as Instagram is for life.” 😅 Just perfect quote by @yaili #patternsday
— Jan Toman (@HonzaTmn) June 28, 2019