Stop making user flows, do this instead 

Hey ya'll, when I made this video, about a year and a half ago, I wasn't really sure what I was doing with OOUX. Sophia Prater, the originator of OOUX, now has an excellent course on Udemy with Joe Natoli (another UX legend) that I would highly, highly recommend anyone interested in this technique to do: www.udemy.com/course/oouxfundamentals I finished it just recently and have improved my process with OOUX ten-fold. I appreciate all of you watching and commenting. :)

The user flow is useful for opening the discussion about what tasks the user must perform. The object-orientedd design is useful to discuss how to perform the tasks. This is why is used by developers, because is more oriented for practical implementation, but not for project discussion.

This really helps me. In my projects, there is a page that varies depending on the time. This means that when users access the page at different times, the available actions and services we can offer are completely different. So, I need to create so many user flows to cover all the processes, but these flows are so complex and cannot intuitively show the problems. This chart can make the information clearer.

This changed the way i look at UX flowcharts & Journey maps, Thank you for this!

This is quite a bit different to how I teach object mapping! Under Section types you are kind of confounding attributes and values of types (I think). Glad this is working for you though! And thank you for linking my articles!

Thank you so much for summarising this. very helpful. I notice I have already been doing something similar but I didn't know there is a name for it. It is a very efficient method. it's like you see multiple flows together instead of one. Like it.

Your explanation of the problem is top tier. Interested in this product

Very interesting, reminds me of jobs to be done, you're trying to understand the outcome and the actions a user wants to perform before thinking of the linear flow.

Man...everyday someone is making up something new for ux.

I was a former developer and this is a mix between of Object Oriented development and remember the classic UML and Use Case scenarios? Everything, everywhere all at once :) so of course this will work. It’s just bringing different concepts together.

This is quite interesting. I can see how devs can work with this.

Thanks for this video bro

I have other UXer friends who talk about OOUX. From my understanding of OOP, what you're talking about in this video is extensibility, which is indeed a very important capability to emulate in UX. The other major principles from OOP don't seem to apply to UX per se (polymorphism, inheritance). There may very well be a way to truly import them into UX thinking, but it's a heavy lift. Prob worth continued research about.. but as well know the typical UXer customer is usually a so-called stakeholder (often proxied through the Product Owner). From my experience the kinds of design pattern and model work you're showing here are beyond the understanding of folks outside of UX. IOW - this is prob years ahead of its time. :)

I'm new to this UX thing and perhaps I'm taking my CS background for granted but this should be very useful for people who aren't introduced to OOP concepts. It's perhaps too many apps nowadays feel just intuitive and simple yet functional when in the past it felt like software somewhat relied on the volume of available features to determine its worth Would it be bad design to have a starting point that allowed for both (linear flow/OOP "flow") if you find your users have relatively close to equal preference between the two?

What software are you using to make that flowchart?

Hi Robert, thanks a lot for this Tutorial! can i ask what software you use for this charts?

Looks similar to use cases, wouldn't it be a better representation switch to use cases?

I feel like this is the answer to many questions I've had to product planning, and I would like more information. Can you recommend resources to learn more about this

so, OOUX is basically UML chart simplified? this looks like I learn on object oriented development like; class Dog { string name; function bark(){} } in this case we have a dog that in this system has a name and as an action, it can bark. OOUX is something like this?

Interesting.

Object Oriented anything takes some adjustment in the way my mind processes things, not because it's especially difficult, but linear/flow thinking is so much more natural I feel like. The best way that I've been able to grasp it is to think of each node in a flow as an object, with its own properties and sub-functions. Kind of like a file tree in an operating system, where there's potential depth to each folder and sub-folder, with things nested underneath. Interesting to see you laying UX out this way! Also, what software are you using for this demonstration? It looks very slick.

Very interesting video, thanks ! I just discovered you and followed you 😎 What is your tool to "design/work" in this video ? Thanks in advance !

ahhhh you beat me to the ~!0 minute OOUX explainer. Thanks for sharing this Robert. How'd you find about OOUX and how are you learning more? :)

Hey! Obviously your knowledge is around the healthcare industry. I stumbled over your channel while I was looking for journey mapping videos. I am creating a software (not an app) In the healthcare industry(Australia). Still in early stages, graduating from an accelerator program end of this month. would you be interested to have a chat? Maybe we can do something

Hi, did you not continue this series or where can I find the next video? :)

What's the app used to create these flows?

New text layer 🧐

Task based UIs is what you're talking about, use cases with intent. This isn't OO, i think you're mixing things up.

Why am I watching this thinking about Redux lol Types Actions Thunks lol

Ah Yes, New Text Layer

Bro I never flow user journeys. It’s a major waste of time. It’s shallow and uninformed in almost every way. I always design back end to front end architectures. But designers hate the idea of learning that.

this is a comment \\

I don't like it, and I’m not convinced. Sorry, but I like experiences to be linear.