►
From YouTube: Digital Experience Retro - June 30, 2022
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
meeting,
we'll
we'll
go
over
what
went
well
and
some
things
to
improve
on
from
this
last
two
week:
iteration.
It
is
thursday
june
30th.
First
up
for
things
that
went
well
tina.
B
Thanks,
I
might
be
just
speaking
for
myself,
but
for
me
and
my
group
collaboration
is
working
really
good.
I'm
able
to
focus
I'm
experiencing
way
less
context
shifting
and
I
feel
like
I'm
building
or
at
least
we're
building
good
relationships
with
the
two
teams
that
we're
for
now
directly
in
contact
with
the
s8,
oh
team
and
the
product
marketing
team
nathan
is
doing
a
plus
one,
don't
know
if
you
want
to
vocalize
no.
D
Yay
for
hannah
yeah,
I
think
our
group's
in
a
really
good
flow
with
the
new
teams
and
the
the
sprint
cycles
we're
we're
shipping
work
and
yeah
we're
doing
really
good
tina.
B
D
Oh
shoot.
That's
me
again.
I
wanted
to
get
some
clarity
on
our
strategy
for
the
topics,
solutions
and
category
leadership
pages.
Are
they
all
going
to
resolve
to
the
same
url
structure?
What
is
that?
Because
we're
getting
so,
we
can
be
unified
and
our
communications
out
because
they
keep
coming
in.
D
E
Yeah,
but
just
going
to
concur
that
when
whatever
we
do
decide,
we
should
also
make
sure
we
change
your
naming
across
the
board,
so
we're
not
confusing
people
if
it's
solutions
or
topics
or
content
leadership
whatever
it
is.
It's
just
make
sure
that
we
all
us
as
well
as
externally,
know
like
what
we're
talking
about.
F
B
I
don't
have
an
answer,
but
I
think
we
need
to
realign
on
the
category
leadership
topic
pages
with
somebody
from
like
niall
probably-
and
maybe
I
I
put
your
name
there-
michael,
maybe
also
I
thought
about
maybe
getting
you
involved,
because
I
think
there's
a
lot
of
confusion
with
all
three
of
those
sections.
So
we
can
maybe
deal
with
that
later.
Yeah.
D
All
right,
we
got
an
action
item
to
discuss
that
I'm
gonna
move
to
the
second
one,
I'm
seeing
a
lot
of
merge.
Quests
come
through
that
are
still
in
draft
mode,
and
then
they
don't
have
any
description
and
I'm
like
well.
What
is
this
so
tyler?
I
hear
so.
You
got
the
first.
H
Yeah,
I
think
the
the
first
thing
that
comes
to
mind
is
like
I
I
would
get.
We
have
a
lot
of
folks
who
are
still
new
to
the
team
right.
It's
easy
to
forget
that,
because
every
time
so
oh
my
screen
and
my
camera
is
the
worst
anyways
every
time
someone
joins
the
team.
H
The
person
who
most
recently
joined
before
them
stops
feeling
like
they're
a
fresh
face
and
so
like,
as
we
keep
on
adding
people
like,
I
feel
like
we're,
like
oh
yeah,
we've
all
been
here
forever,
but
I
think
a
lot
of
folks
are
still
basically
like
in
I'm
going
to
take
off
this
blur
and
see.
If
that
helps,
because
I
know
it's
distracting,
nope
didn't
help.
Now
it's
just
now
anyways.
H
I
I
think
one
to
be
clear,
like
I
think
a
lot
of
folks
are
still
getting
used
to
processes
and
processes
have
changed,
and
so,
like
you
know,
we
should
be
patient
as
people
like
get
up
to
speed
on
those
communication
practices
two,
I
don't
care
one
way
or
another
about
being
added
as
a
reviewer
in
draft
mode
or
not,
but
three-
and
this
is
the
most
important
thing
there
is
a
handbook
page
about
low
context,
communication
and
the
takeaway
is
because
of
the
remote
nature
of
the
work
that
we
do.
H
One
of
the
best
ways
to
communicate
with
people,
especially
using
the
gitlab
tool,
is
whenever
you
might
be
communicating
with
someone
I
either
because
they
got
a
notification
from
you
or
you've
like
tagged
them
in
something
you
should
assume.
They
know
absolutely
nothing
about
what's
going
on
and
you
should
provide
the
context
and
so
something
that
I
really
like
to
do
when
I
like
ask
for
reviews
or
that
I
like
to
see
what
I've
been
requested
for
a
review.
H
Is
I
like
to
like
tag
the
person
directly,
even
if
you've
like
added
them,
as
the
reviewer
like
sometimes
just
the
ping,
is
like
more
visible
and
say
hey
that
person?
I've
asked
for
a
review
on
this.
This,
mr,
is
in
draft
and
here's
why
here's?
What
I'm
looking
for
from
you
or
this
draft
is,
as
far
as
I
know,
good,
to
go.
H
I've
like
run
it
by
these
people
or
I
have
yet
to
run
it
by
these
people,
et
cetera,
et
cetera,
give
them
the
context,
because,
even
if
they
have
heard
a
little
bit
about
it
or
even
if
they
did
know
this
was
coming.
They
maybe
like
forgot.
H
It's
been
a
couple
days,
or
it's
also
just
really
good
to
document
for
like
the
future
right
six
months
later,
when
everyone
has
forgotten
what
happened
with
that
merge
request,
it
will
be
really
useful
to
be
able
to
look
back
and
see
who
asked
for
what
and
why.
So
all
that
to
say
give
the
handbook
page
a
read.
H
Let's
start,
let's
try
and
provide
more
context
with
all
of
the
things
that
we
are
doing
in
the
gitlab
tool,
and
I
would
I
would
certainly
agree
with
lauren
of
like
don't
ask
for
review
unless
stuff
is
ready
or
if
you
need
like
something
early
reviewed
for
like
or
if
you
want
to
say
like
hey,
can
we
talk
about
this
here's
the
code
like
that's
useful,
too,
but
review
to
when
I
see
reviewer.
I
usually
assume
that
someone
wants
me
to
review
and
merge
and
it's
confusing
if
it's
still
in
draft
mode.
D
Yeah
really
good
points,
I'm
totally
in
line
with
the
providing
context,
yeah
that
will
help
immensely
and
then
filling
out
that
mr
description
adds.
You
know
additional
context,
because
once
you
link
back
out
to
the
issue,
then
you
you
go
into
gitlab,
never
never
land
and
you
gotta
get
back
there.
I
added
another
point
like
we
have
a
handbook
page
specifically
in
like
in
our
handbook
for
merge
requests,
reviewed,
merge
quest.
I
Are
we
good
on
that
one?
I
can
vocalize
on
behalf
of
jess,
okay,
sweet,
so
yeah
just
left
a
comment
and
had
some
feedback
around
when
we
get
requests
from
other,
like
departments
or
teams.
We
just
need
to
be
very
conscientious
of
who
is
making
the
ask
and
who
actually
owns
that
page.
I
I
B
Oh
sure,
I
just
wanted
to
add
to
that
that
as
an
assignee,
really,
in
my
opinion,
shouldn't
be
up
to
them
to
dig
around
for
stakeholder
information.
I
think
the
author
should
be
responsible
for
that,
because
that
information
can
be
hard
to
find.
B
B
E
E
E
I
I
J
Yeah
just
focus
vocalizing
the
next
point
solution
page
that
was
gonna,
be
deprecated,
but
then
taking
the
seo
scoring
into
consideration.
I
think
we're
not
gonna
do
that
anymore.
J
So
I
was
just
wondering
like:
is
there
a
procedure
and
it
looks
like
yes,
web
traffic,
but
also
include
seo
scoring,
and
then
I
saw
earlier
in
slack
brian
may
had
brought
up
some
points
about
another
page.
So
I
don't
know
if
we
want
to
talk
through
that.
G
I
think
the
point
I'd
like
to
add
is
it's
expected.
I
think
this
is
okay,
like
it's
like
when
you
have
right
now,
my
I
have
to
renew
my
nexus.
It's
been
expired
for
eight
months
and
like
I'm,
not
gonna,
renew
it
until
I'm
gonna
take
a
trip.
I
should
just
renew
it
now.
It'll
save
me
time
later,
but
similar
to
insurance,
you're
you're,
never
happy
with
like
paying
it
until
you
need
it.
G
So
I
think
this
is
just
like
one
of
those
where
we
just
we've
been
communicating
for
a
couple
quarters
that
we're
going
to
do
this
and
now
we're
doing
this
and
it's
becoming
the
top
of
mind
for
people,
so
I
think,
just
being
kind
and
kind
of
hospitable,
overly
communicative,
reminding
or
pointing
people
that
hey
we've
been
working
on.
This
apologies
that
example
dennis
here
we're
just
talking
about
brian.
H
Yeah,
like
it's,
it's
not
bad
to
have
people
flag
that
stuff
right
like
that
is
not
a.
That
is
not
a
reason
not
to
do
the
work
and
like
if
we
remember
the
reason
we're
doing.
H
The
work
is
to
like
dramatically
simplify
the
information
architecture
and
like
like
those
folks
like
people
who
come
and
and
ask
us
to
do
something
differently
like
likely,
have
different
sets
of
objectives,
they're
working
on
right
in
front
of
them
right
than
we
do,
and
so
I
think
it's
just
like
we
figure
out
like
which
objective
is
like
you
know
the
the
priority,
and
where
can
we
meet
their
objectives
and
like?
And
where
can
we
meet
both
by
taking
a
different
course
of
action?
H
But
like
michael,
like
one
of
the
reasons
that
we're
where
we
are
with
thousands
of
pages
that
get
under
10
views
right
is
like
because
we
don't
like
rip
off
the
band-aid
and
also
like
we
can
revert
in
mr
pretty
fast
like
that's
the
other
like
this
stuff
is
like
for,
like
all
things
considered,
even
the
longer
pipelines,
the
20
to
30
minute
pipelines
like
to
undo
a
change
like
that.
Like
is
that
is
not
a
huge
cost
to
say
like
I'll
just
revert
the
mr.
We
wait
30
minutes
and
you're
fixed
right.
H
D
I'll
just
bring
bring
me
attention.
Hanif
has
this
great
issue,
but
I
refreshed
appreciating
pages
and
it
goes
through
some
of
their
approach
that
they're
using
data
back
up
this
stuff,
so
phase
one
so
removing
all
this
stuff
and
not
doing
any
back
links
and
then
face
boards
like
the
mat
or
three
twos
manual
review
phase:
three,
we'll
we'll
do
the
redirects
for
those
pages
great
issue
to
refer
people
to.
A
I'm
done
yeah,
I
don't
know
where
we
are,
but
I
I
posted
that
you
know
I've.
I've
seen
just
our
search
enough
support
team
has
deleted
at
least
30
pages
this
last
sprint
and
I've
seen
two
people
kind
of
come
back
and
say
hey.
I
want
my
pages
back.
One
of
them
just
happened
today,
right
the
one
that
brian
brought
up,
so
those
aren't
too
bad
odds.
You
know
like
we're
still
taking
out
a
lot
of
the
the
really
old
kind
of
taking
of
the
trash.
A
I
hate
to
say
that,
but
you
know
like
we're
getting
rid
of
a
lot
of
stuff
and
doing
a
lot
of
good
work
and
yeah
like
tyler
said
it's
pretty
easy
to
revert.
I've
also
been
trying
to
encourage
people
who
want
their
pages
back
to
ask.
If
that
could
be
a
handbook
item,
you
know.
Can
this
information
that's
on
this
page
be
moved
to
the
handbook
instead
of
like?
Is
it
performing
a
marketing
function,
which
is
a
good
thing
to
ask
the
people
who
who
fight
for
those
pages.
E
Yeah
I
was
just
going
to
build
on
michael's,
like
to
kind
of
like
go
back
to
jeff's
point
above,
but
just
with
a
release
post
back
and
forth,
we've
been
having
like
there's,
been
a
lot
of
good
conversation
going
on
there
about
with
that
team
and
like
features
that
they
have
wanted
for
some
time
now,
but
just
never
did
and
now
there's
more
of
an
impetus
like
made
the
change
they
saw.
There
was
changes.
G
And
make
new
relationships
like
this,
the
reality
of
working
remotely,
like
brian,
like
I
think
I
had
a
conversation
with
him
a
year
ago,
but
I
didn't
remember
him
and
then
he
popped
up
and
was
like
oh
yeah.
So
it's
it's
kind
of
a
good
way
for
I'm
sure
they're
the
same,
they
don't
know
we're
out
there.
We
don't
know
they're
up
there.
So
all
positives.
A
Any
last
thoughts
before
I
stop
the
recording,
I
think
we've
got
some
to
do
items
in
there.
Thank
you,
everyone,
and
we
will
see
you
next
time.