There is no intake form to work through. Reach me directly about a senior product design role, a product or website problem, or one critical page or flow that needs clearer thinking.
Need more context first? See the product, website, research, and front-end work behind the résumé.Reach me directly
Email is usually best for a job description, project link, screenshot, or a little background. Call when the situation is easier to explain out loud.
Send the context, the link, or the job description. A rough explanation is enough to start.
Phone
Call when the work is complicated, the situation is moving quickly, or you would rather talk than type.
What helps
A useful first message makes the situation concrete. It does not need to explain the entire company or predict the solution.
I would rather understand the real problem than read a polished description that leaves out the difficult parts.
What should people, the team, or the product be able to do when this is working?
Where do people hesitate, misunderstand, leave, repeat work, or take the wrong path?
What is already fixed, technically difficult, politically sensitive, regulated, or expensive to change?
Is this early thinking, an active build, a launch problem, a hiring need, or something that is already overdue?
Common reasons to reach out
These are the conversations that usually make sense. Each one links directly to email with a useful subject line.
Full-time role
Share the team, product, level of ownership, and why the role exists now.
Talk about a roleProduct or website
Send the product, page, audience, intended action, and what the current experience is failing to do.
Talk about the projectOne critical page or flow
Send the URL, what people should do, and the behavior or outcome that concerns you.
Send the page or flowWhat happens next