[Sigia-l] the lesser importance of home pages -> moresplashpagefun?

[Stewart Dean]

On 20/12/05 9:14 pm, "Listera" <listera at rcn.com> wrote:

> Christopher Fahey:
> 

>> One can *conceptually* separate graphic design from strategy, structure,
>> architecture and (even selection of) content without *actually* denying a
>> graphic designer a role in those tasks.
> 
> Design is a holistic process, I flatly refuse to cannibalize it in any shape
> or form with what are silly titles to me. Design is problem solving
> (balanced between the client and the user): it's strategy AND structure AND
> architecture AND interaction AND interface AND graphics AND usability. In my
> book, there's no OR. So your pitting "graphic designer" against the rest is
> not something I share at all.

This is where you have a huge problem, as I have others have raised before.

By labeling the whole problem solving 'design' you effectively devalue that
word. Why - because all of a sudden the programmers and technical architects
and copy writers become designers as they are part of the problem solving.
It is about working as a team and if I called myself a designer even though
I could say I am designing a solution it would lead to confusion, concerns I
might be doing someone else's job etc.

Christopher is right about his conceptual split between roles - all these
roles work together to create the final solution and the process of getting
ot the final solution is not 'design'.

Design is problem solving - but so is engineering, authoring, architecting,
coding, strategizing etc....

Thankfully design is commonly understood to be visual design unless prefixed
with something else in the world I work in. It really avoid confusion. Come
to think of it it was the same for the US companies I was working for so I'm
confused over how you can the term without being thought of as a visual
designer first.

Stew Dean