1
2


August 2018
Service Design, Workshop Facilitation
When my mentor Sela Lewis asked me if I would like to present with her at UX Week around the concept of slow service design, I was thrilled. Too often, designers use rapid prototyping as a band-aid solution, ignoring the larger social issues at play.
Using the public transportation system as a model, we led workshop participants through an exercise in which they first quickly came up with some design solutions for a bus system. We then rode an actual public bus and took note of all of the interactions at play around them: from the visible like drivers and passengers, to the invisible like the marketers responsible for advertising on buses. After actually experiencing the system we were trying to redesign, we built out a service blueprint to understand who the actual stakeholders were in the proposed solutions we had.
The conclusion? Designing for the physical world, especially when it comes to service design, is way more complicated than we think. Our design decisions cause ripple effects through entire communities of people, and we shouldn’t be making them lightly.
Service Blueprint
During the workshop, we had participants create a service blueprint together. The most interesting part was getting them to agree on what actions were frontstage versus backstage—a concept that many of them (including myself, before this project!) weren’t familiar with before.