►
From YouTube: Plan group weekly meeting
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).
B
Yeah,
just
a
quick
thing
to
start
with
so
get
loud
contributes
is
unconference
event,
that's
happening
in
New
Orleans
in
May.
As
part
of
that
there
is
a
space
on
the
Saturday
for
a
self-organized
team
dinner,
it's
described
as
now,
engineering
and
product
or
a
bit
unusual
there,
because
the
team's,
obviously
late,
there's
people
from
multiple
teams
in
this
call
right,
like
Victor's,
got
one
manager.
B
I've
got
a
different
manager,
Donald
well,
Donald's,
not
the
same
manager
as
maybe
you
know
what
I
mean
well,
there's
got
a
different
manager,
so
I
don't
know
exactly
how
that
shakes
out
like
you
know,
because
it's
called
the
team
dinner.
Some
people
are
treating
as
a
stage
group
dinner
I've
just
copied
what
Dylan's
doing
in
configure
and
said
well,
I'm
gonna
invite
everybody
from
the
backend
so
one
out
for
the
back-end
team,
but
anybody
else
in
the
stage
group
can
also
join
that
one
like
it's.
B
It's
like
the
minimum
is
gonna,
be
the
back-end
team,
but
it's
it's
open
to
everybody
from
the
plan
stage.
Group
who's
attending
contribute.
So
if
you
yeah
comes
up
that
issue,
if
you're
joining
that's
all
I
really
need
right
now
to
get
an
idea
of
the
numbers
and
then
once
I
have
that
I'll
start
looking
at
options
for
where
to
eat.
Obviously,
if
anybody's
got
a
strong
opinion,
I'd
like
to
eat
feel
free
to
just
add
it
to
that
issue.
Already
yeah.
B
B
C
B
B
Don't
think
it's
like
it's
a
problem
to
just
go
out
and
do
something
different
on
those
ones
as
well:
I'm,
just
organizing
the
one
that
sort
of
highlighted
on
the
slides
that
I've
linked
to
in
the
issue,
which
is
on
the
Saturday,
because
I
have
to
organize
that
for
my
team
anyway,
so
I
figure,
like
you
know
we
can.
We
can
pour
our
efforts
and
do
as
many
people
as
possible,
but
some
like
I,
said
from
what
I
understand
I
like
this
I
see
who
joins.
B
B
B
B
So
basically,
if
you
just
got
want
something
you
want
to
throw
in,
there
don't
feel
like
you
have
to
wait
for
that
vote
to
be
finished
before
you
do
that,
like
we
can,
we
can
always
figure
that
out
later,
but
some
idea
behind
opening
the
new
issue
earlier
was
just
that
you
might
have
something
that
you
forget
about,
but
if
it's
already
there
you
can
just
put
it
in
and
then
you
won't
forget
about
it.
Chrishelle
epic
relationships
within
ethic.
D
Yep,
so
this
was
something
that
we
realized
while
discussing
with
how
to
go
about
handing
dragon
droplet
preview.
So
I
left
my
concern
in
the
original
issue,
I'm
mentioning
both
Victor
and
animal,
like
whether
we
should
be
allowing
to
do
full,
drag
and
drop
across
the
entire
preview.
Like
a
fuser
wants
to
drag
an
item
from
preview
to
anywhere
within
the
preview.
Should
it
be
changing
parent
and
child
relationships
between
the
epics,
or
should
we
not
do
it?
D
Based
on
what
I
have
received
the
in
response
from
animals,
it
mentions,
like
we
shouldn't,
be
doing
the
tree
view
for
this
situation.
Instead,
we
will
be
having
only
two
tabs,
one
for
discussion
and
one
for
nap
emitting.
So
what
we'll
do
is
that
will
leave
both
issues
and
related
epics
lists
as
it
is,
but
just
wanted
to
clarify
if
I
understood
the
response
correctly
so
Victor.
What
do
is
list
on
that?
One
that.
A
Sounds
good
to
me,
let's
see
is
handle
on,
doesn't
look
like
it.
I
mean
that
sounds
like
a
good
approach
to
do
the
next
thing
right
and
then
after
this,
if
there's
other
versions,
front-end
issues
or
just
other
planned
tasks
to
work
on,
you
know
work
on
those
ones
first
and
then,
if
you
have
time
just
you
know,
work
on
the
tree
view
itself,
so
I
think
a
good
approach
is
separating
two
tabs.
That's
a
smaller
sounds,
like
I,
said
more
as
a
simpler
iteration,
so
I'm
definitely
up
for
that.
A
D
So
the
the
original
design
that
was
proposed
was
to
have
three
tabs.
So
initially,
when
you
any
epoch,
we
would
be
seeing
title
and
description
right
below
that
will
be
having
three
tabs
one
for
discussion
where
we
would
have
comments
and
system
notes.
Second,
tab
would
be
to
show
related
items
which
would
be
the
three
view
with
issues
and
epics
all
combined
together,
and
the
third
tab
was
to
show
the
road
map
for
that
specificity.
So
that
was
basically
the
idea
yeah.
D
So,
as
you
can
see
in
the
tree,
we
are
seeing
both
issues
and
epochs
are
separated
by
the
drop
down.
So
if
you
want
to
see
just
issues,
we
would
select
relevant
item
from
that
drop
down
and
it
would
show
the
items
and
the
third
tab
was
to
show
roadmap
for
that
specific
epoch.
So,
for
instance,
if
an
epoch
has
multiple
child
epochs
assigned
to
it,
then
all
those
child
epochs
would
have
intern
start
and
finish
dates
define.
D
So,
in
that
case,
we
would
have
a
small
version
of
roadmaps,
but
with
similar
experience
that
we
have
for
the
entire
full
page
roadmap,
just
that
would
be
showing
child
picks
for
that
specific
epoch
with
the
timeline
rendered
accordingly.
So
so
for
this
situation
now,
what
what
is
suggested
here
is
that
we
will
be
showing
only
two
tabs
discussion
and
roadmap
while
leaving
rest
of
the
page
as
it
is
so
the
list
of
related
issues
and
epics
woods.
The
show
up
before
the
entire
tab
UI,
so
those
items
will
be
appearing.
D
A
D
So
because
adding
map
is
still
straightforward,
the
road
map
apps
that
we
have
right
now
it
doesn't
need
to
be
the
the
same
one
as
the
one
we
are
seeing
for
the
full
page
like.
Basically,
you
can
provide
the
base
path
for
which
you
need
to
pull
a
fix
for
and.
E
D
Will
pull
in
the
data
for
those
many
epics
and
show
up?
Yes,
it
might
need
some
back
in
hell
because
right
now,
if
you
want
to
fetch
epics
only
for
one
specific
epic,
so,
for
example,
we
have
epic
age
and
we
have
a
child
epics
like
a
1,
a
2,
a
3,
a
5
of
2.
If
I,
then
those
5
epics
cannot
be
fetched
directly
right
now,
there
is
only
one
API
which
gives
you
a
picks
from
a
specific
group.
D
D
E
A
That
would
be
consistent
with
what
we
have
right
now,
because
we
don't
have
all
the
sentence.
We
only
have
immediate
children
in
the
yes
area
and
then
we're
showing
a
visual
for
those
now
be
consistent.
There,
okay,
yeah
now
that
that
sounds
like
a
good
iteration,
whether
we
put
like
ourselves
and
like
the
further
descendants
I
think
that
that
can
be
a
separate
like
whether
we
do
that
are
not
back
in
your
second
step:
separation
by
a
lake,
how
it's
consistent!
So
thanks
for
clarifying
that
go
sure,
I
thought
we
were
doing
the
tree.
A
A
D
So
I'll
leave
the
response
based
on
what
we
just
discussed
and
then
you
could
go
ahead
and
update
and
as
far
as
the
tree
view
is
concerned,
so,
although
we'll
have
to
discuss
it
separately
with
anĂbal
like
how
to
go
about
drag-and-drop
because
right
now
we
have
flat
list
with
nodes.
There's
no
do
not
expand
and
child
items
do
not
show
up
within
a
particular
parent
item.
But
if
you
want
that
entire
tree
to
be
dragon
droppable
there,
you
can
reorder
epics.
D
However,
you
want,
then
that
needs
to
be
like
a
checklist
of
cases
where
we
very
basically
determine
how
to
go
about
reordering,
because,
for
example,
if
we
have
one
apparently
expanded
with
all
the
child
effects
showing
up
underneath
it
and
then
if
we
want
to
reorder
one
of
the
child
epics,
then
how
that
epic
should
be
the
order
first.
So,
for
example,
user
can
basically
drag
it
anywhere
throughout
the
list
and
would
try
to
drop
somewhere
within
the
list,
and
if
that
child
epic
goes
all
together
into
a
different
parent
to
them.
D
That
would
mean
lot
of
things
going
happening
in
the
background,
because
you
would
need
not
only
to
change
the
order
of
that
epic
within
that
list,
but
the
parent-child
relationships
will
also
be
changing.
It
would
directly
go
from
one
parent
to
the
other
parent,
so
whether
we
want
to
go
with
that
route
or
not
or
if
we
do
not
support
reorder
at
all,
because
those.
E
A
Once
you
have
a
tree,
it's
a
lot
more
complicated,
so
yes,
so
I
yeah!
No,
that
makes
sense
differing
it,
especially
since
apples,
not
here
I'm,
making
this
particular
day
and
probably
week.
Okay,
that
sounds
great
anything
else
before
we
jump
to
Walmart
I
copy
and
pasted,
where
your
point
somewhere,
because
it's
we
might
as
well
talk
about
this
first
number,
four.
A
C
So
yeah
so
yeah
I
asked
this
because
well
since
I'm
new
I'm,
not
really
aware
of
everything
that's
going
on,
but
my
question
regarding
asking:
if,
if
a
big
issue
can
turn
into
an
epic,
it's
because
I
imagine
that
at
some
point
issues
may
be
created
and
they
may
be.
You
think
they
are
small.
They
can
be
worked
in
a
small
piece
that
is
at
some
point.
Then
the
you
realize
they
are
bigger
and
then
I
am
just
wondering
if
they
could
turn
into
an
epic,
a
child.
A
A
Ok,
so
I
totally
made
that
googly,
but
anyways
I
mean
you
can
read
that
on
your
own
or
read
that
page
on
your
own.
But
what
I
realized
right
now
is
that
with
planning
we
can
do
top-down
planning
and
Bottoms
Up
planning,
so
top-down
planning
or
the
my
definition
of
top-down
planning
is
when
whether
you're
a
executive
at
a
company
and
planning
big
initiatives,
whether
you're
using
gill
net
for
your
personal
projects,
any
type
any
when
you
say
top-down
planning,
the
idea
is
you
don't
have
the
details
yet
right.
A
A
I,
don't
know
if
this
was
your
question.
Well
more,
but
I'll
just
offer
some
context.
I,
don't
think
we're
using
that
very
well
within
get
lab
in
particular,
but
I
have
seen
customers
use
it
so,
but
but,
for
example,
I
kill
that
what
we
do
often
is
anybody
that
has
an
idea,
even
though
it's
a
big
idea
to
create
an
issue.
I
think
that's
that's
Killa
culture,
because
we've
always
done
that
and
also
the
features
are
also
better
for
issues
because
there's
just
it's
this
more
full
fledge.
So,
by
definition,
that's
a
better
experience.
A
If
you
want
to
get
the
other
capabilities
of
linking
and
all
the
sidebar
attributes
and
so
on
and
so
forth,
issue
boards
and
then
the
other
respect
is
bottoms
up
planning
which
we
do
very
well
at
your
lab
and
which
is
a
feature
very
much
supported
by
get
lab,
which
is
you
just
create
the
issues
and
then
to
what
you
said
about
an
issue
getting
big.
We
have
a
feature
called
promoting
an
issue
to
an
epic
via
the
quick
action,
so
that
would
adjust
that
specifically
space.
That.
A
C
C
A
Obviously,
every
are
you
just.
These
types
of
decisions
are
fine
for
me,
but
when,
when
I,
when
I,
when
I
hear
that
that
makes
total
sense,
because
that
seems
a
very
well
defined
functionality,
unlike
the
one
that
Khrushchev's
working
on,
which
is
very
complicated
and
difficult
by
creating
an
epic
from
within
epic
I.
Think
it's
not
very
controversial
about
even
the
visual
interaction
designer
thing
is
that
controversial,
so
I
think
that's
a
great
one
to
start
to
test
out
the
process
and
for
you
to
figure
out
what
that.
C
A
C
Way,
one
thing
that
I
have
aligned
imean
where
well.
Actually
it
was
her
suggestion
so
since
I
would
be
splitted
working
for
plan,
but
also
for
the
quality
Department.
She
suggested
that
I
could
work
like
three
days
working
in
the
test
framework,
helping
the
quality
department
in
general
and
two
days
like
creating
the
task
plans
for
a
plan.
Is
that
okay,
as
well.
A
C
B
H
E
H
C
A
C
Thank
you
so,
and
the
last
is
more
like
a
question,
so
I
notice
in
the
in
the
kickoff
document
that
there
are
two
issues
that
they
mention
design
so
I
just
want
to
confirm
if
they
are
for
now,
just
design
related
and
not
development
related
yet,
and
they
will
be
development-related
in
in
the
future
or
are
they
already
development
related
as
well?
I'm
talking
about
issue
lease
raw
raw
design
and
related
merge
request,
ish
in
issue
design,
good.
A
Question
so
I'm
gonna
link
to
the
kickoff
talk,
so
everybody
can
can
read
it
so
doing
that
right
now.
So
in
the
past,
we've
struggled
a
little
bit
to
have
issues
that
were
designed.
Deliverables
I
didn't
like
that.
I,
don't
think
that
worked
very
well
because
we
had
things
like
we
would
mark
a
an
issue,
as
we
still
have
something
called
like
product
discovery
or
something,
and
then
maybe
we
had
like
design
deliverable
like
maybe
for
all
of
two
weeks.
A
Oh
I
forget
specifically
what
the
labels
were
called,
but
at
least
in
the
plan
team,
what
I've
observed
as
we
moved
away
from
it
I
think
that's
very
successful.
We
have
a
label
called
UX
ready,
which
is
something
that
designer
would
often
use
to
indicate
that
the
discussion
of
the
design
is
mature
to
a
stage
that
you
know
it.
It's
an
indicator
of
such
but
it's
not
again.
A
It's
not
permission
like
you
should
be
empowered
to
work
on
things
and
then
you
should
always
an
engineer
should
not
use
it
as
an
excuse
not
to
work
on
something
because
it
doesn't
have
UX
ready
yet.
But
so
to
me,
it's
a
it's
an
indicator.
It
tells
that,
oh,
this,
the
designers
has
moved
to
a
certain
stage
that
you
can
be
confident
on.
A
So
maybe
if
the
designer
is
not
responding
because
they're
sleeping
you
know,
please
go
ahead
with
whatever's
in
the
description
or
if
the
description
is
not
up-to-date
and
then
there's
a
UX
ready
label
on
it.
So
then
you
should
ask
designer
why
why
that
is
the
case
and
then
so,
the
in
general.
When
we
put
an
issue
and
it's
like
99%
of
the
time
the
issue
should
be
the
deliverable
of
the
issue
is
merging
a
merger
quest
to
ship
code.
A
That's
when
you
should
close
the
issue
and
so
the
issue
that
might
mean
that
the
issue
may
stay
in
multiple
milestones
and
that's
okay.
My
opinion,
like
we
might
be
hard
to
track
and
stuff
like
that,
but
especially
for
bigger
issues
like
the
one
that
Kershaw
is
working
on
what
we're
gonna
do
after
this
college,
probably
I
will
probably
copy
and
paste
some
of
the
designs
into
a
new
issue,
because
Kushan
was
working
on
and
work
with
the
designer
King
me
and
we
found
out
that
something
was
different.
A
So
in
the
past
what
we
would
have
done
is
Mayo,
then
we
finished
a
design
and
then
we
copy
and
paste
it
into
other
issues,
and
we
close
that
issues
and
turns
out
that
in
theory
that
sounds
like
makes
sense,
but
in
practice
it's
actually
very
confusing,
because
everything
is
so
fluid
at
good
lab
and
everything
is
not
waterfall
at
all.
So
it
turns
out,
if
you
try
to
put
a
process
on
to
our
issues
and
say,
like
design
is
done,
then
we
do
this.
Then
we
do
this.
A
E
I
A
A
J
B
Pages
per
stage
group
yeah
I'm,
just
gonna,
update
that
now,
but
it's
fine
thanks
forum
yeah,
just
for
the
benefit
of
the
video.
What
we
were
talking
about
there
was
I
had
a
link
to
an
old
plan,
YouTube
playlist.
That
leaked
quotes
together
of
all
these
meetings,
that
we
have
and
there's
a
new
one,
because
it's
on
a
different
YouTube
channel,
well
account
or
something
I,
don't
really
know.
Thanks.
A
G
A
No,
no
no
I
can
I
can
add
a
description
I'll.
Do
that
right
away
the
playlist
support
descriptions.
So
that's
something
that
is
it'll.
Take
me
two
seconds
to
do
if
I
can
find
the
list
now
I'll
do
that
right
now,
as
we
talked
about
the
next
topic-
oh,
but
then
that's
me
talking
okay,
so
so
we're
waiting
on
an
analyst
to
get
back
to
us
because
we
submitted
something
for
EAP
ta
belief.
So
if
you
click
on
that
link,
it's
goes
this
slack,
Channel
and
I.
A
Think
technically
I'm
not
supposed
to
talk
about
it
publicly.
So
that's
why
I'm
just
saying
analyst,
even
though
there's
not
a
lot
of
analysts
out
there,
so
we're
we're
we're
sort
of
antsy
waiting
for
that,
because
we
would
work
on
that
late
last
year
and
it's
it's
gonna,
be
pretty
significant,
I!
Think
if
we,
if
we
do
well
there,
especially
in
light
of
recent
announcements,
there
was
the
acquisition
by
Atlassian
of
agile
craft,
which
is
squarely
a
portfolio
management
tool
very
much
more
so
than
a
project
management
tool
right.
A
So
if
you
look
in
various
are
various
black
channels
and
even
a
group
conversation.
Obviously
we
talked
about
that
yesterday
and
then
something
that
wasn't
really
I
didn't
see
really
within
the
gitlab
Paul's
talked
about
a
Trello
made
some
big
announcements
yesterday
too
about
some
of
their
new
features
and
really
focusing
on
the
enterprise.
A
A
You
know
you
for
your
home
renovation
project
or
almost
or
it's
a
very
generic
tool
for
customers
and
then,
obviously,
that
approach
and
design
ethos
really
want
a
lot
of
you
know
hearts
of
people
who
love
or
another
way
to
put
it
like
Enterprise
design,
called
design
quality
of
enterprise
tools.
This
has
only
been
improving
the
past
10
20
years,
right
like
before,
like
Enterprise
still
suck
and
you're
just
forced
to
use
it.
That's
not
the
case
anymore.
A
So
the
to
me,
Trello
is
sort
of
making
that
bridge
and
so
with
Atlassian
buying
Trello
and
turning
it
now
into
enterprise
to
end
them
with
acquiring
hydrograph.
There's
a
lot
of
consolidation
and
a
lot
of
movement
in
this
industry.
So
I'm
really
excited
about
that,
and
so
this
waiting
for
this
will
be
will
allow
us
to
make
a
big
splash
I
in
the
conversation
as
well,
and
that's
all
I
have
to
say
about
that.
So
folks
feel
free
to
to
participate.
They're
thinking.
C
I
think
it
makes
a
lot
of
sense
to
you
for
this
kind
of
product
to
start
with
smaller
business
and
medium
business
and
when
they
get
mature
enough
to
grow
to
the
enterprise
in
the
previous,
a
startup
company
that
I
work
that
appeared
off
in
their
go
so
far
is
to
achieve
like
small
customers
and
meet
your
business.
But
in
the
future
they
have
the
vision
to
to
go
to
the
enterprise
and
I.
Think
Trello
is
already
mature
enough
to
tradition.
Well,
I
mean
so.
A
I
think
if
we
can
benefit
from
now,
two
years
to
me,
it
took
them
two
years
after
being
fired.
That's
too
slow,
even
cute
lap
time
skills,
that's
true
yeah,
but
but
it's
but
it's
interesting.
It's
it's
like.
On
the
same
day,
this
happened
literally,
but
like
not
a
lot,
people
were
talking
about
the
Trello
I
mean
the
Trello
piece.
A
I
talked
because
I
thought
we
made
a
huge
improvement
last
time
like
I'm
having
everybody
talk,
so
I
just
wanted
to
get
a
sense
of
what
everybody
thinks
about
that
and
might
my
comment.
My
meta
comment
is
that
we
can
all
participate
in
other
ways
outside
of
the
group
conversation
and
we
can
record
videos.
We
can
have
separate
conversations.
A
B
Purely
for
myself-
and
you
know,
I
realized
that,
like
I
talk
a
lot
anyway
play
I,
have
plenty
of
opportunity
to
talk,
cannot
call
it
all
my
like
for
me
personally.
The
way
I
see
the
group
conversations
working
as
it
stands
now,
because
we
don't
present
the
slides
is
that
most
of
the
questions
sort
of
naturally
product.
B
Strategic
questions,
which
are
going
to
be
more
focused
on
the
product
management
side
of
things.
There
will
be
questions
that
require
more
detail,
which
are
more
later
to
sort
of
speak
to
people
within
the
teams
working
on
that
part
of
the
product.
You
know
whether
they'll
have
like
you
know
the
exact
details
to
hand
or
what
you
know
we
might
be
asking
for
opinions
like
the
outer
I
think
yesterday,
you
got
called
on
to
answer
something,
for
instance,
that.
E
I
B
A
No,
no
actually
that
by
definition,
that
is
the
case
and
my
and
I'm
okay
with
that
I
think
that's
a
good
use
of
time.
More
broadly,
as
a
group
conversation,
the
purpose
of
a
group
conversation
and
the
purpose
of
informing
the
company
and
that
just
being
a
good
venue
for
that,
so
the
downsides
I
see
are
at
least
twofold.
One
is:
is
there
an
opportunity
for
the
plan
came
to
share
more
details,
technical
things,
design,
process
and
so
I?
A
E
B
Of
the
directors
that
report
to
Christopher
and
the
developments,
the
departments
also
have
their
own
sub
department
also
have
their
own
Tim
Zalman
had
one
where
he
went
into
more
details
about
graph
QL
run
prints
in
a
week.
Do
Dahlia
will
have
one
sort
of
the
ops
stuff
and,
as
we
get
more
direction,.
B
E
B
To
the
slides
which,
because
we
don't
present
those
it
feels
you
know
it
can
feel
like
those
don't
exist,
but
obviously,
like
people
are
reading
those
before
and
you
know
there
was,
there-
was
sort
of
a
lot
of
mentions
of
specific
things
that
specific
people
had
done
in
those
slides.
Exactly
you
put
links
where
people
could
find
out
more
yeah
nor
Mario
as
I
can
see
you
both
they're.
Like
do
you
have
any
opinions
there.
L
L
L
A
So
it
doesn't
sound
like
a
problem,
so
we
don't
have
to
solve
it
and
I
just
wanted
to
be
very
cognizant,
because
if,
if
you
came
to
kill
AB
thinking
that
this
is
a
great
opportunity
and
you
loved
the
previous
format-
and
you
love
that
you
have
an
opportunity
to
speak
about
your
awesome
work.
I
personally
want
to
be
biased
and
I
want
to
be
be,
be
selfish
for
the
team
and
saying,
let's
take
advantage
of
this
opportunity.
A
But
if
it's
literally
like
something
you
don't
care
about
and
whether
it's
you
know
your
personal
capacity,
something
that
you
come
in
and
contribute
to
something
that
you
find
fun
and
rewarding.
If
you
literally
don't
care
about
that,
then
this
is
a
non
problem.
So
I
am
happy
to
spend
the
30
minutes
blabbering
away
wrong.
Shawn.
A
B
E
B
B
What
I've
done
sometimes
for
other
group
conversations
is
just
like
add
a
question
like
any
question
as
like
the
first
one.
So,
first
of
all,
you
don't
get
that
sort
of
awkward
moment
at
the
start,
where
there's
sort
of
that
big
gap.
While
you
wait
because
I
assume
most
people
sort
of
basically
read
the
slides
pretty
much
at
the
start,
the
call,
but
secondly
like
in
it
means
that
nobody
has
to
be.
E
B
E
B
A
A
But
like
the
format,
matters
and
I
think
I
did
cheat
less
there.
I
I
would
build
out,
maybe
donald's
I,
don't
know
if
that
was
your
suggestion,
or
my
suggestion
would
be
like
if
you
just
have
general
questions.
Like
literally
you
know,
48
hours
of
24
I
tried
to
do
that
like
30
minutes
ahead,
but
it
failed
spectacularly
I
started
advertising.
A
This
group
conversation
like
30
minutes
prior
I
mean
just
lacking
in
everywhere,
and
just
hoping
people
will
add
questions,
but
if
we
were
more,
if
we
did
that
actually
carefully,
we
could
collect
questions
in
general.
We
could
ask
people
specifically
to
go
to
the
dock
and
add
questions
prior
and
then
you
know
we
could
prepare
better
for
that
and
then
specifically
again,
if
we
somebody
really
wanted
to
talk
about
their
work,
we
could
bias
toward
that
time
as
well,
so
I
think
I
think
they're
yeah,
that's
pretty
good
improvements.
There
yeah.
H
I
mean
just
to
Brett's
point:
you
know
in
chat
there,
I
think
and
I,
don't
think
it's
just
him.
I
think
there
are
a
few
people
that
really
don't
like
being
put
on
the
spot
on
video
like
that.
So
if
we
are
able
to
give
a
couple
minutes,
or
at
least
a
little
bit
of
time
to
prepare
for
the
answers,
we
may
be
able
to
get
more
engagement.
K
Yeah,
those
are
good
points,
I
mean
we
can
always.
You
know.
If
somebody
wants
to
answer
questions
during
the
during
the
improvisation
we
can,
you
know,
have
a
list
of
who
once
thought
who
would
rather
not
that's
an
easy
way
to
not
call
somebody
out
that
wouldn't
like
to
unless
we
really
need
that
person
to
answer
or.
I
A
A
A
A
Thanks
for
bringing
this
up,
Donna
I
missed
the
first
half
of
your
point,
but
I
think
you
mentioned
bread
and
I
suddenly
called
up
Bread
on
one
of
our
EMA's
bread.
I,
don't
know
if
you
remember,
and
that's
called
you
out
but
like
I,
think
Sid
said
something
about
like
we
should
do
more.
Youtube
videos
and
I
said
something
like,
but
what
if
people
didn't
want
to
do,
YouTube
videos
and
I
what
I
was
trying
to
get
out
of
Sid
so
that
he
could
tell
the
whole
company
and
so
to
sort
of
reinforce?
A
The
idea
like
we
all
contribute
in
different
ways
and
and
I
think
that's
that's
great
right
so
like
when
I
push
bread
and
thought
to
do
a
video,
they
said
no,
no,
no
I
want
to
do
a
blog
post
like
that.
That's
awesome,
so,
just
as
different
people
consume
content
in
different
ways,
you
should
be.
You
know,
free
to
present
content
in
different
ways
and
I
think
this
applies
to
the
group
conversation
and
then
we
have
the
slides
or
in
the
future
it
will
be
a
blog
post.
Hopefully
I
think
that
that's
better
there's.