►
From YouTube: Digital Experience Retro - March 23, 2023
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/digital-experience/
A
Hi
everyone
welcome
to
digital
experience.
This
is
our
iteration
retro
today
is
Thursday
March
23rd
and
we'll
go
over
some
of
the
things
that
went
well
and
things
to
improve
on
from
the
last
two
week
period.
First
up
for
things
that
went
well
is
Nathan
thanks.
B
Laura
yeah
I
want
to
give
a
massive
thank
you
TM
for
jumping
on,
like
I,
think,
there's
two
or
three
15
10
released
post
issues
that
the
the
team
popped
up
with
Christina
does
if
we
can
get
them
out
in
like
a
day
or
two
for
the
1510
release,
and
we
did
it
and
I
went
through
and
looked
at
their
their
1510
retro
and
like
the
only
thing
that
went
well
was
like
found,
a
team
that
can,
you
know,
fix
our
bugs
quickly
kind
of
thing
and
I
was
like
yeah.
B
That's
us
so
huge.
Thank
you,
then,
also
for
the
the
homepage
thing
that
we
had
a
timeline
to
get
it
released
yesterday,
and
we
did
so
amazing.
Thank
you,
Laura
I
think
you
got
the
next
one.
A
Yeah
sorry
I'm
still
typing,
but
I'll
use
it.
Thank
you
for
doing
the
all
of
the
changes
to
CSS
in
our
navigation,
repo,
switching
things
up
so
that
we
have
One
Import
kind
of
top
level
and
then
getting
to
remove
every
single
reference
to
slippers
on
on
all
of
our
components.
It's
just
much
more
efficient,
I,
don't
know
if
it'll
help
your
problems
like
it
sounds
like
you're
you're
chasing
all
these
rabbit
holes,
but
worth
a
try
and
I
think
it's
going
to
be
an
improvement
anyway.
C
I
just
want
to
say
thank
you
Laura,
for
showing
up
like
a
boss
in
our
smart
Lane
synced
meeting
like
you,
asked,
really
good
questions
and
got
down
to
the
meat
of
like
hey.
What's
going
on,
help
us
fix
this.
Is
it's
really
good.
D
I
think
I've
got
the
next
under
things
to
improve,
so
we
just
we're
working
on
this
free
trial,
Landing
a
paid
search
page
and
like
ideally
the
when
you
land
on
this
page
you'd
be
able
to
just
fill
out
the
form
right
there,
but
because
it's
on
the
product
side
to
like
sign
up
for
a
free
trial,
we
can't
embed
the
form
on
the
like
about
docket
lab
side
of
the
website.
D
D
Yeah
so
the
like,
if
you're
gonna,
sign
up
for
free
trial,
you're
no
longer
on
the
about
document,
lab
page
you're
on
just
like
gitlab.com
like
the
product
side
and
that's
where
the
form
lives
and
so
I.
Think
because
of
like
different
codes
and
whatnot
I
mean
it's
I,
don't
think
Megan's
here
she
was
working
on
it,
but
there
was
no
way
to
like
move
that
form
from
the
product
side
to
our
side
of
the
website.
D
So
we
weren't
able
to
to
do
what
we
wanted
to
do
in
terms
of
like
having
a
an
experience
for
that
person
was
just
like
on
the
page
ready
to
go
sign
up
right
there,
no
just
like
send
them
one
more
step
further
and
every
time
you
have
like
an
extra
step,
you
know,
and
that
blow
it
just
like
breaks
it
down
a
little
bit.
E
D
Some
of
this
a
dedicated
search
or
paid
search
page,
so
it's
most
likely
not
someone
who
is
already
a
user.
Someone
who
saw
an
advertisement
forget
lab
and
click
through
and
is
like
ready
to
potentially
purchase
or
sign
up
per
trial,
so
unlikely
that
they'd
be
an
existing
customer,
but
the
extra
step
is
just
like,
instead
of
embedding
the
form
right
on
the
page
that
they
go
to
now,
we
have
to
like
click,
a
button
to
go
to
another
page
to
get
the
form
that
they
wanted.
D
So
it's
just
one
not
a
huge
step,
but
I
need
an
extra
step
and
just
any
time
you
have
an
extra
step
in
ux.
Usually
you
could
drop
off.
So
that's
what
we
want
to
avoid.
B
C
C
D
C
C
Drop
a
thread
in
the
issue
with
just
a
little
update
of
what's
going
on
what
work
has
taken
place.
This
shows
movement
and
it
enables
us
to
recall
the
actions
that
needed
to
be
done
to
complete
those
issues
and
it's
just
yeah.
A
C
B
I
actually
want
to
piggyback
on
that.
It's
I
noticed
this
especially
helpful
when
dealing
with
third-party
vendors,
like
when
we
were
dealing
with
smartling
and
and
just
kind
of
those
conversations
that
happen,
sometimes
just
through
email,
threads
and
then
you're
like
hey,
like
I,
didn't
know
this
happened
like
oh,
it
was
an
email
with
me
and
I,
don't
know
the
rep
from
sparkling,
so
even
some
of
those
Communications
just
getting
them
publicly.
Like
I
learned
my
lesson
with
the
with
sparkling.
C
Yeah
and
we
can
make
things
private
like
if
you're
not
sure
if
it
should
be
a
public
thread,
you
know,
make
the
thread
private
or
the
whole
issue,
but
at
least
it.
It
allows
us
to
look
back
and
find
all
that
that's
stuff,
because
we're
working
on
really
complex
things
and
it's
nice
to
have
like
a
single
source
of
Truth
or
that's
all
all
documented.
If
it's
not
in
the
handbook
or
something.