►
From YouTube: Diagnostics WG meeting
Description
A
B
D
A
A
F
A
Cool
proposer
to
drive
diagnostic
working
group
initiative
as
new
user
journeys.
It's
still
waiting
for
me.
I
need
to
work
more
on
the
survey
to
being
able
to
send
it
out,
but
I'm
wondering
if
maybe
we
can
come
straight
to
one
to
use
cases
which
we
know
for
sure
that
you're
gonna
tackle
just
to
make
some
progress,
because
this
survey
takes
longer
than
I
expected.
I.
Think.
F
A
That
was
this
conversation.
If
we
should
change
the
dynamic
working
group
meetings
to
have
deep
drives
instead
of
status
updates,
should
we
try
in
two
weeks
to
go
with
that
use
case?
I
think
it's.
This
is
the
post-mortem
stuff
or
at
least
doing
something
like
half
of
the
meeting
is
deep
dive
on
that
and
half
of
them
say
to
sub
date.
Would
would
be
the
people
open
to
try
this
new
approach,
I
mean.
F
A
F
F
C
C
Probably
I
got
a
little
bit
confused
because
the
agenda
item
proposal
to
drive
diagnostic
working
group
initiated
through
user
journey.
In
my
opinion,
Peter,
was
trying
to
get
some
feedback
on
the
user
journeys
document
which
he
prepared,
and
that
is
also
getting
stagnated
a
bit
and
he
wanted
to
discuss
that
with.
A
A
A
F
A
C
A
So
I
think
the
two
is
related.
Maybe
maybe
I
made
a
mistake,
not
sharing
what
I
meant
on
the
deep
dive,
but
my
idea
would
be
basically
we
discuss
that.
Okay,
this
is
the
user
symptom
that
the
user
is
saying
that
my
process
is
crashing
and
we
can
discuss
what
are
the
available
tools
today.
What
would
be
the
ideal
tool
in
the
future
and
what
should
be
the
recommended
and
the
best
practice
today
to
the
users,
so
I
kind
of
thinking
both
to
to
covering
the
state
of
the
ecosystem
today?
A
F
B
A
A
F
A
F
Now
I
think
we're
at
the
state
where
we
need
a
champion
to
be
pushing
it
forward,
and
there
isn't
one
so
I
would
agree
that
there's
not
much
point
having
it
on
the
agenda
right
this
at
this
point.
Unless
we
find
somebody
who's
gonna,
be
you
know,
pushing
it
forward
or
making
sure
there's
something
to
talk
about.
F
I
am
still
trying
you
know,
sort
of
his
very
background
tasks.
I
am
still
interested
in
the
the
terminology
and
sort
of
whatever
it
was
like
the
terminology
that
mike
coffman
had
put
together
in
terms
of
acing
contexts
and
stuff,
but
and
so
I'm
still
interested
in
seeing
if
we
can
move
that
for,
but
only
like
yeah,
it's
not
gonna
be
fast
and
it's
not
gonna,
be
anything
that's
worth
reporting
on
in
the
meetings
until
at
some
point
later
on.
So
okay.
A
E
F
A
F
Think
that
would
be
you
know
if
we
find
that
we've
got
non-overlapping
times,
we
should
do
that
and
that's
part
of,
like
Peter,
was
gonna
put
together
a
spreadsheet
like
we
use
for
the
TSE.
It
just
takes
some
work
to
do
that,
so
that
would
tell
us
like
hey.
If
there's
like
half
the
people
can
make
one
time
and
half
the
people
can
make
the
other
time
and
there's
no
overlap.
That
spreadsheet
would
show
us
that.
F
There's
a
short
form,
I
think
just
posting
an
issue
and
if
people
say
well,
I
can't
make
this
time
but
could
make
what
time
could
I
make?
What
day
time
could
you
make
we
can
sort
of
see
what
comes
out
of
that
and
if
people
respond
it's
it's
a
better
signal
that
they're
just
not
making
the
meeting
versus
just
don't
have
time
over
all
right.
A
Then,
let's
end
early
and
hopefully
in
two
weeks
with
a
deep
dive,
we
can
make
more
progress
moving
a
very
little
bit
from
this
status,
update
meetings
which,
which
is
great
when
lots
of
things
happening
to
share
context.
But
when
not
many
things
happening,
it's
not
the
best
way
of
spend
our
time
so
see
you
in
two
weeks
and
thank
you
for
coming.
Yep.
B
A
F
Having
said
that,
the
the
issue
like
the
the
meeting
generator,
will
generate
the
standard
template,
so
you'll
probably
need
to
go
in
there
and
say
no
we're
not
doing
this
we're
doing
distance.
You
know
this
other
thing.
Instead,
okay
and
that'd
probably
be
a
good
time
to.
You
cannot
mention
the
team
to
say
by
the
way,
we're
not
doing
this,
we're
actually
having
deep
dialects
and.