►
From YouTube: 2023-01-18 Product Analytics PM:UX Sync
Description
Weekly sync where we discuss the latest UX developments, questions and ideas in Product Analytics.
A
Hello,
everyone
welcome
to
the
January
18th
product
management,
ux
meeting
for
group
product
analytics.
Let
me
share
my
screen,
so
people
can
see
their
gender
and
we
can
run
through
everything.
It
feels
very
much
like
a
more
of
a
discussiony
conversation
today,
rather
than
I'd
like
to
see
it.
If
we
can
get
any
actions
out
of
this
because
I
feel
like
definitely
we
haven't
got
issues
for
some
things
yet
so,
let's
get
started,
we've
got
some.
Do
we
have
any
sticky
items
from
last
week?
A
A
It
is
90
of
the
way
there.
Actually
you
know
what
yeah
I
have
an
action
item
to
discuss
this
so
I'll
I'll
leave
that
until
we
discuss
it
in
more
detail.
Okay
and
last
week,
as
I
said,
we
had
no
action
items
I,
don't
think
we're
doing
any
shelters
before
that.
No,
so
let's
discuss
the
meaty
topic
of
the
left,
sidebar
Jan.
Do
you
want
to
make
your
point
or
go
close?
Your
point.
C
Sure
I'll
vocalize
the
point
that
you
made
so
yeah
Rob
made
a
comment
on
the
left
sidebar
issue
with
a
proposal
for
a
first
iteration
I.
Think
it's
reasonable
and
I
just
wanted
to
see
if
we
can
get
some
consensus
on
it
or
like
a
go
ahead
so
that
we
can
get
started
because
yeah
like
I
said
this
means
that
we
can
actually
get
a
menu
item
in
and
we
no
longer
have
to
go
through
the
URLs
or
make
it
easier
for
everybody
to
use
this.
B
Yeah
so
reading
through
the
comment
I'm
fine-
if
we
want
to
promote
this
to
an
epic,
to
make
child
issues
to
break
it
down
as
needed,
yeah,
so
let's
go
ahead,
definitely
add
the
dashboard
tab,
that's
where
we
ultimately
landed
as
part
of
this
issue
point
taken
about
funnels
and
experiments
because
we're
not
there
yet.
Are
we
not
at
the
point
where
we
know
what
we
want
for
configuration,
though,
because
we
we
know
we
need
cluster
configuration
at
the
project
level
right.
A
A
We
can
add
that
dashboards
item,
because
we
have
the
dashboards
page,
there's
a
bigger
discussion
around
that
whole
dashboards
page
on
the
onboarding
flow
and
stuff.
We
need
to
talk
about,
but
so
we
can
definitely
add
that,
but
then
configuration
funnel
to
the
experiments
we
don't
currently
have
Pages.
For
so
we
need
to
hold
off
on
them.
A
So
we
I
as
I
as
you
just
alluded
to
we'll,
create
I'll,
convert
this
into
an
epic
and
break
out
into
separate
issues.
So
we
can
tackle
these
separately
in
terms
of
my
other
point,
around
I.
Is
it
okay
to
have
the
dashboards
currently
behind
the
product?
Analytics
internal
preview
feature
flag?
Is
that
okay,
because
I
don't
think
we're
linking
up
with
optimized?
Yet
are
we
for
the
dashboards
yet.
B
D
I'm
just
joining
away
at
sound
issues,
we
I
mean
if
we
know
we're
going
to
it,
I
guess
we
would
sync
up
with
them
on
the
timeline
and
Sam
and
I
can
follow
up
on
that.
But
would
it
make
sense
to
just
kind
of
generalize
that
feature
flag
because
we
know
they're
going
to
to
want
to
use
the
dashboard
listing
sooner
rather
than
later,.
A
A
So
it's
that-
and
we
haven't
even
had
that
conversation
yet
around
what
the
dashboard
listings,
how
it's
going
to
look
or
function,
we've
optimizers
content
included,
which
so
my
feel
that
my
purse,
my
immediate
feeling,
is,
we
put
it
under
the
feature
flag
and
then,
when
we've
had
that
discussion,
we
could
then
change
it
to
an
alternative
feature
flag
or
move,
or
it
may
end
up
being
that
we
show
the
item.
All
the
time
optimize
adds
their
content
and
we
move
that
feature
flag
to
within
the
page.
To
then
render
our
content
conditionally.
D
D
So
ideally,
we
could
have
that
ready
so
that
other
groups
can
can
move
their
dashboards
into
it
as
well,
and
then
second
I
feel
like
that
was
kind
of
the
reason
why
we
ended
up
getting
a
little
mixed
up
on
feature
Flags
when
we
found
out
that
we,
let's
use
an
existing
feature
flag
for
application
settings
and
it
was
using
the
cube.
Api
proxy
feature
flag
right,
and
then
we
ended
up
having
to
separate
that
out,
because
that
that
actually
caused
issues
for
staging
and
production.
D
A
Okay,
well,
in
that
case,
then
I
guess
we
can,
but
I
still
have
reservations
around
our
current
existing
dashboards
listing,
which
is
another
Topic
in
our
list.
Okay,
I
will
create
a
new
feature.
Flag.
I
have
no
idea
how
we're
going
to
remember
or
manage
all
these,
but
I
will
create
another
feature:
flag.
D
A
C
C
A
D
A
D
Sorry,
good,
no,
no
go
ahead.
I
I
I!
Will
it's
not
a
hard
Mission?
It's
it's
not
fun!
We've
done
this
before
when
we
had
the
group
access
and
there
were
I,
think
I
can't
remember
what
it
was
called.
It
was
like
group
managed
accounts
where
there
were
four
or
five
different
feature
flags
and
different
toggles.
D
You
had
to
set
and
a
combination
in
there
of
so
it's
definitely
not
ideal,
but
it's
I
as
far
as
I
can
tell
I,
remember
just
bookmarking
and
I'm
looking
at
it
right
now,
bookmarking
a
slack
message
that
contains
our
feature,
Flags,
so
I
think
that
merge
request
right
now.
The
where
you
have
the
docs
would
make
the
most
sense.
For
now.
A
That's
fine
I
worry
having
too
many
of
them
will
cause
us
to
not
turn
something
on
in
the
way
that
we
wanted
to
turn
on
or
not
or
if
we
want
to
start
rolling
out
gradual
roll
out.
If
you
try
and
do
a
conditional
rollout
of
20
on
every
feature
flag,
you're
not
going
to
get
the
same
users
all
on
the
same
feature
flag
but
I
guess
that's
much
further
down
the
line
when
we
want
to
stop
removing
these
flags.
Okay,.
D
I
think
in
terms
of
like
I
agree
with
yarn's
point
in
terms
of
kind
of
seeing
where
we're
at,
because
if
we
have
Cube
API
proxy
and
then
the
internal
preview
I
wonder
if
we
can
merge
those
eventually
into
what
would
be
the
into
one
flag
or
a
customer
PV
flag
to
try
to
consolidate
and
keep
things,
keep
the
amount
of
feature
Flags
to
a
minimum.
Yeah.
C
A
Let
me
create
an
action
item
for
that.
Where
am
I
am
I
on
the
right
one,
yeah
there's
a
lot
of
comment
topics.
Oh
thank
you
young
all
right,
so
just
to
confirm
we're.
Okay,
with
splitting
these
out
into
an
epic
individual
issues,
we'll
tackle,
adding
the
dashboards
and
a
new
feature
flag
item
into
the
data
in
59.
That
will
then
unblock
people
if
they
want
to
start
making
use
of
that
dashboard
listing,
although
that
is
a
actually
making
use
of.
A
A
B
D
A
Okay,
the
next
topic
can
something
I've
spoken
as
spoken
with.
Dennis
about
is
the
dashboards
listing
with
us.
Moving
to
that
dashboard
everyone
using
a
unified
dashboards,
it
I
want
to
create
some
issues
and
start
that
conversation
with
mate
around
that
listing
and
how
they're
optimized
and
everyone
else
is
going
to
start
using
that
list,
whether
that
listing
makes
a
sense
for
them
from
a
user
experience.
A
D
That's
fine.
This
is
partially
just
because
I'm
I
joined
late,
but
it
seemed
like
we
kind
of
touched
on
the
fact
that
we
don't
have
issues
for
the
dashboard
list
in
terms
of
what
we
need
to
change,
to
make
it
more
generalized.
Is
that
correct,
like
we
haven't,
covered
that
yet?
And
that's
part
of
this
point
in
terms
of
having
that
conversation
or.
A
D
No
I'm
not
opposed
to
like
a
working
session
even
with
but
like
or
not
even
but
like
with,
whoever
wants
to
attend,
to
kind
of
just
figure
out
again:
I
guess
similar
to
taking
stock
of
what
we
have
for
future
Flags,
but
like
not
understand
what
we
have
for
our
dashboard
listing
and
what
would
need
to
change
under
the
hood
to
be
more
generalized
and
then,
of
course,
having
these
the
conversation
with
potato.
Let's
say:
I
think
we
and
other
groups
want
to
be
able
to
prompt
the
user.
D
To
say:
hey,
you
don't
have
Dash,
you
don't
have
your
group
level
project
planner
set
up,
so
your
your
project
analytics
dashboard,
aren't
working,
but
then
optimize
will
have
their
own
prompt
and
so
we'll
have
to
have
a
discussion
about
how
we
want
to
organize
that.
So
we
don't
have
50
pop-ups
in
the
dashboard
list.
When
you
haven't
activated
and
configured
anything
so
I,
don't
know
if
that
conversation
I,
think
that
conversation
will
help
there
with
mate.
A
Yeah
I
agree,
and
it
goes
into,
as
you
say,
with
the
onboarding
flows,
as
my
next
point
around
how
we
currently,
if
you
go
to
the
dashboards
listing
and
products
and
assistance
set
up
it
redirects
the
onboarding
flow
which
isn't
going
to
work
for
anyone
else.
So
we
need
to
come
up
with
another
way
which
me
and
Sam
have
commented
before
around
the
idea
of
using
like
what
we
did
with
compliance
Frameworks.
A
B
D
Well,
I
think
it's
some
like
sorry.
This
might
be
tangential,
but
part
of
it
is
that
we
right
now
have
the
dashboard
locations
hard
coded
and
we
need
them
to
find
somewhere
pointed
somewhere,
because
eventually
we're
going
to
be
like
creating
like
project
level,
copies
of
those
dashboards
right,
so
we're
kind
of
missing
part
of
this
flow
because
for
the
internal
preview
we
just
kind
of
hard
coded
it
in
right.
D
But
as
we
move
into
customer
preview,
we
have
to
fit
that
piece
back
in
of
how
actually
does
the
user
or
how
do
we
actually
get
those
dashboard
configurations
into
the
project
and
so
I
think
part
of
that
an
idea
or
the
current
line
of
thinking.
I
think
for
my
discussions
from
Tim
is
like
for
project
analytics.
It's
that
project
level
pointer,
whereas
for
optimizes
that
group
level
pointer.
So
we
could
use
that
as
a
hook
to
say
Hey.
D
C
Also
Sam
to
what's
your
question:
I
think
there
is
president
for
that
in
I
need
to
remember
what
the
Tool's
name
is,
but
some
of
our
Cloud
integration
in
gitlab,
like
for
gcp,
there
are
tabs
where
the
tab
is
there
and
once
you
click
on
it
and
it's
not
configured,
you
just
see
basically
empty
state
with
a
button
saying
hey,
you
need
to
set
this
up
before
you
can
use
it.
That
is
potentially
a
flow
for
us.
B
A
Okay,
I
will
create
issues
listing
out
the
dashboard
listing
and
a
separate
one
to
discuss.
The
onboarding
flow
I
will
pull
Mateen
and,
after
he's
had
a
chance
to
review
and
discuss.
It
may
make
sense,
then,
to
have
that
sync
discussion.
That
Dennis
is
talking
about
where
we
just
sit
down
and
have
a
working
session
with
everyone
that
wants
to
be
involved
just
to
try
and
figure
things
out,
because
I'm
sure
mate
is
going
to
have
questions
and
lots
of
raised
eyebrows.
D
A
I
realize
that
we've
got
about
nine
minutes
left
and
some
of
us
have
meetings
following
on
to
this.
So
I'm
gonna
keep
this
moving.
Unless
anyone
has
any
particular
points
they
want
to
raise.
If
not,
we
can
Circle
back
to
both
of
these
points
next
week,
and
hopefully,
we'll
have
had
some
decent
discussions
in
those
issues
by
then.
A
A
So
a
key
one
is
the
fact
that
it
feels
like
panel
is
going
to
be
the
preferred
name
over
widget
across
the
gitlab
product
for
dashboards,
and
we
use
widget
in
a
lot
of
places
and
we've
optimized
and
others
other
groups,
one
starting
to
make
use
of
this
dashboarding
system.
We,
the
sooner
we
rename
those
values,
the
less
painful
it's
going
to
be
for
everyone.
A
D
No
I
think
we're
gonna,
hopefully
be
able
to
lock
that
in
the
next
working
group
session,
which
I
think
is
right
after
this
call,
but
it
seems
like
panels
unofficially
declared
the
what
I
don't
think
there
was
any
strong
opposition,
I
I
personally,
don't
care
so
I
think
things
like
panel.
We
can
probably
go
ahead
and
get
started
just
renaming.
I
guess
that
could
that
could
be
my
famous
last
word
for
somehow
widgets
when
it's
over
at
the
very
end.