Jun 23

Capturing Design Decisons

An excellent article from B&A last month goes over some techniques for writing design documentation. Don’t let the word “documentation” throw you. It’s really a way to explain and sell your design to the stakeholders. As its author, Ryan Olshavsky, explains in the comments, “the type of document I talk about in the article is typically oriented less toward programmers than toward the decision makers (who are more likely to be product managers, executives, or possibly even other designers).”

I think a nice example of such a document is the introduction to the beta test of the new Simon Fraser University site. If you would like to help them out, once you’ve had a look, the team seems to be soliciting constructive criticism from the general public as well.

Comments & TrackBacks

Comments and trackbacks are closed.

A Few Related Entries

Document Centered Design
The six phases of a design project
Design for Conversation
Design by Committee