36
STOP LOOKING FOR DESIGNERS. BECOME ONE! On why developers need to learn design.

Stop looking for designers. Become one! (On why developers should learn design)

Embed Size (px)

Citation preview

Page 1: Stop looking for designers. Become one! (On why developers should learn design)

STOP LOOKING FOR DESIGNERS. BECOME ONE!

On why developers need to learn design.

Page 2: Stop looking for designers. Become one! (On why developers should learn design)

DESIGNERS SHOULD LEARN HOW TO CODE.

Kids too. And grandparents. And your dog.

Page 3: Stop looking for designers. Become one! (On why developers should learn design)

WHAT ABOUT DEVELOPERS?

Page 4: Stop looking for designers. Become one! (On why developers should learn design)

DEVELOPERS vs. DESIGNERS

Page 5: Stop looking for designers. Become one! (On why developers should learn design)

AWS IS A PLATFORM TO HELP DEVELOPERS RUN THINGS IN THE CLOUD™

Page 6: Stop looking for designers. Become one! (On why developers should learn design)
Page 7: Stop looking for designers. Become one! (On why developers should learn design)
Page 8: Stop looking for designers. Become one! (On why developers should learn design)

USABILITYYes. Developers need usable tools too.

Page 9: Stop looking for designers. Become one! (On why developers should learn design)

"HEY, WE JUST FINISHED IMPLEMENTING THIS. LET'S CALL THE DESIGNERS AND

MAKE IT LOOK NICE!"Unknown developer. All the times.

Page 10: Stop looking for designers. Become one! (On why developers should learn design)

NO!

Page 11: Stop looking for designers. Become one! (On why developers should learn design)

USER EXPERIENCE DESIGN (UX)

Human-Machine interaction

Page 12: Stop looking for designers. Become one! (On why developers should learn design)

DESIGN AS A SERVICE™

Page 13: Stop looking for designers. Become one! (On why developers should learn design)

BUSINESS NEED

Page 14: Stop looking for designers. Become one! (On why developers should learn design)

BUSINESS NEEDDESIGN AGENCY

Page 15: Stop looking for designers. Become one! (On why developers should learn design)

BUSINESS NEEDDESIGN AGENCY

DEVS IMPLEMENTATION

Page 16: Stop looking for designers. Become one! (On why developers should learn design)

BUSINESS NEEDDESIGN AGENCY

DEVS IMPLEMENTATION???

PROFIT

Page 17: Stop looking for designers. Become one! (On why developers should learn design)

TODAY IS DIFFERENTAgile methodologies, design thinking.

Page 18: Stop looking for designers. Become one! (On why developers should learn design)

BRAINSTORMPROTOTYPE

SHIPTESTING

ITERATE ON PROTOTYPE

Page 19: Stop looking for designers. Become one! (On why developers should learn design)

WE ARE NOT "JUST" SOLVING A PROBLEM.

WE DELIVER AN EXPERIENCE

Page 20: Stop looking for designers. Become one! (On why developers should learn design)

TASK DRIVEN TEAMSVS

USER DRIVEN TEAMS

Page 21: Stop looking for designers. Become one! (On why developers should learn design)

TASK DRIVEN TEAMSThey find a solution to a specific business or technological

problem

Page 22: Stop looking for designers. Become one! (On why developers should learn design)

USER DRIVEN TEAMSThey solve a user problem

Page 23: Stop looking for designers. Become one! (On why developers should learn design)

FROM TASK SOLVERS TO EXPERIENCE CREATORS

Page 24: Stop looking for designers. Become one! (On why developers should learn design)

USER CENTERED DESIGNDesign based on the needs of the user.

Page 25: Stop looking for designers. Become one! (On why developers should learn design)

"[..] simplifying the structure of tasks, making things visible, getting the mapping right, exploiting the powers of constraint,

designing for error, explaining affordances and seven stages of action. [..]"

https://en.wikipedia.org/wiki/Don_Norman#User-centered_design

Page 26: Stop looking for designers. Become one! (On why developers should learn design)

PERSONASCENARIOUSE CASE

Page 27: Stop looking for designers. Become one! (On why developers should learn design)

PERSONA: "[..] is a user archetype used to help guide decisions about

product features, navigation, interactions, and even visual design.

In most cases, personas are synthesised from a series of

ethnographic interviews with real people. [..]"

https://en.wikipedia.org/wiki/User-centered_design#Analysis_tools

Page 28: Stop looking for designers. Become one! (On why developers should learn design)

SCENARIO: "[..] is a fictional story about the "daily life of" or a sequence of events with the

primary stakeholder group as the main character. Typically, a persona that was created earlier is used as

the main character of this story. [..]"https://en.wikipedia.org/wiki/User-centered_design#Analysis_tools

Page 29: Stop looking for designers. Become one! (On why developers should learn design)

USE CASE: "[..] describes the interaction between an individual and the rest of the world. Each use case

describes an event that may occur for a short period of time in real life, but may consist of intricate details and

interactions between the actor and the world. [..]"

https://en.wikipedia.org/wiki/User-centered_design#Analysis_tools

Page 30: Stop looking for designers. Become one! (On why developers should learn design)

CULTURAL CLASH

Page 31: Stop looking for designers. Become one! (On why developers should learn design)

ILLUSTRATORUSER RESEARCH

WIREFRAMEYou designers are better. That's fine, it's your job.

Page 32: Stop looking for designers. Become one! (On why developers should learn design)

IT'S ABOUT UNDERSTANDING THE IMPLICATION OF WHAT

WE ARE IMPLEMENTING

Page 33: Stop looking for designers. Become one! (On why developers should learn design)

IT'S ABOUT TESTING AND KILLING

OVER-ENGINEERING

Page 34: Stop looking for designers. Become one! (On why developers should learn design)

IT'S ABOUT SPEAKING THE SAME LANGUAGE

Page 35: Stop looking for designers. Become one! (On why developers should learn design)

IT'S ABOUT CREATING AN EXPERIENCE.