►
From YouTube: Digital Experience FY22 Q1 OKR Candidates
Description
Overall OKR Candidates: https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/150
Digital Experience Specific OKRs
• [Q1 FY22 OKR Candidate] Slippers Design System
• [Q1 FY22 OKR Candidate] Inquiry Generation
• [Q1 FY22 OKR Candidates] CMS & Blog
• [Q1 FY22 OKR Candidates] Measurement
• [Q1 FY22 OKR Candidates] Tech Debt/Improvement
A
A
So
this
came
about
our
entries
came
about
as
a
team
from
our
off-site
held
in
the
first
week
of
january
2021,
and
we
did
an
exercise
where
we
just
spent
some
time
a
fair
amount
of
time.
A
He
was
about
an
hour
writing
down
the
tops,
five
things
with
one,
the
six
as
a
bonus
and
what
I
went
through
as
you
can
see
here,
as
I
went
through
everybody's
group
them
into
themes,
I
saw-
and
we
started
with
just
these
overall
overarching
arching
objectives,
so
todd's,
I'm
sorry,
sids
is
just
increa
increase
iacb
for
the
company
todd's
from
the
strategy
deck
that
he
shared
a
few
months
ago,
hit
130
million
dollars,
iacv
and
fy
22
on
a
flat,
year-over-year
marketing
budget.
A
A
There's
a
lot
of
things
we
need
to
do
to
make
it
operationalizable
it's
a
bit
of
a
mouthful
of
a
word,
primarily
thinking
about
implementation,
thinking
about
localization
how
it
relates
to
local
legislation,
efforts
we
have
going
on
operationalization
governance
and
documentation
and
then
accessibility.
A
So
we
don't
have
any
targets
in
mind
yet,
but
you
can
see
here,
we've
we're
sticking
to
this
format,
so
we
will
deliver
changes
that
drive
our
metrics,
which
will
be
inquiries
on
the
marketing
site
faster
by
measured
by
these
below.
Here
I
won't
go
into
those
individually
feel
free
to
click
into
each
one
of
these,
for
example,
implementation.
A
Just
a
couple
notes
so
implementing
it.
So,
let's
rolling
it
out
so
on
the
navigation.
If
we
don't
complete
that
this
month,
the
feature
maturity
chart
on
our
home
page
other
pages
that
we
have
in
flight,
basically
saying
that
we're
gonna
build
this
out,
while
we're
supporting
other
okrs
that
we
commit
to.
So
this
one
will
sort
of
be
a
a
yes
and
okr
for
us.
A
So
if
it's
localization
that
we've
commit
to
as
a
team,
great
20
of
that
time
would
be
really
well
suited
for
us
to
do
the
localization,
but
also
bring
that
into
our
design
system
and
do
a
couple
things
to
make
sure
that
we're
by
the
end
of
q2,
able
to
roll
this
out
company
wide
and
anyone
can
go
through
the
documentation,
copy
paste
and
build
these
sites,
which
is
the
ultimate
goal
for
us.
Speed
us
up,
make
our
team
of
currently
nine
into
effectively
1300
or
whoever.
A
However,
many
people
work
for
gitlab
or
want
to
contribute
inquiry
generation.
So
we
really
want
to
think
about
things
that
we
can
drive
our
key
metric
forward.
So
things
that
came
up
diversifying
lead
sources,
making
sure
that
we
have
consistent
lead,
gen
mechanisms
on
every
page,
improving
the
ux
of
inquiry,
capture,
focusing
on
specific
segments
and
target
audiences,
so
meeting
people
where
they're
at
giving
them
a
little
bit
of
personalized
content
with
the
limited
ability
we
have
to
do.
So.
A
I
still
think
there
is
opportunity
for
us
to
make
things
a
little
bit
more
relevant
and
then
we've
also
put
localization
into
here
as
well,
because
effectively,
if
we
don't
have
an
experience
for
japan
and
we
then
have
an
experience
for
japan,
we've
just
diversified
our
inquiry
generation
by
100
percent,
it's
kind
of
easy
math
and
again
each
one
of
these.
You
can
go
into
and
there's
just
a
little
bit
more
information.
A
A
That
could
slip,
and
if
it
does,
we
want
that
to
be
something
that
is
brought
into
q1
measurement
metrics
that
we're
looking
at
are
inquiries
generated
from
blog
content
increase
in
page
views,
bounce
rate
time
on
page
some
pretty
standard
metrics.
You
expect
to
go
up
by
putting
some
time
and
effort
into
you
know,
enhancing
your
your
content,
delivery
mechanisms
so
just
clicking
into
this
redesign
of
the
blog
homepage,
because
this
is
something
I
think
we
have
a
ton
of
opportunity.
A
It's
that
first
impression
of
people
coming
to
you
know,
engage
with
all
this
amazing
content.
The
content
team
is
making
and
it
just
doesn't
really
do
the
best
job
of
positioning
us
as
the
awesome
company
that
we
are.
A
A
We
don't
want
to
just
start
measuring
everything,
because
that
it
inevitably
slows
down
the
site
and
then
makes
a
whole
bunch
of
data,
that's
useless,
so
really
being
able
to
explicitly
communicate.
Hey.
We
changed
this
and
we
saw
this
number
go
up.
We
know
when
that
number
goes
up
this
other
number.
A
You
know,
maybe
its
inquiries
goes
up
by
this
many
percent,
so
we
can
start
having
a
data
informed
approach
to
all
the
work,
we're
doing
and
being
able
to
report
back,
maybe
twice
a
month
on
how
like
quantitatively,
how
the
work
we're
doing
is
having
a
positive
impact
to
gitlab
as
a
company.
A
Finally,
tech,
debt
and
improvement.
So
this
is
the
one
that
no
one
likes
to
talk
about.
We
aren't
going
to
beat
the
drum
too
hard
on
this
one.
There's
things
that
are
just
necessary.
A
You
know
having
a
a
stable
tech
stack
is
really
going
to
enable
everybody
in
marketing
or
the
company
site-wide,
and
we
also
would
like
to
have
a
agreement
that,
while
we're
doing
the
work
against
everyone
else's
okrs
as
as
our
own,
while
we
have
a
page
open
we'd
like
to
dedicate
a
small
amount
of
time
to
just
making
sure
we
can
make
that
page
as
good
as
possible.
A
So
everything
is
incremental
tech,
debt,
tech
improvement,
things
like
a
digital
asset
manager
and
cdn
integration.
So
these
are
things
that
are
going
to
massively
help
our
performance
so
having
a
single
source
of
truth
for
marketing
assets
on
the
dam
and
then
delivering
our
images
via
cdn
is
gonna.
Have
a
twofold
benefit.
One
our
page
load
speed
is
gonna,
go
up
immensely,
which
is
obviously
a
good
thing,
and
by
removing
using
a
cdn
and
moving
all
of
our
images
outside
of
git.