►
From YouTube: Verify UX/PM Meeting
Description
Discussing upcoming milestones and efforts related to the verify stage group
A
A
Put
this
in
these
notes
in
last
week,
we'll
focus
our
efforts
initially
to
get
us
one
full
month
ahead.
So
basically
what
we
discussed
last
time,
the
80/20
percent
rule
I'll
focus
mainly
on
the
current
milestone.
Mike
is
busy
on
the
issue
on
directed
acyclic
graphs,
see
some
progress
already
there.
So
that's
exciting.
A
B
So
I
have
added
I,
will
add
to
the
agenda
a
link
to
the
handbook
for
aware
of
meets
updates
for
the
what
we're
calling.
What
are
we
calling
them?
Experience,
baselines
and
experience
recommendations
so
wanted
to
know
per
the
conversation
last
week
wanted
to
move
away
from
the
term
roadmap,
since
that
was
a
little
bit
misleading,
so
I
will
add
to
the
agenda
the
link.
A
Nice,
thank
you
all
right
and
then
Brennan
was
like
hey.
Can
we
say
that
the
milestone
12,
though
aligns
with
80/20
rule
right?
You
already
said
we
were
in
a
good,
pretty
good
spot.
At
the
same
time,
I
had
one
thought
towards
that
because,
as
far
as
you
know,
less
time,
I
looked
I
can
look.
I
can
look
directly
right
now,
but
I
know
they're
like
what
is
your
process
like
with
assigning
deliverables
for
future
milestones.
A
C
Right,
the
deliverable
label
is
an
engineering
label,
not
a
product
label.
So
basically
the
what
how
the
process
looks
is
product
tries
to
balance
the
right
number
of
issues
within
a
milestone
right,
but
we
prioritize
them
and
then
based
on
like
the
what
gets
finisher
or
spills
over
and
the
like
capacity
for
the
team
in
the
coming
milestone.
The.
C
C
A
A
These
do
you
say
that
if
you
know,
if
we
look
at
12
that
oh
right
now
right,
do
you
say
that
the
label
hygiene
or
the
indicator
of
what
is
really
going
to
be
worked
on
for
12,
that,
oh,
it's
pretty
clear
with
this
this
thing
without
any
labels
being
assigned
to
indicate
hey,
this
is
definitely
gonna
be
worked
on
of.
This
are
like
potential
stretch
issues
even
though
I
believe
we're
phasing
out
to
stretch
label
right,
yeah,
yeah,.
C
No
I
so
I
do
order
them
like
literally
physically
the
like
wait,
waited
order.
You
know,
that's
not
easiest
to
use
and
get
loud,
those
against
each
other,
but
it
still
is
very
ambitious,
so
like
I,
actually
I
added
a
note
below
about
that
like
I'm.
So
like
we
we've
been
talking
about
the
DAGs,
but
it's
like
you
look
at
12'o.
Let
me
just
share
my
screen.
Real
quick.
C
Okay,
so
these
are
actually,
in
my
priority
water
right
if
I'm
looking
at
the
direction
issues-
4:12,
oh
and
so
I'm.
Just
using
my
like
concern
for
the
fact
that
I
know
that
there's
a
lot,
that's
still
spoon
makers
from
release
to
release
to
say
that
it's
very
possible
that
they
won't.
We
won't
get
to
this
like
it's
possible
that
only
these
two
things
will
be
in.
A
C
I,
don't
know
I'm
just
kind
of
pre
warning
you
like
an
ideal
world.
We
would
ship
all
of
this
until
though,
but
I'm
just
I'm
concerned
that
even
seven
is
going
to
be
too
many.
What's
like,
what's
spilled
over
from
eleven
ten
and
eleven
eleven
is
there,
but
from
a
product
perspective,
that's
that's
the
plan.
It's
just
you
know,
then
it's
prioritized
and
and
issued
based
on
engineering.
You
know
capacity.
C
A
B
No
one's
doing
it
yet
from
what
I
can
tell,
and
so
everybody
has
I
mean
that's
a
common
thing
that
I
have
heard
over
the
course
of
three
weeks
is
that
no
one's
really
working
ahead
and
prioritization
is
a
major
issue
as
well
as
the
carryover
from
milestone
to
milestone.
So
when
things
don't
get
hit,
they
move.
So
then
that
creates
some
churn.
So
good
news
is
that
we're
very
aware
of
the
problems
that
are
the
challenges
that
we
have.
A
D
I've
been
getting
on
boarded
here
and
kind
of
going
through
the
process
trying
to
learn
the
whole.
You
know
CI
CD
workflow,
you
know,
I
had
had
the
thought
that
these
it
basically
comes
done,
but
these
these
yellow
files
right
editing,
those
and,
in
the
spirit
of
you,
know
getting
Auto
Doh
kind
of
thing
and
getting
people
onto
that.
You
know
it's
a
little
daunting
right.
If
you
haven't
written
these
things
before
so,
I
had
been
thinking
the.
D
If
we
had
some
sort
of
editor
kind
of
thing
like
that,
that
would
be
fantastic
and
then
lo
and
behold
you
posted
that
one
from
Microsoft
Azure
in
there
and
I
thought.
That
was
a
great
implementation
of
it,
and
so
basically
just
wanted
to
bring
that
up,
that
you
know
kind
of
the
rear
that
you
get
a
UX
guy
who's
good,
getting
to
play
the
role
of
a
user
getting
to
see
something
for
the
first
time
before
you,
it's
really
tainted.
I
was
really
feel
like.
D
That
would
be
a
big
win
for
us
from
a
user
experience
down
point
for
people
like
me
that
are
trying
to
get
into
out
of
DevOps
or
get
into
DevOps.
You
know
and
had
a
little
guided
thing,
but
I
ultimately
ended
up
doing
is
having
documentation
pages
open
in
other
tabs
and
copying
a
little
sample
code
out
of
there.
So
even
if
it
was
just
that
simple
where
we
could
put
those
items
in
there,
the
other
side
to
that,
though,
is
am
I
really
the
user
right,
you
know.
D
Are
we
going
after
a
maya
target
user
right
if
you're
in
a
larger
corporation,
really
where
more
folks,
where
I
think
a
lot
of
more
of
our
revenue
comes
from?
You
know
they
probably
have
a
guy
that
writes
these
things.
It's
probably
not
UX
guys
it's
trying
to
figure
this
stuff
out
right.
So
I
guess
that's
the
balance
of
yeah
I
do
think
it
is
a
big
UX
win,
but
how
big
of
a
segment
do
I
really
make
up?
You
know
users
like
myself
so
just
want
to
bring
that
up.
C
Think
I'm,
sorry,
my
headphones
role,
no,
no
we're
still
yelling
at
me.
Yeah
I
mean
I
think
that
we
have
the
persona
of
a
DevOps
engineer.
That's
probably
the
number
one
persona
but
I
think
that
there's
also
so
I'm
trying
to
like
get
to
the
personas
to
get
loud
as
a
product,
as
you
know,
trying
to
expand
that
horizon
right
and
so
I
think
it
expands
our
horizon
as
well,
because
the
other
thing
is:
there's
there's
trying
to
find
it.
C
C
Like
to
get
more
developers
on
board,
and
so
then
that
could
then
lead
to
okay.
Well,
you
know
it's,
it's
not
just
CI
experts
that
are
the
persona
that
we're
going
after
I
feel
like
again,
I
kind
of
talked
about
that
that
spectrum-
and
you
know
I,
talked
about
that
last
meeting
where
you
know,
we've
got
great
stuff
for
the
middle
road
of
like
CI
folks,
but
the
really
advanced
folks
on
the
just
getting
started.
C
Folks
are
the
ones
that,
where
there's
a
lot
of
room
for
growth,
I
think
and
I
heard
that
too
in
the
cab
I
mentioned
it
in
the
last
call
not
so
much
new
to
CI
but
new
to
get
lab
right
like
these
folks
that
have
been
using
Jenkins,
which
is
very
point-and-click
e
for
years
and
years
to
its
detriment,
I
mean
the
UI.
Drinkin's
is
horrendous,
but
you
know
it's
someone
that's
been
very
pointy
clicking,
doesn't
think
in
terms
of
Oz
code.
C
There's
still
plenty
of
people
out
there
that
don't
think
of
infrastructures,
code
or
even
the
pipeline
is
code
and
so
I
think.
There's
there's
definitely
something
to
be
learned
from
that.
Not
not
necessarily
just
ignore
it,
this
much
new
one.
Can
you
exit
like
I
think
those
are
those
are
still
good
instincts
to
take
care
about
I,
guess,
yeah.
B
D
Yeah
I
think
this
goes
a
little
bit
to
what
Dimitri
and
I
were
we're.
Talking
about
off
of
this
was,
you
know,
is
it
it
might
actually
invent
a
new
persona
right,
like
kind
of
you're,
saying
it
drags
more
people
in
and
how
much
do
we
want
to
focus
on
that
thing
you
know
like
if
me
I
would
never
do
DevOps
because
it
was
daunting,
but
if
I
had
this
little
cookie
thing
that
made
it
not
daunting
now,
I
would
do
DevOps
right.
D
D
A
A
A
A
If,
before
that,
the
agenda
said
like
hey
I,
want
a
part
of
the
vision
for
verifies
getting
to
the
whole
spectrum
of
users
right
we're
mostly
targeting
intermediate
users
right
now
who
have
features
which
we're
missing
either
the
experts
or
the
beginning
users.
I
what?
What
is
your
idea
to
getting
to
those,
because
that
can
add
to
that
case
as
well
right,
like
hey,
which
features
are
implementing
what?
But
you
know
how
advanced
are
the
users
that
will
be
actually
using
them
and
perhaps
get
a
little
bit
more
transparency
into
what
we're
actually
out.
C
I
mean
the
example
would
be
where
the
analogy
would
be
like
a
lot
of
users
come
to
us
not
knowing
yet
itself
right,
and
so
that
means
that
those
users
are
kind
of
coming
to
us,
not
just
because
or
not
because
of
only
the
very
advanced
stuff,
but
because,
like
they
see
us
as
a
market
leader
right
and
so
in
that
case
again
and
again,
I
talked
about
on
the
group
conversation
even
then
again
at
customers.
There's
this
wide
spectrum
right.
So
out
of
customer
have
someone
who's.
C
You
know,
got
a
team
that
super
advanced
Aggie
lab
CI
and
has
this
like
really
complex
thing,
and
then
you
have
some
other
team,
that's
just
kind
of
getting
started
and
doesn't
really
know
where
to
start.
So,
if
you
know
the
overall
goal
was
drive,
you
know
stage
monthly,
active
user
or
smell
like
that
means
that
not
only
do
we
need
to
serve
there's
advance
customers,
the
less
advanced
and
they're
just
getting
started.
Customers
is
I,
think
also
important,
and
what
features
are
most
important?
C
B
We
need
to
figure
out
a
way
to
document
those
and
that's
what
the
item
that
I
added
to
the
handbook,
it's
the
link
is
now
in
the
agenda
of
how
we
can
create
some
benchmarks
for
the
experience
today.
I
think
the
second
thing
that
comes
to
mind
is
we
need
to
bring
in
a
UX
researcher.
We
need
to
kind
of
outline
where
we
are
today.
B
What
are
our
big
questions
that
we
would
love
to
have
answered
and
they're
there's
a
lot
of
good
questions
that
just
came
out
of
this
discussion,
so
we
need
to
bring
those
and
probably
add
to
that
list
and
then
get
the
UX
research
team
involved,
see
where
they
can
guide
us.
You
know
what
do
we
need
to
do
to
get
these
questions
answered
and
then
that'll
I
think
give
us
once
we
get
those
questions
answered
kind
of
a
foundation
to
build
upon,
because
right
now
we're
we're
kind
of
it's
great.
B
C
B
I,
don't
know
how
it
works
at
get
lab,
but
traditionally
I
would
just
contact
like
Sarah
Sarah
O'donnell
and
would
outlined
kind
of
our
problem
space.
So
this
is
where
our
area
focuses-
and
this
is
what
we
know
of
today
and
here's
our
long
list
of
things
that
we
don't
know
that
we
would
love
to
know
and
then
get
guidance
from
her
and
her
team
of
how
do
we
get
answers
to
it
and
I
think
the
most
important
thing
is
why
we
need
those.
Why
we
need
these
answers.
B
We
need
to
be
able
to
convey
that,
because
what
do
we
want
to
do
with
it
right?
We
want
to
build
a
product
strategy
for
verify.
We
want
to
be
able
to
add
features
to
verify
that
are
meaningful
and
useful
to
our
users.
We
want
to
have
a
clear
understanding
of
who
our
users
are
for
this
and
if
there
is
to
Mike's
point
an
opportunity
in
the
market
to
expand
that
user
base
for
verify.
B
A
Depends
I'd
say
you
know
if
very
more
I'd
say
that
an
issue
is
ideal
if
we
know
what
we're
looking
for,
but
perhaps
for
a
little
bit
more
back
and
forth
discussion
and
meeting
it
would
be
nice
I
think,
depending
on
how
this
discussion
is
going,
I
think
we're
still
figuring
out.
You
know
what
are
the
questions
to
ask?
A
B
B
Getting
these
questions
answered
then
I
think
it's
going
to
start
formulating
the
kind
of
a
research
strategy
for
the
stage
group
and
and
then
that'll
really
help
us
and
propel
us
and
give
Brendon
what
he
needs
in
order
to
help
prioritize
what
needs
to
happen
and
when
it
needs
to
happen
so
I
think
over
time
that
it
will
evolve,
but
right
now,
I'm
kind
of
just
seeing.
We
just
need
to
have
a
conversation
with
research
and
and
we
do
need
to
document
all
of
our
questions
and
we
kind
of
we
need
to
do
some
homework.
B
I
think
that's
great
and
the
document
that
Kyle
has
started
for
the
secure
stage
and
I
think
is
have
a
lot
of
the
questions
that
are
coming
up
now
that
there
just
aren't
specific
to
verify.
So
again,
let's
take
a
look
at
that
document
because
it
really
is
a
product
management
/ux.
It's
like
the
bridge
questions
that
kind
of
span
both
spaces.
So
if
we
could
take
a
look
at
that
and
then
convert
it
over
to
be
specific
to
verify,
I
think
that
would
be
great.
B
A
A
So
I'll
put
that
in
my
agenda
to
work
a
little
bit
ahead
for
that
alright,
we're
in
about
5,
more
minutes
left
or
6
more
minutes,
let's
quickly
go
through
the
next
I
saw
that
you
appointed
this
one
I
want
to
make
it
a
little
bit
of
a
habit.
Perhaps
Brendan
use
I
saw
this
posted
by
you
in
the
verified
chat
on
this
item
on
CI
templates
being
an
important
one.
You
want
to
want
us
to
work
head
a
little
bit
on
it.
A
C
It's
based
off
of
just
to
kind
of
convey
the
I
again
just
to
convey
the
idea,
but
in
my
mind
this
is
like
completely
just
I
threw
together
an
idea,
and
it's
probably
something
that
we
want
to
think
about
a
lot
more
than
that
and,
like
you
said,
because
of
our
these
conversations,
I've
been,
you
know,
my
spidey
sense
went
off
when
I
was
thinking
about
scheduling
this
like
something
we
should
get
on
really
quick.
So
anyway,
I
think
my
mic
just
changed
again.
Sorry.
A
A
C
C
Let
you
know
that,
like
using
my
spidey,
what
is
actually
going
to
ship
sense
that
it's
possible
that
this
one,
which
is
higher
priority,
will
ship
in
1200
and
the
dag
won't
I
was
tempted
to
even
move
it
today,
but
staying
ambitious,
I
haven't
moved
it,
but
I'm
thinking
it
and
below
the
line
might
not
ship
in
12.
That's
not
to
say
that
the
work
isn't
valuable
because
it'll
be
the
first
thing
and
it'll
be
the
highest
priority,
singing
one.