October 2015 - Method+Madness Conference A talk about methods for designers to follow in order to facilitate a smooth and more seamless hand-off to development. Includes some tips, best practices, and one very ill conceived entrance music idea.

1. LiveTogetherinPerfectHarmony
+

3. Fostering better relationships between
developers and designers.
J-MAN, WHAT ARE YOU TALKING ABOUT?

4. Bro, the Internet has gotten ugly.
(Also, tryin’ to up that gif game.)
HAMMER, WHY ARE YOU TALKING ABOUT THAT?

6. Combining our forces will save us all.
Only together can we succeed.
BUT HAMBONE, HOW DO WE STOP IT?

7. If I said to you, “Hey champ, I want to
give you like, a bunch of years of
experience and skill right now, without
you doing much…” would you take it?
IT STARTS WITH UNDERSTANDING EXPERTISE.

9. Which is why we need that designer or
that developer on our side to do our best.
AUDIENCE, REAL TALK–YOU CAN’T ACTUALLY BE EVERYTHING

11. “The only way to make a relationship
work is through communication.”
-BASICALLY EVERYONE EVER, REGARDLESS
OF SUCCESS OR ADHERENCE

12. If you want to have success in web
design (and relationships!) you
simply must…
DEAR DESIGNERS,

16. And yes, developers, that means you
have to make an effort also. Not just
in learning some design jabber but also…
WE NEED TO FIND COMMON GROUND WITH EACH OTHER

18. …is that they run both ways. Designers
should educate themselves. But they
don’t need to prostrate themselves.
THE TRUTH ABOUT OUR RELATIONSHIPS…

19. …is that they run both ways. Developers
should have some flexibility. But they
don’t need to stay quiet about design
decisions or experience issues.
THE TRUTH ABOUT OUR RELATIONSHIPS…

20. PARSIMONY VS. PRECIOUSNESS

21. While I regale you with a poignant,
pertinent, and enthralling anecdote.
THIS SPACE NEEDS TO REMAIN UNADORNED

22. Make the time to have real discourse
about the styles, technologies, ideas,
or crazy proofs of concept you’ve been
mulling over.
COLLABORATION IS JUST A FEW QUESTIONS AWAY

25. Why, if we develop under the auspices
of object oriented programming, do we
still struggle to design that way?
OBJECT ORIENTED PROGRAMMING

27. It can be atomic, subatomic, macro,
micro, creationist, libertarian…whatever.
As long as it’s intelligent design.
YOUR DESIGN SYSTEM CAN BE WHATEVER WORKS

29. “I *state your name*, do hereby promise
to avoid comps, pixel perfection, and
designing without content until my soul
and spirit are in horrible jeopardy.”
HEY, I HAVE AN IDEA–DESIGNERS, LET’S MAKE A PACT

30. “I *state your name*, do hereby promise
to be kind about line-height, letter-spacing
margin, padding, and fussy shit.”
HEY, I HAVE AN IDEA–DEVELOPERS, LET’S MAKE A PACT

31. “I *state your name*, do hereby promise
to keep lines of copy between 45 and
60 characters whenever possible. I also
promise to quit starting my bio with
flaccid shit like, “Why, hello there!”
HEY, I HAVE AN IDEA–EVERYBODY, LET’S MAKE A PACT

33. Designers, make a point of making a
seat for your developer compatriots.
Too many scopes are decided without
consulting the dev team.
IT’S 2015, WE ALL DESERVE A SEAT AT THE TABLE

34. So let’s quit hiding behind our monitors,
our excuses, our traditional process, and
weird company politics and make sure
everyone’s voice is heard.
NONE OF US, HOPEFULLY, DO THIS FOR THE MONEY

35. These rules and ideas work with
marketers, project managers, clients,
students, peers, bears, and soul and
rock legends.
JUST IN CASE YOU WERE WONDERING

37. fatandhandsome
jeremy@jeremyhamman.com
R.I.P. #ExpertiseBalloon