Week 3: Joining design sprints

Hey, I hope that you’ve enjoyed your first two
weeks of the course. So far, you’ve learned about
the UX design career field, explored common UX
design frameworks, and learned about
user-centered design. You also spent some time with my colleague Shabi to understand equity-focused design
and the importance of accessibility in
the design process. Now it’s time to switch gears and learn about the
world of design sprints, including the phases of a design sprint and how to
plan and participate in one. You’ll also learn
about retrospectives, which are a way to reflect on a design sprint and
identify areas of improvement to implement into your designs. Let’s get to it.

Introduction to design sprints in UX

What is a design sprint?

A design sprint is a time-bound process with five phases typically spread out over five full, eight-hour days. The goal of design sprints is to solve a critical design challenge through designing, prototyping, and testing ideas with users.

Benefits of design sprints

Design sprints offer a number of benefits, including:

• Speed: Design sprints can help teams make decisions and launch products more quickly than traditional development processes.
• Focus: Design sprints force teams to focus on the most important aspects of a product or service, and to prioritize user needs.
• Collaboration: Design sprints bring together teams from different disciplines to work together on solving a common problem.
• Validation: Design sprints provide an early opportunity to test ideas with users and get feedback, which can help to avoid costly mistakes later on.

When to use design sprints

Design sprints can be used to solve a wide range of design challenges, but they are particularly well-suited for:

• New product development: Design sprints can help teams to quickly develop and launch new products or services.
• Product improvement: Design sprints can be used to improve existing products or services by understanding user needs and testing new solutions.
• Strategic planning: Design sprints can be used to develop strategic plans for products, services, or even entire businesses.

How to run a design sprint

A design sprint is typically run by a facilitator who is responsible for keeping the team on track and moving through the different phases of the sprint. The five phases of a design sprint are:

1. Understand: The first phase is all about gathering information about the design challenge and the users who will be affected by it. This can be done through user research, interviews, and data analysis.
2. Ideate: In the second phase, the team generates ideas for solving the design challenge. This is a brainstorming session where all ideas are welcome, no matter how crazy they may seem.
3. Decide: In the third phase, the team selects the best ideas to move forward with. This is done by evaluating the ideas based on their feasibility, desirability, and impact.
4. Prototype: In the fourth phase, the team creates prototypes of the selected ideas. Prototypes can be anything from a simple sketch to a working model of the product or service.
5. Test: In the fifth and final phase, the team tests the prototypes with users to get feedback. This feedback can be used to refine the prototypes and ensure that they meet user needs.

Conclusion

Design sprints are a powerful tool that can be used to solve complex design challenges in a short period of time. By following the five phases of a design sprint, teams can quickly develop and launch new products, improve existing products, and develop strategic plans.

Additional tips for running a successful design sprint

• Involve the right people: Design sprints should involve a cross-functional team of people with different skills and perspectives. This will help to ensure that the team generates a wide range of ideas and that the final product or service meets the needs of all users.
• Set realistic goals: It is important to set realistic goals for the design sprint. The goal should be to achieve measurable progress on the design challenge, not to solve the entire problem in five days.
• Be flexible: Things don’t always go according to plan, so it is important to be flexible and adaptable during the design sprint. If a prototype is not working as expected, don’t be afraid to pivot and try something different.
• Get feedback early and often: It is important to get feedback from users early and often throughout the design sprint process. This will help to ensure that the team is on the right track and that the final product or service meets user needs.

Design sprints can be a great way to solve complex design challenges quickly and efficiently. By following the tips above, you can increase your chances of success.

What is the goal of a design sprint?

The goal of a design sprint is to solve a problem through designing, prototyping, and testing ideas with users.

A design sprint can answer critical business questions to design challenges.

Hey, welcome back. So far we have
covered common terms, frameworks, and tools that entry-level UX
designers should know. We’ve also talked about the importance of
user-centered design and why UX designers
should focus on equity in the design process. Let’s start with a
little exercise. Take a look around the
room you’re in right now. Notice the shape of your table and the ergonomics of your chair? What about the device you’re using to play this
video on right now? All that stuff and almost
everything else around you started off as a design
problem or design challenge. So, how does something go from a design challenge to an
actual user-centered product? One way is through
design sprints. A design sprint is a
time-bound process with five phases typically spread out over five full,
eight-hour days. The goal of design sprints is to solve a critical design
challenge through designing, prototyping, and testing
ideas with users. At Google, we use design
sprints to answer questions, define product directions, figure out cross-team strategies, and even build team culture. For example, I was
recently a part of a design sprint for Google’s
Transparency Report. The goal was to better understand how our users
experience the reports. We also discussed
the website’s goals, values, and future vision. Design sprints generally
include five phases: understand, ideate, decide,
prototype, and test. We’ll come back to these phases and investigate each one later. So, what makes a design
sprint so useful? For one, design
sprints save time. With a sprint, your team can cut the decision-making process down from several months
to a single week. Sprints also create
an effective path to bring a product to market. Sprints prioritize the user, putting their needs
front and center. Sprints allow you to fast
forward into the future to test your product and get customer reactions before
making any expensive decisions. Running a design sprint is
like using a superpower. With all these benefits, you’d think every product team would want to run design sprints, but that’s not always the case. Before launching into
a design sprint, you need to review your
design challenge and ask yourself these key questions: Are there many potential solutions to your design challenge? Does a design challenge require people from cross-functional teams to weigh in? Is the design challenge’s scope
wide enough for a sprint? If you answered yes to any
one of these questions, a design sprint might
be the right move. You’ve got the basic idea
behind design sprints down. Now you know what a
design sprint is, the benefits of running
a design sprint, and how to identify when
to use a design sprint. Next, let’s check out each phase of the
design sprint process.

Five phases of design sprints in UX

Design sprints are a five-day process for rapidly prototyping and testing new ideas with users. They are a popular tool in the UX design world because they allow teams to quickly iterate on their designs and get feedback from users early in the process.

The five phases of a design sprint are:

1. Understand: The team learns about the design challenge and the users they are designing for. This may involve conducting user research, interviewing experts, and brainstorming potential solutions.
2. Ideate: The team generates a wide range of solutions to the design challenge. This is a time to be creative and come up with as many ideas as possible, no matter how crazy they may seem.
3. Decide: The team selects the most promising solution to prototype and test. This may involve voting on ideas, discussing the pros and cons of each option, and making trade-offs.
4. Prototype: The team builds a realistic prototype of the solution. This may involve creating a paper prototype, a wireframe, or a working prototype with basic functionality.
5. Test: The team tests the prototype with users and collects feedback. This feedback can then be used to improve the prototype and iterate on the design.

Here is a tutorial on how to conduct a design sprint in UX:

1. Day 1: Understand the design challenge and the users.
   • Conduct user research to learn about the users’ needs and pain points.
   • Interview experts to get their insights on the design challenge.
   • Brainstorm potential solutions to the design challenge.
2. Day 2: Ideate solutions to the design challenge.
   • Generate as many ideas as possible, no matter how crazy they may seem.
   • Sketch out your ideas on paper or on a whiteboard.
   • Present your ideas to the team and discuss their pros and cons.
3. Day 3: Decide on a solution to prototype and test.
   • Vote on the most promising ideas.
   • Discuss the trade-offs of each option.
   • Make a decision about which solution to prototype and test.
4. Day 4: Prototype the solution.
   • Create a realistic prototype of the solution.
   • This may involve creating a paper prototype, a wireframe, or a working prototype with basic functionality.
5. Day 5: Test the prototype with users and collect feedback.
   • Recruit users to test your prototype.
   • Observe how they interact with the prototype.
   • Interview the users about their experiences.
   • Use the feedback to improve the prototype and iterate on the design.

Tips for conducting a successful design sprint:

• Get the right people involved. The design sprint team should include a mix of people with different skills and perspectives, such as UX designers, product managers, engineers, and researchers.
• Set clear goals. What do you want to achieve by the end of the design sprint? Make sure everyone on the team is aligned on the goals.
• Be focused. The design sprint is a fast-paced process, so it’s important to stay focused on the task at hand. Avoid getting sidetracked by new ideas or tangents.
• Be open to feedback. The goal of the design sprint is to get feedback from users as early as possible. Be open to the feedback you receive and use it to improve your design.

Design sprints can be a powerful tool for UX designers to quickly and efficiently prototype and test new ideas with users. By following the tips above, you can conduct a successful design sprint and create better products for your users.

Which design sprint phase helps a team gain a better idea of the design challenge by learning from experts in different departments and industries?

Understand

This is an example of the Understand phase because the team took time to learn from and engage in discussions with industry experts. These steps help team members understand the design challenge more clearly.

Hi again. Let’s think back to those five design
sprint phases we introduced earlier: understand, ideate, decide,
prototype, and test. Now we’re going to go beyond introductions
and really get to know each phase. A traditional design
sprint lasts five days, with each phase taking up to one full day. The whole process is super hands on. Creative collaboration is
at the core of every phase. Let’s explore how a team might
conduct a design sprint. Okay, imagine you’re a UX designer for
a company called Cycling Enthusiasts. Your latest app lets cyclists track
their distance ridden and calories burned. Sadly, the app sales
have started slumping, kind of like how your energy would start
slumping if you had actually taken a long bike ride today. So, how can a design
sprint solve this problem? Let’s find out. The understand phase sets your
sprint on the right track and helps your team get a clear
picture of the design challenge. Your team takes time to learn from experts
and engage in creative discussions with a lot of different people from
other departments and industries. These conversations help you more
clearly understand the design challenge. But what’s the first rule of UX design? The user comes first. This means everything your
team does during the sprint should focus on the user. So now your team understands
the design challenge. For our imaginary sprint, let’s say sales are slumping because the
app doesn’t offer bicyclists anything new. Your team arrives for
phase two of the design sprint, pumped full of inspiration and
ready to ideate some solutions. To get the creative juices flowing,
you start this phase by coming up with ideas and building off
of them to create solutions. Once you’ve got the team thinking, each
participant takes time to sketch and present their ideas. Don’t worry about your drawing skills
here, the idea is what matters. On top of all the ideating that happens in
phase two, you also need to start planning for user testing, which happens
in phase five of the sprint. During user testing, you’ll have a diverse
group of people test your product and provide feedback. To be able to do this, you need to
start recruiting users that fit your target profile now, so the
sprint stays on schedule. By the time you reach phase three,
you have a lot of potential solutions for your design challenge. Now it’s time to decide which
solutions you want to build. Together, your cycling app team
discusses each possible solution, and eventually decides on the one solution
that is most likely to excite users and increase sales. For example, the solution might be
a feature that uses the cyclist’s location to create customized routes that meet their
fitness goals. Sounds pretty cool, right? Finally, you’ll wrap up the day by
creating a step-by-step blueprint for your prototype. Next, phase four: prototype time. You’re now ready to build the first
version of your new app feature. At the end of this phase,
you don’t need a finished product, just something realistic
enough to test with users. By focusing only on what the user
experiences on their screen, your team creates a working prototype
of the new customized routes feature. Way to go! During this phase,
you also finish prepping for user testing by confirming the test
schedule, finalizing interview questions, and making sure your
prototype is good to go. Alright, it’s been a
busy week, but you did it. You reach the final phase: testing.
Now it’s time to put your prototype in front of users. As users test your prototype, you observe how they react and then
interview them about their experiences. Your team gains critical insight about
changes that need to be made before you launch the new feature. To recap the five phases
of design sprints are: understand the scope of the design
challenge, ideate possible solutions, decide on the most viable solution, create a workable prototype, and finally, test that
prototype with actual users. Congrats, you made it to
the end of the sprint. Now your team knows exactly what to adjust
before launching the new cycling app feature. Promotions for all! Design sprints are a big part
of the UX design world, so you’ll probably participate in a lot
of them and even lead a few someday. Coming up, we’ll explain why design
sprints are beneficial to UX designers.

Benefits of design sprints in UX

Design sprints are a five-day process for rapidly prototyping and testing new ideas with users. They are a popular tool in the UX design world because they offer a number of benefits, including:

• User-centricity: Design sprints are focused on the user and their needs. This is because the user is the ultimate customer, and it is their satisfaction that determines the success of a product.
• Collaboration: Design sprints are a collaborative process that brings together people from different disciplines, such as UX designers, product managers, engineers, and researchers. This diversity of perspectives leads to better ideas and solutions.
• Focus: Design sprints are a focused process that gives the team time to focus solely on a design challenge. This is in contrast to the typical work environment, which is often filled with distractions and interruptions.
• Reduced risk: Design sprints reduce the risk of an unsuccessful market debut by getting feedback from real users early on. This feedback can be used to make necessary adjustments to the product before it is launched.
• Versatility: Design sprints can be used at any point during a project, whether you are just starting out or you are facing a specific challenge. This makes them a versatile tool that can be used to solve a wide range of problems.

Here are some specific examples of how design sprints have benefited UX teams:

• A design sprint helped a team at Google to develop a new feature that increased user engagement by 20%.
• A design sprint helped a team at Airbnb to develop a new pricing strategy that increased revenue by 15%.
• A design sprint helped a team at Netflix to develop a new recommendation algorithm that improved user satisfaction by 10%.

Overall, design sprints offer a number of benefits to UX teams. They are a user-centric, collaborative, focused, and versatile tool that can be used to reduce risk and create better products for users.

How to get started with design sprints

If you are interested in using design sprints in your UX process, there are a few things you need to do to get started:

1. Learn about the design sprint process. There are a number of resources available online and in libraries that can teach you the basics of design sprints.
2. Assemble a diverse team. Your team should include people with different skills and perspectives, such as UX designers, product managers, engineers, and researchers.
3. Schedule the sprint. Design sprints typically last for five days.
4. Prepare for the sprint. Gather all the necessary materials and resources.
5. Follow the design sprint process. The design sprint process is divided into five phases: understand, ideate, decide, prototype, and test.

There are a number of tools and resources available to help you plan and execute a design sprint. One popular tool is the Google Ventures Design Sprint Kit. This kit provides you with everything you need to run a successful design sprint, including templates, worksheets, and a facilitator’s guide.

Design sprints can be a powerful tool for UX teams to solve complex problems and create better products for their users. By following the tips above, you can get started with design sprints and start reaping the benefits.

Ready to learn even more
about design sprints? Me too. From tech to finance to retail, future-forward companies
in all kinds of different industries
use design sprints to solve complex problems. In other words, sprints are
pretty much a game changer. But what makes design
sprints beneficial? Why are they so darn popular? Here is what a few seasoned UX
designers have pointed out. First, in design sprints, it’s all about the user. Sprint participants make sure the design challenge is always focused on the user
and their needs. After all, it’s the users who ultimately decide if your
product is successful, right? Second, sprints value
every person in the room: From the office intern to
the senior stakeholder, including people from
lots of disciplines and experience levels is a
key part of the process. Why? Because considering
all angles of the problem and the solution means the best ideas will
rise to the top. Next, sprints give
the core team time to focus solely on a design
challenge. Think about it: Five work days
devoted entirely to distractionless, gadgetless
creative collaboration. Now, that’s a recipe for some
serious problem-solving. Also, sprints lower the risk of an unsuccessful market debut because the team gets feedback from real users and can make critical adjustments before
the product launches. And finally, sprints are versatile
because they can be scheduled at any point
during your project. When a challenge arises, you’ve always got the
design sprint option in your back pocket. So are you sold on the benefits
of a design sprint yet? Awesome. Next, let’s focus on how to plan an effective one.

What is a design sprint?

A design sprint is a five-day process for rapidly prototyping and testing ideas with users. It is a great way to solve complex UX design challenges in a short period of time.

Benefits of design sprints

Design sprints offer a number of benefits, including:

• Speed: Design sprints can help you quickly validate or disprove your ideas, and iterate on your designs.
• Focus: Design sprints force you to focus on the most important aspects of your product or service.
• Collaboration: Design sprints bring together cross-functional teams to work together on solving a problem.
• User feedback: Design sprints allow you to test your ideas with users early and often, to get their feedback and make sure you are on the right track.

How to plan a design sprint

To plan a design sprint, you will need to:

1. Define your goal. What do you want to achieve by the end of the sprint?
2. Recruit your team. You will need a team of people with different skills and expertise, such as designers, developers, product managers, and researchers.
3. Schedule your sprint. Design sprints typically last five days, but you can adjust the length to fit your needs.
4. Prepare your space. You will need a space where your team can work together comfortably and collaboratively. Make sure to have whiteboards, sticky notes, and other supplies on hand.
5. Plan your activities. Each day of the sprint has a specific focus. You will need to plan activities that will help your team achieve the goals of each day.

Here is a more detailed overview of each day of a design sprint:

Day 1: Understand

On the first day of the sprint, your team will focus on understanding the problem you are trying to solve. You will do this by conducting user research, interviewing experts, and brainstorming potential solutions.

Day 2: Sketch

On the second day of the sprint, your team will sketch out potential solutions to the problem. You will do this by creating quick and low-fidelity sketches of your ideas.

Day 3: Decide

On the third day of the sprint, your team will decide on the best solution to pursue. You will do this by reviewing your sketches and feedback from your users.

Day 4: Prototype

On the fourth day of the sprint, your team will build a high-fidelity prototype of the solution you decided on. You will do this by using tools such as Sketch, Figma, or InVision.

Day 5: Test

On the fifth and final day of the sprint, your team will test your prototype with users. You will do this by conducting usability testing and gathering feedback.

Tips for planning a successful design sprint

Here are some tips for planning a successful design sprint:

• Get buy-in from your team. Make sure everyone understands the purpose of the sprint and is committed to participating.
• Be prepared. Plan your activities in advance and make sure you have all the supplies you need.
• Be flexible. Things may not always go according to plan, so be prepared to adjust your schedule or activities as needed.
• Focus on users. Keep your users in mind at all times throughout the sprint. Make sure you are designing a solution that meets their needs.

Conclusion

Design sprints are a great way to quickly and efficiently solve UX design challenges. By following the steps above, you can plan a successful sprint that will help your team achieve its goals.

When planning for a design sprint, what should you look for in a meeting space to ensure the best experience for all participants? Select all that apply.

• Whiteboards to capture your ideas or hang sticky notes
• Accommodations for anyone who needs them
• Comfortable furniture that you can move around easily

Spaces with comfortable furniture you can move around easily are ideal spaces for design sprints because they accommodate meetings that require a lot of time. Provide accommodations for anyone who needs them, and whiteboards to capture ideas.

Hey, nice to see you again. As an entry-level UX designer, you probably won’t be expected
to lead a design sprint. But it’s still helpful
to know what it takes to plan a successful one. Let’s check out some
of the basic ideas. First up, user research. If you’re lucky enough to have a dedicated researcher
on your team, they can own this step. If not, well, you might
be taking it on yourself. User research is always the first step in any
sprint planning process. Your research should focus on the user problems you’re trying to solve during the sprint. You don’t have to detail out a specific problem right away. But getting a rough idea of what your sprint
will focus on will help you decide
which research methods make the most sense. We’ll discuss different
research methods in more detail later. Next, it’s time to
call in the experts. If you’re planning the sprint, it’s up to you to schedule short talks with colleagues
or industry experts. You’ll listen to
these info-packed talks during the understand
phase of the sprint. A good talk helps clarify the problem your sprint
is trying to solve. Keep in mind, the more
experts you bring in, the more schedules you
have to accommodate. Start planning early; we
promise, it’ll be worth it. Step 3: Find the right space. Sounds a little obvious. But trust me, booking the right room can make
all the difference. It’s important to ensure
that the space allows all employees equal opportunities
to perform their job. Let’s talk about a few
things you should look for. Whiteboards to capture your ideas or hang sticky notes, acoustics so participants
can hear each other easily, accommodations for
anyone who needs them, and comfortable furniture that you can move around easily. You’re going to be
spending a lot of time in this room, so get cozy. Once you’ve found
the right space, it’s time to gather supplies. If you’re planning
the design sprint, it’s your job to make sure everyone has what they
need to participate, kind of like a teacher handing
out classroom supplies. Some essentials include markers, sticky notes, and a lot
of snacks and water. On to Step 5: Establish
the rules of the sprint. If you want this to be a gadgetless,
distraction-free zone, now is the time to say so. Figuring out the ground
rules in advance sets the tone for the sprint, gets everyone on the same page, and helps your team stay focused. You’ve done your research, called in the experts, found the right space, gathered supplies, and established your
sprint rules. What’s next? Step 6 is planning
introductions. This can be pretty important
since sprints involve cross-functional teams that
may have never met before. We all know icebreakers
can be a little cheesy, but they’re still a
great way to help your team get comfortable
with each other. Plus, choosing icebreakers that are relevant to your sprint can motivate your team and put
them in the right mindset. Here’s an idea for an icebreaker. Ask everyone to talk about a time they called customer
service to complain. This puts the team in
the shoes of a user, exactly where you want them to be when solving UX
design challenges. We made it to the final
step: post-sprint planning. That means thinking about what will happen after
the sprint wraps up, like how your team
might use what you’ve learned to achieve other goals. To do this, you
need documentation. Make sure you enlist
a few people to help document the design
sprint by taking pictures, collecting sticky notes,
and jotting down ideas. Let’s recap the sprint
planning basics. To prepare for a design sprint, you’ll need to conduct
user research, schedule talks with experts, find the right space,
gather supplies, establish ground rules, break
the ice with your team, and plan out post-sprint
action items. Sound about right?
Awesome. Let’s keep going. Up next, we’ll walk through
a design sprint brief.

A design sprint brief is a document that introduces your team to the sprint objectives, identifies the key deliverables, and outlines the logistics of the sprint. It is an important tool for ensuring that everyone on the team is aligned on the goals of the sprint and what needs to be accomplished.

What to include in a design sprint brief

Your design sprint brief should include the following sections:

• Design sprint challenge: This is a brief description of the problem you are trying to solve during the sprint. It should be clear and concise, and it should be easy for everyone on the team to understand.
• Key deliverables: This is a list of what your team wants to create by the end of the sprint. It could include a prototype, a user flow, or a list of recommendations. Be specific and measurable, and make sure that the deliverables are aligned with the design sprint challenge.
• Logistics: This includes the date, time, and location of the sprint, as well as the names of the attendees and the sprint leader. It is also helpful to include a list of all the supplies that will be needed.
• Approvers: This is a list of any stakeholders who need to sign off on the product before launch. If there are any approvers, be sure to communicate with them early and often to keep them updated on the progress of the sprint.
• Resources: This is a list of the resources that will be needed for the sprint, such as people, time, and materials. Make sure to identify any resources that may be scarce or difficult to obtain, and make a plan for how you will acquire them.
• Project overview: This is a brief overview of the current status of the project, any roadblocks, any early wins, and the estimated launch plan. This information will help your team to understand the context of the sprint and how it fits into the overall project.
• Sprint schedule: This is an hour-by-hour schedule of the sprint, including break times. It is helpful to create a schedule in advance so that everyone knows what to expect and can plan accordingly.

Tips for writing a design sprint brief

Here are some tips for writing a design sprint brief:

• Be clear and concise. Your brief should be easy to read and understand. Avoid using jargon or technical terms that your team may not be familiar with.
• Be specific and measurable. When defining your key deliverables, be as specific as possible. Make sure that you can measure progress towards each deliverable.
• Be realistic. Don’t try to cram too much into your sprint. Be realistic about what your team can accomplish in five days.
• Be flexible. Things don’t always go according to plan. Be prepared to adjust your brief as needed.
• Get feedback. Once you have written a draft of your brief, share it with your team and get their feedback. This will help you to identify any areas that need improvement.

Conclusion

A design sprint brief is an important tool for ensuring that your design sprint is successful. By following the tips above, you can write a brief that will help your team to stay on track and achieve its goals.

Hi again. We’ve covered the
basics of sprint planning, now, let’s build a five-day
design sprint brief. The sprint brief is a
document that you’ll share with all of your attendees to help them prepare
for the sprint. Let’s check out the things that make up a design sprint brief. Start with the design
sprint challenge, this introduces your team
to the sprint objectives. Think back to the cycling
app from earlier. If you created a brief
for that sprint, the design challenge might be, build exciting new features for the cycling app in time for
relaunch later in the year. Next, you need to identify
the key deliverables, meaning what your
team actually wants to create by the
end of the sprint. For the cycling app, you might say that
we want to have a complete prototype that
includes the feature update. Then it’s on to logistics. First, everyone
participating in the sprint needs to know where
the sprint will happen and when it will be held. You also want to list who’s attending and the name
of the sprint leader. Usually the sprint leader is the person who sends out
the brief to the team. But, that’s not always the case. If you want to designate
a sprint leader, you should do it before you
send out the sprint brief. Next, add approvers, got some higher-ups that need to sign off on the
product before launch? This is the place to note it. If your cycling app needs the official approval of
Miss Cycling Enthusiasts, CEO before launching, the sprint brief
should mention it. Your sprint brief should also include a list of resources. For short-term sprints, there’s probably a team already
assigned to this project. For long-term sprints, you may need to create a plan to secure additional resources. For example, with
the cycling app, you might need to
assign resources from engineering to take on the work needed to launch
the new feature. Next, we have the
project overview where you should explain the current status of the project, call out roadblocks
that stand in your way, state early wins
if you have any, and outline the
estimated launch plan. Finally, we wrap it all up
with the sprint schedule, an hour-by-hour schedule of the five-day sprint,
including break times. This lets people know what to expect and gives them time to prep so that you can keep things moving along
during the sprint. And you’re done, you’ve planned your desired sprint and
created your brief. The only thing left to do now is to put the
sprint in motion. If you’re still a
little confused about what goes into the
design sprint brief, you’ll find some great
examples in the readings. Onward. We will learn
about the role of an entry-level UX designer
in the sprint process.

An entry-level designer’s role in a sprint

Design sprints are a five-day process for rapidly prototyping and testing new ideas. They are often used by startups and tech companies to develop new products or features quickly and efficiently.

Entry-level UX designers can play an important role in design sprints by contributing to each phase of the process.

Understand phase

In the understand phase, the team gathers information about the design challenge and the target users. Entry-level UX designers can help with this by:

• Conducting user research, such as surveys, interviews, and usability testing.
• Summarizing the findings of user research and presenting them to the team.
• Identifying any pain points or unmet needs that users have.

Ideate phase

In the ideate phase, the team generates as many possible solutions to the design challenge as possible. Entry-level UX designers can help with this by:

• Participating in brainstorming activities.
• Offering new perspectives and ideas.
• Collaborating with other team members to develop and refine ideas.

Decide phase

In the decide phase, the team selects the best solution to move forward with. Entry-level UX designers can help with this by:

• Voting for the solution that they think has the most potential.
• Providing feedback on the different solutions.
• Helping the team to weigh the pros and cons of each solution.

Prototype phase

In the prototype phase, the team creates a low-fidelity prototype of the solution. Entry-level UX designers can help with this by:

• Designing wireframes and mockups.
• Collaborating with other team members to build the prototype.
• Testing the prototype with users to get feedback.

Test phase

In the test phase, the team tests the prototype with users to get feedback. Entry-level UX designers can help with this by:

• Conducting user interviews and usability testing.
• Summarizing the findings of user testing and presenting them to the team.
• Identifying any areas where the prototype needs to be improved.

By contributing to each phase of the design sprint process, entry-level UX designers can make valuable contributions to the team and help to develop a successful product or feature.

Here are some additional tips for entry-level UX designers who are participating in a design sprint:

• Be open to feedback and be willing to learn from others.
• Be proactive and take initiative.
• Be organized and efficient.
• Be communicative and be able to work well as part of a team.

By following these tips, entry-level UX designers can make a positive impact on the design sprint process and help to develop successful products and features.

Welcome back. Let’s do a quick recap of what
we’ve covered so far. We’ve defined the design sprint, identified the five phases, and explored what goes into
planning a successful sprint. Now you’re probably
thinking, “That’s great, but where does a
newbie UX designer like me fit into all of this?” As an entry-level UX designer, you won’t be running the show, but you’ll play
an important role contributing to every
phase of the sprint. Let’s check out what your
sprint week might look like. When you get to
the sprint space, you’ll find everything
you need to do your work. You’ll have office supplies, water to drink and
maybe some snacks. The sprint leader will welcome everyone and lay out
some ground rules. For example, you
might have to give up your phone and keep your laptop closed until
the end of each day. There might also be
a team icebreaker, like the example
mentioned earlier. Once everyone is settled in, it’s time to get started. The first day is the
understand phase, where you’ll get a clear picture
of the design challenge. There will be plenty
of short talks by experts that are
designed to inspire you. Make note of any
thoughts you have. Phase 2 is the ideate phase. The sprint leader will guide the team through brainstorming
activities to spark creativity and generate
many possible solutions to the design challenge. Your main focus
is coming up with ideas and putting
them out there. Welcome to phase 3,
the Decide Phase. Congratulations, you’re
halfway through the sprint. Your team will decide on the solution with the
greatest chance of success. As a newbie UX designer, you’ll get involved
in every stage of the decision-making process. When potential
solutions fight it out, you’ll vote for the one you
think has the most potential. As you might remember,
at this point, you also need to start
planning ahead for testing or phase 5 of
the design sprint. As an entry-level UX designer, you might help by
scheduling testers, creating survey or
interview questions, and gathering
necessary equipment. Phase 4 is all about creating a prototype
of your product. As an entry-level UX designer, you’ll be actively involved in creating a solid prototype
for users to try out. You’ll ask questions,
offer ideas, and review the
completed prototype. You might also confirm the
test users for phase 5. We’ve made it. It’s test day. The test phase is
the final phase of the process where you put
your prototype to the test. You might be asked to collect user feedback by observing
and interviewing users. This feedback helps
the team know what to revise before
bringing the product to market and that’s it. You’ve learned all about an entry-level UX
designer’s role in the design sprint process. As you reach the design
sprint process finish line, expect to feel like
you just completed an actual sprint
at a track meet. A successful sprint will leave
you tired, but energized, chock full of new ideas, and with a fire in your
belly to get to work. I still remember the first
sprint that I was a part of. I came up with some cool ideas, but also a lot of bad ones. No worries if this
happens to you as well. This is why validating
your ideas with users is baked into the
design sprint process. You’ll have ideas and so
will the rest of your team. Meaning, it doesn’t
rely solely on you. It’s a team effort and by
the end of the process, you’ll have a better sense
of whether your idea is working or not
before implementing it. Coming up, we’ll talk about retrospectives and
why it’s important.

During the decide phase in a design sprint, team members decide on the solution with the greatest chance of success.

True

During the decide phase, the design team evaluates all potential solutions and votes for the one with the most potential.

My name is Jason, and I’m an interaction
designer at Google. The goal of a design
sprint is to take really complex problems and come together with other
people on your team, like product managers, engineers, and marketing, and try to
solve that problem together. You do it over the
course of a week. You do multiple
design activities, from wireframing and prototyping, and then at the end of the
week, test with users. It’s a really good way to get quick feedback and test
those initial hypotheses. That’s why it’s so important to bring people with multiple
perspectives together. Now, you may bring this fresh new
perspective and you may have somebody else
with historical knowledge on this project. But we also are bringing people together from product management and marketing to bring all of
these unique perspectives. I think that this
just proves that sprints at their core
are about inclusivity. We really want to bring people together with
multiple perspectives to surface these
multitude of ideas. It’s always important to understand who your
participants are, and make sure that this overall
experience is thoughtful. You put everyone’s needs first. I think that it’s, in a way, a condensed version of
your user experience job. Where, right now, when you’re
designing a sprint, these participants
are your users, and it’s important to
understand their needs and put them first
when designing a sprint.

Design Sprint Retrospectives: Mastering the Art of Continuous Improvement

You’ve conquered the design sprint! But the journey doesn’t end there. Sprint retrospectives are the final, crucial step to solidify your learnings and propel your future sprints to even greater heights. Let’s dive into the world of retrospectives and unlock their power!

Part 1: What is a Design Sprint Retrospective?

Imagine a sprint as a learning experiment. The retrospective is your chance to analyze the results, celebrate successes, and identify areas for growth. It’s a collaborative reflection held immediately after the sprint, while everyone’s memories are fresh.

Part 2: Why are Retrospectives Important?

• Prevent repeating mistakes: Learn from past experiences to avoid stumbling over the same hurdles in future sprints.
• Boost team dynamics: Open communication and shared learning strengthen collaboration and trust within the team.
• Fuel individual growth: Reflect on your own contributions and identify areas where you can refine your skills and knowledge.
• Empowerment, not blame: Retrospectives are about learning, not pointing fingers. Create a safe space for honest feedback and constructive criticism.

Part 3: Conducting a Powerful Retrospective:

1. Set the Stage:
   • Gather the team immediately after the sprint.
   • Choose a facilitator (ideally the sprint leader) to guide the discussion.
   • Prepare a whiteboard or digital tool for capturing notes.
2. Focus on the Key Questions:
   • What went well? Celebrate successes, big or small. Acknowledge everyone’s contributions.
   • What can be improved? Identify areas where things could have been smoother. Be specific and actionable.
3. Encourage Open Dialogue:
   • Create a safe and inclusive environment where everyone feels comfortable sharing their thoughts.
   • Actively listen to all perspectives without judgment.
   • Use techniques like brainstorming and voting to encourage participation.
4. Capture Key Learnings:
   • Document key takeaways, suggestions, and action items.
   • Categorize them based on priority and potential impact.
5. Close with Action:
   • Agree on concrete steps to implement the identified improvements.
   • Assign ownership and set deadlines for follow-up.

Part 4: Remember:

• Retrospectives are an ongoing process. Use these learnings to inform future sprint planning and execution.
• Focus on continuous improvement. Small, incremental changes can lead to significant progress over time.
• Celebrate the journey. Embrace the learning opportunities and growth potential within each sprint.

Bonus Tip: Explore different retrospective formats and tools to find what works best for your team. Remember, the goal is to create an engaging and productive learning experience for everyone involved.

By mastering the art of design sprint retrospectives, you unlock the true power of iteration and continuous improvement. So, gather your team, embrace the feedback, and watch your design sprints reach new heights!

Here’s some exciting news: You now know how to prepare for and execute a design sprint. There’s just one last thing to do — the sprint retrospective. So let’s check out what a
sprint retrospective is, how it’s conducted, and
why it’s important. We’ve all experienced seeing someone make the same mistake over and over again. Chances are, we’ve sometimes
even been that person. What if there was a way to
stop making mistakes for good? Well, that’s exactly
what retrospectives do. The retrospective is a
collaborative critique of the team’s design sprint. We usually do retrospective
meetings immediately following the sprint so that everyone’s
thoughts are fresh. Retrospective meetings don’t
have any particular agenda. The goal is to make
sure everyone who took part in the sprint has a
chance to give feedback. The two key questions we aim to answer in the meeting are: “What went well?” and “What can be improved?” The person who led the sprint will guide the conversation, and someone will take notes so that the team can use the feedback to make the next sprint even more productive. Retrospectives are super useful. They can help you to
work better as a team, improve how you
communicate with clients, and even point out
areas where you can grow as an individual. Retrospectives are all about
empowering, not shaming. If something didn’t go well, this is your chance
to make sure you have the resources and the tools
to do better next time. One of the most effective
retrospectives I took part in was one where people actually felt comfortable
contributing, and we focused on
continuous improvement. Speaking of retrospectives,
let’s recap what we learned. We now know what a
design sprint is, what’s involved in each
design sprint phase, and how to plan a design sprint. We highlighted where you, as an entry-level UX
designer, fit into the design sprint process, and we learned about the importance
of sprint retrospectives. Next up, we’ll
focus on how to build a professional
presence, but first, we’ve got your next assessment. You’ve got this and if
you need any refreshers, you can always review. Good luck.