Downloaded 74 times
![]](https://image.slidesharecdn.com/smashingconf-lets-work-together-170623140647/85/Let-s-Work-Together-101-320.jpg)
Uploaded byBrad Frost
Let's Work Together!
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.
More Related Content
Let's Work Together!
- 1.
- 4. OUR WORK ISDONE WITH OTHER PEOPLE FOR OTHER PEOPLE
- 5.
- 6. HOW DO WEWORK WITH EACH OTHER?
- 7. HOW DO WETALK TO EACH OTHER?
- 8. HOW DO WECOORDINATE WITH EACH OTHER?
- 9. HOW DO WECOLLABORATE WITH EACH OTHER?
- 10. SPACES VS TABSSKETCH 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
- 13. complete chaos stiflingrigidity
- 15.
- 16.
- 17.
- 18.
- 19.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26. ZAPPOS 10 COREVALUES ๏ 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
- 27.
- 28. –Chris Edmonds An organizationalconstitution 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/
- 29.
- 30.
- 31.
- 32.
- 33. principles & guidelines management publicrelations research digital social creative services analysis cmo vp assistants
- 34.
- 35.
- 45.
- 46.
- 49.
- 50. team 1 team 2 team3 team 4 team 5 team 7 team 6 team 9 team 10 team 8
- 51. team 1 team 2 team3 team 4 team 5 team 7 team 6 team 9 team 10 team 8
- 52.
- 53. team 1 team 2 team3 team 4 team 5 team 7 team 6 team 9 team 10 team 8
- 54. principles & guidelines team1 team 2 team 3 team 4 team 5 team 7 team 6 team 9 team 10 team 8
- 55.
- 56.
- 57.
- 58.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 80. code block .thisishowwedoit { } CSSSYNTAX GUIDELINES
- 81. code block .this-is-how-we-do-it { } CSSSYNTAX GUIDELINES
- 82. code block .thisIsHowWeDoIt { } CSSSYNTAX GUIDELINES
- 83. code block .this__is__how__we__do—-it { } CSSSYNTAX GUIDELINES
- 84. code block .- -...-- ..- - —— .. . ..—— — { } CSS SYNTAX GUIDELINES
- 85.
- 86.
- 87. BENEFITS OF DESIGNSYSTEMS ๏ 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
- 88. MAKING DESIGN SYSTEMSHAPPEN
- 89. RESEARCH & USERINTERVIEWS
- 90. "You can probablycarbon date our UIs based on the design."
- 91. "The main challengesare 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 lotof 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 basicexpand/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 ๏ Roundup 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
- 95.
- 96.
- 101.
- 102. PRIORITIES WORKSHOP ๏ Discussemerging 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
- 103. REGROUP & NEXTSTEPS
- 105. REGROUP & NEXTSTEPS ๏ 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.
- 106.
- 107. –Luke Wroblewski Design principlesare 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
- 108.
- 109. DESIGN SYSTEM PROCESSPRINCIPLES ๏ 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 PRODUCTPRINCIPLES ๏ Just enough interface ๏ Strong and direct ๏ Speed is a feature ๏ Adaptable density ๏ Safety always ๏ No tricks or stunts ๏ Recycle, reduce, reuse
- 112. 6 COUNTER-INTUITIVE TESTSFOR 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/
- 113. DESIGN PRINCIPLES UNDERPINEVERY BUSINESS, DESIGN, & DEV DECISION
- 114.
- 115.
- 116.
- 117.
- 118.
- 119.
- 120.
- 121.
- 122. WHAT ARE SOMEGENERAL PRINCIPLES YOUR TEAM SHOULD FOLLOW WHEN WRITING HTML?
- 123.
- 124. SMACSS, BEM OROTHER METHODOLOGY?
- 125. WHAT TOOLS (SASS,NORMALIZE, AUTOPREFIXER, ETC) DOES YOUR TEAM RELY ON TO WRITE CSS?
- 126. WHAT JS TOOLS(JQUERY, REACT, ANGULAR, POLYFILLS, DEPENDENCIES) DOES YOUR TEAM RELY ON?
- 127. THE WORKSHOP ANDTHE STOREFRONT
- 135.
- 136.
- 148. Pattern Lab Grunt/Gulpcopy task Style Guide
- 149.
- 154.
- 155.
- 157.
- 159.
- 160.
- 161. native appscommunications intranetmarketingsite product
- 162. native appscommunications intranetmarketingsite product design tokens
- 163. native appscommunications intranetmarketingsite product design tokens implementation-agnostic source of truth
- 164. DESIGN TOKEN PROPERTIES ๏Background colors ๏ Type colors ๏ Font families ๏ Font sizes ๏ Font weights ๏ Line Heights ๏ Border colors ๏ Border thicknesses ๏ Border radii ๏ Animation speeds ๏ Media queries ๏ Margins ๏ Padding
- 165.
- 166.
- 175.
- 180. THERE IS NOSUBSTITUTE FOR HUMAN COMMUNICATION AND COLLABORATION
- 188.
- 189. whiteboard sketch working product thattool you've spent 7 years mastering
- 190.
- 191. COLLABORATION AND COMMUNICATION BEATDELIVERABLES
- 192. complete chaos stiflingrigidity
- 193.
- 194.
- 195.
- 196.