Info

Info

My work has helped companies fulfill brand promises, innovate and get closer to achieving their mission. I have over a dozen years of experience making digital products for notable brands. As the iPhone and the App Store emerged and became more integrated into our lives I started working for a consultancy in Seattle called Übermind who built several first generation mobile products for companies like Target, Showtime and Nike, among others.

Developers at Übermind worked on the original version of the Apple Store app, that allowed anyone to walk into an Apple Store and purchase products in a frictionless way, eliminating the need for a point of sale. That kind of transformative, focused utility made a big impression on me and is an good example of how technology can improve our lives, remove barriers and provide seamless experiences.

Originally I studied photography. After college in Philadelphia I sold most of my belongings and moved to the mountains in Colorado where I worked as a ski patroller mitigating avalanche hazard.

What I do today as a designer is similar to the photographic process. You have an idea, choose a camera and lens, find your subject, wait for the right lighting, set your ISO, exposure and depth of field, compose the image through the frame and finally you take the shot. Then there’s a fair amount of post production, not to mention printing process. In the end there are many steps to getting to a final image. You can put many images together to make up your story or photo essay. Product design is related in many ways—you end up with a series of images and an experience.

Übermind was purchased by Deloitte in 2012 and the client work changed. Starbucks was one of the first retailers to invest in technology and mobile at the time. They had an open API actually and a very lucrative mobile payments system. We redesigned the Android app from the ground up in 8 months. During my time there we also worked on mobile ordering and redesigned the Pay and Manage flow on iOS.

Product design is related in many ways—you end up with a series of images and an experience.

After a couple years there I was recruited by Google to work on Cloud UX. Google has a SaaS offering similar to Amazon Web Services. Snapchat and Spotify run on GCP. Cloud was technically challenging for many reasons. Technical infrastructure was new to me. I don't have a computer science degree. The engineering manager who ran the team I worked with had a PhD in Nuclear Physics.

We were mostly focused on the alerting and monitoring scenario. In DevOps, there's usually someone on call, say an SRE (site reliability engineer) or cloud engineer who is responsible any time there's an outage. If PayPal goes down for 30 seconds it costs the company tens of thousands of dollars, causes unnecessary pain for users and hurts their brand. Admins and CEOs also need insight into the KPIs and metrics impacting their environment in the cloud. While at Google I was also on the SignalsUX team, based in NYC, that was responsible for all the data visualizations and charting for Cloud.

Having had experience working in an agency, being in house at Starbucks and getting after it at a large transformative technology company like Google I came to the Bay Area for more startup experience and some new challenges. I'm still interested in the digital craft of product design and prototyping and getting at the root of the problem, but I also see the benefit of empowering other team members with the right tools, methodologies and approaches to help them solve their problems or think about creating their own customer experiences.

 

Resume requires password. Request access

 
 

Early to late stage design

Through collaboration, common understanding and shared values I’ve worked with stakeholders, writers, researchers and other designers to make progress during all stages of the product development lifecycle. I realize I don't have all the answers. Understanding the problem space by conducting research, doing a competitive analysis and the necessary information and requirements gathering are high priority for any new initiative. Asking why is as important as attempting to answer a product question with a how.

When there’s an understanding of what the hypothesis is and what we’re building to test, call it MVP or otherwise, low fidelity drawings and whiteboarding can begin.

Process makes perfect

Companies have their different environments, team dynamics and their way of doing things. There are some commonalities when new work kicks off. After looking at previous research or conducting my own and initial conversations with stakeholders, PMs and designers, we can start the design process, which honestly is more requirements gathering and understanding what problem we're solving. It's important to be flexible and keep an open mind.

Discussing use cases, users journeys and the current way users solve the problem usually come next. I'll ask questions to get a sense of the success metrics, business goals and timeline. When there’s an understanding of what the hypothesis is and what we’re building to test, call it MVP or otherwise, low fidelity drawings and whiteboarding usually begin. Drawing is a great communication tool and relatively inexpensive. This is great because drawings can also be easily discarded. Drawing is really a form of thinking.

Once ideas have been socialized and vetted with stakeholders, I will start with mid-fidelity designs. The higher the fidelity the better chances you have for communicating your vision. It doesn’t have to be perfect to get feedback or start validating assumptions with users and there's no reason to wait.

Products with excellence, have focused utility, are effortless to use and fit into someone's workflow increase your chances of higher customer satisfaction, better retention and reviews.

For bigger problems I've conducted stakeholder interviews or facilitated workshops and sprints with cross functional partners. Complicated problems usually benefit from the tribal knowledge of the group and divergent concepts can inform great experiments from a combination of focused work alone then sharing with the group.

The implementation and execution phases of software development can take a some legwork and parts can get overlooked. This is especially true if you’re building out new components. Focusing on the details and putting in the time to implement, leaving nothing to chance builds trust with users. Products with excellence, have focused utility and are effortless to use increase your chances of customer satisfaction, can improve retention and lead to better reviews.

I pride myself on my adaptability, empathy, attention to detail and big picture thinking. I’m looking for an inclusive, diverse workplace that supports healthy discourse and differing opinions to call home.

Get more

Still have questions? Check out the Answers section for more context. Or you can download a Keynote presentation of my work and my background below.

 
  • Skills
  • Accessibility
  • Animation
  • Drawing
  • Layout
  • Typography
  • Color Theory
  • Visual Hierarchy
  • Gestalt Principles
  • Data Visualization
  • Digital Design
  • Product Design
  • Interaction Design
  • User Experience Design
  • Strategic Design
  • Design Advocacy
  • Systems Thinking
  • User Research
  • Prototyping
  • Workshop Facilitation
  • HTML/CSS
  • Tools
  • Figma
  • Sketch
  • Abstract
  • Principle
  • Framer
  • Adobe Creative Suite
  • Wacom Tablet
  • Canon 5D Kit