DESIGN SPRINT 2.0 - Prototyping Day Tips by AJ&Smart

[@AJSmart]

Gives us all your prototyping tips here!! 👇

[@fastmoveralpha19]

Minimize the amount of designing required by making the prototype understandable without color, effects, transitions, textures (physical and visual), etc. If it can be understood without enhancing elements, it's going shine with them. Question for AJ&S: How would you differentiate between a minimum viable product (MVP) and a design sprint prototype?

[@superpirate]

@@fastmoveralpha19 A MVP is functional, ready to go, only with the main feature. The prototype is a way to show the IDEA

[@Ganji2009]

Do not use any coding!!! I repeat! NO CODE!!! (unless you are testing if the code works)

[@san4ik2]

Thank you for the great video. 👍 I have two more tips for the prototyping day: 1. Assign only the stitcher role to one of the members and split the storyboard in to small tasks (e.g. find the picture for the header, write the description of XY,...) and put the tasks on a todo/doing/done board on the wall. Now you don't have to explain the roles and team member can pick a task that he/she feels capable of doing. Thus, you have automatically a priority of screens you were talking about. 2. Create a Google Slide document with a rough overview of your prototype and share it with your team. The team can than work simultaneously on the wordings and paste images to the right place. In parallel the designer can work on the polished prototype and just copy the images and texts from the shared document.

[@AJSmart]

Hey Alexander, thanks for the tips! These seem to be very useful time saving / management hacks! Glad to gain your prototyping day insights!

[@juancarloscisnerosortega3937]

I love your enthusiasm !!!

[@LuesNefandum]

Hi to you lovely AJ&Smart people, first thanks for all those great videos about the Design Sprint, you got me hooked for them :D Your idea of how to organise the wednesday leaves me with one question open: how do you keep all participants of the Design Sprints busy? Do you recommend all of them to prototype on a seperate computer? Or do you encourage teaming up? Or do you prefer giving those very busy C-Levels their room for other calls and meetings? (Don't get confused, there might be four questionmarks, but it's only one question, really ;) )

[@natesolon]

Since you're just focusing on the most important part of the experience, the prototype would usually be only a small part of the whole app right? I was wondering how you go about building out the rest of the app. Do you do additional Sprints for other parts? Or is it mostly up to the designers to build the rest?

[@karismoffat1968]

Please @AJ&Smart, answer this one!! \o/

[@fede7449]

Thanks for the video, the prototyping day of my first sprint was mostly a disaster. I ended up doing all the hardwork by myself :(

[@AJSmart]

Thanks for the feedback Fede! Prototyping day can be a tough one!

[@justinstraver24]

What did you change in the following sprints? How did you get the others to prototype?

[@huntrrams]

Please do some Whiteboard Challenge video!!

[@AJSmart]

We're on it! Thanks!

[@celinewinkel]

Haha, I love that you're making the videos fun and so easy to follow along 😍 gonna try out a Sprint next week and am so excited for it ✨

[@AJSmart]

Thanks so much Celine! Greatly appreciated! Best of luck with the Sprint next week and please let us know if you have any questions!

[@ProductJonas]

This is great!!

[@AJSmart]

Thanks Jonas! 😁

[@sarroora]

Hey guys! I have a question regarding time boxing in general, cos I have a bad habit of allocating too much work to myself in a single day, and I end up exhausted. What's considered realistic when it comes to finishing a prototype in a single work day? Even if we're just talking about the basic functions I wanna test, how many screens is common for a prototype? How complex/complete should they and their transitions be? Thanks so much again for your awesome content! Been a fan since 2018-2019 ;)

[@JacksonBeale]

Australia!!!!!

[@sakthishachin4573]

It's a great video. I have a question. After the prototype is designed on the prototype day, should we show it to the client before taking them the next day for user testing? Won't the client ask to see it. But on a curious note, if we show the prototype to the client before user testing, we might have a couple of challenges: 1. We may not have enough time to showcase the prototype to the client because the next day will be booked with user testing. 2. If we show it to the client, the possibility that the client will start asking for changes before going into user testing. I would like to understand how to tackle such a scenario. Thanks in advance.

[@lnfung]

Thanks for the video! One question. No logins, no navigations... are you guys not creating a "working" prototype but wireframes only?

[@AJSmart]

Hey Steven, sorry for the slow reply. During the Sprint week you just want to create something functional that can be tested. It doesn't have to be a fully completed app or functioning prototype in that sense. We don't do wire-framing here at AJ&Smart, but go straight from the concept sketching / ideation to prototype design. Hope that helps?

[@deepakjoseph8625]

In the book, we have the entire team pooling up their resources and time to make the prototype a success, in this video i heard, something like a specific set of people only involved in making the prototype. So what do the other members of the team do? :) I'm talking from a context, were all the members of my company (5) are involved in the sprint. Thanks in advance.

[@laurafaint6595]

Loveeeee this 😱🙌😍

[@AJSmart]

Thanks Laura!

[@julienpecorino]

Hi there I have a question! What do you do when ideas are NOT validated by users? (During user testing) What to say to the team who has spent 4 days into the Design Sprint? 😅 Thanks

[@vagkalampalikis]

Great insights! On the other hand, in which way user testers interact with the prototype? And if there are no interactions at all users just share their thoughts on the screens chosen by the storyboard process? Thx in advance! :D :D

[@flemmingmiguel8831]

I'm going to send this video to everybody that decides to do random calls on prototyping day. "Hey, don't worry you can keep working, I just wanted to get your thoughts on X" 😡 I hope they see this comment and find out why I send them here. As always guys YOU ARE AMAZING!!!!

[@AJSmart]

Thanks a lot Flemming! Yeah, Check-in times are the way forward!

[@fede7449]

Just one thing. I struggled to get the right testers, so, how can I show the "pre-prototype" to potential users in this case?

[@AJSmart]

Hey Fede, thanks for the question! We have a few solutions for finding the right user testers. 1.) Go through your own personal network and try to leverage testers within your own business networks / communities. 2.) Create highly targeted ads, primarily using the Facebook ad generator (as it's a super cheap and a very specific way to target the people you need). 3.) You can create more of an incentive by using small vouchers / rewards where applicable. If the product or client are not attracted by these, you could ask the client or business for a list of prospective customers / testers to reach out to. For all these solutions we recommend creating a highly specific survey, to further sift, guaranteeing you get the testers you need for your prototype. Hope this helps!?

[@fede7449]

@@AJSmart helpful as always, thanks so much guys! :)

[@AJSmart]

@@fede7449 Happy to help!

[@jonathancourtney1175]

THIRD!

[@AJSmart]

👍 First in our hearts!