►
From YouTube: Product Group Conversation (Public Livestream)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
C
D
Hey
so
kind
of
calling
myself
out
here,
I've
never
filed
an
issue
or
improvement
suggestion
or
anything
on
get
lab
product
and
I
feel
a
little
daunted.
Cuz,
there's
just
a
lot.
So
if
I
was
going
to
do
that,
mostly
just
to
learn
like
what's
a
good
place
to
start,
because
I
feel
a
little
unsure
about
that
and
I
don't
really
want
to
make
someone
crazy
with
a
duplicate
or
whatever.
D
I
mean
I,
guess
even
stepping
back
from
that
cuz
I
think
if
you're
not
in
product,
you
might
not
even
know
what
those
are
just
like
say:
I'm
using
I'm
using
gitlab,
calm
and
I'm.
Like
oh
yeah,
you
know,
I
keep
doing
this
manual
thing.
I
really
wish
I
could
just
have
some
easier
way
to
do
that.
What
do
I
even
begin
I.
C
Would
I
would
go
to
the
what
we
call
Direction
pages
so
if
you're
interested
in
a
given
area,
you
know,
for
example,
if
we
take,
let's
say
it's
something
in
in
plan:
Eric
Brinkman
has
a
direction
page.
It's
called
dev
direction,
slash
dev
and
he's
got
a
bunch
of
themes
in
there
that
we,
we
believe,
are
important
for
our
overall
dev
strategy.
You
underneath
that
you
can
find
where
we're
headed
for
a
given
stage
and
also
for
a
given
group.
So
if
we
go
down
to
like
chi,
has
the
web,
the
web
IDE
stuff.
C
If
that's
the
area,
where
you're
having
an
issue,
you
can
go
in
and
see
what
he's
already
planned
milestone
over
milestone
and
if
there's
an
issue
that
you
think
is
as
close
to
what
you
want,
you
can
get
in
there
and
add
your
feedback
so
that
you're
not
creating
duplicate
issues.
If
you
don't
see
it,
you
could
always
create
a
new
issue
and
tag
Chi
in
it
for
his
consideration
Chi
since
I
used
you
as
an
example,
is
there
anything
else
you
would
recommend
Danielle
do
no.
E
E
D
F
A
C
We
do
the
third-party
is
working
on
a
doc
to
summarize
their
opinions
of
what
they're
seeing
we
have
yet
to
review
that
as
an
e
group
and
make
many
decisions
so
I
might
I
might
defer
my
plus
on
answering
this
question
because
I
don't
want
to
I,
don't
want
to
miss
that
expectation
that
what
we
will
or
we
won't
do.
Maybe
I
could
summarize
a
few
key
themes.
C
C
There's
pain
around
true
ups,
trying
to
think
of
some
other
key
takeaways,
the
we're
looking
at
all
kinds
of
stuff
like
billing
models
for
comm,
true
patterns
price
points.
What
what
do
they
value
or
not
value
in
each
package
so
that
we
can
market
better,
there's
a
ton
of
stuff
that
they're
looking
at
and
we're
looking
at.
We
have
a
new
pricing
product
manager,
who's
now
on
the
mix
as
well
and
is
looking
at
a
variety
of
things
too.
C
G
Yeah,
it's
got
so
for,
like
you,
know,
section
or
stage
specific
feedback
like
that,
like
the
perception
of
value
of
plan,
especially
from
users
who
use
JIRA
now
I'm.
Considering
the
conversations
we
have
last
week
about
the
importer
like
where,
where
can
we
or
can
we
see
some
of
this
feedback
or
at
least
get
it
in
a
form
that
we
can
use
to
inform
decisions?
It's
it
seems
like
there's
some
value
we
could
get
from
that
yeah.
C
H
C
H
Got
eight
so
yeah,
so
our
number
one
theme
is
enterprise,
readiness
and
I
know
I'm
working
on
group
level.
Integration
I've
got
some.
You
know,
enterprise
specific
integrations
that
I'm
looking
at
add
I
just
be
curious
to
know
like
what
are
some
some
other
interesting
initiatives
that
we're
doing
across
there
different
stages
for
enterprise
readiness.
Just
so
I
have
some
clarity
on
here.
People
I
should
go
talk
to
you
like
what
are
some
other
things
that
I
can
help
align
with.
You
bet
the.
C
Manage
area
is
is
handling
a
lot
of
them,
as
is,
is
enable
that
and
I'll
cover,
some
of
them
so
in
manage.
We
have
large
customers
want
a
lot
of
flexibility
in
authentication
and
authorization.
They
tend
to
have
groups
that
they've
acquired
in
funky
org
structures,
and
they
want
to
set
permissions
in
very
granular
specific
ways,
and
so
the
access
group
is
working
on
a
lot
of
things
around
that
that's
a
big
one.
C
The
manage
team,
let's
see
so
also
in
manage,
there's
a
group
called
compliance.
A
lot
of
large
enterprises
want
to
be
able
to
do
quick
audits
and
want
to
be
able
to
keep
their
compliance
teams
happy
with
very
little
effort,
and
so
we're
going
to
be
investing
more
in
compliance,
features
and
functions
for
larger
companies
where
they
have
more
of
an
audit
motion
in
enablement,
we're
working
on
calm
stability
and
performance
for
large
customers
that
might
test
our
system
in
unique
ways.
C
The
Geo
team
is
has
a
lot
of
work
to
do
for
some
large
customers
to
improve
the
way
GL
functions
for
very
large
customers
that
have
different
deployments
of
gait
lab
around
the
planet.
Giddily.
The
Gili
team
is
working
on
gittel
eh-eh-eh
for
a
number
of
large
customers
that
really
exercise
giddily
in
heavy
ways.
Those
are
a
handful
of
examples,
but
it's
it's
a
very
cross
stage.
Activity.
I
C
Geo
teams
doing
some
work,
there
just
feel
free
to
pile
in
if
I'm
missing
any
but
we're
adding
more
people
to
enablement
teams
which
are
very
much
helping
with
calm
readiness,
and
we
want
to
be
in
a
position
where
a
large
enterprise
can
pick
their
deployment
model.
We
don't
want
to
only
be
in
a
position
where
we
offer
self-hosted
to
larger
customers.
Sas
is
a
trend.
C
A
lot
of
customers
are
not
going
to
want
to,
ideally
will
not
want
to
host
this
themselves,
not
all
of
them,
and
we
intend
to
make
self-hosted
an
awesome
option
going
forward
as
well,
but
we
don't
want
comm
to
be
viewed
as
a
liability
relative
to
self-hosted.
We
want
them
to
just
make
the
deployment
choice
they
would
like
and
and
have
a
great
experience,
either
way.
L
Yeah,
so
just
wanted
to
highlight
it.
It's
interesting
that
it
probably
sounds
a
little
bit
more
like
it
is
focused
on
self-manage,
but
if
you
think
about
the
dot-com
experience,
I
think
it
actually
helps
calm
users
even
more.
If
you
are
a
self-managed
customer,
you
have
all
sorts
of
admin
controls.
You
have
things
that
you
can
do
with
the
instance
that
you
inherently
can't
do
on
calm,
because
calm
is
a
large
get
live
instance
and
we're
the
admins
of
that
instance,
and
so
the
ways
that
groups
interact.
L
The
controls
that
group
owners
have
the
way
that
groups
are
isolated,
is
incredible,
important
for
calm
being
able
to
ensure
that
other
groups
can't
see
even
users
or
other
projects
ensuring
that
forking
and
cloning
happens
in
a
certain
namespace.
These
are
all
things
that
enterprises
expect
that
you
can
enforce
on
self-managed
that
you
can't
necessarily
enforce
the
Viacom.
So
all
sorts
of
improvements
are
going
there
out
of
the
managed
access
groups
and
the
managed
spaces
groups,
and
so,
when
we
say
in
a
priority
is
we
are
definitely
considering
calm
here.
C
All
right,
thank
you
very
much.
Eric
appreciate
the
extra
context
as
well
as
Josh
Cindy
slight.
Eight.
We
D
investing
from
defend
altogether.
No
I
would
view
it.
As
a
merger
of
the
two
sections
we
will
expend
more
energy
on
secure.
That's
a
near
term.
Fy
21
driver,
our
defend
offerings
are
a
longer-term
bet.
We
are
going
to
keep
a
handful
of
those
categories
going
with
this
combined,
secure,
plus
defend
group.
B
C
Is
normal
for
for
a
large
organization
like
ours
to
do
some
shifting
at
SendGrid
we
had.
We
managed
our
our
our
new
investments
through
something
called
the
three
horizons
model
and
we
had
horizon.
One
was
the
profit
Center
horizon
2
was
the
growth
center
horizon
3,
where
your
longtree
longer-term
bets,
and
so
each
year
we
would
evaluate
how
much
we
were
spending
in
each
area
and
we
would
we
would
readjust
if
we
were
yeah.
C
We
wanted
to
make
sure
that
our
strategy,
as
a
company
as
a
product
line
mat
where
we
were
investing,
and
so
it's
quite
normal
for
us,
probably
on
an
annual
ish
cadence,
to
make
shifts
like
this
I
think
it's
healthy.
It's
kind
of
like
rebalancing.
Your
financial
portfolio,
like
you,
want
to
have
the
right
amount
of
investments
in
near
term
versus
long
term,
and
so
we
well,
we
didn't
use
a
three
Harrisons
model
here.
C
C
M
While
I'm
being
noisy
and
asking
questions
the
it
says,
compliance
will
be
under
desired
staffing
levels,
just
my
my
two
cents,
three
cents
for
what
it's
worth.
I.
Think
that
that's
an
area
that
has
been
a
big
driver
of
conversations
for
a
very
long
time
that
we
haven't
focused
on
enough.
Given
the
interest-
and
it
just
seems
like
we're,
missing
an
opportunity
there
to
really
use
compliance
to
drive
more
ultimate
deels
yep.