3. “The way we work at Apple is that the
complexity of these products really
makes it critical to work collaboratively,
with different areas of expertise. I think
that’s one of the things about my job I
enjoy the most. I work with silicon
designers, electronic and mechanical
engineers, and I think you would
struggle to determine who does what
when we get together. We’re located
together, we share the same goal, have
exactly the same preoccupation with
making great products.”
!
Sir Jonathan Ive
4. TightIntegration
the board is misleading by snickclunk
http://www.flickr.com/photos/snickclunk/4119284398/in/photostream/
17. DONot
Critique engineering prototypes on
aesthetics or usability.
Expect developers to have the same
design sensibilities you have.
Tug Of War by Tom Blackwell
https://flic.kr/p/6pjYgc
18. DONot
Critique engineering prototypes on
aesthetics or usability.
Expect developers to have the same
design sensibilities you have.
Force your process on the developers.
Tug Of War by Tom Blackwell
https://flic.kr/p/6pjYgc
19. DONot
Critique engineering prototypes on
aesthetics or usability.
Expect developers to have the same
design sensibilities you have.
Force your process on the developers.
Expect developers to make last-minute
changes just because you haven’t been
involved until late in the process. Tug Of War by Tom Blackwell
https://flic.kr/p/6pjYgc
21. YesPleasePosition your involvement as something that
makes your developers’jobs easier.
Green Ants by Kasi Metcalfe
https://www.flickr.com/photos/kasimetcalfe/339113868
22. YesPleasePosition your involvement as something that
makes your developers’jobs easier.
Be inclusive. It’s not our responsibility to make
decisions so much as to offer options.
Green Ants by Kasi Metcalfe
https://www.flickr.com/photos/kasimetcalfe/339113868
23. YesPleasePosition your involvement as something that
makes your developers’jobs easier.
Be inclusive. It’s not our responsibility to make
decisions so much as to offer options.
Dare to compromise.
Green Ants by Kasi Metcalfe
https://www.flickr.com/photos/kasimetcalfe/339113868
24. YesPleasePosition your involvement as something that
makes your developers’jobs easier.
Be inclusive. It’s not our responsibility to make
decisions so much as to offer options.
Dare to compromise.
Find opportunities to educate.
Green Ants by Kasi Metcalfe
https://www.flickr.com/photos/kasimetcalfe/339113868
25. YesPleasePosition your involvement as something that
makes your developers’jobs easier.
Be inclusive. It’s not our responsibility to make
decisions so much as to offer options.
Dare to compromise.
Find opportunities to educate.
Be social.
Green Ants by Kasi Metcalfe
https://www.flickr.com/photos/kasimetcalfe/339113868
27. “Have a beer with your engineer. You can accelerate
trust and communication if someone feels you care
about them as a person—and not just a set of skills
that you rely on to realize a design vision.”
Jenna Bilotta – How Designers and Engineers Can Play Nice
(and Still Run with Scissors)
37. EstimateTime
&Effort
“Ideally, the developers and I are to work
closely together during the design phase...
but it typically works out that they gloss over
the document or attend a few meetings and
get a basic understanding of what we are
planning on doing, but never pay attention
to the full details. Then they tend to come to
me with questions or ‘are you crazy? I can’t do
that!’ when it’s time for them to put together
a timeline for their development assessment.
After a few times of close calls, they are
beginning to pay more attention to the
pencil sketches and overall workflows we
put together for them.”
By eflon http://www.flickr.com/photos/eflon/5079163335/
43. A successful tool is one that was used to do something undreamed of by its author. by katerha
http://www.flickr.com/photos/katerha/5746905652/
Usetheir
tools
45. IssueTracking Create items for each of your
design tasks.
Developers can subscribe to the
ones that relate to their own tasks.
Your estimates can be calculated
in the burndown chart, or not.
54. Design
Documentation
Design documentation to be a
reference tool.
Always reference the requirements.
Be concise and explicit in your
explanation.
Label screens effectively.
Be thorough.
Be consistent.
59. Bill Scott
“The developers really appreciated it, because they
could just look at it, and they didn’t have to wonder
if the designer had forgotten something.”
62. Questions?
Roberto Clemente Bridge in Pittsburgh by Brook Ward
https://flic.kr/p/dAWcYQ
Jack Moffett | @jackmoffett
Senior Interaction Designer
Inmedius, a Boeing Company
jackmoffett@mac.com
designaday.tumblr.com
63. 1. State of the Industry
2. Looking for Group
3. Collaboration Life Cycle
4. Why HTML and CSS?
5. Tooling Up
6. Formatting Standards
7. OOCSS
8. Owning Behavior
9. Looking Toward the Horizon
Chapter