Stop making user flows, do this instead
ฝัง
- เผยแพร่เมื่อ 3 ต.ค. 2024
- User flows and journey maps can be a useful tool when designing a product. However, there is one technique that can be more useful, object oriented user experience design. Let's talk about how it works, what it is, and how you can use it in your work.
More reading on OOUX:
uxdesign.cc/an...
alistapart.com...
Subscribe to my channel: bit.ly/3ltauIc
Learn more about Alloy: bit.ly/3Pt9Ok0
Founder’s Logs: bit.ly/3sNurOh
About Robert
I’m make videos about my work as a product designer and aspiring entrepreneur. Follow along with my journey to revolutionize healthcare.
#startup #design #ux
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. :)
Sruggling to get my head around how this applies to what I'm working on right now, but convinced it could be beneficial. Time to dig into the articles!
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!
This changed the way i look at UX flowcharts & Journey maps, Thank you for this!
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.
Hey JE! You're definitely right! There are a lot of techniques and methods out there. This is another one but you should stick to what works for you. I think that's one of the best parts of UX is that we can always evaluate techniques for our practice/users/businesses.
@@rbrtflyd Totally Understand, its just hard to keep up sometimes. I too believe this process needs to be a product life cycle relationship (with dev) I have a background in dev so its been quite easy for me to communicate and work along with dev teams. (Wont use the phrase... hand off) lol
That is a totally valid thing to feel. Keeping up is super tough. Particularly when every wacko with a TH-cam channel tells you what to do. If you've got techniques that are proving successful for you, then I say keep on keeping on!
I feel you on the idea of hand off. That would be another excellent topic to make a video about :)
And also your background as a dev gives you a super power as a UXer.
Ah Yes, New Text Layer
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.
I really want to get this but it isn't happening. Maybe I need to reverse engineer it.
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.
Task based UIs is what you're talking about, use cases with intent. This isn't OO, i think you're mixing things up.
Very interesting video, thanks ! I just discovered you and followed you 😎
What is your tool to "design/work" in this video ? Thanks in advance !
Hi Sonia, thank you for the kind words and support! I’m using FigJam from Figma in this video. It is a collaborative white-boarding tool.
@@rbrtflydHi 😄 You’re welcome ! And thank you for FigJam, I didn’t know it, it looks great !
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? :)
Hi Sophia, I'm not here to steal anyone's thunder. Please make a better video and tell the world all about the magic of OOUX! I don't remember how I discovered your original articles but I realized I'd been practicing something similar for a few years so your articles gave me a lot more confidence in it. I almost certainly have gotten some things wrong here so I'm always looking to improve my knowledge. I've seen yours and Joe's courses and content about it so I will have to check that out when I have the chance!
@@rbrtflyd haha OMG you are not stealing any thunder! I am so thankful you made this! I hope to see you in the Udemy course and am excited to know what you think. 💙💛❤💚
Looks similar to use cases, wouldn't it be a better representation switch to use cases?
Hey Reginaldo! Sorry for missing this. I may not be familiar with what you're defining as "use cases" but in my experience this would be in addition to using a system to understand the "use case" behind the feature. This is a more granular approach to flows in my opinion.
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
Hi Jasmine! Glad you found a lot of value in the video! Here are a few additional resources that you may find helpful:
www.ooux.com/
alistapart.com/article/ooux-a-foundation-for-interaction-design/
uxdesign.cc/an-introduction-to-object-oriented-ux-and-how-to-do-it-829bf6b248a1
Let me know if you have other questions!
Jasmine, WELCOME TO THE WORLD OF OOUX!!!
this is a comment \\
This is quite interesting. I can see how devs can work with 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?
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.
What Tasks the user performs on what? That’s why objects always come first. Objects first, and then what tasks you do to them
What software are you using to make that flowchart?
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 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.
Interesting.
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?
Hey Josh! Thanks for watching and for your question/input!
I see linear flows and OOUX as two sides of the same coin. One may be better suited depending on what kind of problem you are trying to solve and/or which stage in the development cycle you're at. I've found myself making much higher level user flows and then doing the nitty gritty details in OOUX which just works for my brain a bit better. However, design processes are just processes, so if you find a way that works for you, then more power to you!
New text layer 🧐
😅
Hi Robert, thanks a lot for this Tutorial! can i ask what software you use for this charts?
Hey Atilla! I’m using FigJam in this video!
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? :)
Hey there! I didn't explicitly follow up on this video, however, I'd be more than happy to make an updated "My design process in 2024" type video if you're interested!
@@rbrtflyd oh i see! Im currently learing ooux and I struggle to find any good information on how to proceed after the Steps you have showed in this video!
@@viktorhilden266 I get it! "What do I do after?" is definitely a fair question to ask when doing OOUX. I'll make a video talking about my process related to this soon!
What's the app used to create these flows?
I used FigJam!
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.
Why am I watching this thinking about Redux lol
Types
Actions
Thunks lol
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.
Glad you enjoyed the video, John! Agreed that it's not super intuitive but as I continue to use it I begin to break down problems much more easily by the thing rather than the function which I think really helps.
The tool is FigJam, from Figma. Highly recommend!
I don't like it, and I’m not convinced. Sorry, but I like experiences to be linear.
That's totally fine! It won't be for everyone and not every problem needs it! Do what works for you and your process!
sorry, but not every experience can be constrained to a linear framework