I think at the heart of what we are trying to do lies a need to fully appreciate and understand what it is that a project entails, and to then figure out how we want to create, capture, and navigate, and share them. Above is a stab at a taxonomy of the concept of “project”. Each piece and sub-piece of the project is surrounded by a cycle of thinking and making, and each piece is capable of informing or contributing to the other pieces. What is important here is not that the causal process of the project be defined, but rather the basic categorization of the pieces that both support the process and are a product of the process. Also, it is important to note that it is the whole project that creates a bridge between a designer and the audience designed for, not just the final output, and that the relationship between the designer and the project is itself mediated by the tools which allow the designer to work within it.

Some definitions for the diagram:

Brief: the initial starting point for the project, the constraints, and the anchor for its development.

Library: the place where project related content lives, whether generated through process, or gathered as reference material from elsewhere. Sketches, comps, writing, photos, etc. This includes past projects, your own, and those of others.

Tools: a collection of project relevant, non-volitional assets.

People: collaborators whose consultation, content based contributions, or tool based expertise are an asset to the project.

Formats: A collection of possible ways to curate, package, and share content.

Output: The combination of content and its pulished qualities (location, format, time, distribution). This may also include a piece of contents location within the library of someone elses project.