►
From YouTube: Digital Experience Retro Video - Oct 21, 2021
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Digital Experience Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit?usp=sharing
A
B
Only
because
I
came
in
here
and
made
the
agenda
right,
I'm
sure
whoever
got
here.
First
was
the
same
thing.
The
ipo
went
great
good
job
team,
good
job
company,
good
job,
everyone.
You
know,
there's
so
many
things
to
say
and
if
you
were
on
the
marketing
call
the
department-wide
with
craig.
There
was,
you
know
like
45
minutes
of
congratulations,
so
I
don't
think
we
need
to
do
the
same
thing
but
like,
but
I
I
did
want
to
call
it
specifically.
I
put
a
really
bad
screenshot
in
here.
B
I
guess
we're
not
recording
screens,
I
put
a
bad
screenshot,
sorry
of
there's.
We
have
a
google
data
studio
like
traffic
monitoring
thing
and
there's
two
things
that
are
happening
in
there.
One.
You
can
see
a
huge
increase,
that's
like
obviously
from
ipo
traffic
right
in
general,
but
you'll
notice
that
the
traffic
goes
up
a
day
beforehand,
like
there's
a
there's.
B
A
big
hockey
stick
there
and
that
is
actually
before
ipo,
and
I
believe
that
it's
because
of
laura's
one
trust,
mr
because
the
hypothesis
was
that
cookie
bot
was
getting
in
the
way
of
our
analytics.
And
so
we
swapped
over
to
one
trust.
I
think
we
eliminated
a
whole
class
of
errors
with
our
analytics,
which
means
that
our
instrumentation
is
better
and
we
were
capturing
a
lot
more
of
that
traffic
and
then
because
we
turned
that
on.
Like
tuesday.
B
Just
I
think
for
our
team,
like
we
did
a
ton
of
we
did
a
ton
of
stuff
right
in
terms
of
like
getting
traffic
to
the
site,
instrumenting
traffic
on
the
site,
capitalizing
traffic,
on
the
site.
I
saw
a
bunch
of
other
metrics
about
like
a
ton
of
like
inquiries
and
stuff,
so
yeah,
just
huge
and
congrats
to
everyone.
A
B
Yeah,
but
I
mean
also
like
plus
one,
because
I
also
took
off
listing
day
like
we
had
a
bunch
of
people
off
during
like
one
of
the
busiest
so
like
thanks
to
people
who
are
around.
Obviously
you
know
but
like,
but
I
think
you're
right
about
the
processes
and
like
you
know,
but
we
still
managed
to
make
it
work.
Or
you
know
yeah.
B
Yeah,
I
think
that
everyone
like
us,
the
people
we
work
with
people
work
around
us.
I
think
that
everyone
got
really
used
like
I
think
a
ton
of
processes
broke
at
get
lab
and
I've
seen
that
same
sentiment
across
a
ton
of
like
retros
on
like
three
or
four
different
projects.
I've
been
on
the
last
couple
months
and
it
makes
a
lot
of
sense
like
pressure
happened
and
like
people
like
did
whatever
was
the
path
of
least
resistance,
and
sometimes
that
is
like
not
the
process
I
would
like
likes.
B
I
think
you
know
some
of
gitlab's
values
and
ways
that
we
operate
are
not
the
default
way
that
people
have
been
trained
to
operate
in
the
modern
working
world,
and
so
it
is
like
hard
to
do
that
by
you
know
naturally,
and
then,
when
the
pressure
gets
turned
up
a
notch
or
like
over
a
thousand
percent
like
things
break
down,
so
I
think
things
to
improve
on
is
like.
We
just
need
to
start
like
drawing
those
boundaries
again
like
I
am
still.
A
B
Didn't
do
this
because
we're
doing
all
these
other
things
so
now
everything
else
has
more
pressure
built
up,
but
I
think
that,
like
we
should
be
like
really
on
our
game
about
like
async.
First
like
like
get
it
in
an
issue,
don't
take
work.
I
thought.
Barker
has
a
note
here
of
async.
First
always
work
from
issues,
merge,
request,
agendas,
do
not
work
from
slack,
do
not
work
from
dms
and
slack
like
like
don't
like.
B
B
A
Yeah
I'll
just
follow
up
on
that,
because
I
think
and
learn
hit
on
it
too,
but
it's
not
just
being
async
but
also
being
async
using
gitlab
tools,
and
I'm
not
sure
if
there
was
some
particular
reason
why
we
weren't
able
to
use
private
issues
or
private
epics
for
this
ipo.
But
I
definitely
didn't
see
a
single
one
and
since
that's
how
it
all
how
we
all
work
most
of
the
time
that
feels
like
it
would
have
made
things
a
lot
smoother.