►
From YouTube: Digital Experience Retro Video - Sept 9, 2021
Description
Digital Experience Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit?usp=sharing
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
A
Hi,
everyone
welcome
to
the
digital
experience
team
retrospective,
we'll
be
going
over
what
went
well
and
what
we
can
improve
on
from
the
last
two
weeks
today
is
september
9th
and
for
things
that
went
well.
First
up
is
nathan.
B
Yeah,
I
just
wanted
to
add
that
kind
of
once
the
essentials
were
in
place
and
a
lot
of
the
components,
the
view
components
were
in
place.
Building
out
new
pages
is
going
to
be
a
lot
quicker.
I
already
noticed
it,
so
I
don't
want
to
get
quoted
on
like
some
time
frame,
but
I
think
going
forward.
If
we
have
to
revamp
a
page
or
rebuild
a
page,
I
can
already
tell
it's
going
to
take
a
lot
less
time
so
yeah
just
something
that
went
well
and
something
to
look
forward
to.
A
I
added
a
plus
one
on
there,
it's
looking
cool.
I
can
start
with
the
things
to
improve
on.
I
think
I've
got
the
the
only
point
there.
Sometimes
things
come
up
in
slack,
which
we've
talked
about
before
in
the
is
this
known,
channel
or
website
or
whatever
that
are
bugs,
and
you
know
we
don't
really
have
a
process
in
place
for
who
takes
those
on.
I
don't
know
if
I'm
over
processing
it
over
processifying
this
or
if
it's
fine,
it's
just
whoever
you
know
smells.
A
Sees
it
first
like
a
hot
potato
situation
in
previous
companies,
we
have
had
one
person
that
like
takes
it
on
every
week.
They
like
manage
to
support
channels,
but
I
don't
know:
if
that's
the
way
we
need
to
go
but
yeah.
I
see
a
few
points
in
there.
B
Yeah
not
much
to
add
other
than
I'm
assuming
this
would
fall
under
the
responsibilities
of
a
pm.
I
think
I
know
that
there's
I
think
we're
still
trying
to
hire.
I
think
I
saw
an
interview
next
week,
so
hopefully
that
could
you
know
kind
of
fall
off
our
plates.
C
I
have
the
next
point,
and
I
I
I
I
I
see
that
a
lot
of
people
have
thoughts
on
this,
so
I'm
just
gonna
focus
on
that.
C
I
don't
know
how
comfortable
I
feel
with
our
team
like
taking
requests
straight
from
sly,
because
it's
like,
I
feel
like
if
product
like,
if
other
teams
have
the
other
teams
have
like
essentially
like
different
processes
for
like
bringing
up
like
issues
and
like
escalating
issues
like
I
feel
like
we
should
too
and
it's
I
don't
think
it's
fair
to
us
to
just
be
like
the
oh,
like
something's
broken.
C
Let's,
let's
get
tagged
on
slack
and
like
do
that,
I
feel
like
there
should
be
like
more
definition
about
that
and
then
at
some
point
for
that,
it's
like
whose
responsibility
is
it
to
look
through
issues
for
all
our
it's
like
a
ton
of
teams
responsibilities.
So
it's
but
again,
since
I
feel
like
we
are
from
an
engineering
perspective,
like
the
only
people
that
really
work
in
that
it's
I
don't
know,
it
gets
tricky,
especially
as
we
start
to
like
who
owns
this
project
like
that.
C
D
I'll
vocalize,
my
point
on
that
I
it
is
tricky
because
I've
noticed
that
sometimes
you
know
we
say,
make
an
issue
and
then
like
the
issues
created
and
then
it's
not
assigned
to
anyone
for
the
same
reasons
as
youtube
pointed
out
like
who,
I
think
some
of
the
people
creating
issues
don't
know
who
to
assign
them
to
they
assign
them
to
michael.
I
imagine
he's
got
tagged
in
too
many
things
and
then
they
post
on
slack
because
they're
like
I
have
they
have
a
deadline.
They've
got
some
pressure
coming
from
somewhere.
D
So
that's
not
an
answer,
but
it's
an
observation.
So
if
we
say
we're
not
taking
things
from
slack,
we
need
to
stay
on
top
of
our
issue
boards
or
not.
Maybe
not
we,
but
somebody
needs
to
be
accountable
for
that.
E
I
will
try
to
vocalize
my
thoughts
here,
they're
kind
of
going
all.
Sometimes
when
it's
put
in
slack,
you
have
to
fill
out
a
damn
issue
and
then
it
goes
on
the
issue
board
and
then
it
goes
blah
blah
blah
like
it
just
takes
forever,
and
it's
so
much
busy
work
like
what.
If
it's
just
a
little
thing
like.
I
noticed
this
bam,
mr
done
in
10
minutes,
so
efficient
and
clean
up
over
sign
off,
and
I,
if
it's
easy,
I
like
doing
that.
Plus
everyone
can
contribute.
E
We
are
not,
though
everyone
in
the
whole
entire
company
can
make
an
mr
to
dub
dub
dub.
So
if
they
post
something
and
the
website
channel
needs
fixing,
anyone
can
pick
it
up
and
I've
seen
myra's
like
a
perfect
example.
She's
all
over
the
mr
buddies
channel,
all
the
time,
there's
lots
of
other
people.
We
can
rely
on
to
help.
So
I
we
should
have
a
process
like
if
it's
a
big
issue.
E
You
know
like
it's
a
big
thing
yeah,
but
if
it's
a
small
thing-
and
it
feels
good
to
like
help-
people
out
real,
quick
and
then
once
you've
been
around
a
while,
you
know
kind
of
like
the
latter
like
who
the
big
fish
are,
and
if
you
see
someone
from
like.
Oh
that's
an
og
git
lover.
That's
been
here
for
six
years,
pointing
something
out.
E
F
I
strongly
agree
with
barkers
I
added
another
sub
value,
which
is
bias
for
action,
and
I
think
you
know,
I
think,
nate
you
said
responsibilities
of
project
manager
like
absolutely
again
like
but
like
we
don't
have
one
right
and
so
like.
I
think
I
I
think
it's
a
mix.
I
think
the
value
of
like
here's.
C
F
I
don't
think
that
I'm
bullish
on
ai's
capabilities
in
the
future.
I
think
that
ai
will
become
increasingly
advanced
and
useful,
but
I
don't
think
that
it
will
replace
humans
working
together
in
organizations,
because
I
think
that
the
thing
that,
like
that,
the
value
that
we
contribute
to
an
organization
as
humans
is
like
adaptability
right
over
process
and
like
if
there
was
one
process
solved
that
would
fix
all
of
these
things.
Then
someone
would
probably
know
what
it
is
figure
it
out
and
every
company
would
do
it.
F
But
they
can't,
because
that's
like
not
the
nature
of
work
and
like
what
value
is
I
love
process.
I
think
it's
great
and
like
I
have
over
indexed
on
it
myself
in
the
past,
and
I
think
that,
like
having
no
process
is
bad
and
inefficient,
and
if
we
had
no
process
like
we
would
not
have
like
a
clear
trajectory
or
path
forward
right
and
like
we
would
have
nothing
to
fall
back
on.
F
But
like
sometimes
there
are
things
that,
like
don't
need
to
be
shouldn't,
be
or
like
can't
be
in
a
process
right
and
like
the
value
that
you
can
add
and
like
the
reason
that,
like
the
reason
that
we
have
a
team,
the
size
that
we
are
is
so
that,
like
real
human
people
can
read
stuff
and
like
make
judgment,
calls
about
it.
And,
like
you
know,
and
so
I
I
think
it's
just.
F
I
think
that,
like
often
when
I
see
stuff
in
slack,
if
I
see
like
parker
said
like
you
get
a
sense
of
like
like
who's
been
around
for
a
while
like
like
who
you
should
really
listen
to
and
like
perk
up
at
attention,
for.
You
also
get
a
sense
of
like
the
size
of
different
tasks,
and
it's
like
for
big
ones.
Where
you're,
like
it's
probably
gonna,
take
like
two
or
three
weeks
of
like
someone's
time
or
like
multiple
people's
time
like
that
needs
to
get
into
a
process.
F
F
I
I
don't
think
we
should
treat
that
as
a
hard
rule,
though,
like
I
think
that,
like
that
should
be
the
guideline
and
then
sometimes
when
you
see
stuff
in
slack
like
it
makes
sense
to
just
go,
do
it
like
parker
said
like
sometimes
it's
like
this
is
a
10
minute,
mr
and
I'm
gonna
solve
someone's
problem
and
it
won't
get
like
lost
and
they'll
feel
very
grateful
for
us
and
then,
when
we
have
something,
that's
gonna.
Take
someone
not
a
lot
of
time
to
do,
but
it'll
unblock
us
in
a
big
way.
F
A
Yeah
I
agree.
I
I
think
that,
like
asking
people
to
always
create
issues,
especially
for
like
smaller
bugs
is,
is
just
a
heavy
lift
and
not
worth
it
the
amount
of
time.
I
like
I've,
noticed
that
when
I
first
started
kind
of
while
I
was
still
on
boarding-
and
I
was
learning
the
ropes
I
took
on
everything
I
could
find
in
the
is
this
known
channel-
and
I
know
nathan
did
the
same
thing.
A
I
watched
him
like
not
have
any
work
to
do
for
the
first
you
know
month
and
that
channel
was
like
watched
like
he
was
on
top
of
all
the
things
and
now
tyler
in
the
last
day
and
a
half
you
know,
like
you've,
jumped
on
a
couple
of
things
that
I've
seen
the
carousel
thing
and
there
was
a
different
thing
and
a
different
channel.
I've
noticed
you,
you
have
the
time
to
to
do
it,
so
it
is
nice.
A
Just
I
just
don't
know
if
we
should
kind
of
have
an
idea
of
like
who
should
be
doing
who's
got
the
spare
time
to
do
it,
because
I
also
saw
those
things
come
into.
Is
this
known
or
whatever
and
like
you
know,
I'm
like
not
right
now,
I'm
in
the
middle
of
something
else,
you
know
and
it's
great
that
someone
else
joined
it.
F
I
think
there's
also
an
on
paper
solution
to
that
which
is
you
know
if
someone
needs
something
done
like
the
company
is
handbook.
First
and
like
you
can
go
to
google
and,
like
you
can
it's,
this
is
a
unique
company
where
I
can
go
and
ask
like
who
processes
my
reimbursement,
request,
gitlab
in
google
and
get
an
answer
and
a
handbook
page
and
so
like?
I
think
you
know,
I
think
we
shouldn't
feel.
I
think
we
should
never
feel
obligated
to
to
be
tasked
from
slack.
F
So
I
think
that
you
shouldn't
feel
bad
if
things
sit
because
people
do
have
the
ability
and
should
know
that
they
can
google,
you
know
like
if
they've
made
it
to
the
website
channel
or
the
marketing
channel,
then
they
know
we
exist
and
they
could
google
gitlab
handbook
digital
experience,
marketing
website
website
and
they
would
get
to
the
page
that
has
our
process
that
has
a
link
to
our
issue.
I
don't
think
that
they
always
have
to
do
like.
F
I
don't
want
to
ignore
some
someone
if
they
haven't
done
that,
like
it's
fine,
if
you
haven't
but
like
I'm,
not
going
to
feel
bad.
If
I
don't
get
to
your
issue
that
you
like
didn't
google
for
the
steps
to
resolution
for
right,
like
I
think,
that's
the
trade-off
in
the
slide
and
tina
says
in
the
chat
it's
linked
in
the
slack
header
in
our
channel
like
there
are
self-serve
ways
to
do
it.
It's
a
kindness
and
a
good
thing
for
us
to
go
out
of
our
way
and
above
and
beyond,
to
be
good
partners.