►
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
Hello,
everyone,
I'm
Gina
I'm,
the
product
designer
for
Runner
and
pipeline
insights
and
I'm
gonna,
be
walking
you
through
kind
of
like
a
scenario
where
I
was
able
to
get
some
really
quick
feedback
from
users,
async
about
a
new
feature
that
we
were
creating
for
Runner
and
so
to
just
give
a
little
context
around
what
was
happening
here.
So
we
started
with
this
issue
of
or
this
problem
where
we
had
so
much
data
that
we
wanted
to
show
admins
about
Runners,
that
it
was
no
longer
readable
in
all
the
viewports.
A
So
we
were
struggling,
keeping
that
data,
readable,
The
Columns
were
collapsing,
the
data
was
becoming
overlapped
and
not
all
that
data
that
was
in
all
those
columns
were
equally
important
either,
but
they
were
all
treated
that
way
and
then
we
also
wanted
to
add
more
data.
So
we
were
really
struggling
doing
that
with
the
current
Table
design
that
we
were
working
with,
and
so
what
we
ended
up
doing
was
I'll
just
scroll
down
into
this
design.
A
But
to
get
back
to
the
point
of
this
presentation,
what
we
wanted
to
do
was
we
ended
up
in
the
Mr.
Putting
this
underneath
a
feature
flag
and
the
reason
for
that
is
because
we
we
did
run
solution,
validation
around
that
design.
That
I
was
just
showing,
but
we
wanted
to
make
sure
that
it
didn't
impact
those
admins
jobs
negatively
when
we
released
it.
So
that's
why
we
started
with
the
feature
flag,
but
when
we
did
that
we
were
able
to
make
some
iterations
to
get
there.
A
A
So
for
this,
what
we
ended
up
doing
was
we
added
a
a
banner
to
the
page
to
collect
their
feedback
about
this
new
feature
and
I?
Think
I
have
a
screenshot
of
it
or
I
thought
I
did
so?
Let's
see
I
don't
have
it
here,
but
it's
we
just
added
a
feedback
Banner.
You
know
above
the
table
here
so
that
it
linked
to
an
issue
and
they
could
leave
their
feedback.
A
I
wasn't
really
sure
what
to
expect
from
that.
Like
I,
didn't
I
didn't
know
how
helpful
that
would
be
for
users
or
if
they
would
even
interact
with
it,
to
be
honest,
but
it
turns
out
that
a
lot
of
them
loved
it
and
we're
getting
a
ton
of
feedback
now,
not
just
about
that
specific
change
that
we
made,
but
more
specifically
about
things
that
are
even
painful
for
them
outside
of
that
change
when
it
comes
to
runners.
A
So
what
we
did
was
we
created
this
feedback
issue
and
left
three
different
threads
open
for
them
to
add
to
so.
What's
working?
Well,
what
doesn't
work
well
and
then
what
should
be
improved?
And
then
some
people
were
leaving
comments
like
outside
of
those
threads
as
well,
but
the
threads
seemed
to
work
pretty
well
and
what
I've
been
doing
now
is
to
kind
of
like
understand
or
get
them
to
understand
that
I'm
actually
reading
it
and
we're
doing
stuff
about
it.
A
They
brought
up
some
stuff
about
monitoring,
Runner,
metrics,
so
understanding
if
Runners
were
performing
as
expected
and
getting
data
around
that,
because
we
don't
provide
any
data
around
that
right
now
and
it
was
awesome
to
see
that,
and
so
what
I
did
was
when
we
were
going
through
the
MVC
for
that
type
of,
like
monitoring
feature
I
was
able
to
bring
a
lot
of
them
into
the
conversation
here
to
get
feedback
on
our
our
solution
there.
If
I
can
scroll
there,
it
is
so
what
I
did
is
I
tagged
them
here.
A
I
asked
them
if
they
could
add
some
feedback
async
around
it
and
they
were
all
interested.
They
all
responded
and
provided
some
feedback
around
that
and
I
kind
of
just
recorded,
like
a
video
of
how
this
feature
would
work
so
that
they
would
understand
it
because
I,
you
know,
when
you
don't
have
a
clickable
prototype
for
them
to
play
around
with
it's
kind
of
harder
to
understand
how
the
feature
would
work
by
the
static
images.
So
that's
why
I
recorded
the
video
and
yeah,
so
it
was
just.
A
It
was
a
super
quick
way
for
me
to
get
quick
validation
of
a
feature.
I'm
still
gonna
run
moderated
testing
around
this,
because
it's
I
want
to
understand
better,
like
in
a
full
scenario,
how
it
will
impact
their
jobs,
but
it
was
a
really
great
way
to
collect
feedback.
If
anyone
else
is
thinking
of
or
needing
to
solicit
feedback
for
a
new
feature,
I
would
say.
B
I
haven't
typed
my
question
in
yet,
but
one
thing
I
think
about
when
I
think
about
these
banners
is
every
team
doing
this,
and
then
we
have
a
million
banners.
So
I'm
wondering
if
we
have
thought
about
tracking
any
of
this.
So
we
know
how
many
we
have
in
the
product
currently
when
they're
going
in
when
they're
going
out
that
type
of
stuff,
so
that
we
can
make
sure
we're
having
a
reasonable
amount
of
feedback
requests
in
the
product
at
one
time.
A
That
is
a
great
idea,
I
think
I
think
also.
It
might
help
to
have
better
like
more
specific
guidelines
of
when
to
use
the
banner
so
that
we're
not
just
using
that
to
get
feedback
around
new
features
like
maybe
there
needs
to
be
more
specific
scenarios,
I,
guess
and
and
when
to
do
that,
I,
don't
I
I
did
not
implement,
or
our
team
didn't
Implement
tracking
onto
that
Banner.
So
I'm
not
sure.
B
B
C
C
D
Again,
when
we
did
this,
we
had
a
banner
that
sent
users
to
a
survey
and
we
had
a
qualtrics
link
that
we
monitored.
So
when
we
hit
our
Target
cohort
of
like
we
needed
100
completes,
we
were
able
to
then
like
flip
the
feature
flag
off
and
send
it
to
engineering
and
say:
please
take
the
banner
down
because
it's
going
to
be
across.com
and
self-managed
as
well.
D
So
I
think
the
guideline
would
just
be
like
look
for
a
Target
goal,
make
one
with
your
pm
and
say
when
we
get
x
amount
of
information
and
we
feel
like
we
have
enough
to
make
a
change
or
make
a
decision.
Then
you'll
want
to
take
it
down.
But
our
strategy
was
like.
We
created
the
banner
takedown
issue,
the
minute
we
created
the
banner
like
implementation
issue,
so
that
we
knew
that
we
were
ready
to
take
it
down
and
could
react
quickly,
especially
when
you're
not
collecting
data.
D
D
So
the
banner
has
some
information
in
pajamas
right
now,
but
it's
berries
bars,
perhaps
maybe
getting
an
actual
research
product
into
our
application
could
be
a
solution
so
that
we
aren't
using
our
product
componentry
and
they're
mixed
with
gathering
information.
That
could
be
a
discussion
to
have
yeah.
E
Yeah
to
to
Andy's
plan
I
think
I've
only
used
like
more
formal
surveys.
Yes,
your
call
tracks
as
well
looping
in
the
research
team,
so
I
think
I
do
think
it's
like
a
cool
idea
like
this
really
low
cost
research
like
then.
Maybe
there
could
be
guidelines
around
like
when
to
do
certain
levels
of
research,
Within,
These,
banners
or
like
you
know
where
to
attach
these
links
when
it
would
be
valuable,
Etc
I
like
when
it
should
be
more
formal
versus
Lo-Fi.
D
Yeah
and
keep
in
mind
the
risk
too,
so,
if
you're
sending
them
off
to
a
survey,
there's
no
expectation
of
a
conversation
right,
give
us
we're
looking
for
this
information.
This
is
helping
you
you're,
asking
your
questions.
You're
collecting
your
data
you're,
creating
an
issue,
and
you
maybe
forget
to
monitor
it
or
forget
to
respond
that
might
send
like
a
double
negative
message
to
the
users
who
are
like
I'm
trying
to
give
you
feedback-
and
this
issue
is
six
months
old
and
no
one's.
D
A
Yeah,
that's
a
great
point.
It
has
been
a
lot
to
monitor
it.
I
won't
lie
and
it's
been
like
something
that
is
constantly
on
on
my
mind,
to
make
sure
that
they
know
that
I'm
listening,
that's
kind
of
why
I
was
saying
that
I
was
going
in
and
making
sure
I
was
responding
and
reacting
to
their
their
comments
there.
So
that's
a
good
point.
F
State
this,
since
you
were
already
talking
about
it
in
the
previous
thing,
but
I
think
this
might
be
the
impetus
to
discover
possibly
a
more
holistic
solution.
This
is
a
gap
that
we
have
in
our
iteration
value.
We,
our
iteration
value,
is
about
releasing
something
and
then
getting
feedback,
so
they
can
iterate,
but
we
don't.
We
miss
that
getting
feedback
part.
We
don't
have
a
consistent
way
of
doing
that.
C
C
C
C
There's
no
third
party
involved
like
qualtrics
me
personally,
sometimes
when
I
click
on
like
I,
don't
click
on
a
banner
to
take
a
survey
because
I
don't
want
to
go
off
into
quadrics
and
like
I
I,
don't
like
that
sort
of
stuff,
so
I
don't
know,
there's
something
to
be
said
for
it
being
implemented
in
this
way,
and
maybe
we
do
our
own
sort
of
In-House
implementation.
I,
don't
know.
F
That's
a
great
point:
this
has
a
human
aspect
to
it,
especially
since
Gina
you
were
so
on
top
of
it
and
participating
and
communicating
with
the
feedback.
The
people
giving
feedback,
but
I
agree
with
that
sentiment.
I
ignore
those
little
pop-ups
give
me
a
rating
of
one
to
ten
I'm
like
no
go
away.
I'm
busy.
C
Yeah
like
if
you,
in
the
way
that
is
implemented
here,
you're
at
the
user
feeling
like
you're
dealing
with
the
designer
of
this
feature,
and
it's
it's
kind
of
endearing-
forms
a
relationship
genus
book
about
that
sort
of
Open,
Source
Loop
that
we
have
with
our
community,
so
yeah
there's
definitely
benefit
of
doing
it.
This
way
or
the
other
way
as
well.