The design outcomes I've shown in my portfolio represent the vision and direction of sites and applications as they were ultimately produced. However, much of my work in the digital design space is conducted prior to creative direction and detail design of the user interface.

Applications demand detailed requirements for interaction design and development sprints. But requirements can only be produced when there is clear understanding of the audience, the desired user experience, and the business cases driving the product. I use service diagrams, interaction maps, information architecture diagrams, and other documents during the initial experience design phases of a project to clarify strategy and drive conscensus. I prefer to be light on documentation, producing one only if it will be a living document and continually useful. At this stage, the products or services themselves are in development, and diagramming the service helps to visualize the interactions and opportunities to improve the experience.

Those opportunities become projects like the ones you see elsewhere on this site.