Wednesday, December 10, 2008

. . .that design is not a manufacturing activity.

The process of design and design thought is not something that can be corralled into processes that work well for coding.

A developer works to build, or assemble code into a working product. They don't sit and ponder if one set of code instructions is better than another or more beautiful or pleasing. They just know it needs to work flawlessly. The goal is to produce predictable results every time.

The goal of design is to arrive at something new and fresh. For that, design thinking needs time, space, breathing room. It is intensity, then lull, for this is often when ideas are born, solutions become evident, or the right design coalesces. This "loafing" can be seen as unproductive by some, but is essential for designers.

Trying to force the visioning part of the process into the same methods that work for the development part of the process is square-peg-in-round-hole uncomfortable. Each process has it's place in the overall success of a user's experience and should be not only allowed to exist, but supported and encouraged and sought after in the company.


Let each person exercise the art they know best.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.