►
From YouTube: UX Showcase: Plan::Project Management (2021-03-17)
Description
Holly shares her experience facilitating the 1-year vision exercise with her team.
A
So
my
name
is
holly
reynolds
senior
product
designer
here
at
get
lab
for
the
plan
team
and
the
project
management
group.
Actually
I'm
going
to
share
my
screen.
I
don't
have
slides
today
make
sure
that
I
can
get
to
the
yes
there
we
go.
I
don't
have
slides
today,
just
wanted
to
share
an
activity
that
I
had
worked
on
recently
that
I
found
to
be
really
useful.
A
So
I
talked
with
my
manager
and
my
pm
and
decided
it
would
be
useful
to
do
a
vision,
map
and
mapping
session,
but
for
just
a
year
anything
longer
than
that
felt
a
little
too
nebulous
and
a
little
too
hard
to
kind
of
really
properly
define
and
plan
for
a
couple
of
other
groups
have
done
similar
activities
to
this.
So
I
reviewed
some
of
the
mural
boards
on
the
topic
that
existed
and
created
my
own
variation
from
one
that
I
believe
nick
post
had
created.
A
So
if
that
was
the
case,
thank
you
so
much
much
nick.
If
some
of
this
looks
kind
of
familiar
and
then
schedule
the
synchronous
call
with
my
pm
gabe,
we
initially
discussed
how
we
should
think
about
project
management
within
get
lab.
So
I'm
going
to
pause
here
and
go
to
the
issue
we
there
is
an
issue
for
it.
I
did
it
a
little
bit
backwards
in
that
we
started
on
the
discussion
and
on
the
mural
before
creating
the
issue,
and
then
I
went
back
and
created
the
issue.
A
If
you
do
want
to
go
back
and
watch
any
of
the
sessions
that
we
did
for
this,
they
are
all
listed
here
in
the
issue.
They
are
all
private
because
we
mentioned
customers
here
and
there
so
you'll
need
to
be
logged
into
the
respective
account
on
youtube
to
see
it,
but
you
can
also
get
to
the
mural
board
here.
If
you
want
to
see
some
of
that,
and
of
course
please,
let
me
know
if
you
have
any
feedback
or
thoughts
on
it
if
you
do
go
to
visit
it.
A
So
this
is
the
map
at
a
high
level,
I'm
going
to
just
kind
of
zoom
in
on
a
couple
of
specific
pieces.
This
is
the
question
we
started
out
with,
which
was
how
should
we
think
about
project
management
within
git
lab?
This
was
a
bit
of
a
stakeholder
interview
to
help
me
better
understand
his
vision
and
perspective
on
our
group.
A
A
So
I
feel
at
times
I'm
also
impacted
or
potential
persona
impacted
by
some
of
our
product
management
use
cases
and
having
this
discussion
was
really
helpful
for
us
to
kind
of
talk
through
and
identify
some
of
our
own
biases
align
on
core
pain
points.
One
in
particular
that
we
continue
to
hear
over
and
over
and
plan
is
that
our
users
feel
that
gitlab
is
geared
more
toward
a
highly
technical
audience,
rather
than
maybe
less
tech
savvy
users.
So
that's
something
in
product
management
in
particular
that
we're
always
aware
of
and
striving
to
improve
on.
A
A
I
also
added
in,
of
course,
some
of
my
own
interests
such
as
ux,
okrs
and
design
refinements
work.
There
was
no
real
reason
for
the
three
to
six
month
timeline
that
was
just
kind
of
a
time
that
felt
like
enough
time
for
us
to
have
the
ability
to
think
kind
of
longer
term.
Without
losing
sight
did
I
freeze
still
good
okay.
I
got
the
message
that
my
internet
pros
for
a
moment
so
no
particular
reason
for
that
particular
timeline.
A
Just
again,
it
felt
like
long
enough
for
us
to
think
a
little
bit
bigger
without
losing
sight
of
what
we
could
be
doing
now
to
work
toward
those
goals
and
then,
of
course,
we
had
the
sort
of
longer
vision,
which
is
where
we
maybe
want
to
go.
Eventually.
We
were
striving
for
end
of
the
year
and
not
really
beyond
that,
but
that
was
an
option
if
we
needed
to
do
that.
A
Lastly,
I
went
through
all
of
the
sus
feedback.
I
read
every
single
piece
of
user
feedback
regarding
plan
and
documented
the
key
ones
on
stickies,
which
we
reviewed
together.
This
was
extremely
helpful
in
providing
some
validation
surrounding
the
proposed
vision
and
timelines,
as
well
as
helped
us
both
to
kind
of
surface
some
additional
concerns
and
questions.
So
again,
you
can
see
all
of
this
here.
Of
course,
we
went
through
and
grouped
those
items
and
have
them
all
listed
here,
just
as
reference
as
we
went
through
this
process.
A
That
went
so
well
that
we
had
a
third
and
final
conversation
synchronously,
at
least
in
each
of
these
we
moved
items
around
we
removed
questions
that
we
had
or
would
have,
that
would
have
become
rather
blockers
and
aligned
on
larger
visions,
and
that's
what
I
would
say
the
primary
benefit
of
this
was
for
me.
It
was
just
to
get
everyone
in
alignment
on
the
vision,
get
those
questions
answered
that
helped
us
to
better
plan
and
prioritize
our
work,
as
well
as
to
identify
dependencies
between
work.
A
So
there
were
things
that
I
didn't
realize
certain
pieces
of
this
larger
vision
that
were
dependent
on
one
another,
and
those
were
questions
that
it
was
just
really
helpful
to
have
the
engineers
there
to
just
quickly
say.
Well,
we
really
can't
do
this
until
we
can
complete
that,
but
we
could
move
this
and
you
know
so.
We
were
able
to
have
those
conversations
which
do
happen
asynchronously
as
well,
but
it
was.
A
It
was
done
very
quickly
to
be
honest
in
this
sync
session,
and
you
know
we
were
all
again
in
the
same
vision
map.
So
we
could
see
everything
at
once
and
kind
of
have
that
larger
visual
in
front
of
us
that
kind
of
plotted
everything
out
in
one
place,
rather
than
trying
to
kind
of
think
through
all
of
the
different
pieces
of
the
puzzle
and
how
everything
needed
to
fit
together
to
complete
the
overarching
vision
for
the
year.
A
So
for
next
steps,
we
are
looking
to
locate
and
document
all
of
the
relevant
epics
and
issues
for
each
higher
initiative
into
a
single
issue,
which
will
be
this
one
here
likely
just
so.
We
have
understanding
as
to
what's
associated
with
what
and
then
go
back
and
revisit
the
list
in
a
few
months
to
kind
of
examine
how
things
have
changed
if
they've
changed
and
maybe
talk
through.
Why?
But
I
did
receive
great
feedback
from
some
of
the
other
people
that
attended
the
session,
that
it
was
extremely
helpful
for
them
as
well.
A
So
I
think
that
again,
the
final
benefit
for
everyone
was
just
alignment
on
vision
and
understanding
of
priority
and-
and
you
know
why
we
might
need
to
do
something
after
something
else,
just
getting
clarity
on
those
kinds
of
things.
That's
really
all
that
I
had
for
this
particular
session.
So
I
don't
know.
Are
we
taking
questions
now?
Are
we
doing
questions
async.
B
B
C
Yeah
sure
so
my
question
for
you
holly,
is
with
these
like
visionary
issues.
One
thing
I've
struggled
with
is
like
keeping
them
lightweight,
so
they
don't
become
this
heavy
artifact.
That
has
to
be
like
manually,
updated
all
the
time.
Do
you
have
any
strategies
that
have
worked
well
for
you
or
you
think
you'll
be
doing
you
mentioned
like
going
back
and
visiting
it
every
couple
of
months.
I
found
this
a
challenge.
I
come
back
three
months
later
and
I'm
like.
C
A
So
I
think
that's
a
great
question
and,
to
be
honest,
I'm
I'm
still
kind
of
doing
this
for
the
first
time
this
particular
type
of
activity
and
we
kind
of
leading
it
for
the
first
time.
So
I
haven't
really
encountered
that
type
of
challenge
yet,
but
it
makes
perfect
sense
that
it
would
be
something
that
would
be
a
challenge
to
sort
of
maintain
over
time.
A
I
think
I
would
want
to
understand
the
benefit
of
going
back
in
a
few
months
and
revisiting
it.
I
have
a
theory
that
it's
valuable,
but
we
haven't
done
that
yet
so
it
could
be
that
we
get
back
to
it
into
your
point.
Everything
is
different
and
we
realize
we
need
to
just
do
something
else
altogether.
So
in
that
case
it
might
not
be
valuable
to
maintain
it.
A
It
might
be
valuable
to
look
at
doing
something
different,
but
I
do
like
the
thought
at
least,
and
I'm
hoping
that
if
we
were
to
go
back
in
a
few
months,
not
that
much
would
have
changed
that
we
would
still
have
a
bit
of
a
baseline
in
place
and
that
we
could
just
evaluate
any.
You
know,
adjustments
that
may
have
occurred,
but
I
don't
know
it
could
be
that
everything's
wildly
different
and
the
whole
thing
is,
is
kind
of
purposeless.
At
that
point,
if
you
have
any
suggestions,
I
would
love
to
hear
them.