►
From YouTube: Create:Editor Product/UX Weekly - 2021-01-20
Description
Weekly Editor group sync between Product, Design, and UX Research
A
Hello,
everyone:
this
is
the
editor
group
weekly
product
and
design,
sync
for
january
20th,
2021
and
I'll.
Just
kick
off
the
agenda,
real
quick.
The
only
item
I
added
was
that
I
I
got
a
ping
today
from
someone
on
our
data
team
that
they
had
resolved
an
issue
with
one
of
our
periscope
dashboards
for
the
wiki
usage,
which
had
been
skewed
for
context.
Here
we
have
our
data
reported
from
sas
and
then
self-managed
and
then
there's
a
percentage
of
our
self-managed
customers
that
don't
report
data.
A
So
we
have
an
algorithm
that
estimates
the
uplift
for
those
customers,
as
if
you
know
we
can,
we
can
make
some
assumptions
based
on
the
percentage
of
people
using
certain
features,
etc,
etc,
and
our
uplift
for
a
little
while
for
wiki
was
showing
that
we
had
like
four
million
users,
which
was
great.
I
think
that
would
have
been
fun,
but
the
the
uplift
was
a
little
generous.
A
So
this
link
I
have
in
here
shows
a
much
more
accurate
estimate,
it's
still
very
exciting,
to
see
the
shape
of
this
graph
for
the
wiki,
where
I'm
going
to
look
into
whether
or
not
this
is
due
to
some
new
instrumentation.
That,
like
is
reporting
that
maybe
hadn't
there
was
like
an
upgrade
or
something
like
that.
A
A
If
that's
the
case,
I'm
very
excited
that
so
many
people
are
taking
advantage
of
group
wikis
and
it
makes
our
decision
to
start
investing
in
the
rich
text
editor,
but
using
the
wiki
as
our
playground
even
easier.
I
think
we'll
be
able
to
reach
a
lot
of
people
and
yeah.
That's
all.
I
really
have
to
say
about
that.
A
I
have
to
dig
in
deeper
and
understand
the
data
model
a
little
bit
more
and
whether
or
not
I
can
slice
this
up
and
confirm,
like
which
section
of
these
are
group
wiki,
but
it
should
be
possible,
and
then
that
should
give
me
a
better
picture
of
whether
all
wikis
saw
an
increase
or,
if,
like
that,
that
big
jump
in
november
was
was
exclusively
group.
Wikis.
B
B
A
A
I
just
remember
the
other
thing
I
wanted
to
add
to
the
design
agenda
is
something
I
pinged
you
in
issues
you
may
not
have
had
a
chance
to
see
them
yet
michael,
but
the
import
team
wants
to
make
some
changes
to
the
drop
downs
for
adding
new
projects
and
groups
which
would
conflict
and
complement
the
solution.
Validation.
A
You
just
went
through
because
I
know
you
had
a
button
there
for
like
creating
a
new
group
and
a
new
project,
even
new
snippets
they're,
looking
to
pick
this
up
in
the
next
couple
releases,
so
we
want
to
make
sure
we
partner
with
them
and
they're
aware
of
the
direction
we're
headed
and
maybe
have
them
collaborate
on
the
mvc
or
just
solve
their
problem
for
them.
If,
if
it's
all
just
the
same
to
do
it
in
one
place,
cool.
B
A
In
particular,
a
decision
point
between
whether
they
were
going
to
add
add
buttons
to
simply
add
a
new
group
or
project
or
whether
they
wanted
to
introduce
an
import
link
as
well,
which
didn't
show
up
on
your
concept.
So
I
just
wanted
to
make
sure
we
had
a
dialogue
in
the
issue
about
whether
that
was
part
of
the
mvc.
A
A
A
So
really
it
sounded
like
there
was
a
chance
they
might
pick
it
up
for
1310
and
if
we're
starting
our
implementation
of
the
top
nav
consolidation
of
those
in
1310,
which
is
my
hope,
but
you
know
it's
not
nothing
set
in
stone.
I
want
to
make
sure
we're
not
both
trying
to
compete
for
changes
in
and
then
their
work
gets.
Overwritten
yeah.
So
absolutely
glad
that
you're
keeping
an
eye
on
that
one
and
I'll
work
with
their
pm
as
well.
B
B
The
moment
I'm
pretty
fine
with
the
split
button,
I
don't
see
it.
I
think
it's
a
catalyst
for
us
to
potentially
improve
the
way.
Our
split
button
works
because
there's
have
been
research
studies
in
the
past,
showing
that
the
spread
button
is
confusing
because
of
the
way
it
works
as
a
drop
down
more
so
than
a
button.
But
this
could
be
a
catalyst
for
improving
that.
A
Yeah,
that's
great,
I
I
think
the
the
more
as
I've
mentioned,
I
think
in
the
issue.
The
more
we
build
out
sort
of
use
case,
optimized,
editing,
experiences,
whether
it's
the
static
site,
editor
or
the
pipeline
visual
editor
or
likes.
You
know
a
rich
text
editor
down
the
road.
We're
gonna
have
a
little
more
like
heavy
lifting
to
do
on
presenting
the
options
in
a
way,
that's
not
overwhelming,
so
that
people
can
pick
the
right,
editing,
experiences
and
and
finding
an
intelligent
default,
which
I
know
was
discussed
in
those
pipeline
issues
as
well.
B
I'll
jump
over
to
ux
research
now
so
with
settings
solution,
validation.
I
think
one
thing
that
I
was
doing
at
the
beginning
of
the
year
was
like
compounding
a
lot
of
things
on
top
of
each
other,
but
speaking
to
catherine,
I'm
almost
seeing
that
there's,
potentially
two
unmoderated
solution,
validations
or
maybe
just
one.
It's
like
looking
at
just
the
interaction.
So
there's
that
like
save
and
updating
items
in
the
settings,
so
one.
C
B
Ideas
that
we
have
is
like
this
progressive
review
on,
adding
and
and
then
showing
the
form
to
add
the
information.
There
see
that's
a
good
direction
for
it
to
go
with,
because
yeah
we
can
get
a
solution,
validation
there,
especially
on
moderator.
We
could
get
like
a
signal
on
that
prior
to
like
creating
tickets
to
get
that
developed
and
the
other
one
is
I'm
going
to
start
off
as
a.
I
think
it
makes
sense
as
an
unmoderate
solution
validation,
but
I'm
navigating
to
a
settings
page
from
within
the
product.
B
So
this
is
part
like
looking
at,
oh
if
I'm
in
the
merger
press
or
other
parts
of
the
application
like.
If
I
wanted
to
make
some
changes
to
this,
how
would
I
get
to
it-
and
this
is
might
be
like
a
small
like
foray
into
like
exploring
this
deeper,
but
it's
just
saying
like
is
having
on-page
navigation
somewhere
helpful
to
improving
the
user
experience
of
getting
to
settings
and
then
getting
back
to
where
they
came
from,
and
my
current
hypothesis
is
like
this
could
be
like
the
big
thing
within
settings.
B
B
And
then
my
other
point
is
around
searching
settings,
so
we
already
have
it
running
in
the
handbook
project
and
some
other
internal
more
like
get
lab
level
get
lab
team
member
accessible
area,
so
I'm
debating
whether
that
should
be
done
internally
or
whether
that
should
we
should
just
activate
another
project
and
have
that
as
a
moderated,
moderated
solution.
Validation
to
like
get
deeper
into
place
on
that.
So
I'm
going
to
focus
on
that
one
after
after
the
moderator
once
go
out
the
door.
B
B
At
this
moment,
like
searching,
is,
is
almost
like
a
universal
behavior,
so,
whether
it's
internal
external,
I
don't
think,
there's
much
difference
in
like
behaviors,
but
as
long
as
whoever
we
speak
to
actually
interact
with
settings
on
a
regular
basis.
That's
probably
the
key
thing
and
then
yeah
for
the
bigger
question
is
like
we're
searching
settings
and
if
we
go
trying
to
get
a
signal
to
see
how
we
might
do
multi-page
settings
like
search.
B
So
if
I'm
on
a
certain
I'm
on
the
first
page
of
settings,
what's
the
best
way
to
do
search
of
all
settings?
Is
it
in
that
search
bar
that
we're
propos
that
we've
executed
on
at
the
top
of
the
page,
or
is
it
like
the
global
search
or
do
we
need
to
make
some
other
ui
changes
to
make?
It
make
sense
that
this
is
a
global
setting
search
rather
than
an
in-page
search?
So
that's
what
I'm
kind
of
curious
about.
A
Yeah
that
all
sounds
good
and
also
that,
just
tactically
speaking,
the
search
component
is
just
behind
a
feature
flag,
so
we
should
be
able
to
enable
that
for
another
project
easily,
if
we
decide
to
go
that
route
or
you
know
just
leave
it
on
the
dot
com
repository,
I
don't
know
if
it
could
be
a
challenge.
We
need
to
make
sure
that
our
recruiters
actually
have
access
to
the
settings
view,
and
so
I
guess
they're,
maintainers
or
developers.
B
C
And-
and
so
my
point
is
just
a
fyi
that
I
have
wrapped
up
today-
we
reached
our
50
response
number
today,
so
I
wrapped
up
the
project
level
left
sidebar
tree
test.
So
now,
I'm
in
the
data
analysis
and
synthesis
phase
of
pretty
much
everything
we've
collected
so
far,
so
I
just
shared
a
sheet
where
that
is
going
on,
and
I
will
just
quickly
give
you
a
little
bit
of
a
overview
of
what
what
that's
all
about.
C
C
And
so
what
I'm
going
to
do
in
this
sheet
is
take
basically
all
the
different
feedback
that
we've
gathered
throughout
the
years
and
all
the
different
patterns
that
we
observed
in
these
tests
and
kind
of
see
where
they
align
across
different
tests.
They're
not
going
to
align
one
for
one
most
of
the
time
because
they're
group
level
versus
project
level.
C
But
there
are
some
areas
that
were
tested
in
both
tests
like
insights,
around
repositories
that
is
relevant
both
at
the
project
and
group
level
that
might
paint
a
picture
into
a
potential
miscategorization
or
things
like
that.
So
what
I'm
doing
is
taking
that
data
and
then
taking
I'll
also
take
our
assessed
survey
feedback
and
then
compare
that
with
some
of
the
observations
and
recommendations
that
we
received
in
the
past
and
try
to
see
if
there's
a
picture
kind
of
being
painted
across
the
different
data
sources.
C
So
I
just
wanted
to
give
you
a
heads
up
that
that's
where
I'm
at
right
now,
hopefully
next
week,
we
can
start
to
talk
to
discuss
more
of
those
findings
and
have
a
better
picture
of
that.
But
that's
where
we're
at
now
and
if
you're
curious,
you
can
kind
of
click
around
through.
As
I
start
to
add
more
and
more
things
to
this
sheet.
But
that's
where
it'll
be.
C
A
And
our
one
of
the
next
biggest
areas
of
improvement,
I
think
we
can
tackle
with
with
fairly
limited
impact.
I
should
say
like
we
can.
We
can
make
changes
here
with
high
results
but
low
like
dependency
on
the
back
end
code
base
changes,
and
things
like
that.
I
think
we
can
move
some
stuff
around
and
get
a
a
lot.
A
C
Yeah,
it's
it's
definitely
an
interesting
topics,
but
things
like
incidents
where
there's,
I
think
we're
talking
about
this
michael.
Where
there's
a
similar
pattern,
I
think
they're,
both
issue
types
or
the
incident
is
an
issue
type.
So
there's
like
something
that
might
remind
them
of
the
incident
might
remind
them
of
an
issue,
but
it
might
not
actually
belong
in
that
category
depending
on
how
we
are
categorizing
things,
so
there's
kind
of
potentially
a
friction
point
in
some
places.
C
Settings
is
kind
of
this
there's
another
level
of
navigation
or
another
method
that
we
need
for
wayfinding
and
finding
features
aside
from
them
just
existing
in
the
left
sidebar,
because
right
now,
that's
like
the
main
way
that
groups
will
promote
the
discoverability
of
a
feature
or
kind
of
just
place,
a
new
thing
there.
But
if
there
are
other
ways
that
users
can
discover
these
features
in
like
a
sensible
way
in
their
workflow,
I
think
that
might
help
with
the
problem
of
things
kind
of
loading
up
in
the
left
sidebar.
C
So
that's
why
I
think
all
of
this
will
be
interesting
to
see
if
these
are
like
related
to
different
pathways.
Like
you
know,
you
start
in
issues
and
then
you
go
into
incidents,
and
then
you
kind
of
do
something
else,
and
maybe
that's
why
they're
kind
of
being
clustered
together
rather
than
incidents
needing
to
be
a
a
an
item
under
issues
or
something
like
that.
I
don't
know
if
that
made
sense,
but
that's
what
I'm
trying
to
tease
apart
here
in
what
we're
seeing
in
the
data.
C
D
Great,
so
one
quick
thing,
while
you
were
talking,
I
I
spent
a
little
time
looking
at
that
query,
to
see
what
the
result
of
the
spike
is,
but
yeah,
it's
like
hidden
behind
some
function
that
has
some
magic
sizes
and
variables
and
yeah.
It's
not
just
understanding
sql,
so
I'd
like
to
know
more
about
size
and
just
to
know
how
to
figure
those
things
out,
but
I
would
have
to
learn
too.
A
A
Well,
I
think
we
can.
We
can
put
out
a
request
to
the
data
team
to
to
help,
or
at
least
help
us
learn
how
to
do
it.
But
I'm
just
happy
that
our
our
numbers
are
at
least
more
realistic
and
the
two
potential
scenarios
are
that
group
wikis
were
adopted
very
quickly
and
and
or
we
are
using
the
wrong.
We
were
or
are
using
the
wrong
numbers.
D
A
Yeah
well
in
the
the
last
quarter
or
two,
there
have
been
big
pushes
across
groups
to
get
that
instrumented,
especially
in
self-managed,
so
for
a
lot
of
groups.
They
they
maybe
only
had
it
in
sas
or
or
instrumented.
Not,
you
know
not
completely
at
all,
so
that
I
think
the
the
graphs
for
a
lot
of
the
groups
are
are
going
like
up
starting
about
mid-year.
A
As
the
new
data
was
coming
in.
I
think
it
was
like
a
12
4,
12
or
13
4
13
5,
or
something
like
that
when,
when
we
were
trying
to
get
everything
in,
I
don't
know
static
site
editor
had
that
in
you
were
working
on
that,
and
that
was
all
part
of
that
big
push.
So
we've
we're
getting
the
data,
hopefully
in
a
consistent
and
accurate
as
accurate
as
we
can
manner
so
we'll
verify
that
and
then
try
and
slice
it
up
by
group
wiki
and
see
what
we
get.
A
Users,
that's
it
for
me.
I
believe.
That's
it
for
the
agenda,
no
need
to
keep
you
longer,
but
if
anybody
has
anything
else
before
we
stop,
I
can
turn
it
over
chat.
Anything
else.
You
wanted
to
chat
about
cool,
we'll
get.
I
think
we'll
get
a
few
minutes
back
from
the
scheduled
time,
but
I
hope
everybody
has
a
great
rest
of
your
day
or
beginning
of
your
day
and
I'll
see
you
next
week
or
and
most
of
the
editor
team
we'll
see
tomorrow.