Hi there, I like your videos and I am new to design sprint so I have a confusion between Brief and long term goal. Means if we discussed this before design sprint so what we will do in a long term goal in design sprint.
Hi there Akhilesh! Thanks for watching. The sprint brief is a small statement that we do prior to getting into Day 1. Usually we only do this with the Decider instead of all sprint participants. The point is for us to align ourselves and agree on a challenge to solve FOR THE SPRINT. Whereas the long term goal that we do on the Day 1 of the Sprint week itself is a much bigger picture statement that generally starts with the words like “In 2 years time....”. This one tends to be an optimistic top level vision. That’s why it’s also called the golden goal. If you’re in a team, everyone in the team can chip in their version of a long term goal too... An example of a Sprint Brief is: To create a user friendly mobile app for teachers to connect with their students remotely by the 3rd quarter of this year. An example of a long term goal: In 2 years time, this product will be the most sought after educational mobile app that connects teachers, students and parents that e-learning processes are much more effective than face-to-face learning. So as you can see, the long term goal is a top level vision. And the brief is literal and focuses on the sprint’s short term aim. Hope that helps!
Hi there, how do we do a customer journey map for a completely new product? Say the new brief is to create a new meal booking app for diners to ease their pain points so that they'll adopt to our new platform?
Hi Drew thanks for watching! If it’s a completely new product often times you can start with general assumptions (unless you have access to data to help with accuracy on your assumptions)... Most startups don’t have the privilege of data on their side though... So assumptions will do. You just have to start somewhere. First, pick a User Persona that you want to focus on and picture their experience cycle. An easy way to do it is to start with their Goal first. Then try to connect the experience stages from the moment and they find out (Discover) about the product, until finally reaching their desired Goal. Here’s a video on how to easily understand User Journey Mapping: User Journey Mapping (GV Design Sprint Technique) | #RELABLIFE ep.54 ua-cam.com/video/MOKqb5_62Ws/v-deo.html Hope this helps!
Hi there, I like your videos and I am new to design sprint so I have a confusion between Brief and long term goal. Means if we discussed this before design sprint so what we will do in a long term goal in design sprint.
Hi there Akhilesh! Thanks for watching.
The sprint brief is a small statement that we do prior to getting into Day 1. Usually we only do this with the Decider instead of all sprint participants. The point is for us to align ourselves and agree on a challenge to solve FOR THE SPRINT.
Whereas the long term goal that we do on the Day 1 of the Sprint week itself is a much bigger picture statement that generally starts with the words like “In 2 years time....”. This one tends to be an optimistic top level vision. That’s why it’s also called the golden goal. If you’re in a team, everyone in the team can chip in their version of a long term goal too...
An example of a Sprint Brief is: To create a user friendly mobile app for teachers to connect with their students remotely by the 3rd quarter of this year.
An example of a long term goal: In 2 years time, this product will be the most sought after educational mobile app that connects teachers, students and parents that e-learning processes are much more effective than face-to-face learning.
So as you can see, the long term goal is a top level vision. And the brief is literal and focuses on the sprint’s short term aim.
Hope that helps!
@@relabstudios thanks for your valuable time to convey this in detail with example.🙏
Hi there, how do we do a customer journey map for a completely new product? Say the new brief is to create a new meal booking app for diners to ease their pain points so that they'll adopt to our new platform?
Hi Drew thanks for watching! If it’s a completely new product often times you can start with general assumptions (unless you have access to data to help with accuracy on your assumptions)... Most startups don’t have the privilege of data on their side though... So assumptions will do. You just have to start somewhere.
First, pick a User Persona that you want to focus on and picture their experience cycle. An easy way to do it is to start with their Goal first. Then try to connect the experience stages from the moment and they find out (Discover) about the product, until finally reaching their desired Goal.
Here’s a video on how to easily understand User Journey Mapping:
User Journey Mapping (GV Design Sprint Technique) | #RELABLIFE ep.54 ua-cam.com/video/MOKqb5_62Ws/v-deo.html
Hope this helps!
Helpful video. Background music is a little distracting.
Thanks for watching and also the feedback Kunal 👍