Align, co-create, and reduce rework with object-oriented UX (OOUX)

The best time to get super curious about all the unknowns is early on in a project. But all too often, we end up brushing complex business rules and information architecture aside and jumping into design too early. And when we avoid asking clients and stakeholders the tough questions, we end up with piles of rework.
In this talk, you’ll learn the basics of OOUX and how it can help teams achieve a shared understanding of scope, strategically structure content, and shine light on hidden complexity - reducing rework in the process.
Sophia Prater (she/her), UX designer and chief evangelist for object-oriented UX, Rewired ✅🚀
Sophia teaches her OOUX methodologies at conferences and through her Certification Program. She’s brought the complexity-untangling magic of OOUX to a variety of companies throughout her career. Sophia is also the host of the OOUX Happy Hour meetup and the OOUX Podcast.
Presented at Webflow's No-Code Conference 2021.
#NoCodeConf #NCC
----------
Get started with Webflow: wfl.io/2r7cVUW
Join the Webflow Community: webflow.com/community
webflow.com
/ webflow
/ webflow

[@NorthWriter]

Honestly, that simple animation of the page elements shifting into the object list/map was SUPER helpful in understanding this whole concept more thoroughly! We're just starting to use object mapping at the agency I design for, and I'm really excited to make it a solid part of our process!

[@thumandidelange]

This is great! I've been working with UX for a year, and definitely struggled with structuring my research findings in a way that helps screen design. This helped me so much, thanks 🎯

[@SioPao105]

I'm a convert, I feel like this would be a great addition to a JTBD framework

[@jpthedio]

This is really interesting. There's a similar diagram from Architecture called the Space Matrix. I can see ORCA being very helpful with mid-to-large-scale projects. 🙌

[@SharkClips703]

This really helps, I was just planning to create a demo site with related content.

[@zelenoye]

I am shocked this is not the norm. I am a designer from Russia, and we have a different school of thought (I am talking for every Russian designer, but a lot of professionals are working that way) - development ALWAYS starts with a ton of research and in-depth interview of business owner and people who work with customers AT LEAST for 3 hours. We want to know business goals, we want to know everything about the product and customers. No one is building anything until we understand what this is about. We record those interviews, transcribe it and use some of it in copy.

[@Pavel555]

The research stage was described in classic programming books ages ago (in “Code Complete”, 1993 by Steve McConnell, for example, or in “Object-Oriented Analysis and Design with Applications”, 1990 by Grady Booch). The school of thought of product design you mention was taken from there (I come from Russia too by the way) and doing research before designing UI screens or writing any code is a normal practice in every good company. Exceptions are small agencies or beginner UI/UX designers maybe.