►
From YouTube: Digital Experience Retro - July 15, 2021
Description
Sprint 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/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
B
B
B
I
think
that
there's
like
more
work
to
be
done,
but
I
do
think
that,
like
we've
done
a
really
good
job
of
both
like
like
compromising
where
we
needed
to
and
to
like,
go
above
and
beyond
for
people
we
were
working
with
and
then
also
like
advocating
for
the
things
that
we
actually
need.
So
I'm
excited
about
what's
to
come,
even
though,
like
you
know
honestly,
like
we
have
a
lot
of
things
that
are
basically
on
fire
right
now,
because
we
can't
push
code
to
our
primary
repository,
which
is
extremely
bad.
A
C
Yeah,
so
I
had
a
really
positive
meeting
with
william
and
it
kind
of
gave
a
good
sort
of
idea
around
the
back,
the
background
of
like
what
features
is,
and
he
was
very
receptive
to
like
what
we're
doing.
Usually
that
can
be
tricky
to
sort
of
communicate.
What
we
want
to
do
to
somebody
who
maybe
has
a
vested
interest
or
a
history
behind
something
that
we're
touching,
but
it
was
quite
the
opposite.
C
There
was
a
lot
of
good
insights,
definitely
learning
more
about
why
we
have
a
features
page
in
the
state
that
it's
in
you
know,
I'm
not
just
around
the
technical
dependencies
around
the
ammo,
but
also
the
request
where
it
came
from
within
the
organization
and
and
then
even
getting
down
to
the
new
degree
of
like
what
defines
a
feature.
And
so
it's
probably
got
more
trickle
on
to
stuff
that
maybe
can
happen
in
q3.
But
it
was
really
nice
to
kind
of
cross
collaborate
and
not
have
any
kind
of
confusion.
C
D
I
think
I'm
next.
For
me,
what
went
really
well
was
using
user
research
to
work
on
the
comparison
top
to
bottom
page
design.
It
just
like
really
helped
validate
ideas.
Assumptions,
as
just
mentioned,
you
do
learn
something
new.
Some
assumptions
that
I
had
about
the
page
were
totally
not
true.
For
example,
I
thought
the
page
had
too
much
information.
All
the
users
thought
they
needed
all
that
information
and
the
stage
they
were
in
so
had
I
not
done
that.
E
Yeah,
I
just
want
to
shout
out
there's
a
lot
of
cross-functional
planning
around
the
pricing
page
recently,
there's
been
multiple
departments,
all
sorts
of
people
to
make
you
change
the
pricing
page
and
it
started
to
get
a
little
unmanageable
and
then
run
experiments
and
what
experiments
and
when.
So.
We
had
good
conversations
this
week
on
kind
of
how
to
organize
that
and
potentially
create
a
backlog
and
then
pull
them
in
from
there.
So
that
was
really
good
and
thanks
jess
and
michael
for
helping
with
that.
E
B
So
that's
really
bad
and
I
think
everyone
else
is
in
that
state
too.
So
everyone
who's
pushing
code
is
blocked
and
that's
our
team,
but
also
because
the
handbook
isn't
there,
anyone
who's,
updating
the
handbook
or
anyone
who's
working
with
netfly
cms.
It's
really
bad
and
we
have
a
lot
of
like
long.
Oh
we're
getting
500
errors
from
the
rep
from
the
repository
as
well.
Javi
says
in
the
chat.
B
It's
just
really
bad
and
like
there
are
a
ton
of
outstanding
issues
that,
like
people,
have
done
a
lot
of
work
on
like
researching
and
talking
about
like
what
to
do
to
resolve
the
issues
and
they've
never
made
the
priority.
We've
talked
a
little
bit
about
like
things
we
can
do
in
like
limited
scopes.
We
have
a
lot
of
like
buy-in
for
repository
health
day
and
health
week
and
I
think
that's
cool,
but
I
think
the
thing
to
improve
on
here
is
like
I
don't
like.
B
B
If
you
want
to
talk
more
about
those
or
other
things
or
if
other
people
want
to
jump
in
here,
I
just
want
to
like
fly,
get
that
like,
like
it's,
not
sustainable
and
like
we're
at
a
broken
point
and
we're
fortunate
that,
like
the
site,
is
still
up-
and
you
know
it,
the
fallback
on
this
as
a
statically
hosted
site
is
like
it
probably
won't
go
down,
but,
like
probably
I
don't
know,
but
like
we
certainly
right
now.
I
certainly
couldn't
make
an
urgent
change
to
anything
if
something
was
like
flagrantly
wrong.
F
Stop
there
what
I
I
I'm
in
really
strong
disagreement
with
leadership,
stands
of,
don't
fix
it
till
it's
broken,
because
when
it's
broken,
that
comes
right
back
to
the
engineers
to
fix
and
that
doesn't
make
our
team
happy.
It's
not
good
for
employee
satisfaction,
all
the
things.
So
hopefully
we
see
something
change
there.
A
Yeah
I
had
added
on
that.
You
know
it.
It
shouldn't
need
to
break
before
we
we
fix
it,
but
I
I
get
this
kind
of
sense
of
like.
Oh
I'm,
sorry
that
happened
to
you
like.
Oh
I'm,
sorry
that
you're
frustrated
with
the
with
the
repo
and
it's
you
know
I
I
can
go
about
my
day.
I
can
make
my
grilled
cheese
sandwich
and
keep
pushing
up
on
my
terminal
and
trying
to
push
code.
You
know
all
that
you
can
pay
me
to
do
that.
A
You're,
paying
me
a
lot
but
like
this
is
not
good
for
anyone
in
terms
of
day-to-day
work.
But
it's
it's
shocking
that
this
isn't
more
of
an
alarm
bell.
Like
apparently
chad
posted
that
this.
This
comes
up
every
couple
of
months
and
this
is
going
to
continue
to
happen
and
it
doesn't
really
matter
how
many
like
pre-commit
fixes
we
make
or
like
kind
of
little
pieces
we
take
off
like
it's
just
going
to
be
an
ongoing
problem,
because
the
repo
is
so
so
huge.
A
C
Well,
it
will
affect
potential
plans
for
future
improvements
that
we
want
to
perform
as
a
team
in
terms
of
design
and
user
experience
too,
because
if
we
have
things
that
are
prepped
and
ready
for
engineering,
but
you
don't
have
capacity
to
do
that,
because
you
have
to
maintain
a
fractured
website
and
just
make
sure
that
things
don't
break
that
pushes
out
everything
and
then
the
relevancy
of
that
it
can
go
out
of
date
by
the
time
it's
ready
to
roll.
So
there's
it's
it's.
C
It
is
obviously
a
very
core
engineering
issue,
but
it's
actually
a
user
experience
issue
as
well,
because
if
we
haven't
got
designers
or
if
we
haven't
got
developers
to
push
through
experiences,
then
we
just
all
we're
doing
is
designing
figma
files,
we're
not
actually
designing
experiences,
we're
designing
potential
experiences,
but
you
know
someone
could
be
working
on
something
and
then
like
what
tyler
says:
something
breaks,
quick
all
hands
on
deck
and
then
that
design
that
started
gets
put
on
hold.
Okay,
I
better
get
back
on
that
after
it's
fixed.
Oh
that's
going
to
break
it.
B
Speeds:
well,
it's
not
even
the
time
like
there's
like
lit
like
at
this
moment,
there's
like
a
practical,
a
practicality
here
like
I
am
unclear.
If
I
would
be
able
to
merge
the
comparison
infographic,
I
know
that
no
one
would
be
able
to
go
through
and
enter
the
data
that
we
need
to
merge
it.
So,
like
I
don't
know
what
the
resolution
time
frame
is
on
it.
It
sounds
like
there's
like
I
feel
like
it
seems
like
people
think
like
it
will
resolve
in
some
matter
of
time.
B
Maybe
it's
today
or
tomorrow,
but,
like
I
don't
know,
I
don't
have
any
details
on
why
that
is
the
prevailing
opinion
that
we
should
just
wait
it
out.
I
don't
understand,
like
I
haven't
gotten
clarity
on
that.
I
haven't
looked
far
enough
either
but
like
if
this
is
still
the
state
through
the
weekend
and
like
as
of
monday.
B
It's
like
all
of
a
sudden
all
like
I
could
build
the
your
designs
steven,
but
there's
I
couldn't
send
them
anywhere
and
like
I've
got
two
or
three
things
that
live
as
mrs
right
now
or
like.
I
have
one
thing:
that's
fully
locally
on
my
computer
that
I
can't
even
push
up
and
like
if
something
happens
to
my
computer,
I'm
going
to
lose
that
work
too,
like
and
I'd
have
to
redo
it.
So
that's
another
like
we
just
like
we're,
actually
blocked
we're
like
at
a
standstill
for
anything.
B
C
Yeah
and
then
like
we
could
talk
all
day
about
the
knock-on
effect
of
what
that
has
to
like
get
gathering
data
to
understand
how
pages
are
performing
and
how
we
use
that
data
to
inform
some
of
the
directives
that
we
want
to
have
with
whatever
okay
ours.
It
is
you
know,
if
we're.
If
we
can't
whatever
we
can't
measure,
then
we
can't
manage
our
plan
for
so
we're
just
putting
ourselves
at
a
longer
disadvantage
over
time.
C
E
B
Else
has
stuff
on
this,
but
there's
a
lot
of
detailed
issues
and
threads
going
on.
So
I
don't
know
if
we
need
much
more
here.
That's
super
like
way
smaller.
I
just
totally
didn't
realize
there
was
a
family
and
friends
day.
This
week
I
managed
to
like
finish
the
stuff
that
I
had
intended
to
use
to
do
on
friday,
I'm
like
stoked
on
that
but
like,
and
it's
not
major
like
this
isn't
like
I
just
like.
I
need
to
look
ahead
more.
I
thought
that
I
had.
B
I
like
usually
look
like
on
mondays
for
planning.
I
like
look
at
or
usually
on
like
fridays.
I
like
going
to
the
planning
dock.
I
add
my
stuff
for
the
planning
doc.
I
go
check
the
calendar
to
look
for
like
days
off
and
stuff,
and
I
did
that
process,
but
then
I
didn't
see
the
family
and
friends
day
until
like
tuesday
of
this
week
or
something,
and
so
it
wasn't
huge.
B
I
love
the
family
and
friends
day,
but
I
just
like
I
know
in
terms
of
things
to
improve,
like
I
need
to
get
better
at
like
there's
a
handbook
page
that
lists
them.
So
I
think
I
just
need
to
include
that
in
my
rotation
of
hey,
look
at
the
calendar,
look
for
the
holidays
and
also
look
at
the
handbook
page,
but
I
don't
know
maybe
which
I'd
maybe
I'll
ask
someone
if
they
can
like
put
it
on
the
company
calendar
or
something,
because
that
would
be
super
useful.
A
A
A
A
Sorry,
I
was,
I
was
just
looking
it
up
in
the
repo
to
see
when
it
was
edited
when
the
16th
was
added,
so
it
was
two
weeks
ago
it
was
added
to
the
handbook
page
on
the
16th,
so
that
sounds
like
that's.
When
it
was
decided,
which
is
short
notice,
I
think,
like
I
think,
that's
shorter
notice
than
a
lot
of
the
ones
that
we've
had.
I'm
sorry,
I
think
we're
not
all
like
imagining.
D
F
B
Take
it
away
yeah,
but
don't
take
it
away
yeah,
I
don't
want
it.
I
just
I
feel
bad
because
I
like
sometimes
I
make
commitments.
I'm
like
I'll
use
this
friday
to
like
deliver
on
my
commitment
and
then
I
don't
have
it
and
like
I
will
take
the
day
off,
because
I
appreciate
it
and
I
value
that
and
that's
like
the
correct
thing
to
do,
but
then
I
have
to
like
adjust
my
which
I
think
people
are
understanding
it.
I
just
like.
I
feel
bad
readjusting
my
commitment,
this
late
in
the
game.