►
From YouTube: Roadmap Review for q4 to q1 with Tim Hey
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
Hey
y'all
just
wanted
to
do
a
quick
review
of
of
how
I
create
road
maps
for
the
expansion
group
and,
at
the
same
time
get
some
get
some
kind
of
feedback
on
some
new
things
that
I'm
doing
kind
of
to
plan,
with
our
new
focus.
A
So
we've
gone
through
a
couple:
different
iterations
as
a
growth
group,
and
now
we
all
have
kind
of
like
this
new
focus
to
focus
on
sas
free
to
paid
conversions
and,
as
a
result
of
it,
we're
trying
to
get
a
little
bit
more
organized.
A
You
know
how
I've
you
know,
historically
created
road
maps
and
and
organized
issues
and
and
things
for
the
for
the
team
to
work
on
and
then
now
what
I'm
doing
kind
of
for
this
next
iteration,
which
is
much
more
focused
on
just
like
one
swim
lane,
which
is
increasing
member
invitations
to
get
lab
and
I'd
love
to
get
some
feedback.
A
A
We
did
some
work
to
improve
the
workflows
for
our
sales
and
support
team,
and
then
there
was
a
small
period
of
time.
There
were
just
focusing
on
increasing
ci
cd
usage
on
gitlab.com,
so
about
the
big
themes
here
this
this
is
the
one
that
is
really
interesting.
I
think
this
is
where
we're
going
to
be
spending
the
most
the
majority
of
our
time
in
the
near
term,
so
figured
I'd,
get
this
one
kind
of
really
ironed
out.
A
So
what
I've
done
here
is
first
and
foremost,
I'm
I'm
just
using
kind
of
a
very,
very
broad
kind
of
label
for
this.
Just
so
that
way,
it's
easy
to
orient
around
the
overview
is
is
pretty
light
at
this
stage
of
the
game,
but
I
think
it
it
does
a
good
job
of
just
saying
hey.
This
is
why
we've
created
this
it's
kind
of
like
that
meta
epic.
A
So
that
way
we
can
have
child
or
that
parent
epic,
so
we
can
have
child
epics
underneath
it
that
then
allow
us
to
kind
of
cascade
the
road
map
once
they've
been
created.
So
that's
where
that's
what
this
actual
parent
epic
is
for.
It's
really
just
to
house
the
child
epics
for
all
of
the
work
that
we're
planning
on
doing.
A
As
you
can
see
here,
I've
got
one
two
three,
four,
five,
six
seven
kind
of
child
epics
that
roll
up
underneath
this,
the
the
first
four
are
really
the
ones
that
are
gonna
that
we're
gonna
be
working
on
over
the
next
one
to
two
quarters.
The
three
down
here.
These
two
have
already
been
completed
and
they're
they're
in
the
past,
which
I
guess
I
could
just
remove,
but
I
like
to
keep
my
work
there.
A
We
can
kind
of
house
it
in
that
one
place.
What
I
like
about
this
is
that
it
allows
us
to
do
a
couple
of
different
things,
one
from
the
list
view.
Not
only
can
we
see,
you
know
what's
happening
here
from
a
thematic
perspective,
so
obviously
this
this
first
one
and
they
go
in
order.
You
can
drag
and
drop
these.
Obviously
I
try
to
keep
these
nice
and
neat
and
in
the
order
in
which
I
think
they'll
they'll
actually
happen.
A
A
We
can
see
that
there's
three
issues
in
it
too,
and
if
we
wanted
to
see
the
actual
issues
you
can
just
hit
this
arrow
and
see
what's
happening
here
at
a
high
level.
You
can
see
that
we're
going
to
test
the
invite
member
copy
we're
going
to
send
an
email
to
single
member
group
owners
and
then
we're
also
going
to
add
a
form
to
inviting
teammates
to
the
from
the
create
group
page.
So
that's
one
way
to
see
kind
of
the
themes
at
a
high
level
and
then
also
the
work
that's
associated
to
them.
A
So
if
we
were
to
then
like
go
to
the
next
one,
which
has
eight
issues,
it's
probably
a
heavier
one.
This
is
where
all
the
work
is
going
to
be
done.
That's
focusing
on
uis
and
empty
state
improvements.
So
if
we
open
this
one,
you
can
see
all
of
the
individual
issues.
A
lot
of
these
are
still
in
problem
validation.
We
haven't
necessarily
sorted
out
exactly
what
it
is
that
we
want
to
do
yet,
but
they're
good,
valid
ideas.
A
We
definitely
need
to
need
to
validate
them
now
and
you
can
see
at
a
high
level
that
we've
got
eight
issues.
One
of
them
is
has
actually
already
been
completed.
This
one
was
an
experiment
to
add
invite
team
members.
This
is
going
to
be
shipping
in
13-6,
which
is
the
current
milestone,
but
the
work
has
been
done
and
it's
moving
forward.
So
it's
pretty
easy
for
us
to
kind
of
go
through.
A
Have
a
quick
view
of
this
see
the
themes
for
inviting
team
members
to
gitlab,
which
is
ties
back
to
our
overall
goal
of
for
the
quarter
and
our
focus
area,
and
then
what's
really
neat
about
this
is,
if
you
look
at
the
roadmap
view-
and
you
have
to
have
child
epics
in
place
to
do
this,
if
you
don't
it
it'll
just
show
you
basically
an
empty
state.
That
says
you
need
child
epics,
which
I
think
is
pretty
good.
A
A
You
know:
where
are
we
right
now
and
you
can
see
all
of
the
milestones
and
how
they're
plotted
out
once
you
get
a
good
understanding
where
you
are,
you
can
kind
of
just
collapse
that
and
then
you
can
see
back
to
the
actual
epics
that
have
either
passed.
This
is
one
of
the
reasons
why
you
can
make
the
argument
to
get
rid
of
the
old
ones
that
have
already
been
completed,
because
it
would
make
this
view
like
really
really
clean.
A
These
are
the
these
are
the
five
the
four
down
here
that
I
think
are
really
important
for
us
to
focus
on
over
the
next.
You
know
one
to
two
quarters,
so
we've
got
q4
right
now,
we're
almost
a
third
of
the
way
through
q4,
so
we've
got
to
start
getting
to
work
on.
Some
of
these
one
is
for
the
ui
and
empty
state
improvements,
and
you
can
see
how
that
kind
of
cascades
the
amount
of
work
we
have
in
there
might
go
into
the
q1
of
of
2021
the
low
hanging
fruit
stuff.
A
You
know
this
one.
If
you
click
on
it,
you
can
jump
right
in
and
see
the
actual.
The
three
different
issues
here
test:
invite
member
copy
you've
got:
send
an
email
campaign,
single
member
groups
and
add
a
form
to
inviting
teammates.
I
think
this
stuff
we
can
move
through
pretty
quickly.
You
know
I
say
that,
but
then
again
once
you
get
into
it
and
you
start
really
getting
to
work,
sometimes
other
things
kind
of
cramp
up
the
some
of
the
other
things
too.
So
we've
got
new
features
and
functionality.
A
I
think
this
is
a
really
interesting
one,
and
then
we've
got
new
programs
to
incentivize
users.
So
when
I
think
about
these
themes,
there's
like
kind
of
quick,
easy
wins
with
low
hanging
fruit,
there's
the
ui
and
empty
state
improvements
that
we
can
work
on.
I
think
we
can
get
a
good
handle
on
that
and
move
through
those
rather
quickly
new
features
and
functionality.
A
I
think,
are
going
to
need
they're
going
to
need
more
product
time
to
actually
figure
out
what
it
is
that
we're
going
to
try
to
build
and
really
kind
of
get
that
down
and
then
also
the
new
program.
So
new
programs,
just
at
a
high
level,
I've
identified
two
interesting
opportunities.
One
is
to
use
credits
to
incentivize
members
to
invite
more
people
right,
and
you
can
do
this
a
number
of
different
ways.
A
If
we
were
to
click
into
this,
you
can
kind
of
see
the
idea
here,
but
really
what
we
would
we
would
want
to
do
is
like
allow
allow
users
to
feel
empowered
to
invite
more
people
to
gitlab
and
when
we
do
that,
not
empowered
when
we
want
them
to.
We
want
to
incentivize
them
to
invite
more
people
to
gitlab
and
when,
when
they
do
invite
more
people
to
gitlab,
we
want
to
give
them
credits
to
things
like
ci
minutes,
storage
or
actually
discount
the
number
of
discount
the
amount
that
they're
paying
for
every
seat.
A
A
We
need
to
really
iron
this
one
out,
which
is
why
I
have
it
kind
of
scheduled
for
13
nine,
and
that
might
even
be
too
soon.
A
You
know
just
given
the
fact
that
there's
a
lot
of
things
going
on
in
gitlab
at
any
given
time
and
then
if
we
were
to
go
back
and
look
at
this
one,
the
send
merchandise
to
users
who
have
more
than
five
men
that
have
invited
more
than
five
members,
this
one's
pretty
cool
too.
This
one
would
probably
be
a
little
bit
lighter.
A
I
think
applying
credits
to
an
account
or
for
inviting
members
might
be
pretty
heavy
and
we
might
not
actually
want
to
do
that
right
out
of
the
gate,
but
something
like
this
might
be
a
little
bit
lighter.
I
would
consider
it
kind
of
a
program
because
we
would
have
to
set
up
basically
the
ability
for
for
a
user
to
identify
a
product
that
they
would
want
to
have
shipped
to
themselves.
A
They
have
an
api
offering
and
part
of
the
onboarding
solution
for
them.
Is
you
actually
have
to
send
yourself
a
t-shirt
through
their
api?
I've
always
thought
that
was
like
so
cool.
Maybe
it's
maybe
for
gitlab,
it
isn't
the
api.
Maybe
it's
they've
invited
x
number
of
users
and
then
they
can
get
a
link
to
you
know
a
swag
shop
that
has
a
collection
of
items
that
are,
you
know
like
us,
like
socks
or
a
hat,
or
something
that's
kind
of
inexpensive
but
meaningful.
A
So
when
I
think
about
programs
they're
a
little
bit
headier,
they
involve
more
parts
of
the
organization
and
they're
going
to
take
they're
going
to
take
more
time
for
us
to
actually
execute.
So
that's
kind
of
why
I've
justified
the
way
that
I've
I've
kind
of
set
them
up
here,
and
you
can
just
go
right
down
the
list
here
and
see
what's
happening
so
anyway.
That's
kind
of
my
my
spiel
on
on
how
I'm
going
about
the
road
map
and
how
I'm
organizing
issues
I
think
too.
Another
opportunity
is
there's
two
opportunities.
A
One
is
to
continue
ideation
and
I
and
and
and
identify
other
opportunities
for
us
to
create
issues
that
might
have
high
impact
with
low
effort.
I'm
always
open
to
that.
We
just
did
one
recently
probably
two
months
ago,
and
you
know
we
compiled
a
list
of
about
30
30,
different
ideas,
but
there's
always
opportunities
for
us
to
kind
of
find
new
things
and
and
come
up
with
ideas,
so
I'm
always
open
to
it
and
I'm
thinking
about
actually
scheduling
them
kind
of
more
frequently
like
on
a
cadence.
A
So
that
way,
we
don't,
we
don't
get
stale,
but
at
the
same
time
I
don't
want
to
burn
everybody
out
just
by
brainstorming
or
brainstorming
just
to
brainstorm,
and
then
the
other
thing
too,
that
I
wanted
to
call
out
here
is
these
these
child
epics.
These
are
pretty
light
right,
so
we're
looking
at
these
and
it's
really
just
kind
of
a
container.
A
What
I'm
thinking
about
doing
next
is
actually
building
out
the
definition
of
these
child
epics.
That
kind
of
give
the
overarching
theme
some
some
structure
and
some
direction.
So
that
way,
it's
easy
for
people
to
land.
On
this
and
say:
oh
okay,
this
is
where
we're
headed.
This
is
why
we're
doing
this
so
things
that
you
would
typically
see,
I
don't
want
to
say,
like
an
opportunity
canvas,
but
you
know
something
like
that
that
allows
us
to
identify
like
what
is
the
opportunity
here.
A
A
So
I
think
that's
kind
of
the
next
step
for
me
is
to
really
dig
into
these
themes
and
kind
of
create
some
more
structure
and
definition
around
them.
With
that
said,
I'd
love
some
feedback.
I
figured
I'd
just
do
this
quick
video
to
get
get
it
out
there
just
a
couple
of
ideas
anyway,
thanks
y'all,
if
you
made
it
this
far,
I
really
appreciate
it
see
ya.