The human side of a Design System

Video

• A mind-expanding presentation from @braposo that clearly shows why designers should not fear code.
  
  Instead, should embrace the new powers they’d get from acquiring the skills to build out their own designs.
  
  Static design tools only go so far.https://t.co/1ttTnE7HmU

  — Jared Spool (@jmspool) September 29, 2020

• Key takeaways from a great talk by @braposo in the last talk of the day! #DesignSystemsLondon pic.twitter.com/P1FG9Eq6D4

  — Jan Toman 👨‍🎓 @DSLconf (@HonzaTmn) November 15, 2019

• Extended by this one:
  ”Use design systems as an excuse for enabling design for everyone.” @braposo pic.twitter.com/GXJeLsoPh4

  — Jan Toman 👨‍🎓 @DSLconf (@HonzaTmn) November 15, 2019

• By far, @braposo's talk was the most useful one I've seen today at #DesignSystemsLondon

  — Farnood Foroudi (@nudefar) November 15, 2019

• Thank you @braposo super inspiring! #designsystemslondon

  — Stuart Giles (@stuart_giles) November 15, 2019

• Awesome to share a stage with these #designsystems brainiacs - thank you for chatting with me at #DesignSystemsLondon @DSLconf @YLDio @james_hevey @zaggazhao @Mirandagarrido @lily_dart @Jon_Reidy @resource11 @shaunbent @siddharthkp @braposo @UX_musings @freezydorito @anja100 pic.twitter.com/nSg4bf1egE

  — luis eduardo (@luis_klefsjo) November 15, 2019

• @pixelbeat you are a celebrity right now:) thanx to @braposo at @DSLconf pic.twitter.com/Cf6KGWK1oU

  — Sergiy Voronov 🇺🇦 (@mamezito) November 15, 2019

• Aww.. I was hoping the Design Tokens Community Group would get a shout out. https://t.co/Ea7F2lNshU

  — James Nash (@c1rrus) November 15, 2019

• Great talk Bernardo... you covered pretty much all the spectrum of possibilities. Moving into 2020, feeling a little bit optimistic.
  cc @claudioguglieri pic.twitter.com/yP3oEQ3zVf

  — Davo Galavotti (@pixelbeat) November 16, 2019

• Thanks for the shoutout @mamezito + @braposo!
  We need to get the conversation going.@kilianvalkhof mentioned about @avocode sdk and their work with a universal format called Octopus.https://t.co/KJunD7NZ7a https://t.co/OKSANu1SCM

  — Davo Galavotti (@pixelbeat) November 16, 2019

• A lingua franca for Design Systems? pic.twitter.com/SLDi5e2hYV

  — Cristiano Rastelli (@areaweb) November 15, 2019

• honestly, I think about this more than I should 😅 pic.twitter.com/UPf1ZmRx0z

  — Sid @DSLconf (@siddharthkp) November 15, 2019

• *chefs kiss* pic.twitter.com/1wzUeQo2Ns

  — Sid @DSLconf (@siddharthkp) November 15, 2019

• @braposo with an interesting proposal...#DesignSystemsLondon pic.twitter.com/nGzM1NxWW9

  — dhuntrods is @DSLConf 💫 (@dhuntrods) November 15, 2019

• And of course, @markdalgleish gets a mention :) pic.twitter.com/CC1ud5KUFD

  — Cristiano Rastelli (@areaweb) November 15, 2019

• /giphy had us in the first half, not gonna lie pic.twitter.com/zUT9a6bQ9P

  — Sid @DSLconf (@siddharthkp) November 15, 2019

• “This is from Apple HIG that are ~30 years old and we are still struggling integrating accessibility to our design systems.” @braposo #DesignSystemsLondon pic.twitter.com/oq5YclBtTM

  — Jan Toman 👨‍🎓 @DSLconf (@HonzaTmn) November 15, 2019

• Last talk of the day @braposo on the human side of a Design System. #DesignSystemsLondon pic.twitter.com/QP01rU9tr3

  — Cristiano Rastelli (@areaweb) November 15, 2019

• This is getting too real 😱😱😱 Excited and nervous about tomorrow! This is a great bunch of people, had so much fun tonight! https://t.co/FJ83Xv64eE

  — Bernardo Raposo (@braposo) November 14, 2019

• All set for an amazing day @DSLconf!
  
  You can find all the resources from my talk at https://t.co/gaDzUrQZZR
  
  I'll be using this thread to post the updates throughout the day so make sure you follow this if you're interested.
  
  Let's do this! 💪 #DesignSystemsLondon

  — Bernardo Raposo (@braposo) November 15, 2019

• I'm also doing something different this time and (inspired by @swyx) I'm going to prepare this talk out in the open so that anyone can see how are things shaping up leading to the conference. #LearningInPublic
  
  If you're interested, follow this 👉 https://t.co/rQBUVp5poI

  — Bernardo Raposo (@braposo) October 13, 2019

• Haven't had the chance to talk about this yet but... in an incredible turn of events... I'm actually recording this live... at #DesignSystemsLondon!! 😱😱
  
  Very thankful for the opportunity @DSLconf and hope to see you all in November!https://t.co/R1s4Cg9rrr

  — Bernardo Raposo (@braposo) October 13, 2019

• Doing some research for my #DesignSystemsLondon talk, any help is very much appreciated! 🙏
  
  How many parts (documentation, design files, components, prototypes) of your design system are *automatically updated* if you change a primitive/token (let's say the primary colour)?

  — Bernardo Raposo (@braposo) October 20, 2019

• Design systems are 80-90% people stuff, 10-20% design/dev/tools stuff.

  — Brad Frost (@brad_frost) August 16, 2019

• A design system is a language. If people aren't speaking the same language, there will be nothing but confusion. Choosing a new language is a culture shift. Culture doesn't change unless management buys in. Make sure your design system speaks to both technical and non-technical

  — Alex 👨🏻‍💻 (@MetalHaze) August 16, 2019

• 2yrs ago: the design system is the documentation
  
  1yr ago: the design system is our code
  
  Today: a design system is a mirror of all the relationships between designers and managers and engineers

  — Robin Rendle (@robinrendle) March 19, 2019

• A component library isn't a design system.
  
  In order to qualify as a design system, it also needs to have a bunch of documentation nobody reads.

  — Mark Dalgleish (@markdalgleish) October 5, 2019

• New landscape of tools for Component-Driven Development 2019. Interesting that tooling is cross functional + interdisciplinary by default.
  
  Featuring amazing tools by: @storybookjs @figmadesign @framer @invision @chromaui @fbjest ✌️ pic.twitter.com/F5Hl3HqSOT

  — Dominic Nguyen (@domyen) August 3, 2019

• The design system's manual is not the design system.

  — Mark Dalgleish (@markdalgleish) October 12, 2019

• Is the latest design system or a style guide that you've recently built and launched, still up-to-date (and usable) today?

  — Smashing Magazine (@smashingmag) October 7, 2019

• Most of my frontend work at Stripe begins in our internal sketchpad tool, which gives me full access to our design system and offers shareable, fork-able links.
  
  It's a neat way to prototype out features and share it with any Stripe employee. You should build one for your team. pic.twitter.com/1hcQeCdnWf

  — Jordan Scales (@jdan) October 22, 2019

• Designer: How do I use the design system?
  
  Me: You install it from npm.
  
  Designer: pic.twitter.com/bHOkOx9tSz

  — Mark Dalgleish (@markdalgleish) October 22, 2019

• The more advanced our design system gets, the less sense it makes to perform a lossy translation back to static illustration tools.
  
  Yes, we make changes to the code based on input from designers.

  — Mark Dalgleish (@markdalgleish) October 25, 2019

• We're pushing consumers, including designers, to use our Playroom if they want to design with the system: https://t.co/3OOxIdeZXY

  — Mark Dalgleish (@markdalgleish) October 25, 2019

• A design system isn't just a library of assets with some documentation, it's how you collaborate and communicate between teams and disciplines. @natalyathree at #cssday pic.twitter.com/tC1Cn8rMPG

  — Brad Frost (@brad_frost) June 14, 2019

• Before design systems: Drawing whatever you want.
  
  After design systems: Drawing whatever you want—then asking if the design system can do it.

  — Mark Dalgleish (@markdalgleish) October 7, 2019

• When someone spends months building a component library for you but it's missing one tiny little feature. pic.twitter.com/0xewRepCVL

  — Mark Dalgleish (@markdalgleish) October 14, 2019

• design systems are supposed to save us time, but quite quickly they demand more of our time to keep them up to date & thereby useful.

  — Luke Wroblewski (@lukew) March 11, 2019

• It took design tools about 5 years to notice React. I wonder how long it will take them to notice GraphQL.

  — Mark Dalgleish (@markdalgleish) August 26, 2019

• And designers, we are halfway on 2019: can we please make some noise and ask @adobe, @sketch, @figmadesign, @InVisionApp, @framer, @goabstract and the rest of the pack to figure a way to make UNIVERSAL FILE FORMAT for Web Design files?

  — Davo Galavotti (@pixelbeat) June 17, 2019

• Now, what I think is feasible short term, is a “lowest common denominator” format that would allow best effort transfers between design tools. Facebook has their Semaphore format, but it is pretty much internal only. Others, like Abstract or Zeplin could play a role too.

  — Eelco Lempsink (@eelco) June 20, 2019