►
From YouTube: Create:Editor Product/UX Weekly - 2020-12-03
Description
Weekly Editor group sync between Product, Design, and UX Research
A
All
right,
hello,
everyone-
this
is
the
weekly
product
and
design
and
ux
research,
sync
call
for
the
editor
group,
so
we'll
jump
right
into
the
agenda.
I
want
to
leave
as
much
time
as
possible
for
design
and
research,
because
that's
the
crux
of
what
I
think
has
been
going
on,
but
one
thing
I
did
want
to
chat
with
you,
michael
about,
was
in
relation
to
the
ux
okr
around
improving
our
sus
score.
I
guess
catherine,
this
is
relevant.
B
A
To
you,
too,
but
I
think
the
the
ask
was
for
me
to
prioritize
issues
on
this
list.
We
don't
actually
have
that
many
that
were
on
that,
like
that
first
pass
from
the
ux
team
that
included
the
label
that
would
qualify
for
this
okr.
So
we
discussed
on
a
product
call
earlier
this
week
that
we
should
go
back
and
retroactively,
look
at
13.6
and
anything
we
have
already
prioritized
for
13.7
and
see
if
we
would
classify
any
of
those.
We
can
do
this
async,
but
michael.
A
If
you
could
just
look
at
the
ones
I
suggested
or
any
of
the
links
in
the
agenda
to
some
searches
that
filter
just
our
issues
and
see,
if
you
think
they
qualify
for
the
okr
catherine,
you
could
do
the
same
because
it's
about
sus,
if
you
know
what
would
be
qualified
as
a
sus
driver
and
and
system
usability
score
for
so
I'm
not
using
acronyms,
but
the
the
gist
of
this
is
we
want
to
like
try
and
close
as
many
of
these
as
we
can.
A
A
Obviously,
if
we
could
help
exceed
that
by
saying
that
we
addressed
usability
on
our
own,
that
would
be
great
and
I'll.
Try
and
prioritize
at
least
one
or
two
and
thirteen
eight.
Some
of
the
stuff
we're
doing
on
settings
in
nav
anyway,
was
on
the
list,
so
hopefully
we'll
be
able
to
address
this.
A
Similarly,
we
can
discuss
this
async,
but
I
had
posted
in
slack
a
proposed
structure
for
our
epics
and
categories
and
trying
to
organize
all
this.
You
know
it's
there's
a
lot,
I'm
basing
it
heavily
off
of
what
we
did
for
static
site
editor,
and
I
thought
that
worked
pretty
well,
but
one
of
the
questions
was
whether
or
not
it
even
makes
sense
to
have
an
epic
or
issues
related
to
customer
insights
or
if
your
preference
would
be
to
keep
that
all
in
dovetail
anyway.
A
B
C
B
The
insights,
what
that
usually
comes
out
of
as
like
actionable
insights
from
like
the
dovetail
studies,
so
those
exist
in
like
doing
solution,
validation
or
problem
validation
and
the
outcomes
of
those
to
to
force
people
to
take
action
rather
than
just
leaving
them
in
a
dovetail.
What's
what
the
research
team
has
suggested
is
converting
those
insights.
You
know
like
insights,
that
you're
going
to
do
something
on
or
like
iterate
on
those
become
actionable
insights.
B
So
there's
a
label
for
actionable
insights,
and
I
don't
know
how
that
kind
of
like
fits
in
with
this
because
it'd
be
like.
Let's
say
it's
improved
xyz,
so
whether
that
goes
in
insights.
Like
I
explicit
epic,
we
might
not
need
that.
It
might
just
be
like
bucketed
under
something
else,
but
it
gets
tagged
so
how
that
gets
surfaced.
That's
probably
a
different
question.
Like
are
you
looking
at
this
as
a
board?
B
A
Yeah,
so
I
guess
I
was
thinking
that
that
makes
a
lot
of
sense.
I
guess
I
was
the
way
I
hoped
to
use
it
for
static
site.
Editor
was
more
like
if
I
end
up
having
a
call
with
a
customer
or
a
user
or
or
even
an
internal.
You
know
gitlab
team
member
that
has
been
using
the
static
site
editor.
I
would
document
the
conversation
or
any
notes
I
took
maybe
even
linked
to
the
video
or
something
like
that
and
it
feels
like.
A
Yeah
I
mean
I
guess
in
in
the
worst
case,
if
we
ever
move
away
from
dovetail,
we
can
export
and
create
issues
for
individual,
like
pages
from
there.
So
I'll,
probably
not
push
too
hard
to
have
that
as
a
separate
like
part
of
our
structure
in
our
categories
and
and
try
it,
and
if
I
ever
need
it
again,
we'll
revisit.
B
C
B
C
Yeah
I've
seen
it
done
both
ways
and
I
personally
yeah
would
recommend
the
dovetail
approach,
because
I
like
the
the
tagging
and
how
you
can
organize
and
then
get
the
transcription,
but
it's
also
fine.
If
you
want
to
keep
it
in
your
lab
as
well,
we
don't
at
least
the
research
team
doesn't
have
a
policy
one
way
or
another.
A
A
Like
potentially
interviews
serving
as
problem
validation,
or
something
like
that,
where
we
might
want
to
organize
them
differently
so
anyway,
we
can
move
on
from
that
that
that
answers
my
question
I'll
turn
it
over
to
michael
and
catherine
and
talk
about
research
and
design
efforts.
Most
mostly
it
looks
like
chad's,
got
a
great
question
that
I
meant
to
answer
in
slack.
So
I'm
done
talking
take
over.
D
After
okay
sure
so
yeah.
B
D
I
have
too,
because
I'm
hopefully
finally
going
to
get
soon
merged
to
the
mr,
where
I'm
at
new
ones
around
the
the
projects,
the
groups
drop
down
and
yeah.
When
I
asked
all
a
lot
of
people,
it
wasn't,
they
mostly
said
well.
Yeah
the
product
managers
usually
just
make
some
dashboards
to
show
this
stuff.
So
I
don't
know
if
there's.
B
D
Some
or
we
need
to
make
them
and
if
we
need
to
make
them
there
should
probably
be
some
planning
around
that,
like
different
ones,
for
the
different
areas
of
focus
that
our
group
has-
and
I
think
I
have
you
know
enough
experience
in
science
and
some
examples
to
help.
Do
that.
Other
people
on
the
team
don't.
But
I
just
need
to
know
what
direction
to
go
and
if
we
already
have
one.
B
Okay,
okay
cool
the
answer
to
this,
then,
is
we
probably
have
to
make
it
ourselves,
because
I
remember
that
when
the
growth
team
was
looking
at
the
top
navigation
and
they
were
like
adding
all
the
like
tracking
on
that,
they
added
all
the
tracking
and
there
was
a
separate
issue
to
create
an
analytics
dashboard.
On
top
of
that,
I
was
just
curious
whether
that
was
already
created
or
like.
B
How
do
I
jump
in
and
add
like
the
additional
more
button,
which
is
something
in
that
derrick
looked
at
so
I
was
like
okay.
Maybe
we
can
start
looking
at
some
of
those
stats,
but
off
the
back
of
that
I'll.
Try
to
find
that
issue
and
I'll
bring
you
on
that
one
chad
and
then
eric.
C
B
I
agree
we
probably
have
to
set
aside
some
time
in,
like
a
milestone,
say:
okay
like
during
this
month.
So
let's
take
a
look
at
this,
whether
that's
done
by
you,
chad
or
eric
or
myself-
that
I
think
that's
for
for
grabs
for
everyone,
but
yeah
if
you,
because
that
would
be
really
helpful
for
cross-referencing
some
of
the
stuff
that
we're
doing
with
the
top
nav,
like
whatever
changes,
would
bend,
introduce.
D
And
I
think
that'll
be
a
good
opportunity
to
get
some
more
clarity
around
what
exactly
we're
asking
for
and
what
we
can
can't
get
because,
for
example,
user
identify
metrics
are
hard
getting
stuff
from
on-prem
is
harder.
It's
like
a
whole
different
system
and
there's
like
how
do
we
present
these
like?
Are
they
aggregated
over
what
period
of
time
and
what
areas
sometimes
mean
we
may
want
to
like
pull
in
existing
metrics
that
are
already
there
like?
I
know,
there's
still
that
the
growth
team
has
instrumented
some
stuff
on
around
various.
A
D
A
I
was
going
to
answer
your
question
slack
I'll,
do
it
now,
but
the
the
answer
that
you
gave
is
correct
that
we
probably
will
have
to
do
it
ourselves.
I
can
ask
the
the
growth
team
if
they
ever
instrumented
it.
I
found
a
link
to
this
work
in
progress.
A
Periscope
dashboard
that
versailles
dashboard,
that
I
don't
have
access
to
or
is
just
going
to
their
home
page.
So
maybe
they
deleted
the
dashboard
and
created
a
new
one.
If
it
doesn't
already
exist,
we
would
have
to
create
one.
I
have
a
sequel
book
on
my
shelf
because
it's
not
my
strong
suit.
I
need
to
brush
up
on
it
and
see
if
I
can
figure
out
how
I
can
kind
of
run
these
queries
on
my
own,
but
you
know
that's.
A
We
do
have
some
existing
dashboards
for
other
categories
like
snippets
and
obviously
we
had
one
for
static
site
editor
and
there's
one
for
web
ide.
So
for.
A
Categories
as
we
instrument
things,
we
will
probably
add
to
existing
dashboards.
But
I
don't
know
if
there's
one
already
for
like
the
nav.
B
D
A
B
Cool
I'll
take
that
as
a
covered.
C
B
Then
the
point
that
I
had
was
like
for
the
key
results
around
this
improving
settings
and
navigation
for
for
this
quarter.
I
gave
an
update
on
that
issue
and
I
addressed
some
of
the,
like,
probably
the
concerns
from
senior
stakeholders
around
movements
of
issues.
At
the
moment
I
couldn't
find
any
that
we
officially
closed
as
part
of
settings
and
navigation.
B
B
I
think
the
rest
of
the
month
will
handle
some
of
the
ux
research
and
ux
work,
which
will
pave
way
for
more
executional
development
work,
because
I
think
we're
still
deciding
what
we
want
to
do.
C
B
That's
why
we're
doing
solution
validation
that
starts
next
week
on
the
top
nav
and
we're
setting
up
some
stuff
for
settings
which
we
had
a
discussion
earlier
this
week,
eric
and
myself
and
enrollment,
and
then
and
catherine
and
I
separately,
about
the
kind
of
the
general
direction
and
the
goal
for
me
started
next
week
is
probably
formalizing
some
of
that
stuff
and
then
getting
feedback
from
designers,
but
also
starting
recruitment
for
the
settings
and
solution
validation.
B
C
B
B
And
I
think
that's
fine.
Okay.
Some
point
is
like
that
frequently
visited
thing
that
that
probably
opened
up
the
more
conversation
of
like.
Should
we
be
using
recently
field
projects
and
then
like,
where
should
we
use
them
and
it
actually
opened
up
a
lot
of
doors
and
opportunities
elsewhere
in
the
product
to
potentially
solve
some
other
three-year-old
problems?
So.
A
That
sounds
great
and
we
were
actually
just
discussing
before
you
joined
kathryn
and
I
about
usertesting.com,
and
if
we
can
in
any
way
use
that
to
speed
up
our
recruitment
and
and
get
these
through.
Hopefully,
you
know
there's
at
least
a
few
people
on
there
that
aren't
taking
time
off
for
the
holidays,
but
totally
understandable
if
it
slows
down
a
little
bit,
I'm
glad
that
we're
getting
ready
to
start
next
week.
A
I
think
the
goal,
in
my
mind,
is
like
let's
get
as
much
as
we
can
as
many
insights
as
we
can
in
137,
so
that
we
have
some
actionable
work.
We
can
schedule
for
13
8,
at
least
to
begin
work
in
138
right
like
even
if
we
can't
ship
something
fully.
A
Hopefully
at
least
one
part
of
the
solution.
Validation
that
you
run
is
like
a
clear
win
and
we
can
just
chip
away
at
them,
because
obviously
you're
testing
a
lot
of
really
amazing
things,
we're
going
to
break
them
down
into
iterative.
You
know
releases
anyway,
so
maybe
there's
like
one
iteration
that
we
can
get
in
13,
8.
C
C
We
have
some
people
trickling
in,
but
I'm
not
sure
how
many
have
scheduled
yet
with
michael
and
then
I
also
need
to
schedule
my
own
so
getting
recruiting
moving
and
then
it
should
be
pretty
straightforward,
at
least
for
the
moderated
ones.
You
know
run
the
sessions
analyze
the
results,
so
I'm
still
I'm
still
feeling
that
it'll
be
wrapped
up
by
end
of
thirteen
seven
but
I'll.
Let
you
know
if
it'll
slip.
D
So
I
just
wanted
to
add
on,
like
you
said
that
that
snowplow
link
that
you
had
was
broken.
So
I
added
in
the
one
that
I
didn't
put
in
the
select
thread
and
it's
another
one
that
doug
stahl
from
the
growth
group
had
pointed
me
to.
D
I
don't
think
it
may
be
related
to
anything
we
want,
but
it
is
something
that
is
pulling
snowplow
data
and,
in
my
experience
like
just
finding
the
right
tables
to
pull
the
data
from
is
like
percent
of
the
battle.
So
even
if
that's
not
the
right
events,
it
at
least
tells
us
where
to
find
the
events
and
after
that
it
should
be
pretty
easy
to
write
whatever
we.
A
A
Yeah,
that's
awesome
thanks
most
of
my
work.
In
writing.
Any
code
comes
from
starting
from
someone
else's
and
replacing
variables
and
and
events,
because
I
I
need
that
template
that'll
help
a
lot.
D
Yeah
there's
just
like
hundreds
of
these
tables,
with
no
description
or
or
data
dictionary
that
I
know
of
and
stole
power,
and
it's
just
figuring
out
the
right
ones
to
look
in.
A
Cool,
well,
I
think
that's
about
it
for
the
agenda
anything
else
we
so
our
weekly
call
this
week
on
the
the
editor
group
was
our
social
one.
So
there
wasn't
anything
to
carry
over
to
discuss
like
tactically.
I
think.
A
The
only
thing
to
chat
about,
I
guess
michael,
is
we're
probably
trying
to
try
and
get
ahead
of
the
game
with
13
8
and
13
9
planning,
wise
and
because
roman's
gonna
be
taking
some
time
off
around
the
holidays.
The
rest
of
his
paternity
leave.
B
Okay,
cool,
let
me
jump
in
here
and
a
question
something
so
earlier.
This
week
we
talked
about
some
of
the
settings
kind
of
standardization
of
patterns
and
one
of
the
areas
that
we
identified
as
a
potential
candidate
to
like
demonstrate,
updating
the
patterns
and
guidelines
was
the
merge
request
page
and
look
for
different
reasons
around
success.
B
B
Usability,
so
that's
why
I'm
cracking
up
yeah
so
chatting
to
katherine
yesterday.
Another
potential
area
would
be
repository
so
that
in
itself
has
like
kind
of
like
a
existing
standalone
area
in
in
the
page.
B
So
if
you
go
to
settings
it's
already
its
own
thing,
so
that
could
be
another
potential
candidate
of
exercising
some
of
our
patterns
in
a
potentially
safer
environment,
because
it's
less
moving
parts
because
it's
already
isolated,
but
it
still
would
have
high
enough
impact
on
the
sas
scores
because
in
the
feedback,
because
of
the
over
indexing
on
the
crate
and
kind
of
core
repository
emergence
usage
like
that
could
be
another
area
that
we
demonstrate
some
of
the
best
practices.
B
So
a
candidate
here
is
like
starting
to
remove
the
expanded
collapse
to
adopt
some
of
these
other
patterns.
So
then
that
could
be
something
that
could
be
done
with
not
too
much
risk
compared
to
merge
requests
where
we
potentially
would
be
moving
it
out
of
different
areas
and
adding
new
links.
A
repository
is
still
highly
impactful
but
lives
in
its
own
little
world.
B
Yeah,
I
was
planning
to
create
an
issue
similarly
to
the
merge
request.
One
to
illustrate
this
so
I'll
do
that
over
the
next
few
days,
and
hopefully
that
will
I'll
ping.
You
enrollment
on
that
for
your
eyes
in
your
consideration,
for
something
to
do
in
13.8.
A
All
right
well,
thank
you
for
running
me
through
all
that
I
am
excited
to
see
the
outcomes
of
this
research
so
yeah,
and
I'm
also
gonna
try
and
wrap
my
head
more
around
the
other
categories
that
we
should
be
focused
on
for
this,
but
I
know
that's
as
far
as
syncing
between
us
this.
A
This
research
on
settings
in
nav
is
probably
the
most
most
relevant
thing
to
talk
about
should
be
noted,
though,
for
the
recording
we
are
doing
great
work
in
all
the
other
categories,
just
not
just
not
a
lot
of
research
going
on
right
now
in
those
so
yeah,
I'm
looking
forward
to
when
we
can
do
some
research
in
this,
especially
in
the
rich
text,
editing
and
potentially
adding
that
into
other
editing
experiences.
So
I
guess
that
yeah
that's
about
it,
have
a
good
rest
of
the
day.
Everyone.