Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
The designers’ guide
to working with
development

teams
C O L L A B O R A T E O R D I E
Design?
eh???
…for humans
“Design is not just
what it looks like and
feels like. Design is
how it works.”
- Steve Jobs
…for humans
- UX ...
expectation
Design for humans
for humans
Design
DEFINE
IDEATE
PROTOTYPEIMPLEMENT
ANALYZE
ITERATE
Design Process
DEFINE IDEATE PROTOTYPE
Designers deep dive into
the problem

Designers conduct
research and interviews
Developers don’t d...
IMPLEMENT ANALYZE
Designers come to
developers with mockups
Designers and developers
lost so much time and don’t
even get ...
Designer’s ideas may be difficult to
implement on a tight deadline
Designers are unaware of technical
possibilities that c...
Collaborative Design Process
DEFINE
IDEATE
PROTOTYPE
IMPLEMENT
ANALYZE
Invite developers to attend initial
meeting, or at ...
Collaborative Design Process
DEFINE
IDEATE
PROTOTYPE
IMPLEMENT
ANALYZE
Involve all designers and coders who will
be involv...
Collaborative Design Process
DEFINE
IDEATE
PROTOTYPE
IMPLEMENT
ANALYZE
Show the sketches/wireframes to
developers as early...
Collaborative Design Process
Incorporate as realistic content as
possible (avoid Lorem Ipsum)
Consider designing for all v...
Collaborative Design Process
DEFINE
IDEATE
PROTOTYPE
IMPLEMENT
ANALYZE
Delete all unused layers and guides
Render all asse...
Involve developers from start
to finish.
Document and annotate your
designs excessively.
Always create prototypes .
Be rea...
Thanks!

See you later.
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at ...
Prochain SlideShare
Chargement dans…5
×

[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at Axon Active Vietnam

34 vues

Publié le

Collaboration and open communication tend to be categorized as “soft skills” and are often overlooked in organizations. In this session, he is going to discuss how to develop an effective strategy in bridging the gap between product, design, and engineering teams. He will also share some tips for including developers in different stages of design — from planning features to usability testing.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

[DevDay2019] Collaborate or die: The designers’ guide to working with development teams - By Zyrus Deri, Lead Designer at Axon Active Vietnam

  1. 1. The designers’ guide to working with development
 teams C O L L A B O R A T E O R D I E
  2. 2. Design? eh???
  3. 3. …for humans “Design is not just what it looks like and feels like. Design is how it works.” - Steve Jobs …for humans - UX Designers
  4. 4. expectation Design for humans
  5. 5. for humans Design
  6. 6. DEFINE IDEATE PROTOTYPEIMPLEMENT ANALYZE ITERATE Design Process
  7. 7. DEFINE IDEATE PROTOTYPE Designers deep dive into the problem
 Designers conduct research and interviews Developers don’t do anything Designers look for meaningful patterns Designers try to come up with solutions 
 Developers don’t do anything Designers create high- fidelity prototypes Designers get feedback from product. Iterate. Developers don’t do anything Design Process
  8. 8. IMPLEMENT ANALYZE Designers come to developers with mockups Designers and developers lost so much time and don’t even get here. Design Process Developer Developers start to criticize their ideas, asking questions, suggesting new ideas and give feedback to things that will take ages to implement.
  9. 9. Designer’s ideas may be difficult to implement on a tight deadline Designers are unaware of technical possibilities that can make their solution better. Developers feel disengaged because they are just handed the solution and they don’t understand the reasons that brought to it. Stop wasting your time working on a solution that is never gonna be developed,
 and only makes your developers frustrated
  10. 10. Collaborative Design Process DEFINE IDEATE PROTOTYPE IMPLEMENT ANALYZE Invite developers to attend initial meeting, or at least one user interview. Create a bulleted summary of the problem or the insights from research, and share them with developers. Get inputs on technical constraints from developers.
  11. 11. Collaborative Design Process DEFINE IDEATE PROTOTYPE IMPLEMENT ANALYZE Involve all designers and coders who will be involved with the project. Get in a room together, review all research notes, make observations, and turn them into ideas.
  12. 12. Collaborative Design Process DEFINE IDEATE PROTOTYPE IMPLEMENT ANALYZE Show the sketches/wireframes to developers as early as possible Hold regular Design Sparring meetings: https://www.atlassian.com/team- playbook/plays/sparring
  13. 13. Collaborative Design Process Incorporate as realistic content as possible (avoid Lorem Ipsum) Consider designing for all viewports (desktop, tablet, mobile) Prototypes should account for data extremes (short vs long names) Prototypes should account for all interaction states (hover, error, transition) Rename all your layers appropriately Create as many reusable layers as possible Avoid using non-whole px values (0.5) DEFINE IDEATE PROTOTYPE IMPLEMENT ANALYZE
  14. 14. Collaborative Design Process DEFINE IDEATE PROTOTYPE IMPLEMENT ANALYZE Delete all unused layers and guides Render all asset files (fonts, images, icons, svgs) and organize them in subfolders Document and annotate your designs excessively Ensure all documentation stays updated to reflect the final system as it evolves.
  15. 15. Involve developers from start to finish. Document and annotate your designs excessively. Always create prototypes . Be really organized Adapt your processes.
  16. 16. Thanks!
 See you later.

×