PRODUCT CLARITY
Work with me to transform ambiguous ideas and difficult product problems into clear, distinctive directions worth pursuing.
Work with me to transform ambiguous ideas and difficult product problems into clear, distinctive directions worth pursuing.
From product strategy to interaction details to technical constraints, I can move between high-level decisions and hands-on design.
From rough ideas, I'll build distinctive, realistic prototypes that clarify the bet before you make it.
I've held dozens of research interviews and can help you structure conversations to help you learn rather than confirm.
Let's make your product feel distinctive without a rebrand (not my specialty). We'll focus on how it feels, how it communicates, behaves and interacts.
I'm available for scroped projects, sprints, on-demand consulting, or “fractional” design leadership.
My identity as a designer is the same as my identity as an individual. I’m ego free, down to earth, thrive on feedback and am interested in doing work that I can be proud of. People enjoy working with me because I make myself easy to work with and seek to make their work easier too. I work with empathy and a desire to understand. That means asking the questions that need to be asked, properly defining scope and aligning on deliverables that will yield a proper return on your investment.
I most recently led design at an AI Commerce startup. There I explored greenfield design problems with a strategic lens, ran user research and encouraged an environment of building to learn. Prior to that I was ⅓ of the design team at Play, a mobile & desktop design tool recognized with an Apple Design Award.
My career began as a software engineer for a small startup, where I bootstrapped machine learning models and built dashboards for visualizing large amounts of content. That background makes me a practical designer. I understand technical constraints, communicate well with engineers, and can prototype directly on-device.
The most important part of my design process is done up front before opening any tool. Properly defining the problems, goals and prior work is not an area to be afforded any wiggle room. I'll ask a lot of questions to soak in needed context and help set objectives that will actually move the needle.
Early in a project, I tend to focus on desiging to learn and collect signal. After letting initial concepts marinate, gathering feedback, and gauging reactions, I'll use what I've learned to push the concept forward.
Sometimes I'll challenge myself to think of software as a place, and ask: what sort of space do we want our customer to feel like they're in? When they leave, what do we want them to remember?