►
From YouTube: 2021-06-03 Planning Objects Design Sync
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
Obviously,
we've
talked
about
the
there
we
go.
We've
talked
about
the
side
panel
approach,
which
I'm
still
going
to
present
and
get
some
feedback
on
in
usertesting.com.
A
I
think
I'm
going
to
reduce
some
of
the
information
here
and
just
be
sure
that
what
I'm
showing
is
a
little
more
consistent
with
what
we're
probably
going
to
offer
out
of
the
gate
and
then
for
the
actual
detail
view
of
the
issue,
probably
something
like
this,
I'm
still
kind
of
thinking
through
it,
but
I've
added
in
the
author
and
the
status
as
well
as
the
actual
id.
Let
me
just
quickly
make
sure
I
got
the
right
prototype
here
and
I'll
show
you
kind
of
what
I'm
thinking
for
this.
A
There
we
go
so
maybe
having
little
hovers,
that
kind
of
show
what
these
do
and
when
you
click
on
them.
For
some
reason
this
is
not
working,
but
when
you
click
on
them,
it
kind
of
launches
the
panels
that
we
had
looked
at
before.
So
I'm
going
to
test
some
of
that.
But
then
also
the
modal
approach
is
kind
of
what
I'm
playing
with
now
and
trying
to
think
through
what
information
is
going
to
be
most
valuable.
A
I
still
think
that
we
need
to
have
both
the
side
panel
sort
of
minimal
view
and
then
the
larger
detail
view,
even
if
the
larger
detail
view
ends
up
just
being
what's
in
the
side
panel,
but
in
a
full
screen
view,
so
I
think
there's
still
value
in
offering
both,
but
it
could
be
that
it's
the
same
same
stuff,
just
one's
in
in
more
of
a
condensed
form.
A
I
don't
love
this
area
right
here.
This
is
kind
of
where
I
was
just
before
we
started.
The
conversation
was
playing
around
with
maybe
a
different
way
to
show
this
information,
but
once
I've
kind
of
got
that
refined,
I'm
going
to
get
these
put
in
front
of
users
on
usertesting.com
and
get
that
feedback.
My
goal
is
to
have
that
by
the
end
of
the
day,
these
little
tweaks
refined
and
to
get
it
in
people's
hands
and
at
least
start
getting
some
feedback.
A
So
I'll
keep
you
all
in
the
loop
as
I
make
progress
there,
but
that's
kind
of
what
I've
been
working
on
yesterday
and
today
is
just
playing
with
some
of
these
additional
approaches.
Nice.
A
B
A
Was
thinking
it
needs
like
a
thousand
more
labels
well
and
yeah,
and
actually
so
this
view.
My
thought
with
the
labels
was
potentially
condensing
it
into
something
kind
of
like
this,
where
you
see
like
a
couple
of
labels
or
a
label,
and
then
you
can
click
to
expand
and
view
like
a
little
panel
of
all
of
them.
But
again
I
don't
know
yet
I
I
don't
like
the
cluttered
look
of
it.
A
But
what
led
me
there
was
thinking
about
how
jarrah
has
theirs
laid
out
and
one
of
the
things
that
I
like,
and
I
think
that
asano
does
this
as
well.
Is
they
have
a
very
clear
like
two
column
layout
that
says
title
and
then
the
title
and
then
description
and
then
the
description?
And
you
know
the
each
item
has
a
clear
label
and
then
the
content
associated
with
it,
and
I
do
kind
of
like
that
and
by
labels.
A
Of
course
I
mean
something
like
status
labels
assignees,
not
our
traditional
view
of
labels,
but
I
like
that,
because
it
kind
of
gives
you
a
quick
at
a
glance
understanding
of
what
you
can
discard
if
you're
not
interested
in
reading.
Something
then
you
see
the
title
and
you
can
just
move
on
as
opposed
to
having
to
stop
and
reflect.
Do
I
need
to
process
this?
Does
this
need
to
be
something?
I
need
to
worry
about
so
still
playing
with
that,
but
yeah
but
gaba.
B
A
B
B
Yeah
think
about
too
is:
I
would
go
ahead
and
design
this
with
the
idea
of
clearly
showing
or
indicating
what
the
type
of
planning
object
is
and
then
also
status.
B
I
think
if
we,
if,
if
you
think
that,
like
that
way,
that
we're
presenting
open
will
work
once
we
get
customizable
statuses,
then
that's
fine,
but
I
think
those
are
the
things
that
at
least
like,
I
think,
that's
a
good
yeah.
I'm
sorry
go
ahead.
I
was
gonna
say
after
we
kind
of
get
over
the
hump
of
getting
epics
on
the
types
of
issues,
then
I
want
to
start
working
on
the
customizable
statuses
so
that
we
can
basically
more
easily
build
reports
and
also
like
manage
workflows
and
stuff
like
that.
So.
A
Okay,
that's
a
good
point.
I
know
their
feedback
too
yeah,
please!
No!
Please
go
ahead
for
like
for
me
just
looking
at
this.
I
think
it's,
the
half
and
half
layout,
that's
bothering
me,
but
I
would
this
still
feels
overwhelming,
like
I
was
hoping
that
like
in
this
view,
it
would
just
be
simple.
I
would
be
able
to
read
the
description
and
like
if
I
want
to
scroll
down
to
comments.
A
I
could,
but
I
feel
like
that,
like
this,
the
sidebar
might
work
well
on
the
actual,
like
detail,
page
like
the
url
page,
where
you've
got
the
width,
whereas
with
this
especially
on
my
machine,
would
be
really
frustrating
to
have
like
that.
Much
going
on
in
such
a
small
space,
it's
like
I'd
almost
want
mine
to
go
more
towards
a
mobile
stack
where
I
could
choose
to
scroll
down
to
comments.
If
I
wanted
to
I'm.
B
A
You
said
that,
because
I
actually
started
with
that
thought
and-
and
I
thought
about
you
when
I
was
working
on
this
and
designed
it
so
that
it's
a
maximum
width
of
900
and
possibly
would
even
go
smaller
just
to
ensure
that
everything
is
addressed.
But
I
I
agree,
I
think
it's
a
lot
to
squeeze
into
a
small
space,
so
that
kind
of
helps
to
validate
my
initial
concern
that
maybe
we
should
just
do
top
to
bottom
layout,
similar
to
what
we
have
now,
but
maybe
even
more
simplified.
A
If
you
want
your
full
width
and
you,
like
gray,
set
like
gabe,
said
if
you
could
gray
them
out
or
have
like
a
dot
dot
dot
or
something
where
it's
less
intrusive
and
they're
still
present,
and
you
could
like
click
to
see
more,
but
they
aren't
like
in
your
face
to
the
same
level,
I
think
that
could
work
cool,
that's
good
feedback.
B
A
few
things
I
don't
ever
want
to
go
to
a
detail
page
again,
like
at
least
have
to
leave
my
contacts.
If,
if
you
can
like
have
a.
A
A
B
A
A
B
Yeah
there
will
be
a
detail
page
like
if
I
go
to
an
issue
list
like
maybe
like
I
don't
know
we'll
figure
it
out,
but
I
wouldn't
want,
like
the
detail
page
to
look
any
different
than
what
it
would
be
like
if
I
wanted
to
interact
with
the
detail
of
an
issue
from
a
board.
B
Like
you,
if
you
had
one
where,
if
you
wanted
to
start
with
the
sidebar,
and
you
showed
just
like
sort
of
a
high
level
preview
and
then
if
I
like,
hit
arrow
to
expand
it
out
to
the
left
or
something
like
that,
would
slide
out
and
show
me
the
full
view
like
in
the
two.
That's.
A
B
With
this,
too,
is
when
you
have
the
comments
underneath
the
description
and
you
deep
link
into
a
comment.
Then
you,
like
the
we
have
this
problem
right
now
with
pagination,
and
it's
not
going
to
be.
We
can't
fix
it
without
changing
the
ui
or
the
ux
because,
like
if
you
deep
link
into
a
thread,
we
have
to
load
every
single
note
before
we
can
render
and
then
scroll
you
to
that
location
and
that's
a
super
like
clunky
user
experience,
and
so
that's
why
I
was
interested
in
exploring
the
side
by
side.
Not
just
so.
B
I
could
like
edit
the
description
while
reading
comments,
but
so
that
we
could
load
them
independently
and
basically
load
the
description
stuff
like
that.
While
we
load
and
point
you
to
the
right
point
in
the
discussions
without
having
to
like
auto
scroll
you
if
that
makes
sense
like.
A
A
Well,
I
like
the
side
by
side
just
because
you
can
have
access
to
the
title
and
the
description
in
the
same
place
as
the
conversation.
So
you
don't
have
to
do
so
much
back
and
forth,
but
I
like
the
thought
of
having
both
the
detail,
view
and
the
sort
of
smaller
contextual
view,
but
giving
the
user
the
ability
to
choose
when
they
want
to
do
what
you
know.
I
don't.
I
would
like
to
not
ever
force
them
to
go
to
a
detail
view,
but
I.
B
A
It
to
be
an
option
if
they
have
a
need
to.
I
think
some
people
feel
a
little
insecure
about
sharing
a
link
when
it's
to
a
thing
that
is
nested
within
a
page
like
what's
going
to
happen.
If
I
send
this
link,
is
it
going
to
pull
up
my
to-do's
page
with
this
panel
exposed?
Is
it
going
to
go
straight
to
a
page
that
just
has
the
issue
itself
or
planning
object
itself?
A
So
I
like
the
thought
of
having
both,
but
I
do
want
to
try
to
create
the
smaller
view
in
such
a
way
that
they
don't
have
to
necessarily
go
there
if
they
don't
want
to
and
that's
kind
of
what
I
was
trying
to
do
in
both
cases
but
agree.
I
don't
love
this
view
again.
So
this
feedback
is
super
helpful
and
I
may
still
go
ahead
and
explore
just
putting
the
comments
below
in
this
modal
view,
just
to
try
to
keep
things
even.
B
A
A
B
A
A
way
to
have
those
open
over
top
almost
like
a
layer
that
can
take
that
width
of
the
modal
again,
like
some
quick
view
that,
like
just
lets,
you
see
it
better
because
this
is
small.
That's
a
good
question
too,
because
I
think
the
design
management
opens
in
a
modal.
Doesn't
it
or
is
it
yeah?
It's
a
new
page.
It's
a.
B
A
And
it's
always
over
an
issue
right,
and
so
in
that
case
we
would
have
a
layer
over
a
layer
which
I
I
think
feels
kind
of
odd.
So
in
that
case,
probably
what
it
would
do
is
launch
the
detail
view
and
then
overlay
that
and
take
them
out
of
their
context,
all
together,
I'll
think
on
that
a
little
bit
more
yeah.
I.
B
A
B
Thing
for
me-
and
I
also
think
with
the
design
manager,
there's
a
way
to
explore
right
now.
It's
no
full
screen
overlay,
but
is
there
a
way
to
like
that's
a
perfect
example
of
building
the
ux
for
the
issue
to
be
extensible,
where
you
have
like
these
apps
within
the
issue
view
or
the
playing
object
view
like
you're
gonna
have
a
road
map
right,
which
is
on
fx
right
now.
You
have
your
your
hierarchy
tree.
What
about
viewing
designs
like?
B
Yeah,
in
this
view,
if
you
were
to
have
like
let's
say
you
have
some
of
those
little
design
thumbnails
in
the
description
you
click
on
one.
Maybe
it
replaced
the
description
with
the
design
image
and
then
you
still
have
your
comments
over
there
to
the
right
of
it.
So
it's
almost
like
the
same
kind
of
experience.
A
The
negative
feedback
that
we
got,
though,
is
the
designs,
aren't
big
enough
they're,
not
that
so
good
making
smaller
in
the
full
screen
view
would
be
really
bad.
They
want
to
see
it
at
100
of
what
the
design
is
actually
going
to
be
for
the
app,
so
it
would
need
to
you'd
need
to
go
to
the
full
real
estate.
B
B
That
would
be
fine.
I
would
almost
like
to
have
like
the
little
sidebar
and
then
the
full,
like
the
detail,
view
just
be
overlaid.
If
you
can
have
the
detail
view,
that's
the
same
thing
but
like
when
I
want
to
open
it
up.
It
is
just
like
the
full
width
overlay
that
has
an
x
in
the
top
corner
that
I
can
go
back
to.
A
Yeah
yeah
you're
on
a
layer
above
yeah
that
would
work
as
long
as
they
get
the
full
width,
so
they
can
like
see
the
app
yep
well
again
for
usertesting.com,
I
was
looking
to
primarily
test
side
panel
versus
modal
and
then
some
of
the
kind
of
shuffling
around
of
the
layouts,
it's
possible
that
we'll
need
to
go
back
and
get
some
additional
feedback
as
we
continue
to
make
changes.
But
I
will
let
you
both
know
once
I've
got
kind
of
a
final
proposed
design
again.
A
My
goal
is
to
get
this
done
today,
so
that
I
can
go
ahead
and
start
getting
feedback
sooner
and
then
we
can
and
actually
what
I'm
gonna
try
to
do.
Or
what
I'm
going
to
do
is
one
test
for
each
design,
initially
get
feedback
and
then
see.
If
there's
anything,
I
need
to
tweak,
and
so
it
could
be
that
we'll
have
feedback,
a
revision
and
then
get
more
kind
of
bulk
feedback
on
each
idea.
A
A
I
want
to
keep
seeing
my
to-do
list
and
work
on
an
issue
at
the
same
time
or
do
I
want
to
focus
on
this
issue
and
let
the
other
stuff
melt
away
and
like
get
into
the
content
or
a
comment
and
like
I
don't
the
52-views
I
have
are
actually
super
distracting
in
that
mode.
So
I
almost
think
that
that's
an
interesting
question
to
explore
is
like
do
I
need
to
see
that
noise
of
the
other
things
on
a
board?
A
B
B
I
was
just
going
to
put
like
riffle
on
that
a
bit
and
it's
if
you
have
like
a
single
view,
app
or
whatever
for
the
planning
object,
detail
view
what
you
can
do.
Then,
if
it
is
a
modal,
you
can
kind
of
wrap
that
with
like
different
sort
of
elements,
depending
on
the
context
so
like
in
the
to
do's,
I
would
want
instead
of
seeing
all
the
twos,
I
would
just
want
a
navigation
thing
to
say
like
go
to
the
next
to
do
so.
B
B
In
the
top
just
to
move
to
the
next
or
the
previous,
you
can
you
can
use
cool
stuff
like
that.
So
that's
all.
A
Well-
and
all
I'm
showing
here
is,
this
is
all
of
the
places
that
I
identified,
that
you
might
want
to
access
an
issue
in
particular,
but
of
course,
we'll
also
need
to
consider
merge,
requests
and
epochs
and
the
different
places
incidents
where
people
will
want
to
access
those
things
and
how
that
might
change
things.
A
And
then,
as
a
user,
you
could
choose,
because
if
you
go
doc
mode,
then
your
other
work
is
front
and
center.
I
like
that
idea.
I
was
talking
with
my
ux
buddy
today
about
this
as
well,
and
he
was
saying
that
there
might
be
some
places,
because
we
have
to
think
obviously
globally
about
this
and
and
where
else
people
might
want
to
access
other
issuables,
and
he
was
saying
that
there
might
be
other
places
where
people
don't
want
that
option.
A
So
I
like
giving
them
the
choice
of
modal
or
side
panel,
and
I
know
that
mike
had
had
some
concerns
in
the
past,
about
it
being
shared
too
soon
with
too
many
people
and
getting
kind
of
inundated
with
feedback.
But
I
think
we
need
to
go
ahead
and
start
sharing
it
a
bit
more
widely
because
it
will
have
an
impact
on
so
many
different
folks-
and
I
do
want
to
understand
other
stage
groups
thoughts
on
this
and
how
they
could
see
it
impacting
their
work.
A
So
once
I've
got
these
prototypes
kind
of
finalized,
my
goal
is
to
start
sharing
it
in
the
ux
channel
and
getting
feedback
there
and
feel
free
to
share
it
as
well.
If
you
have
any
ideas,
docs
mode
could
be
exciting,
because
if
I
could
even
dock
an
issue,
I'm
working
on
almost
and
then
navigate
around
like
oh
gabe
talked
about
it
over
in
this
thing,
I'm
gonna
go
find
it,
and
then
I
pull
up
more
contacts
and
then
I
keep
working
on
what
I'm
on.
I
don't
know.
A
A
B
I
yeah,
I
was
just
gonna
say
about
sharing
more
broadly,
I
would
wait
until
you
are
comfortable
with,
like
the
I
think
we
talked
about
this
the
other
day,
but
like
the
widget
system
or
the
how
other
teams
might
be
able
to
integrate
in
in
a
consistent
way
and
like
how,
like
the
the
core
like
building
blocks,
sort
of
work,
because
I
think,
if
you
don't,
then
people
are
gonna.
Have
all
sorts
of
questions
like.
Oh,
where
do
designs
live
and
where
do
like?
B
How
do
I
integrate
vulnerabilities
and
how
do
I
do
all
this
other
stuff
and
then
I'll
like
spur
a
bunch
of
questions?
So
if
you
don't
have
all
the
details
being
like
here's,
how
like
the
widget
type
system,
will
work
and
how
you
like
we're,
creating
this
way
for
anyone
to
easily
integrate
into
issues
and
consist
or
playing
objects
in
a
consistent
way.
B
That
will
stave
off
a
lot
of
questions.
I
think.
A
Okay,
let's
get
feedback,
I
like
the
thought
actually
of
maybe
offering
both
the
doc
and
a
sort
of
modal
version.
So
I
think,
instead
of
trying
to
do
two
separate
sets
of
tests
one
for
each,
then
I'm
going
to
try
to
combine
everything
into
a
single
view
and
give
them
the
option
to
choose
one
or
the
other
and
get
feedback
that
way,
since
that
is
potentially
what
we
would
propose
anyway,
I'll.
Let
you
both
know
as
progress
is
made
on
this
today
and
how
it's
going
and
yeah.