Communication among Designers & Engineers

27 Jan 2005 - 9:11am
9 years ago
1 reply
415 reads
Suresh JV
2004

dave: from [buy-in, consensus,etc]
> That's another interesting point ... How do DESIGNERS communicate among
each
> other? I know Andrei you worked at Adobe, which has a host of designers.
How
> did communication between designers on the same project, on related but
> separate projects communicate their research findings?

Oh! this is something I'd love to hear from other over here. How do we all
put
across our points to other teams in general. [not just among designers]
I've always had difficulty to communicate my ideas without
prototypes/sketches.

Here is an interesting article with regard to this topic.
"I'll show you mine, if you show me yours: enhancing communication between
designers and engineers"
http://www.jonathanboutelle.com/mt/archives/2004/06/ill_show_you_mi.html

Regards,
Suresh JV.

Comments

27 Jan 2005 - 9:19am
Dave Malouf
2005

On 1/27/05 9:11 AM, "Suresh JV" <sjv at inteplan.com> wrote:

> Oh! this is something I'd love to hear from other over here. How do we all
> put
> across our points to other teams in general. [not just among designers]
> I've always had difficulty to communicate my ideas without
> prototypes/sketches.
>
> Here is an interesting article with regard to this topic.
> "I'll show you mine, if you show me yours: enhancing communication between
> designers and engineers"
> http://www.jonathanboutelle.com/mt/archives/2004/06/ill_show_you_mi.html

Interesting piece. I both agree and disagree.
1. he doesn't acknowledge how much "design" work has to happen before
prototypes can begin. I mean research to be honest. I also think there are
concept models (which can be seen as a type of prototype) that also need to
get done as well.

2. I like the fact that requirements aren't thrown over a wall, turned into
designs, thrown over another wall, and then made manifest. Blackboxing that
exists in many organizations is not healthy.

3. Data models should not be done until after intitial flow diagrams and GUI
prototypes are designed. Technology is he enabler of UX, not a driver. Later
in the process that back and forth about GUI and Data models makes sense.

To me the best design processes are ones that have as much transparency as
possible along its lifecycle. This means leadership changes hands, but input
and consulting is throughout regardless of title, or primary role.

-- dave

Syndicate content Get the feed