►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Cool
okay,
Alexis
here
so
I'm
the
designer
on
product
planning
within
plan.
Hopefully
you
all
know,
but
just
to
reintroduce
myself
so
I'm
just
going
to
quickly
go
over
some
of
the
work
we
were
doing
on
the
product
planning,
ux
workshop
ux
roadmap
Workshop,
and
this
is
very,
very
work
in
progress,
so
kind
of
high
level
talking
about
some
of
my
process
going
through
this
and
just
like
thoughts
as
I'm
still
documenting
a
lot
of
this
work.
So,
first
of
all,
what
is
this?
A
A
Being
you
know
bringing
some
of
this
user
focus
into
the
the
roadmap
or
the
product
robot
as
well,
so
within
this
Workshop
I
think
it
was
an
hour
and
a
half
or
two
hours
with
my
new
PM
who
is
now
onboarding
and
my
old
interim
PM,
not
old.
Just
you
know,
past
PM,
we
went
through
this
mural
board,
the
Andy
and
Justin
set
up
for
us
just
really
high
level.
A
We
kind
of
thought
of
like
our
goals,
what
our
ideal
States
would
be,
and
then
we
pulled
in
issues
from
basically
our
backlog
that
were
Direction
items
in
our
kind
of
our
category
of
maturity,
ethics
and
put
these
on
this
board
and
then
clustered
them
did
some
kind
of
affinity,
mapping.
Thinking
of
the
high
level
themes
of
all
these
groupings
and,
like
I,
said
this
is
all
very
work
in
progress,
so
we
just
really
high
level
bucketed
each
of
these
and
talked
through
it
and
I
think
this
was
really
valuable.
A
A
What
are
the
strategies
behind
each
of
these
and
then
I
went
through
and
kind
of
did
little
mini
groupings
as
well
here,
but
this
is
what
we
worked
on
together
and
thinking
about
how
these
tied
back
to
our
jobs
to
be
done
as
well,
and
then
we
pulled
these
into
kind
of
a
refinement
of
thinking
of
these
themes
from
more
of
a
business
perspective.
So
one
of
the
business
objectives
of
these.
This
is
what
I
still
need
to
work
on
with
my
PM,
like
I,
said,
it's
really
timely.
A
She
is
ramping
up
on
product
planning,
so
it's
been
I
think
a
really
great
experience
working
through
this
with
her
thinking
of
these
objectives
from
her
perspective,
as
well
and
kind
of
refining
these
and
almost
like
resetting,
not
resetting
but,
like
you
know,
level
setting
some
of
our
goals
as
a
team.
So
we're
going
to
go
through
this
thinking
about
the
confidence
we
have
in
the
scene
from
a
ux
perspective
like
has
it
been
researched?
Do
we
have
thoughts
there?
Is
it
really
important
to
the
users?
A
Are
we
confident
there
and
then
thinking
like
I
said
what
are
the
business
objectives
like
you
know,
do
we
want
to
increase
share
of
market
like
how
do
we
measure
success
of
this
from
a
business
perspective
and
then
plotting
these
out?
I
guess
by
Milestone
is
the
way
we
would
think
about
it.
But,
like
you
know,
ranking
these
in
parity,
we
have
these
buckets
of
kind
of
quarter
right
like
next
couple
milestones
and
then
maybe
ones
that
we
weren't
really
sure
about.
Yet
we
don't
need
to
prioritize
at
this
moment.
A
A
This
was
the
workshop
we
got
probably
here
and
we
have
like
I
said
work
in
progress.
We
have
more
to
do
I'm
going
to
work
on
this
with
my
pm
and
then
I
want
to
pull
the
rest
of
the
human
as
well
just
my
thoughts
on
this.
So
we
got
here.
We
were
synthesizing
now
I
need
to
create.
Also
once
we've
you
know,
really
solidified.
These
themes
I
need
to
create
some
issues
around
it.
For
me,
it's
always
easier.
A
Sometimes
since
I'm
creating
many
issues,
just
you
know
create
an
Excel,
Doc
and
then
upload
it
in
so
here
Andy
had
a
ux
team
template,
so
I
just
pasted
that
into
each
cell
and
again
this
is
really
work
in
progress.
So
I'll
just
talk
about
it
really
high
level,
but
for
me,
I
was
creating
these.
These
themes
so
creating
ux
theme,
issues
and
I
think
the
goal
is
to
then
pull
all
these
ux
themes
into
one
shared
board
and
really
understand
where
our
work
overlaps.
A
You
know
across
stages
and
maybe
any
dependencies
anything
we
can
help
each
other
with
I.
Think
that's
great
some
things,
I'm
thinking
about
and
I
want
to
talk
through
it
with
my
PM
as
well.
It's
like
what
is
the
best
way
to
document
this.
We
have
what
we're
thinking
now,
which
is
you
know,
put
this
on
a
shared
board.
A
Some
of
the
things
I'm
thinking
about
here,
though,
is
keeping
these
items
up
to
date.
So,
for
example,
I'm
sorry
that
I'm
pulling
up
Gina.
This
is
a
great
documentation
here,
but
within
each
issue
we
have
kind
of
like
a
mini,
almost
like
a
kanban
board
itself
like
we
have
the
way
the
status
something
I'm
thinking
about
is.
A
A
A
A
So
that's
something
I'm
playing
with
and
like
I
said,
work
in
progress,
I'm
kind
of
going
to
work
through
some
of
these
questions
and
ideas.
I
have
with
my
pm,
but
I
also
want
to
make
sure
I'm
consistent
and
pulling
this
into
the
shared
board
with
the
team.
So
we
can
play
around
with
this
this
pilot
first,
because
I
think
this
is
an
amazing
idea,
but
that's
just
some
things
I'm
working
on
and
then
also
you
know
level
setting
with
my
pm
on
some
of
the
questions.
A
Things
like
that.
So
it's
cool
for
me.
Thinking
about
this!
It's
very
meta!
It's
like
stuff!
My
team
wants
to
work
on
in
general
anyway,
but
yeah
high
level.
Some
things
I'm
thinking
about,
like
I,
said
still
work
in
progress
where
I
get.
But
overall,
this
is
a
really
fun
workshop
and
I'm
I
really
appreciated
being
able
to
work
on
this,
especially
with
my
PM,
who
is
onboarding
and
it's.
A
B
Okay,
yeah
I
I
had
one
because
I
saw
that
you
had
a
ton
of
stickies
a
ton
of
issues
to
deal
with
like
in
the
beginning
when
bundling
bundling
the
themes
together.
I
was
wondering
you
kind
of
already
spoke
to
this,
but
I
was
wondering
how
that
impacted,
how
you
went
about
creating
the
themes,
because
I
I
think
the
goal
is
that
the
theme
would
be
taken
on
in
a
single
like
Milestone
set.
So
yeah
I
just
wanted
to
learn
more
about
how
you
went
about
that.
B
A
Yeah
good
question
I'll
share
my
screen
again
so,
for
example,
yeah,
like
I,
said
I'm
still
work
in
progress
Amanda.
My
newer
pm
and
I
are
gonna.
Keep
working
on
this
and
I
think,
based
on
the
documentation
that
Justin
and
Andy
created
and
some
of
the
information
around
road
maps,
we
might
have
to
break
some
of
these
down
right
for
now.
A
These
are
just
the
large
themes
and
then
I,
we
kind
of
went
through
I
think
created
smaller
buckets,
Within
These,
like
maybe
sub
themes
or
just
different
ways
to
group
these,
so
they
might
have
to
be
broken
apart
because
we,
you
know,
like
you
said,
we
want
to
keep
it
to
a
smaller
time
box
and
then
kind
of
ranking
these
themselves
as
well.
So
it
might
just
be
more
themes
or
sub
themes
within
the
theme
that
we
then
prioritize.
If
that
makes
sense,
does
that
answer
your
question?
Yes,.
B
A
Yeah,
the
the
sub
groupings
have
been
helpful
for
me.
Tactically,
we'll
see
right
what
happens
there,
that
like
grouping
that
in
ways
that
makes
sense,
has
been
good
and
that's
how
I
think,
like
let's
say,
I
was
going
to
put
all
this
work
in
an
epic.
That's
probably
how
I
do
it
like
what
work
within
this
larger
theme
of
work
would
I
work
on
together?
How
would
that
make
sense
to
deliver
value
and
honestly
going
through
this?
A
Another
thing
I
didn't
talk
about
was
this
has
been
really
helpful
in
refining
issues
as
well,
because
we
just
have
so
many
issues
so
going
through
all
these
making
sure
everything's
captured
in
this
mural
board.
I
went
through
like
a
million
issues
and
some
were
like,
oh
that
a
day
I
closed
Consolidated
move.
So
that's
been
helpful
too.
You
might
you
might
notice
that,
as
you
work
through
this.
C
Alexis
I
had
some
advice
on
tracking
and
keeping
things
up
to
date.
Don't
try
it
you'll,
spend
more
time
doing
that
than
you
will
doing
the
design
right
so
linked
to
an
example
in
like
a
weird
figma
file
and
I
kind
of
keep
on
how
this
process
should
go,
but
to
explain
it
better.
If
you
could
share
your
screen
again
and
go
back
to
that
design
management
theme,
it
can
kind
of
explain
what
we
were
getting
at
is.
C
If
you
see
here
on
the
left,
where
it
says,
manage
discussion,
visibility,
there's
an
issue
that
says,
convert
a
regular
comment
to
an
internal
note,
but
up
and
to
the
right,
you
say,
add
context
to
or
discuss
designs
like
if
we
were
going
to
design
these.
We
should
be
designing
these
things
contextually
at
the
same
time
for
the
span,
so
that
all
of
these
stickies
here
are
really
just
requirements
for
you
to
keep
in
mind
as
you're
evolving.
C
The
collaboration
of
designs
workflow,
because
the
the
nvcs
that
were
broken
down
were
broken
down
prior
to
us
actually
doing
any
of
the
work
right.
So
we've
already
kind
of
broken
our
design
process.
Prior
to
even
started
so
we're
designing
in
these
small
small
silos
and
microscopic
views
of
these
features
not
really
understanding
the
pure
connection
between
them.
So
by
breaking
down
those
like
microscopic
silos
that
we
created
within
our
silos
and
our
silos,
then
we
can
see.
C
So
you
know
an
example
showed
design
discussions
and
comments
view,
but
then
you
have
another
one
talking
about
converting
comments
into
an
internal
note.
Those
things
are
probably
going
to
be
happening
near
to
the
experience
in
which
you'd
want
to
be
designing
site.
So
we're
just
saying
the
intent
is
to
design
these
things
at
once.
If
it's
really
big,
then
chunking
it
down
makes
sense,
but
chunking
it
down
into
an
MVC
before
we
start
designing,
puts
us
into
a
tough
spot.
A
I
think
that
makes
sense,
I
think
what
I
meant
by
keeping
up
to
date
was
items
like
this
I.
Think
personally,
I
find
it
difficult
to
manage,
like
like
tables
like
this.
For
me
personally,
things
get
out
of
date
really
quickly
because
I
just
create
tons
of
documentation.
It's
a
personal
problem,
but.
D
A
C
Mean
engineering
has
their
own
way
of
tracking
right
and
I.
Think
that's
what
we
try
to
do
with
the
organization
in
git
lab
is
to
to
separate
anything
from
the
needs
of
tracking
on
the
ux
side,
for
the
needs
of
tracking
on
the
engineering
side
right.
So
essentially,
your
themes
are
ready
for
design
ready
for
problem
validation,
InDesign
and
all
the
issues
within
them
are
all
ready
for
design
or
InDesign
right
or
have
you
been
defined
so
problem,
validation.
A
A
Yeah
but
I'll,
let
y'all
know
where,
like
everyone
know,
I
mean
it's
something
my
PMR
talk
and
I
are
talking
to
like
because
we
do
want
to
use
the
product
through
a
map
as
a
single
source
of
truth,
because
it,
you
know,
as
a
cross-functional
team
I,
would
like
to
like
make
these
themes
more
visible
on
the
product
roadmap
itself,
but
anyway
we're
gonna
keep
working
through
it.
Blair
did
you
have
any
questions
really
fast
and
then
we'll
move
on.