Speaker 1: You tested it on Figma as well. You didn't test it in the wild. So ethnographies, one thing which you could do that would make your solution much more sound as well. We would want to shadow an actual swimmer and go through their journey end to end. Literally ask, can I be next to you on a boat? So we'll have another portfolio to review. And this time is by UXer from the Design Squad Discord community. Make sure to join it if you want to connect with like-minded individuals, people who want to get into UX, and generally get advice or share or help each other out because that's how you actually learn. And it's super important to stay connected, especially in the field which requires so much to enter. So it's a no-brainer, do join. Anyhow, immediately there is one thing, and I'm gonna call out, which is atypical to my reviews, is that visual layer, which I don't really touch much usually. But it feels like it was maybe a PowerPoint or a keynote presentation, and then a lot of those slides were actually entered here, and then the text seems to be added on top of that, or the text is a lot of mixed different format bits. So this is a small thing, of course. You could optimize it further. Another thing what I immediately called out is to be very careful using the actual stock imagery or doing very sparingly. So if you want to illustrate something like companionship, let's say, you could add this photo, of course. But make sure it's not just there all across the board, because there is a lot of information here. Add the content to illustrate the story or support the story, not the other way around. One thing I would be careful here is adding the lead next to UX researcher. Maybe just say that you did UX research and you actually project-led or project-managed it, or maybe you were product-managing it, you know, you wore that hat. Just say that as a discipline. Don't put, like, seniority to it, because it's a bit of a dichotomous to say that it's a conceptual project in a school and then you've been actually a lead, because a lead is an actual title in the industry. So just, you know, it's a small bit. And I guess you simulated a client who's a GPS maker, I presume, of software development for geolocations. You kind of, I guess, ran some opportunity discovery to understand where you could use it. And then you went into the very specific use case. Prevent accidents for open water swimmers. It's not too clear exactly how did you arrive at that from, you know, all the different opportunities and why did you decide that way. Would take you just one line to be very descriptive. There is lack of competition, maybe, or things of that nature. You could kind of guide me a bit more through your decision. One concern which you highlight is drowning. Third leading cause of accident that's faced in a worldwide. Immediately, it's a bit concerning if it's the right solution to me. And if perhaps you're linking yourself too much to the methods or to the channels or to the technology at hand. So you did some surveying to user research it. You find out that we go unsupervised, experienced swimmers can face anxiety. And then also a quote which is powerful to use. It's good to kind of showcase exactly what we mean by that, especially if you want to get that message across. Without looking into detail, there is almost like a very specific set of people who would use this or whatever solution you come up with. Evident on my wrist, let's say with endurance sports, I tend to invest heavily in tech to support my things because I need that. But you need to consider who are those people maybe to reflect this better. You could have used, and maybe this is a tip for everyone else, like a persona grid, defining that their tech aptitude, even income could drive it too, because not every runner or not every swimmer invest heavily in their gear. With a journey map, something to call out. Of course, I like that you included it. I feel like it should be richer and grander and it should have more steps because it's never that simple, especially in these cases. One thing what I noticed is that you're thinking touch points, emotions are not too reflective of the, let's say the safety. Like again, those variables, what would they consider? Is it their personal safety? Is that the other people are informed? Is it that, I don't know, their goals are completed? Is it time maybe they're spending in the water and that urgency is what makes them make poor decisions or something like that. So maybe it's decision-making too. Emotion could be replaced with that. Like you could literally say, instead of satisfied, neutral, or unsatisfied, it could be like feeling of safety. Getting deep into the psychology and the human needs. You did some competitive analysis. I like that you looked at the hardware because what played in my mind as I was introing into this case study was like, oh, why would you even go for a watch or a smartphone? Of course it's readily available, but you could also consider introducing a device. And you considered exactly what the features are like. And of course, every single thing has differently. Jumped immediately into ideas. Ah, like you could ideate a bit further. Instead of saying how might we reduce drowning with a phone or the smartwatch, you could ask how might we improve the actual user experience? The two are very different. One is solution-driven, one is user-driven. You need to pick which one. Like if it's UX, you kind of need to start with what do the users need. And it could be that your GPS and everything else you had in mind, like using smartphone and things like that, it's not gonna stick anymore. But you should be fine with that. You could challenge the business, the stakeholder of it, and say, hey, your solution should look slightly different. But your ideation should come of how might we improve the actual user safety, the user experience? How might we indicate to them that these are the safe zones? Of course, you could default back into the smartphone and represent it there. But you need to think a bit more holistically before you just jump into it and just churn these mock-ups or things of that nature. And looking at the actual features, you covered a lot of that. The only thing what I think what you restricted to yourself, again, is the channel that you're gonna stick with it and nothing else is gonna matter. And I'm gonna give you a small example, but it's sort of related that then my wife is running somewhere in, let's say, woods or parks. She likes to go on WhatsApp and share her location life for at least an hour. She preventatively turns it on. And then I can, on WhatsApp, just say, okay, how far is she from home? Let's say to do lunch or something. Along those lines, I can check it on my WhatsApp app and I can check exactly where she is. That's one of the features which combines two apps on two different phones, one single product. It could be multiple different products like that. It could be smartwatch. It could be. But this kind of tells you that holistically how you could do that. It doesn't have to be just you and SOS service. If you are reflected holistically and you understand how people do this, your solutions are gonna be much more meaningful to them. You tested it on Figma as well. You didn't test it in the wild. So ethnographies, one thing which you could do that would make your solution much more sound as well. And kind of going back to your user research, which I didn't point out and kind of like now it came a bit too late to me as well. It's like you probably would want to shadow an actual swimmer and go through their journey end to end. Literally ask, can I be next to you on a boat? Or can I like, you know, go for a swim with you and see exactly what you do to what extent, you know, what do you consider? Can I talk to you? And interview them at that point. And in the same way, you should also test it in a natural environment as they do their actual tasks and activities. And I'm not gonna go too much into the actual UI of it because the thing, the underlying UX is much more important here to make this a success. I like the look and feel of it. I like the concepts and things of that nature, their sound is what I'm questioning is really like that, like how does that connect? Does it actually have a strong legs to succeed? You refine the designs, make changes, that's great, great, great, great. As I said, the stock photos here, I think cheapen your statements and your visuals and things of that nature, you could simplify it. And in the next steps, you're saying many open water swimmers use Swim Boy. So this would be a great idea, even putting GPS. These things show holistic thinking, but you could have started in the ideation of that or user research of that. And at points, you're not gonna be flexible and have ability to challenge your stakeholders who might have wild ideas or be attached to their ideas. But as you grow, you're gonna need to think bigger and bigger and bigger and then see exactly what makes sense, what doesn't make sense and almost like go with that and maybe ignore the rest. If you like this video, smash that like button, leave a comment down below what you think about it. And on that note, I'll see you next time.