►
From YouTube: Why move features down
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
So
we're
talking
about
the
urgency,
if
you
can
move,
features
down
that
we
should
do
it
as
fast
as
possible,
and
the
reason
is
is
if
we
move
features
down.
For
example,
we
open-source
them
down
in
tears
and
we
open-source
something
we
get
more
users.
The
users
get,
are
gonna,
get
more
value
from
get
loud,
they're,
gonna,
use
more
stages,
and
that
increases
the
future
potential
for
get
laugh.
So
it's
we
have
our
buyer
based
open
core
model
and
it's
sometimes
hard
to
figure
out
who
the
buyer
is.
A
So
we
tend
to
put
features
in
a
bit
of
a
too
high
tier
and
then
move
them
down
as
we
as
we
figure
out
that
we
were
wrong.
However,
what
happened
in
the
last
year,
or
so
is
that
we
put
them
in
high
tiers,
but
then
never
really
waited,
and
everyone
was
a
bit
hesitant
to
move
them
to
move
the
features
down.
That's
now
really
hurting
the
popularity
of
Gitlin,
but
because
we
have
features
that
should
be
figured
out.
We
should
be
open
core,
for
example,
a
focus
mode
for
issues.
A
That's
not
a
feature
that
managers
care
about.
That's
four
ICS:
we
should
have
moved
that
down
a
long
time
ago
and
because
we
don't
do
it,
the
feature
doesn't
have
as
many.
It
doesn't
increase
users
like
people,
don't
tell
their
friends
about
gate
lab
because
it
doesn't
have
a
focus
mode.
So
we
get
fewer
users.
A
Also
users
use
less
of
the
product
people,
maybe
user
source
control,
but
not
our
planning,
because
that
sort
and
they
were
missing
the
focus
mode
and
third
people
aren't
contributing
if
the
focus
mode
is
broken
or
mobile.
If
it's
only
for
our
paid
users,
that's
10%
of
our
users,
it's
much
less
likely
that
someone
will
contribute
a
fix.
A
We
have
to
optimize,
get
lab
for
like
long-term
revenue.
That's
our
goal
want
to
be
at
a
billion
dollars
of
revenue
in
2023.
That's
gonna,
be
how
many
users
do
we
have?
How
much
value
do
we
create
for
users
and
I?
Think
stages
being
used
per
user
is
a
good
proxy
of
that
like
the
more
stages
you're
using
it
lab
like
the
better.
You
benefits
from
having
everything
in
a
single
application
and
then
of
tikrit
like
how
much
of
that
value
that
we
created,
which
is
users
time
stages.
A
A
The
number
of
stages
in
a
dis
effect
give
up
getting
better
as
a
product,
and
we
need
that
sense
of
urgency
like
hey,
we
can
be
wrong,
but
then
we
quickly
move
it,
but
what
I'm
seeing
now
is
okay,
we
were
wrong,
but
we're
not
we're
not
in
a
rush.
Maybe
maybe
we'll
introduce
something
in
the
future.
If
you're
going
to
introduce
something
in
the
future.
Great
you
make
that
a
page
feature.
For
example,
service
desk
service
does
so
probably
be
in
court
and
then
custom
template
should
be
a
page
feature.
So
we
got.