►
From YouTube: Collaborating on UX strategy | GitLab Design Talks
B
My
experience
is
really
with
git
lab
is
reading
the
cd,
so
ci
cd
er
the
product
but
prior
to
git
lab
I've
been
mostly
a
ui
engineer.
So
I
was
that
person
that
designed
and
built
the
interface
and
here
get
lab.
I
do
a
little
bit
of
everything
and
it's
super
exciting
yeah,
I'm
looking
forward
to
our
conversation
today,
let's
see
how
what
we
get
from
this.
A
B
I
was
actually
thinking
about
this
this
morning,
like
what
was
this.
This
idea,
this
sense
of
collaboration
to
me-
and
I
always
go
back
to
you-
know
this
idea
that
everyone
can
contribute,
and
I
feel
like
that's
a
lot
of
my
experience
with
collaboration
at
gitlab-
is
that
as
a
designer,
it's
a
blessing
and
a
curse
that
you
have
access
to
everything
and
you
can
figure
out
where
and
how
you
want
to
collaborate,
but
also
learn
from
other
people.
B
So
I
think
a
lot
of
my
experience
with
collaboration
is
really
watching,
what's
happening
around
me
and
figuring
out
yeah,
how
I
want
to
to
be
part
of
the
conversation
yeah,
it's
a
little
bit
of
that,
but
also
figuring
out
on
the
fly.
You
know
with
the
ux
team
and
the
ux
department
changed
so
much
from
when
I
first
joined
in
was
that
2018
and
you
can
really
see
how
yeah
we're
getting.
Is
it's
stronger
with
with
every
iteration
of
what
collaboration
is?
How
do
we?
You
know
what?
A
B
Yeah
wow
are
we
that
many
I
stopped
counting
at
some
point.
It's
very
different
in
the
sense
of
it
was
easier
to
have
an
overview
of
what
was
happening
before
right.
So,
for
example,
if
you
talk
about
pajamas,
so
it
was
easier
to
know
when
a
merger
quest
was
approved
or
what,
what
kind
of
like
the
main
topics
that
we're
discussing
today,
you
really
have
to
choose
your
battles.
B
That's
that's
how
it
feels
to
me
at
least
so
my
role
as
a
designer
really
evolved
around,
where
I
wanted
to
be
inserted,
so
I
started
working
with
two
stage
groups
back
in
the
day.
I
think
we
were
just
my
goodness.
What
were
we?
I
think
we
were
verifying
release
now
we
that
broke
down
into
a
lot
of
subgroups
and
stage
groups
and
direction
etc.
B
A
Nice,
nice,
that's
really
interesting
and
you
and
I
have
had
some
some
discussions
previously
around
ux
strategy
and
you've
got
some
really
interesting
perspectives
on
this.
So
maybe
to
start
out
with
you,
could
you
could
tell
me
about
what
is
ux
strategy?
Maybe
how
is
it
different
from
something
like
product
strategy.
B
Yeah,
I
feel
like
in
my
my
experience.
You
know
talking
about
stage
group
strategy,
not
necessarily
the
ux
department.
Ux
strategy
well
still
overlaps,
but
it's
really
about
the
business
or
strategy,
the
kind
of
like
the
innovation
that
you
want
to
bring
to
the
product,
research,
of
course,
and
how
you
can
design
that
collaboration.
You
can
design
that
strategy
to
your
stage
group
or
to
your
counterparts
so
yeah
we
are.
B
So
for
the
we
had
a
conversation
in
that
one
issue,
maybe
I
should.
I
think
I
have
it
open
here
where
I
say
something
like
when
my
my
counterparts
are
not
strategic.
I
cannot
be
strategic.
Remember.
There
was
a
very
long
comment
on
that
and
I
think
it
goes
back
to
what
ian
said
on
on
his
his
call
with
you
about.
You
know
having
a
shared
vision
and
understanding
that
we
are
working
towards
one
goal.
B
The
main
topics
for
me
was
really
like
the
competitive
analysis
talking
to
our
customers.
Both
internal
and
external
for
release
did
a
lot
of
dog
footing,
so
the
delivery
team
was
one
of
our
main
internal
customers,
so
they
were
pretty
much
yeah
there
when
we
needed
them,
but
also
you
know
just
when
we
wanted
to
validate
our
assumptions
and
yeah
the
scorecards
everything
between
you
know.
You
know
the
drill
all
the
things
that
we
have
in
place
so
far,
but,
most
importantly,
how
do
we
want
to
use
these
tools?
B
B
But
how
can
I
use
these
tools?
You
know
in
a
way,
that's
yeah,
it's
valuable
to
my
team
and
that's
what
I
saw
a
lot
with
the
release
management
team.
So
how
can
we,
for
example,
use
the
product
development
workflow
to
improve
the
ux
and
engineering
collaboration?
That's
also
my
ux
strategy
right.
I
want
to
make
sure
that
my
developers
are
not
being
blocked
by
design
review
because
they
are
empowered
to
make
design
decisions.
B
A
Where
is
the
market
going?
What
are
users
asking
for
and
from
there?
What
should
we
be
doing
in
our
build
tracks
and
in
our
validation
tracks
in
order
to
achieve
the
sort
of
desired
outcomes
that
we're
looking
for
and
then
from
there?
You
can
deploy
like
a
number
of
of
different
tactics
or
activities
such
as
these
think,
big
sessions
and
so
on
in
order
to
sort
of
nudge
you
towards
where
you
want
to
get
to.
B
Yeah
exactly
and
I
think
the
the
role
of
the
designer
or
well
it's
my
role
in
this
whole
process
was
really
to
shadow
product
right.
What
is
my
pm
doing?
What
are
the
market
opportunities?
What
are
the
the
interesting
problems
that
she
thinks
that
we
should
focus
on
based
on
the
level
of
confidence
that
she
has?
You
know.
B
B
You
know
that
and
in
the
end,
it's
really
about
figuring
out
what
works
best
for
you
and
your
team.
Some
teams
are
going
to
have
a
harder
time.
You
know
thinking
about
thinking
or
talking
about
collaboration
or
strategy.
Others
are
just
going
to
you
know,
roll
out
with
the
with
issues
or
with
proposals
for
delivery,
but
it's
a
constant
challenge
and
I
think
that's
at
least
to
me:
that's
why
it's
so
interesting
to
work
at
gitlab,
because
it's
never
the
moment.
You
know
there'll
always
be
a
challenge.
A
A
So
if
I
look
and
invest
area
in
like
a
really
high
value
area,
that
gives
me
more
outcomes
than
if
I
just
invest
in
like
a
little
widget
that
doesn't
really
move
the
needle
on
business
outcomes
or
anything
like
that.
So
I
think
you've
got
a
really
interesting
perspective
on
like
what
ux
strategy
means,
what
ux
strategy
means
in
gitlab.
A
So
what
I
want
to
do
like
for
the
rest
of
the
session
is
maybe
look
at
some
tangible
examples
of
how
you
do
ux
strategy
and
how
that
helps
you
to
share
a
clearer
product
vision
between
you
and
your
team,
because,
as
you
mentioned,
when
your
team
is
strategic,
you
are
strategic.
So
I
think
that's
that's
a
great
mindset
to
have
so
so
yeah
tell
me
what
what?
What
can
we
do
to
to
to
be
more
strategic
with
our
designs.
B
Yeah,
I
think,
to
start,
I
would
say
that
this
is
also
related
to
you
know
the
people
aspect
of
how
you
function,
how
your
team
functions
and
how
like
what
you
understand
of
strategy.
I
think
also
in
that
one
comment
I
talked
about
now.
If
my
team
is
just
talking
or
my
pm
or
my
counterparts
are
very
tactical
and
I
want
to
solve
just
the
problem
of
today,
then
I'm
going
to
spend
most
of
my
time
selling
design
right.
B
So
I
think
my
experience
and
then,
if
I
can
share
the
tip,
is
to
start
with
the
conversation
you
know
about.
Why
is
understanding
or
creating
or
just
having
a
ux
strategy
or
having
a
shared
vision
about
what
you
share
understanding,
maybe
not
even
share
vision,
just
understanding
the
problem,
why
that
is
so
important
and
then
break
it
down
into?
How
do
you
understand
that
problem?
B
What
do
you
need
to
do
right,
clear,
create
a
clear
plan
because
indeed,
it's
a
very
attractive
way
to
say
very
sexy
way
to
say
yeah
ux
strategy,
but
what
is
that
on
a
day-to-day
right?
So
if
I
can
think
about
some
of
the
examples
and
things
that
yeah
I
was
able
to
apply
with,
my
team
was
really
shadowing.
Pm
right
is
the
pm
involved
in
I
don't
know
a
customer
call,
it
doesn't
have
to
be
about.
B
I
don't
know
opportunity,
canvas
or
a
more
formal
research
is
my
pm
talking
to
someone
cool.
I
want
to
be
there
right
and
most
likely
your
pm
is
not
going
to
ask.
I
do
you
want
to
be
in
the
call.
Do
you
want
to
be
involved?
Is
that
interesting
to
you
but
find
ways
to
know?
What's
going
on
and
kind
of
cut,
some
steps
you
know
in
in
the
process
be
in
the
shadow
ask
about
questions
they're
not
yet
on
the
table
and
just
make
yourself
available.
B
A
B
Gets
lost
and
when
you
have
the
hands-on
experience
in
the
hands-on
contact
with
that
type
of
information,
whereas
that
customer
feedback
or
just
a
insight
that
you
had
with
a
rent
in
a
random
conversation,
it
takes
time
for
us
to
catch
up
in
that
conversation,
so
I'll
definitely
say
be
involved
and
try
to
understand
the
bigger
picture
so
participating
on
those
calls
or
even
if
you
cannot,
because
time
zones.
But
you
know
draft
a
plan
for
the
interview
together.
Just
read
the
answers
or
the
questions
that
the
pm
is
thinking
about.
A
A
Interviews,
I
found
was
really
useful
for
like
finding
alignment
with
with
the
pm.
So
even
if
you
can't
necessarily
participate
synchronously,
you
can
still
watch
the
video
and
then
in
some
way
debrief
with
the
pm
and
that
just
that
activity
of
collect
like
that
activity
of
communicating
with
your
pm
is,
I
found
really
valuable.
B
Exactly
and
I
think
it's
going
back
to
two
rituals
right
if
you
know
that
that's
a
standing
topic,
if
not
that's
part
of
your
criteria,
like
your
success
criteria
as
a
designer,
make
that
a
standing
conversation,
don't
ask,
you
know,
wait
for
someone
to
kind
of
bring
that
to
the
table.
So
one
thing
that
jackie
and
I
did
yeah
pretty
much
every
month
or
whenever
we
had
the
ad
hoc
customer
calls-
is
that
in
our
weekly
calls.
What
have
we
learned
today
right?
B
Our
teams,
our
things
with
engineering,
also
had
that
this
is
what
I
learned
today.
This
is
what
I
learned
from
my
customer
and
we
came
into
the
conversation
in
the
call
thinking
that
I
don't
know
people
whatever
random
example.
They
want
to
configure
their
secrets
using
gitlab
variables,
but
in
the
user
interviews
they
say
no.
B
We
want
to
have
a
complete
different
section
in
the
product
for
that,
because
blah
blah
blah
so
just
bring
that
one
liner
that
one
inside,
because
that's
the
information
that
usually
we
share
in
comments
right
in
the
issues,
those
long
tracks.
This
is
the
information
that
you're
gonna
have
to
refer
over
and
over
and
over
to
so
making
that
information
available
firsthand
to
people
it's
really
powerful
and
also
what
I
really
appreciate
it
is
to
be
included
in
the
direction
changes.
B
B
So
I
know
that
a
change
in
the
direction
page
is
going
to
be
is
going
to
mean
a
change
to
my
ux
priorities
if
the
product
they're
actually
changing
the
wax
direction,
is
changing
so
keeping
track
of
that
asynchronously
or
at
least
having
to
wait
once
a
week
to
talk
about
that
was
a
it
wasn't
working
for
me.
So
I
asked
jackie
every
time
you
update
something.
B
I
don't
need
your
it's
not
from
my
approval,
it's
just
for
my
awareness
so
that
I
know
how
you're
updating
things
or
where
and
how
that
affects
my
design
plan.
So
it
it's
really
about
that
shadowing,
but
also
that
exchange
of
information
that
you
can
translate
as
collaboration.
But
I
think
it's
more
like
a
partnership
between
you
know.
Everyone
involved
in
building
a
beauty
of
future
building
a
product,
so
it
kind
of
goes
that
way
in
my
head.
A
I
love
that
I'm
gonna,
I'm
gonna,
steal
that
and
put
that
into
my
team
meetings
from
now
on
as
well.
I
think
that's
that's
a
really
good
thing.
Yeah,
I
think
of
team
rituals
are
like
basically
shared
habits
that
you
have
between
your
team
that
try
and
point
you
in
a
particular
direction
that
you're
trying
to
achieve
so
so
what
are
some
more
like
team
rituals
or
team
habits
that
you
and
your
team
have
that
that
help
you
to
be
more
strategic
that
help
you
to
collaborate
more
effectively.
B
Yeah
we
have
the
think,
big
sessions
where
we,
you
know
anyone
could
just
bring
a
problem
and
talk
about
that
and
really
let.
For
example,
the
developers
inform
the
decisions,
so
I
had
a
conversation
with
a
couple
of
designers
in
the
past,
where
there
is
always
a
question
like
how
much
should
the
developers,
our
engineers,
you
know,
influence
a
feature?
How
how
opinionated
should
people
be
I'm
from
the
opinion
that
they
should
be
operated?
We
are
all
experts,
whether
you
like
it
or
not.
We
all
use
this
tool.
B
We
all
use
this
platform
and
we
might
not
know
best.
You
know,
because
sometimes
we
are
not
exactly
the
persona,
but
I
think
it's
so
powerful
that
we
all
can
bring
some
perspective
to
what
we're
building
here
so,
for
example,
having
these
sessions
or
having
this
structure
moment
where
we
can
say.
I
want
to
discuss
this,
because
I
have
all
these
ideas
for
how
this
feature
should
work,
it's
so
powerful
in
the
sense
that
we
can
work
on
a
proposal
together.
B
At
least
my
my
opinion
helps
people
understand
the
role
of
designing
in
the
development
process
right.
Is
that
we're
here
to
to
bridge
the
gaps
and
to
link
product
engineering
interface
whatever,
but
we're
here
to
understand
everyone
and
kind
of
come
up
with
oh
yeah.
This
is
everything
I
heard.
This
is
how
I
think
we
should
solve
the
problem.
So
this
is
one
of
the
actionable
insights.
If
I
can
can
say
like
that
and
yeah-
and
I
see
I
know
the
teams
are
doing
it
did
this
differently.
B
I
know
I
think
soon
june
she
does
async
design
reviews.
She
has
an
issue
where
she
poses
a
proposal
and
then
the
developers
go
into
comments
in
ci
cd.
Some
of
the
girls
are
also
trying
to
do
the
same.
So
I
think
it's
so
important
to
just
have
that
one
channel.
You
know
to
communicate
ideas
and
validate
that
people.
B
B
I
think
we
are
all
very
great
at
what
we
do,
but
how
can
we
yeah
have
a
shared
share
items,
for
example
settings
or
navigation
things
that
are
common,
so
everyone
not
just
solve
those
problems
but
create
the
yeah
the
platform
where
the
designers
can
make
room
to
collaborate
to
high-level
things.
I
think
that's
a
challenge
that
I
see,
because
we
are
all
so
busy
and
we
all
have
these
problems
that
yeah
exist
and
that
affect
everyone
and
create
yeah.
B
That
kind
of
that,
I
don't
know
just
an
opportunity,
is
to
solve
these
problems
together.
I
think
that's
a
at
least
that
since
the
icd
that's
a
big
thing,
and
I
see
that
as
a
pattern
across
other
teams,
but
we'll
get
there,
I'm
super
confident
on
yeah
our
teams
and
new
videos
and
everything
we
do
so,
let's
see
what
happens
next
year,
let's
see
how
we're
going
to
be
solving
these
problems.
Let's.