►
From YouTube: CI Adoption Journey Research - Kick Off - August 12 2020
Description
Lorie Whitaker and Andrej Kiripolsky kick off the UX research effort to learn more about the CI Adoption Journey
00:02 Start
12:20 Product direction input into the data analysis
20:28 Individual vs organizational perspective
A
Everybody
else
who
can't
make
it
today
so
thanks
so
much
guys
for
and
gals
for
coming.
I
appreciate
it
what
we're
going
to
do
andre
and
I
are
going
to
present
a
little
bit
about
the
project,
what
we've
done
so
far
and
then
our
our
proposed
research
activities
for
the
remainder
of
the
quarter
to
gather
additional
data
and
what
we
are
going
to
do
with
the
data.
A
We
do
not
stand
on
ceremony
so
if
you've
got
questions,
just
shout
them
out,
there's
also
a
link
in
the
agenda
to
the
agenda
in
the
meeting
invite
feel
free
to
write
them
in
there
too.
I've
got
that
up
as
well,
but
either
either
way.
Well,
let's
get
at
it.
So
thanks
again
for
coming.
This
is
the
official
unofficial
kickoff
meeting
for
the
ci
adoption
journey
project
that
andre
and
I
are
taking
on
so
a
little
bit
about
the
project.
A
This
has
come
from
the
question
of
what
is
ci
adoption
and
how
can
we
help
promote
it
because
it
is
seen
as
a
gateway
to
more
than
one
additional
feature
of
git
lab.
We
want
to
increase
the
usage
of
those
other
items,
we're
going
to
go
over
what
we've
done
so
far
and
all
those
things
so
so
I
found
this
graphic.
I
don't
know
who
made
it.
It's
super
super
cool
on
our
website
and
so
we're
gonna.
A
Try
we're
gonna
attempt
with
this
project
to
define
what
adoption
consists
of,
especially
as
it
relates
to
ci
we're
going
to
hopefully
uncover
some
additional
barriers
to
that
adoption
cycle.
The
adoption
process
and
understand
them
deeper,
and
so
the
whole
goal
is
so
that
we
can
increase
the
usage
and
conversion
to
our
other
features
that
sit
over
here
in
this
area
of
our
product.
A
B
A
Where
you're
right?
Okay,
guys,
I
am
awesome.
Thank
you
so
much
stop
me
before
I
I
heard
again
hurt
somebody
else,
thanks
all
right.
So
this
is
what
I
just
said:
love
the
graphics,
so
we're
going
to
really
focus
on
trying
to
get
people
converted
to
like
the
review
production,
the
cd
pieces
of
our
our
product,
as
well
as
testing
and
runners
too.
A
So
what
have
we
done
so
far?
We
had
some
stakeholder
interviews
with
most
everybody
on
this
phone
call
and
as
well
as
brian
wald,
we
talked
to
him.
He
had
done
some
prior
research
into
this
as
well,
so
we
wanted
to
give
his
perspective
and
the
major
takeaways
were
five
major
bullets.
So
the
definition
of
the
ci
adoption
journey
varied
everybody
had
a
different
perspective
of
what
that
actually
meant,
and
they
also
had
a
different
definition
of
what
success
looked
like.
A
A
A
That's
fine!
This
is
something
that
we
learned.
We
know
that
there
are
multiple
barriers
to
both
ci
adoption
and
use
and
cd
adoption
and
use.
So
there
has
been
some
research
done.
There
have
been
many
customer
conversations
around
this,
so
we're
not
going
in
blind,
which
is
great.
We
have
a
really
really
great
base
of
information
to
to
start
from.
So
the
next
couple
slides
are
going
to
be
all
of
our
research
activities
that
we
are
andre
and
I
are
proposing
for
this
project.
A
It
will
span
from
august
all
the
way
through
october,
because
it's
a
q3
project.
There
are
many
phases.
There
are
many
efforts
and
I
would
love
your
thoughts
and
feelings
on
all
of
them.
If
you
feel
like
we're
missing
something,
let
us
know,
we
want
to
make
sure
that
this
the
outcome
of
this
project
is
consumable
and
useful
for
everybody
on
the
phone
calling
everybody
at
the
company,
so
so
the
first
activity
that
we're
going
to
undertake
is
a
literature
review.
So
this
is
going
to
consist
of
looking
in
our
handbook.
A
A
We're
also
going
to
do
a
dive
into
forester
and
see
what
articles
they
have
around
ci
and
cd
usage
and
the
barriers
to
those
features
and
functions,
and
and
why
people
don't
adopt
them,
or
maybe
why
they're
accelerated
in
their
adoption
and
what
we
can
do
to
pull
that
information
into
our
product
and
our
documentation
as
well,
and
so
in
this
activity?
We're
hoping
to
answer
the
questions
on
the
right
hand,
side!
It's
our
goal.
A
We
won't
know
until
we
dive
into
it
if
we
can
actually
get
answers
to
all
of
those
those
questions,
but
we're
really
starting
this
this
piece
to
get
a
more
solidified
definition
of
what
adoption
means.
What
is
what
do
the
industries
say?
Adoption
is
defined
by
where
does
it
start?
Where
does
it
end?
Who
is
this
most
valuable
population,
which
is
the
user
for
ci?
We
we've
got
variable
definitions
of
that
when
we
talk
to
each
one
of
you
what's
their
goal,
is
it
to
automate?
Is
it
to
reduce
staff?
A
Is
it
to
increase
efficiency
and
trust
in
their
pipelines
and
their
data?
We're
going
to
find
out,
I'm
hoping
for
a
store
will
help
us
also
understand
the
features
that
are
most
in
demand
for
ci
now
and
in
the
future,
and
that
what
point
of
the
adoption
cycle
does
having
a
single
ci
tool,
make
it
the
valuable
reason
for
companies
to
ditch
their
other
tools
and
come
to
something
like
us.
So
those
are
our
goals
that
we're
hoping
to
be
able
to
get
answered
with
the
literature
review.
C
C
Around
the
struggles
for
adopting
devops,
the
devops
enterprise
summit
produces
a
bunch
of
content.
I
can't
remember
the
name
of
the
organization
that
gene
kim's
publishes
under
jason.
You
might
know
that
that
off
the
top
of
your
head,
but
there's
tons
of
content
around
the
struggle
for
large
organizations
to
adopt
devops
in
general
and
typically
the
starting
first
thing
of
that
is
ci
and
then
now
we're
kind
of
evolving
to
pain,
points
around
adopting
cd.
A
C
Yeah,
I
just
I
I
do
want
to.
I
think
what
you're
suggesting
in
that
research
is
that
you
want
to
understand
the
context
in
this
literature
review
and
I
think
forrester
might
give
you
more
of
the
kind
of
point-blank
market
analysis
of
required
features.
But
if
you're
looking
for
some
of
that
context,
it
might
be
better
to
think
of
it
in
terms
of
just
devops
adoption,
perfect.
E
There's
something
else,
maybe
not
so
much
for
ci,
but
sometimes
forester
has
some
strange
ideas
as
well
that
yeah.
So
maybe
we
should,
as
it's
all,
coming
together,
just
don't
kind
of
like
assume
that
they're
correct
and
then
align
us
to
whatever
they're
saying.
But
you
know
we
can
talk
about
how
it
all
ties
together.
Everything
which
I'm
sure
was
the
plan.
A
A
E
E
Exactly
yeah
and
they
do
have
good,
they
do
talk
to
tons
of
people
and
they
have
lots
of
good,
but
it's
all
through,
if
you
think
about
like
who
does
forrester
talk
to-
and
it's
generally
like
medium
to
large
enterprise,
customers
and
sometimes
they're
dealing
with
different
problems
with
adopting
devops.
Then
then
more
like
what
kenny
is
alluding
to
so
it's
interesting
information.
It
is
correct.
It's
got
its
own
bias
and
factors
that
play
into
it.
B
A
Good
point
all
right,
so
our
next
research
activity
is
looking
at
what
we
know.
So
we
started
that
with
the
stakeholder
interviews
and
there's
a
link
in
the
deck
to
the
dovetail
project,
where
we
put
all
your
notes
and
all
your
videos,
if
you
want
to
watch
yourself
and
as
well
as
all
of
our
insights,
are
in
there
too,
but
we
also
want
to
dive
into
any
of
the
other
information.
A
We
can
get
our
hands
on
any
customer
conversations
and
course,
or
anywhere
else
they
might
be
living
any
other
research
like
kenny
jason.
You
just
gave
us
more
to
go,
look
at,
which
is
great,
so
we
want
to
include
that
as
well
in
our
literature
review
of
what
we
already
know.
So
we
don't
try
to
learn
it
again.
If
that
makes
sense
like
we
want
to
focus
on
the
new
stuff,
with
this
project.
F
So,
as
I
already
mentioned,
one
of
the
outcomes
of
the
stakeholder
interviews
was
that
the
direction
is
not
like
super
clear
for
us.
At
the
moment
we
were
talking
about
enterprise
users,
but
also
smb
users.
We
were
talking
about
migrating
from
different
ci
tools,
but
also
starting
from
scratch
with
gitlab
and
to
make
sure
that
we
have
the
direction
set.
F
Except
for
that?
This
is
the
main
main
question,
but,
except
for
that,
I
would
also
like
to
add
two
like
more
open-ended
questions.
While
I
will
be
working
with
this
with
this
data,
I
will
probably
also
see
some
see
some
other
patterns
appearing,
so
I
also
recommend
that,
like
what
can
we,
we
learn
in
general
about
ci
and
runners
from
the
usage
data
of
our
product
and
also
what
we
can
learn
from
the
usage
data
of
our
documentation.
C
I
I
would
consider
json
to
be
your
kind
of
product
drive
for
any
product
direction,
input
into
that
in
the
sense
that
you
know
as
a
product
organization,
we
might
say
well
kind
of
our
most
important
strategic
type
of
customer
for
us
to
understand
their
adoption
journey
is
smb
smaller
teams
or
larger
enterprises.
So
please
make
sure
you
coordinate
with
jason
on
not
just
looking
at
the
data
to
target
how
which
to
determine
our
most
impactful
users,
but
also
the
product
direction.
Input.
F
Yeah
that
would
actually
make
our
lives
much
easier
because,
like,
as
I
mentioned
like
during
the
stakeholder
interviews,
we
heard
about
like
multiple
directions
that
we
might
we
might
take.
But
if
we
decided
right
away
in
the
beginning,
we
might
focus
on
different
kinds
of
activities.
That
would
probably
give
us
like
more
new,
like
more
of
the
novel
information
that
we
didn't
have
before.
C
Can
I
jump
in
andre
I'm
interested
in
your
exact
answer,
but
I
think
actually,
that
question
is
for
us
as
a
product
org
for
andre's
perspective.
He
wants
to
know
that
so
that
he
can
target
what
types
of
users
to
do
research
with
right.
So
I
think
we
need
to
help
him
define
who
he
should
be
looking
for
and
target
in-person
research,
and
we
do
that
by
saying
which
ones
would
be
most
impactful
to
the
business
for
us.
B
F
F
F
A
Yeah,
because
that
was
one
of
the
things
that
when
we
talked
to
each
one
of
you
and
brian,
we
got
varying
perspectives
of
who
this
is
and
tell
to
that
point
on
that
continuum
of
who's.
Is
it
a
decision
maker?
Is
it
a
user?
Is
it
somebody
who's
used
it
before
in
another
company
who
wants
to
use
it
now?
A
A
It
became
really
apparent
that
there
are
two
groups
that
we
we
might
need:
more
information
about,
non-web
app
software
development
developers,
teams
that
that
piece,
those
people
we
don't
from
what
we
understand
from
talking
to
everybody-
is
that
we
tend
to
focus
on
the
web
app
people
in
either
our
documentation,
our
marketing,
our
messaging,
whatever
it
is
so
andre
and
I
talked,
and
we
decided
that
that
is
definitely
a
persona
that
we
want
to
explore
more.
How
are
they
different?
What
if
they
are
different?
You
know
what's
going
on?
Are
they
different?
A
They
may
not
be,
but
let's
find
out
and
the
other
persona
that
we
want
to
dive
into.
Are
these
non-engineering
technical
use
users?
These
are
like
your
scientists
and
professors
and
things
that
people
who
are
not
software
developers
for
like
a
full-time
job,
part
of
devops
team,
whatever
but
they're
using
gitlab
for
other
uses,
could
be
us
the
design
team.
So
we
want
to
get
into
those
two
personas
and
understand
them
more
and
then
hopefully
get
a
more
robust
picture
of
do.
How
do
they
play
into
the
ci
adoption
journey?
A
B
A
Slide
we
work
together
too
much
time.
So
yes,
so
the
next
piece
of
this
is
out
of
that
persona
research.
Not
only
will
we
have
personas
that
we
can
use
and
we'll
put
up
on
in
our
handbook,
but
we
will
also
have
jobs
to
be
done
as
they
relate
to
ci
from
those
two
personas.
So
I
know
tao
dimitri.
I
think
dimitri
wants
to
start
doing
some
ci
jobs
to
be
done
as
well,
but
this
will
help
flow
into
that.
C
A
B
B
A
A
B
C
This
is
purely
a
like
kenny
hypothesis
that
I'm
not
sure
I
know
how
we
would
answer
in
this
process,
but
the
personas
that
you're
looking
at
they
seem
to
be
about
individual
adoption,
and
there
is
a
component,
especially
when
I
think
about
the
intent
of
this.
Research
is
geared
around
our
new
kind
of
go-to-market
motion
of
land
and
expand
that
we
will
land
and
we
might
have
one
team
or
a
central
team
that
offers
gitlab
ci
to
the
rest
of
their
organization,
but
they
they
need
help
rolling
it
out.
C
A
I
you
know
my
researcher
gut
has
just
told
me
that
that's
a
whole
new
project,
because
I
think
you're
going
to
have
different
definitions
of
end
and
beginning
you're,
going
to
have
different
definitions
of
what
is
adoption
at
an
organizational
level.
Just
like
you
just
said,
does
adoption
mean
one
team's
using
it
does
adoption
finish
when
the
whole
org
uses
it?
Does
it
finish
when
one
team
spreads
to
another
team
and
and
that's
the
end
of
it?
A
So
I
that's
just
my
instinct
tells
me
that
that's
like
a
whole
another
project
to
really
understand
it
at
an
organizational
level,
but
I
will
tell
you
I
will
ask
you
a
question
to
your
question:
is
that
more
valuable
than
us
doing
any
of
the
things
that
we've
listed
here
so
far
from
an
individual
standpoint?
Would
you
prefer
this
project
to
be
at
an
organizational
level
so.
B
C
Yeah,
that
might
that
might
be
a
good
way
to
phrase
it
I'm.
I
guess
and
lord
to
answer
your
direct
question.
I
don't
know
and
what
I
would
think
from
a
like.
There's
a
hypothesis
that,
like,
if
you
think
of
the
funnel
to
adoption
the
biggest
barrier,
is
just
individual
users
being
able
to
understand
and
get
to
a
green
ci
pipeline.
C
That
might
very
well
be
true
and
that's
the
place
where
our
r
d
investment
would
yield
the
best
results,
but
it
could
be
that
no
like
getting
to
a
pipeline
is,
is
pretty
straightforward.
People
can
do
that,
but
the
problem
is
sharing
a
kind
of
organizational
wide
set
of
best
practices
through
ci
is
the
difficult
thing,
and
what
I
guess
I'm
just
trying
to
suggest
is.
C
We
probably
need
to
invalidate
the
first
hypothesis
before
we
move
on
to
the
group
one,
so
it
makes
sense
to
start
with
the
research
you've
outlined.
But
so
maybe
your
response
is
telling
me.
We
should
just
look
to
see
if
the
general
thesis
that
we
have
a
like
there
is
an
adoption
journey
problems
in
the
individual
user.
Adoption
are
more,
are
going
to
pay
more
dividends
than
the
group
one.
We
can
look
out
for
that.
I
guess.
A
Yeah,
we
can
also
look
out
for
the
converse
too,
like
what
organizational
barriers
do
we
find
in
the
individuals,
desperate
search
for
ci
adoption
for
themselves
like
what
what
do
they
run
into?
What
are
they
seeing
that
has
overcome
those
organizational
barriers,
and
we
can
use
that
as
a
springboard
for
the
next
round
of
research
to
dive
deeper
into
that
organizational
structure?
And
what
is
it
there?
A
Because
when
we
talk
to
brian
it,
he
had
a
very
strong
sense
that,
from
what
he's
done,
it's
more
of
an
organizational
barrier
than
anything
and
I've
dipped
my
little
toes
into
talking
to
people
about
this
in
in
the
context
of
other
projects,
and
I
found
a
mix-
I
found
a
mix
of-
I
don't
know
what
I'm
doing,
but
I
want
to
and
I'd
like
to,
but
they
won't.
Let
me
they
won't
pay
for
it
whatever
they
just
won't.
Let
me
so,
I
don't
think
it's
bad
to
start
with
one
or
the
other.
A
A
E
Gila
had
that
was
around
like
within
the
first
12
weeks,
either
ci
adoption
increases
or
falls
off
for
a
new
project,
and
that's
a
trend
that
they've
seen
and
they've
got
clear
data
supporting
that.
That
might
be
another
way
to
just
focus
the
research
around
something
and
ask
what
happens
in
that
first
12
weeks
that
people
churn
or
don't
cause.
I
don't
think
we
actually
know
right
now.
We
just
know
that
if
they
stay,
then
they
grow
and
they
adopt
more
stages.
C
Yeah,
that's
a
great
way
of
targeting,
I
think,
at
the
end
of
the
day
it
that
is
jason's
call,
but
it
makes
sense
to
me
to
start
with
something
focused
like
that
time
period
and
the
user's
adoption
journey
and
if
it
bubbles
out
that
actually
the
user's
concerns
or
problems
in
that
adoption
are
geared
towards
the
organization's
adoption.
Then
we
kind
of
we
can
pivot
in
that
direction.
G
C
B
It's
a
it's
like
it's.
A
gradual,
like
reduction
in
in
ci,
builds
nci
pipelines
triggered
in
merged
requests
submitted,
which
makes
sense
if
you're
transitioning,
to
a
different
third-party
tool
than
than
ours.
It
takes
time
to
move
all
your
pipelines
over
and
so,
as
you
move
them,
you're
treating
those
pipelines
less
and
less.
B
B
One
of
the
things
we
want
to
explore
on
the
barriers
are
the
users
that
are
prospects
that
are
not
users
yet
whose
organization
won't
even
buy
them
the
tool
to
to
use
that's
a
different
aspect
of
the
organizational
barrier
to
adoption,
and
that
that
question
is
already
assumed.
If
you
looked
at
that
data
that
their
organization
sorry
about
them
the
tool,
so
I
don't
know
how
you
want
to
explore
them
separately.
B
I
thought
the
organizational
adoption
barrier
was
something
that
would
come
out
as
an
insight
of
looking
at
it'd
be
one
of
the
factors
that
would
be
a
barrier
when
you
research
out
of
your
research.
Finding
I
didn't
and
then
maybe
it
justifies
a
deep
dive
later.
But
if
we
started
with
that,
you'd
already
made
an
assumption
right.
D
C
A
D
I'll
just
mention
because
it
seems
I
mean-
maybe
it's
relevant,
I'm
not
sure,
but
it's
like
I'm
having
flashbacks
to
the
conversation
I
had
yesterday
with
david
director
of
product
before
secure,
where
we
were
discussing
a
foundational
study
for
secure
and
we
were
talking
about
the
adoption
of
secure
features
by
developers
and
what
it
seems
to
this
is
just
early
thoughts.
But
it
seems
like
the
direction
we're
going
to
head
is
talking
about
adoption
on
an.
D
Level
in
the
sense
that
we
are
going
to
probably
be
talking
to
engineering
leads
and
just
trying
to
understand
their
attitudes
around
security
and
what
metrics
they
would
like
to
be
reported
on
in
relation
to
security,
if,
if
at
all
from
their
developers,
so
I
don't
know
that
whole
discussion
around
organizational
level.
What
versus
individual
level
seems
to
be
happening
here
as
well
and
I'll
just
mention
that
it
would
be
great,
lori
and
andre
if
we
were
to
just
I
don't
know,
I'd
be
happy
to
share
a
script
and
adopt
it
adopted.
A
A
This
is
solely
to
understand
the
impact
of
the
proposed
ci
changes
that
is
in
the
meta,
epic,
that
jason
put
together
to
to
understand
like
if,
if
we
were
to
do
these
things,
how
would
they
impact
people's
perception
or
usage
of
ci?
So
we
put
this
piece
at
the
end
of
our.
We
have
a
nice
little
gantt
chart
here,
go
go
keenan
and
his
team.
A
We
put
that
at
the
end,
because
we
wanted
to
understand
our
people.
First,
our
landscapes.
First,
our
challenges
first
and
then
we'll
know
better
who
to
roll
this
quantitative
survey
out
to
to
get
some
some
data
around
expectations
and
impacts
of
these
features
and
they're
all
outlined
there
in
that
meta,
epic,
that
jason
and
tao
have
been
working
on,
which
is
perfect,
so
so
yeah.
So
here
is
our
swag
at
our
timelines.
A
These
are
children
epics
with
multiple
research
issues,
inside
of
them
that
cover
all
of
those
slides
that
we
just
went
through,
but
just
let
you
have
a
sense
of
what's
going
to
happen,
and
this
last
one
at
the
top
here
is
the
quantitative
survey
just
cut
it
off
when
we
did
the
picture.
So
one
of
the
things
we
wanted
to
chat
with
y'all
about
today
was
expectations
and
how
we
can
meet
them
for
sharing
data
as
we
go
well.
E
A
Oh
yeah,
I
know
so
like
I
when
say
the
literature
review.
We
are
aiming
to
finish
that
up
by
mid-september,
you
guys
will
learn
what
we
learned
we'll
we'll
have
a
con.
We
can
either
have
a
meeting
like
this.
We
can
have
an
asynchronous
shot
in
a
document
or
an
issue,
so
these
are
our
little.
I
want
to
call
them
milestones
because
that's
what
we
call
our
sprints,
but
it's
our
little
checkoff
points
whenever
we
finish
an
effort,
so
they're
not
going
all
the
way
to
the
end
of
october.
A
E
A
No
yeah
because
it's
it's
all
to
inform
the
rest
of
the
research
right.
So
it's
like
here's.
What
we've
learned
so
far!
This
is,
if
we're
going
to
pivot.
This
is
how
we're
going
to
pivot.
If
not,
this
is
still
what
we're
going
to
do
and
now
we're
going
to
do
this
next
piece.
So
it's
like
a
continuous
cycle
of
of
information.
C
Cool
you
asked
about
kind
of
output
formats
and
making
sure
that
you're
informing
correct
stakeholders.
There
is
a
use
case
for
gitlab
ci.
That
is
a
high
priority
for
the
entire
customer's
success
team.
So
david
sakamoto's
entire
organization
is
aware,
and
building
kind
of,
like
adoption
flows
for
how
they're
going
to
market
with
customers
exist,
customers
or
new
customers
talking
about
how
to
adopt
gitlab
ci,
so
to
the
extent
that
we
can
update
some
artifacts
on
a
rolling
basis.
C
I
think
this
might
also
help
to
jason's
point
like
you
know,
as
we
do
some
persona
research
we're
updating
those
artifacts
with
what
we've
learned
to
date,
and
then
we
continue
to
evolve
that
the
better,
because
there
is
a
real
hunger
for
this
type
of
research,
not
just
with
to
make
product
decisions
but
to
make
on
the
ground.
How
are
we
suggesting
customers
adopt
ci
decisions.
A
C
C
Is
I
don't
know
where
to
put
it
I'll
put
it
down
here
in
the
questions
that
is
kind
of
like
their
playbook
for
go
to
marketing
going
to
market?
And
if
we
update
that
that
playbook
links
to
the
personas?
But
if
we
update
kind
of
that
playbook
and
the
personas
as
we
go,
that
will
help
inform
his
team
jason's
the
point
person
the
product
point
person
for
that
use
case.
But
there
are
product
marketing
and
other
folks
involved
too
jason.
E
Think
that's
great
the
other
place
that
will
update
and
it
will
just
depend
so
the
I
think
the
go
to
market
strategy
output
should
definitely
go
into
there
and
that's
the
place
that
we're
all
working
from
anyway.
So
it's
like
the
ideal
perfect
place
for
it,
and
not
only
that
but
it'll
bring
in
more
people
through
the
merge
requests
as
we're
making
those
changes.
E
But
then
the
other
place
that
we
kind
of
will
do
the
exact
same
process
is
that
this
will
have
outputs
to
the
direction
pages
as
well
for
each
of
the
categories
and
then
for
the
the
stage
and
probably
even
to
a
certain
extent
to
the
section.
So
I
would
say
you
know
our
main
outputs
at
each
of
these
stages
are
merge,
requests
to
those
two
sources
of
truth,
and
if
we
do
that,
then
it's
in
the
right
place
and
it
will
flow
into
planning
and
execution
appropriately.
C
C
A
G
G
A
A
So
these
are
our
two
big
buckets
that
we
want
to
start
with
and
then
we'll
probably
refine
down
from
there.
What
that
actually
looks
like
so
we
can
start
to
recruit
them
and
talk
with
them.
So
if
anybody
knows
anybody
who
meets
he's
either
like
a
not
like
a
scientist
or
a
non-web
app
software
developer,
that
you
feel
would
have
some
good
information
that
they
can
talk
with
us
about
their
job.
I'm
open
happy
to
talk
to
anybody.
G
Got
it
yeah?
I
guess
that
makes
sense,
I
mean.
Maybe
this
is
way
off
base.
I
was
just
kind
of
thinking
in
relation
to
healer's
data
that
jason
and
ken
just
pointed
out.
Is
it
any,
and
maybe
this
is
it's
true
now?
Is
there
any
value
in
trying
to
to
chat
with
those
companies
that
churned
before
those
organizations
have
churned.
A
A
Data,
it's
just
okay,
yeah!
We
can
try
in
my
in
my
experience
at
other
companies,
people
you
have
a
very
low
rate
of
people,
saying
sure
I'll
talk
to
you
after
they've
churned
they've
turned
they
moved
on,
but
doesn't
mean
that
we
can't
try
and
talk
to
them.
I
think
it
would
be
very
interesting
from
if
nothing
else,
but
an
organizational
perspective.
A
What
happened
at
a
at
a
high
level
of
that?
Why
did
they
drop
us?
Why
they
leave?
We
know
the
timeline,
but
what
were
the
factors
that
went
into
that?
So
that's
definitely
something
we
can
look
into
and
if
we
run
out
of
time
in
this
particular
effort,
we
can
definitely
put
that
in
our
next
effort,
where
I
suspect
we
will
be
doing
and
looking
at
it
from
a
more
of
an
organizational
standpoint.
B
A
B
A
I
am
too,
I
really
am
I'm
looking
forward
to
it
cool.
Well,
you
guys
all
know
where
to
find
me
and
andre
any
anytime.
You
need
anything,
let
us
know,
and
we
will
keep
you
updated
through
the
issues
as
well
on
our
progress
so
just
like,
we
normally
do
and
yeah
looking
forward
to
it
all
right
thanks.
Everybody.