►
From YouTube: Create:Editor Product/UX Weekly - 2021-01-06
Description
Weekly Editor group sync between Product, Design, and UX Research
A
So
we
I
don't
have
much
on
the
product
side
that
I
really
want
to
highlight
that's
more
important
than
the
topics
you've
already
listed
in
the
agenda,
but
I
did
want
to
just
call
out
that
I
I
do
have
an
opportunity.
Canvas
review
next
week
scheduled,
I
believe
from
monday
evening
my
time
and
that's
to
cover
the
rich
text,
editing
architecture
that
we've
been
proposing
for
months
and
talking
about
and
sort
of
formally
present
that
to
product
leadership
and
and
design
leadership.
So
I'm
excited
to
get
the
feedback.
A
I
don't
expect
it
to
be
all
that
like
controversial
or
I
don't
expect
them
to
disagree-
that
we
should
invest
in
this,
but
it'll
be
good
to
get
the
feedback
and
and
get
sort
of
the
official
go
ahead.
I'm
excited
to
sort
of
show
our
work
and
I'm
sure
that
will
be
recorded
and
we'll
we'll
share
that
in
slack
when
it's
over
and
with
that
I'll
turn
it
over
to
michael
for
design,
stuff.
B
Oh
yeah,
so
I
guess
the
first
one
is
actually
more
of
a
ux
research
one,
but
the
solution
navigation
for
top
nav.
I
wrapped
that
up
on
monday.
So
please
review
that
issue
and
like
the
the
findings
from
there
before
I
kind
of
share
it
more
publicly.
So
I
pinged
catherine
yourself,
eric
and
and
marcel
and
roman
and
yeah
just
some
feedback
on
the
points
there
would
be
good
and
then,
if
it's
cool,
then
I'll
publish,
let
other
people
know
about
it.
Its
existence
yeah.
B
I
guess
the
tough
part
for
that
for
me
was
just
like
trying
to
formulate
the
fine
findings
into
insights
and
like
just
shaping
the
words
so
yeah.
I
think
it
was
like
christmas
time
it
was
like
slow
with
some
piecing
sentences
together,
so
yeah
after
the
break.
I
was
surprised
like.
Oh
the
words
go
like
this,
so
that
was
good.
I.
C
B
Help
with
one
thing
eric
in
our
last
chat
with
a
with
roman
and
yourself.
There
was
like
a
point
that
roman
mentioned
that
I
should
start
looking
into
for
this
for
the
editor
like
editing,
kind
of
like
flows
or
something,
but
I
couldn't
find
it
in
the
meeting
notes
and
it
was
like
some
kind
of
not
a
thing
big
thing,
but
it
was
like
thinking
with
the
road
map
of
what
things
should
look
like,
but
I
forgot
exactly
what
that
was.
B
So,
if
you
could
remember
what
we
talked
about,
that
would
be
great.
A
Yeah,
we
don't
record
those
either
do
we.
We
talked
about
I'm
looking
at
the
agenda
now.
A
Feels
like
a
year
ago,
I'll
have
to
get
back
to
you
on
that.
I
I'm
sure
there's
some
some
vision.
Work
on.
It
probably
was
related
to
the
rich
text,
editing
and
like
maybe
the
toolbars,
but
I'm
not
super
confident
in
that
answer.
So
I'll
have
to
go
back
in
the
agenda
and
jog
my
memory
a
little
more.
A
C
A
All
looks
great,
I
didn't
actually
click
through
all
of
them
yet
in
dovetail,
but
it
feels
pretty.
A
A
My
request
would
be
over
the
next
week
or
so,
if
you
and
I
could
collaborate
on
making
very
clear,
like
epic
and
iterative
steps
towards
getting
to
the
consolidated
menu,
because
I'm
I'm
not
sure
if
we'll
have
room
to
pick
that
in
13
9,
but
in
1310.
I
think
that
should
be
our
our
main
focus.
It
seems
like
we
should
do
that.
A
It
does
seem
to
help
with
discoverability
and
and
reduce
the
overhead
when
you
combine
the
project
and
group
menu
items,
if
you
feel
confident
confident
enough
in
the
solution
to
start
writing
out
those
proposals,
we
can
work
on
that
over
the
next
week
or
so
and
start
picking
those
apart,
maybe
there'll
be
some
technical
discovery
or
issue
refinement
or
something
that
we
can
do
in
13.9.
To
make
sure
we're
set
up
to
hit
the
ground
running
in
1310.
B
Cool
that
sounds
good
yeah
I'll,
create
some
an
epic
for
that
there's,
probably
finding
details
that
would
require
a
little
bit
more
refinement.
So
that's
good!
Oh
yeah,.
A
C
Yeah,
I
also
read
through
them,
and
I
watched
the
different
video
clips
as
well.
It
was
very
interesting,
the
feedback
that
was
coming
in.
I
I
personally
agreed
a
lot
with
what
they
were
saying
about
how
kind
of
reveals.
C
Basically,
what
was
under
more
like
you
kind
of
see
more
of
those
options
all
at
once,
which
I
thought
was
interesting,
because
what
I
was
noticing
in
the
study
that
I
ran,
which
was
just
basically
a
benchmarking
study.
It
was
just
see
how
people
are
interacting
with
the
top
navbar
if
they
are
interacting
with
it.
If
there
were
any
challenges
they
were
running
into,
and
things
like
that
and
what
I
was
just
kind
of
noticing
going
through
that
study
is
that,
depending
on
what
they
were,
what
they
needed
to
do.
C
It
was
kind
of
like
hovering
over
projects
or
hovering
over
groups
or
kind
of
going
back
and
forth,
and
then
remembering,
oh
okay,
I'm
looking
for
a
group.
So
then
I'll
go
to
this
one,
that's
kind
of
like
when
I
was
thinking
of
that
study
and
how
they
kind
of
go
back
and
forth,
and
then,
if
it's
not
in
there.
Okay,
maybe
I'll
check
under
more.
C
Thinking
about
the
task
again
and
then
clicking
through
again,
so
that
was
interesting
to
see
between
the
two
studies,
a
similar
pattern
coming
out
and-
and
since
my
next
point
was
about
this
as
well
I'll,
just
continue
on
with
some
things
I
had
noticed
and
something
I
noticed
was
around
just
the
different
types
of
search.
C
I
think
it'd
be
interesting
to.
I
guess-
observe
this
more
naturally
in
a
setting
where
they're
not
completing
tasks
that
maybe
they
don't
do
in
regular
time,
but
they
definitely
had
to
think
again
about
okay.
Am
I
trying
to
search
for
something
at
the
project
level
at
the
group
level?
Or
is
it
global,
it's
kind
of
like
an
active
thought
about
where
to
go,
and
then
sometimes
they
would
go
to
one
of
those
drop
downs
and
then
remember,
oh,
I
can
only
search
for
the
group
name
or
project
name
here.
C
Let
me
go
to
the
global
search
and
or
they
would
say,
okay
now,
I'm
going
to
go
click
on
explore
projects
and
then
do
the
search
on
that
page.
I
felt
like
there
were
kind
of
a
lot
of
different
apps
leading
back
to
one
spot
or
another,
so
I
do
think
exploring
this
consolidation
path
will
be
really
interesting.
C
I
don't
know
if
this
is
a
specific
task
or
if
there's
something
that
applies
more
broadly,
but
searching
for
the
getlab.org
group
in
particular
was
a
very
difficult
task,
one,
it's
something
that
they
don't
often
do,
but
they
kind
of
had
to
think
about.
Okay,
where
to
search
for
it,
they
go
on
the
search
page.
They
can't
find
the
project
name
there,
so
they
try
to
sort.
Maybe
I
sort
by
name
or
I
try
to
trace
my
steps
back
in
some
way,
so
there
was
just
something
around
the
search
being
off.
C
That
kind
of
showed
up.
I
think
in
both
studies,
so
it
was
interesting,
let's
see
but
yeah,
so
I
also
have
shared
the
dovetail
findings
here.
Feel
free
to
read
more
into
that,
but
I'm
not
I'm
not
sure,
michael.
Maybe
we
can
talk
about
this
in
our
next
meeting
kind
of
how
how
you'd
like
to
go
deeper
into
these
findings
or
if
there
are
any
parts
of
your
study
that
you
thought
you
might
want
to
compare
with
my
study.
C
Just
let
me
know-
or
we
can
focus
more
on
where
to
go
from
the
solution,
validation
so
from
the
things
that
you
would
learn
how
to
break
it
down
into
something
that
we
can
start
to
iterate
on.
Let's,
let
me
know
how
you
kind
of
want
to
navigate
this
okay,
I
didn't
mean
to
say
navigate,
but
I
said
it
anyway,
but
yeah,
and
then
the
last
thought
there
oh
was
around
the
breadcrumb.
C
C
C
B
B
A
Yeah
I
mean,
I
think,
there's
one
thing
that
we
can
probably
tee
up
as
our
next
big
exploration.
Well,
two
things
one
would
be
the
the
left,
sidebar
navigation
information
architecture,
I'd
like
to
get
to
that
once
this
is
wrapped
up
and
then
the
next
would
be
that
that
question
you
were
just
asking
about
whether.
A
A
I
think
that
there's
enough
evidence
that
that's
like
not
going
to
be
consistent
and
reliable
enough,
it's
also
potentially
relatively
like
unintuitive,
is
the
wrong
word,
but
like
hidden,
you
know
it's
not
it's
it's
something
you
need
to
discover,
so
it's
even
as
the
primary
way
to
do
it.
It
might
not
even
be
the
best
way,
but
I'd
like
to
keep
pushing
on
that
and
see
if
we
can
solve
the
problem,
because
the
problem
is
real,
as
you
just
described
like
people
do
have
problems
with
this.
C
Yeah
and
I
I
will
say
that
so
for
the
left
side
bar,
so
I'm
currently
now
in
the
process
of
documenting
the
findings
from
that
group
level
test
and
then
we'll
run
the
project
level
test.
So
I
plan
to
get
that
done
in
this
milestone
as
well.
C
There
was
also
the
op
study
I
kind
of
need
to
take
in
what
we
learned
from
the
op
study,
but
basically,
after
that
top
navbar
benchmarking
study,
it
seems
that
the
left
sidebar
is
kind
of
the
hot
spot
of
everything,
because
while
it
was
a
study
that
was
conducted
with
experienced
gate
lab
users
similar
to
the
solution,
validation,
the
top
navbar
was
more
straightforward.
The
feedback
was
kind
of
like
yeah,
you
know.
C
Sometimes
it
took
me
longer
to
get
to
where
I
needed
to
go,
or
I
knew
I
needed
to
find
snippets,
but
it
was
hidden
behind
either
more
or
this
plus
sign,
but
I
eventually
found
it
it.
Doesn't
it
didn't
have
the
same
sort
of
challenges
that
I've
heard
about
the
left
sidebar.
So
that's
what
that's
something
that
stuck
out
to
me
about
the
studies,
though
the
next
focus
of
the
left.
Sidebar
will
be
more
challenging
and
very
important,
but
we'll
get
there.
A
Yeah
I
saw
the
discussions
on
the
the
operations
one
related
to
the
study
and
the
findings
there
about
the
the
fact
that
the
the
test
they
were
running
showed
like
a
concrete
and
clear
improvement
in
bringing
some
of
those
items
out
of
the
left
side
or
out
of
the
operations
menu
into
the
left
nav
at
the
top
level,
so
yeah
taking
what
they
learn
there
with
whatever
you
you
know
benchmark
on
yours.
I
think
there's
a
lot.
We
can
do
to
improve
the
experience
there,
but
it's
going
it's
gonna.
A
It's
gonna,
be
a
multi-faceted
conversation.
C
Yeah
because
I
think
in
the
op
study
it
was
basically
kind
of
like
okay,
so
this
proposal
to
move
items
out,
we
can
move
forward
with
that,
but
the
task
success
rate
in
the
study
was
much
lower
than
anticipated,
so
that
just
pointed
to
even
more
problems
like
in
a
general
sense.
So
that's
something
that
I'll
be
able
now
that
I
got
this
top
navbar
study
kind
of
squared
away,
but
I'll
be
able
to
dive
more
into
that.
So
we'll
see
very.
A
C
A
C
B
Oh
yeah,
so
so
the
last
one
is
solution,
validation
for
settings.
I
think
there's
already
a
few
solid
ideas
from
our
group
from
where
we
might
want
to
take
this
because
over
the
next
couple
of
days,
I'm
just
going
to
break
that
down
to
see
what
we
can
do
around
solution.
Validation
like
if
we
can
get
some
stuff
done,
un
moderated
versus
moderated
and
whether
that
would
be
sufficient.
B
C
B
Cool
awesome
yeah,
I
think,
with
the
benchmarking,
is
going
to
be
interesting,
because
this
might
be
a
time
when
we
run
a
little
bit
with
our
instincts
and
then
see
if
our
benchmarking
fits.
So
when
we
create
our
benchmarks,
I
guess
we
should
try
to
be
super
unbiased
because
we'd
probably
be
biased
by
the
time
we
get
to
like
stating
what
our
benchmarks
are.
C
Yeah
exactly-
and
I
think
it's
in
the
case
of
navigation,
we
at
least
have
a
lot
of
feedback,
so
we
we
can't
be
well,
we
might
be
biased
by
feedback,
but
we
can't
be
too
crazy,
like
unbiased,
and
we
know
what
the
problems
are.
The
benchmarking
is
kind
of
like
seeing
it
in
action,
so
our
solutions
come
from
somewhere
at
least
which
makes
me
feel
better.
C
A
As
always,
I
appreciate
all
your
efforts
with
the
with
research
and
all
these
user
interviews
and
collating
insights
and
things
like
that.
It's
really
helpful
and
yeah.
I'm
excited.
I
think
we
have
a
lot
of
great
work
to
tee
up
in
the
beginning
of
this
year
and
I'm
gonna
be
working
on
thirteen
9
planning
in
earnest
a
little
bit
more,
the
second
half
of
this
week.
A
C
Yeah
and
I'm
thinking
that
as
we're
getting
more
of
these
insights
kind
of
pulled
together,
we
either
can
maybe
make
a
deck
or
something
to
kind
of
play.
The
story
out
a
bit
more
and
highlight
what
changes
might
come
out
from
it,
or
maybe
an
epic
or
just
something
that
pulls
them
all
together
towards
the
end
of
the
quarter
slash
month,
which
is
basically
the
same
thing
right
now.
C
A
Yeah,
I'm
just
trying
to
think
if
a
deck
or
maybe
even
like
a,
I
don't
know,
we
should
find
a
way
to
communicate
this.
Maybe
it's
even
in
the
form
of
like
a
group
conversation
or
something
like
that
where
we
can
just
combine
everything.
Maybe.
A
Show
what
we
have
ships
show
what
we
plan
to
ship.
What
are
the
outcomes
that
might
be
valuable?
A
I
think
there's
many
many
people
that
are
interested
and
would
be
would
appreciate
a
sort
of
summarized
view
of
this
and
potentially
a
venue
to
ask
questions.
So
I
think
that
sounds
good.
A
I
did
just
remember
one
thing,
michael.
I
pinged
you
in
an
issue
that
came
up
related
to
the
new
visual
pipeline
editor
and
some
you
may
have
seen
the
comments.
There
were
a
sort
of
a
pair
of
issues,
one
related
to
making
it
like
prompting
users
when
they
come
to
the
web,
ide
and
they're,
trying
to
edit
the
ci
file
that
we
have
a
pipeline
editor
and
then
the
other
was
like
eventually
making
it
the
default
way
to
edit
a
ci
file.
So
there's
some
great
conversation
in
those
issues.
A
If
you
want
to
take
a
look,
but
the
gist
of
it
was
we're
reopening
this.
This
discussion
about
like,
if
you
have
multiple
editing
options
on
a
file,
what's
the
best
way
to
present
that
to
users?
Is
it
a
combined
split
button
where
you
click
on
it?
It
shows
you
three
different
options,
or
is
it
we
pick
a
primary
cta
and
then
find
a
way
to
show
secondary
options.
A
B
Cool
sounds
good.
I
also
noticed
there
were
some
other
issues
out
there
that
floating
and
someone
called
the
the
normal.
C
A
Yeah
anyway,
I
think
that's
about
it
for
me
and
I'll.
Let
you
carry
on
with
your
days
and
I'll
I'll
chat
with
you
all
next
week
and
if
you're
not
or
or
sooner,
if
you're
in
the
social
call
tomorrow
morning,
my
time,
so
I
will
stop
the
recording
and
thanks
for
thanks
for
joining
talk
to
you
all
soon
happy
new
year
again.