DESIGN BY FIRE
MEET PARTNERS WHERE THEY ARE
My business partners came to me and the product designer with a problem statement. We helped them refine it the problem statement. Then we cowrote the user needs. This process helped the stakeholders see how customer-centricity and problem solving go hand in hand.
SERVICE BLUEPRINT
I developed a service blueprint with our stakeholders and verified it with the employees who respond to regulator requests. We discovered that they took eight manual steps to assemble documents the regulator requested. They accessed several systems and depended on other employees to fill in the gaps. This process made it difficult to gage if they'd gathered a complete and accurate loan history.
DOCUMENT USER EXPERIENCE
The product designer took on the painstaking task of documenting the systems that an Ops Analyst accessed to compile a loan credit file. She discovered that the analyst got data out of eight systems, everything from a mainframe to a SharePoint site. Her work helped executives gain empathy for the employees and gave them a clear understanding of why it takes so long to assemble a complete set of documents.
Rita the Regulator
I led the creation of personas for the key players in the process. I knew it was crucial to build out a persona for the regulator because they were the customers. Fortunately, a team member was a former regulator. He helped us get into that headspace. We determined that a regulator's ultimate goal is to protect the public from flawed banking practices. They needed to ensure that our practices were sound and transparent, helping the customer and the bank.
Use Case & Success Measures
Owen the Ops Analyst
Owen assembled the loan files. We put a name to the face and articulated his challenges and goals. Again, being able to share Owen's plight with executives helped build empathy and the desire to help.
Use Case & Success Measures
We Didn't Start the Fire
Somewhere near the end of the discovery process we learned that regulators expected us to deliver a technical solution roadmap. We stopped everything to engage with the tech team and the business stakeholders to create the document.
I went so far as to find a good remediation plan template via Google and drafting it.
Though tech should have been involved since the beginning, they consumed the research readily and could immediately identify business requirements.
INFLUENCE
We don't have a design yet but we are in the plan. User research and product design are built into each component of the remediation plan.
I was lucky this time. I was brought in at the beginning and had the opportunity to influence the outcome all the way along the journey.