User driven functionality, experience design planning, team leadership and process design.
Defining and designing UX/VX architecture for applications, mobile and desktop products.

For a while (10 years) I led IF/THEN, a design studio I co-founded in Seattle. After serving as Creative Director for Deloitte Digital's Seattle office, I joined Microsoft as Design Director for Maps and People teams, and headed the Communications and People family of products as Creative Director. Following this, I led the Mixed Reality Studio Avatars Creative team, UX/VX/Art, expanding identity representation, driving connections between people, work and social experiences in Mixed Reality and traditional contexts. 

Currently I lead the Seattle UX/UI team at Sonos as the Senior Design UX Manager.


Print Regional Annual
Communication Arts
Seattle Show
Regional Emmy

The cost of "Easy". Or; is there such a thing as too simple?

Is the drive to simplicity making us stupid? Are we over-preaching the gospel of "easy" with all the gurus and specialists advocating and requiring that systems should be simple and idiot-proof?

How far should we really push it? Should a fighter jet's controls be simple? Should it have just an ignition key, a fly and shoot button? Of course, some things you want Kim Kardashian using, like an iPhone, should only have one big shiny button.

On the other hand, if your device (fighter jet) can cause an international incident, maybe adding a couple of complexity layers may not be such a bad idea after all. Then again, an iPhone is just as likely to cause an  international incident... Ultimately it’s about perspective, I suspect.

Is the drive to simplification causing us to automate ourselves to the degree of removing the ability to analyze the situation + decide the right course of action?

Occam's Razor states that all things being equal, the simplest solution is the right solution. This shouldn't be looked at as a license to dumb down, it's really an editing tool that, ideally, should drive clarity.

In the end it's all about analysis vs categorization. And in the case of categorization, we let the machines we built make the decisions we need in order to simplify our life. By having a tool take over the decision process required for categorization, we are removing the power and ability to analyze and determine actions.

Take driving for example.

The problem with driving is that we become conditioned, we develop muscle memory and we act instinctively. Not all bad, when you see brake lights ahead and act reflexively in order to avoid that expensive deductible for bumper and airbag replacement.

However, if the Google driverless car becomes reality, and we don't have to think about it anymore, should the “oh shit” moment occur, you will become paste when that “Powered by Google” driverless semi truck smashes your “Microsoft Enabled“ Ford Escort.

What it should come down to is this: when your users habitually engage the cruise control on your system, it's time to complicate matters a bit and re-force analysis of the situation. It is good to occasionally force reflection and encourage analysis.

I don’t know about you but when my phone dies on me, I know I’d appreciate a handy alternative that I hope and pray I haven’t forgot how to use...