Hey! If you want access to exclusive UX / UI design resources, casestudies, links and commentary - sign up for our FREE (and non-spammy!) weekly newsletter here: 👇 📝aj-smart.ck.page/21100f1c73 👀 Also if you haven't already, subscribe to our RU-vid channel for weekly UX / UI / Career / and Design Sprint videos: ❤️ru-vid.com&Smart?sub_confirmation=1 😉
@AJ&Smart : how you put all hand-drawn work on screen (figma or other software) because those hand-drawn work came very clear ..how you did that..please make the video on that , it helps junior designers to learn.
It starts so well with the HMWs and the call, the board... then you got lost. No mention on user research No mention on any data insights No mention on how you solved a full wall of HMWs No mention on any user validation (at some point you need to validate the assumptions or it will happen in the appstore=) It feels just like a visual redesign to Kevin's taste. The section about the paintings is really unnecessary, especially after omitting all the important steps. But the paintings are beautiful :D You can do better guys
It was a redesign, according to the team. So, more like rebuilding what already exists rather than creating something new for the users. Basically, all based on aesthetics and assumption. And sorry I'm replying to a one-year old comment.
@@johnsonbabawale8175 That is the same as rebuilding a house without taking into account the familly that will live there. Does not make sense - Especially redesign work has to have the user as the main focus since, the first product/service has failed otherwise there would be no need to do a redesign.
This was awesome! More of these, please!!! Case study style with more workflow breakdowns (who did what and how many on that team), the UX portion, other team roles, etc. thanks again for this. There’s not another video on youtube like this.
I'm an industrial designer and I found that there's so much in your process that I can borrow and will benefit mine, even though you're in a completely different line of work. Thank you for sharing
Absolutely! Our intern right now is also in industrial design! @Myrin The Design Sprint process is absolutely applicable for all kinds of work. Not limited to design at all. Very cool that you recognised that!
Thanks so much for sharing this. About to start my first job as a UX designer in an agency and this is insanely helpful in preparing me for some of it. Awesome work!!
Hi Jonathan! Thank you for sharing your process to the community, really hepfull to see how you guys work on a real project. Looking forward for this kind of videos again. All the best!
What is the composition of your team? How do you divide tasks to accomplish this kind of speed, what is your work flow like? It'd be nice to do a video breaking these down or redirect me to one if it exists. We need to know!
@@ongkiherlambang7416 He said the app was ready in about four months since they started. So minus the initial four weeks, Development should have taken up the remaining time that is 3 months.
I’ve used oak before watching this video and what stood out to me was actually the simple and intuitive design! It’s actually one of the apps I use as a great example of what an app should look like👀
As a junior UX designer this was SUPER helpful! Thank you so much for sharing the process of creating this app and giving me some inspiration on how I want to grow as a designer.
Great video, there is always so much to learn from real-world case studies, particularly when it covers the complete process. thanks for sharing - looking forward to seeing more 😉
Wonderful video. Solid gold. Keep doing these. These are so helpful and I personally prefer them over any article I could read about the experience. I've already viewed it three times today. One thought: For the 90% of the paintings from Sarah didn't use from the app, could they be repurposed? Maybe offer a framed original for some event in the future, or do something with charity? Dunno. Just seems like some magnificent artwork that could be showcased in different ways. All the same, thanks again for posting this. Been using the app since it came out. Btw, can you add a feature to end a meditation session after the 10/20 minute period is done? Don't mind the extra, but I try to fit in a session during the day before a stressful meeting, and having a end timer (with a chime or something) would be awesome. See you!
Superb documentation of the design process here. I love how you delineate the steps going from concept to the prototype. Naturally there is more depth in each stage than is actually shown on the video, but I think this is meant to just be a brief overview.
Just found your channel. Thank you for this video. Exactly what I was looking for. Amazing work! I hope I can find more content like this on your channel.
I would like to thank you for this video. It motivated me to push myself, to explore, to discover. It is crucial to focus your energy into understanding the right parts of the project just as you did.
Loved this! I am interested in how you deliver for development. I have worked with scrum development teams and it is easy to have ceremonies and talk about all the details in the functionalities and flows you´ve designed. How do you find a way to explain every single design and interaction - and even the back-end logic that goes with it - when doing it remotely?
We make a high-fi prototype with all the animations included so not much thinking is required - we also did a few calls with the dev to explain some of the weirder Ideas we had.
Congratulations! Johnathan... to you, the team at AJ & Smart, and to Kevin Rose. It is a beautiful App. I wish I had been part of the design team and process. I would be very proud. Besides the many added features, I love the Japanese theme throughout, the illustrations by the very talented Irish lass, Sarah, and the watercolor look. Thank you. I like and subscribe to all of your videos but I especially liked this video. I really hope you make a part 2 where you describe the user research finding, usability studies, and everything else that came just before production. Who did the user research and content writing?
Hey there Robert, glad you enjoyed the video! Because we were following the Design Sprint process, there was little to no previous work involved - that's the whole beauty of the process :)
Awesome video guys! but it's also nice to have the customer committing their time to you. So many times we get into a design process and customer communication being the biggest delay... Would be awesome to see a video on how you guys deal with that...
Hey, thank you for your knowledge. I just recently finished working for an automotive app startUp and all your videos have opened my eyes and shown me why we had so many problems with the product-market fit in the beginning. By the way, I am a little bit curious to learn, how you build your qualitative and quantitative questions for the expert interview session and user testing phase? Thank you very much and keep doing videos, you are helping a lot of Latinos as my self to become each day better as UX/UI Designers and have better opportunities in international markets.
This is very amazing! But whenever I see design sprints being used to really deliver a product, the question that always pops in my mind is: what about the backend? Does the process of creating a back-end architecture and system exists within the sprint? How do you manage the client's expectations about that? And how does people who build this side of the project perpetuate the sprints and the concept work itself? Asking it because I am a designer and work directly daily with a bunch of back-end dudes and most of the consumed time goes to tickling the server side of the question. Front-end work is always quicker and minimal in comparison to effort and time put shipping the API.
This is a great question! The short answer is that the Sprint isn't a process for back-end development. It's for testing new ideas fast. Our delivery to a client can sometimes be the design elements, but we don't use a Sprint to work through the back-end. Managing the expectations from the client is quite simple, you need to make sure that you are upfront with them about this before the Sprint! Setting expectations, is a massive part of onboarding our clients!
Hey, thanks for replying. The question I made came from a place in my reality where backend architecture dictates a lot in how we can or will do whatever stuff. Sometimes me, a designer, points to the back-end guys some change I intent to make - going from simple to complex stuff, like changing labels from CAPS LOCK to Caps Lock - and then, for whatever reason, could be time, priority, etc, they can't do it. So the design is only a frame of what the product could be like, not what will actually be shipped. But I came from a place where the product was built with some inevitable UX thought but none design at all. Maybe wherein products are built with the design being the perfect representation of clients and, sometimes, user needs, the back-end follows along and turn themselves upside down to built stuff. Thanks!
I just discovered all your videos 1 week ago, and I just wanted to thank you for the amazing & quality content you offer to the community. I like the format and to pickup more or less randomly some videos everyday. Good job guys !
Great work. Really well done User Interfaces but I am quiet surprise that no Usability Testing were included there. Renewing the app is a great opportunity to improve the User Experience and talk with the real users to check what could be improved on the app flow.
This is solid work for a 1 week sprint. Like wow! Because it was 1 week I don't find it that controversial to not have users involved initially though I'm a test early and hard fan. I was all thumbs up from the moment I saw you guys used Realtimeboard. I'm a HUGE fan! Do you use the Concepts App? Geek Tip: You can export your drawings to Sketch (SVG) and then separate out the pieces to let others assemble how they would approach the IA/Hierarchy. I did this recently with a very inexperienced team and it worked wonderfully :)
Hey Steve, I don't believe we do use that but we'll check it out for sure! Thanks so much for your feedback, and for sharing your resources too! Glad to hear the Concepts worked well for your project too!
!. Can we see the storyboard? 2. What did you use to animate your prototype? 3. Can you talk more about the prototyping work? How many people were working in it at the same time?
I am really intrigued to know what went behind not mentioning the user aspect. Did you guys actually involved the users and just couldn't mention it here, or you decided to not involve the user during this part of your process? I am really interested to know how and why you made that decision and what were the impacts. Please make a video on this topic as well, it will really help. Thank you :)
When will be a good time to do testing with users? I notice in the video you did not mention about testing but it went straight to handover and launch. I am little confused haha.
I think hearing about Basecamp part would be the most interesting part of this video actually. As a designer it's easy to understand your design process but it's hard to predict or understand how do you put together design and project management processes all together?
We can certainly aim to do a video on the basecamp sections of the project. It would be a great round up of the project as a whole too! Great idea IIhan, thanks for sharing!
Would you guys consider doing a video on how you would integrate Design Sprints within an Agile environment? I am trying to push this effort, but would like some clarity on this. Thanks again, you guys are awesome!
Great video! What kinds of questions did you ask Kevin during the expert interview? Were you trying to ask him about how the users are using the app or what kinds of problems the app has or how he envisioned improving the app? I feel like there has to be some obvious objective of the interview in order to get to the HMW questions.
I love the design process and the work done. Watercolors to lighten it up was a master stroke. However, one thing felt out of place. It looks like it is a lot of stuff and some of it may not be something the user wants? I understand the psychology behind giving badges and the growing bonsai tree ( which was rejected ) but it all seems so anxiety inducing as a user. You are guilt tripping me into meditating because if I don’t my badges and points or whatever aren’t accumulating. So now I am viewing it with my obsession to complete things than with a calm relaxed mind. In other words, I am bearing the burden of meditating so I can get those badges because I am a compulsive over achiever. Of course this is a far fetched scenario, but doesn’t take away from the fact that you have not focused enough on the meditation part. Even the time binding of every meditation is so anxiety inducing. I don’t want to know how long I meditated for because in my head I’m just going to count time to beat my previous time if I use the app again. Also as a user I just want to get down and dirty with my purpose - meditation - and move on. I don’t want to get sucked in to a world your designers and you have created to set apart your identity. It is frustrating. In the end, not even considering what a user wants is not good. Your users are not one kind - healthy minds looking to meditate - they are anxious, confused, overwhelmed and many more. You are not really catering to the other types and that is bad from the application point of view. Not sure why I ranted so much.. but food for thought :)
Thank you, Amit! That's very important feedback. You're completely right, many of the users won't fit into the "healthy minds looking to meditate" but, as designers, we also can't design with everyone in mind. We need to focus on a design persona that best represents the customers.
How did you guys validate the concepts with users? Did that happen at any point before hand off to development, or was this sprint primarily around updating the look and feel of the app?
Thanks for such valuable info, one thing I found rather odd is the fact that in the entire process the end user was never involved , no user testing or whatsoever , pretty risky approach IMO
This is nugget! Awesome tips. 🙋🏻♂️ Question: What are your takes on this “work-backward strategy”, where you have pre-assumptions before diving into user research and so on? I find this strategy is similar to the “Faster Horse Theory” (inspired from Henry Ford’s famous quote).
Hey Jonathan, amazing work, really love the vibe that the illustrations give to the app. Did you guys include the final user in any point of the design process?
thank you so much personally learned a lot but i wonder how you did UX part without considering users? (it is just a question) i mean the whole ux part is about users but i really liked the video it helped me a lot to know the steps of a ui/ux project
