interdisciplinary teams

32

Upload: carolann-bonner

Post on 21-Jan-2017

1.067 views

Category:

Design


0 download

TRANSCRIPT

Page 1: Interdisciplinary teams
Page 2: Interdisciplinary teams

Studied design in school

Worked at a creative agency

Worked at thoughtbot

Now working at Segment

Page 3: Interdisciplinary teams

Favorite website right now:

Page 4: Interdisciplinary teams

It’s hard to change our perceptions and our

understanding.

Page 5: Interdisciplinary teams

segment blog

Page 6: Interdisciplinary teams

There are user needs and there are business needs.

Page 7: Interdisciplinary teams

You want them to be like this:

Page 8: Interdisciplinary teams

Now the blog can reach its potential.

Page 9: Interdisciplinary teams

We found a similar situation when we rebuilt our setup

flow.

Page 10: Interdisciplinary teams

Again, we want this:

Page 11: Interdisciplinary teams

We had something more like this:

Page 12: Interdisciplinary teams

segment setup flow

Page 13: Interdisciplinary teams

Sometimes the business needs and the user needs fight

against each other.

Page 14: Interdisciplinary teams

My job is to help our business and our users complement each

other.

Page 15: Interdisciplinary teams

What do I do now? UNCLEAR

Page 16: Interdisciplinary teams

This is why we work on teams!

Page 17: Interdisciplinary teams

Because there’s too much information. And it feels like this:

Page 18: Interdisciplinary teams

– Christopher AlexanderNotes on the Synthesis of Form

“The technical difficulties of grasping all the information needed for such a form are out of hand – and well beyond the

fingers of a single individual.”

Page 19: Interdisciplinary teams

Be comfortable with being confused.

Page 20: Interdisciplinary teams

Remember what you didn’t know.

Page 21: Interdisciplinary teams

Remember what you found confusing.

Page 22: Interdisciplinary teams

Don’t be the smartest person in the room.

Page 23: Interdisciplinary teams

– Matthew Frederick101 Things I Learned in Architecture School

“An architect knows something about everything. An engineer knows everything

about one thing.”

Page 24: Interdisciplinary teams

Invite yourself to meetings.

Page 25: Interdisciplinary teams

Develop relationships with people outside of your team.

Page 26: Interdisciplinary teams

– Christopher AlexanderNotes on the Synthesis of Form

“…not only is the quantity of information itself by now beyond the reach of single

designers, but the various specialists who retail [the information] are narrow and

unfamiliar with the form-makers’ peculiar problems, so that it is never quite clear how the designer should best consult

them.”

Page 27: Interdisciplinary teams

Learn how to facilitate conversations.

Page 28: Interdisciplinary teams

Be clear about who gets the final decision-making power.

Page 29: Interdisciplinary teams

Stick to your process-oriented training.

Page 30: Interdisciplinary teams

– Matthew Frederick101 Things I Learned in Architecture School

“Being process-oriented, not product driven, is the most important and difficult

skill for a designer to develop.”

Page 31: Interdisciplinary teams

Be inclusive!

Page 32: Interdisciplinary teams

– Max EhrmannDesiderata

“Go placidly amid the noise and haste, and remember what peace there may be

in silence. As far as possible without surrender be on good terms with all

persons. Speak your truth quietly and clearly; and listen to others, even the dull and ignorant; they too have their

story.”