Yes, this is a post about Mozilla, but you can generalize to any open-source software project. At every conference I hear the same refrain, “Why is design so hard in open source?” It’s so hard because *drumroll please* it’s not made a priority. None of the top decision-makers are designers. Period. The End. You can stop reading.

Without someone in the c-level or steering committee with a design background to speak on users’ behalf, Mozilla is missing out. Engineers and business people see entirely different challenges. Without all sides (technical needs, business needs, user needs), we have a giant blind spot.

Chief of Experience? Never heard of one.

If everyone jumped off the bridge, would you do it too? It’s true, there aren’t many tech companies, especially open-source ones that have a design representative at the executive level. Google, Microsoft, Opera, Facebook, Intel, Amazon and even Adobe lack it. There are some surprising companies that do. Oracle has a Chief Evangelist of User Experience. Flipboard has a Head of Design. Nokia and Yahoo have a Senior VP of Design. You might’ve heard of the most notable SVP of Design, Johnny Ive of Apple. You’ll note titles of this position haven’t settled down, not surprising given the short time the discipline has been around.

There’s an opportunity for Mozilla to be the first big open-source tech company to deeply bake design DNA into the process. Gary (CEO) has been exalting us to to produce a kick-ass product. UX and UR are a source of innovation. Further, prioritizing around user needs is essential to making an excellent product.

One bit I didn’t expect in my survey was that the Chief of Design is a well-established role in car companies. Tesla, BMW, Volvo… they all have one. It’s curious to me because car manufacturers are entrenched in technical, mechanical requirements as well. Seems as though they’ve figured out that it takes more than the feature list and specifications to sell cars to people.

Get to the point

  1. UX is an objective discipline, not something based on feelings about which shade of blue is prettier.
  2. It should be an organizational priority that blocks projects from launching in the same way the infrasec does.
  3. UX is vital part of every project. We shouldn’t DO a project unless a trained interaction designer can ensure user needs are met. Until UX is included from the very beginning, before requirements are written, it will be chasing after product and engineering.

So what do we DO?

  1. We need someone with an interaction design background at the c-level and/or steering committee.
  2. Hire UX at a sane number. The ratio in my group is 30:1. It should be around 4:1.
  3. Until we can do that, hire contractors to pick up the slack.

 

[Video: the ROI of User Experience]

[Post: We Tried to Warn You, Socializing UX into organizations]