►
From YouTube: Create:Editor Product/UX Weekly - 2021-03-17
Description
Weekly Editor group sync between Product, Design, and UX Research
A
A
First
off
michael,
I
wanted
to
get
just
like
a
just,
a
quick
gut
check
on
the
in-page
search
for
settings
and
whether
or
not
you
felt
like
there
was
anything
that
we
could
do
quickly
to
improve
the
experience
before
we
turn
off
the
feature
flag
or
whether
we
should
just
roll
it
out
as
is
and
iterate
later,
knowing
that
the
next
two
milestones
are
pretty
packed
and
we
might
have
to
live
with
it
for
a
little
while.
B
So
with
how
the
settings
search
now
per
page,
I
think
that's
an
okay
experience.
There
are
possible
iterations
on
how
how
granular
we
make
this.
You
know
when
we
search
for
something
and
we
it's.
The
text
is
within
a
block.
How
granular
that
block
is
something
that
came
out
of
solution,
validation
to
be
more
narrow,
but
that
I
feel
like
could
be
handled
within
a
separate
issue.
Iteration.
B
What
have
you,
because
it's
really
good
that
we
made
that
move
to
put
the
search
at
the
top,
because
that
has
kind
of
led
the
design
and
exploration
of
how
we
could
do,
search
and
like
a
more
holistic
search
across
all
settings
pages
yeah
so
far
that
solution
validation
for
search
is
like
I'm
feeling
confident
about
that
direction.
B
C
B
A
Cool,
so
I
think
the
the
takeaway
here
is:
let's
create
some
follow-on
issues
based
on
your
solution,
validation
and
the
ideas
where
we
can
take
this
for
different
iterations,
which
I
agree.
It
opens
up
a
wide
number
of
options
and
then,
let's
create
one
follow-on
issue
to
just
tweak
the
styling
of
the
highlight
a
little
bit
try
and
get
that
in
as
a
stretch
for
1311..
A
I
I
think
that
it
just
somewhat
somewhat
related,
but
I
was
chatting
with
marcel
and
we
were
talking
about
your
concept
for
the
settings
and
moving
away
from
like
the
le
the
breakdown
of
the
pages
on
the
left
to
more
of
a
tab
breakdown
and
where
the
setting
bar
could
be
located
in
relation
to
that,
and
I
think
those
are
iterations
that
we
should
definitely
be
considering
for.
A
Like
you
know,
the
next
group
of
work
that
we
do
in
that
area,
so,
let's
just
get
out
ahead
of
this
one-
get
the
search
in
there.
Since
it's
working,
I
haven't
heard
any
negative
feedback
from
from
the
folks
that
have
used
it,
and
I
can
maybe
well
yeah
tomorrow's
the
last
day
before
friends
and
family
day,
but
I
was
going
to
post
about
it
last
week
and
realized
it
was
friday.
A
A
So
cool
I'll
I'll
update
the
issue
with
that
decision
and
we'll
take
it
from
there
and
let
me
just
make
a
couple
notes:
while
we
talk
about
this
next
topic
so
as
we
were
discussing
before
we
hit
record,
but
there
was
a
ux
group
conversation
the
other
day
and
settings
and
navigation
came
up.
A
There
was
a
good
discussion,
a
lot
of
interest
from
sid
on
the
the
the
road
map
and
what
we
have
planned
for
14
0
and,
as
a
result,
michael,
you
set
up
set
up
this
figma
doc
that
just
outlines
sort
of
a
consolidated
look
of
what
we
would
want
to
ship
for
14-0.
A
It's
spread
across
multiple
high-level
epics
right
now
and
we're
working.
You
know
in
a
big
push
to
get
some
of
this
in,
but
it
was
really
helpful
to
look
at
that
like
singular
design
file
and
say
like
if
we
are
able
to
achieve
what
we
want
to.
It
will
look
like
this
so
anyway.
I
just
wanted
to
first
of
all
thank
you
for
putting
that
together
and
I
think
we
should
do
more
of
that.
A
As
a
company
like,
I
think
we
we
get
very
granular
iteration
written
right
a
lot
of
the
times
and
we
get
some
level
when
we
have
time
and
and
inclination
some
level
of
like
large
vision,
work
accomplished,
but
that
in
between,
like
what's
the
three
to
six
month,
vision,
look
like
that
we
can
kind
of
chip
away
at
and
when
we
come
out
of
this
iterative
loop,
we
will
have
this
like.
That's
that's
something
that
I
think
would
be
really
helpful
for
the
content
editor
discussion
as
it
moves
into
the
wiki.
A
It's
something
that
I
think
would
be
helpful
for
a
lot
of
teams,
so
not
meant
to
be
bringing
this
up
as
criticism
like,
we
should
have
done
it
because,
obviously
we're
busy-
and
this
is
something
the
whole
company
needs
to
you-
know
work
towards,
but
I
think
it
was
really
helpful.
So.
B
Thanks
for
that
feedback,
yeah
I'll
touch
more
upon
this.
Once
I
get
into
my
design
bit
because
putting
this
together
also
taught
me
some
other
things
that
I
want
to
take
forward
so
yeah
I'll.
Let
you
voice
your
last
point.
There
eric.
A
No,
you
know
I
was
just
gonna
document,
the
the
takeaway
from
the
first
point.
So
if
you
want
to
move
into
that,
the
last
point
actually
is
a
good
transition,
which
is
just
the
content.
Editor
wiki
discussion
is
tomorrow
morning,
my
time,
so
maybe
we
can
work
on
something
like
this,
for
that.
I
think
where
we
would
get
a
lot
of
benefit
from
that
is
like
framing
it
like
we,
it's
not
so
much
the
mvc
like
the
smallest
thing.
A
We
can
ship
but
the
and
it's
not
the
minimum
lovable
product,
because
lovable
implies
a
huge
amount
of
scope
and
everybody
is
really
happy
with
it.
But
when
do
we
feel
like
what
is
this
going
to
look
like
when
we
feel
like
it's
ready
for
everybody
to
use
for
real
work
like
this?
It's
the
minimum
like
complete
product
right
like
what?
What
is
this
thing
going
to
look
like
when
we
we?
We
think
it's
really
ready.
A
You
know
what
can
we
work
towards
and
that
that
strategic
vision,
rather
than
like
the
the
long-term
blue
sky
vision
is,
is
really
important.
So
you
can
take
over
and
and
chat
about
what
you
learned
from
that.
B
Yeah,
I
I
think
what
you
said
about
the
big
picture:
long-term
vision,
something
that
you've
explored
using
in
the
past
was
this
whimsical
platform
and
to
kind
of
like
map
out
where
things
will
go.
I
think
like
doing
that
kind
of
mapping,
along
with
some
kind
of
visual
side
by
side
or
like
next
to
it
at
least,
could
help
with
kind
of
that
framing
saying,
like
oh
yeah,
we're
doing
this
in
this
milestone
these
blocks
and
those
milestones
so
that
people
have
a
clear
picture.
B
Maybe
that's
something
that
we
can
like
work
together
on.
You
know
in
preparations
for
not
only
events
like
this
but
like
in
discussions
pre-milestones,
and
things
like
that
that
I
can
help
contribute
to
like.
What's
the
latest
views
on
this
like?
Where
do
we
feel
things
should
land
and
based
on
that?
Have
some
kind
of
visual
talking
points,
so
yeah
I'll
be
better
at
trying
to
get
that
sorted
for
you
in
the
future.
C
B
That
in
the
past
we
talked
about
getting
some
kind
of
vision,
stuff,
ready
and
then
comes
three
weeks
later,
and
it's
like
oh
nothing
because,
like
we
get
swamped
with
some
other
things
and
it's
deemed
less
priority,
but
I
think
it
is
a
good
practice
in
general
for
transparency
to
just
keep
these
types
of
documents
updated
wherever
that
may
be
direction,
pages,
whimsical
or
figma
or
issues
ethics.
Whatever
we
decide
to
do,
I
think
yeah
just
hold
each
other
accountable
and
just
like
little
nudges
like
hey.
B
I
need
something
because
it's
probably
for
from
my
side,
it's
just
like
a
cut
and
pace
of
multiple
worlds,
which
which
is
like
the
hard
part
right
like
because
we're
in
the
issues
we
kind
of
know
where
everything
is
but
yeah,
it's
nice
not
only
for
stakeholders,
but
sometimes
myself,
to
see
where
how
everything
gets
pulled
together.
That
said,
dealing
with
settings
and
navigation,
one
of
the
things
is
like
I'll
get
lost
in
rabbit
holes
like
you
start
attacking
one
thing,
and
then
you
start
pulling
pulling
and
then
everything
feels
connected.
B
So
you
feel,
like
I
felt,
like
I
needed
to
hand
cover
all
the
bases
before
like
presenting
it
back
or
telling
people
what's
up
and
what
I
realized
that
some
things,
for
example,
like
our
plan
to
move
the
merge,
request
approval
settings
into
its
own
thing,
but
as
part
of
that,
we
also
listed
a
bunch
of
other
things
that
could
be
done,
such
as
putting
in
the
menu
link
or
like
putting
a
link
to
merge,
request
settings
from
somewhere
in
merge
requests.
B
Things
like
that
are
like
blocking
the
bigger
thing
which
is
like
moving
the
merge
requests
out
of
general
and
into
its
own
page.
It
feels
like
those
are
very
related,
but
distinct
things
that
my
kind
of
own
personal
yeah,
probably
like
experience,
would
like
kind
of
lump
them
together
and
present
them
together
as
one
piece
versus
the
spirit
of
minimum
vial
change,
where
we
can
like
release
them
as
three
separate
issues
and
then
what
I
want
to
start
doing
is
being
more
visible
with
like.
B
Yes,
these
are
the
three
things
I
want
to
move
with,
but
these
points
here
are
like
I'm,
not
I'm
not
certain
yet,
but
we
can
probably
move
forward
with
these
other
points.
I
think
this
is
something
that's
come
up
in
the
last
two
weeks,
where
there's
strong
direction
and
understanding
of
what
things
will
be,
such
as
like
the
flyout
menu
and
what
that
label
might
be
is
another
example
where
it's
like
I
just
need
to.
We
just
need
to
make
a
decision.
B
C
B
Back
the
whole
issue
from
moving
forward,
so
I
want
to
prevent
situations
like
this,
so
at
least
I
can
pull
you
eric
in
or
roman
or
marcel
or
tech
writer,
to
help
me
kind
of
finesse.
It
or
say
don't
worry
about
this,
like
in
the
grand
schemes
of
things.
B
This
is
fine,
but
because
I
haven't
been
very
clear
with
which
areas
we're
confident
in
and
not
it's
been
kind
of
like
a
black
box
even
for
myself,
because
I
get
deeper
and
deeper
into
the
rabbit
hole
it
gets
darker
and
darker,
and
then
it
takes
me
two
weeks
to
get
out.
So
I
want
to
prevent
that
in
the
future
and
over
the
next
few
days,
I'll
be
looking
at
like
moving
along
some
issues.
B
We
have,
I
feel,
like
I
have
a
stronger
sense
of
where
things
land
there
but
yeah
for
this
week.
It's
just
wrapping
up
solution,
validations
for
setting
search-
and
this
is
where
all
the
settings
are
at
in
tabs
at
the
top,
with
a
global
settings
search
and
yeah.
Overall,
that
felt
like
it
was
well
received
and
it's
using
existing
components.
So
this
was
just
like
testing
out
the
idea
of
a
global
search
for
things
and
not
pushing
the
box
too
much
with
the
ui
or
things
like
that.
B
So
yeah
we're
leveraging
a
similar
pattern
that
we
use
for
our
global
search.
So
it's
actually
kind
of
consistent
in
in
a
nice
way.
Yeah.
C
B
Then
yeah
over
the
next
few
days,
like
I
said,
tackling
some
more
breaking
down
of
issues
and
being
more
clear
of
next
steps
and
looking
towards
solution
validation
of
web
id
tabs
and
that's
something
that
using
unmoderated
testing
is
what
I'm
aiming
for
and
being
a
little
bit
more
focused
with
my
questions
to
be
more
direct
and
around
the
solution.
Couldn't
help
turn
around
analysis
time
as
well.
So
yeah,
that's
what
I'm
looking
at
over
the
next
week.
A
The
the
element
of
breaking
those
down
into
iterations
now
that
you've
synthesized,
like
this
vast
amount
of
information
related
to
our
existing
backlog
and
our
existing
research,
is
yeah.
It's
the
great
next
step
and
I
think
we'll
have
a
lot
more
actionable
issues
coming
out
of
it
and
then
yeah.
We
can
just
prioritize
and
take
it
from
there.
C
A
A
lot
we've
done
a
lot,
especially
youtube.
I've
done
very
little,
but
we've
done
a
lot
as
a
group,
and
I
think
it's
a
natural
cadence
that
we're
following.
So
I
didn't
want
it
to
come
off
as
or
I
don't
want
you
either
of
you
to
feel
like
going
in
the
weeds
like
that,
has
been
a
deterrent
to
our
progress.
It
was
like
you
have
to
get
that
deep
to
form
opinions
and
then
come
up
and
and
break
it
down.
A
So
I
think
we're
coming
out
of
that
stage
in
a
really
good
place
and
we
can
start
making
stronger
recommendations
that
are
that
are
rooted
in
the
research
and
yeah.
I
think
it's
going
to
be
a
good
whatever
second
quarter
for
for
settings
and
navigation.
C
Yeah
yeah,
that's
a
good
call
out.
There
was
a
lot
to
dive
into
because,
honestly,
if
we
started
with
a
lot
that
was
kind
of
presented
in
the
epics
the
priority
epics
that
we
started
with,
we
wouldn't
really
have
known
a
lot
of
what
we
learned
by
now.
We
would
have
just
kind
of
had
a
the
bias
towards
action
that
is
great
after
you
kind
of
know
the
space,
and
you
know
what
are
the
key
challenges
now
we
can
have
that
bias
towards
action.
A
We
knew
we
knew
a
lot
of
the
problems.
That's
how
I
felt
like
there
were
a
lot
of
like
consistent
themes
identified
as
problem
spaces.
We
didn't
have
baseline
measurements
to
back
up
those
assumptions
and
we
didn't
have
validated
solutions
and
and
actionable
insights
that
would
make
those
problems
go
away
and
we
still
don't
have
all
of
them
covered.
A
But
you
know
like
it's
one
thing
to
just
say:
like
people
are
confused
by
the
left
nap,
you
know
it's
another
to
say
like
these
are
the
specific
things
that
are
getting
in
people's
way
and
we've
identified
repetition
that
needs
to
be
resolved
and
we've,
you
know,
identified
several
areas
that
need
to
be
renamed
and
reorganized,
and
the
fact
that
it
took
a
few
milestones
to
get.
There
is
not
surprising.
C
Agreed
awesome,
so
I
will
move
into
my
two
points.
Actually
I'll
go
with
the
second
point.
First,
because
it's
just
like
an
fyi
on
mic.
So
after
the
baseline
period
is
what
I
will
call
that
what
I'm
currently
working
on
is
evaluating
some
of
the
left
nav
proposals
that
have
resulted
from
the
research
one
is
the
more
exploratory
approach.
It's
it's
more
of
a
bold
approach
to
see
how
we
can
simplify
the
menu
structure
by
creating
these
higher
level
buckets
to
contain
all
the
different
items
that
are
on
there.
C
So
there
will
be
a
lot
of
considerations
in
there.
There
will
be
a
consideration
of
whether
those
buckets
make
sense
kind
of
the
priority
of
certain
items
that
are
currently
in
the
left.
Nav
like
do
they
all
do
they
all
need
to
be
there
per
se
or
are
there
other
points
where
they
can
be
discovered
or
other
like
pages
where
you
could
surface
it,
and
things
like
that,
so
that
will
also
come
into
that
and
then
I'm
also
doing
a
parallel.
C
There's
like
this
parallel
work,
going
on
with
dots
the
left
navigation
in
the
dots
that
I'm
working
with
them
on
doing
a
similar
baseline
measurement
of
the
experience
and
then
seeing
how
they
can
improve
the
ia
there.
So
there's
kind
of
shared
learnings
going
on
between
the
two
projects,
which
is
why
I
wanted
to
put
that
on
your
radar
as
something
that
I'm
doing
and
then
the
next
area
of
things
would
be
in
the
settings.
C
Follow-Up
research
area,
because
we
kind
of
identified
settings
operations
and
analytics
as
these
big
hot
spots
of
challenges
and
operations
is
being
addressed.
Currently,
so
I
see
settings
as
the
next
area
to
dive
deeper
into
and,
in
my
opinion,
analytics
is
a
bit
lower
in
priority,
because
settings
is
like
our
our
second
piece
of
things,
navigation
and
settings,
and
we
have
all
this
other
ongoing
work.
C
How
we
can
maintain
that
and
how
we
can
better
define
the
regions
of
navigation,
so
explain
kind
of
the
logic
behind
the
relationships
that
are
there,
so
that
other
teams
who
might
want
to
add
things
there
can
kind
of
understand
how
to
make
a
decision
on
that
behalf
and
understand
when
they
need
to
conduct
research.
So
that's,
I
guess
more
on
the
documentation
and
handbook
guidance
piece
of
things,
but
that's
another
thing
that
I
am
thinking
about.
So
I
just
wanted
to
put
that
out
there
and
if.
A
C
A
This
is
great.
I
love
this
talk
about
the
approach
to
proposing
changes
and
maintaining
it's
very
much
in
line
with
how
I
hoped
we
would
where
I
hoped
we
would
get
as
the
the
temporary
stewards
of
the
category
and
eventually
somebody
will
want
to
take
it
over.
But
it's
not
it's
a
shared
responsibility.
A
Right
like
we
don't
ever
want
to
be
gatekeepers,
but
I
do
think
we
needed.
I
felt
that
we
needed
to
approach
this
in
a
design
from
like
a
design
system
standpoint
right
like
we
need
to
have
consistent,
behavior
and
consistent
components
and
a
consistent
way
to
create
things,
and
so
I
think
we're
I'm
starting
to
circle
back
around
to
that.
Now
that
we've
kind
of
built
momentum
around
the
top
nav
and
and
we're
realigning
the
left
nav.
A
I
think
this
is
a
good
next
step
to
start
thinking
about
that
system
that
we
put
into
place
to
help
keep
things
consistent
so
documenting
in
pajamas
the
types
of
components
that
people
use
documenting
the
types
of
behaviors
you
might
expect.
But
I
think
we
could
take
this
a
step
further
and
we've
started
to
seriously
talk
about
the
idea
of
data-driven
settings
and
data-driven
navigation
and,
in
our
last
issue,
refinement
or
monthly.
I
can't
remember
where
this
came
up,
but
fran
was
discussing
the
challenges
we
have
with
moving
items
around
on
the
left
now.
A
So
I'm
looking
at
your
proposal
for
the
more
sweeping
changes
related
to
the
buckets
and
and
in
my
head,
I'm
thinking.
Oh
that's
going
to
be
challenging
because
there's
a
lot
of
logic
tied
up
in
the
left
nav
around
what
is
visible
to
who
and
and
and
when
and
like
if
the
features
turned
off.
What
is
the
other
default
view
and
his
his
take
on?
It
was
there's
a
lot
of
work
to
undo
and
untangle
that
logic.
A
If
we
took
a
couple
milestones
stepped
back
and
built
a
framework
that
people
could
use
to
more
consistently
build
the
left
nav
then
something
tackling
something
like
this
would
be
a
lot
easier
and
maintainable.
So
I
guess
put
in
another
way
we
could
look
at
this
epic
and
we
could
just
execute
on
it
right
and
then
we
would
untangle
some
code,
but
we
would
largely
be
punting
on
the
that
is
making
it
hard
for
everybody
to
contribute
consistent,
behavior
to
the
left
nav.
A
So
if
we
took
a
page
from
the
geo
handbook
and
built
a
self-serve
framework,
that's
well
documented
and
you
had
a
data
file
that
essentially
described
the
behavior
of
your
left
nav
item.
It
would
be
a
lot
easier
to
write
a
handbook
page
that
said
like,
if
you
want
your
thing
to
do
this
write
this
code
and
here's
maybe
a
template.
You
can
go
off
of
versus
like
having
to
write
a
hamil
file
for
your
your
navigation
item
and
you
know,
make
sure
you're
you're
implementing
it
consistently.
That's
that's
a
lot
more
overhead.
A
Similarly-
and
this
is
actually
something
we
were
talking
about
for
settings-
and
I
know
we're
over
so
I
don't
want
to
keep
us
too
long,
but
I
have
an
epic
that
we're
just
starting
to
discuss
like
what
that
would
look
like
for
settings,
and
I
think
some
of
the
larger
things
we
want
to
solve
for
settings
are
almost.
A
Dependent
on
us
solving
a
data-driven
settings
model,
because
then
we
can
experiment
a
lot
more
readily.
We
can
scale
a
lot
more
easily
and
people
can
be
the
owners
of
their
settings
without
having
to
worry
about
how
the
view
is
structured
and
they
can
just
focus
on
the
functionality
of
their
settings
and
let
the
system
and
the
framework
determine
where
those
are
available
and
what
they
look
like
and
how
they
behave.
A
C
Yeah
that
that
was
really
great
context.
I'm
I'm
excited
to
hear
all
of
that,
because
yeah
that's
why
I
want
to
get
get
ahead
on
evaluating
these
proposals
to
see
if
it's
something
that
could
potentially
hold
up
or
be
a
a
direction
we
go
for
the
future,
then
we
want.
We
would
want
to
keep
that
in
mind,
because
that
would
involve
so
much
reorganization
and
change
that
yeah.
We
would
have
to
be
prepared
for
that.
A
Yeah
and
I
I
think
the
goal
would
be
to
to
empower
groups
to
run
experiments
and
run
a
b
tests
and
not
have
to
worry
so
much
about.
Am
I
going
to
break
something
by
introducing
this
new
menu
item
it
should
be.
It
should
be
easier
for
us
to
figure
this
out
right
for
us
collectively
to
work
on
the
left,
nav
and
if
we
want
to
run
an
experiment
where
some
people
are
getting
persona-based
or
activity-based
navigation
and
hiding
certain
elements
based
on
context
or
something
more
dramatic
things.
A
From
before
I
joined
the
effort,
but
if
we
wanted
to
do
those
things
like
their
massive
efforts
just
to
put
that
in
place,
given
our
current
structure,
but
if
we
could
lower
that
bar
so
that
the
growth
team
could
tackle
it
or
the
growth
team
in
conjunction
with
another
group
could
could
write,
could
build
an
experiment
more
quickly.
A
We
could-
I
don't
know
it
might
it
might
be
too
ambitious,
but
I
hearing
friend
talk
about
it.
The
other
day
in
relation
to
the
left,
nav
felt
very
similar
to
how
I
was
thinking
it
would
work
for
settings,
and
I
think
we
could
probably
start
with
the
left,
nav
and
learn
from
it
before
we
apply
that
to
the
settings.
B
Cool
all
right
before
we
go
this
whole
talk
of
like
future
documentation
and
all
this
stuff,
we
actually
have
an
opportunity
to
start
working
on
some
documentation,
I.e
the
top
navigation,
because
that's
getting
changed
in
14.00.
B
There
is
already
like
a
area
within
pajama
that
talks
about
navigation,
where
what
I
would
like
to
do
over
the
next
few
milestones
is
start.
Yeah.
Contribute
is
like,
like
fixing
that,
like
updating
that
document,
what
my
vision
for
this
is
explaining
the
rules
of
like
how
many
action
items
should
be
in
there.
B
You
know
why
things
are
laid
out
how
they
are
and
like,
if
you're
a
team,
and
you
want
to
add
more
items
into
there-
that's
probably
where
we're
going
to
start
putting
some
rules
and
recommendations,
and
this
is
probably
where
I'm
going
to
look
for
your
help.
Eric
and
catherine
to
say,
like
you
know,
what
should
the
rules
be
around
the
top
nav,
but
at
the
same
time
this
is
also
an
excellent
opportunity
to
start
incorporating
user
research
into
pajamas
as
well,
more
prevalent
as
in,
like
we
can
surface
like
a
block
in
there.
B
So
it's
like
this
decision
was
also
made
by
this,
like
kind
of
general
insight
that
we
found
in
this
solution,
validation
or
research
validation.
Why
we
decided
to
group
things
like
this
or
like
section
things
off
like
this.
So
I
think
this
is
a
near-term
opportunity
for
us
to
start
like
exercising
this
muscle
of
documenting
before
we
get
gran's
game
on
the
left.
Now,
because
that's
a
that's
a
bigger
beast.
C
A
Thanks
great
well,
I
kept
you
all
too
long
thanks
for
it's
always
great
to
talk
to
you
and
we
will
follow
up
more
and
talk
more
about
all
these
concepts
in
our
next
sink
and
obviously
within
slack
and
in
the
issue.
So
until
next
time-
and
oh
also,
you
know
given
daylight
savings
time,
we'll
keep
chatting
on
slack
about
a
new
time
for
this
meeting
that
works
for
everybody,
but.
A
C
A
minute
I
forgot
about
it,
it
was
the
first
one,
but
I
I
think
michael
might
have
commented
below
about
whether
there's
any
existing
data,
because
I
know
in
general
we
we
will
probably
have
an
initiative
around
tracking
usage
for
the
whole
menu.
But
if
there's
any
existing
tracking
data,
that
would
be
interesting
to
look
at.
A
You
know,
I
don't
know
of
your
of
like
a
direct
answer
for
that
right
now,
I'll
have
to
look
into
it.
I
don't
know
of
any
events
right
now.
A
Sounds
good,
but
I
I
remember
we
talked
about
this
in
in
the
issue
refinement
and
it
was
relatively
low
effort
to
get
basic
tracking,
but
I
was
concerned
that
the
basic
tracking
wouldn't
give
us
the
insights
we
were
looking
for
as
far
as
like
the
behavior.
That
michael
was
proposing
or
like.
Are
you
clicking?
Which
path
are
you
clicking
and
whether
it's
the
collapse
state
or
not
like
there's,
there's,
there's
things
actually
on
this
one
that
we
could.
A
Maybe
this
is
a
great
topic
for
next
time,
but
we
could
really
benefit
from
some
basic
user
tracking
and
then
additional
like
actual
moderated
or
you
know,
like
just
observational
testing,
just
like
watching
users
interact
with
the
left
nav.
Maybe
I
don't
know
if
our
user
testing
platform
has
screen
recording
or
not,
but
like
actually
watching
their
mouse
go
back
and
forth,
but.