UX thinking vs Product Thinking
I’ve been designing experiences for 10+ years, and I know I’m ready to level up in my career, not because of my skills, but because of my thinking. My brain thinks beyond one facet of the experience—I can’t help but think of things at a larger scale.
Unfortunately, some of my coworkers were impacted in a recent round of layoffs, and a project in UAT was given to me. Our business partners brought a concern with the design while it was in UAT, which is why the project was given back to product and UX.
The original problem:
Customers are complaining that they can not find their pharmacy locations via the address on the web homepage header. This web update was to add the pharmacy-only locations to the list on the store selector. In UAT, they found that some locations have so many pharmacy-only locations that they push down stores that they can actually select to shop.
Solutioning:
Some folks suggested we shorten the cards. Others suggested we add tabs for pharmacy only versus retail. There was also an idea to add a toggle or checkbox.
My thoughts:
Why would we add pharmacy-only locations to the “store selector” that is specific to retail only? If customers are anticipating the address in the header is for locating a store, why don’t we just take them to the store locator? How many people are complaining about this? Can’t we just merge the store locator with store selector functionality so all customers can be happy? Why do we even have a separate store selector and store locator?
What Sets Us Apart
People-First Approach
Everything we do is built around understanding your needs and helping you succeed—because when you thrive, so do we.
Long-Term Relationships
We’re not just here for the now. We love creating lasting relationships with our clients and growing with them over time.
Proven Process, Flexible Execution
We bring structure where it counts and adaptability where it matters. Our methods are clear, but always responsive.