 |
|
 |

| |
Design Leadership
by Morgan Ramsay on 03/24/09 11:00:00 pm
|
|
| |
|
Posted 03/24/09 11:00:00 pm
|
| |
A few weeks ago, Kimberly Unger wrote about The 'Ideas' Guy. One element that struck me was her reference to design documents as things. While that's true, I think looking at design as a means to produce things, documents, can set you on the wrong path.
Like meeting minutes, the design document is a record of the decisions made during the design process. The purpose of keeping and sharing a record, of course, is to facilitate communication of those decisions to anyone that should care.
Raise your hand if you've participated in a planning meeting and the outcome of that meeting ended up on a dusty shelf. That's where many strategic plans end up and that's exactly what you don't want to happen. The outcome should not be merely tangible.
After all, if communication is the goal, then the record is secondary. As the designer, you ought to engage those people who should care in the design process and mobilize them to take up your vision as their own. As the designer, you ought to recognize that your responsibility is not only one of design but also one of leadership.
|
| |
|
|
The occasional parts that read, "this module really sucks and I hate its guts RARH" is amusing to read two months after the fact. Its truth makes it amusing, plus the fact that I did in fact scale that barrier is good for later morale-boosting.