With the rise of climate change, an NGO created a new program requiring service design to expand disaster assistance, serving the most vulnerable clients with long-term recovery needs. With more specific criteria, the new program can now serve clients who may have been previously missed through prior initiatives. Since this service was new, the vision was to design a minimum viable service that focuses on quality outcomes over traditional outputs to learn and plan for future scalability.
Image Credit: Freepik – Pikisuperstar
There’s a lot of work I’m proud to share. Continue to browse through or go to a section:
Being a new service offering in need of design, my goal was to gather a baseline understanding from our business stakeholders and their teams to help them organize their program and bring clarity to both of our teams. There were no product design touch points as part of this design process.
I designed and facilitated nine workshop activities over four weeks with eighteen participants in fifteen working sessions, totaling twenty-four hours of meeting time to set the foundation for our teams working on the new program.
The Lean UX Canvas, created by author Jeff Gothelf, is a facilitation tool for discussing and documenting outcomes and initial hypotheses to understand the “why” behind the work to be done.
I facilitated this activity to:
Continuing from Lean UX Canvas outcomes, we took a deeper dive into brainstorming critical program outcomes, data sources, and how / when to measure indicators.
Nine critical program outcomes were identified in consideration of many important aspects including:
I love the structure you’re bringing to the user feedback as well as an approach to measure results. It’s going to be game changing.
I created this canvas to extend the Lean UX workshop discussion to document critical outcomes, data sources, how the outcome can be measured, and at what intervals.
The first research framing session documented what we think we know, want to know, and list all service users, actors, and stakeholders.
The second research framing session covered service / organization objectives, service context and promise, and the most important results to stakeholders.
Meeting as a group, we worked through two research framing activities modeled after Service Design Tools. These workshops were used to define the service’s objectives, context, and goals while helping to understand, prepare, and plan for research opportunities.
In these workshops and discussions, everyone was empowered to:
The new program serves the org’s most vulnerable clients with long term recovery needs. Through extended criteria, the program serves clients potentially missed before.
Stakeholders identified four critical areas of results that were important to them as they launched their new service: Clients, Workforce, Stakeholders, and Program.
As part of assigned pre-work, participants created their own boards documenting the traits for seven different personas. The boards were combined and what they think they already knew about the personas was discussed as a group. As a new person, this was helpful to me and prepared me for design research to create qualitative personas.
Each persona summarizes user behaviors, tasks, goals, pain points, and how we can serve them to build shared team understanding.
Each persona summarizes user behaviors, tasks, goals, pain points, and how we can serve them to build shared team understanding.
The user interview discussion guide included questions geared towards learning about their role, technology and tools, product experience, workflows, and future visioning.
Initial actor personas were co-created to quickly discuss key roles. Since these are purely assumption based, they must be challenged and evolve as part of a future ongoing user research plan. Afterwards, I conducted user interviews to create qualitative personas.
Additionally, the preliminary workshop was helpful to me for learning about each role and how the stakeholders and team perceive them before beginning a research plan.
After the preliminary workshop, I started incorporating user research into the roadmap as part of the service touchpoints. Taking a design approach rooted in research, I created and conducted a series of activities to learn more about our users and business problems to solve for outcomes.
I used Dovetail to code user interview transcriptions and assign them tags for quick reference, consolidation, and sharing with stakeholders.
After user interviews and coding research insights, I created an empathy map for the team as a communication tool to build compassion for the persona.
I am impressed with your workshop today. You did a great job. You were very professional and inclusive. I am confident in your ability to come up with an additional feature that will work for everyone. Looking forward to your finished work.
Your workshop facilitation was excellent.
Since everyone is so busy, I created a series of field postcards based on user research as a way to quickly communicate to our development and program teams high-level user feedback. This artifact is helpful alongside in-depth qualitative personas.
As part of designing a new product feature and related service, I created a Crazy Eights activity as a way for users to share what would be most helpful to them in the system.
Rose, Thorn, Bud was designed to uncover and discuss pain points, likes, and opportunities in the current existing solution so the team could discuss any overlaps and considerations for the new program.
This easy to understand activity was adapted from Luma Institute.
The Design Criteria Canvas was a helpful activity for everyone’s voice to be heard about product features and then organizing them into musts, shoulds, coulds, and won’ts. Afterwards, I collaborated with the product manager on prioritization for stories. Through this activity we gained further clarity of the immediate work to be done.
Using the Design Criteria Canvas, we documented an initial design strategy by listing what the design must, should, could, and won’t have to prioritize design criteria for the initial service offering.
I love this process that you are working through with all of us.
In a realtime series of workshop sessions, I facilitated and created a service blueprint of the previous state of the new service. For each pain point I captured notes in Lucidchart.
It was important to examine and discuss pain points and lessons learned from the 2018 version of the program with our business stakeholders and subject matter experts.
The overall process of the program takes place starting with the disaster event date plus 8–12 months. This service blueprint details the caseworker journey and steps they work through for assisting a client with their recovery as part of the program.
Way to be a trailblazer in this field for our organization. I love how rich and information dense the blueprint is while at the same time being easy for almost anyone to get a holistic and especially shared understanding.
This Ecosystem Map was helpful for everyone to visualize all of the entities inside and outside of the organization contributing to the service.
In a vast ecosystem, seven primary personas play unique roles to help clients as part of the new program’s processes.
The ecosystem map shows value exchanges between different entities both in and outside of the organization. This visualization displays primary roles and entities that influence key actors and the broader service environment.
The information gathered was based on a discontinued version of the program in 2018.
With many paths to recovery, this journey map visualizes one path of financial assistance recovery after a major disaster like a hurricane.
To get a clear understanding of the client experience, I met with our care team and subject matter experts to map the general client’s journey of receiving another form of assistance similar to the new program we were designing. The process for this included gathering insight from client research transcripts and speaking to workers interacting with clients as part of their recovery.
The printed journey map was a great addition to the product booth.
This journey map was professionally printed and displayed at the development team’s Salesforce product booth at the organization’s annual Information Technology Expo in August 2022. This display, in addition to kiosk screens I made for our product demo (below), set the scene as a human-centered design team during our product manager’s presentation to the organization’s CEO.
I created an interactive kiosk using Microsoft PowerPoint for the product booth on display at an IT event. Illustrations were provided.