►
From YouTube: Support Metrics Analysis Workgroup - 2020-10-27
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
No
minute
saved
it's
tuesday,
october
27th.
This
is
the
metrics
analysis,
working
group
and
we're
starting
to
wind
down.
I
think
first
section
on
the
agenda
is
the
status
on
persistent
items.
Elia.
Would
you
take
us
through.
B
Thank
you,
lyle
support.
We
can
review
asset
is
trending
back
up,
can
already
give
some
preliminary
results
for
october
right
now
at
92
percent
for
asset
for
all
groups.
So
that's
good
again.
Nice
results
for
frt
nice
results
for
well,
at
least
within
target
for
energy,
says
general
again.
This
is
for
september,
but
in
total
the
effect
of
says
and
says
accounts
is
a
bit
less
because
we
have
less
tickets
there.
Hence
why
we
are
increasing
to
92
in
october,
but
anyways
as
of
september.
B
These
are
the
results
we
already
are
familiar
with,
self-managed
still
within
target
on
all
the
parameters
that
we're
monitoring
but
again
in
support.
We
can
review
and
we
can
see
for
self-managed
that
for
nlt
we're
within
target
for
self-managed,
we
are
within
target
for
dot-com
frt.
We
are
close.
We
are
a
bit
under
and
for
energy
we
are
good
and
asset.
As
I've
mentioned,
we
have
been
steadily
increasing
back
to
normality
for
that
in
l.a.
Now,
support
can
review.
B
A
The
next
is
the
outstanding
hypotheses.
Most
of
them
are
closed
at
this
point
billy
and
I
spent
some
time
last
week,
looking
at
number
six
frt
hawks.
Oh
no
sorry,
sass
tickets
have
gotten
harder
number.
Eight,
that's
the
one
with
it.
Italy
posted
kind
of
a
summary
comment
there
haley
do
you
want
to
read
it
or
should
I
read
it.
B
I
can
go
for
it.
I
can
do
the
tldr
version.
We
believe
that
we
don't
necessarily
have
information
to
dispute
our
hypothesis,
so
it
does
seem
likely.
I
will
probably
have
to
collect
some
more
information
as
of
right
now
we
don't
really
have
a
system
of
collecting
ticket
difficulty
and
it's
a
notoriously
difficult
subject
to
measure,
but
we
have
suggested
a
few
procedures
which
will
follow
up
in
due
time.
B
One
of
them
is
updating
the
ticket
with
a
subjective
measurement
counter
which
engineers
can
fill
in
at
some
given
moments
on
time,
and
we
can
also
we're
considering
to
do
a
quantifiable
frequency
word
usage
measurement,
which
we
can
do
using
a
few
scripts,
that
we
have
to
kind
of
try
to
create
a
mapped
view
of
types
of
tickets
that
we're
working
on,
based
on
customer
words,
not
based
on
product
type,
not
based
on
problem
type,
something
a
bit
more
consistently
measurable
and
then
maybe
see.
A
A
One
is
the
upcoming
work
group,
the
proliferating
about
like
identifying
problem
types,
and
I
think
that
will
also
help
because
I
think
each
problem
type
would
probably
assign
a
relative
difficulty,
to
which
I
think
that
could
also
help
give
a
piece
of
this
puzzle.
But
overall,
I
think
it's
he
said
it
well,
it's
very
it's
notoriously
difficult.
A
Other
hypotheses
that
are
open.
I
think
that
may
have
been
the
last
one
yeah,
so
I
mean
number
six
would
be
prioritized
so
I'll
mark
that
one
as
I
think
we
actually
need
a
new
a
new
label
inconclusive,
but
we
can
do
that
so
that
actually
takes
us
through
our
initial
hypotheses
in
agenda
item
number
three.
I
wanted
to
note
that
the
merge
request
that
talks
about
reforming
this
work
group
and
our
floors
is
now
merged.
Thank
you.
Tc.
A
I
tried
to
make
it
too
big
by
adding
a
bunch
of
like
of
the
hypothesis
action
steps,
but
I
took
that
out
and
so
that's
what
kind
of
the
next
step
is
is
getting
this
page
into
us
into
a
state
where
future
working
groups
can
you
know
rest
on
the
work
that
we've
done
so
far,
so
if
they
have
similar
hypothesis
to
what
we
have
being
able
to
go
through
the
analysis
that
we
did
and
then
very
rather
than
having
to
invent
the
analysis
themselves,
use
that
information
to
just
quickly
support
or
falsify
the
same
hypotheses
and
hopefully
get
onto
new,
more
interesting
ones
and
well,
maybe
not.
A
I
think
that's
gonna
take
some
time,
so
I
don't
have
any
other
agenda
items
for
this
meeting.
But
that
would
be
kind
of.
My
suggestion
is
that
we
skip
next
week.
We
check
in
on
slack
just
like
as
a
touch
point
and
then
do
our
final
wrap
up
november
10th
with
this
being.
The
outstanding
thing
is
for
your,
if
you
did,
if
you
went
through
one
of
these
hypotheses
analysis,
then
make
a
merge
request
to
that
actions.
Page.
B
C
I
was
curious
one
thing
about
kind
of
the
reporting
art
the
artifacts
of
reporting-
that
kind
of
help
guide
the
investigation
into
hypothesis
if
it
makes
sense
to
kind
of
either
build
a
dashboard
or
just
a
location
that,
for
these
kinds
of
analysis
to
have
to
go
back
to
so
they
they
also
don't
have
to
be
reinvented
right.
We
have
the
the
top
ones
that
say
do
we
need
to
do
anything,
and
then
we
have
the
deeper
ones
things
like
you
know.
C
Ilia
is
done
and
waving's
done
and
that
sort
of
thing
if
we
have
a
consistent
kind
of
here's,
here's
a
set
of
tools
to
use
as
we
go
back
and
look
at
different
new
hypothesize,
not
the
seas,
hypothy.
A
C
C
Yeah
that
needs
to
be
maintained
or
held
there
right
not
to
leave
it
removed,
whatever
cleaned
up
yeah
but
easy
to
find
too.
A
So
that's
why
I
was
kind
of
we
should
definitely
have
like
the
the
dashboards
defined
as
they
exist
today,
but
I
expect
that
they'll
probably
get
out
of
date
and
that
they'll
be
something
that
has
to
be
rebuilt,
which
is
why
I
was
hoping
for
sort
of
like
the
qualitative
piece
as
well
about
like
what
we
took
a
look
at.
A
A
Yeah
next
criteria,
number
one
define
conditions
under
which
a
metrics
work
group
will
be
formed,
defined
and
formed
with
the
asset
group
create
a
dashboard
that
exposes
metrics
and
targets,
that'll,
trigger
actions
done
and
then
document
the
common
hypothesis.
This
is
where
our
outstanding
action
is
so
I
think
we're
pretty
good
else
on
y'all's
minds.
A
My
mind
is
hurting,
but
yes,
cool,
okay,
so
I'm
gonna
cancel
next
week's
meeting
and
I'll
send
a
summary
to
donique
and
weiming
just
so
that
they're
aware
and
I'll
prioritize
getting
my
mr
in
early
this
week,
so
that
you
all
have
an
example.
We'll
have
a
touch
point
next
week
on
tuesday.
In
slack,
I
will
probably
ping
you
so
prepare
to
be
picked.