Hi, I'm Lia.
I'm a Product Designer who likes complicated problems.
I design products and experiences for complex environments where the challenge isn't always knowing what to build—it's understanding the problem well enough to build the right thing.My work sits at the intersection of research, product strategy, systems thinking, and interaction design. I like getting into messy problems, figuring out how people, processes, and systems actually work, and turning that complexity into experiences that feel clear and useful.
I've spent the last several years designing enterprise products at the intersection of people, data, and business operations, working closely with product managers, engineers, researchers, architects, and business stakeholders. I'm especially drawn to problems where there isn't an obvious answer—and where good design means helping a team figure out what the right question is in the first place.
How I Work
I start with the problem, not the interface.
I'm naturally curious, which is convenient because most of the problems I work on require a lot of questions. I use research, synthesis, and systems thinking to understand what's actually happening before jumping into solutions. Sometimes that means talking to users. Sometimes it means mapping a complicated workflow, untangling a domain, or digging into the assumptions behind a set of requirements.
I like making complicated things make sense.
Enterprise products rarely have one clean definition of the problem. Different teams have different goals, terminology, workflows, and ideas about what the product should do. I enjoy creating the frameworks, models, and shared language that help teams work through that complexity and move from "it depends" toward a clearer understanding of what they're actually trying to solve.
Design doesn't stop at the screen.
I see product design as more than creating interfaces. I work closely with cross-functional teams to shape direction, facilitate difficult conversations, evaluate tradeoffs, and connect user needs with business and technical realities. And then, of course, I still really like making things. I bring that thinking into the product through interaction design, prototyping, testing, and iteration.
A little more about me
Before becoming a product designer, I worked as a college adviser, helping students and families navigate the complicated world of college admissions and financial aid. I learned a lot about listening carefully, asking the right questions, explaining complicated things clearly, and figuring out where people get stuck—skills that have followed me into design.
I eventually went back to school for my Master of Human-Computer Interaction at Carnegie Mellon University, where I discovered that there was, in fact, a career built around being curious about how people interact with complicated things.
I also have a background in Philosophy-Neuroscience-Psychology, computer science, and English, which is probably why I'm equally happy thinking about a system, arguing about the wording of a button, or wondering why someone decided to organize an entire workflow that way.
When I'm not designing, I'm usually reading a book or five. I'm also prone to re-watching old seasons of the Real Housewives, and I will happily spend far too much time trying to keep my many houseplants alive.
