►
From YouTube: Verify & Release UX Team Design Review | 31 March 2020
Description
Design Review session of Verify & Release UX Team.
- Juan J. Ramirez - Frictionless Runners - Discovery
A
All
right
so
yeah
I,
just
put
some
something
for
today's
review.
I've
been
working
on
I
have
been
working
on
this
thing
for
Runner,
which
is
a
little
bit
okay.
Let
me
kinda
like
preface
everything
so
runner
is
a
very
special
team,
because
it's
not
the
classical
team.
That's
gonna
have
a
lot
of
ux/ui
challenges
or
implications,
but
it
has
a
lot
of
implications
in
the
they're
not
seen
in
the
UI
or
not
seen
in
the
final
user
experience,
but
like
they
impact
everything
that
we
do
in
CI,
CD,
right
and
yeah.
A
So
I
wanted
to
share
these
because
it's
so
early,
we
haven't
even
finished
the
problem.
Validation
cookies,
we're
almost
there,
but
we're
kind
of
the
process
of
finishing
these,
but
I
wanted
to
share
some
some
early
thoughts,
which
I
think
they're
very
interesting
and
they're
I.
Think
that
now
that
they
have
been
surprising
me
because
I
think
they
I
kind
of
knew
some
of
these
things.
A
B
A
That's
a
great
that's,
a
great
question
because
I
don't
have
a
specific
question,
but
I
would
definitely
love
to
get
that
feeling,
but
also
yeah
I,
understand
I,
think
so
it's
very
easy
to
get
blindsided
when
you're
working
in
something
like
runner,
because
you
don't
know
how
are
you
impacting
certain
themes
that
are
used
in
other
areas
of
CI?
So
you
know
if
we
change
something
in
runner
today,
he
might
change
the
way
that
the
cuban
air
esteem
works.
A
A
Yeah
I,
don't
I,
don't
me
I,
don't
think,
there's
any
kind
of
implications
for
anyone
right
now
in
this
team,
but
I,
don't
know
that's
what
I
don't
know
you
know
so
I
want
to
kind
of
get
that
general
feeling
of
these
looks
good.
This
is
it.
This
is
the
right
direction
or
you
should
look
more
into
these
type
of
things,
because
we're
still
early,
so
there's
still
a
lot
of
time
and
room
to
basically
change
course.
If
we
need
to
so
yeah,
that's
more
or
less
the
idea,
all
right.
So
let
me.
A
A
A
Making
it
easier,
smoother,
I
mean
there's
many
ways
that
we
have
been
calling
these,
but
I
think
the
bucket
name
is
frictionless
runners
and
we
are
on
the
problem.
Validation
for
that.
So
there's
kind
of
one
important
thing,
and
this
is
something
that
that
it
was
reading
the
direction
document
and
it's
actually
a
goal.
So
we
have
a
one
one
of
the
three
years
goal
of
the
verify
group
in
the
direction
document
is
that
we
want
to
provide
100%,
automated
setup
configuration
scaling
and
management
of
gitlab
runners
for
medium
to
large
enterprises
right.
A
A
These
customers
are
installing
runners,
configuring
runners,
managing
runners,
and
they
do
that
every
day,
because
their
CIS
depend
on
the
right
so
and
there's
many
ways:
the
runners
work
and
there's
people
who,
like
they
never
have
to
think
about
these
and
there's
customers
who
have
to
think
about
this
daily
and
there's
customers
who
do
it
once
and
then
they
can't
forget
about
it.
So
it's
a
very
wide
problem.
You
know
it's.
A
It
falls
into
many
jobs
to
be
done
because
it
it's
easily
something
that
you
can
basically
set
up
once
and
forget,
and
then
it's
not
a
problem
once
you
do
it,
but
there's
people
who
actually
have
to
provision
runners
in
weekly,
perhaps
in
a
daily
basis.
So
that's
where
we
want
to
kind
of
like
find
that
validation
right
wanna,
see
that
that
perfume
problem
that
we
see,
which
is
that
installing
my
runners,
it's
too
hard
for
customers
and
configuring
and
managing
the
drummer
runners
is
too
hard.
A
You
know
so
there's
a
lot
of
manual
process
and
there's
a
lot
of
challenges
when
it
comes
to
just
putting
a
runner
in
a
machine
and
then
connecting
that
to
your
grid.
Lab
instance,
and
then
like
interfacing
between
those
two
things
right.
So
what
we're
trying
to
validate
is
what
are
the
challenges
that
our
customers
are
facing
and
the
problem
itself
that
we
think
that
we
have
is
that
installing
runners
and
manage
managing
runners,
it's
a
very
hard
process.
A
So
that's
kind
of
the
problem:
I
guess
that
I
wanted
to
explain
what
is
a
runner
first,
because
I
don't
want
to
be
I,
don't
want
to
be
I.
Don't
want
to
assume
that
everyone
knows
what
a
runner
is.
You
know
it's
easy
to
fall
into
that
trap
of.
Oh
because
we
are
hauling
the
opps
and
we
are
all
in
verify.
We
kind
of
know
what
a
runner
is
and
I.
Don't
think
that's
the
case.
You
know
we
cannot
have
a
sense
of
what
the
runner
does.
What
are
you,
what
is
it
but
I?
A
Don't
think
everyone
understands
well,
what
is
it,
and
especially
outside
of
this
group
like
if
I
ever
I
likely,
I'm
gonna
present
these
for
the
UX
showcase
and
the
next
one
that
that
we
have
so
I
think
it's
important
to
explain
what
is
a
runner
right?
So
a
runner
is
a
continuous
integration
agent
right.
So
it's
an
agent,
it's
a
program
that
it's
used
by
you'd
love
to
delegate
all
the
CICE
jobs
that
that
are
running
in
indeed
lab
right.
So,
basically,
their
job
is
to
execute,
execute
those
pipelines
from
end
to
end.
A
So
someone
goes
and
creates
this
set
of
instructions.
Those
instructions
are
executed
by
the
runner.
They
are
not
executed.
By
get
love,
it
love
it
love,
it
self
doesn't
have
anything
to
do
with
that's
just
job
by
the
gitlab
runner,
so
runners
are
essentially
a
part
of
the
get
up
stock,
but
it's
a
completely
different
program.
You
have
to
install
it
in
a
different
way,
the
even
in
the
context
of
the
way
that
we
develop
runner
runner
is
something
that
it's
developing
a
different
cadence
and
in
a
different
repo.
A
So
it's
a
completely
different
animal
right
and
one
implication
of
that
is
that
usually
many
customers
have
the
runner
in
a
different
server
than
the
gitlab
server.
So
if
they
are
self
hosted,
they
might
have
two
different
machines.
One
further
eat
lab
and
one
further
get
lab
runner
and
I.
Think
I
mentioned
this
earlier,
but
runners
can
be
installed
in
many
different
ways.
Many
many
different
ways.
So,
of
course,
the
basic
thing
that
you
can
do
with
a
runner
is
insulating
your
machine
and
testing
your
machine
and
building
your
machine.
A
But
there's
many
ways
that
you
can
sell.
It
is
install
a
runner
right,
so
one
thing
that
customer
choose
is
to
use
a
cure
in
this
cluster,
which
seems
to
be
the
modern
approach.
Build
infrastructure,
but
probably
the
most
popular
one
is
customers
to
speak
an
instance
in
a
cloud
provider
and
then
using
doctor
machine.
A
They
install
the
runner
in
that
machine
and
then
they
register
the
runner
with
get
lap,
and
then
they
run
the
job
from
that
machine
dedicated
for
the
for
your
jobs
and
runners
can
be
installed
in
Linux
in
Windows
or
a
Mac
OS,
and
then
there's
this
concept
of
shore
runners,
which
it's
kind
of
a
weird
concept,
but
the
the
essentially
a
showrunner
can
be
assured
runner
in
any
instance.
So
you
can
have
show
runners
in
your
own
self
hosted
instances
of
gitlab
and
they
will
be
sure
for
everyone
who
uses
your
instance
right.
A
So
anyone
they
will
pick
jobs
that
are
run
in
your
instance,
so
they're
sure
freely
by
by
anyone.
That's
the
difference
between
a
shirt
and
on
a
specific
burner
and
a
specific
runner
is
a
type
of
runner
that
is
only
running
one
type
of
job
right.
That's
the
difference.
The
funny
thing
about
that
is
that
there's
like
kind
of
a
vague
concept
there,
because
we
also
have
show
runners,
shirt
runners
in
gitlab,
calm
and
those
are
used
by
everyone
in
the
community
right.
A
So
they
are
used
by
customers
who
pay,
see
I'm
CI
minutes,
and
then
they
use
them
and
they
pick
the
jobs
of
anyone
who
is
using
it
up
the
comm.
If
that's
their
choice
right,
they
can
also
use
our
soft
posture.
Brunner.
So
I
also
have
an
issue
somewhere
where
I'm
trying
to
fix
this
problem.
It's
kind
of
a
weird
confusion
and
I
know:
I,
don't
I
I
mean
I.
A
Think
customers
are
not
getting
confused
by
that
nowadays,
but
it's
probably
an
area
that
needs
a
little
bit
of
polishing,
so
it's
more
clear
for
the
outside
and
for
the
customers.
Here's
a
common
configuration.
So
you
have
a
geat
lab
somewhere
right
and
then
what
most
customers
do
is
that
they
have
on
AWS
ec2
instance
somewhere,
and
then
they
go
on
the
solder
run
order.
A
Sometimes
they
they
they
set
it
up
in
an
outer
scale
way
right
so
like.
If
the
runner
starts
getting
a
lot
of
email,
then
the
instance
how
to
scale
basically
to
meet
the
demands
of
the
runner
so
and
as
in
anything
about
infrastructure,
you
can
have
it
in
different
regions.
So
it's
closer
to
for
your
today
place
where
the
jobs
are
being
dispatch.
So
there's
there's
many
things
that
you
can
do
in
this
area,
and
customers
are
actually
doing
a
lot
of
interesting
things
in
this
area.
A
So
what
we
have
been
doing
with
the
problem,
validation,
research.
So
far,
we
had
four
four.
We
are
planning
to
have
five
holes.
We
had
four
so
far.
So
what
are
the
things
that
we're
trying
to
understand?
So
one
thing
is
why
customers
use
are
usually
in
sub,
hosted
burners
when
they
are
on
github.com.
You
know
that's
something
that
we're
very
interested
because
you'd
love
that
come
Husker
runner
right
and
if
we
and
we
cannot
sell
those
us.
A
Stander
experience
for
anyone
who
has
good
laptop
come,
so
you
don't
need
to
worry
about
runners,
because
you
can
basically
create
an
account
on
github.com
write.
Your
CI
get
up,
CI
Yama
file
and
then
ID
links
are
going
around
because
they'd
sure
get
LeBrons.
We're
gonna
pick
those
jobs
right,
but
we
have
customers
that,
although
they're
on
get
up
to
come,
they
say
like
no
I.
A
Don't
want
those
sure
runners,
I'm,
gonna,
install
my
own
Runner
in
my
own
machine,
don't
worry
about
it
and
then
they
register
the
runner
and
then
they
don't
use
the
showrunners
at
all.
So
we
won't
understand
why,
right
because
there's
there
must
be
something
about
that,
because
why
will
you
take
all
that
effort
downward
to
go
on
manage
your
own
infrastructure
if
we
already
are
providing
a
way
for
you
to
run
your
job?
A
Because
you
can't
host
your
runners
anywhere
and
anything
that
it's
Linux
machine
can
basically
run
our
kind
of
basically
hosts
the
runner
right.
So
it
could
be
a
SS
Google
digitalocean,
it
could
be
Linode,
it
could
be
on
pram.
You
know
it
could
be
whatever
right.
So
we
want
to
find
out
that,
because
we
think
that
that's
gonna
give
us
a
little
bit
of
direction
of
how
to
optimize
for
this
another
thing
that
we're
asking
is
well
what
is
their
current
process
to
install
and
manage
those
runners?
A
So
if
they
have
certain
processes
that
they
have
created
to
manage
the
runners,
we
want
to
learn
about
that
if
they
already
found
a
way
to
automate
it.
We
want
to
found
that,
because,
as
with
everything
in
software
because
we're
the
fact
that
we're
not
doing
it
doesn't
mean
that
people
are
not
finding
ways
to
out
or
maybes
already
right,
so
there
might
be
people
who
are
already
automating
certain
aspects
of
the
runner.
A
So
we
want
to
learn
about
that,
and
we
also,
of
course,
want
to
learn
what
are
their
biggest
pain
points
when
dealing
with
runners,
because
there's
potentially
a
lot
of
those.
But
we
don't
know
what
are
the
surface
areas
for
those
who
we
want
understand
that
and
then
finally,
we
want
to
understand
what
improvements
are
they
seeking
for
in
the
runner
experience
you
know,
so
we
believe
there's
always
room
to
improve
and
they
are
likely
demanding
for
certain
things
that
we're
not
necessarily
seen
in
the
community
issues.
So
we
want
to.
A
We
want
to
learn
about
those
things.
So
here's
some
of
the
foreign
findings
and
trends
that
we
have
been
seen
so
the
first
one
is
that
users
who
self
hosts
runners
they
do
it
primarily
out
of
security
concerns
right,
so
they
might
have
a
compliance
issue.
They
work
with
the
government.
They
cannot
use
something
like
the
Shirdi
table
runners.
They
have
to
have
control
of
the
machine
where
the
runner
lives
right.
So
that's
a
very
big
reason
that
we
we
hear
almost
in
every
call
right
on
in
every
interaction
that
we
have
about
these.
A
A
Another
interesting
thing
is
that
I
said
here
in
the
line
there
seems
to
be
the
most
popular
option
to
host
runners.
The
fact
is
that
everyone
we
talked
we
have
been
talking
so
far.
We
all
have
the
runners
in
AWS,
so
AWS
is
basically
the
place
where
these
are
runners
and
it's
not
a
surprise.
Just
because
AWS
is
the
cloud
computing
leader
so
like
they
probably
have
a
lot
of
infrastructure
there
right
yeah.
That
seems
to
be
a
very
popular
option.
A
The
AWS
thing
it's,
of
course
it
depends
on
the
service
that
they're
using
because
you
could
be
using
ec2.
You
could
be
using
eks,
you
could
be
using
Fargate,
that's
one
of
the
challenges
with
it
always
is
that
they
have
so
many
services
to
host
and
create
machines
that
they
could
be
using
any
of
those.
A
You
know
we
could
be
using
5000,
so
that's
gonna
be
I,
don't
know
like
a
hundred
dollars
more
per
month
or
there's
gonna
be
ammonium,
which
will
not
gonna
be
paying
see
a
minute.
So
people
like
that
they
have
that
flexibility
of
the
CA
minutes,
but
they
cannot
justify
that
to
their
cost
centers
and
to
their
bosses.
So
many
customers
would
be.
Basically
one
is
just
a
predictable
cost
rubric,
so
the
base
is
way
to
go
about.
A
That
is
just
pay
for
a
single
machine
max
it
out
in
whatever
sense
it
means
for
them
to
max
it
out
and
then
just
pay
that
monthly
recurrently
right.
So
that's
that's
a
big
big
part
of
the
Gil
experience
point
when
it
comes
to
pain,
eat,
love,
and
it's
also
kind
of
interesting,
because
many
people
said
that
we
did
love
it's
kind
of
hard
to
explain
to
their
bosses
or
to
their
decision
makers.
Oh,
we
have
we're
paying
for
gilda,
but
we're
also
paying
for
runner.
You
know
it's
kind
of
weird.
A
A
Another
thing
that
we
found
so
far
is
a
developers
in
general.
Don't
consider
the
process
of
installing
the
runner
painful,
which
interesting,
because
we
work
from
the
premise
that
they're
it's
a
painful
process.
So
what
I
take
from
that
is
that
they
don't
find
it
painful
because
most
of
them
they
do
it
once
and
then
they
forget
about
it.
And
then
the
runners
work
so
well
in
the
sense
that
they
never
break
mostly
never
break
that
their
general
experience
of
the
runner.
A
A
But
there's,
of
course,
a
lot
of
issues
in
the
configuration.
Not
everyone
is
there's
people
who
are
doing
kubera
kinetics
clusters,
there's
people
who
are
doing
ec2
instance,
there's
people
who
are
doing
many
things
so
yeah,
it's
a
challenging
area
because
they
don't
consider
consider
this
painful.
But
if
there's
definite
of
pain
hidden
under
that-
and
you
can
tell
that
because,
when
you,
when
you
talk
customers
about
the
idea
of
automating
the
process
of
installing
or
updating
the
runners,
they
get
super
excited
they're,
like
oh
yeah,
we'll
be
amazing.
A
I
love
that
so
you
kind
of
get
a
sense
that
they
actually
have
some
hidden
paints
that
they
are
not
revealing.
When
we
talk
about
these,
so
we
we
have
been
also
doing
a
couple
of
other
explorations
and
discovery
in
other
areas,
so
something
that
I
did
was
analyzing.
The
current
flow
that
we
have
for
the
Cuban
areas,
close
supervision
and
inside
deed,
lab
I.
A
Did
this
because
that's
what
we
sell
as
the
frictionless
way
to
install
runners
when
you
go
to
see
I,
see
de
configuration,
it
says
you
want
your
own
runner
install
a
key
varnish
cluster.
That's
basically
there's
a
flow
that
it's
optimized
for
doing
these,
and
the
interesting
thing
is
that
it's
not
frictionless
at
all.
If
anything,
it's
more,
it
has
even
more
friction
than
just
going
to
a
match
in
opening
the
terminal
and
installing
this
in
the
terminal
by
yourself.
A
You
know
it's
so
so
painful,
you
know
and
I,
don't
know
why
we
promote
that
so
heavily,
but
yeah
I,
don't
I
wish
I
had
more
thoughts.
Besides
the
fact
that
this
is
not
ideal
and
we
promote
these
pretty
heavily
there's
a
link
there.
I'm
gonna
show
those
lights.
If
you
want
to
check
the
actual
ratio
in
behind
that,
but
anything
that
shred,
bread,
yeah
anything
that
it's
red
or
yellow
here
means
that
there's
a
lot
of
friction.
A
Basically
their
selling
point
is
that
you
go
you
get.
You
gain
a
lot
of
speed
by
doing
these,
not
working
with
the
showrunners
provided
by
github
and
basically
their
service
service
is
just
a
wrapper
around
some
cloud.
I,
don't
know
what
cloud
and
then
it
allows
you
to
pick
a
machine
and
then
it
automates
the
process
of
picking
the
machine
and
installing
the
runner.
So
it
basically
makes
very
easy
the
process
of
putting
a
runner
in
a
computing
instance.
So
that's
interesting
to
use.
That
seems
to
be
something
that
that
we're
missing.
A
That's
pretty
much
that
the
discovery
they're
happy
doing
around
these,
so
that's
kind
of
ending
abruptly
because,
like
that's
where
we
are
right
now
in
the
process,
we're
still
doing
problem
validation
for
these,
but
I
wanted
to
share
it
with
you
with
the
team,
because
yeah
I
feel
there's
so
many
hidden,
hidden
angles
on
so
many
hidden
things
here.
So
one
I
kind
of
get
some
rate
of
the
room
and
understand
these
seems
accurate.
These
doesn't
seem
to
be
a
problem.
I,
don't
know
kind
of
get
some
temperature
and
validate
that
the
problem.
A
B
B
A
A
Know
this
is
dry.
You
know,
I
know
this
is
not
a
school
saying
like
oh
look
at
these
shiny
UI.
That
I
have
you
know,
but
I
feel
it's
important.
So
I,
don't
wanna
I,
don't
want
to
throw
anyone
under
the
bus
with
a
question
here,
because
I
know
the
dryness
of
these
but
I.
You
know
I'm
curious
about
something
you
know.
So,
if
you
go
to,
if
you
go
to
this
to
this
thing,
you
know
which
is
the
direction
page.
We
have
these
three
year
goals
of
the
verify
group
right.
A
We
have
a
be
a
tool
of
choice
for
groups
that
want
to
reduce
your
lead
time
for
changes
to
under
an
hour.
Part
of
how
we
will
achieve
this
is
by
taking
CI
CD
analytics
to
the
next
level,
provide
100%
automated
setup
configuration
scale
in
the
management
of
the
lab
runners
from
medium
to
large
enterprises
and
make
our
ml
/
AI
workflows
easier,
including
features
like
adding
the
ability
to
install
industry-leading
applications
like
cue
flow
to
your
kubernetes
cluster
I.
A
Wanted
to
talk
about
these
because
I,
don't
think
we
ever
have
talked
these
as
a
team
about
these
three
things
and
I
think
we
should
right
because
I
don't.
What
are
we
doing
to
achieve?
This
is
a
team
so
I
brought
this
up
because
I
think
frictionless
runners
Culver
part
of
that,
but
I
don't
think
it
covers
absolutely
everything.
I
think
mainly
because
these
medium
to
large
enterprises
thing
it's
very
vague
and
it
could
mean
many
things.
A
You
know
that
span
across
many
many
of
our
groups,
but
yeah
I
want
to
kind
of
segue
into
a
discussion
about
these.
How
we
talk
about
these?
How
are
we
planning
to
support
these
from
the
UX
perspective
and
yeah
I?
Don't
know
this
is
I
found
this
yesterday,
so
I
was
reading
through
the
direction.
I
was
like:
oh
wait.
We
actually
have
these
three-year
goals.
You
know.
C
Because
when
I
this
list,
I'm
like
hey,
this
is
very
much
aligned
with
what
we
are
planning
for
release
management.
So,
for
example,
a
lot
of
these
items
in
sea
ice
lean
analytics.
They
are
directly
linked
to
what
we
visit
for
the
Seattle,
City,
dashboard
and
I'm,
having
conversations
with
Nick
from
analytics,
but
I'm
not
talking
to
you
guys
about
it
right.
C
So
it's
a
great
that
you
show
this,
because
it's
really
really
puts
in
a
lot
of
things
in
perspective
that
there's
so
much
opportunity,
especially
because
yeah
those
are
the
North's
arts,
but
we
should
start
having
this
conversation
sooner
than
later,
even
to
see
like,
for
example,
what
data
points
are
even
available
right
now
or
in
what
stage
of
planning
you
guys
verify
and
analytics
are
so
that
we
can
leverage
and
build
something
together.
The
thing
like
and
I'm
just
only
thinking
about
dashboard
right
for
this,
because
that's
a
proposal
from
our
side
yeah.
C
D
It
makes
sense
to
know
to
discuss
these
kind
of
things
in
like
a
follower
thing,
big
session,
where
you
know
we
give
we
state
these
at
the
beginning
of
the
session
that
we
have
burries
state
their.
You
know
their
plan
to
come
up,
and
then
we
discuss
like
hey.
We
do
think
they
need
these
align
with
these.
You
know
these
know
what
stars,
but
we
do
think
that
these
kind
of
things
are
less
in
line
with
that
and
make
it.
A
Yeah
I
think
that
it's
interesting
because
when
I,
when
I
read
these
three
things
for
my
groups,
of
course,
these
wings,
a
bird
like
two-
is
a
very
runner
thing.
But
when
I
read
about
the
other
ones
front,
for
instance,
CITV
analytics
testing
has
so
many
of
those
initiatives.
Right
now
we
actually
just
shaped
rough.
A
A
Have
we
ever
even
thought
about
the
third
one
ever
and
I
will
say
personally
in
my
tenure
at
get
lab,
which
is
not
well,
it's
March,
8,
nine
9,
eight
point,
I,
don't
know
whatever
I
have
never
thought
about
this
one
right
and
I'm
curious.
If
you
guys
have
ever
thought
about
this,
one
particular
make
much
learning
and
artificial,
intelligent
workflows,
easier
right
that
seems
to
be.
D
I
actually
discussed
this
because
this
was
within
CI
and
I.
Think
it's
important
for
these
kind
of
Direction
pages
to
think
of
hey.
These
things
have
probably
changed
a
lot
recently
right,
like
I,
think
you
know
like
let's
look
seven
months
back,
let's
look
at
the
game.
History
and
I
can
assure
you
this
was
not
in
there.
This
is
our
adjustment
by
product
management
in
the
last
month
or
so,
and
in
a
sense
you
know,
like
I,
think
that's
one
of
the
hard
like
one
of
the
pain
points
with
these
Direction
pages.
D
These
are
very
product
management
coordination
like
directed
and
they
are
for
marketing
purposes,
almost
to
some
extent
and
the
way
for
keeping
us
in
line.
But
it's
it's
not
really
like
I
think
we
can
do
better
than
in
order
to
be.
You
know
like
you
who
is
like
product
managing
tighten
these
up
for
external
exposure,
they're,
not
so
much
used,
yeah
internally
to
really
say
Larry
the
actually
align
the
things
we
stayed
in
our
direction
pages.
D
A
Interesting
because,
like
I
I
agree
with
you
on
that
same
but
I
know
Darren
from
runner.
He
I
found
I
found
out
about
this
because
he
actually
pointed
out
this
one,
and
he
said:
okay,
we
have
this
goal
on
disease.
We're
gonna
use
his
North
sort
for
the
for
the
work
that
we're
gonna
be
doing
in
runner
for
the
foreseeable
future.
So
he
actually,
he
actually
did
being
these
particular
goals
to
what
we're
gonna
be
doing
in
the
future.
For
for
the
runner,
the
runner
group,
so
it
seems
that
everyone
is
I,
don't
know.
A
A
B
This
topic
from
the
rulli's
management,
like
director
level,
CI
CD,
dashboard
I've,
seen
that
for
the
cross
station
I
think
which
is
coming
up
next
week
and
if
you've
seen
in
the
document
in
the
agenda,
we
can
work
with.
You
Ian
suggested
to
define
a
schedule
like.
So
we
share
the
stage
groups
by
the
days
we
shared
here,
just
a
document
again
and
yeah
I
know
who,
on
so
test
it
test
is
also
that
testing
is,
has
a
place
a
spot
there.
B
C
Makes
a
lot
of
sense
and
I
think
I'm
having
my
one-on-one
with
Jackie
tomorrow
and
I
already
put
as
a
topic,
and
so
we
can
investigate
a
little
bit
further
and
come
to
these
states
were
prepared
about
what
we
can
learn
from
verifies
vision.
And
what
are
the
you
know?
The
metrics
are
the
steps
that
you
know.
We
match
our
own
vision
for
our
release,
management
and
I.
Think
I
can
also
bring
some
insights
from
from
the
analytics
team
or
for
the
things
that
I
learned
from.
C
Because
this
is
Jimmy
this,
it
just
makes
a
lot
of
sense.
This
topic-
and
we
mentioned
I-
think
also
you
mentioned
it
last
week
or
last
time
you
had
it
made
that
we
don't
necessarily
need
to
have
a
dashboard.
That's
not
the
point,
but
I
think
we
need
to
figure
out
what
the
strategy
that
we
wants.
You
as
a
state
group
as
I
this
stage
group
sorry
guys
I,
never
know
they
keep
changing
the
names.
C
There's
a
ops,
ops,
people
because
I
think
that
once
we,
for
example,
cover
the
user
flows
or
user
stories
or
even
whatever
is
the
data
or
the
end
points
that
we
want
to
whatever
showing
you.
Why
and
the
what
the
low-hanging
fruits
are.
I
see
that
leverage
a
lot
from
our
UX
findings
and
our
goals.
Also,
all
of
us
to
you
know
we
push
games
to
bring
this
together.
You
know.
A
A
A
You
should
be
able
to
be
more
a
catalyzer
in
those
discussions.
I
feel
that
I'm
doing
a
little
bit
of
that
job
with
Runner,
where
I'm
like
trying
to
give
Darin
a
lot
of
food
for
thought
and
create
that
foundation
for
the
future
work
ambition
that
we're
gonna
have
for
Runner.
You
know
so
I,
don't
know,
I
thought
it
was
important
to
bring
this
up.
A
Not
not
this
particular
thing,
but
just
in
general,
everything
for
we're
documenting
the
direction
of
the
ops
and
verify,
and
our
groups
themselves
I
think
it's
important
that
we
always
have
that
informed
thread
that
goes
back
and
forth
between
what
what's
changing
here
and
what
we're
doing
individually
in
you
know
we're
tactical
work.
You
know
so.
D
D
D
If
you
look
at
the
three
points,
he,
like
you
know
like
a
500%,
automated
setup,
be
the
tool
of
choice
of
groups
like
they're,
they're
kind
of
like
a
little
bit
like
an
OPR
format
and
I
would
say
like
alright.
This
this
page
is
being
edited.
You
know
constantly
and
there's
not
too
much
to
say
like
all
right.
This
is
the
three-year
goal
is
going
to
change
along
the
way,
and
the
thing
is
we
need.
We
need
something
like
a
baseline
and
we
can
see
how
well
we
got
over
a
certain
amount
of
time.
D
That
is
the
thing
where
this
direction
page
is
not
being
good
at
right.
I
would
say:
that's
exactly
what
opioids
are
good
at,
so
perhaps
we
should
investigate
how
we
can
do
that
and
say.
Alright.
This
is
the
current
goal.
Let's,
let's
create
our
opioids
for
this
quarter,
based
on
this
direction
page
and
then
see
how
far
we
can
get
and
actually
I'll
go
we're
doing
towards
that.
C
We
don't
I,
think
we
do
use
to
the
directions
page
like
an
assault
on
the
High
Line.
But
lacy
will
please
management
to
update
on
our
stars,
because
I
know
that,
for
example,
Jackie
she's
constantly
updating
the
direction
of
the
categories
based
on.
For
example,
what
we
found
from
usability
testing
or
going
from
come
from
competitor.
C
Blah
blah
and
but
I'm
not
sure
how
that
translates
to
like
the
overall,
how
that
relates
to
the
CI
CD.
So
maybe
we
interesting
because
I
think
that's
I
forgot
also
I
wanted
to
mention
that
in
the
beginning
Dmitry,
when
you
were
talking
about
yeah,
this
is
more
like
for
marketing,
and
this
is
really
p.m.
that
you
know
I'm
kind
of
curious
service
and
how
order
PMS
are
feeding
this
direction
pages
you
know,
is
it
like?
What's
the
what's
the
base
lining?
C
A
This
way
brought
up
because
I
think
that
I
have
never
with
my
PMS.
Never
this
cause
these
things
like
open
this
page
and
talk
about
them.
We
implicitly
talk
about
these
things,
I
guess,
but
we
never
say
we
never
have
discussions
in
which
in
which
we
say.
Okay,
this
is
the
direction
we
my
interactions
with
my
p.m.
so
far
happy
very
tactical
and
I.
Don't
know
if
that's
a
fall
of
my
own,
but
I
don't
want
that
to
be
the
case.
You
know,
I
want
them
to
be
more
strategic
right.
C
This
link
like
this
is
what
happens.
This
is
how
I
get
to
know
that
okay,
good
boy
three
days,
is
moving
from
twelve
ten
to
twelve,
like
3000
or
whatever,
because
it's
difficult
to
get
on
board.
The
trailer
is
constantly
moving
and
those
changes
sometimes
are
minimal
and
they
will
reflect,
for
example,
how
much
prioritize
my
work
or
how
we
prioritize
the
you
know
the
North
Stars,
so
yeah
should
see
what
change.
For
example,
it's
just
a
minimal
change
on
I.
Think
in
this
case
was
the
analytics
now
the
analyst
landscape.
C
A
It's
it
seems,
are
you
you
guys
are
ahead
of,
at
least
at
least
ahead
of
me
on
these,
because
my
PM's
are
not
doing
these
like.
These
would
be
super
helpful
for
me
just
getting
the
full
review
and
just
seeing
what's
the
change
that
that
already
it's
an
improvement
over
my
workflow,
because
it
it
allows
me
to
see
how
they're
thinking
right
they
the
changes
here
were
whatever
they
are
right.
Now
you
you,
you
read,
you
read
this
and
you're
like
okay,
she's
thinking
about
changing
the
granular
approval,
workflow
process.
A
B
C
Of
the
things
that
I
also
felt
like
that,
that's
why
I
asked
her
to
practically
like
beat
me
on
everything
and
I
was
being
assigned
but
being
assigned
to
something
needs
that
I
need
to
take
an
action.
This
is
kind
of
like
an
agreement.
We
team
between
Jackie
and
I
I
asked
her
whenever
you
change
category
directions
pages.
Please
ping
me
on
the
merge
request
car.
Let's
do
everything
that
that's
our
agreement,
so
maybe
we
can
experiment
with
our
pH
as
well.
Yeah.
A
A
B
A
C
B
Week
and
let
me
know
if
we
should
change
there-
are
times
of
this
I'm,
not
sure
if
that's
every
week,
the
same
time,
it's
actually
bi-weekly.
Yes,
it's
exactly
at
the
same
time,
so
maybe
it
will
have
to
find
in
your
time
for
our
for
this
design
review.
So
we
could
attend
that
because
that's
a
great
meeting
indeed-
and
we
had
in
the
past,
like
a
conversation
with
Diana
I,
think
Diana
and
Jackie
are
doing
a
lot
of
cool
things.
As
a
p.m.
B
you
acts
couple
like
a
pair
and
I
think,
a
lot
of
PMS
can
actually
like
well
learn
a
lot
of
good
things
from
that,
so
I
yeah
I'm,
not
sure
what
is
the
best
way
is
here
to
like
share
that
practice
with
probably
weekly
product
is
one
of
them.
Maybe
we
should
also
discuss
that
more
between
ourselves.
So
then
Hanna
can
show
what
they
are
doing.
A
B
Use
our
bi-weekly
meetings
to
share
those
things
between
ourselves
or
like
feel
free
to
ask
I.
Guess
it's
important
that
we
erase
these
questions
between
ourselves
and
then
so
we
have
the
topics
to
share
so
that
inspires
us
to
to
share
the
best
practices
yeah.
You
know,
at
least
in
this
team
and
then
we'll
see
that
I
know
that
we're
probably
that's
over
the
time
and
I
want
to
keep
anyone
longer
than
that,
but
so
Ayanna
thanks
for
sharing
Quan
thanks
for
presenting
in
the
first
place
and
I
love
these
conversations
yeah.