I’ve always had a fascination with what I’ll call Communication Design: the visual representations of ideas, information and relationships in such a way that something of value is communicated to the reader. While on some level, you could just refer to this as information design, I prefer to leave that term as it related to designing the information contained within web sites and applications, which is discussed in the Interaction Design section of this site.
The organization of content in an ecosystem of web sites often needs to be visualized. In this case, I created visualizations that showed how different personas would interact with the distribution of content, highlighting how many different properties they would need to touch in order to have their needs met. This type of diagram can quickly illustrate where personas might encounter difficulties with far-flung content.
In this illustration, I lay out the high-level technical landscape for an online retailer, illustrating properties, technologies and people involved in the publication of product-related content. The goal was to provide quick visualization of how the pieces fit together; this type of “Big Picture” visualization is common and very useful for large, complex systems.
Back in the dot-com days, web technologies were changing very quickly, and competency models for UI developers needed to keep pace with the change in order to remain relevant. During my time at Sapient, I helped develop our UI developer competency model, and used this illustration to show how competencies needed to evolve from the current state at the time.
We were looking at the content landscape for an online publisher who was looking to overhaul the way their different content properties interacted with one another. In an effort to provide a spectrum of possible directions, I illustrated a number of different models being used by other publishers, then created a simple illustration to visualize these different models.
One of my project teams was having difficulty reaching a stable set of functional requirements for our product. In an effort to facilitate discussion, I drew a schematic of our iterative requirements process, identifying places where we might improve or change our behavior to streamline definition.