Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranî)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
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, a bottle of water, and maybe some snacks.
The sprint master 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.
And then you'll get down to it. 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.
So, make note of any thoughts you have.
Phase 2 is the ideate phase.
The sprint master will guide the team through brainstorming activities to spark
creativity and generate tons of 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 that 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 sprint.
As an entry level UX designer, you might help by scheduling testers,
creating survey and 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.
As a newbie designer, 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, with a fire in your belly to get to work.
I still remember the first sprint 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.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.