►
From YouTube: Persona meeting
Description
Discuss buyer and user persona's management and usage at GitLab
A
A
We
always
talk
about
personas
who's,
a
buyer
persona
who
we
try
to
talk
to
what
are
their
problems,
understanding
the
personas
we
sell
to,
and
it
was
a
product
management
meeting,
I
think
Demetri
about
a
month
ago
you
were
talking
about
the
work
in
the
UX
handbook
and
the
get
lab
design.
You
know
that
we
were
doing
and
you
guys
were
doing
around
in
defining
personas
and
trying
to
work
on,
defining
that
you
have
to
do
for
users
as
well,
and
it
happened
that
in
parallel,
I
had
resurrected.
A
Some
work
I
had
done
at
HP
software
and
Micro
Focus,
where,
because
we
were
selling
to
these
unique
groups
of
people,
whether
it's
testing
and
QA,
or
it
was
ops
or
security.
One
of
the
observations
I
made
was
that
in
in
an
IT
organization,
there's
these
there's
and
because
I
used
to
live
it
I,
the
aha
or
the
conclusion
I
reach
was
there
are,
and
it's
funny
some
other
guys.
A
I
talked
to
recently
called
them
feudal
kingdoms,
but
there's
these
groups
that
exist
that
don't
have
that
there
they
might
be
defined
by
the
org
chart,
but
they're
more
defined
by
their
culture
by
who
they
talk
to
who
they
listen
to
it's
persona
like,
but
but
they
have
their
own
culture
Security's.
You
know
we
don't
want
to
have
risk.
We
want
no
vulnerabilities,
there
they're
all
focused
on
reducing
risk,
whereas
you
know
that
the
people
in
the
PMO
are
focused
on
schedule
and
budget
on
time
and
hit
me
and
their
cadence.
A
They
go
to
different
conferences,
they
speak
different
languages
and
when
I'd
go
to
happy
hour
after
work,
they
would
sit
at
different
tables
because
they
were
different
and
they
saw
each
other
differently.
And
so
so
you
know
thinking
about
how
IT,
how
our
customers,
the
people
that
work
in
the
IT
shops
that
we
sell
to
you
know
what.
How
do
we
think
about
those
cultures?
How
do
we
start
interacting,
so
we
started
to
use
that
as
a
way
to
to
define
a
kind
of
a
top-down
layer
of
saying
what
are
the
hidden
IT
groups.
A
What
are
these
groups
that
are
they're?
Not
there's,
not
a
precise
definition
that
says
oh
I'm
this,
but
when
you
talk
to
them
and
you
listen
to
them
talk,
it
becomes
really
really
obvious
of
what
culture.
What
group
are
they
really
part
of?
And
so
that's
what
one
of
the
things
we
started
doing
we've
done
persona
work
in
the
past
before
I
joined,
we
actually
hired
a
consultant
we'd
had
somebody
outside
you,
some
outsource
work
on
a
couple
of
different
personas,
and
so
that
was
where
I
said
to
Dmitry.
A
B
A
B
Getting
wide
adoption
within
gitlab,
you
know
the
the
personas
are
finally
being
defined,
and
you
know
we
should
work
together
as
much
as
we
can
to
be
able
to
push
that
effort
throughout
the
organization
that
is
kind
of
what
god
has
kick-started
as
well
aside
from
the
whole
of
the
hugest,
which
was
on
point
and
gives
less
piece
of
context
this.
So
this
meeting
was
already
there
before
you
joined
Christi
and
I
thought
was
also
nice
to
include
you
into
this.
You
know
to
get
you
kick
started
on
the
personas
persona
effort
as
well.
B
C
I
have
not
had
time
but
I'm
sure
you
guys
when
I
say
AHA,
he
said,
then
we
have
three
different
sets
of
personas
right
now,
so
we
have
one
through
marketing
one
through
UX
and
one
through
I
can't
remember
the
third
that
he
said
and
the
the
ask
from
him
was
for
us
to
rationalize
those
and
put
them
in
one
place.
So
that
can
be
a
part
of
this
effort.
I
think.
A
I
think
we
need
to
do
that.
I
mean
we
continue
to
research.
Who
I
mean
we
look
at
from
a
buyer
perspective.
We
try
to
understand
the
person's
gonna,
write
the
check
and
what
problems
they're
having
that's
gonna
drive
them
to
write
a
check,
it's
kind
of
related,
but
it's
you
know
the
when
you
look
at
it
from
a
different
perspective
of
what's
a
users
problem,
what
are
they
trying
to
do
and
sometimes
buyers
might
be
users?
A
Today
we
don't
have
an
exact
when
we
think
about
executives
using
gitlab
or
leaders,
use
didn't
get
lab,
I,
don't
think.
We've
really
ever
thought
about
that.
I
mean
yeah
as
a
when
I
before
I
joined,
I
started
to
use,
get
lab
to
do.
Project
management,
I
had
no
interest
at
all
and
having
a
repository,
I
didn't
want
to
know,
get
I
didn't
need
to
know
yet.
I
was
running
a
team
and
my
team
needed
a
place
to
manage
issues
and
to
do
planning,
that's
all
and
so
from
a
user
experience.
A
This
was
over
a
year
ago,
and
it's
still
I
think
arguably
true
today,
that
when
you
get
get
lab,
but
you
kind
of
get
it
all
and
here
figure
out
what
you're
gonna
do
with
it.
It's
like
a
lump
of
clay
and
as
a
user
as
an
executive,
that's
not
gonna
that
they
want
green
lights
and
green
bars
and
dashboards
and
really
high
level
views
of
the
world
which
we're
not
there.
Yet
right.
A
We
haven't
thought
about
that
as
a
whole
set
of
personas
to
solve,
for
which
to
be
honest,
when
I
listened
to
the
sales
team,
the
QPR's
last
week,
you
know
one
of
the
threads
that
I
heard
and
the
various
discussions
was
we
got
it
beat
JIRA
Goldman
Sachs
has
told
us
figure
out
how
to
go
displace
JIRA
and
one
of
the
things
with
displacing
feature.
Is
it's
going
to
be
executive,
dashboards
and
visibility?
That's
we
don't
have
today
that
we're
gonna
have
to
solve,
for
but
yeah
so
I
think
Eric's
request
is
spot-on.
A
We
need
to
figure
this
out
and
get
a
line,
because
there's
no
reason
to
do
so.
Do
duplicate
of
work
right
as
we
start
to
define
these
groups
these
areas,
you
know
I've
got
a
point
of
view
and
a
perspective
from
having
lived
them
lived
in
some
of
them
and
having
had
to
work
with
them.
So
at
some
level,
I'm
fluent
in
some
of
their
languages,
it's
funny
speaking
of
languages,
I
was
filling
out
a
form
over
the
weekend.
C
A
Things
of
bandwidth,
its
its
bandwidth,
its
priority,
I
mean
given
the
bandwidth
we
have
and
the
things
that
we're
doing.
It's
just
a
question
of.
When
do
we
do
it
in
order,
and
so
there's
it.
Last
year
there
was
the
end
product
marketing
or
some
work
to
do
to
define
some
Enosh.
Some
a
handful
of
a
couple
of
key
personas
and
I
can
send
you
the
link
to
those
in
the
design.
You
know
the
work
that
Dimitri
and
the
team
has
done
around
design,
there's
been
work
to
define
a
set
of
personas
and
I.
C
C
A
C
A
A
How
do
we
make
get
lab
useful
for
a
VP
of
Bath's,
not
CID,
not
a
not
a
get
lab
BP,
but
a
real
VP
of
apps,
who
is
who
frankly,
doesn't
care
too
much
about
the
tool
that
cares
about
knowing
what
how
their
team
is
meeting
the
business
need
and
how
big
they
want.
The
big
picture
to
be
able
to
have
a
snapshot
in
view
of
the
big
picture,
you
know,
how
do
we
take?
A
How
do
we
solve
for
that
or
how
do
we
solve
for
the
project
slap
for
the
project
manager,
we'll
just
let's
say,
project
manager
for
now
versus
product
manager
to
different
personas
that
exist
that
will
exist
in
the
world
for
a
long
time
to
come.
You
know
how
do
we
solve
for
that
product
managers
are
going
to
go
to
more
technical
project
managers,
a
little
less
technical,
more
focused
on
flow
I.
Don't
know
it's
it's
a
very,
very
it's
a
very
real
challenge
that
we
have
to
figure
out.
A
A
B
It's
it's
about
specialization
right,
I
mean
in
future.
Looking
at
product
management,
for
example,
it
could,
you
know
there
could
be
credit
owners
and
product
managers,
so
there
would
be
an
additional
one
that
you
know
we
need
to
think
of
and
I
I'd
say
this.
The
same
would
go
for
any
other
role
inside
of
the
company.
You
know
so
one.
Maybe
two
were
you
for
free
in
terms
yeah,
how
we
decide
to
specialize,
but.
A
B
At
the
same
time,
John
I
don't
want
em
too
much
interrupt
you,
but
I'd
like
for
us
to
have
at
least
one
or
two
action
points
coming
out
of
this
meeting.
You
know
getting
us
such
further
I
think
there's
a
lot
of
opportunity
for
us
to
and
they'll
discover
and
argue
about
a
lot
of
the
things
that
are
involved
with
this,
but
you
know
that
is
best
done.
B
Asynchronously
instead
of
synchronously
and
I
had
as
a
idea
of
like
how
you
know
so
one
of
the
action
items
comes
from
Christie
I'd
say
you
know:
how
can
we
unify
all
the
personas
across
the
organization
and
the
second
one
would
be?
How
can
we
make
them
use
I
mean
if
that
was
the
point
that
I
was
most
concerned
with.
You
know
we
got
this
first
on
the
information
done
by
by
Sarah
and
Katherine,
Emily,
etc.
D
So
so
the
original
personas
and
one
of
the
first
things
I
worked
on
when
I
joined,
get
lab.
Where
we've
been
here
two
three
months
and
at
the
time
there
was
no
like
product
marketing
team
as
well.
So
the
way
that
personas
were
worded
for
really
for
you,
axon
marketer
and
then
they
kinda
came
outdated.
No
one
was
really
using
them.
D
They
were
very
worried
if
they
weren't
your
typical
personas
I,
just
found
out
a
lot
about
users
and
I
wanted
to
share
it,
and
then
we
had
the
initiative
last
August,
which
was
an
OK
R
for
the
UX
research
team
to
do
new
personas,
and
these
were
led
by
Katherine,
Emily
and
under,
and
we
found
that
there
was.
We
had
meetings
with
all
product,
marketing
and
product
team
and
all
the
designers
to
see
what
they
wanted
to
get
out
of
the
new
personas,
and
there
was
two
very
like
distinct
groups.
D
We
found
that
on
the
secure
and
the
outside,
we
wanted
personas
at
a
high
level,
so
we
didn't
really
who
would
be
using.
The
up
speeches
might
insist
happening.
Some
people
like
that,
where
were
the
responsibilities
of
a
DevOps
engineer
and
then
on
the
other
side
on
the
development
side,
they
felt
they
knew
they.
You
there's
a
lot
better.
They
didn't
really
want.
Personas
I
only
wanted
them
when
they
were
designing
a
feature
and
I
wanted
them
created
on
a
per
future
basis,
rather
than
as
broad
as
as
developed
it.
D
We're
now
in
a
place
where
to
meet
you
very
kindly
added
and
personas,
and
the
issue
templates
of
product
managers
could
think
about
using
them
more.
However,
we
have
had
a
bit
of
a
mixed
reaction
to
this
myself
of
me
and
Katherine.
In
terms
of
we
had
someone
an
engineer,
the
other
week
open
an
issue
in
the
UX
research
project.
D
To
say,
can
you
create
personas
for
this
person
and
when
we
dug
into
why
that
person
might
be
personas,
because
they
could
open
an
issue
and
they
didn't
think
that
any
of
our
existing
personas
matched,
who
they
reminds
designed
for
and
I
think
this
is
an
issue
that,
as
we
were
just
touching
upon
earlier,
that
we're
going
to
run
into
a
lot.
You
know
we
we
thought
gate
like,
which
is
everyone
can
contribute
how
many
personas
de
create.
Where
do
you
draw
the
line
and
something
that
I've
been
thinking
about
and
is
like?
D
We
know
that
the
reporting
isn't
working
and
within
the
UX
research
team
and
we're
thinking
about
moving
to
an
insight
repository,
and
what
that
would
mean
is
that
we
would
tag
the
insight
repository
with
the
different
people
that
were
speaking
sue
so
that
when
a
designer
comes
to
work
on
something,
can
they
think
well?
I
want
to
know
more
about
this
and
person.
D
Repository
and
I'd
also
have
you
that
to
some
extent,
some
of
the
product
managers
that
I've
spoken
with,
because
I'm
going
through
and
big
thing
of
speaking
through
all
the
product
managers
at
the
moment
have
said
that
they
don't
finally
piss
on
this
useful
because
they
feel
that
they
talked
to
customers
every
single
week.
So
therefore,
they
feel
they
already
have
a
good
understanding
of
the
people
new.
You
know,
they're
creating
and
features
for
I
think
it's
different.
D
That's
kind
of
everything
from
the
UX
side,
so
I,
don't
know,
I
think
I
definitely
think
we
can't
go
on
just
creating
personas
really
nearly
every
time.
Someone
opens
an
issue
and
we
have
to
draw
the
line
somewhere.
At
the
same
time,
I
want
to
be
in
a
position
where
we
can
support
designers
as
they're
building
something
to
get
them.
An
idea
of
the
person
that
they're
designing
for.
C
Iii
love
your
idea
of
using
the
research
repository
to
help
push
usage
of
personas,
at
least
amongst
the
US
team.
Our
UX
team
I
think
that's
that's
a
really
smart
idea.
I
was
kind
of
taking
notes,
as
you
were
talking
and
one
of
the
things
that
came
out
and
it
seems
like
we
need
persona
guidelines
right
to
where
we
actually
like
say
this
is
this
is
what
a
persona
means
to
us.
This
is
when
we
will
create
a
persona.
This
is
the
level
at
which
the
persona
will
be.
C
D
C
C
How
do
you
feel
about
going
like
having
a
plan
that
basically
for
the
next
researcher
we
hire
their
first
project,
would
be
to
drive
forward
on
at
least
the
UX
personas,
and
not
necessarily
the
marketing
personas
that's
up
for
for
debate,
but
it
felt
like.
Maybe
it
could
be
also
a
good
introduction
to
a
researcher
to
our
company
thoughts,
I.
D
Think
I
think
it
depends
on
and
to
what
extent
you
mean
so
the
personas
that
we've
got
in
the
design
system
are
up
to
date
at
the
moment,
because
we
are
updating
them
from
every
time.
We
find
out
insights
that
are
relevant
to
those
people
and
so
I
think,
like
the
UX,
personas
and
I
kind
of
formed,
it
is
how
I
would
see
it,
but
I
am
wondering
whether
those
sharat's
personÃs
should
now
really
become
the
ownership
of
marketed.
So
like
we've
got
them
in
the
design
system.
D
I
know
that
marketing
have
got
their
own
personas
and
maybe
there's
somewhere.
We
can
collaborate
and
pull
them
together
and
then
they
and
maintained
by
marketing
and
I
think
the
UX
personas,
like
I,
said
they
should
be
created
more
from
the
insight
repository,
so
we'd
be
pulling
together
the
insights
to
create
a
persona
and
the
way
might
do
this,
for
example,
is
through
every
insight
will
be
in
an
issue
and
then
we
might
use
an
epoch
to
say
designer
and
they'll,
be
every
instant
that
we've
got
about.
A
designer
will
be
linked
to
my
epoch.
D
C
A
Tell
if
I
was
on
you
yeah
my
objective:
isn't
it's
not
about
ownership,
I
I
think
it's
it's
a
collaboration
that
we
have
to
have.
We
have
I
think
different
needs,
but
at
the
end
of
the
day,
having
insight
about
the
audience
that
we're
trying
to
reach
and
we're
trying
to
connect
with
whether
it's
used
to
their
buyers-
or
you
know
we're
doing
a
messaging
and
content
on
web
pages
or,
however,
it
is
we're
reaching
out
to
people.
You
know
the
just
commit
campaign
that
we're
launching.
A
We
took
it
a
look
at
this
and
they
said,
look
we're
not
going
to
message
to
everyone.
We're
gonna
go
after
the
VP
of
apps,
because
the
director
or
VP
of
applications
is
the
person
who
is
most
likely
to
buy
get
lap
period
full
stop.
The
CSO
is
not
going
to
buy
gitlab
they're
not
going
to
buy,
get
lab
and
tell
everyone
else.
The
organization's
start
using
get
lab
to
do
development
because
I,
like
their
security
features,
the
VP
of
Operations,
probably
is
less
likely.
A
I
mean
there
might
be
there's
situations
where
they
will,
but
we
think
we
can
sell
mostly
there.
So
that's
why
we
went.
We
targeted
that
so
I
think
it's
a
question:
how
do
we
collaborate?
How
do
we
do?
How
do
we
get
together
on
this
and
our
understanding
of
our
customers
and
the
people
that
are
buying
and
using
it
lab,
but
we
just
have
to
do
it
together
and
for
me
at
least
it's
not
ownership.
It's
together
and
I'm
updating
a
link
to
the
hidden,
IT
oops
work
that
I
did
before.
C
D
Definitely
I
think
that's
throw
and
ship
I
think
what
I'm
more
thinking
is.
Is
that
there's
always
been
a
big
debate
about
where
this
owners
should
live,
whether
they
should
be
in
a
design
system
or
the
handbook
and
I
think
perhaps
they
if
they
go
with
more
of
a
market
since
language
belong
in
the
handbook
rather
than
the
design
system
and
I
think
we
do
just
need
to
make
it
clear
whether
we
want
to
come
at
it
from
the
angle
of
users
or
buyers
and
I
think
as
well.
D
C
C
A
Think
the
other
opportunity
here
is
that
product
market
not
market
in
general,
but
product
marketing
specifically,
and
if
you
look
at
the
the
the
kinds
of
people
were
hiring
and
the
talent
we're
bringing
in
and
I
know
in
my
case,
I
am
that
persona
I've
been
that
persona
Cindy,
you
know
knows
the
security
side.
You
know
Cindy
Blake,
you
know
William,
you
know
he's
been
know,
he's
been
learning
these
and
driving
the
ops
side
of
the
house,
and
you
know
so:
we've
been
bringing
in
people
who
got
the
experience
on
that
side
of
it.
A
A
D
A
The
the
what
I
called
you
know,
what
I
call
the
IT
groups
hidden
IT
groups
is.
Is
this
overarching
uber
look
at
these
cult,
these
hidden
cultures
that
exist
within
an
IT
organization?
It's
it's
from
which
I
could
say
the
personas
probably
lived
within
one
of
those
groups.
They
typically
will
align
to
one
of
them,
and
so
it's
a
for
me
at
least
a
starting
point,
rather
than
get
me
into
I
want
to
talk
about
this
one
persona.
A
At
this
point,
it's
a
stereotype
of
let's
talk
about
the
people
that
kind
of
shared
these
things
in
common
and
it's
it's
in
the
handbook.
We
used
it
those
a
way
to
model
how
we
think
about
growing
product
marketing.
To
talk
to
these
different
groups
that
we
have
to
engage
with
and
the
term
hidden
is
because
they're
not
precisely
defined
it's.
There
is
no
clear
definition,
which
is
your
this
or
that,
but
boy
I'll
tell
you
this
much.
A
When
I
talk
to
people,
they
it's
often
very
easy
to
figure
out
which
group
are
they
part
of
the?
The
anecdotal
example
I
had
was
a
solution
architect
who
had
can't
come
to
get
lab
from
having
worked
at
version
one
and
he's
talking
about
project
planning
and
how
it's
you
just
didn't
get
into
it,
couldn't
get
into
selling
it
because
he
said
I'm.
Actually,
a
developer
I
want
a
code.
I
want
to
help
people
code,
I
wasn't
it.
A
You
know
the
planning
stuff
didn't
make
any
sense
to
me,
and
he
basically
said
I'm
this,
not
that
and
he
chose
get
lab
because
it
was
it
aligned
to
the
group
that
he
thought
made
the
most
sense
to
him.
It
was
just
it
was
fascinating,
listen
to
himself
identify,
he
didn't
know
what
he
was
doing,
but
that's
one
did
and
and
I
find
that
a
lot
when
I
talked
to
customs
I
talked
to
people
they
aligned
along
some
boundaries
like
this
by
the
way.
A
A
Think,
as
as
we
work
together
to
define,
you
know
where
we
think
what
goes
into
and
how
we're
going
to
use
personas
where
we
have
gaps
as
we
start
to
research
and
dig
into
the
personas
I
think
it's
an
opportunity
where
we
have.
We
have,
you
know
shared
interests
on
it.
So
it's
for
me,
I,
think
that
the
the
design
system
and
the
personas
defined
in
the
design
system
should
be
as
important
to
me
as
they
are
to
you
in
marketing.
I.
A
It's
not
it's
not,
as
if
I
you
know,
I,
don't
know,
that's
the
way.
I
see
it
tactically.
What's
that
look
like
I
think
it
means
we're
talking
to
each
other
we're
planning
together
as
we're
working
on
things
we
identify.
How
do
we
work
on
together?
So
if
we're,
if
you're
working
on
a
deaf
person
or
a
product
manager,
persona
or
a
executive
persona,
look
like
to
help,
you
know
it's
one
of
those
things
that
were
not
working
in
silos.
A
C
D
C
A
very
simple
person,
so
I'm
gonna
sue
spec
to
you
as
simply
as
I
possibly
can
see.
You
can
confirm
or
deny
so
it
sounds
like
we
all
agree
that
they
all
need
to
be
in
one
place.
No
one
seems
to
have
super
strong
feelings
about
whether
it's
in
the
design
system,
site
or
in
the
handbook,
I'll
say:
I,
don't
have
strong
feelings
as
long
as
it's
in
one
place,
so
I
would
rely
on
the
team
to
make
that
decision
and
just
say
hey.
C
This
is
where
it's
going
to
be
and
we
go
okay,
that's
where
it's
gonna
be.
It
seems
like
we
need
to
take
a
look
at
the
existing
personas
and
make
to
two
decisions.
One
decision
is:
are
they
are
the
not
the
content
of
the
personas
but
the
personas
themselves?
Are
they
complete,
as
is
or
are
we
missing?
Some
personas
I
think
the
the
assertion
in
this
meeting
has
been
missing
some,
so
we
need
to
work
together
to
figure
out
which
ones
are
missing
great
and
then
maybe
Sarah
and
I
you
can.
C
Maybe
we
can
talk
about
this
in
our
one-on-one.
We
need
to
figure
out
how
closely
we
think
the
UX
personas
can
align
with
marketing
personas,
based
on
what
you've
got
in
your
head
around
via
the
the
research
you're,
not
calling
it
a
repository
I'm.
So
sorry,
what
are
you
calling
it
insights
repository
there
we
go.
So
that
seems
like
those
are.
Are,
though,
those
are
kind
of
our
action
items
coming
out
is:
let's
decide
where
it's
gonna
live.
C
D
Was
going
to
say,
I
think
it's
probably
something
myself,
Katherine
and
Emily
could
all
work
on
together
with
the
original
people
who
put
the
personas
together.
I
think
it'd
be
something
that
we
could
do
a
sync
and
we
just
chip
at
them,
one
by
one
and
because
we've
all
had
different
parts
and
creating
those
personas
as
well:
Mike,
Katherine's,
obviously
creating
ones
on
the
dev
side
and
Emily's
on
the
outside.
So
they're
the
specialists
in
the
area.
So
I
would
like
that's
Caitlyn
to
health
as
well.
Yeah.
C
C
D
C
C
A
A
And
I
think
we're
already.
Mostly
there
I
mean
in
the
design
system.
We
have
references
to
the
buyer
personas
which
exist
in
the
form
of
videos
and
slide
decks.
So
at
some
level
I
think
it's
there
we're
referencing
where
they
exist.
We
references
the
the
pricing
page,
the
tiers,
the
pricing
page
I,
don't
think
matters
from
a
buyer
persona
perspective,
I,
Cristina
I
would
argue
that
the
first
step
of
consolidating
is
largely
done.
A
The
only
thing
I
would
change
in
the
persona
and
stuff
in
the
design
would
be
I
there
referencing
the
the
the
hidden
IT
groups
as
an
element
of
it,
which
is
really
collections
of
personas.
Where
they're
gonna
exist
within
those
groups,
I
mean
you
guys
need
to
look
at
that
and
see
whether
or
not
that
makes
sense,
but
that's
that
framework
that
overarching
kind
of
structure
has
been
at
least
without
getting
into
you
know:
one
persona,
two
persona,
three
persona.
A
C
A
I
mean
yeah
because
it
is
I,
let's
find
out
what
he's
thinking
where
he
thinks
there
are
multiple
persona:
multiple
definitions
of
personas
but
and
I'll.
Look
in
the
product
marketing
stuff
to
to
see
what
we
have
it.
Cuz
I
think
what
we
have
in
the
product.
Marketing
part
of
the
handbook
is
his
referenced.
He
is
the
same
as
what's
here,
I
think
I
gotta
go!
Look
though,
and.
C
A
A
It's
it's
a
question
of
referencing
and
not
having
the
same
information
in
two
different
places.
That's
I
think
that
the
problem
right
now
is
that
we
have
the
same
exact
words
in
two
different
places.
Then
they
should
reference
and
point
to
the
one
place
where
we
do
it
so,
which
I
agree
with,
doesn't
make
sense
to
have
the
exact
same
words
in
two
different
places,
because
someone
will
change
the
exact
same
words
to
make
them
different.
B
D
B
D
Difference
of
why
they
ended
up
with
them
in
different
places
is
because
obviously,
buyer
personas,
the
best
sir,
in
the
handbook
for
like
the
product
mark,
seem
to
share,
but
I
think
the
UX
personas
ended
up
in
the
design
system
because
we
wanted
people
who
were
contributing
to
get
like
to
be
able
to
use
them.
Obviously,
we've
then
moved
by
personas
into
the
design
system.
That's
probably
a
bit
of
a
weird
experience.
I
think
we
will
be
better
moving
the
UX
ones
into
the
handbook.
A
With
you
there,
okay,
I,
want
to
make
sure
I
understood
which
which,
which
anti-pattern
you
were
referring
to
I,
live
either
way
with
it,
but
I
think
we
could
look
at
how
do
we
resolve
this
in
either
point
where
appropriate?
So
you
point
to
the
buyer
personas
that
exist
in
the
in
product
mark
in
the
in
the
hand,
looking
we
could
do
that
or
we
could
decide
to
move
stuff,
I
think.
B
It
makes
sense
I'm
at
I'm
aligned
with
what
Sarah
says.
I
think
the
buyer.
Personas
is
something
you
know
the
company
strives
for
to
know.
You
know,
get
our
sales
going.
While
you
know
building
features
for
gitlab
itself,
and
it's
actually
targeting
the
people
who
make
sure
you
use
the
product
itself,
which
is
difficult
by
it.
I
and.
A
You
know
I
think
about
it
is
I'm
thinking
about
this
down.
Just
just,
let
me
see
if
I
can
say
this
in
simple
terms:
I
think
there
will
be
cases
where
we
will
have
a
buyer
persona
that
will
have
a
user
persona
side
to
it,
that
there
would
be
a
buyer
persona
that
talks
about.
Why
do
they
buy
what's
their
problem?
What's
their
business
problem,
but
they
also
will
have
a
user
perspective
as
a
potential
user.
We
might.
We
will
end
up
with
that
scenario.
A
I
believe
if
we
go
down
this
path,
we'll
end
up
with
a
scenario
we'll
have
a
buyer
persona
talks
to
their
purchasing
problems,
why
they're
buying,
but
there
will
be
equally
a
user
persona
that
says
these
are
the
things
they're
doing
in
at
school
and
the
things
are
looking
for
them,
what
from
a
user?
And
how
do
we
design
for
that
user,
which
we
different
yeah.
B
D
A
D
B
A
The
buyer
persona
language
exists
in
two
places.
Exactly
the
same.
Language
exists
in
two
places,
and
so
maybe
so
I
don't
know,
that's
I.
Think
that's
one
option
is
to
say,
look
we're
gonna,
keep
them
in
two
separate
places:
buyers
here,
users
here
and
we'll
point
to
the
other
to
make
sure
people
can
navigate
to
where
they
want
to
be.
If
they
land
on
one
they
want
to
know
the
other
they
can
go,
but
we
won't
duplicate
information.
That's
one
option.
Yeah.
B
B
Feel
there's
a
hidden
problem
that
is
the
root
cause
of
this
and
I.
Think
that
it's
the
way
that
every
no
approach
this
he
knows
the
handbook
he
doesn't
know
the
design
system
I
think
I
mean
this
is
a
this
is
wager
I,
don't
think
he
is
edit
that
much
so
I
would
I
would
I
would
want
him
to
ask
him
that
question
myself
like
hey,
did
you
have
a
look
at
the
design
system?
Have
you
actually
used
it
once
he
you
know
in
things
you
need
to
do
or
I
have?
B
Has
it
been
used
by
the
people
directly
reporting
to
you?
How
many
of
those
people
have
used
it
and
I?
Think
most
of
all
I
expect
is
an
assumption,
will
say:
I
only
use
the
handbook
and
not
the
design
system.
So
in
that
way,
I
can
understand
his
reasoning
of
like
hey
I,
just
want
anything
in
the
handbook.
I
don't
want
to
look
in
two
different
places
right,
but
I
think.
B
A
A
C
He
didn't
tell
me
that
the
request
came
from
Sid,
so
I,
so
as
I'm
I,
guess,
I'm
thinking
about
UX,
personas
and
then
also
thinking
about
Sarah's
take
on
how
we
can
use
the
research
insight,
know
the
insights
for
posture
I'm,
going
to
get
this
right.
Sarah
I
will
get
this
right.
Eventually,
the
insights
repository
to
really
be
more
of
where,
where
that
UX
persona
lives
lives
and
when
I
think
about
what
a
design
system
is
for,
which
is
more
about
component
patterns
than
it
is
about
usage
behavior.
C
It
feels
to
me
like
we
could
write
an
especially
since
Sarah
to
your
point.
What's
in
the
design
system,
right
now
is
not
even
the
user
personas
really,
it
is
the
marketing
personas.
We
could
probably
take
pretty
quick
action
and
say:
okay,
no
problem,
let's
pull
what's
in
the
design
system
out
that
gets
rid
of
duplicate
of
content.
There's
no
downside
to
having
this
information
in
the
handbook.
So
let's
go
ahead
and
just
get
it
into
the
handbook,
at
least
in
some
sort
of
an
updated
format
where
we
all
go.
C
C
B
Actually,
to
go
for
right
now
and
that
gives
us
value,
then
I
think
that
we
should
do
that
I'm
still
almost
and
like
hey.
We
should
have
two
places,
but
you
know
if
that
is
the
end
goal,
we're
striving,
for
that
seems
like
good
idea
and
doesn't
work
in
the
you
know
in
the
right
now
here
we
should
do
something
else
and
yeah
I'll
put
it
on
my
facilities
for
next
week.
Awesome.
C
Yeah
I
think
I
think
that's
yeah
I
think
that's
a
really
good
short-term
change
and
then
we
start
to
figure
out
how
the
incites
repository
works
and
where
maybe
that
fits
into
the
overall
design
cyst
and
we
can.
We
can
always
change
from
there,
but
at
least
I
gets
rid
of
duplicate
of
content,
and
that's
that's
a
positive
thing.
So.
D
The
use
of
consumers,
but
obviously
like
product
marketing,
we're
involved
with
them,
so
we
could
to
be
kind
of
flexible
in
a
way
and
but
we
targeted
here
we
think
we
use
is
we
couldn't
concentrate
on
everyone.
So
again
we
kind
of
got
confirmation
from
product
managers
about
what
they
wanted
to
get
out
of
it.
So
they
were
the
personas
we
concentrated
on
first,
but
we
know
that
even
since
August
they
have
grown
the
type
of
people
that
we
should
be
designing
for.
D
I
think
this
is
where
the
insight
reposed
I
keep
thinking
about
it,
because
I
can't
keep
pace
with
the
amount
of
personas
that
they
want
us
to
produce.
But
we
can
produce
insights
that
some
people
are
good.
That
they're
in
and
you
know
we
can
do
user
interviews
and
we
can
collectively
pull
together
those
insights
to
give
people
an
understanding
of
the
type
of
user.
This
design
involved
so.
A
C
Yeah
I
think
that
I
think
that's
exactly
what
we
were
proposing
and
Dimitri
I'll
leave
it
up
to
you
as
you
move
the
content
because
to
link
to
the
handbook
to
the
personas
in
the
handbook
from
the
design
system.
Sure
that
makes
sense
does
it
make
sense
for
it
to
still
have
its
own
page
I,
don't
know,
you're
a
good
designer.
You,
like
you,
figure
out
where
it
goes.
B
Note
this
this
meeting
has
been
going
quite
quite
long,
I
thought.
Maybe
we
could
push
it
within
the
hour.
That
gives
us
around
five
more
minutes
and
I.
Think
that's
a
pretty
nice
timing
for
this
meeting.
We
can,
you
know,
continue
next
time
with
any
additional
topics
that
we
might
have
so
I
want
to
give
the
opportunity
for
everyone
like
we
have
any
less
points
for
this
agenda
or
any
points
that
you
want
to
discuss,
tasks
that
I.
D
Think
one
thing
that
will
just
very
quickly-
and
this
is
for
John-
is
that
product
marketing
we
work
with
you
intermittently
now
and
again
and
I
think
we
should
have
a
regular
meeting
set
up
between
us
research
and
product
marketing,
and
in
that
way
we
can
be
sharing
insights
more
regularly
and
I
work
quite
closely
with
Cindy
on
the
secure
side
as
well
and
she's
fantastic.
So
I
think
it
would
be
really
good
to
get
insight
from
the
rest
of
the
team.
I.
A
B
I
have
I
want
to
quickly
touch
fun,
but
I
we
don't
have
to
like
would
go
way
into
it.
I
saw
this
point
number
P
at
point:
five
by
Christie
disciple,
to
infuse
personas
into
our
design.
Thinking
Sarah
proposed
a
label
into
the
research
repository
I'd
introduced
some
labels
like
more
general
route.
Labels
I
think
you
know,
personas
give
their
value
when
they're
actually
being
used
and
I.
Think
that
is
currently
still
kind
of
missing.