Tweet
Tweet

Slide 1

Slide 1 text

Building a UX Team Based on: http://us5.campaign-archive1.com/?awesome=no&u=7e093c5cf4&id=cfe9dbcac8 @bruno2ms Aaron Walter Director of User Experience at MailChimp post by slides by

Slide 2

Slide 2 text

USER EXPERIENCE

Slide 3

Slide 3 text

research development design customer support UX

Slide 4

Slide 4 text

MailChimp UX team of one generalist professional, who: Designed UIs; Wrote front-end code; Built prototypes; Interviewed customers; Conducted usability tests; Responded to Customer Support; Back in 2008 Aaron Walter Director of User Experience at MailChimp

Slide 5

Slide 5 text

A Team of Generalists with specific skills: 4 design researches 2 UI designers 1 expert email designer/developer Aaron Walter (Leader) In 2014

Slide 6

Slide 6 text

When you focus on wireframes and workflows things get lost in translation as ideas are passed to other departments A team filled with specialists but no generalists creates silos. Don`ts

Slide 7

Slide 7 text

EASY TO HIRE, HARD TO FIRE

Slide 8

Slide 8 text

Because it`s easy to hire someone who`s mediocre, but it`s really hard to fire them. Look for passion, curiosity, selflessness, openness, confidence, communication, skills, emotional intelligence, and intrinsic motivation, too. Hiring is hard

Slide 9

Slide 9 text

These things can`t be taught, most skills can

Slide 10

Slide 10 text

Can this person say “we" instead of “me”? Can they let someone else have the glory? Can they put in their best work, then leave control to someone else to take it further? Ask Yourself

Slide 11

Slide 11 text

RESPECT

Slide 12

Slide 12 text

Great designers need to understand engineering enough to empathize with, listen to, and respond to the people who build what they want.

Slide 13

Slide 13 text

Respect between design and development is critical. It don`t happens organically. It has to be a core value of the company, demonstrated by leadership daily.

Slide 14

Slide 14 text

AUTONOMY

Slide 15

Slide 15 text

If failure is not an option in your organization, then neither is success

Slide 16

Slide 16 text

Team needs autonomy to follow their gut. When big decisions need to be made, team autonomy has to give way to the perspective of the whole company.

Slide 17

Slide 17 text

Absolute Autonomy leads to CHAOS Sometimes

Slide 18

Slide 18 text

"Autonomy sometimes lead to miscommunication. Meeting are often vilify, but there`s great value in short, regularly scheduled check-ins."

Slide 19

Slide 19 text

PARALLEL CYCLES

Slide 20

Slide 20 text

5 weeks release cycle followed by our UI design, front-end dev, and engineering teams. It works for refinement but restricts deeper studies. The cycle for deep research is considerably longer, and happens parallel to the rapid cycles of app development.

Slide 21

Slide 21 text

Having in-depht research continually tricking into rapid iteration cycles helps ensure that we`re not only moving fast, but that we`re also moving in the right direction.

Slide 22

Slide 22 text

CREATE A CULTURE OF EMPATHY

Slide 23

Slide 23 text

For a UX team, nothing is more motivating than watching users struggle with your app.

Slide 24

Slide 24 text

THAT`S SERIOUS

Slide 25

Slide 25 text

The outcome of these tests is always the same: We`re made so uncomfortable on their behalf that we`re compelled to make things better immediately.

Slide 26

Slide 26 text

as your customers` experiences become more visible your team will become more empathetic.

Slide 27

Slide 27 text

TELL STORIES

Slide 28

Slide 28 text

Research can`t create change in an organization until it has been turned into a compelling story. research is much more influential when it`s made accessible to others

Slide 29

Slide 29 text

tl;dr;

Slide 30

Slide 30 text

When smart, capable people with complementary skills are united by a deep desire to help customers, great things happen.

Slide 31

Slide 31 text

http://us5.campaign-archive1.com/?awesome=no&u=7e093c5cf4&id=cfe9dbcac8 THANK U Reference: