RADS - Rapid Application Design Sprint

Editor's Notes

• #4: What does UX do for Valuga - OutSystems uses the principles and has good base themes as a starting point from which to elevate the UI, but to not focus on the technical part, functional part it helps to set the horizon, for who you build something. But to give the best starting direction for an application we start of with Design sprints for Rapid application
• #5: My first UX experience with Application design - started off with designing a iPad video-call app for elderly (75+). Which, looking at when they see someone while calling ,is super cute, reactions were amazing and got to the heart. But the initial action, touching the screen to call, using the iPad, made it scary for them. So how to lower that bar? That was my first experience, which, testing with an elder, makes you care immediately. This made me want to do it for everyone, getting an application that includes and goes for someone who uses it, not focused on the technical part, but on the one person using it.
• #6: Early involvement of the user takes away (problematic) changes in the future. How do you do that? Well, with RADS we have basis to kickstart an application, which helps getting everyone on the same page, with the same goal, with all known possible issues in mind. How?
• #7: Users at the heart Rapid Application Design Sprint praktische implementatie van design thinking bedacht door google voor start projecten aangepast door ons voor low code projecten google 5 dagen, wij aangepast naar 2 dagen plus wat follow up ivm user testen Early involvement of the user takes away (problematic) changes in the future. How do you do that? Well, with RADS we have basis to kickstart an application, which helps getting everyone on the same page, with the same goal, with all known possible issues in mind. How?
• #8: Will it work or not? How can you be sure what you’re about to build applies in the field and its users?
• #9: Look at it from a room without light and you have to throw a dart at the board. The chances of you hitting the bullseye is near impossible, maybe you get super lucky though. You throw it, hear it hit somehting //insert joke, hitting a teammember in the but, so you might know you hit it totally wrong // But by throwing that dart...
• #10: But by throwing that dart... You get to see the room, you know if you went in the right direction or not. You fail first time, but it helps to know where to go now. you can see the bullseye, the horizon!
• #11: But by throwing that dart... You get to see the room, you know if you went in the right direction or not. You fail first time, but it helps to know where to go now. you can see the bullseye, the horizon! https://www.imdb.com/title/tt0112384/?ref_=nv_sr_1?ref_=nv_sr_1 NASA must devise a strategy to return Apollo 13 to Earth safely after the spacecraft undergoes massive internal damage putting the lives of the three astronauts on board in jeopardy.
• #12: But by throwing that dart... You get to see the room, you know if you went in the right direction or not. You fail first time, but it helps to know where to go now. you can see the bullseye, the horizon!
• #13: Will it work or not? How can you be sure what you’re about to build applies in the field and its users?
• #14: Will it work or not? How can you be sure what you’re about to build applies in the field and its users?
• #15: Will it work or not? How can you be sure what you’re about to build applies in the field and its users?
• #16: Will it work or not? How can you be sure what you’re about to build applies in the field and its users?
• #17: made it through test fase, right after this moment getting involvement of users early on - their feedback and know where to go that way, turning the light on.
• #18: If i had this at my first ever application design, i’d probably be much quicker in understanding the problmen. Conveying this to the team and getting a real prototype, instead of paper-prototyping.
• #19: Pro points