►
From YouTube: Digital Experience Retro July 14, 2022
A
It
was
a
little
bit
of
sweet.
I
want
to
thank
everyone
for
being
flexible
and
last
minute
changes,
lack
of
content,
things
that
were
kind
of
out
of
our
control
and
out
of
our
current
control
and
some
things
we'll
be
chat
about
on
things
to
prove
moving
forward.
But
I
just
want
to
thank
everyone
for
keeping
it
keeping
it
together.
D
Yeah,
so
moving
on
to
things
to
improve
on,
I
think
this
is
going
to
be
kind
of
the
topic
of
discussion
today
I
can
already
tell
but
yeah.
I
ended
up
seeing
like
three
roll
back
mars
which,
like
it
happens,
but
there
were
a
lot
of
work
like
some
of
those.
Mrs
were
like
weeks
of
work
and
just
how
do
we
mitigate
that
in
the
future
like?
Is
it
more
stakeholders
or
do
we
just
keep
going
and
if
it
happens,
it
happens?
C
E
Yeah
sure
we've
been
talking
about
this
in
other
meetings
as
well,
just
the
fact
that
we
need
to
figure
out
who
our
stakeholders
are
first
and
foremost,
and
then
beyond
that
we're
also
having
issues
with
our
stakeholders
of
just
confusion
and
miscommunication,
so
having
some
sort
of
kick-off
meeting
where
we
can
all
decide
like
what
our
single
switch.
The
truth
is:
what
are
the
deliverables?
We
need
all
that
good
stuff.
How,
when
are
we
getting
content?
B
I
have
a
next
one,
probably
also
a
topic
of
discussion
with
the
commit
registration
page.
It
was
very
tough
to
work
on
without
content
and
I'm
I'm
thankful.
We
had
kind
of
a
schedule
that
worked
back
when
we
should
expect
content
etc.
There's
some
seems
to
have
been
like
some
deadline.
Pushbacks
and
one
thing
I
noticed-
I
never
noticed
this
before
and
getting
con
content
previously
was
there's
a
lot
of
like
legal
acceptance,
but
with
all
that,
it's
difficult
to
work
on
a
page.
B
I
feel
like
a
few
of
the
boring
solutions
I
thought
were
going
to
be
boring
to
to
kind
of
get
around.
This
ended
up
being
very
complex,
but
I
guess
I'm
wondering
if
you
know
now
that,
like
this
happened
just
looking
back,
what
can
we
do?
Maybe
what
can
we
maybe
work
towards
at
like
a
triage
or
refinement
level?
It
sounds
like
in
the
previous
note,
from
like
nathan
and
jess,
like
these
kickoff
calls,
but
justin
you
want
to
take
your
point.
A
Yeah
I
it's
it's
it'd
be
great,
I
know
like
I'd
say
you
know
we
have
85
of
the
projects
we
work
on.
We
probably
can
push
back
it's
these
it'll,
be
these
weird
ones
that
come
up
and
like
jess
says
down
below
we
knew
like
people
knew
commit
was
coming.
We
need
to
better
communicate
or
work
with
them
to
understand
like
what
things
are
when
they're
coming
and
actually
plan
for
them
better.
What's
hard
with
these
is
like
they're.
These
have
big,
you
know,
sid
level
visibility.
A
So
it's
hard.
We
can't
necessarily
push
back
and
say
we
won't
do
it
until
we
get
content,
it's
still
going
to
happen.
We're
going
to
need
to
make
on
it
make
it
work.
So
it
is
that
you
know
boring
solution,
kind
of
a
thing
that
we
can
work
towards,
but
we
we
like
feel
to
myself
lauren
we
do
need
to
be
better
to
like
either
have
a
cadence
that
we
reach
out
to
these
groups
that
we
know
have
these
larger
things
coming
down
the
pike
and
understand.
E
I'll
just
add
on
to
that.
With
about
the
timelines,
I
feel
like
we
have
a
lot
of
fire
drills
that
don't
necessarily
need
to
be
fire.
Drills,
like
justin
was
saying
like
we
know,
there's
gonna
be
a
commit
next
year
like
we
could
start
planning
for
that
now
and
we
might
not
know
exactly
who
the
speakers
or
the
schedule's
going
to
be,
but,
like
the
larger
bulk
of
it
like,
we
could
have
that
whole
thing
set
up
a
year
in
advance.
E
That's
that
we
have
to
but
like
that
portion
of
it
can
be
done
without
the
final
content,
and
I
feel
like
even
that
part
was
like
missing
and
is
maybe
even
still
missing
to
some
degree.
So
I
think
maybe
we
can
work
with
our
stakeholders
on
like
timelines
and
when
we
should
expect
things
like
well
in
advance.
If
we
can.
C
Yeah,
I
completely
agree
jess,
I
think,
for
the
annual
events
for
sure.
Like
the
survey
too,
it's
like,
we
knew
we
know
it's
coming.
We
should
be
able
to
plan
for
it
in
advance
and
commit
to
so
totally
100
hear
the
frustration
understand
how
difficult
it
is,
and
thank
you
again
for,
like
your
patience
and
like
agility,
to
be
able
to
like
work
through
that.
C
The
other
thing
that
I
just
want
to
add
is
the
content
team
is
like
severely
understaffed,
cormac
left
and
then
I
think,
there's
another
person
that
also
left
recently
so
they're
like
severely
understaffed,
so
they
they're
stretched
incredibly
thin.
So
I
think
we
just
need
to
like,
I
guess,
have
give
them
a
bit
of
space
too
to
kind
of
like
adjust
and
know
where
they're
going
they
we
did
hire
a
new
director
of
content.
C
I
saw
that
they
just
started
recently,
so
hopefully
for
them
having
someone
at
the
director
level,
we
can
kind
of
do
a
bit
more
of
that.
Like
future
planning,
like
just
said
like,
maybe
we
just
plan
out
the
year
in
advance
to
say
like
what
are
the
big
milestones
coming
up
and
then
for
our
own
quarterly
planning.
We
can
also
incorporate
and
absorb
that,
so
we
know
what
to
anticipate,
but
I
think
those
are
also
like
future
solutions.
C
I
don't
think
any
of
these
things
are
gonna
get
solved
immediately
but,
like
justin
said
we're
going
to
try
our
best
to
connect
with
their
stakeholders
as
early
as
possible.
Do
the
kickoff
meetings,
and
hopefully
that'll
alleviate
some
of
it,
but
a
lot
of
it
is
also
that
they
don't
know
what
to
come
to
the
table
with
like
a
lot
of
the
times.
They
don't
know
what
images
or
what
is
required
for
a
website.
So
a
lot
of
that
is
coaching
to
an
rn
to
explain
to
them
what
they
need,
but
yeah.
B
B
F
B
A
It's
pretty
much
related
to
like
the
first
couple
ones,
but
yeah.
We
just
need
to
have
better
communication
with
the
true
stakeholders
and
I
think
that's
where
some
other
issues
have
come
into
play
with
the
release
post.
The
initial
request
kind
of
came
from
someone
else,
but
they
were
not
necessarily
the
true
stakeholder
of
the
page.
It's
finding
that
out
sooner
and
not
jumping
on
to
these
rush
requests
without
doing
a
little
more
research.
And
again
this
really
falls
into
myself.
Lauren
feels
to
do
more
of
the
research
before
we.
E
F
C
Yeah
totally,
I
think
so,
I'm
meeting
with
christina
after
this
actually
to
see
if
there's
other
places
that
she
can
support.
I
think
the
challenge
is
like
a
lot
of
groups
are
honestly
moving,
so
fast
too,
like
the
commit
group
they're,
you
know
obviously
working
towards
this
deadline,
so
they
don't
even
know
what
they
need.
They
just
are
like.
We
need
a
website
and
then
they
kind
of
just
went
off
into
the
abyss,
and
I
think
it's
just
like
pulling
them
back
in
to
be
like
wait
a
sec.
What
do
you
need?
C
Why
do
you
need
it
similar
to
the
release
post
thing
too?
It's
like.
We
need
a
brand
new
release
post
and
then
no
further
communication.
I
think
it's
just
like
a
symptom
of
the
company
growing
so
fast
everyone's
moving
so
fast.
A
lot
of
this,
though,
is
just
we
need
to
give
grace
and
patience
and
also
recognize
like
none
of
this
is
at
the
end
of
the
world.
We
can
do
as
much
as
we
can
do,
and
that's.
C
Okay
and
like
mistakes
will
happen,
changes
will
be
needed,
but
please
don't
take
this
like
to
heart.
If
anything
got
reverted
that
you
worked
on,
it's
truly
like
not
on
you.
This
is
a
collective
team.
It's
a
collective,
get
lab
thing!
It's
not
that
deep.
I
promise
you.
No
one's
upset
no
one's
crying
over
spilled
milk
here,
like
it's
totally
fine,
we'll
work
towards
it.
We'll
get
better
as
time
goes
on,
we'll
get
better.
As
director
of
content
comes
in
the
content
team
gets
fleshed
out,
we'll
we'll
start
working
through
this.
C
But
dennis
to
your
point
like
I
don't
I
don't
know
if
people
will
reach
out
proactively
to
office
hours
or
group
conversations
just
because
I
feel
like
a
lot
of
people
are
in
their
own
like
bubble
or
their
own
world,
but
I'm
hoping
like
with
justice
process
like
we're,
gonna
update
the
handbook
to
say
like
hey,
if
you're
submitting
an
issue
here,
here's
all
the
information
you
need
ahead
of
time.
We
need
to
identify
a
dri.
C
G
C
And
maybe
wouldn't
say:
let
us
fail
because,
like
we
do
want
it
to
be
a
success,
but
I
think
maybe
just
communicate
up
and
out
as
much
as
possible
as
early
as
possible,
like
hey,
I'm
blocked
on
xyz,
documenting
the
issue
and
then
when
we
do
retros
and
when
we
communicate
back
to
other
groups,
we
have
that
feedback
for
them,
because
we
do
want
to
be
good
partners.
We
do
want
to
support
where
we
can.
C
G
C
E
A
C
Lauren-
and
I
were
also
talking
to
another
product
manager-
and
they
have
like
automated
responses,
so
I'll
work
with
lauren
to
get
that
set
up
where
you
just
like
type
in
like
a
word
and
it'll
like
automatically
like
write
out
the
blurb
and
like
a
link
to
the
handbook
so
lauren
and
I
can
get
that
set
up
so
then
anytime,
we
get
any
requests.
It's
like
a
super,
easy
way
to
get
them
to
where
we
need
them
to
be.