Snapshots of the work process. Documents that help me communicate with the team, align stakeholders in makeing decisions for branding and marketing strategies, and streamline the product development process. The process is always tailored to the project and the team. Have a look at individual projects for the custom-fitted process of each.
Laying out the land to Visualize where our product fits in. Spreadsheets for detailed analysis of key players around the product.
Use Case and User Stories
Visually depicted scenarios with diagrams and cartoon strips. They show context, problems, and solutions as it is handled without technology. It is an internal communication tool for the team to visualize which pain points in the process our technology will alleviate.
Using plain documents to capture user behavior, pain points, motivations, and needs/desires from customer interviews.
Low Fidelity Wireframes
Visually communicating concepts and specific placement of data and displayed information to collect feedback. I usually recommend this step because fully stylized mockups can distract from the core functionality and result in a poor evaluation. Often times, due to time constraints, this step gets skipped.
Visually communicate 'if user does x, then y happens' with my team and test users to collect feedback. This is typically accompanied with a clickable prototype in InVision or AdobeXD (or html & css in the old school when I first started).
High Fidelity Mockups
Apply product branding, grid structure, typography, color scheme, and icons to key screens to get alignment from the entire team before executing on the details.