►
From YouTube: UX Showcase: It's never too late to pivot
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
Okay,
hey
everyone.
My
name
is
austin
a
senior
product
designer
here
at
git
lab.
I
work
on
the
compliance
group
and
today
I
want
to
do
a
little
presentation
on
the
subject
of
it's
never
too
late.
To
put
it,
so
maybe
it's
a
little
bit
relevant
to
to
like
daniel's
point
with
the
previous
presentation
so
to
help
set
the
stage
here
a
little
bit,
I'm
going
to
walk
through
an
illustrative
example
that
kind
of
will
help.
A
A
It
gives
us
feedback
on
things
that
we
need
to
fix
before
we're
ready
to
merge,
but
that's
not
exactly
how
other
companies
do
things.
So
it's
worth
considering
that
for
other
companies
or
customers
or
users
of
gitlab
that
they
don't
have
a
gitlab
bot
kind
of
coaching
them
through
how
to
get
a
merge
request
to
completion.
A
There
are
instances
where
they're
using
external
services
to
make
sure
that
there's
some
validation
checks
in
place
to
ensure
that
the
right
code
is
being
merged
to
production,
which
is
requiring
developers
or
people
to
look
outside
gitlab
to
verify
that
things
are
good
to
go
before
they
hit
the
merge
button,
so
that
was
kind
of
the
problem
that
was
set
in
front
of
me
to
address
about
this
time
last
year,
and
so
honestly,
I
thought
I
had
the
right
solution.
I
had
gone
through
the
validation
track.
A
I
had
verified
our
ideas
around
this
problem
with
customers.
We'd
heard
good
feedback
from
people
collaborating
in
the
issue,
and
I
felt
pretty
confident
by
the
end
of
2020
that
we
were
ready
to
move
into
the
build
track
so
solid
shelf
for
a
bit
sat
there
for
a
few
months,
and
eventually
we
got
to
the
point
where
we
were
ready
to
start
building
it.
A
A
Building
I
kept
in
touch
with
code
reviews
specifically
because
this
was
really
impactful
on
the
merge
request,
experience
itself
and
I
learned
some
new
things
that
changed
my
perspective
on
whether
or
not
this
was
the
right
solution,
and
so
at
some
point
we
had
to
make
some
painful
decisions
to
decide
to
pivot
away
from
what
we
were
building,
and
this
is
kind
of
a
story
of
how
we
progressed
through
that.
So
as
we're
going
into
13
9
13
10,
we've
got
all
these
implementations.
A
She's
planned
we're
working
on
it
and
kai
was
kind
enough
to
bring
back
some
feedback
to
help
me
understand
what
the
intent
of
approval
rules
were
supposed
to
be.
So
in
my
head,
I
was
thinking.
Oh,
let's
do
the
most
like
minimal
thing:
let's
reuse,
an
existing
feature,
tuck
my
new
thing
in
there
and
it'll
be
great
because
in
my
head,
I'm
thinking
this
is
like
an
approval
rule.
It's
essentially
giving
you
a
way
to
prove
whether
or
not
merge
request
is
ready
to
move
forward.
A
So
kai
was
helping
me
better
understand
that
it's
not
exactly
the
same.
Like
you
take
action
in
a
merge
request
to
approve
something
specifically
and
that's
not
the
same
as
like
doing
a
check
for
something
on
like
ci,
where
it
needs
to
pass
or
fail.
So
really
we
needed
to
kind
of
go
back
to
the
drawing
board
about
the
solution.
In
the
first
place,
we
knew
that
functionally.
It
was
kind
of
solving
the
problem.
A
It
was
helping
expose
this
external
system
telling
you
whether
or
not
something
had
passed
or
not,
but
the
solution
of
exactly
how
it
was
designed
and
where
it
was
landing,
wasn't
great.
So
we
had
a
number
of
discussions
happening
in
a
gitlab
issue
and
epic
once
we
had
reached
like
a
pretty
long
thread.
We
said:
okay,
we
need
to
have
a
sync
meeting
on
this,
so
that's
where
pedro
really
helped
me
bring
things
back
into
focus
by
reminding
me
to
keep
my
horizons
broad.
He
was
helping
me
better.
A
Look
at
some
of
the
competitor
products
that
we
have
surrounding
this
feature,
and
it
was
pretty
obvious
that
they
were
doing
something
similar,
which
helped
give
us
some
inspiration
for
how
we
could
better
integrate
this
feature
into
the
lab
itself
and
then
from
there.
We
really
focused
on
how
we
could
iterate
by
moving
forward-
and
this
is
a
what
I
thought
was
a
great
example
of
upholding
our
results
values.
A
So
after
13
9
13
10,
13
11,
we
came
up
with
some
following
issues.
This
is
a
holistic
list.
I
just
tried
to
grab
a
few
to
kind
of
show
like
how
we
move
like
kind
of
lift
and
shifted
the
future
to
a
different
place
that
we
felt
was
a
better
place
for
it.
This
did
delay.
I
guess
you
could
say
the
releasing
of
the
feature.
A
However,
it
is
ultimately
for
a
better
solution
and
I
think
that's
a
good
enough
reason
to
call
pivot
when
we
needed
to-
and
engineering
was
really
great
about
this
when
we
brought
the
problem
to
them
and
told
them
what
we
were
facing.
They're
like
hey,
we'd,
rather
bite
the
bullet.
Now
it'll
save
us
tech,
debt
down
the
road
and
ultimately
we
can
solve
this
quicker.
A
So,
like
I
said,
I
think
this
is
a
good
demonstration
of
our
results
value.
We
kept
a
bias
for
action
by
continuing
to
ask
hard
questions,
while
still
developing
the
feature
that
we
thought
was
functionally
serving
the
right
purpose.
We
are
embracing
the
uncertainty
of
we
don't
know
100
what
the
perfect
solution
is,
but
not
having
the
solution
at
all
is
worse
than
not
having
it
in
the
product
and
then
we
disagreed
we
committed
on
a
path
forward
and
then
we
continue
to
disagree
on
a
way
to
continue
to
refine
this.
A
I
just
wanted
to
highlight
a
diff
of
how
it
looks
when
we
kind
of
started
and
where
we're
going
to
be
moving
so
initially
we're
calling
this
approval
gates.
It
was
going
to
be
tied
into
merge,
request
approvals.
You
could
see
a
various
number
of
services
that
you
were
sending
a
payload
to
whether
or
not
they
sent
a
positive
or
negative
feedback
response
on
now.
It's
going
to
be
part
of
the
merge
request
reports,
which
makes
more
sense
functionally
in
terms
of
how
it's
presenting
information.
A
We
definitely
want
to
expand
features
in
it,
but
this
just
kind
of
gives
you
a
way
to
see
side
by
side
what
we
initially
were
going
after,
how
we
got
course
corrected
with
code
review
and
then
how
we
kind
of
pivoted
towards
a
better
solution,
and
what
we've
heard
so
far
is
that
users
really
love
the
feature,
they're
kind
of
sad
to
see
it
in
ultimate
because
they're
on
premium.
But
I
guess
that's
just
a
sign
that
we're
creating
features
that
people
want.
So
with
that
I'd
love
to
hear.
If
there
are
any
questions.