►
From YouTube: CI PM/UX Research Planning on 2020-06-10
Description
Our first session that we started with a goal to focus on discussing Problem validation and Solution validation in Verify:CI .
B
Awesome
so
welcome
everyone
to
the
CI,
a
P,
mu,
ax
research
planning
that
that's
the
first
session
that
we're
introducing
just
give
it
a
little
bit
more
time
to
talk
about
the
research
activities,
user
research
activities
in
CI.
So
thanks,
everyone
for
joining
and
yeah
I
didn't
have
like
I,
think
I
just
needed
one
actually
but
yeah.
B
So
basically,
the
session
is
planned
to
for
us
to
drop
items
that
we
think
will
need
user
research
or
maybe
that
we
already
running
is
research
on
or
maybe
we
need
help
of
team
material
or
your
vehicle
and
like
we
need
to
specifically
address
that
yeah.
Any
questions
about
go
all
of
this
session
before
we're
gonna
move
on
to
the
topics.
No,
that's
great
I
don't
have
any.
What
do
you
want
to
add
something.
C
Can't
think
of
anything
I
mean
it's
kind
of
what
Nadia
said.
We
kind
of
get
together
to
talk
and
I.
Think
Dimitri.
You
had
last
time
the
Ithaca
before
you
started.
We
talked
about
having
a
separate
meeting
to
talk
about.
Ux
research
needs
to
start
getting
those
off
the
ground,
so
we're
going
to
focus
that
conversation
I
think
separately
from
this
one.
But
this
will
feed
into
that
conversation.
D
C
D
B
E
So
there
yeah
I
had
a
couple
there,
so
the
first
one,
the
Jenkins
rapper
solutions.
Thank
you
to
Dimitri
for
creating
the
the
stuff
issue
for
that.
It
came
out
of
a
discussion.
I
had
with
him
that
we
were
having
difficulty
getting
users
to
test
the
to
beta
test.
The
Jenkins
wrapper
that
we
delivered
as
like
the
MVC.
The
first
thing
we
can
deliver
to
help
users
migrate
from
Jenkins
to
get
lapped
CI
CD,
so
Dimitri
had
create
this
issue.
E
After
discussing
with
me
that
maybe,
if
we
did
as
a
formal
research
project-
and
we
gave
a
little
bit
incentive
of
you-
know
the
the
the
thank-you
gift
car
that
we
give
out-
that
that
might
be
enough
incentive
to
get
participation.
I
am
aware
that
a
lot
of
users
that
initially
express
interest
in
testing
this
beta
version
I
got
a
lot
of
response
to
my
solicitation
for
testers
from
in
LinkedIn.
C
E
If
you
go
to
the
Jenkins
rapper
beta
testing
link
tissue
it,
it
does
call
out
that
there
are
in
testing
instruction
number
two.
There
are
requirements
and
limitations,
and
so
the
help
that
I
need
from
this
group
is
maybe
I
read
this
research
approach.
Maybe
we
don't
use
it
just
to
find
testers
for
the
Jenkins
wrapper.
E
But
the
approach
of
doing
that
in
an
emergency
kind
of
skipped,
the
steps
of
problem,
validation
and
solution,
validation
I
still
want
to
go
back
and
do
that
and
skipping
all
that
really
expose
that
we
were
shooting
in
the
dark
of
what
the
users
wanted
and
I
think
we
missed
I.
Think
we
missed,
because
there's
not
a
lot
of
interest
in
this
wrapper
so
either
like
I
said:
I
I,
don't
know
what
the
lack
of
interest
is.
Is
it
because
we're
not?
E
C
E
C
What
I
was
gonna
say,
Tao
I
think
you've
got
two
problems
that
you've
identified
that
you
need
to
solve.
You
need
to
figure
out
one.
Why
is
this
thing
not
getting
used
that
we
made
and
two?
What
is
it
that
they
actually
want,
and
it
may
or
may
not
be.
This
thing
is
I
think
those
are.
Those
are
two
almost
separate
efforts.
Okay,
because
they
may
not
be
the
same
person.
You
could
talk
to
you
if
they
are,
you
can
talk
to
them
about
both,
but
yeah
III
think
it's
two
separate
things.
Oh.
D
E
E
C
D
C
We
kind
of
went
a
little
backwards
like
you
said
we
jumped
into
the
solution
before
we
understood
the
problem,
but
now
that
we
have
it,
let's
understand
how
it's
meeting
or
not,
meeting
people's
needs,
and
then
we
also
need
to
jump
back
like
you
said
and
start
from
beginning
to
say
what
is
the
need
and
you
can
get
some
of
that
from
the
solution.
Validation.
C
Conversations
with
people
by
having
the
conversation
without
this
solution
here
is
also
I,
think
needed,
because
you
need
them
to
also
jump
back
out
of
the
solution
with
you
to
talk
about
their
use
of
Jenkins
talk
about
their
versioning,
how
they
use
it.
What
do
they
need
from
us
if
we
were
suppose
if
we
were
to
provide
them
some
sort
of
Jenkins
solution?
What
what
do
they
need
it
to
do?
So
you
might
be
able
to
combine
these
efforts
in
one
session
with
somebody,
but
you
would
really
need
to
find
somebody
who's.
E
E
C
E
All
right
so
I
need
to
create
one
maybe
beat
the
gun
I
we
could
create
one
together,
like
you,
can
look
over
my
shoulder
as
I
create
a
UX
research
issue
for
the
stepping
back
and
finding
out
what
our
users
do
want
as
a
a
solution
for
them
to
migrate
from
Jenkins,
and
that
one
would
be.
Here's
there's
the
other
question
that
I
have
for
all
of
you
is.
We
know
there
is
a
general
problem
which
is
customers
and
sales
prospects,
don't
know
how
to.
E
C
E
Okay,
so
that
sounds
good.
The
Ithaca
I
did,
if
you
don't
mind,
the
Coffey
chat
that
I
sketches
with
you
I
think
later
this
week,
I
might
use
some
of
that
time.
You
can
just
look
over
my
shoulder
as
I,
create
an
issue
I
think
it's
tomorrow.
Actually,
okay,
that
helps
me
Laurie.
Thank
you
for
that
input,
so,
in
which
case
I'll
leave
this
linked
issue
for
the
Jenkins
wrapper,
solution,
validation
and.
E
Dmitry
has
some
good
questions
for
me
to
work
through
on
what
my
what
I
want
to
get
out
of
it
I'll
add
those
details
to
the
description.
You
know
what
I
might
stop
me.
I
might
I
want
to
leave
our
coffee
chat
alone.
I'll
create
a
separate,
deep,
drag
session
for
us
to
work
on
these
two
UX
research
issues
and
once
I
define
what
I
really
want,
and
the
issue
is
the
next
step
then
Laurie
to
get
help
from
you
or
take
our
best
stab
at
the
screener
I
forget
the
process.
It.
C
E
B
D
B
Have
that
those
two
processes
are
described
in
a
handbook
and
for
the
problem,
validation
that
the
DRI
is
p.m.
and
Lauren?
Please
correct
me:
if
I'm
wrong,
so
problem
validation
process,
that's
Drive,
well
driver!
The
idea
is
the
PM
and
I
think
it
would
be
great
if
product
designer
would
be
involved,
helping
you're
not
facilitating,
but
like
at
least
like
listening.
You
know
like.
C
B
D
C
D
C
There
I
think
there's
two
here:
Demetri,
there's
a
solution,
validation
with
the
thing
that
they've
already
made
for
the
rapper.
What
what
is
this?
Why
are
you
using
this?
What's
going
on
with
this
bag
that
kind
of
solution
validation
with
that
solution,
then
there
is
a
problem
validation
because
they
move
so
fast.
They
didn't
get
to
do
that
part
in
the
way
that
it
should
have
been
done.
C
There
was
a
lot
of
assumptions
made
and
now
our
solution
is
not
getting
met
getting
used,
so
we
need
to
back
up
and
look
at
it
from
the
problem:
validation
lens,
so
you're
using
Jenkins.
What
would
you
like
to
do
would
get
lehem
him
and
Jenkins
like
how
can
we
help
you
so
vacuum
that
up
so
there's
they're,
two
different
efforts.
C
But
I
think
in
this
case
that
if
Tao
wanted
to
have
those
conversations
with
one
customer
about
hey,
let's
talk
about
how
we
can
help
you
now
I
have
a
solution.
Let
me
show
you
what
this
is
walk
through
it
with
that
person
to
get
their
feedback.
I
think
that's
also
very
applicable
in
this
moment,
because
she
was
the
one
who
was
so
close
in
helping
to
create
the
solution
as
well.
E
D
I,
like
like,
we
like
I,
want
to
loop
back
to
my
first
question:
who's
gonna
be
DRI.
Are
we
gonna
split
it
off
and
split
into
separate
researches
like
one
is
gonna
focus,
focus
on
solutions.
Elevation
yet
or
is
gonna
be
problems
I
fill
addiction
are?
Are
we
gonna
make
it
a
joint
effort,
in
which
case
we
are
still
unclear?
Who's
gonna
be
main
DRI
for
this,
like
I.
Just
want
us
to
be
super
clear
here.
So
now
we're
like
that.
We
know
what
we
want
and
that
we
can't
before
then
that
way,
I
think.
C
C
D
I,
like
I,
think
as
the
scope
is
small
from
the
solution.
Validation
perspective.
These
small
think
that
would
a
grain
of
salt,
but
like
not
super
huge,
it's
specific
part
of
the
application.
I
think
this
is
gonna,
be
a
good
project
for
you,
physica
to
start
rolling
in
and
I
will
be
your
backup
with
any
questions
you
have
and
get
you
set
on
on
the
way
get
you
ingrained
within
the
UX
research
process.
You
know
we're
actually
you're
gonna
be
as
new
as
me
with
some
of
the
things
regarding
the
new
tool,
a
Laurie.
B
E
B
E
E
E
Okay,
so
then
the
next
one
I
linked
to
this.
This
is
a
stub
issue,
I
created
based
on
a
discussion
and
a
request,
suggestions
from
Jason.
Let
me
back
up
so
what
we
were
delivering
in
13.1,
that
is,
continuation
of
work
from
13.0
is
sarah.
Our
fine
engineer
is
putting
out
a
very
initial
version
of
the
directed
acrylic,
a
silly
graph,
the
the
dag
and
she
was
not
comfortable.
E
She
was
more
comfortable
calling
it
a
beta
and
collecting
feedback,
as
opposed
to
making
Amy
warranty
that
this
is
a
fully
baked
new
new
feature
to
visualize
a
dag
pipeline
and
Jason's
suggestion
was,
if
we're
going
to
call
it
a
beta,
let's
truly
run
it
as
a
bailer
beta
and
collect
feedback,
and
there
was
Sarah
need
to
make
some
reference
to
this.
An
issue
about
where
to
put
feedback
and
also
Jason
needed,
wanted
to
go
out
and
make
a
Twitter
post
and
say:
hey.
We
have
this
bag
pipeline
in
beta
version
out.
E
E
Should
we
formalize
this
as
kind
of
a
research
thing
and
Thank
You
Dimitri
for
the
questions
that
you
think
we
should
add
to
the
the
description.
I
haven't
had
a
chance
to
go
copy
and
paste
it
in,
but
maybe
we
can
talk
about
it
in
this
in
this
meeting.
Is
this
something
or
E
that
sounds
to
you
that
it
is
a
kind
of
a
problem
validation
that
kind
of
organically
came
about
out
of
development.
E
C
C
I
think
we
just
have
to
have
a
mechanism
to
figure
out
who
all
is
going
to
look
at
the
feedback
and
how
long
we're
gonna
let
that
run
and
what
are
we
looking
for
in
the
feedback
to
say
this
is
a
go/no-go
success
or
failure,
but
that's
how
I
that's
all
I
would
say
that
we
need
to
define
for
this
process.
In
addition
to
left,
Dmitry
has
here,
okay,
so.
C
C
Okay,
so
what
I
said
was
we
in
addition
to
what
Dmitry
has
there
in
his
bulleted
list?
He's
got
a
section
detailing
our
hypothesis?
We
also
need
to
describe
what
success
and
what
failure
looks
like
based
on
the
anticipated
feedback
that
we're
going
to
receive,
because
we
are
asking
them
for
their
feedback.
So
how
do
we
know
if
it's
not
doing
what
it's
supposed
to
be
doing
so
we
need
to
figure
out
like
what
that
looks
like,
so
we
can
go
back
and
look
at
the
feedback
and
go
oh
okay.
C
D
So
mainly
who's
gonna
be
Bri
for
this
research
in
a
way,
I
would
say
right.
Let's
I
think
we
can
handle
this.
Similarly,
as
any
other
solutions,
elevation,
but
more
publicly
created
I
would,
by
the
way
wanna
as
a
related
point.
The
issue
we
now
have
created
is
gonna
include
our
details
on
how
we're
gonna
set
this
research
up
at
least
because
I've
been
putting
in
that
information
within
this
issue.
E
I
think
I
think
we
need
a
separate
UX,
a
separate
issue
under
our
UX
research
project
that
has
all
of
the
sections
like
the
hypothesis
and
all
that
that
you're
suggesting
Dimitri
but
part
of
what
you're
suggesting,
which
is
guidance
on
what
type
of
feedback
or
guiding
the
user
on
what
feedback
to
give
us,
we
can
add
supplement
in
the
description.
Is
there
a
template?
C
Necessarily
something
that
we
like
I
know
like
Jackie,
the
PM
Jackie
she's
got
like
a
Google
situation,
a
Google
document,
or
something
that
she
uses
when
she
interviews
customers.
But
it's
it's
not
passive.
It's
like
she's
doing
it
with
them.
So
I,
don't
think
we
Dmitry
do
you
know
if
any
of
the
other
designers
are
doing
anything
like
this,
but.
D
I
have
been
asking
around
based
on
this
issue
like
hey.
If
anybody
else
do,
we
have
any
other
issues
in
beta
which
we
are
doing.
Something
of
a
similar
thing
with
I
got
a
few
responses,
and
basically
the
only
thing
that
that
is
there
is
like
there's
some
setting
in
our
personal,
like
customization
options
that
features
the
words
experimental
and
data.
Apart
from
that,
there
is
no
like
a
real,
like
any
collection
of
data
surrounding
that.
D
Then
there
is
a
issue
in
progress
currently
being
worked
on
by
camellia
from
I
think
she's
in
security,
if
I
remember
correctly,
and
she
is
offering
like
an
like
a
bat
attack,
the
same
as
we're
doing
for
this
issue
and
I
have
suggested-
or
at
least
I
have
I've
made
in
common
in
that
in-progress
issue
that
for
verify.
We
are
thinking
of
like
implementing
an
issue
for
collection
of
feedback
from
users
using
this
feature
and
we're
implementing
in
a
certain
way.
So
there
might
be
a
chance
that
she
will
be
following
suit.
That
way.
D
E
This
I
may
use
something
like
this
Demitri
for
the
feedback
for
the
dag
beta
version
and
then
all
of
the
comments
you
have
move
it
over
to
a
research
issue
in
our
research
UX
research
project,
but
so
I
just
call
it
something
Beit
public
testing
to
let
them
know
it's
open
to
anyone.
I
give
a
short
little
paragraph
on
the
background
and
then
I
just
give
them
the
instructions
on
what
in
this
case,
I
had
to
you
normally
give
them
stretches.
Maybe
we
just
go.
E
The
instruction
is
here:
go
look
at
this
dag
and
then
give
us
your
feedback
in
a
comment
in
this
case,
because
Jenkins
had
some
very
specific
things:
the
user
had
to
set
up,
I,
went
ahead
and
and
and
spelled
out,
the
steps
and
I
numbered
them
so
that
the
user
can
refer
to
step.
Number.
Four
doesn't
make
sense,
you
know,
or
I
got
I
got
stuck
on
step
number
four,
which
I
know
it's.
E
They
couldn't
install
the
Jenkins
Runner
container
builder
and
I,
don't
if
and
then,
and
then
I
did
have
a
section
for
documentation
and
I
agree
with
you
Dmitriy
in
your
comment
that
the
the
feedback
issue
for
the
dag
beta
should
link
to
some
documentation,
but
a
little
bat
if
everyone's
okay
with
it
I
will
I
can't
well
I'm,
probably
not
the
usual
DRI
for
the
solution.
Validation
issue
for
the
dag
beta,
but
I
don't
want
to
put
it
I,
don't
know.
What
are
y'all
saying.
D
B
Yeah
I
think
for
us
it's
also
better,
like
we
will
have
this
for
equipment.
I
think
I
set
up
this
every
the
other
week.
Let
me
just
double
check.
We
have
it
yes,
bi-weekly
yeah
and
kind
of
like
running,
maybe
a
little
bit
ahead.
I
think
we
should
be
cautious
with
the
amount
of
research
studies
we
plan.
It
looks
like
you,
prob'ly
Laura
can
confirm
my
words.
Usually
it's
pretty
like
heavy
on
the
initiatives
plus
also
we
have
design
work,
but
yeah
I
think
the
best
is
Dimitri
and
ichika
to
answer
this
question
together:
okay,.
E
B
Clean
up
my
sound
like
you,
what
we
can
do,
maybe
you
can
plan
some
efforts
here
and
there
for
both.
Let's
see,
yeah
thanks
a
lot
I
love
that
we
started
having
these
discussions.
I
think
this
is
definitely
like
nice
and
I
hope
you
will
get
a
bit
more
up
to
speed
to
doing
those
research
studies
more
in
CI.
So
thanks
a
lot.
Everyone,
okay,.