Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Iterative Design

Iterative Design

In this presentation I went through how engineers can better utilize their designers in an iterative process.

Garth Braithwaite

April 15, 2012
Tweet

More Decks by Garth Braithwaite

Other Decks in Design

Transcript

  1. • Designing as a product progresses • Designing in sprints

    • Changing design as needs change Iterative Design Wednesday, July 11, 12
  2. What it isn't • Going dark • Design perfectionism •

    Icing on the poo cake Wednesday, July 11, 12
  3. What it isn't • Going dark • Design perfectionism •

    Icing on the poo cake • Weasley House Wednesday, July 11, 12
  4. Causes • Designers failing to understand technical ramifications • Developers

    failing to understand design • Too many assumptions, not enough passion Wednesday, July 11, 12
  5. Causes • Designers failing to understand technical ramifications • Developers

    failing to understand design • Too many assumptions, not enough passion • Lack of communication Wednesday, July 11, 12
  6. Causes • Designers failing to understand technical ramifications • Developers

    failing to understand design • Too many assumptions, not enough passion • Lack of communication Wednesday, July 11, 12
  7. How to care for your designer Table of Contents 1.Picking

    your designer Wednesday, July 11, 12
  8. How to care for your designer Table of Contents 1.Picking

    your designer 2.Understanding design Wednesday, July 11, 12
  9. How to care for your designer Table of Contents 1.Picking

    your designer 2.Understanding design 3.Communication Wednesday, July 11, 12
  10. How to care for your designer Table of Contents 1.Picking

    your designer 2.Understanding design 3.Communication 4.Forging a relationship Wednesday, July 11, 12
  11. Picking your designer • Engineers need to be in the

    interviewing process Wednesday, July 11, 12
  12. Picking your designer • Engineers need to be in the

    interviewing process • Designers need to be able to code Wednesday, July 11, 12
  13. Picking your designer • Engineers need to be in the

    interviewing process • Designers need to be able to code • Pick a designer you can respect Wednesday, July 11, 12
  14. Picking your designer • Engineers need to be in the

    interviewing process • Designers need to be able to code • Pick a designer you can respect • Don't be a dick Wednesday, July 11, 12
  15. Understanding design • Design != pretty pictures • Design is

    a process • Design is objective Wednesday, July 11, 12
  16. Understanding design • Design != pretty pictures • Design is

    a process • Design is objective • Design pushes limits Wednesday, July 11, 12
  17. Understanding your designer • Not all designers are equal. •

    Different skill sets, strengths, weaknesses Wednesday, July 11, 12
  18. Understanding your designer • Not all designers are equal. •

    Different skill sets, strengths, weaknesses • Design school is a complex learning process Wednesday, July 11, 12
  19. Understanding your designer • Not all designers are equal. •

    Different skill sets, strengths, weaknesses • Design school is a complex learning process • Designers are damaged goods Wednesday, July 11, 12
  20. Understanding your designer • Not all designers are equal. •

    Different skill sets, strengths, weaknesses • Design school is a complex learning process • Designers are damaged goods • Designers != PS monkeys Wednesday, July 11, 12
  21. Understanding your designer • Not all designers are equal. •

    Different skill sets, strengths, weaknesses • Design school is a complex learning process • Designers are damaged goods • Designers != PS monkeys • Designer != the guy who can't code Wednesday, July 11, 12
  22. Communication • Examples of non-feedback • make it pop •

    it doesn’t seem finished Wednesday, July 11, 12
  23. Communication • Examples of non-feedback • make it pop •

    it doesn’t seem finished • make it look more like x Wednesday, July 11, 12
  24. Communication • Designers capable of compromise • Don't confuse debate

    with contention • Designers are trained to be criticized and to defend their decisions Wednesday, July 11, 12
  25. Communication • Make the designer a part of standups •

    Have them give status updates Wednesday, July 11, 12
  26. Communication • Make the designer a part of standups •

    Have them give status updates • Use Dropbox - Creative Cloud Wednesday, July 11, 12
  27. • Higher Brain • Imagining • Self Understanding • Thinking

    • Control Over Emotions • Planning Forging a relationship Wednesday, July 11, 12
  28. • Lower Brain • Basic needs • Breathing • Blinking

    • Anger • Fear Forging a relationship Wednesday, July 11, 12
  29. Forging a relationship A priority is observed, not manufactured or

    assigned. Otherwise, it's necessarily not a priority. Wednesday, July 11, 12
  30. Forging a relationship Making something a BIG RED TOP TOP

    BIG HIGHEST #1 PRIORITY changes nothing but text styling. If it were really important, it'd already be done. Period. Think about it. Merlin Mann Wednesday, July 11, 12
  31. Forging a relationship • Bring them in early and often

    • Define roles • Who is the ultimate decision maker? • What is the end goal of the designer? • Explain roadmap Wednesday, July 11, 12