►
From YouTube: UX Showcase How to make design a team sport
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
A
So
the
makings
of
it
of
a
team
sport.
The
first
thing
is
that
we
in
in
a
team
spot
you're,
obviously
working
in
teams
and
here
similar
to
here
at
gitlab.
A
We
work
in
teams
as
well,
which
has
helped
us
achieve
a
lot
of
success
and,
as
we
know,
working
in
teams
can
get
complicated
and
one
of
the
things
I
asked
myself
is
what
makes
a
a
great
team
and,
as
you
can
tell,
I've
been
watching
too
much
all
or
nothing,
and
one
of
the
ones
I
watched
was
the
main
city
one,
because
Pep
Guardiola
is
one
of
my
favorites
football
coaches.
A
Although
he's
not
coaching
my
team
and
he
says
for
a
successful
team,
everyone
has
to
contribute
the
team
comes
first
and
not
the
individual,
and
what
years
of
research
has
shown
that
the
four
main
things
that
make
a
team
successful
are
one
a
compelling
direction
as
to
a
strong
structure,
supportive
context
which
we,
which
we
all
have
here
at
gitlab,
and
the
third
is
having
a
shared
mindset
and
I'll,
be
speaking
on
the
on
the
last
one,
which
is
having
a
shared
mindset.
A
So
having
a
part
of
having
a
mind,
a
shared
mindset,
is
you
know,
having
things
like
single
source
of
Truth
and
and
some
of
the
things
that
are
a
part
of
the
culture
here
at
git,
lab
and
well
I
I
used
to
have
weekly
design
sessions.
I
mean
weekly
session
catch-up
sessions
with
my
pm,
and
we
would
discuss
a
lot
of
design
related
issues
or
do
a
walkthrough
of
wireframes,
and
sometimes
they
would
turn
into
a
code
design
session
where.
B
A
Both
trying
to
design
and
if
even
though
I
was
in
a
good
good
place
regarding
the
context
of
what
I
was
designing,
I
noticed
that
some
of
my
designs
had
some
pretty
major
blind
spots,
and
and
so
we
decided
to
start
extending
the
whole
collaboration
session
to
the
whole
team.
A
So
at
first
with
Envision.
It
is
just
me
the
the
PM
and
the
front
end
designer
and
and
and
we
called
it,
the
pair
paired
design
sessions
and
pet
design
sessions
taken
from
pair
programming,
which
is
the
practice
of
Perry,
of
pairing
up
to
work
on
programming
tasks
and
the
concept
of
peer
programming
is.
Is
that
like?
A
It
involves
a
lot
of
collaborative
efforts,
a
lot
of
communication
and
the
idea
there
is
to
have
a
a
driver
or
a
navigator
who
who
communicates,
discusses,
approaches
and
helps
to
solve
issues
that
might
be
difficult
for
a
simple
for
a
single
developer
to
work
on
and
which,
which
was
great
for
our
area,
because
we,
you
know
as
I
as
I
realized
like
it's.
It's
a
very
technical
area
like
there's
so
many
nuances
and
having
the
opportunity
to
pair
up
with.
A
Pm
and
and
if
a
frantic
designer
and
a
back-end
developer
at
times
was
what
was
really
helpful
in
moving
forward
with
certain
issues
and
studies
support.
This
I
try
to
look
at
some
of
the
studies
that
are
out
there.
There's
this.
A
These
two
two
main
outcomes
that
I
I
I
I
wanted
to
highlight,
and
one
of
them
was
that,
like
in
in
one
study,
they
used
interviews
and
controlled
experiments,
and
one
of
the
benefits
was
that
pair
programming
decreased
development
Time
by
about
15,
and
it
also
improved
the
design
quality.
A
It
also,
it
also
improved
the
number
of
defects
and
what
one
of
the
things
that
was
highlighted
was
that,
like
this
form
of
working,
was
significantly
enjoyable
than
than
other
ways,
ways
of
working
and
in
in
one
of
the
studies
they
even
found
that
like
teams,
who
did,
who,
who
worked
in
using
pair
programming,
had
greater
confidence
in
the
solutions
that
that
they
delivered.
A
So,
even
though
we
didn't
know
at
the
time,
but
in
in
hindsight,
when
I
go,
look
at
some
of
the
studies,
I
I
see
some
of
the
results
that
we
have
managed
to
achieved
and
what
we
have
achieved
in.
In
the
short
time,
we've
been
experimenting
with
this,
which
has
been
about
two
Milestones
we've
managed
to
work
through
one
one
design,
which
was
for
the
environments
page.
A
We
managed
to
finish
a
user
Journey
that
we
we've
been
meaning
to
work
on
for
a
a
long
time,
because
we
had
everyone
there,
and
also
one
of
the
things
was
that
we've
started
to
have
more
interest
in
in
design
from
the
rest
of
the
team,
and
even
the
rest
of
the
team
has
been
asking
how
they
can
join
the
sessions
and
which
has
led
to
a
challenge
to
me
rather
to
try
and
improve
the
whole
session
and
how
how
how
we
can,
how
we
have
it
and
so
moving
forward
with
trying
to
improve
how
we
collaborate
we're
going
to
start
experimenting
with
design.
A
Sprints
that'll,
hopefully
bring
a
little
bit
of
more
structure
to
to
the
sessions
in
terms
of
like
how
it
how
we
work
together
with
in
Discovery
and
all
all
the
way
to
delivering
the
the
final
solution,
and
one
of
the
things
that
we
aim
to
achieve
is
like
increasing
the
levels
of
participation
for
engineers
at
the
validation
phase
and
also
increasing
the
levels
of
participation
for
design
at
at
the
build
phase
as
well,
because
we
will
just
be
collaborating
more
closely.
A
So
we
have
team
members
which
are
in
all
time
zones,
so
we're
busy
trying
to
think
of
ways
to
make
decisions
more
inclusive,
maybe
alternating
between
one
times
on
this
week
and
another
time
zone
or
looking
at
other
ways
how
we
can
make
it
more
inclusive,
which
is
which,
which
we're
still
thinking
about
and
then
one
one
idea
that
I
that
I
I
thought
of
was
especially
since
I
see
that
some
of
the
configure
features
into
intersect
with
other
product
areas
was
invite
inviting
guest
designers
to
some
to
the
core
design
sessions
and
trying
to
see
how
how
how
that
can
can
improve
the
design
process
and
the
outcome
of
the
whole
process
so
yeah.
B
C
I
am
still
to
type
like
I'm,
yet
to
type
that
here,
but
I
am
interested
in
knowing
Ali.
Like
do
you
plan
to
take
like
do
you
have
any
plans
to
evolve
your
process
to
be
more
asynchronous
I
like
right
now
the
collaborative
sessions
that
you
are
doing.
It
appears
that
they
are
they're
happening
in
sync
and
I
would
like
point
out
that
not
many
teams
here
have
that
they
are
lucky
enough.
A
C
A
Yeah
so
we've
we've
tried
to
have
an
an
agenda
and
try
to
share
a
video
of
the
session,
so
we
we
do
record
the
sessions.
A
A
Maybe
one
of
the
things
we
could
do
is
maybe
have
someone
on
on
the
team
facilitate
that
who's
in
the
other
time
zone,
but
I
I
haven't
thought
that
far
about
it
I
mean
we
were
just
doing
what
what
we
can
for
now,
but
there's
certainly
ways
that
I
think
creative
ways
we
can
think
about
to
make
the
sessions
more
inclusive.
A
Besides
just
sharing
video
and
agendas.
C
Right
so
something
that
we
have
been
trying
a
lot
I
mean
we've
been
practicing
a
lot
in
our
team,
our
async
discussion
issues
so,
for
example,
creating
an
issue
only
for
discussions
to
have
around
a
particular
topic
and
sort
of
like
taking
a
control
of
the
conversation
by
starting
threads
about
the
different
aspects
of
the
topic
that
we
want
clarification
around
yeah
and
that's
kind
of
preferred
by
most
of
our
team
members.
A
Sure
yeah,
that's
that's
actually
sounds,
sounds
good
and
do
you
get?
Are
you
happy
with
the
levels
of
participation.
C
Oh
yeah
so
like,
if
I
need
any
urgent
responses
on
that
I
make
it
a
point
that
I'm
also
broadcasting
the
links
for
that
issue
on
slack
channels
on
the
relevant
slack
channels,
because
that
gives
more
visibility
to
the
issue
and
yeah.
The
participation
has
been
really
good
on
those
in
the
team.
A
Cool
I
will
definitely
incorporate
them.
D
That
also
really
helps
that,
like
hey
I,
need
your
feedback
by
the
state,
so
that
like
they
could
be
also
focusing
on
not
just
ignoring
the
notification
yeah
I'll
just
do
it
later,
so
maybe
also
you
could
try
out
that
the
expected,
like
feedback.
You
can
set
a
due
date
here.
Please
responded
to
this
issue
by
this
thing.
A
Yeah
and
by
the
way,
I'm
not
saying
we
work
on
all
issues,
we
just
choose
like
issues
that
we
think
are
a
little
bit
complex
and
we
yeah.
We
have
a
lot
of
those.
Unfortunately,.
E
Write
stuff
yeah-
this
is
really
great,
definitely
has
encouraged
me
to
reach
out
to
developers
more
in
the
brainstorming
phase.
E
I
guess
my
question
is
around
like
what
Cadence
have
you
found
works
best
and
you
know
I
think
there's
always
this
concern
for
some
designers
that
worrying
about
implementation
capabilities
can
restrict
like
pushing
the
designs
forward
a
little
bit.
So
I'm
also
wondering
if,
if
you've
encountered,
that
at
all.
A
So
we've
been
trying
to
do
it
once
a
week
and
then
we.
B
A
A
Put
some
structure
to
say
like
in
this
45
minutes,
will
try
and
achieve
this
specific
thing,
but
for
now,
we've
just
tackled
two
issues
that
we
try
to
experiment
with
this
method
and.
A
E
A
Yes,
it
has,
it
has
come
up
so
right
now
we're
working
on
trying
to.
A
Like
kubernetes
data
and
some
of
some
of
the
components
we
have
don't
necessarily
like
fit,
and
and
so
that
that
becomes
a
constraint,
but
for
now
we've
just
tried
to
we've
agreed
that
we'll
go
with
a
boring
solution
and
try
and
use
whatever
we
have
and
in
future
improve
that.
So
that's
that's
something
we
agreed
on
up
front
so
try
to
be
boring
as
much
as
possible.