►
From YouTube: UX Showcase - Pipeline list view - a case study of making a high traffic page future-proof
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,
in
short,
this
is
a
really
important
page
in
git
lab
and
talking
about,
like
the
kind
of
traffic
that
this
page
sees
I'm
going
to
be
showing
some
stats
here
and
even
though
this
is
not
like
really
the
ideal
one.
But
when
we,
however,
here
it
is
492
000
views
in
last
30
days.
So
this
is
the
second
most
visited
page
in
the
product
and
that's
what
makes
it
a
really
like
critical
page
to
work
with
now
around
four
1.5
years
ago.
A
What
happened
was
our
front-end
team
in
pipeline
execution.
They
got
very
busy
dealing
with
the
many
incidents
that
were
reported
in
relation
to
this
to
the
layout
breaking
on
this
page,
and
this
was
coming
at
a
time
when
there
were
so
many
different
issues
which
were
being
worked
on
which
were
going
to
add
something
to
the
page.
A
So
it
was
like
quite
scary
for
us,
like
this,
threw
us
off
and
the
series
of,
like
this
whole
series
of
events,
and
that's
when
we
decided
that
okay,
let's
talk
about
it,
so
the
changes
that
for
queued
to
be
added
to
this
page.
Of
course
they
were
valuable.
They
had
gone
through
the
problem,
validation
phase.
They
were
like.
We
had
a
decent
amount
of
confidence.
That
users
would
be
like
very
glad
to
have
those
additions
in
here.
A
But
if
the
page
cannot
I
mean
if
the
page
doesn't
load,
then
there's
no
point
talking
about
the
value
part
right.
So
today,
I
would
be
talking
about
like
for
this
page.
How
are
we
working
on
keeping
this
pipeline
list
view
future
proof,
while
we
also
work
on
adding
some
value
to
for
our
users
through
this
page,
all
right,
so
the
first
thing
that
we
did
after
learning
about
those
incidents,
was
we
started
with
the
discussion
like
because
it
was
something
that
was
really
urgent.
A
We
did
not
have
a
lot
of
time
to
like
conduct
a
research
really
think
about
it
for
a
long
time,
but
we
wanted
to
see
like
what's
the
next
smallest
thing,
that
we
can
do
that
can
make
a
big
change
that
can
like
give
us
some
wiggle
room
to
think
more
later,
but
was
the
very
first
step
that
you
should
we
should
be
taking
so
keeping
on
the
all
the
constraints
in
mind.
All
the
ongoing
work,
the
cute
work,
everything
in
front
of
us.
A
We
started
off
with
like
what
should
be
the
part
forward
and
from
this
discussion
what
we
concluded
was,
but
the
first
thing
we
need
to
do
is
make
space
on
the
page.
So
that
was
the
brief
for
that
time.
Like
make
space.
Do
something
and
make
space
following
that
discussion?
There
was
this
issue
created,
which
said:
rearrange
pipeline
index
page
layout
to
create
more
space.
At
this
point,
we
did
not
have
I
mean.
Of
course,
we
knew
like
what
are
the
primary
jobs
to
be
done,
which
are
related
to
this
page.
A
A
A
So
we
had
too
many
columns
like
status,
51
ID
trigger
there
was
separate
column
for
commit
as
well,
and
then-
and
this
is
one
of
the
like
good
use
cases,
because
the
pipeline
IDs
are
not
long
and
like
there
are
many.
It
doesn't
have
too
many
labels,
but
imagine
if,
on
this
page
with
this
size
of
many
pipeline
graphs
and
long
pipeline
IDs,
it
used
to
look
really
busy
and
it
was
very
difficult
to
work
with.
A
So
this
was
a
success
like
the
very
first
attempt
was
a
success
and
we
were
like
it
did
give
us
some
time
to
think
further
and
plan
out
like
what
was
the
next
thing
that
we
would
want
to
do
and
that's
when
this
issue
was
created.
This
is
just
to
this
was
created
to
keep
a
track
of
everything
that
we
would
be
doing
to
keep
this
page
healthy
performing
and,
at
the
same
time
ensuring
that
we
are
not
eroding
any
value.
A
So
it's
not
always
about
adding
value,
but
they're
with
when
a
product
is
scaling
and
the
challenges
they
like
drastically
change,
not
ensuring
that
we
are
not
eroding
the
value
that
we
are
already
providing
to.
Our
users
also
becomes
a
challenge
all
right,
so
this
was
implemented,
but
at
the
same
time
what
we
implemented
was
like
another
bunch
of
issues,
so
we
improved
the
action
button
layout.
We
started
showing
pipeline
IID.
These
were
all
disconnected
from
each
other.
A
These
were
small
little
efforts
which
were
planned
even
before
I
started
to
take
care
of
the
work
in
this
Stage
Group
but
like
they
were
very
well
validated
and
they
were
very
well
sought
like
they
were
sought
by
the
community.
They
had
a
lot
of
people
following
these
changes,
so
it
was
really
desired
by
the
community
all
right.
So
these
many
changes
happened
and
individually.
A
They
were
each
one
well
validated,
but
then
there
came
a
time,
especially
after
we
made
all
of
these
space
related
changes,
that
he
felt
that
the
Delta
like
what
the
page
looked
like,
maybe
three
months
ago
and
how
it
looks
today,
it's
really
different.
So
we
just
to
be
sure
that
we
are
not
causing
any
disruption
to
the
workflows.
We
thought
we
would
conduct
a
solution,
validation
exercise,
and
this
was
really
helpful
because
this
really
opened
our
eyes
so
individually.
A
Users
did
not
have
any
problem
with
any
of
these
additions,
but
when
they
came
to
the
page,
they
always
found
that
something
had
changed
and
how
they
used
to
work.
Previously
they
had
to
change
their
workflow.
There
was
some
there
were
some
hiccups,
but
at
the
same
time
we
learned
that,
even
though
we
spoke
to
about
9
to
10
users,
out
of
which
I
would
say,
eight
were
good
responses.
A
We
figured
each
and
every
person
works
with
this
page
in
a
very
different
method.
Like
the
we
couldn't
establish
a
standard
workflow
when
it
comes
to
the
pipeline
industry
page
and
that
kind
of
I
wouldn't
say
it
scared
us,
but
it
did
make
a
make
us
more
cautious
of
our
next
steps.
So
we
thought
that
okay,
we
have
received
a
bunch
of
insights
that
we
would
love
to
work
with.
But
at
the
same
time
we
cannot
like.
A
A
We
started
to
create
issues
like
small
issues
as
a
part
of
our
work
and
seeing
that
through
and
so
far,
there's
only
one
that
caused
actual
disruption
in
user's
workflow
and
I'll,
get
to
it,
because
that's
a
small
story
of
a
failure,
but
that
it
teaches
a
lot.
Otherwise,
we
are
now
constantly
keeping
a
track
of
the
performance
of
this
page.
We
keep
visiting
the
dashboard
regularly
in
the
team.
A
We
have
this,
like
small
ritual,
where
we
discuss
about
how
the
performance
is
going
and
create,
if
not
monthly
I,
would
say,
bi-monthly
issues
about
pipeline
speed
go
so
I
know
it's.
It
says
if
I
can
speed
goal,
but
it's
mostly
about
how
the
pipeline
list
view
page
is
responding.
So
we
put
the
lighthouse
data
here
and
based
on
that,
we
have
discussions
on
the
issues
as
in
what
should
be
the
next
step.
Now,
like
we
shouldn't
be
content,
because
we
are
very
sure
that
there'd
be
more
things
like
in
future.
A
A
It's
a
continuous
effort
to
make
sure
that
this
page
can
always
take
some
amount
of
change
that
we
are
making
to
add
value
and
the
format
that
I
had
proposed
that
we
should
use
for
proposing
a
change
based
on
the
data
that
we
are
consuming
is
listing
The,
Proposal
assumption
and
evidence,
because
I
did
not
want
us
to
be
not
cognizant
of
what
risks
we
are
taking.
So
we
should
I
thought
we
should
like
really
have
in
mind.
A
What
are
the
assumptions
that
we
are
making
that
would
require
to
be
validated
before
we
go
ahead
and
work
on
a
proposal
and
implement
it.
So
this
is
the
format
that
we
followed
like
putting
down
the
proposal,
then
also
stating
what
are
the
assumptions
that
I'm
making
while
making
this
proposal
and
then
what
are
the
evidences
that
support
that?
My
proposal
would
be
a
success,
so
we
did
this
and
based
on
this,
we
were
able
to
create
an
issue
which
is
now
going
to
be
worked
on.
A
The
data
for
this
is
coming
from
Lighthouse,
the
dashboard
that
we
have
created
and
also
we
also
have,
in
the
back
of
our
mind,
the
insights
that
we
have
received
through
our
user
researchers.
So
everything
is
playing
a
role
here
as
we
move
forward
and
we
did
not
stop
here.
We
are
now
constantly
posting
the
page
performance
and,
as
we
see
another
opportunity
through
these
new
statistics,
we
are
going
to
create
a
new
issue
now
talking
about
the
failure
stories.
A
We
thought
this
was
a
small
change
to
make
and
worked
on
it,
but
it
backfired,
so
we
had
to
roll
it
back,
and
this
was
my
update
on
why
we
are
rolling
it
back
and
the
learnings
that
we
carried
from
that
experience
anyway.
So
this
also,
this
was
a
good
example
of
how
critical
everything
that's
there
on
this
page
is
to
the
workflows
of
our
users,
and
even
though
that
we
felt
that
we're
just
shifting
a
link,
we
are
just
shifting
a
link
from
a
sentence
to
a
number,
but
it
was
very
disruptive.
A
So
now
we
whatever
we
do,
we
do
with
a
lot
of
caution
and
that's
where
we
are
at
with
this
effort,
but
I
can
say
that
this
is
not
the
end.
I,
don't
even
think
this
is
the
middle
of
the
upward,
and
this
is
going
to
go
on
for
a
long
time,
but
it's
just
something
that
we
have
been
dealing
with
continuously,
to
make
sure
that
we
are
not
taking
away
the
value
that
we
are
already
providing
to
our
users.
A
C
Maybe
I'll
just
ask
my
question
and
I
can
write
down:
I
missed
the
like
timeline
of
your
presentation.
Was
it
like
a
year
a
couple
months,
a
couple
weeks:
I
love
the
progression
and
the
stuff
you're
walking
through,
but
I
just
wanted
to
reframe
my
mind
around
like
realistically.
How
long
did
that
take.
D
B
A
So
currently,
what's
happening
was
like
we
use
the
name
of
the
commit
for
which
the
pipeline
is
running
as
the
title
for
the
pipeline.
So
we
thought
if
we
are
going
to
like
roll
in
this
feature,
that
would
allow
users
to
Define
a
pipeline
name.
It
cannot
appear
on
top
of
the
combat
name.
We
have
to
keep
only
one,
because
it
would
make
this
page
like
really
busy
and
really
crowded,
and
we
already
provide
an
ID
for
the
commit.
A
B
What
was
the
feedback
on
the
issue
that
you
posted
or
how?
How
did
you
get
the
feedback
I'm
just
wondering
like
how
different
teams
deal
with
you
know
backlash
in
these
kinds
of
scenarios,
where
we
try
something
out
that
we
think
is,
you
know
just
a
small
change
and
then
it
turns
out
to
be
catastrophe.
A
The
first
backlash
started
to
appear
like
internally
itself,
like
on
what
is:
is
this
known
channel,
so
that
was
our
first
queue
and
I.
Think
I
saw
one
comment
on
Twitter
and
I.
It
was
Marshall
who
actually
helped
me
through
this
whole
thing
that
we
we
talked
about
on
slack
or
about
rolling
this
back
and
then
an
issue
was
created.
The
developers
were
communicated
and
I
posted.
D
I
was
just
writing
a
question.
I
think
mine's.
Next
I
was
curious.
I
really
appreciate
your
approach
on
ensuring
these
new
features
you're
delivering
values
in
our
Improvement,
because
things
are
always
changing.
So
that
way
they
do
see
the
changes
as
something
good
I
was
just
curious.
Did
you
do
any
more
expiration
into
that
perception
of
constant
change
and
is
it
potentially
leading
to
change,
fatigue
and
yeah
I'm
just
curious
if
you
had
any
thoughts
on
that.
A
Oh
no,
we
did
not
I
mean
we
did
not
research
on
that
particular
aspect.
Yet
we
have
been
thinking
more
about
like
individual
set
of
changes
and
not
we
haven't,
given
it
a
thought
how
users
would
be
feeling
if
we
compound
everything
that
we
have
done
so
far
and
how
they
have
been
adapting
to
the
process.
But
that
would
be
very
interesting.
D
C
A
It
was
a
carryover,
then
I
created
a
budget
list.
It's
still
there
and
I
got
a
ping
from
Jeremy
I
think
yesterday,
which
I
am
yet
to
respond
to.
So
that
discussion
is
going
on
because
we
are
facing
this
problem.
There
are
so
many
different
links.
They
all
look
different
for
some
reason
and
it's
contributing
to
this
stage.
Looking
visually
a
little
noisy
I
would
say.
E
Okay,
so
since
I'm
next
one
is
mine
is
more
of
a
comment
or
there's
a
question.
I
I
was
really
impressed
by
the
the
fact
that
the
team
also
started
to
involve
the
performance
as
part
of
the
experience
Factor.
But
did
you
like
start
from
the
beginning
that,
like
this
performance
of
this
page,
was
a
little
bit
problematic?
Or
did
you
also
bring
into
this
topic
a
little
bit
later,
when
you're
already
working
on
the
design.
A
So
this
discussion
used
to
always
happen
when
there
was
a
change
to
that
page,
but
it
was
never
so
serious,
so
I
never
took
it
as
critically,
but
this
time
when
they
actually
sounded
the
alarm-
and
there
were
so
many
issues
created
around
oh,
this
is
breaking
the
buttons
are
apart.
Things
are
appearing
on
the
next
line.
What
is
happening
on
this
page?
That's
when
we
thought.
First,
we
are
going
to
fix
this.