Work /
Scroll down for project info.
The first rule of consulting is: you do not talk about consulting.
As a designer this means NDAs and not keeping or showing past work, which makes for a challenging portfolio (or an oxymoron).
Turning it into a design challenge, I'm exploring ways to give you a peak into my experience. Right now that looks like mini case studies, from memory, with emphasis on process and learnings over clients and products.
This stands out as my first really complex fourtune 500 project.
Solution design for a responsive web application that brought multiple users and processes into one place. The app included multiple roles and permissions with unique views, integrations, and a workflow to support analysis, planning, review, and execution of promotions.
Through discovery I gained insight into the current end-to-end flow and user experience. In synthesis, two themes emerged to guide design - visibility and flexibility.
Sarting from the Home page, the dashboard was deisgned to provide immediate visibility into workflow and key metrics, while highlighting any critical information or action items. ForMoving into the next step of the user journey, the dashboard provided quick access to click through to those details and common searches. The final stage of review and planning included the use of flexible filters, a customizable table layout, and live calculation of key metrics.
Filters
- Visibility of system status
- Recognition rather than recall
- Flexibility & efficiency of use
Table Settings
- User control & freedom
- Flexibility & efficiency of use
Tags
- Match between system & real world
- User control & freedom
- Flexibility & efficiency of use
There may not be a "right" solution
+ Sometimes the solution is to give the user freedom to design it
I wanted to design an information architecture that met all the needs and solved all the problems. After multiple not-quite-right solutions, we looked at alternatives and concept tested. In the end, it was a less defined IA with highly flexible Tags that delighted.
This is were I started to get more involved in design strategy and Ops, including style guides, design systems, and scalable UI design.
Responsive re-design on a web application for small business owners and employees. The major constraint being the upcoming launch date.
The biggest pain-point for development was the design of a stepper, which was used in multiple flows. The original design had unique hi-fi mocks and specs for each variant ~ 18, which would require hard-coding of multiple div classes. With the re-design I reduced coding to 1 div class.
Stepper Variables:
Number of steps (4-6 currently)
Label length (varied by flow and language)
Viewports (768, 1024, 1440, 1680)
After the successful responsive re-design I was assigned global design strategy. With products already in development, I audited each, documented styles, and created a backlog that prioritized i. Accessibility ii. Inconsistencies iii. Enhancements.
Pros and Cons of Sketch and PDF style guides vs code
Accessibility is a lot more than colour
While constraints did not allow for a live code style guide, it was my recommendation for next steps. Not only will it be easier to maintain over time, they make it possible to see how styles and interactions will actually be rendered - EG. a button hover state that looked good on paper (in Sketch with side by side), but when coded revealed that the shade difference was too subtle to detect. In subsequent projects I also discovered opportunities to leverage coded style guides for multi-lingual design, VQA, and accessibility.
"Schumacher Clinical Partners is one of the nation’s largest and fastest-growing healthcare resources, partnering with more than 7,500 world class providers to help treat more than 8 million patients annually."
This client was truly research driven and agile, which was a great opportunity. Partnering with them, I led design strategy on 3 products, overseeing research, ux/ui design, and service design. The below focuses on the SCP app which I worked on across multiple releases.
Working closely with the PdM I led discovery sprints, integrated assumption testing, and introduced data driven decision making. Initial research validated the user pain points, with communication (general) being priority for the first release. Subsequent releases then addressed tasked based communication such as scheduling and onboarding.
The MVP was released in 6 weeks with 86% Adoption (KPIs Downloads, Weekly Active Users, Messages Exchanged).
Service Blueprints are powerful
The art of data driven design
The service blueprint did it all - captured the big picture, created alignment on what "slice" to solve for, informed UX flows and wireframes, and was the foundation of the product roadmap. Of course, this went hand in hand with the research strategy, which required different methods throughout.