Abstract
With the rise of design-led organizations, the role of the designer has shifted from that of mere stylist to that of a business’s number-one problem solver. Yet, to build products that people love, designers must do more than solely solve problems. They must structure the way they work, establishing the guiding rules and principles that support and drive both their design process and the product for which they are designing.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Rune Madsen, “A History of Design Systems,” http://printingcode.runemadsen.com/lecture-intro/.
- 2.
Bert Bos, “A Brief History of CSS Until 2016,” https://www.w3.org/Style/CSS20/history.html, December 17, 2016.
- 3.
DRY stands for “Don’t Repeat Yourself” and is a term used in software engineering. The aim is to reduce repetition and avoid redundancy.
- 4.
U.S. Department of Labor, Bureau of Labor Statistics, “Issues in Labor Statistics,” https://www.bls.gov/opub/btn/archive/computer-ownership-up-sharply-in-the-1990s.pdf, March 1999.
- 5.
Kent Beck et al., “Manifesto for Agile Software Development,” https://agilemanifesto.org/, 2001.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Sarrah Vesselov and Taurie Davis
About this chapter
Cite this chapter
Vesselov, S., Davis, T. (2019). The Rise of Design Systems. In: Building Design Systems. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4514-9_1
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4514-9_1
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4513-2
Online ISBN: 978-1-4842-4514-9
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books