
Design That Scales
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
After years of building the same interface elements, some designers and developers get wise and try to create reusable, common solutions to help everyone stop reinventing the wheel every time. Most fail. In Design That Scales, design systems expert Dan Mall draws on his extensive experience helping some of the world's most recognizable brands create design practices that are truly sustainable and successful.
"Dan's book is a game?changer for our approach to design systems, leading to significant changes at my company, making it a must?read for streamlining anyone's complex design systems!" ?Nadine Sarraj, Product Designer, 365 Retail Markets"A lively and paradigm-challenging evaluation of what makes good system designs work at any scale."?Kirkus Reviews Who Should Read This Book?People who are building and maintaining design systems, large or small. Designers, engineers, and product managers who are in search of a more efficient way to work. Leaders and executives who want to effect change but aren't sure how to do it. People who have designed web forms and tables, but don't know what's next.Takeaways- A design system is crucial for any organization managing two or more digital products. Learn how to create, manage, and sustain a successful design system.
- See how the ecosystem of a design system works in order to understand the context for success.
- Figure out where the people involved in a design system fit and how they can best collaborate.
- Learn the metrics for success within a design system and how to measure them.
- Determine the best techniques for marketing your design system to stakeholders.
- Learn what guidance and relationships are crucial for a design system to succeed.
- See the end-of-chapter questions that highlight how to guide your design system to a profitable outcome.
More details
Person
Content
- Intro
- Title Page
- Copyright
- Dedication
- How to Use This Book
- Who Should Read This Book?
- Frequently Asked Questions
- Contents
- Foreword
- Introduction
- Chapter 1: Why Design Systems?
- Systems Connect Organizations
- Common Benefits of Design Systems
- Who Are Design Systems For?
- Questions for Reflection
- Chapter 2: Design System Fundamentals
- Word Nerds Unite!
- Different Kinds of Design Systems
- Choose Your Own Design System Adventure
- Questions for Reflection
- Chapter 3: The Parts of a Design System Product
- The Most Common Parts of a Design System
- The Sum of Its Parts
- Design Systems Are About Connectedness
- Component Libraries vs. Design Systems
- Connect the Entire Digital Ecosystem
- Questions for Reflection
- Chapter 4: The Broken Business of "Buy-In"
- "Make System, Use System" Is a Fantasy
- Getting Design System Buy-in Is Often Pitching Vaporware
- Abstract Design Systems Are Difficult to Make
- Good Luck Convincing Someone to Adopt a New Tool
- Product Teams Don't Contribute to Design Systems
- Questions for Reflection
- Chapter 5: Pilots-The Best Way to Start and Sustain a Design System
- Linking Design System to Product Work
- A Design System Pilot Scorecard
- Types of Design System Pilots
- Multiple, Concurrent Pilots
- Improving the System as You Use It
- The Piloting Process
- Extracting and Abstracting
- Questions for Reflection
- Chapter 6: Governance and Contribution
- The WordPress Ecosystem as It Relates to Design Systems
- A Framework for Design System Governance
- A Design System Governance and Contribution Template
- Design System as Canon and the Expanded Universe
- Questions for Reflection
- Chapter 7: Roles and Responsibilities
- Front-end Engineering Is More Important Than Visual Design
- Front-end Engineering Is More Important Than Back-end Engineering
- Front-end Engineering: The Missing Skill Set
- Rebranding the "Front-end Engineer"
- Psychological Safety
- Ecosystem Engineers
- Three-legged Stools
- Other Roles on a Design System Team
- Design System Annual Budgeting
- Questions for Reflection
- Chapter 8: Process and Workflow for Design Systems
- Frameworks over Processes
- Less Is More
- The Hot Potato Process
- A Change in Tools Needs a Change in Behavior
- Hot Potato Gotchas
- Resistance to New Workflow
- Questions for Reflection
- Chapter 9: Success Metrics for a Design System
- Identifying Custom Success Metrics
- A Framework to Measure Success
- People Succeed, Not Systems
- Align Goals to Connect an Organization
- Questions for Reflection
- Chapter 10: Evangelism Never Stops
- Lay Out Your Design System like a Store
- Make Your Design System About Its Users
- Questions for Reflection
- Conclusion
- Index
- Acknowledgments
- About the Author
- Back Cover
System requirements
File format: ePUB
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use a reading software that can process the file format ePUB: e.g., Adobe Digital Editions or FBReader – both free (see eBook Help).
- Tablet/Smartphone (Android; iOS): Before downloading, install the free app Adobe Digital Editions (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePUB works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.