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”
efficiency
๏ Design for contribution
and community
๏ Crowd-proof the markup
๏ Fit the workflow
๏ 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/