Alison R Martin,
Product Design Leader
Why me?
Do you need a designer who’s helped define entire product directions? Who can translate messy, abstract goals into clear workflows and usable, trusted AI features?
​
Do you need someone who can partner with engineering and founders, influence the roadmap, and build early trust in both the product and the process as you scale through growth stage?
​
Do you want a designer who’s led research initiatives, brought design into the room early, and created calm, thoughtful systems in fast-moving, complex environments? I've helped shape a fast-paced AI startup and brought efficiency and speed to larger, methodical teams.
​
I’ve been the sole designer at a Series B AI serving enterprises, working across agentic workflows, chat interfaces, knowledge management, embeddable assistants, and more. I’ve set up scalable design rituals.
​
I’m comfortable working in the unknown. Including rapidly iterating, refining direction through signal, and adapting process to the shape of the problem. I lead with strong product instincts, grounded in both market context and user reality.
I’ve designed and led end-to-end research initiatives, synthesized insights from both qualitative and quantitative data, and created “be your customer” environments when direct access wasn’t possible. Whether I'm working from rich feedback or abstracted signals, I know how to design with clarity and momentum.
​
I’m looking for my next challenge: a Principal Product Design role at an AI startup that needs a strong design voice at the table, and is ready to build something ambitious, valuable, and human centered.
Read about my process
Understand the problem
Written by AM, not AI
Concentrate on solving the right problem.
I do not jump to implementing a solution. That's how costly misdirection leads to long-term user pain. ​
​
Instead, I dig in to the struggle. Ask open-ended questions. Learn users habits, how they spend their time and why, clever work arounds to technical limitations, their goals, concerns, and motivations. I uncover and quantify hidden costs associated with using the product.
I ask the right questions so we can solve the right problem.
​
For example, I identified affiliate marketing users were struggling with intellectual property theft. Spiking ad costs helped us quantify the problem and identify our role in it. The team had previously jumped to solutions that targeted the wrong root cause. Once we moved away from personal assumptions, we were able to save our customers tens of thousands of dollars and build a more robust industry-leading product.
​
The cost was quantifiable, the increase in our product value was tangible, and users felt heard.
What else informs good problem definition?
The best designers create harmony between the users, the business, the design, and the functional product. We prioritize:
​
Improving backend infrastructure.
Building value for the user and organization.
Filling gaps in the product.
Detangling complex puzzles.
Designing with intention.
Iterating hand-in-hand with users.
​
My teammates call it my "strong product intuition," but it's hard-earned, constantly tested, and sharpened by ongoing education.
Explore the possibilities
Good design doesn't jump from research to the perfect solution.
​
I analyze the data.
I consider the broader user flow.
I document what already exists.
I write How Might We statements.
I sketch a wide variety of potential solutions.
I collaborate with teammates - good ideas can come from anyone!
I articulate ideas using wireframes.
I validate a direction using rapid prototyping.
​
Only then do I refine the designs into clean, polished high-fidelity visuals through iteration and validation.
Finalize & Deliver
Delivered not "done"
The best products are never finished.​
​
Something else can always be done to improve, add, or simplify a user's experience. I scope according to resources and timelines, working closely with product managers and engineers to define a reasonable and viable v0. My favorite teams operate with zero ego but celebrate contribution, successes, lessons learned, and teamwork.
​
​
Once usability tests are complete and designs have passed rigorous critiques, it's time for delivery.
Proper documentation
Throughout my career, I have treated engineers as partners and personal "users." I continuously iterate on my documentation and delivery.
​
From organized and well-labeled Figma files to detailed Jira tickets, I ensure my engineers find my designs straightforward to navigate.