Ack! So many great thoughts! How to address them all?
First off, as anticipated, one of the most “controversial” aspects of this article, here and on Twitter, has been what I am calling this. From where I stand, as a UX/product designer that understands the basic principles of database programming, calling it OOUX makes the most sense. And this is just in lieu of calling it Real World Mental Model Thing-Based Design. OOUX is simply catchier.
Adam, you make so many very good points. Your best question is: “What is the goal of this article?” Ah! Goals. I like defining them for my products, but somehow didn’t communicate the goal of this manifesto. The main goal is not to make UX more approachable to developers. It’s not to steal bits of their vernacular to “slip it in.”
The goal of this article is to present a methodology that I truly believe helps teams builds better products and websites in a more sane way. It has helped me so much in my work. I am a more effective (and happier!) UXer designing in this way. So I want to share it. No other ulterior motives.
But the ripple effect of this process CAN BE a smoother communication b/w disciplines on a cross-functional team. When you take any activity (domain-modeling, entity-relationship-modeling, object mapping, content-modeling) and say, “Hey! Let’s do this thing together! Let’s get Discipline A involved in this thing that traditionally siloed in Discipline B!”, two things can happen. One scenario is that Discipline B feels their toes are being stepped on and shout, “get off my grass!” The other scenario is that Discipline B says, “Come on over! When we overlap, less gets lost in translation! Yay!” Let’s hope for that latter.
As far as actions and adjectives are concerned - OF COURSE we have to address these! But I think the nouns should be in the driver seat. Adjectives and verbs need a noun. But a noun can stand alone.
The process I describe above is an abbreviated version of my full process. One step that I didn’t get the chance to share: taking an inventory of CTAs based on each object. What flows will “spawn” from each of these objects? For “ingredient” can user: save, favorite, follow, or buy?
Getting into sounds, feel, emotional design is a whole other layer that OOUX does not address - and doesn’t attempt to! We already have the tools for that. :)