►
From YouTube: Testing / Runner / UX / PM / Research Sync 2021-01-06
Description
Darren (Runner PM), James (Testing PM) and Rayana (Designer) talk about next major research initiatives on the last joint call.
A
Here
we
go
so
this
is
the
testing
and
runners
sink
for
january,
6,
2021
and
hannah.
We
kicked
off
with
just
talking
about
splitting
this
call
up
actually
to
have
it
focused
on
runner
as
you
and
I
now
have
a
one-on-one
set
up
so
we'll
record
that
as
a
separate
sync
and
hand
this
one
back
over
to
just
you
and
darren.
B
Yeah,
I
just
want
to
share
this
app.
I
already
shared
with
you
james
yesterday,
and
I
mentioned
this
to
you
there
I
think
a
week
ago,
or
maybe
last
year
I
don't
even
know
anymore
anyways.
I
finally
created
this
epic
that
I'm
gonna
try
to
I'm
gonna
use
to
track
the
things
I'm
working
on,
so
that
you
can
throw
any
items
that
need
design
so
that
we
have
a
central
place
to
communicate
about
what
I'm
doing
next
and
what
is
the
priority
for
us.
B
Of
course,
this
we
can
discuss
this
synchronously
and
also
doing
a
one-on-ones,
but
just
so
you
know
this
is
how
I'm
tracking
now
so
for
context.
This
is
what
I'm
working
on
the
the
runner
item.
So
everything
that
is
below
the
cut
line
I
haven't
started
yet,
and
the
idea
is
that
yeah,
once
we
have
a
design
proposal
that
is
ready
to
be
weighed
by
engineers
are
ready
to
move
to
the
next
step.
B
B
See
how
it
goes,
but
I
think
it's
important
to
kind
of
try
to
have
this
transparency
about
my
plan
and
another
thing.
This
is
also
an
item
I'm
used
to.
I
think
I
showed
this
to
you
before,
but
so
you
know,
I
create
weekly
plans
about
everything
I'm
doing
so
if
you're
curious
or
if
you
think
that
I
should
re-prioritize
something
other
than,
for
example,
learning
understanding
it
like
runners
this
week.
Let
me
know:
that's
how
I'm
planning
on
organizing
things.
C
No,
this
is
super
organized.
The
only
question
I
have
is
in
looking
at
the
which
is
really
well
done.
I
love
the
cut
line.
That's
pretty
cool
on
the
epic,
try
to
think
for
a
second:
how
to
talk.
How
to
bring
this
topic
in
here.
Jackie
had
created
a
couple
of
issues
around
us
needing
to
do.
I
guess
both
problem
and
solution,
validation
for
that
overarching
enterprise,
epic,
so
I
need
to
get
back
there.
C
So
I
don't
know
if
you
want
to
capture
the
fact
that
at
some
point,
maybe
starting
next
week,
we
actually
have
to
start
thinking
about
scheduling.
You
know,
scheduling,
interviews
and
all
that
stuff.
If
that
also
goes
into
this
view,
that's
the
only
question
I
have,
but,
but
this
is
this-
is
this
makes
a
lot
of
sense.
This
is
perfect.
B
Yeah,
I
think
it's
fine.
Unless
what
are
you
talking
about?
Is
this
one
I
feel
like?
If
there
is
no
issues?
It's
fine,
if
it's
not
there
in
the
in
the
list
on
the
list
yeah,
you
can
communicate
that
that
is
happening.
I'm
also
fine.
If
you
want
to
create
an
issue
just
for
the
sake
of
having
a
placeholder
there,
and
let
me.
C
Kind
of
sit,
kind
of
verbalize
kind
of
where
my
head
is,
and
you
kind
of
tell
me
what
makes
sense
so
right
now
we
have
that
the
epic
you
just
linked
right.
Let
me
make
sure
it's
the
right
one.
This
is
big
gory,
epic
right,
this
big,
huge
behemoth
of
oh.
This
is
research
initiatives
on
okay,
gotcha
did
a
research
one,
so
this
has
oh
so
there's
actually
a
research,
epic
as
well
interesting.
Okay,
so
I
think
there's
also
a
different
one
for
runners.
I
need
to
find
that
from
jackie
yeah.
C
But,
realistically
what
we
wanted
to
do
was
to
step
back
and
kind
of
look
holistically
and
long-term
about,
as
we
talked
about
what
we
wanted
right
and
we
have
all
of
this
information
and,
as
a
matter
of
fact
just
before-
and
I
re
I
apologize
for
this-
I
didn't
realize
it
was
going
to
become
a
research
type
of
customer
meeting.
I
got
pulled
into
a
meeting
with
one
of
our
very
very
large
customers
here
in
the
united
states,
we're
a
very
large
enterprise
customers.
C
They
manage
run.
You
know,
git
lab
at
scale,
they
manage
runners
at
scale,
they
have
multiple
teams
and
the,
and
when
I
was
brought
into
the
meeting
by
the
solutions,
architectural
technical
account
manager,
it
quickly
became
oh.
This
is
really
about
understanding
the
enterprise
management
needs
for
the
runner.
So
I
have
to
go
back.
I
don't
have
time
today
and
I
meant
to
do
before
the
holidays,
but
things
kind
of
got
away
from
me
with
the
timing.
C
C
Story
short,
I
know
we
need
to
organize
the
enterprise
admin,
epic,
the
current
issue
and
then
decide
okay.
How
do
we
now
potentially
validate
the
problem
if
we
still
need
additional
problem
validation?
What's
the
next
step
in
terms
of
a
potential
solution,
proposal
right
and
then
the
solution
valuation-
and
I
know
there's
all
that
work
we
need
to
tell.
B
Okay,
that's
awesome
and
I
think
it's
fine.
If,
once
you
create
this
initiative
and
then
we
have
like
a
place
to
have
this
type
of
discussions,
if
they're
high
level
or
if
they're,
really
technical,
small
designs,
you're
free
to
just
throw
something
on
this
epic
and
then
tell
me
hey
hyuna.
I
want
you
to
look
into
this
and
yeah
if
not,
let's
just
keep
having
a
discussion
about
about.
B
What's
what's
up,
because
that's
also
another
reason
why
I
try
to
track
my
work
like
this
and
that's
why
I
worked
with
jackie,
and
I
is
that
there's
so
many
big
items
that
sometimes
it's
difficult
to
visualize,
where
I
am
on
the
workflow,
but
also
talk
about
capacity.
So
if
I'm
working
on
a
big
validation
item,
I'm
probably
not
gonna
have
a
lot
of
time
to
work
on
five
tactical
design
items
for
two
teams.
B
C
I
mean
our
next
focus
days
worth
of
work
on
the
stepping
back
and
understanding
where
we
might
want
to
go
with
enterprise
management,
and
then
then
we
say:
okay,
we
know
we
where
we
might
want
to
go.
Here's
how
this
reset
might
fit
into
internet.
Does
it
make
sense
western
pause,
the
tactical
in
the
distribution.
B
B
We
just
said
it
the
registration
token
that
issue
what
I
would
generate
there,
it's
something
that
I
can
solve
in
well,
whatever
one
two
days,
if
I
have
the
time
to
sit
and
then
just
break
issues
down
to
the
designs
and
have
a
discussion,
what
I
feel
there
is
that
I
need
to
understand
the
back
end
input
and
that's
what
I'm
not
getting
so
much
there.
That's
actually
one
of
the
points
I
I
want
to
add
here.
B
What's
the
best
way
for
me
to
stay
informed
about
these
back-end
decisions
and
get
to
know
the
product
rather
than
just
pinging
people
and
waiting
for
their
their
response.
So
if
I
can
run
you
understand,
if
I
can
just
get
their
input
on
that
small
tactical
problem,
I'll
generate
the
design
we
jump
to
the
next
point.
C
C
We
stepped
back,
we
organize
the
overall
enterprise
admin,
thingy
right
and
and
the
reason
I
said
we
step
back
and
do
the
overall
big
one.
Is
that
once
we
kind
of,
would
you
want
to
understand
how
we
might
design
this
new
enterprise
management
solution?
Then
we
can
have
this
one,
sync
meaning
with
the
right
folks
on
the
running
team.
Right
back
and
engineering
and
say
reverses
us,
like
hey
reset
registration
token,
do
we
have
a
back
end?
Do
we
need
to
do
back
in
api
work
for
this?
C
This
other
thing
that
we
need
to
back
this
right.
Here's
the
vision
and
we
just
go
through
one
sync
meeting
and
we
can
say:
okay,
if
you
want
to
do
version
offset
that's
all
new
functionality.
If
you
want
to
do
a
registration
token,
that's
existing
functionality.
We
just
have
to
link
in.
If
you
want
to
do
this,
that's
you
know
I
mean
we
can
just
do
it.
C
One
time
like,
and
that
way
it's
a
a
really
good,
solid
knowledge
chain
for
you
as
well,
and
it
won't
solve
every
problem,
because
obviously
there
will
be
new
things
that
come
up
as
we
go
through
iterations
that
we
wouldn't
cover
in
the
big
one
thing.
But
I
think
that
would
be
the
I
feel
as
if
that'd
be
the
best
use
of
everyone's
time
to
get
everyone
kind
of
grounded
like
here's.
The
current
version
that
rayna
and
darren
have
they
can
poke
holes
in
it
and
then
and
by
poking
holes.
C
What
I
will
sign
up
to
do,
then,
is
it's
actually
on
my
own
personal
to
do
this.
I
don't
typically
create
another
issue,
because
I
have
to
remain
like
floating
list,
but
looking
at
my
crazy
calendar,
my
goal
was
to
focus
on
the
enterprise
management
stuff
tomorrow
and
potentially
friday.
So
I'll
make
sure
I
don't
have
some
time
on
my
calendar
to
do
that
and
and
then
once
I
get
my
head
clear,
then
I'll
pin
you
with
hey.
C
B
B
C
A
A
I
actually
had
a
great
conversation
with
my
team
about
this
yesterday
and
they
made
the
point
of
I
mean
it's
always
been
an
assumption
of
mine
that
they
need
to
set
up
a
runner.
First,
that's
always
the
prerequisite,
but
we
have
functionality
in
testing
that
doesn't
require
a
runner.
All
you
have
to
do
is
upload
test
reports
and
you'll
start
to
get
verify
features
enabled.
A
So
we
want
to
explore
through
a
survey
or
of
existing
customers
or
conversations
with
existing
customers
who
are
scm
customers,
but
not
verify
is
that
functionality
that
we
can
get
them
to
tap
into
and
that
will
help
inform
for
us
hey.
We
need
to
enable
an
api
to
get
that
make
that
available
to
them,
so
they
could
upload
from
their
existing
external
ci
solution
and
start
to
expose
them
to
some
of
those
verified
bits
and
pieces,
especially
then,
the
things
we
build
on
top
of
those
reports
that
are
premium
and
ultimate
here.
A
And
in
the
notes
here
which
we're
not
I'm
not
sharing
my
screen
but
I'll
verbalize,
I
also
saw
an
anecdote
in
product
that
of
self-managed.
A
good
chunk
are
on
aws,
so
just
curious
about.
Is
there
an
opportunity
for
us
to
just
spin
up
an
ami
and
make
it
available?
So
it's
super
simple
for
somebody
to
start
with
a
runner
if
the
rest
of
their
infrastructure
is
already
in
aws
to
do
something
as
simple
as
uploading
those
reports.
A
If
we
don't
go
down
the
api
route,
the
other
one
that
we've
looked
at
is
even,
if
you're
not
using
verify
for
anything
else.
What
about
code
quality?
You
can
get
that
scan
done
with
the
runner.
That
way,
and
maybe
it's
a
specific
code
quality
ami,
that's
built
on
top
of
a
super
lightweight
runner,
so
they
don't
have
to
spend
too
much
on
that.
So
just
some
thoughts
that
I
had
and
wanted
to
talk
with
this
group
about.
How
do
we
go
validate
these?
What's
that?
C
I
forget
the
chap's
name
I'll,
find
out
this
and
then
in
parallel
to
that
gosh.
What's
what's
his
name?
Why?
All
of
a
sudden
his
name
escapes
me?
He
works
with
the
alliance
team,
it's
completely
drawing
it
blank
darwin
that
one
subway
has
been
doing
a
bunch
of
work
on
a
clink
on
confirmation
templates
for
setting
up
the
runners
in
aws.
He's
really
keen
on
that.
C
Because
of
the
same,
the
anecdote
you
mentioned
in
terms
of
heavy
usage
on
aws
for
self-managed
he's
keen
on
aws
automation,
so
the
work
that
davin
darwin
saw
has
been
doing
the
fulfillment
team,
the
growth
theme,
sorry
paying
me
back
in
november,
so
they're
doing
some
work
on
that
as
well,
and
then
the
third
leg
of
the
work.
That's
being
done.
This.
This
space
was
actually
being
done
by
the
runner
team.
C
Some
time
back,
where
we
created
a
some
automation,
setting
up
a
virtual
machine
with
all
that
good
stuff
first
on
gcp,
but
then
we're
going
to
change
the
pattern
for
aws.
So
I
think
you
just
get
me.
I
think
you
should
probably
get
plugged
into
those
three
different
conversational
threads
and
kind
of
see
where
it
goes.
But
at
least
that's
that
piece
of
your
own
of
your
own
agenda
and
picking
your
ace
think
I'm
gonna
try
to
find
the
right.
C
I
kind
of
you
know
what
for
me
personally,
I
kind
of
you
know
my
gut.
How
should
I
say
this,
I'm
thinking
I'll
pay.
I
think
the
pattern
that
georgie
created,
which
is
on
the
running
team,
that
planned
with
using
and
I'll,
find
the
repo
and
give
it
to
you
after
this
call
is
the
way
I
I'm
thinking
about
it
that
we
should
go.
It
doesn't
mean
that,
like
the
terraform
patterns
or
the
confirmation
patterns,
aren't
fine,
not
usable
as
well,
but
obviously
you
have
to
maintain
templates.
C
C
A
Cool
that'd
be
great
yeah.
Anything
we
can
do
to
help
get
somebody
we're
using
a
little
bit
of
verify
even
like,
if
you
don't
want
to
bring
everything
over
just
run.
Like
start
one
additional
job
one
job
in
a
pipeline
to
get
code
quality
and
run
that
and
see
how
it
works
and
see
how
it
integrates
into
your
merge
requests.
A
A
A
We
might
be
able
to
survey
some
of
those
folks
or
drop
a
survey
into
there
of,
if
you're,
using
scm,
but
not
verify
what
are
bits
of
functionality
or
what
are
problems
that
you're
looking
to
solve
that
your
current
solution
doesn't
are
those
things
that
we
can
do
without
you
like
migrating
a
pipeline,
I've
been
down
that
road
of
moving
ci
systems
and
moving
all
of
those
pipelines
is
always
the
hardest
part
right.
You
have
to
replicate.
All
of
that.
That's
that's
super
painful.
A
If
it's
additive
instead,
is
that
an
incentive
enough
for
them
to
try
it?
That
might
be
worth
exploring
a
little
bit
more
awesome
that
answers
my
question
I'll
run
down
those
three
leads
as
far
as
the
runners
go
and
we'll
start
some
of
our
own
research
on
just
exposing
an
api
to
upload
those
files
as
well
and
see,
if
that's
that
might
be
our
minimum
viable
change
there
of
getting
more
folks
using
verify.