This document discusses the importance of collaboration, communication, and establishing principles and guidelines when working in teams. It addresses challenges like differing approaches, technologies, and opinions that can arise. The document suggests researching user needs, establishing shared values and priorities, and creating design systems to promote consistency. Overall, it advocates for establishing processes and tools to facilitate interdisciplinary cooperation and coordination across organizations.
10. SPACES VS TABS SKETCH VS PHOTOSHOP GIF VS GIF
GRUNT VS GULP NPM VS YARN
FILE STRUCTURE
BEM VS SMACSS
FLAT VS SKEUOMORPHIC
AZURE VS INDESIGN REACT VS VUE
PROGRESSIVE ENHANCEMENT VS SINGLE PAGE APPS
ANGULAR VS EMBER
NATIVE VS WEB
SVG VS ICON FONTS
WORDPRESS VS DRUPAL
PHP VS RUBY VS NODE VS PYTHON
SASS VS LESS
26. ZAPPOS 10 CORE VALUES
เน Deliver WOW Through Service
เน Embrace and Drive Change
เน Create Fun and A Little Weirdness
เน Be Adventurous, Creative, and
Open-Minded
เน Pursue Growth and Learning
เน Build Open and Honest
Relationships With Communication
เน Build a Positive Team and โจ
Family Spirit
เน Do More With Less
เน Be Passionate and Determined
เน Be Humble
https://www.zapposinsights.com/about/core-values
28. โChris Edmonds
An organizational constitution specifies your teamโs
purpose, values and behaviors, strategies, and goals. โจ
It creates โliberating rulesโ that help leaders and
team members understand exactly how they are
expected to treat each other and their customers.
http://thecultureengine.com/
87. BENEFITS OF DESIGN SYSTEMS
เน Promotes UI consistency & cohesion = more conversions & $$$$$
เน Faster production = roll out more features & iterations faster than ever
เน Shared vocabulary = more time collaborating & less time in meetings
เน Easier to test = more responsive, performant, and accessible experiences
เน Useful reference = an essential resource and hub for best practices
เน Future-friendly foundation = modify, extend, & improve upon over time
91. "The main challenges are the existing thousands of
lines of code, acquisitions, and existing suite of
technologies that makes up a billion dollars a year.
We'd like to not lose that billion dollars."
92. "There's a lot of institutional knowledge here locked up
in people's heads. Slack channels are great, but it
becomes a scavenger hunt to find information about
how something's supposed to work."
93. "For a basic expand/collapse pattern, the devs spent 2
days going to different teams to find the code, then still
had to rebuild it themselves."
94. USER INTERVIEWS
เน Round up a diverse group of stakeholders,users,and other
people who would impact/be impacted by a design system
เน Talk about current workflow,pain points,hopes,fears,
dreams,frustrations,and other things that can influence
the success of the design project
เน Latch onto poignant quotes and emerging themes
เน Start shaping the story and key themes in preparation โจ
for kickoff
102. PRIORITIES WORKSHOP
เน Discuss emerging themes from interviews and introduce
potential principles and tactics
เน Give each person 5 votes for principles they care most about
เน Discuss principles.What won?What lost?Why?
เน Give each person 5 votes for tactics/features they care most
about.
เน Goal is to align around a set of shared principles and priorities
for the design system
105. REGROUP & NEXT STEPS
เน Recap the day's events; talk about the outcomes
เน Make sure to cover any lingering questions,concerns,and
other words of wisdom that will help the design system be
successful
เน Explain what happens next and how they can stay involved
with the design system process
เน Pizza party.
107. โLuke Wroblewski
Design principles are the guiding light for any software
application. They articulate the fundamental goals that all
decisions can be measured against and thereby keep the
pieces of a project moving toward an integrated whole.
https://www.lukew.com/ff/entry.asp?854
109. DESIGN SYSTEM PROCESS PRINCIPLES
เน Make the best thing the โจ
easiest thing
เน Design for โgrab it quickโ
ef๏ฌciency
เน Design for contribution โจ
and community
เน Crowd-proof the markup
เน Fit the work๏ฌow
เน Just enough documentation
เน Technology agnostic
เน Embed the brand in the code
เน Consistent, not homogenous
เน Opinionated defaults
เน Make people smarter just โจ
by using it
110. DESIGN SYSTEM PRODUCT PRINCIPLES
เน Just enough interface
เน Strong and direct
เน Speed is a feature
เน Adaptable density
เน Safety always
เน No tricks or stunts
เน Recycle, reduce, reuse
111.
112. 6 COUNTER-INTUITIVE TESTS FOR CREATING DESIGN PRINCIPLES
เน Does it come directly from research?
เน Does it help you say โNoโ most of the time?
เน Does it distinguish your design from your competitors?
เน Is it something you might reverse in a future release?
เน Have you evaluated it for this project?
เน Is its meaning constantly tested?
https://articles.uie.com/creating-design-principles/