Hi, I’m Christy.

I’m a Product Designer based out of Denver, Colorado.

My background in psychology, education, and design fuels my passion for solving complex problems. I love working collaboratively with diverse teams to create intuitive solutions that address real-world challenges.

designing for impact

Based on my extensive research, I realized efficiency problems could be addressed both by suggesting UI improvements to the UPC List Builder program itself and by making changes to the overall offer build process. I structured my proposals as “now,” “next,” and “later” to provide immediate, mid-term, and long term solutions

now: quick fix recommendations

I made 7 recommendations to immediately address key concerns and improve efficiency. Recommendations centered around:

  • more efficient data clean up

  • increased user control

  • more efficient user flow

All 7 of my recommendations were put on the road map
with 4 already in development at time of my departure

These recommendations were based on Nielsen Norman 10 usability heuristics as well as pain points revealed from usability tests.

I organized findings from my research using sticky notes on a miro board. After combining stickies for issues that showed up on both lists, I plotted them on a chart to look for high impact, low effort issues that I could address in my quick fix recommendations.

next: internal tool redesign

At the beginning of the summer, a new internal tool for data validation was launched.

After countless SME interviews with product managers, workflow analysts, and department directors, I discovered that a new backend pipeline could be created to direct all data clean up to this new tool, rather it being done manually in UPC LB.

This new backend system made it possible to create a re-design that did not need to handle all of the data clean up. The simplified UI is a single screen (see prototype in next section), which makes it possible to integrate it into the main offer build tool.

sketch and mock up of redesigned multi-screen UPC LB

break through sketch for single screen flow

I had a break through sketching one morning. Using some patterns my manager had presented in one of our design reviews, I had an idea for a single screen flow. Based on this sketch and using components from my multi-screen flow I put together an initial hi-fi mockup.

I sought feedback from my team and our UX writer. I incorporated suggestions around architecture, flow, content, and useful components from Pando.

Once the mock up was refined, I began building the prototype. I worked with our UX research director to put together a script for a usability test and began recruiting internal users.

simplified redesigned system blueprint

If implemented, this redesign would lead to a
60% efficiency gain resulting in over $300,000 saved annually

My initial sketches envisioned UPC LB remaining as its own program with a multi-screen flow. These patterns were heavily influenced by designs my team mates presented during our regular design critiques. Due to a limited timeline, I moved directly from low-fi sketches to hi-fi mock ups so that I could have extra time learning and working with Ibotta’s design system, Pando.

Even as I worked on these mockups, I continued to sketch. I realized if it were possible to get the suggsestor flow into a single screen, it could be integrated into the main offer build program. This would represent another huge efficiency gain as data could easily sync rather than needing to be imported and exported between programs.

later: patterns to be adopted into design system

Partway through the summer, business goals around growth led to a decision to overhaul all of the internal tools in the offer creation process. The patterns and backend data flow I proposed will be adopted into the development of the new tools.