►
From YouTube: UX Showcase exploring new pipeline overview page
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
Hi
everyone
I'm
Kevin
I'm,
a
senior
product
designer
in
growth
and
today
I
am
not
going
to
be
talking
about
growth,
because
I
am
currently
covering
ux
needs
for
the
pipeline
authoring
group.
A
So
today,
I
will
be
focusing
mainly
on
exploring
a
new
pipeline
overview
page,
which
is
an
issue
that
the
engineering
team
from
the
pipeline
authoring
group
kick-started
not
so
long
ago
and
essentially,
when
I
just
kind
of
join
via
my
ux
borrow
I've
been
asked
to
provide
some
feedback
on
on
the
ux
direction
and
also
help
moving
this
issue
forward.
So
oops
presentation
click
all
right.
So
what
is
the
pipeline
overview?
Page
just
figured
that
don't
know
about
it.
A
A
So,
essentially,
what
you
have
in
this
page
I
think
the
main
interesting
piece
that
I'm
going
to
jump
into
is
the
pipeline
graph,
because
the
main
point
of
this
page
is
to
basically
for
you
to
monitor
your
current
pipeline
or
somebody
else's
Pipeline,
and
essentially
the
information
that
you
want
to
retrieve
from.
A
A
The
first
one
was
the
graph
scalability,
so
large
pipeline
are
hard
to
parse
and
navigate
using
the
graph
view
that
I
just
showed
you,
which
kind
of
then
correlates
with
some
efficiency
issue,
which
means
critical
information
and
not
simply
surfaced
so
identifying
and
fixing
some
bottlenecks
like
filter
hubs
are,
is
not
an
easy
task.
When
you
have
a
big
pipeline,
essentially
and
in
terms
of
performance,
it's
behaved
well
when
I
just
show
it,
but
it
can
be
pretty
long
to
load
this
specific
graph.
A
So
some
of
the
initiative,
sorry,
the
initiative
that
I'm
talking
about
is
this
one.
So
this
is
Frederick.
A
He
is
a
engineer
in
the
Bible
monitoring
team,
and
this
was
his
kind
of
side
project
to
try
to
fix
this
page,
and
one
of
one
of
I
would
say
the
main
emphasis
that
he
had
was
to
show
a
graph.
I
mean
more
of
a
data
visualization
of
the
pipeline,
where
you
will
see
the
breakdown
of
the
different
jobs
and
the
ones
are
in
progress
and
also
kind
of
flip.
A
The
graph
on
the
side
I
think
in
this
proposal
he
put
it
into
the
pipeline
Tab
and
switch
it
for
a
table
where
you
would
have
directly
a
list
of
all
of
the
jobs
that
you
need
to
act
upon.
So
this
is
not
all
jobs.
This
is
simply
the
one
that
you
need
to
act
upon
so
pending
failed
and
I.
Think
let
me
forget
one
forgot
about
it.
Sorry
about
that,
but
anyway,
I
was
asked
to
gonna.
A
You
know,
provide
you
back
on
on
this
direction
and
try
to
move
the
the
initiative
forward,
but
before
doing
that,
I
had
need
to
get
kind
of
thingy.
A
Thankfully,
and
she
basically
mentioned
that
she
worked
on
something
similar
a
few
Milestones
ago,
so
it
was
not
exactly
targeted
as
improving
the
pipeline
overview
page
directly,
but
more
about
the
experience
around
debugging
and
presenting
job
logs,
which
is
very
related
to
it,
because
once
you're
on
the
pipeline
overview
page,
the
next
stop,
if
you
have
an
issue
with
on
your
job,
is
the
job
log,
but
anyway,
through
the
word
that
she
did.
She
also
built
up
a
different.
A
How
would
I
call
this
media
vision
of
what
the
space
should
be
and
she
run
a
few
moderated
testing
sessions
to
kind
of
try
to
end
refine
the
direction
which
was
amazing
because
she
shared
direct
details
with
me.
So
can
you
be
together
with
this?
Is
super
helpful
and
yeah
and
basically
digging
into
her
research?
What
I
noticed
is
that
these
three
specific
insights
that
she
found
out
so
show
agree:
collectionable
information
about
jobs,
up
front,
a
low
for
contextual
identification
of
jobs
and
Pipeline
and
present.
A
The
trend
report
for
the
running
pipeline
were
directly
correlating
with
what
Frederick
was
trying
to
do
and
ultimately
what
the
direction
of
this
page
was
supposed
to
be
right
and,
additionally,
to
this,
there
was
another
Insight
point:
I
think
that
came
from
a
larger
study
on
verify
and
and
package
usage
and
one
of
those
the
urgencies
that
we
surfaced
was
that
we
should
probably
meet
people
where
they
are
so
we've
spoken
to
the
to.
They
don't
often
come
to
the
UI,
but
when
they
do
come
to
the
UI.
A
Is
that
there's
an
issue
and
something
needs
to
be
fixed
urgently?
So,
if
you
think
about
the
pipeline
overview,
page
today
may
not
be
doing
the
best
job
to
to
meet
people
where
they
are
right
and
another
one
is
that
we
kids
consider
prioritizing
pipeline
insights.
So
CI
in
City
pipeline
dashboard
are
in
the
top
three
features
that
essentially
contribute
people
to
sorry,
there's
fishing
people
to
to
to
buy
a
Premium
plan.
A
So
this
is
something
that
we
pull
out
from
the
poster
shares
survey,
and
what
this
tells
me
is
that
if
we
could
essentially
show
a
sample
of
you
know
insights
or
pipeline
data
that
is
equivalent
to
what
the
pipeline
dashboards
are
doing
for
free.
We
could
kind
of
pitch
the
value
of
higher
tier
feature
and
kind
of
try
to
see.
If
people
would,
you
know,
consider
upgrading
to
access
these
features
and
at
the
same
time,
if
they
don't
want
to,
we
would
still
give
a
bit
of
value
for
free,
as
which
is
great.
A
So
with
all
that
in
mind,
I
started
kind
of
exploring
again
what
this
page
could
be
and
to
get
started
on
that
I
just
simply
took
a
step
back
and
look
at
what
the
page
is.
Today
and
what
I
wanted
to
do
is
essentially
try
to
Zone
it
like
create
area
to
to
areas
to
understand
the
underlying
structure
of
the
page
and
I
may
have
oversimplify
it.
But
to
me
this
was
pretty
much.
A
An
accurate
representation
of
the
situation
is
that
we
have
half
of
the
page
being
the
metadata,
the
other
half
being
pipeline
actions,
as
you
may
think,
maybe
pipeline
actions
should
be
a
bit
more
emphasize
here
right,
based
on
what
we
just
said,
the
media
that
is
really
taking
a
huge
chunk
of
the
structure
and
is
probably
something
that
we
should
consider
changing
right.
A
So
with
that
in
mind,
I
started
kind
of
going
back
into
what
Frederick
Haddon,
what
vitica
had
done.
What
the
page
currently
was
and
I
just
kind
of
stripped
it
out
and
re,
like
rethink
some
of
the
building
blocks,
so
what
I
wanted
to
do
is
obviously
try
to
shrink
The
Meta
data
as
much
as
possible.
A
So
in
this
case
this
is
like
the
comment
box
that
you
see
here
introduce
some
of
the
Maybe
I
would
call
this
pipeline
status,
insights
and
you
know
kind
of
use
visually
data.
Visualization
to
to
basically
add
a
bit
more
value
to
this
page
and
keep
the
actions
where
they
are
at
the
moment,
because
the
ID
is
not
too
completely.
A
You
know,
operate
a
complete
Revolution
on
on
the
page,
but
simply
reorder
things
and
add
a
bit
of
value
here
and
there
so
yeah.
So
I
started
focusing
on
sorry
on
each
of
these
single
bits,
so
first
the
the
metadata
part
and
the
commit
box.
So
drawing
a
lot
of
inspiration
from
the
merge
request,
page
that
we
have
right
now,
I
gotta
start
changing
the
layout
of
the
metadata.
A
So,
instead
of
having
it
vertically
stacked,
you
know
we
just
have
it
in
one
line
and
essentially
all
of
the
information
that
you
have
about
who
approved
the
military
Quest
and
all
that
could
be
retrieve
directly
from
the
merge
request
and
the
title
of
the
merge
request
as
well.
So
we
could
rely
on
tooltip
and
and
pop
over
to
kind
of
Supply
that
information
and
then
I
kind
of
focused
more
on
the
insights
part.
What
do
we
want
to
provide
about
the
current
pipeline
like
whether
what
could
be
valuable?
A
So
again,
these
are
Explorations.
Probably
this
will
change,
but
just
having
some
of
the
insights
in
mind,
I
thought
it
would
be
interesting
to
have
a
clear
role
of
maybe
small
widget.
We
can
call
them
widgets,
one
being
the
status
with
the
time
remaining
and
the
current
duration
of
your
pipeline
versus
the
average
duration
and
link
to
a
potential
like
cicd
analytics
that
we
have
at
the
project
level.
A
A
A
pie
chart
to
try
and
like
save
a
bit
of
space
and
I
thought
that
it
was
also
a
clear
way
to
provide
a
very
simple
view
of
where,
where
your
buy
plan
is
at
the
moment
and
highlight
also
failed
jobs
now
I'm
realizing
that
I'm
missing
the
one
that
passed
with
warnings
and
then
a
third
widget
that
is
focused
on
actionables,
so
the
jobs
that
you
do
want
to
take
care
of
the
jobs
that
are
actually
in
padding
progress.
A
So
what
I
see
in
this
specific
spot
is
potentially
I
mean,
surely
fails
you
up
not
potentially,
but
it
makes
a
failed
job
at
manual
jobs,
basically
anything
that
requires-
and
maybe
the
password
warning,
but
basically
everything
that
requires
your
immediate
attention
and
the
last
bit,
which
is
the
direct
kind
of
view
of
the
job
in
their
relationship
with
the
stages
so
same
thing,
I
kind
of
build
upon
the
table
view
that
survey
had
and
Vita
also
had
the
way,
I
kind
of
approached.
This
is
instead
of
having
another
tab.
A
We
could
kind
of
toggle
between
a
table
of
you
in
the
graph
View,
but
yeah,
then
the
table
view
would
also
have
some
of
your
pending
manual
job
and
sales
jobs.
A
So
yeah.
That
is
a
first
round
of
mockup,
so
it
is
obviously
meant
to
evolve
d,
but
yeah.
Circling
back
to
the
different
areas.
I
think
this
layout
kind
of
provides
a
better
balance
as
it's
reducing
considerably
the
metadata,
but
also
kind
of
re
surfacing.
Some
of
the
actionable
stuff,
we
think,
could
be
a
great
way
to
improve
this
page
so
yeah.
So,
as
I
said,
personal
look
up
after
sharing
it
with
the
team,
I
had
like
a
ton
of
feedback.
A
So
thanks
everyone
for
that,
and
there
are
things
that
I
want
to
add
on
this.
So,
for
example,
surface
the
ability
to
download
artifacts
is
something
that
we
discussed
with
Gina
and
I
think
it
makes
a
lot
of
sense,
because
it's
definitely
something
that
people
check
whenever
they
have
a
fail
job,
then
adding
filtering
installing
option
to
this
table,
because
if
you
start
having
a
large
amount
of
data,
so
like
a
lot
of
rows
in
your
table,
you
would
obviously
you
want
to
simplify
this
View
and
try
to
filter
them.
A
Try
another
visualization
for
the
job
breakdown
like
that.
That
was
the
first
path
and
also
it's
called
a
relationship
between
like
child
pipeline
nasty
jobs,
then
going
a
bit
down
into
the
nitty-gritty
of
you,
know
the
relationship
between
Pipeline
and
jobs
and
how
this
could
potentially
break
this
table
or
not
so
yeah.
So
the
next
steps
on
the
ideally
by
the
end
of
the
year
would
have
completed
some
solution.
Violation
I
think
in
my
main,
rapid
iterative
testing
could
be
a
great
way
to.
B
A
Forward
and
generate
insight
and
test
multiple
layouts
to
kind
of
increase
our
confidence
into
what
the
space
should
look
like
and
then
start
you
know
iterating
on
design
and
then
they
find
like
smaller
chunks
and
a
specific
NPC.
And
ideally
this
is
something
to
be
going
to
confirm
with
the
team,
but
try
and
Implement
a
and
release,
and
let
me
see
by
it
to
next
year-
I
mean
during
next
year.
Basically-
and
that's
it,
do
you
have
any
thoughts.
C
I
would
want
to
start
off
with
giving
a
Kudos,
because
I
saw
like
how
much
information
you
consumed
and
how
much
you
like
caught
up
in
the
context,
and
that's
really
commendable
so
I
can
totally
see
that,
like
there
were
two
things.
First
of
all,
the
toggle
between
the
graph
and
the
list
view
that's
going
to
make
the
page
so
much
better
performing
because,
even
though
the
craft
was
something
that
was
very,
that
that
is
very
attractive
to
our
users.
C
It
was
having
a
really
like
huge
tell
on
the
performance
of
this
page
and
providing
that
as
something
like
optional
and
that
doesn't
load
by
default
when
you
come
to
this
page
rather
than
making
sure
that
they
have
everything
they
need
to
take
the
immediate
action,
that's
most
critical
to
the
context
everything
clubbed.
This
is
a
very
impactful
change.
Thank
you.
So
much
for
working
on
this.
A
Thanks
well
thanks
for
your
help,
honestly,
because
I
don't
think
I
would
have
been
able
to
you
know,
move
forward
and
and
grasp
a
bit.
You
know
faster
the
complexity
of
the
space
without
you
kind
of
showing
me
what
you
did
before,
so
that
was
super
helpful.
So
thanks.
Thank
you
for
that.
B
I
have
a
question:
I
haven't
I,
didn't
write
it
down,
but
I'm,
not
gonna,
I
won't
type.
It
is
the
the
time
remaining
in
the
like
some
of
the
stuff,
the
analytics
on
the
left
there,
where
the
current
duration
average
duration,
is
that
all
numbers
that
we
have
today
or
is
that
like
does
that
need
back-end
work
to
be
able
to
create
those
yeah.
A
So
discussing
with
the
team,
the
time
remaining
is
definitely
a
question.
We're
not
100
sure
on
that,
but
current
version
and
average
duration
seems
good.
B
Yeah,
that's
that's
awesome,
because
I
know
that
that
connects
with
some
of
the
research
that
the
research
team
was
recently
finishing
up
on.
It
was
system
performance
research
and
we
heard
that,
like
a
lot
of
users
were
basically
waiting
around
for
their
pipeline
or
job
to
finish
and
didn't
really
understand
why
and
it
made
the
it
made
the
perception
as
if
our
it
just
took
a
while
for
pipelines.
B
That's
something
that
I
think
would
be
helpful
and
probably
not
related
to
this
project,
but
if
we
could
use
like
the
same
type
of
calculations
that
you
do
that
the
back
end
team
works
with
for
this,
we
could
bring
it
to
the
job
level.
Maybe.
C
I'm,
just
plugging
like
a
research
link
here
that
was
done
recently.
That
could
be
of
help
to
you,
because
there
was
a
similar
feedback
that
I
also
received
in
like
during
that
research.
C
The
booth,
yeah,
okay,
cool
thanks.
D
I
just
find
an
ad
like
thank
you
for
sharing
it's
like
wonderful
process.
You
went
through
and
questioning
some
of
the
you
know,
things
that
have
been
in
our
product
and
UI
for
many
many
moons
longer
than
most
of
us
have
been
here
and
in
your
thoughtful
adjustment.
While
not
removing
you
know
the
necessary
information,
but
really
considering
the
user's
need
when
they
come
to
this
page
and
so
often
we'll
see
creating
dashboards,
as
if
people
would
kind
of
stare
at
stare
in
awe
their
beauty.
D
A
A
I
get
good
help
to
be
honest,
like
everyone
from
you
know
the
the
cicd
ux
team
or
the
pipeline
authoring.
Yes,
super
kind
and
helpful
well,
I'm,
trying
to
you,
know,
adjust
to
what
it
means
to
design
into
ICD.
So
thanks.
D
Bonus
points
for
collaboration,
I,
see
Mike,
writing
down
a
comment.
Yeah.
E
Painfully
typing
it
just
a
thought,
not
really
expecting
an
answer.
Unless
there
is
one
obvious
one
more
just
to
generate
an
idea.
Do
users
need
this
kind
of
summary
data
on
the
jobs,
failed
jobs
and
test
tabs,
and
that
is
a
leading
question
into
like.
Should
we
maybe
move
the
tabs
up
a
little
bit.
A
Yeah
I
was
playing
around
with
that
idea
and
yeah
to
be
honest,
I
I,
don't
necessarily
have
the
answer
right
now.
I
think
the
way
I
exploit
it
I
think
it
kind
of
makes
sense
to
have
it
Global
to
all
of
them,
but
I
think
you
also
have
a
good
point
of
like
yeah.
If
you're
in
fail
jobs,
you
don't
need
to
visualization
of
the
same
thing
right
so
yeah,
it's
yeah,
Food,
For,
Thoughts,.
D
D
D
A
Oh
sorry,
go
ahead.
Sorry,
yeah
I,
don't
know
if
anyone
had
an
extra
question,
but
I
just
had
one
for
anyone
on
the
call,
because
when
I
was
working
on
this
kind
of
pulling
the
the
merge
request,
page
and
kind
of
being
inspired
by
the
way
we've
worked
on
the
header.
A
A
There
is
a
way
we
organize
metadata
on
if
a
lot
of
page
in
gitlab,
for
example,
issues
and
and
a
lot
of
things,
I
can't
get
another
page
online,
but
anyway
the
way
we
order.
It
is
a
bit
scattered
and
it's
taking
a
lot
of
space
and
I.
Think
the
what
has
been
done
in
the
merge
request
page
was
a
great
job
to
kind
of
tie
it
in
to
the
title
of
the
page
and
having
this
kind
of
header
and
when
I
was
working
on
there.
D
Don't
see
anybody
on
the
creatine
here,
but
I
think
that
is
a
great
great
thing
to
pursue
right.
We
could
create
an
issue
in
pajamas
and
start
discussing
that
I
mean
bringing
our
header
metadata
together
and
aligning
it
across
all
of
our
issueable
types
and
other
objects
alerts
vulnerabilities,
even
like
the
project
home
page.
You
know,
with
some
of
the
metadata
all
could
be
beneficiaries
of
this
new
approach.
I
agree.