The Challenge

‍
This client was new to product design, agile methodologies, and design thinking. In addition to my work on various projects and products, I evangelized UX and design thinking and answered the many agile questions for those new to the process.

The Ask

‍
This gig was a very challenging role. Not only did I need to focus on solutions, but I also had to teach and mentor along the way.

The ask was simple; create a tool where caregivers (users) can access this healthcare system's 6,500 Tabluea dashboards. So, naturally, one thinks of an aggregation tool. However, the task quickly grows when dealing with a healthcare system established in the '70s with data spread across many teams and other organizations.

Evaluation and Feasibility

‍
As the UX Strategist for the project, my first step was to understand where we were. Not having a background in analytics or medical, I needed to understand the users to develop a solution. So I spent time interviewing stakeholders, which led me to understand the users who would benefit from this tool. I landed on producers (analysts, users who contribute to the app) and consumers (caregivers and leadership, users who view what's in the app).

I quickly realized we had a massive blocker to the app's success from the analyst's interviews. None of the analysts I interviewed had the same workflow. They weren't even similar workflows. They all had different data sources and locations where they saved their data. If they did perform QA, they had varying definitions of done.

Having a deep understanding of the producer persona and consulting with the backend dev team, I made a process recommendation to address the lack of governance.

The Process

‍
This research helped with setting the goals and scope of an MVP. Then, laying out the proposed app life cycle process, we aligned on what we can do in the short term versus what we hope to do in future states.

Because this client was going through a digital transformation, winning hearts and minds is part of the job. So I created a mid-fidelity prototype to get the team to see the big vision.

Using the prototype for user testing, we were able to get rapid feedback, make changes, and iterate. New to front-end development, our dev team created a coded prototype to test our EDW and cloud storage integration. This live prototype also helped us understand what we could feasibility pull off for a shared repo, a recommendation in the proposed governance process.

I created a dynamic model to move the team from an MVP mindset. It's a schematic of the app from a user interaction perspective. I like to use them when working with other designers and developers. We can all see the "shape" of the app, its states, implicit and explicit user actions,  and data location. I also use it to stay sprints ahead of the dev team. Noting all expected interactions, functionality, and what has been discussed and wire-framed.

Wrapping it up
With a solid UX strategy in place,  I created high-fidelity mockups and assets for the team to continue building in my absence. I left with a UX road map with detailed instructions and accompanying Jira tickets for the entire year.

‍

‍