►
From YouTube: Manage:Analytics Weekly Meeting 2020-06-02
Description
The Analytics group talks about blockers, "on deck" issues, and cool stuff from the past week.
A
Welcome
one
and
all
to
the
June,
2nd
2020
analytics
weekly,
we
have
actually
a
question
about
recordings
from
Brendan:
are
the
recordings
being
uploaded
again
and
thanks
to
some
prompting
from
Ezekiel?
They
are
so
actually,
if
you
scroll
down
in
the
agenda
here,
there
are
recording
links
next
to
the
weekly
calls.
So
I
guess:
we've
still
got
a
problem
with
that
like
password
issue,
which
is
causing
them
not
to
be
uploaded
automatically
so
Ezekiel's
prompting
I
was
reminded
to
do
it
manually
so
anyway,
the
recordings
are
there.
A
B
B
A
Not
actually
sure,
what's
going
on
with
that
I'm
actually
trying
to
remember
if
we
updated
it,
because
maybe
we
didn't
so
maybe
there's
some
other
problem
with
the
uploading.
Maybe
maybe
this
hasn't
had
the
password
I'll
look
into
that.
Thank
you
and
we
have
let's
see
a
couple
of
FY
eyes
here
for
people
to
check
out,
but
those
are
not
verbalized,
so
I'll
jump
over
to
blockers
and
at
risk
items.
So
Martin
do
you
have
an
item
there.
C
Yeah,
actually
it's
I,
don't
know
if
it's
blocker,
but
it
could
be
an
at-risk
items
right.
So
I
was
just
curious
because
well
mainly
because
I
was
out
sick
last
end
of
last
week,
so
I
noticed
we
moved
a
lot
of
the
discussions
around
the
generic
analytics
Trillian
page
to
a
separate
epic
or
issue
where
we
were
discussing
reusing
or
refactoring.
The
existing
I
think
it's
inside
analytics
page.
C
So
I
was
wondering
if
we
came
to
agreement
or
if
we
and
start
implementation
with
the
implementation
phase
or
if
there
is
any
decision
pending
that
we
need
to
resolve
first,
because
if,
if
there's
still
a
lot
of
discussions
going
on
I'm
just
thinking,
we
are
already
middle
of
them
in
the
middle
of
the
milestone.
So
this
could
turn
into
an
at-risk
item.
So
I'm
just
curious.
If
there's
anything
that
we
need
to
resolve.
A
So
I
mean
my
perspective.
Is
that
basically,
that
conversation
kind
of
shifted
over
to
this
epoch
about
using
insights
is
the
foundation
for
the
generic
reports,
page
and
and
I
think
you
know
the
conversation
is
sort
of
active
on
that.
So
you
know
another
thing:
is
we
didn't
actually
end
up?
Putting
any
of
the
generic
reports
features
the
MVC.
A
D
I'd
say
Brandon's
been
doing
some
great
work
in
helping
to
move
that
issue
along
and
so
I
really
appreciate
that
Brandon.
It
would
be
great
to
have
somebody
on
the
backend
team
to
help
kind
of
tie
up
the
backend
issues.
I
think
Brandon
has
had
some
questions
for
the
backend
team
about
how
certain
things
might
be
done,
so
it
would
be.
It
would
be
helpful,
I
think,
to
have
somebody
who's
on
point
so
that
we
can
keep
that
moving
and
close
it
out.
I.
A
C
B
That's
critical,
so
I'm
just
still
waiting
to
confirm
what
so
it's
three
endpoints
on
the
first
one
is
the
route
for
the
page
and
another
two
are
one
endpoint
to
get
the
configuration
data
for
the
charts
and
then
one
thanks.
You
get
data
for
the
jobs,
just
follow
the
same
pattern,
that's
being
used
for
insight.
So
if
we're
going
to
be
really
using
a
lot
of
the
insights
code,.
C
Okay
cool,
so
let
let's
discuss
this
async
I
wish
is
curious.
Whether
it's
like
on
hold
MOH
or
I
saw
there's
a
lot
of
progress
in
the
in
the
issue
happening
and
yeah
thanks
everyone,
especially
Brandon,
and
also
Pavel
and
Adam,
and
then
and
obviously
John
Mason,
for
helping
coming
to
a
close,
close
enough
proposal
or
starting
point.
So.
D
D
D
E
A
A
D
Yeah,
so
thanks
for
your
question,
Martin
about
it
being
in
at
risk,
I
mean
obviously
given
how
far
we
are
into
the
release.
It
might
not
make
it
right
for
13:1,
but
I,
don't
think
we
got
a
pause.
This
is
you
know
one
of
the
most
important
things
we
can
be
working
on
so
driving
it
to
a
conclusion
will
just
help
us
to
be
in
better
shape
for
the
next
milestone.
Yeah.
C
D
E
D
Right,
it's
it's
not
a
snapshot
of
the
data,
it's
live
data,
but
it's
not
making
the
whole
report
page
public,
just
just
that
chart
right.
So,
in
the
context
of
normal
navigation,
all
the
permissions
are
the
same
as
always,
but
but
what
we're
saying
is
a
specific
chart.
You
can
say
you
know
with
that
configuration.
This
is
now
gets
an
an
embedded
link
and
it
becomes
public
you'll.
D
C
A
A
If
not,
I
actually
wanted
to
call
it
something
that
Adam
did
last
week,
which
was
replacing
the
custom
finders
in
value
stream
analytics
with
standard
finders,
which
is
going
to
kind
of
offer
some
more
flexibility
and
less
complexity
in
the
future,
which
I
thought
was
pretty
cool.
So
looking
forward
to
being
able
to
put
that
to
good
use.
F
Do
we
have
any
form
of
capability
other
than
feature
flags
of
yes
story
to
run
in
it?
Oh
sweet,
so
let's
yeah
I
suppose
my
thing
is:
let's,
let's
just
start
doing
that,
let's
identify
an
MVC
issue
to
work
on
so
I.
Don't
need
to
like
pretend
like
I
know
what
I'm
talking
about
with
design
and
just
come
up
with
a
few
hypotheses
and
start
getting
start
testing
it.
The.
C
It's
something
that
I
believe
at
the
moment
currently
roses
or
introduce
this
or
is
using
the
capability
of
this
experiment.
Functionality
and
I
think
also
Ilya
used
it
in
some
other
feature
on
manage
where
we
wanted
to
have.
So
what
would
he
what
he
did?
Is
he
wanted
to
implement
an
a/b
test
for
a
better
UX
for
the
project
creation,
which
is
which
can
be
enabled
by
appending
a
URL
parameter,
and
then
users
would
see
like
the
new
version
or
without
the
parameter.
C
C
About
the
value
stream
navigation,
the
horizontal
I
think
we
talked
about
this
recently
where
we
wanted
to
get
our
data
eventually
at
some
point
which
of
the
two
versions
like
the
horizontal
or
the
stage
list,
has
better
I,
don't
know
the
question
is:
what
is
the
KPI?
Do
we
want
to
use
to
measure
success
in
this
regard?
Yeah.
That's.
F
F
D
D
F
D
C
F
You,
let's
say
next
steps:
are
we
we
look
out
for
a
potential
teeny-tiny
issue
that
we
can
test
this
out
on
and
then
we
can
generate
a
couple
of
hypotheses
ins
and
chuck
them
into
an
AV
tool
that
we
decide
is
best
to
start
out
with,
and
then
we
can
also
test
some
other
stuff.
While
we
do
it
nice
and
and
think
about
analytics
as
well,
not
analytics.
F
Is
it
the
category,
but
analytics
is
just
like
just
generally
user
analytics
I'm
going
to
put
the
link
in
but
I'll
share
my
screen
and
then
talk
about
it.
So
you'll
see
there's
this
nifty
little
object
section
within
pajamas
now
and
there's
a
report
documented
and
it's
it's
NBC.
So
it's
pretty
basic,
but
what
I've
done
is
just
documented,
like
the
purpose
of
the
report
and
the
key
workflows
that
we
want
associated
with
thief
report,
in
other
words
the
generic
drilled
out
page
and
the
way
out
structured.
F
The
report
is
you'll
have
like
one
job
to
be
done,
and
the
the
first
step
I
took
in
the
the
job
to
do
on
is
when
I
drill
down
into
the
detail
of
a
metric
assurance.
I
want
to
view,
filter
and
visualize
the
data
set,
so
that
I
can
spot
patterns
to
take
action
on
the
information.
And
then
there
are
a
number
of
generic
stages
that
you
would
go
through
in
order
to
achieve
that
job
to
be
done
within
the
report.
F
Object,
and
what
we
can
do
is
look
for
signals
at
each
one
of
these
stages
to
understand
where
the
user
is
in
the
process
of
this
job
to
be
done,
meaning
that
we
can
be
a
little
bit
more
contextual
with
the
way
that
we
approach
them
when
we
start
to
understand
it.
So
my
question
here
is:
is
there
a
way
when
constructing
the
generic
drill?
In
page,
the
report
object
to
start
tagging,
some
of
the
UI
elements
that
we
are.
D
You
know
in
its
first
incarnation,
there's
nothing
to
do
right.
There's
there's
a
chart
and
there's
a
back
button
and
that's
nothing
else
right.
That's
it!
The
next
thing
that
we
will
do
is
add
a
data
table.
You
know
and
make
columns
clickable
that
can
be
instrumented,
we'll
start
adding
features
to
the
table
for
searching
and
filtering
and
then
we'll
start
offering
options
about
how
the
data
on
the
chart
is
displayed,
whether
we're
grouping
by
month,
day
or
week
and
so
on.
F
User
has
clicked
on
a
chart
and
they
come
into
the
report
object
and
from
there
we
see
that
they
have
started
to
scope
the
data
and
the
filters
and
they'd
stopped.
They
stop
there.
They
haven't
been
clicked
on
a
chart
or
a
table.
I
haven't
scrolled,
underneath
the
filter
at
all,
so
we're
pretty
certain
that
they're
currently
within
the
scoping
phase.
So
an
example
here
is
like.
Could
you
bring
up
a
and
I
would
never
do
this,
but
could
you
bring
up
a
pop-up
saying
it
looks
like
you're
stuck
on
filtering
right
now?
F
D
I
mean
I,
think
it
normally
just
feeds
a
system
that
allows
us
to
look
at
the
analytics
offline
and
see
what's
going
on,
but
I
I
think
you
could
you
know
if
you
can
design
the
experience
we
can
code
it
and
then
then
it's
just
a
question
of
like
cost-benefit.
You
know
for
the
different
experiences
and
you
know
the
level
of
effort
to
implement
so
I
wouldn't
worry
too
much
about
the
particulars
of
snow
plow
and
so
on.
Okay,.
F
So
I
suppose
the
very
first
stage
is
configuring,
our
report
pages
in
a
particular
way.
So
it
aligns
with
these
stages
within
the
the
workflow
that
that
I've
sort
of
outlined
or
whatever
iteration
that
we
take
on
us.
So
we
get
a
better
understanding
of
how
far
users
come
along
through
that
process
and
as
long
as
like
a
like
a
sales
funnel
or
something
like
that,
and
then
we
can
see
where,
where
they
go
wrong
and
we
can
start
using
that
to
generate
ideas
and
how
we
can
increase
the
flow
through
that
funnel.
That's.