Hi! Great video! I was wondering weather the "client" should be prepared and bring his own examples to show and tell or should the design team be prepared and suggest examples instead. Thank you very much!
Hi Sofia! At a Lightning Demo session, other than the facilitator, each participant or team member is expected to bring some examples. The team is usually a mix of the design team members and the clients. So everyone is expected to participate (while the facilitator will take notes). Thanks for watching and hope it helps!
Just a quick question : do you use sprint methodology in every project? Or simply put, does this method suits for every type of product design e.g web, app? Thanks.
Thanks for watching Chooi. Not all projects require the Design Sprint approach. Although we use parts of Design Thinking and Design Sprints on most of our work, only some type of projects require the full Design Sprint method. So when should you use Design Sprints? 1. When you have a complex or nagging business problem that keeps popping up, or an intricate one, then it’s ripe for a design sprint. This happens often in large companies with cross-functional teams, or with products that cater to a variety of users. 2. When you may have a risky and expensive project that is likely looking to excessive, resource-hungry, and costly affair, then you should run a design sprint for it. Design sprints help clarify the problem and produce realistic solutions with customer validation. Getting early feedback before spending money and resources gives you some form of guarantee to the risk you’re about to take. 3. When you take too long from idea to launch. Sometimes an idea sits in cold storage for years, or an issue remains unresolved for months. Design sprints force you to act because the output is a prototype and recommendations for the next steps. Furthermore, one of the biggest benefits is you’re discarding conventional processes for bringing an idea to life. You can resolve an issue or build on an idea within a week.
Hi! Great video! I was wondering weather the "client" should be prepared and bring his own examples to show and tell or should the design team be prepared and suggest examples instead. Thank you very much!
Hi Sofia! At a Lightning Demo session, other than the facilitator, each participant or team member is expected to bring some examples. The team is usually a mix of the design team members and the clients. So everyone is expected to participate (while the facilitator will take notes). Thanks for watching and hope it helps!
Just a quick question : do you use sprint methodology in every project? Or simply put, does this method suits for every type of product design e.g web, app? Thanks.
Thanks for watching Chooi. Not all projects require the Design Sprint approach. Although we use parts of Design Thinking and Design Sprints on most of our work, only some type of projects require the full Design Sprint method.
So when should you use Design Sprints?
1. When you have a complex or nagging business problem that keeps popping up, or an intricate one, then it’s ripe for a design sprint. This happens often in large companies with cross-functional teams, or with products that cater to a variety of users.
2. When you may have a risky and expensive project that is likely looking to excessive, resource-hungry, and costly affair, then you should run a design sprint for it. Design sprints help clarify the problem and produce realistic solutions with customer validation. Getting early feedback before spending money and resources gives you some form of guarantee to the risk you’re about to take.
3. When you take too long from idea to launch. Sometimes an idea sits in cold storage for years, or an issue remains unresolved for months. Design sprints force you to act because the output is a prototype and recommendations for the next steps. Furthermore, one of the biggest benefits is you’re discarding conventional processes for bringing an idea to life. You can resolve an issue or build on an idea within a week.
👍