Design is a process during which many things occur. Sometimes we need to communicate what this is, where we are at, how we decided, what we learned, or why this could matter to you. At times we must provide enough context so that everyone can make an informed contribution. Here I will share artifacts I've created to tell the story of a process or a product.
When I started my UX role at City of Seattle, I identified that one of our core resources, our public-facing Digital Style Guide, was underperforming because it lacked orientation and a user-centered approach. I pitched a refresh project to my leadership team and it was accepted. The project, which I led from start to finish, resulted in this resource becoming one of the flagship features representing Seattle's innovation in digital government and digital accessibility. I wrote about the project in a blog post for the City's IT department.
I created a 2-minute video promotion for a fictional IoT (Internet of Things) device. The device itself had not been visualized and the video shows a crude placeholder, indicating the project is purely conceptual. This video was recognized for its ability to communicate a quirky concept in an effective way.
On a four-person team, I led the design and content strategy for a presentation that told the complete story of our project from problem statement through completion. I created much of the narrative structure, flow, and content for the deck. A teammate created the mockups of the app itself, and team members all contributed to the writing. This was a student project and this deliverable was recognized for its clear storytelling.
See the project deck
I interviewed a tech CEO with the intent to create a journey map of their experience starting a tech company from the ground up. But I liked the story so much that I decided to create a journey map in the form of a narrative slideshow, with my own sketches.