I'm a product designer and technologist.
I've spent 10 years designing for emerging technologies. Most recently, my domain area has been in VR/AR and data visualization.

I’ve had plenty of practice uncovering unknowns, asking hard questions, and balancing scrappy progress with thorough testing.

While technology is always an inspiration, as a designer I'm often the advocate of the human side of the experience. Long-term adoption is driven by context and purpose, whether in work, daily tasks, or self-expression.

I'm based in the SF Bay area.

What is your design process?

Here are some more words about how I approach working on teams.

Where do people get stuck? What details bring joy and understanding? Where is the technology going? What are ideas that have been on the backburner? What are our own biases in being technology builders?
Find the right questions to ask, and the solution will follow.

Make + Communicate + Iterate
User flow? Personas? Prototype? Presentation? Play test? Create a space to think about the problem and create artifacts that facilitate team feedback. When dealing with unknown complexity or new technologies, breaking up the problem scope into manageable chunks gives a framework to track progress.

Is there a simpler way to approach a problem? Can a complex feature be untangled into smaller addressable parts? Do we really need this feature? What is the point of view of the user? The small ways to simplify leads to larger overall improvements and lets the core concepts shine.

Bridge Cultural Divides
Designing for AR/VR has always required merging expertise from people who build technology platforms and hardware, and people who create content, stories, and tools. As the technology matures into applications for different industries, building understanding between technologists and people from science, manufacturing, construction, education, medicine is a priority. I've worked with a range of different people and teams, and found that bringing together different perspectives leads to a stronger product.

Momentum = Speed X Trust
I’ve found this magic on more than one team, where once everyone gets comfortable working together, work can happen very quickly because an idea can be bounced around among team members and improved. User experience is not simply designed, it is a collaboration between everyone working on a project to take action on improvements and innovations. Momentum means making decisions from trying prototypes instead of debating in meetings. Momentum means empowering each other to try out an idea instead of just talking about it. Some teams already have this culture, other teams have to uncover it. I’ve found that the greatest contribution I can make as an individual is for my personal design process to build toward a culture of momentum.