When to consider technology, during the design process (was RE: Re[3]: "The beginning of the end of the desktop")

11 Jan 2005 - 6:00pm
9 years ago
1 reply
671 reads
Dave Malouf
2005

I like Lada's outline.

I think another great way to work is just x-functionally.
This is something that has been working really wellf or me lately.

Design with your eye on the prize and let your developers tell you "No" for
all the possible reasons that they can say no.

What this leaves you with is the following:
1. You have communicated to your x-functional team (business, opps,
development, etc.) a vision of what is to come.

2. As Lada suggested, often designers under shoot the possibilities when we
consider technology too soon in the process.

3. It actually is a great x-functional team building exercise because the
developers feel engaged in the design process as opposed to having designs
handed to them over a wall.

4. If the x-functional team includes business/marketing types, you can get
their buy-in on designs which can be helpful in pushing resource
adjustments. ;)

I'm sure people can add even more to this list.

-- dave

Comments

11 Jan 2005 - 8:03pm
Lada Gorlenko
2004

DH> I think another great way to work is just x-functionally.

It's the same way :-)

DH> Design with your eye on the prize and let your developers tell you "No" for
DH> all the possible reasons that they can say no.

Works only when design and development teams know each other well and
have respect and trust. In my case (large company, new development
team almost on every project), it has to be earned with every new team,
and one'd better filter hard "all the possible reasons that they can
say no" at the first encounter.

DH> What this leaves you with is the following:
DH> 1. You have communicated to your x-functional team (business, opps,
DH> development, etc.) a vision of what is to come.

DH> 2. As Lada suggested, often designers under shoot the possibilities when we
DH> consider technology too soon in the process.

DH> 3. It actually is a great x-functional team building exercise because the
DH> developers feel engaged in the design process as opposed to having designs
DH> handed to them over a wall.

DH> 4. If the x-functional team includes business/marketing types, you can get
DH> their buy-in on designs which can be helpful in pushing resource
DH> adjustments. ;)

5. It keeps you, the designer, on your toes, which may even result
in a better design (provoked, developers try hard to discover gaps
in what you tell them, too!).

On a personal note: when handled gracefully, it becomes foundation
of a long-term friendship:
6. It can shorten research time in future fool-proofing (two Senior
Developers from past projects are now my first contact points).
7. It may even bring you new work (in our company, developers get
assigned to projects before designers, and I now get often notified
of the vacancies by development teams).

Lada

Syndicate content Get the feed