Who designs what? (see diagram...)

4 Oct 2007 - 10:05am
7 years ago
19 replies
654 reads
russwilson
2005

Given that "design" is a very overloaded and broad term, I often
find it necessary to communicate what "product design" is responsible for,
and "who designs what".

To that end, I created this very basic diagram. I'd love to get feedback from members of the list.
The purpose is to spell out who is designing what and provide an indication of:

1) structure of the two depts.

2) responsibilities of the two depts.

3) communication between the two depts.

What did I leave out? Is this the stupidest thing you've ever seen?
(obviously this would be part of a discussion and not intended to stand by itself, although I suppose
I could evolve it to become more self-explanatory)

[cid:image001.jpg at 01C80675.A55CC5C0]

Russell Wilson | Director of Product Design
NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
NetQoS: Performance Experts
www.netqos.com<http://www.netqos.com/>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 95540 bytes
Desc: image001.jpg
Url : http://lists.interactiondesigners.com/pipermail/discuss-interactiondesigners.com/attachments/20071004/9786e24a/attachment.jpg

Comments

4 Oct 2007 - 10:28am
Calvin Park 박상빈
2007

Before we start flaming Russell "You can't attach picture on the
email", I vote that we implement a system where the mailman bounces
back the email with a friendly message that attachments should be
linked.

On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
> Given that "design" is a very overloaded and broad term, I often
> find it necessary to communicate what "product design" is responsible for,
> and "who designs what".
>
> To that end, I created this very basic diagram. I'd love to get feedback from members of the list.
> The purpose is to spell out who is designing what and provide an indication of:
>
> 1) structure of the two depts.
>
> 2) responsibilities of the two depts.
>
> 3) communication between the two depts.
>
> What did I leave out? Is this the stupidest thing you've ever seen?
> (obviously this would be part of a discussion and not intended to stand by itself, although I suppose
> I could evolve it to become more self-explanatory)
>
> [cid:image001.jpg at 01C80675.A55CC5C0]
>
>
>
> Russell Wilson | Director of Product Design
> NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
> 512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
> NetQoS: Performance Experts
> www.netqos.com<http://www.netqos.com/>
>
>
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>
>
>

4 Oct 2007 - 10:32am
Pierre Abel
2004

Hi Russell,

I think you could have a look at this great article, it is really
connected to your diagram,and it adds product management in the loop.
http://www.uxmatters.com/MT/archives/000194.php

Pierre

4 Oct 2007 - 10:34am
White, Jeff
2007

It's not the stupidest thing I've ever seen. I saw that in the mirror this
morning. Ha!

Seems like some mention of business analysis responsibilities should be in
engineering - or do you have a separate product mgmt group that handles
that? Also, engineering is design design design - no mention of code
development or management. Is the diagram supposed to be inclusive of all
responsibilities - or just the ones involving some sort of design?

Jeff

On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
>
> Given that "design" is a very overloaded and broad term, I often
> find it necessary to communicate what "product design" is responsible for,
> and "who designs what".
>
> To that end, I created this very basic diagram. I'd love to get feedback
> from members of the list.
> The purpose is to spell out who is designing what and provide an
> indication of:
>
> 1) structure of the two depts.
>
> 2) responsibilities of the two depts.
>
> 3) communication between the two depts.
>
> What did I leave out? Is this the stupidest thing you've ever seen?
> (obviously this would be part of a discussion and not intended to stand
> by itself, although I suppose
> I could evolve it to become more self-explanatory)
>
> [cid:image001.jpg at 01C80675.A55CC5C0]
>
>
>
> Russell Wilson | Director of Product Design
> NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
> 512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:
> russell.wilson at netqos.com>
> NetQoS: Performance Experts
> www.netqos.com<http://www.netqos.com/>
>

4 Oct 2007 - 10:37am
Petteri Hiisilä
2004

> Given that "design" is a very overloaded and broad term, I often
> find it necessary to communicate what "product design" is
> responsible for,
> and "who designs what".

I like the diagram a lot, along with the pair of diagrams in the
attachment (adopted from About Face 3).

How about an extended, zoomed out version, in which you also display
the outputs or outcomes of these two departments together?

I guess the CDO+CTO activities would be categorized into "R&D
activities" by many sales and marketing oriented people. They could
justifiably ask: "What do we get out of this, and where's the stuff
that we can actually sell? Are we going to sell specs?"

All this depends on your audience, of course. I mean, some of us _do_
sell specs for living ;)

Best,
Petteri

--
Petteri Hiisilä
Senior Interaction Designer
iXDesign / +358505050123 /
petteri.hiisila at ixdesign.fi

"Simple is better than complex.
Complex is better than complicated."
- Tim Peters

-------------- seuraava osa --------------
Ei-tekstimuotoinen liite on poistettu...
Nimi: overall_success_2.png
Tyyppi: image/png
Koko: 147255 bytes
Kuvaus: ei saatavilla
Url : http://lists.interactiondesigners.com/pipermail/discuss-interactiondesigners.com/attachments/20071004/dd4f0722/attachment.png
-------------- seuraava osa --------------
Ei-tekstimuotoinen liite on poistettu...
Nimi: overall_success_1.png
Tyyppi: image/png
Koko: 114464 bytes
Kuvaus: ei saatavilla
Url : http://lists.interactiondesigners.com/pipermail/discuss-interactiondesigners.com/attachments/20071004/dd4f0722/attachment-0001.png
-------------- seuraava osa --------------

4 Oct 2007 - 10:43am
Mark Schraad
2006

Hi Russell,

Some great thought here. This is precisely why I was pushing the 'who designs' discussion a while back. Just 5 minutes ago I came out of a meeting with a channel (business) group and they kept saying "when you create mocks", in fact so did the CD. The implication being, that we designers create some picture so that the business, product and marketing folks can decide what will be included and where to move stuff around. Certainly it is easier for those folks to work from a visual reference point. Granted this is an extreme case of misperception, but honestly thinking about past projects... many, many product design decisions are made by what is thought of on this list as "non-design" roles.

Specific to your question... loads of people make contributions and decisions about the functional requirements besides engineering. I think your diagram needs to be much broader and include users, purchasers, marketers, revenue directors, and designers.

Mark

On Thursday, October 04, 2007, at 12:06PM, "Wilson, Russell" <Russell.Wilson at netqos.com> wrote:
>Given that "design" is a very overloaded and broad term, I often
>find it necessary to communicate what "product design" is responsible for,
>and "who designs what".
>
>To that end, I created this very basic diagram. I'd love to get feedback from members of the list.
>The purpose is to spell out who is designing what and provide an indication of:
>
>1) structure of the two depts.
>
>2) responsibilities of the two depts.
>
>3) communication between the two depts.
>
>What did I leave out? Is this the stupidest thing you've ever seen?
>(obviously this would be part of a discussion and not intended to stand by itself, although I suppose
>I could evolve it to become more self-explanatory)
>
>[cid:image001.jpg at 01C80675.A55CC5C0]
>
>
>
>Russell Wilson | Director of Product Design
>NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
>512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
>NetQoS: Performance Experts
>www.netqos.com<http://www.netqos.com/>

4 Oct 2007 - 12:00pm
Dave Malouf
2005

What seems to be off to me in this diagram that leaped out to me is
the separation of "Product Design" and "User Experience Design".
What's the difference? Especially in a software company, though I
would argue in hardware you also shouldn't separate these.

I think to address Mark's comments, I would emphasize this as not to
be "solely contributors" but rather accountable owners of the
deliverables and subject matter.

The other part that seems to be missing here is "Product
Management/Program Management/Product Marketing" (the PM-3). don't
they have an MRD, or other How/What documents that contribute?

Lastly, where is research? Not necessarily R&D, but generative
requirements research and validation?

When it comes to R&D from an innovation perspective, where i am now
seems to be the best scenario for a technology firm where the CTO and
the CDO are co-owners of innovation, but projects fall under the CDO
b/c all innovation starts from design research if indeed you want to
be user driven and not technology driven. The design group here has
its own internal advanced engineering team who's purpose is to
execute on innovation projects that are derived through design
research and design processes.

-- dave

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the improved ixda.org
http://beta.ixda.org/discuss?post=21062

4 Oct 2007 - 12:09pm
Mark Schraad
2006

I think, Dave, that you are of the fortunate few.

On Thursday, October 04, 2007, at 02:01PM, "David Malouf" <dave at ixda.org> wrote:

...projects fall under the CDO b/c all innovation starts from design research if indeed you want to be user driven and not technology driven. The design group here has its own internal advanced engineering team who's purpose is to execute on innovation projects that are derived through design research and design processes.

4 Oct 2007 - 12:13pm
Dave Malouf
2005

Well, Russell is trying to build an ideal team and structure from what I
understand, so trying to give him a whiff of the possibilities.

What is most important is not heirarchy but rather culture. The fact that
engineers can live under the management of a designer is very different from
what we are all used to, but it isn't required to make the situation work.
Dotted lines of communication and shared project leadership and
understanding the processes and methods of each other are much more
important than top-down structuring.

-- dave

On 10/4/07, Mark Schraad <mschraad at mac.com> wrote:
>
> I think, Dave, that you are of the fortunate few.
>
>
> On Thursday, October 04, 2007, at 02:01PM, "David Malouf" <dave at ixda.org>
> wrote:
>
> ...projects fall under the CDO b/c all innovation starts from design
> research if indeed you want to be user driven and not technology driven. The
> design group here has its own internal advanced engineering team who's
> purpose is to execute on innovation projects that are derived through design
> research and design processes.
>
>

--
David Malouf
http://synapticburn.com/
http://ixda.org/
http://motorola.com/

4 Oct 2007 - 12:27pm
pnuschke
2007

I just submitted a proposal to CHI for a panel discussing something very
similar to this topic- it's titled something like "Who does what and why in
the design of interactive software." I was less concerned with departments
and more with the actual work being done- some people do research, design,
AND analysis, while other people may specialize within one of these fields (
e.g., IA's doing wireframes). Is it reasonable to expect that one person can
be an expert in all areas? What models of generalization and specialization
do companies (and educational institutions) use and why?

On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
>
> Given that "design" is a very overloaded and broad term, I often
> find it necessary to communicate what "product design" is responsible for,
> and "who designs what".
>
> To that end, I created this very basic diagram. I'd love to get feedback
> from members of the list.
> The purpose is to spell out who is designing what and provide an
> indication of:
>
> 1) structure of the two depts.
>
> 2) responsibilities of the two depts.
>
> 3) communication between the two depts.
>
> What did I leave out? Is this the stupidest thing you've ever seen?
> (obviously this would be part of a discussion and not intended to stand
> by itself, although I suppose
> I could evolve it to become more self-explanatory)
>
> [cid:image001.jpg at 01C80675.A55CC5C0]
>
>
>
> Russell Wilson | Director of Product Design
> NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
> 512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:
> russell.wilson at netqos.com>
> NetQoS: Performance Experts
> www.netqos.com<http://www.netqos.com/>
>
>
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>
>
>

4 Oct 2007 - 12:29pm
Joseph Selbie
2007

Russell,

Do you actually have separate people responsible for Interaction Design,
Visual Design, Information Design and Information Architecture Design? I can
clearly see the need for a separate visual designer, because that is a skill
that rarely crosses over with the others. But your other three design roles
seem to overlap so much that it hard for me to see where you are helped by
separating them.

I am probably projecting my experience with web application design onto your
diagram, but in all the teams I've led or been involved with I would be hard
pressed to separate interaction, information and information architecture
design into separate processes.

Joseph Selbie
Founder, CEO Tristream
Web Application Design
http://www.tristream.com

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Wilson,
Russell
Sent: Thursday, October 04, 2007 9:05 AM
To: IxDA List
Subject: [IxDA Discuss] Who designs what? (see diagram...)

Given that "design" is a very overloaded and broad term, I often find it
necessary to communicate what "product design" is responsible for, and "who
designs what".

To that end, I created this very basic diagram. I'd love to get feedback
from members of the list.
The purpose is to spell out who is designing what and provide an indication
of:

1) structure of the two depts.

2) responsibilities of the two depts.

3) communication between the two depts.

What did I leave out? Is this the stupidest thing you've ever seen?
(obviously this would be part of a discussion and not intended to stand by
itself, although I suppose I could evolve it to become more
self-explanatory)

[cid:image001.jpg at 01C80675.A55CC5C0]

Russell Wilson | Director of Product Design NetQoS, Inc. | 5001 Plaza on
the Lake, Austin, TX 78746
512.334.3725 (v) | 512.422.4155 (m) |
russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
NetQoS: Performance Experts
www.netqos.com<http://www.netqos.com/>

4 Oct 2007 - 1:07pm
russwilson
2005

Agreed (in reality much broader), but I kept it
this way on purpose as a part of a presentation
specifically to the engineering dept.

-----Original Message-----
From: Mark Schraad [mailto:mschraad at mac.com]
Sent: Thursday, October 04, 2007 11:44 AM
To: Wilson, Russell
Cc: IxDA List
Subject: Re: [IxDA Discuss] Who designs what? (see diagram...)

Hi Russell,

Some great thought here. This is precisely why I was pushing the 'who designs' discussion a while back. Just 5 minutes ago I came out of a meeting with a channel (business) group and they kept saying "when you create mocks", in fact so did the CD. The implication being, that we designers create some picture so that the business, product and marketing folks can decide what will be included and where to move stuff around. Certainly it is easier for those folks to work from a visual reference point. Granted this is an extreme case of misperception, but honestly thinking about past projects... many, many product design decisions are made by what is thought of on this list as "non-design" roles.

Specific to your question... loads of people make contributions and decisions about the functional requirements besides engineering. I think your diagram needs to be much broader and include users, purchasers, marketers, revenue directors, and designers.

Mark

On Thursday, October 04, 2007, at 12:06PM, "Wilson, Russell" <Russell.Wilson at netqos.com> wrote:
>Given that "design" is a very overloaded and broad term, I often
>find it necessary to communicate what "product design" is responsible for,
>and "who designs what".
>
>To that end, I created this very basic diagram. I'd love to get feedback from members of the list.
>The purpose is to spell out who is designing what and provide an indication of:
>
>1) structure of the two depts.
>
>2) responsibilities of the two depts.
>
>3) communication between the two depts.
>
>What did I leave out? Is this the stupidest thing you've ever seen?
>(obviously this would be part of a discussion and not intended to stand by itself, although I suppose
>I could evolve it to become more self-explanatory)
>
>[cid:image001.jpg at 01C80675.A55CC5C0]
>
>
>
>Russell Wilson | Director of Product Design
>NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
>512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
>NetQoS: Performance Experts
>www.netqos.com<http://www.netqos.com/>

4 Oct 2007 - 1:13pm
russwilson
2005

Joseph,

No, I don't. I called them out to raise awareness among
non-design teams about the different things we designers do.
Like you, I have three distinct roles:
1) visual designer
2) IA/Interaction designer
3) Usability expert/testing

-----Original Message-----
From: Joseph Selbie [mailto:jselbie at tristream.com]
Sent: Thursday, October 04, 2007 1:30 PM
To: Wilson, Russell; 'IxDA List'
Subject: RE: [IxDA Discuss] Who designs what? (see diagram...)

Russell,

Do you actually have separate people responsible for Interaction Design,
Visual Design, Information Design and Information Architecture Design? I can
clearly see the need for a separate visual designer, because that is a skill
that rarely crosses over with the others. But your other three design roles
seem to overlap so much that it hard for me to see where you are helped by
separating them.

I am probably projecting my experience with web application design onto your
diagram, but in all the teams I've led or been involved with I would be hard
pressed to separate interaction, information and information architecture
design into separate processes.

Joseph Selbie
Founder, CEO Tristream
Web Application Design
http://www.tristream.com

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Wilson,
Russell
Sent: Thursday, October 04, 2007 9:05 AM
To: IxDA List
Subject: [IxDA Discuss] Who designs what? (see diagram...)

Given that "design" is a very overloaded and broad term, I often find it
necessary to communicate what "product design" is responsible for, and "who
designs what".

To that end, I created this very basic diagram. I'd love to get feedback
from members of the list.
The purpose is to spell out who is designing what and provide an indication
of:

1) structure of the two depts.

2) responsibilities of the two depts.

3) communication between the two depts.

What did I leave out? Is this the stupidest thing you've ever seen?
(obviously this would be part of a discussion and not intended to stand by
itself, although I suppose I could evolve it to become more
self-explanatory)

[cid:image001.jpg at 01C80675.A55CC5C0]

Russell Wilson | Director of Product Design NetQoS, Inc. | 5001 Plaza on
the Lake, Austin, TX 78746
512.334.3725 (v) | 512.422.4155 (m) |
russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
NetQoS: Performance Experts
www.netqos.com<http://www.netqos.com/>

4 Oct 2007 - 1:43pm
Joseph Selbie
2007

Russell,

Thank you for the clarification.

I'm not sure it would be helpful as far as your immediate purpose for your
diagram, but I would add team lead, or lead designer, or some such title to
your list, and I would show all the roles you identified funneling into the
lead designer.

In my experience providing contract services inside over 100 different
companies, and in a formal study Tristream conducted about how teams
structure themselves to best develop web applications, the best teams always
had a lead designer(s) (sometimes it was a pair, rarely a triumvirate). This
person had the most holistic view of the project -- business goals, user
needs and IT capabilities and limitations -- and sat in a creative nexus in
the center of the project.

Sometimes this person came from a programming track and had become
comfortable with the tools and practices of design. More often it was senior
IX designer able to effect the entire team's design process at a user
strategy and user experience level. Sometimes they actually designed, other
times they directed other's designs. But it was always clear that the lead
held the vision.

Joseph Selbie
Founder, CEO Tristream
Web Application Design
http://www.tristream.com

-----Original Message-----
From: Wilson, Russell [mailto:Russell.Wilson at netqos.com]
Sent: Thursday, October 04, 2007 12:14 PM
To: Joseph Selbie; 'IxDA List'
Subject: RE: [IxDA Discuss] Who designs what? (see diagram...)

Joseph,

No, I don't. I called them out to raise awareness among
non-design teams about the different things we designers do.
Like you, I have three distinct roles:
1) visual designer
2) IA/Interaction designer
3) Usability expert/testing

-----Original Message-----
From: Joseph Selbie [mailto:jselbie at tristream.com]
Sent: Thursday, October 04, 2007 1:30 PM
To: Wilson, Russell; 'IxDA List'
Subject: RE: [IxDA Discuss] Who designs what? (see diagram...)

Russell,

Do you actually have separate people responsible for Interaction Design,
Visual Design, Information Design and Information Architecture Design? I can
clearly see the need for a separate visual designer, because that is a skill
that rarely crosses over with the others. But your other three design roles
seem to overlap so much that it hard for me to see where you are helped by
separating them.

I am probably projecting my experience with web application design onto your
diagram, but in all the teams I've led or been involved with I would be hard
pressed to separate interaction, information and information architecture
design into separate processes.

Joseph Selbie
Founder, CEO Tristream
Web Application Design
http://www.tristream.com

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Wilson,
Russell
Sent: Thursday, October 04, 2007 9:05 AM
To: IxDA List
Subject: [IxDA Discuss] Who designs what? (see diagram...)

Given that "design" is a very overloaded and broad term, I often find it
necessary to communicate what "product design" is responsible for, and "who
designs what".

To that end, I created this very basic diagram. I'd love to get feedback
from members of the list.
The purpose is to spell out who is designing what and provide an indication
of:

1) structure of the two depts.

2) responsibilities of the two depts.

3) communication between the two depts.

What did I leave out? Is this the stupidest thing you've ever seen?
(obviously this would be part of a discussion and not intended to stand by
itself, although I suppose I could evolve it to become more
self-explanatory)

[cid:image001.jpg at 01C80675.A55CC5C0]

Russell Wilson | Director of Product Design NetQoS, Inc. | 5001 Plaza on
the Lake, Austin, TX 78746
512.334.3725 (v) | 512.422.4155 (m) |
russell.wilson at netqos.com<mailto:russell.wilson at netqos.com>
NetQoS: Performance Experts
www.netqos.com<http://www.netqos.com/>

4 Oct 2007 - 1:49pm
russwilson
2005

Actually another clarification -- I wasn't separating
Product Design and UX -- I meant to show alternative titles
(i.e. you would either have a VP Product Design OR a VP of UX
under the CDO).

Same for the engineering side -- VP of Dev OR VP of Engineering

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of David Malouf
Sent: Thursday, October 04, 2007 6:00 AM
To: discuss at ixda.org
Subject: Re: [IxDA Discuss] Who designs what? (see diagram...)

What seems to be off to me in this diagram that leaped out to me is
the separation of "Product Design" and "User Experience Design".
What's the difference? Especially in a software company, though I
would argue in hardware you also shouldn't separate these.

I think to address Mark's comments, I would emphasize this as not to
be "solely contributors" but rather accountable owners of the
deliverables and subject matter.

The other part that seems to be missing here is "Product
Management/Program Management/Product Marketing" (the PM-3). don't
they have an MRD, or other How/What documents that contribute?

Lastly, where is research? Not necessarily R&D, but generative
requirements research and validation?

When it comes to R&D from an innovation perspective, where i am now
seems to be the best scenario for a technology firm where the CTO and
the CDO are co-owners of innovation, but projects fall under the CDO
b/c all innovation starts from design research if indeed you want to
be user driven and not technology driven. The design group here has
its own internal advanced engineering team who's purpose is to
execute on innovation projects that are derived through design
research and design processes.

-- dave

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the improved ixda.org
http://beta.ixda.org/discuss?post=21062

________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://beta.ixda.org/guidelines
List Help .................. http://beta.ixda.org/help
Unsubscribe ................ http://beta.ixda.org/unsubscribe
Questions .................. list at ixda.org
Home ....................... http://beta.ixda.org

4 Oct 2007 - 1:56pm
russwilson
2005

That's a good question -- someone else brought that up to.
(design design design)

I think mention of implementation on the engineering side is
important -- I'll add that in. It started off as a "design only"
diagram, but I may evolve it to be much more.

Thanks for the feedback!

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Jeff White
Sent: Thursday, October 04, 2007 11:34 AM
To: IXDA list
Subject: Re: [IxDA Discuss] Who designs what? (see diagram...)

It's not the stupidest thing I've ever seen. I saw that in the mirror this
morning. Ha!

Seems like some mention of business analysis responsibilities should be in
engineering - or do you have a separate product mgmt group that handles
that? Also, engineering is design design design - no mention of code
development or management. Is the diagram supposed to be inclusive of all
responsibilities - or just the ones involving some sort of design?

Jeff

On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
>
> Given that "design" is a very overloaded and broad term, I often
> find it necessary to communicate what "product design" is responsible for,
> and "who designs what".
>
> To that end, I created this very basic diagram. I'd love to get feedback
> from members of the list.
> The purpose is to spell out who is designing what and provide an
> indication of:
>
> 1) structure of the two depts.
>
> 2) responsibilities of the two depts.
>
> 3) communication between the two depts.
>
> What did I leave out? Is this the stupidest thing you've ever seen?
> (obviously this would be part of a discussion and not intended to stand
> by itself, although I suppose
> I could evolve it to become more self-explanatory)
>
> [cid:image001.jpg at 01C80675.A55CC5C0]
>
>
>
> Russell Wilson | Director of Product Design
> NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
> 512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:
> russell.wilson at netqos.com>
> NetQoS: Performance Experts
> www.netqos.com<http://www.netqos.com/>
>
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://beta.ixda.org/guidelines
List Help .................. http://beta.ixda.org/help
Unsubscribe ................ http://beta.ixda.org/unsubscribe
Questions .................. list at ixda.org
Home ....................... http://beta.ixda.org

4 Oct 2007 - 3:17pm
dmitryn
2004

Agreed with Jeff regarding the need for BA/product management to be
represented. Also, it seems odd that the engineering counterpart to
the form and behaviour spec is a requirements document - a technical
architecture spec would seem more appropriate.

Nice diagram, though. Now if only more organizations had orgcharts
that looked like that... :)

That being said, I'm now wondering if this is really the "holy grail"
of organizational design from a UX person's point of view. It seems
like the line separating design and engineering could easily become a
wall over which specs are thrown in either direction, rather than a
collaboration between the two.

Dmitry

On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
> That's a good question -- someone else brought that up to.
> (design design design)
>
> I think mention of implementation on the engineering side is
> important -- I'll add that in. It started off as a "design only"
> diagram, but I may evolve it to be much more.
>
> Thanks for the feedback!
>
>
>
>
> -----Original Message-----
> From: discuss-bounces at lists.interactiondesigners.com [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Jeff White
> Sent: Thursday, October 04, 2007 11:34 AM
> To: IXDA list
> Subject: Re: [IxDA Discuss] Who designs what? (see diagram...)
>
> It's not the stupidest thing I've ever seen. I saw that in the mirror this
> morning. Ha!
>
> Seems like some mention of business analysis responsibilities should be in
> engineering - or do you have a separate product mgmt group that handles
> that? Also, engineering is design design design - no mention of code
> development or management. Is the diagram supposed to be inclusive of all
> responsibilities - or just the ones involving some sort of design?
>
> Jeff
>
> On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
> >
> > Given that "design" is a very overloaded and broad term, I often
> > find it necessary to communicate what "product design" is responsible for,
> > and "who designs what".
> >
> > To that end, I created this very basic diagram. I'd love to get feedback
> > from members of the list.
> > The purpose is to spell out who is designing what and provide an
> > indication of:
> >
> > 1) structure of the two depts.
> >
> > 2) responsibilities of the two depts.
> >
> > 3) communication between the two depts.
> >
> > What did I leave out? Is this the stupidest thing you've ever seen?
> > (obviously this would be part of a discussion and not intended to stand
> > by itself, although I suppose
> > I could evolve it to become more self-explanatory)
> >
> > [cid:image001.jpg at 01C80675.A55CC5C0]
> >
> >
> >
> > Russell Wilson | Director of Product Design
> > NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
> > 512.334.3725 (v) | 512.422.4155 (m) | russell.wilson at netqos.com<mailto:
> > russell.wilson at netqos.com>
> > NetQoS: Performance Experts
> > www.netqos.com<http://www.netqos.com/>
> >
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>

4 Oct 2007 - 2:03pm
Matt Nish-Lapidus
2007

My position is similar actually, I'm:

1) interface developer
2) interaction designer
3) usability expert

I find that in a lot of companies, especially small-mid size people
will wear many hats.. we seem to end up creating a position for
ourselves doing a combination of what we love and are best at.

That's actually one of the reasons I enjoy working at smaller companies.

On 10/4/07, Wilson, Russell <Russell.Wilson at netqos.com> wrote:
> Joseph,
>
> No, I don't. I called them out to raise awareness among
> non-design teams about the different things we designers do.
> Like you, I have three distinct roles:
> 1) visual designer
> 2) IA/Interaction designer
> 3) Usability expert/testing
>
>

8 Oct 2007 - 11:53am
Anna Ma
2007

Sorry to ask a silly question since I'm new here: where can I see the
diagram Russell uploaded or attached?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://gamma.ixda.org/discuss?post=21062

8 Oct 2007 - 1:26pm
Anna Ma
2007

A related question I would like to ask is how you define the different
roles of business analyst and UX specialist? I thought there was a
discussion on this before but I can not find it.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://gamma.ixda.org/discuss?post=21062

Syndicate content Get the feed