►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
from
me
so
I'm
Mario,
brownie,
I'm,
the
senior
product
designer
in
configure
and
today
I'm
gonna,
present
a
very
exciting
piece
of
work
with
it
for
configure,
which
is
running
a
design
sprint,
so
I
hope
I
have
the
time,
because
it's
quite
a
lot
of
information
so
we'll
see
I
do
have
five
extra
minutes
so,
starting
with
what
is
a
design
sprint
for
the
audience
that
is
not
familiar.
A
Maybe
outside
this
theme
as
well,
so
the
design
sprint
was
developed
by
Google
Ventures.
It
was
a
method
like
a
workshop
to
optimize
the
product
development.
It
is
a
five
day
process.
We
change
that
answering
critical
business
questions,
so
the
aim
of
the
Sprint
is
within
five
days
to
work
on
a
problem,
create
a
solution
create
a
product
for
that
solution
and
then
test
it
with
customers.
A
This
workshop
is
supposed
to
happen
in
Institute,
so
everybody
in
the
room
without
any
technology
for
five
days
to
work
collaboratively
on
the
problem
and
the
design
solution.
In
our
case,
obviously
that
was
not
feasible,
so
we
needed
to
come
up
with
an
alternative
for
a
remote
sprint
which
I
will
talk
about
later,
so
how
we
went
on
about
it.
So
usually
all
the
tasks
are
sync,
and
in
our
case
we
decided
to
do
some
tasks
acing
so
when
to
run
a
design
sprint.
A
So
this
is
a
copy
pasted
from
Wikipedia
yay,
so
when
launching
any
product
or
service
extending
and
extinct
an
existing
experience,
revising
the
user
experience
of
an
existing
NPC
or
MVP,
as
it's
called
in
other
companies,
adding
new
features
and
functionality,
opportunities
for
improvements
of
a
product
of
opportunities
for
improvement
of
a
service
and
supporting
organization
in
the
information.
So
in
our
case
it
was
mostly
as
trap,
strategy
and
vision
direction,
which
was
a
result
of
many
well
a
couple
things
not
many
things.
A
Then
the
stage
was
the
two
groups
were
invited
again
into
one
group
and
the
old
PM
moved
to
create,
and
then
you
being
p.m.
took
over
the
entire
group
also
Tori
moved
out
as
the
product
designer
a
month
as
well,
so
I
remained
just
a
single
product
designer,
so
the
new
PM
was
not
really
happy
with
the
direction
of
several
of
the
stages
categories
and
he
wanted
a
more
concrete
direction.
Also,
there
were
various
vision.
A
A
So
moving
on
to
planning
the
Sprint
so
getting
started
for
the
Sprint,
the
first
steps
was
a
collaboration
between
myself
and
the
product
manager.
After
deciding
the
Sprint
focused,
we
have
to
decide
who
will
participate
in
this
print,
so
the
design
sprint
are.
The
methodology
defines
that
there
should
be
from
four
I
think
to
eight
or
ten
participants,
including
a
facilitator
who
in
this
case
was
me
and
then
it
would
be
good
to
have
mixed
disciplines,
so
people
from
different
backgrounds
who
are
knowledgeable
about
the
topic
and
can
bring
their
insights
from
different
perspectives.
A
In
our
case
it
was
a
solution
architect,
so
this
person
has
direct
contact
with
customers
and
brings
the
business
knowledge
and
in
our
case
it
would
be
pitied
her
people
in
similar
time
zones,
which
was
not
the
case
for
this
print.
But
if
it
worked
out
fine,
so
the
next
thing
to
design
is
determine
when
this
print
is
gonna
take
place
and
for
to
in
order
to
decide
that
we
should
make
sure
there
is
enough
time
to
prepare
the
agenda
and
material.
A
We
had
I
think
it's
really
pieces
of
homework
on
separate
days,
so
really
needed
to
plan.
For
that,
too,
the
next
step
was
to
create
an
epic
where
Victor
and
I
started
collaborating
on
the
specifics
of
this
print,
and
also
it
was
an
opportunity
to
let
the
participants
know
about
this
print
first
of
all,
and
then
also
they
could
keep
track
of
the
activities
and
give
them
a
visibility.
A
So
we
were
quite
transparent,
so
I
have
created,
I
have
linked
here,
the
epic
to
this
print,
which
includes
all
the
issues
and
materials.
In
case
you
want
to
check
them
out,
so
the
next
steps
for
planning,
I've
split
them
into
two
columns
here
so
I
took
some
tasks
on
myself
and
Victor
took
some
other
tests
for
him
to
do
so.
A
I
started
by
reviewing
the
past
remote
workshops
that
have
been
done
in
Hitler
and
I
found
the
monitoring
team
remote
of
site
very
valuable,
and
especially
the
feedback
issue
where
I
could
see
what
could
be
improved
and
what
feedback
or
distance
gave
about
the
remote
outside.
So
the
main
thing
I
did
from
there
was
a
long.
Video
calls
were
not
really
fruitful
and
they
were
tiring
people
a
lot.
A
So
this
is
one
of
the
main
reasons.
I
decided
to
switch
some
some
sync
activities
to
async,
then
the
next
thing
I
did
was
to
refresh
my
memory
for
the
sprint
process.
So
during
the
sprint
each
day
has
specific
activities.
So
I
took
all
the
activities
with
the
help
of
Justin
as
well,
and
instead
of
a
five-day
sprint,
we
decided
to
afford
a
sprint,
because
some
tasks
would
be
async.
A
Also,
we
took
all
the
activities
and
then
decided
which
day
each
activity
would
happen
and
then
I
started
repairing
the
agenda
so
that
we
could
follow
them
with
the
creation
of
the
material
based
on
the
agenda,
then
I
had
to
think
about
what
tools
we
were
gonna
use
for
this
print,
so
that
I
could
let
the
participants
know
what
I
needed
to
get
access
to
or
have
in
hand
for
this
print
week
and
finally,
I
added
all
the
information
in
the
epic
I'm
like
the
most
work
in
progress
for
whatever
was
not
finalized.
A
Yet
so,
while
I
was
doing
that,
Viktor
was
working
on
inviting
the
participants
he
was
responsible
for
scheduling
the
meetings
in
the
calendar.
Also,
the
participants
asked
him
to
all
also
add
the
time,
their
calendars
for
the
homework
activities
and
finally,
Viktor
collected
the
existing
customer
feedback
and
issues
that
have
been
created
as
bad
improvements,
so
that
we
could
affinities
them
and
add
them
to
the
material
misprint.
A
So
next
preparing
the
sprint
materials,
so
the
first
thing
I
did
was
create
a
Google.
Form
I
saw
this
as
an
opportunity
to
introduce
the
participants
to
the
design,
sprint
process
and
the
scope,
the
ground
rules,
the
agenda
basically
and
also
the
homework
that
they
needed
to
do
and
I
also
included
a
questionnaire
in
the
Google
form,
which
would
serve
as
the
expert
interviews
that
are
supposed
to
happen.
A
In
the
first
day
of
the
sprint,
then
Justin
helped
me
create
the
mural
board,
which
are
added
here,
is
a
screenshot
and
before
the
spring
started,
I
Affinia
ties
the
input
from
the
expert
interviews
and
I
added
them
in
the
neural
board.
As
the
map.
Sorry
I
cannot
go
into
the
details
of
the
spring,
because
I
see
I'm
already
doing
really
badly.
With
time,
then
I
created
a
video
so
that
on
day,
it's
really
normal
I
think
which
we
did
on
day.
Two.
A
There
is
a
solution
sketch
exercise,
so
each
participant
trade
solution
to
a
sketch
and
since
our
participants
were
quite
technical,
I
thought
that
might
need
some
help
with
sketching
their
solution.
So
I
created
this
video
I've
linked
it
here
and
then
get
love
issues.
So
it's
very
helpful
to
have
an
issue
for
each
spring
day
so
that
we
can
up
their
material
as
well
on
top
of
mural
and
also
outlined
activity
for
future
use
or
review
or
visibility.
A
Google
Drive
folder,
where
the
participants
could
drop
their
artifacts.
A
So
the
sketching
exercise,
for
example,
was
anonymous,
so
the
facilitator
supposed
to
blowed
all
the
sketches
or
put
them
in
a
board
on
the
actual
walls
in
an
actual
sprint
so
and
then
recruiting
but
I
suppose,
that's
user
participants,
user
testing
participants
requests
so
at
the
final
day
of
the
sprint,
the
outcome
so
the
artifact
of
the
spring
supposed
to
be
tested.
So
we
needed
to
recruit
the
users
as
soon
as
we
knew
who
the
personas
we
would
focus
on
where.
A
But
this
was
part
of
the
sprint
and
a
feedback
issue
so
that
we
could
get
feedback
on
this
print.
So
this
print
week
very
fast
before
the
spring
started,
the
participants
had
homework
to
create
lightning
talks.
So
each
participant
had
to
create
a
five-minute
video
explaining
well
explaining
what
their
perception
of
the
product
is,
who
their
main
user
they
think
is
and
who
the
ideal
user
would
be
then
discuss
other
products
or
solutions
that
inspire
them
or
they
find
relevant
to
us.
A
And
then
all
the
participants
would
watch
each
other's
videos
and
write
notes
in
the.
How
might
we
format
and
send
them
to
me
so
then
I
added
alter?
How
might
we
in
the
neural
board
and
their
next
homework
task,
was
to
vote
on
to
how
my
please
so
we
had
a
good
starting
point
already
in
day,
one
because
all
this
part
of
the
board
was
already
filled.
A
So
when
we
start
with
the
Sprint,
we
reviewed
how
my
tweeze
and
we
worked
on
the
map
which
came
out
of
the
expert
interviews,
and
then
we
collaborated
to
refine
it
a
bit
and
in
this
stage
I
don't
know
if
it's
feasible,
I
think
it's
not.
We
also
focused
on
which
part
of
the
map
were
mostly
interested
in.
A
A
Then
they
went
away
and
they
had
the
exercise
of
creating
the
four
part
concept
sketching
which
they
sent
to
me
and
I
upload
it
for
day
two.
So
when
we
started
big
two,
we
started
with
going
through
with
a
vote.
Each
person
went
through
all
the
sketches
and
they
voted.
Then
the
decider
take
the
final
vote,
and
this
is
how
the
solution
concept
is
decided
and
following
that
all
the
participants
worked
on
the
user
test
flow.
A
So
these
are
steps
towards
the
decided
solutions
that
a
user
would
take
to
reach
their
goal
and
finally,
based
on
the
user
test
flow
again,
all
the
participants
together
create
the
storyboard
that
was
day
three
of
the
workshop
I
of
the
spring.
So
here
we
first
started
with
describing
the
storyboard
steps
with
text
which
I've
been
converted
into
very
rocks
cheese,
and
then
we
had
another
session
where
they
gave.
Everybody
gave
me
feedback
on
the
sketches.
A
A
So
this
is
a
great
direction
for
companies
and
it's
good
that
it
came
out
of
the
team
as
a
whole,
so
everybody's
on
board
the
store
and
a
storyboard
that
shows
the
basic
steps
for
the
solution
concept,
so
the
basic
idea
and
we're
currently
testing
the
storyboard
with
users
so
learnings
and
next
steps.
What
worked
well.
A
Also,
we
talked
to
our
long
sing
sessions,
but
they
worked
really
well
because
we
had
specific
tasks,
we
kept
the
timings
and
they
didn't
really
drag.
So
it
was
very
interesting
and
also
we
had
timely
breaks,
which
I
understand
it
is
very
important
in
video
calls
sorry
and
what
can
be
improved.
There
is
a
open
feedback
issue.
I,
don't
think
many
people
have
commented
yet,
in
my
opinion,
and
if
we
had
worked
on
the
map
better,
the
spring
would
have
a
very
focused
because
we
had
a
quite
broad
focusing
day
too.
A
A
Finish:
the
user
testing
and
analyze
their
results
to
see
how
the
idea
is
perceived
and
depending
on
that
plan,
the
upcoming
work
I
would
like
to
write
the
blog
post
for
this
print
and
also
Justin
is
aiming
to
have
the
designs
pretty
country
to
the
handbook
and
create
an
issue
template
for
it.
So
if
he
needs
help
waiting
to
help
and
special
thanks
to
just
for
helping
with
facilitating
and
this
preparation
and
to
all
the
participants
for
their
awesome
participation
and
on
time,
thank
you.