►
From YouTube: CI/CD UX Meeting - 2021-06-16
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
Awesome,
so
this
is
the
city.com
for
june
16
15
right
you're,
joining
daniel
yeah,
just
gonna
go
ahead
and
go
over
the
fyi
announcement,
so
you
know
I'll
be
out
of
office
starting
tomorrow.
Finally,
a
holiday
everything's.
Let
me
start
it
I'll
be
back
on
the
28th
so
especially
into
the
effect.
A
That's
the
coverage
that
asks
for
everyone.
That
is
here.
So
if
you
have
any
questions,
if
you
need
any
clarity
before
I
log
off
end
of
the
day
today,
let
me
know
and
the
second
heads-up
it's
about
friends
and
family
day.
We
have
one
coming
up
next
week
next
friday.
So
add
that
to
your
agenda
and
yet
another
short
week,
nadia,
oh,
but
we
can
do
it.
B
A
Awesome
yeah.
Now,
if
you
want
to
avoid,
tell
your
point,
otherwise
you
can
jump
to
general
items.
B
Yeah
so
after
learning
that,
apparently
I'm
not
taking
enough
vacation
time,
I
decided
to
go
on
vacation.
So
I
scheduled
some
pto
time
from
june
20th
till
june
2nd,
which
means
that
basically,
my
last
day
will
be
next
week,
thursday,
because
of
the
family
and
friends
day.
So
just
keep
an
eye
out
for
a
ux
coverage
issue.
I
don't
think
there
will
be
much
proactive
work
to
handle.
B
I
might
ask
you
to
help
out
with
like
one
or
two
user
interviews
potentially,
but
we'll
see
how
it
goes
because,
but
I'm
doing
my
best
to
work
with
dove
to
kind
of
re-prioritize
things
and
move
things
around
to
accommodate
for
the
time
off,
because
there's
plenty
of
things
engineers
can
work
on.
So
there's
actually
no
rush
for
me
to
work
on
things
which
is
great,
so
yeah,
just
a
heads
up.
A
Awesome-
and
my
first
point
here
is
about
your
actual
case,
so
it's
that
time
of
the
the
quarter
again.
So
our
next
actual
case
is
on
the
28th
of
june.
That's
the
monday,
I'm
I'm!
I
returned
from
my
pto
and
I
think
last
time
we
have
to
choose
two
slides
and
last
time
ian
and
daniel
added
their
slides.
So
I
want
to
suggest
that,
oh
sorry,
I'm
looking
at
your
showcase.
That's
not
the
truth!
Group
conversation
that
was
in
april.
A
We
only
need
two
slides
and
last
time
we
had
package
and
pipeline
altering.
A
So
I
want
to
suggest
well
it's
up
to
you
really
what
release
and
ci
or
pipeline
execution
now
to
have
their
slides
presented,
but
you're
pretty
discussing
the
issue.
The
only
thing
is
that
I'm
not
gonna
be
here,
so
you
have
to
align
that
the
content
and
review
with
valerie.
A
D
Yeah-
and
I
can
add
one
too
like
we-
have
worked
on
many
ci
minutes
and
user
related
issues
which
are
very
beneficial
for
users.
A
So
I'll
go
ahead
and
then
just
add
the
notes
on
the
slides
and
you
can
work
from
there.
So
thanks
for
volunteering
awesome,
my
second
heads-up
is
actually
about
deployments
direction
updates.
I
think
kenny
messaged
this
yesterday
in
slack
that
he
uploaded
a
video
to
the
direction
page,
which
is
awesome.
I
wish
we
all
had
a
videos
explaining
the
direction
of
our
categories,
so
watch
a
video
to
get
to
know
a
bit
better,
more
context
about
the
direction
for
deployments.
A
I
do
have
to
do
that
as
well,
but
any
questions-
and
I
think,
that's
relevant
to
to
all
of
us
really
overlaps
with
yeah-
not
only
release
but
configure
anyways
ti
so
have
a
have
a
watch
later
on
yeah
and
next
does
stage
book
work.
I
think,
then,
your
your
first
one.
C
Yeah,
just
quick
sharing
the
issues
I'm
working
on.
The
first
is
a
new
icons
icon
for
environments.
Maybe
it's
worth
sharing
my
screen
to
to
quickly
go
over
this
because
it
was
a
very
interesting
process,
a
shared
spring
right
yeah.
So
this
was
interesting
because
essentially
we
go
to
to
the
new
navigation
on
gitlab
on
a
project.
Ideally
yeah.
We
now
have
the
deployments
top
level
navigation,
but
if
you
remember
this
used
to
be
the
environments
icon-
and
if
you
look
here,
it's
still
the
environment's
icon.
C
When
we
were
discussing
the
new
top
level
header
for
deployments,
we
decided
deployments
were
an
inherit
this
icon.
So
we
need
a
new
one
for
for
environment
environments.
To
avoid
the
duplication,
I
I
tried
to
channel
my
inner
vitica
nadia.
I
just
get
my
ipad
and
and
sketch
some
stuff,
but
but
after
two
minutes
I
I
decided
I
was
very
silly
doing
that.
So
I
just
went
to
figment
iterated
on
top
of
the
existing
icon
and
did
a
few
rounds
of
exploration
and
feedback
with
michael
and
amelia
and
jeremy
as
well.
C
It
was
really
nice.
The
first
one
I
got
to
was
this,
which
visually
is
interesting
and
it's
still
somewhat
related
to
the
deployments
icon,
but
we
we
came
to
the
realization
that
it
was
too
too
bold
compared
to
most
of
the
other
icons
that
are
filled.
C
So
we
had
a
second
round
where
I
explored
some
other
shapes
with
with
an
outline
inside
of
the
field,
and
these
worked
to
a
certain
extent.
But
if
we
see
I
also
made
prototypes
in
context.
So
if
you
look
here,
let
me
reduce
this
and
you
see
we
start
to
lose
a
lot
of
definition
and
it's
a
bit
hard
to
read,
depending
on
on
the
elements
we
have
in
there.
C
C
I
really
like
it
aesthetically,
and
it
still
has
some
connection
to
to
the
deployments
icon,
so
if
they're
next
to
each
other,
maybe
maybe
you
can
infer
that
this
means
environments,
but
on
its
own
it
doesn't
really
tell
a
good
story
of
what
it
is
right
and
one
of
the
of
the
concepts
behind
environments
is
that
they
are
containers
for
pros
that
that
have
a
key
value
nature.
So
yeah.
I
decided
to
go
with
this
open,
an
issue
on
gitlab
svgs
and
we'll
do
all
the
technical
stuff.
C
That's
required
to
actually
turn
this
into
an
icon,
but
it
took
a
little
bit
longer
than
I
expected,
like
yeah,
just
an
icon
right,
but
it
was
a
really
nice
process
that
I'm
not
very
used
to
I'm,
not
such
a
strong,
visual
designer
and
definitely
not
an
icon
designer.
So
it
was
a
really
nice
change
of
pace.
For
me.
D
C
C
Well,
it
looks
great
if,
if
I
need
another
one
I'll,
let
you.
B
Know
or
just
ping
me
so
I
can
like
participate
in
a
review.
C
Yeah
for
sure,
for
sure
it
it
it
went
kind
of
rapidly
like
I
did
one
round
and
then
they
asked
for
feedback
and
immediately
worked
on
it
again.
So
so
it
didn't
even
involve
you
folks.
I
should
have
started
all
that.
Yeah.
C
It
was
a
great
process,
so
I
was
supposed
to
stop
sharing
my
screen
and
yeah.
The
other
point
is
that
I'm
doing
my
first
code
contribution
to
the
gitlab
code
base,
I'm
a
big
nerd
for
for
doing
some
front
end.
So
I'm
really
happy
to
finally
be
doing
that
and
it
was
funny
because
it
took
me
a
while
to
do
it.
It's
a
really
small
issue
like
changing
margins
literally
and
then
marcel
being
hey.
C
A
That's
awesome.
Danielle.
Can
you
just
briefly
talk
about
like
your
experiences
setting
up
the
pod,
I
know
that
we
we
talk
like
during
your
one-on-ones
and
they
think
like
how
to
do
it.
Was
it
as
easy
as
you
expected,
because
I'm
in
the
process
of
also
setting
up,
because
I
have
some
of
these
issues
in
texting
runner
that
I
are
merging
like
various
multiple
pages,
but
the
configuration
part
of
of
the
environment,
the
local
environment,
it's
a
bit
of
a
pain.
So
how.
C
Was
that
for
you,
so
it
was,
it
was
yes
and
no.
It
was
hard
and
and
easy.
At
the
same
time,
gitpod
is
really
nice
in
the
way
that
it's
very,
very
reliable,
to
generate
a
new
gitlab
instance.
So
that's
really
nice
like
it.
It
works.
You
know
you
you,
you
may
have
to
wait
five
minutes
for
the
machine
to
be
spun
up,
but
it
does
work,
but
then
the
problem
starts.
C
Okay,
I
want
to
test
this
specific
use
case
for
merge
strings
right,
like
it
doesn't
show
up
on
my
screen,
like
maybe
you
create
a
project
and
then
you
set
up
a
quick
pipeline.
That's
what
I
did
and
set
up
review
apps
and
I
needed
to
show
a
bunch
of
buttons
on
the
merge
request.
Widget
and
I
managed
to
show
a
few
of
them,
but
not
not
all
all
of
the
ones
that
I
needed
to
test.
So
what
I?
C
What
I
did
was,
I
went
into
the
viewjs
files
and
and
figure
out
like
what
variables
were
showing
up
the
buttons
and
I
like
mocked
up
like
I
changed
the
code
to
show
every
single
button
that
I
wanted.
Like
brute
force,
it
made
the
git
history
kind
of
wonky,
because
you
know
I
had
to
add
some
comments
and
remove
them
and
add
them
to
keep
testing.
C
So
it's
not
the
ideal
way
to
test,
but
it
was
the
way
that
I
found
to
do
it
by
myself,
quick
enough
so
that
ideally
like
what
I
would
like
is
to
just
be
able
to
create
a
gitpod
with
like
some
kind
of
like
templates
like
create
this
instance
with
these
projects
set
up
this
way
right
and
then
to
make
that
easier.
But
I
don't
know
if
that's.
A
B
The
next
couple
items
so
first
I've
been
reading
through
the
product
product
process
handbook
page
and
jackie
shared
it
with
me.
I
don't
remember
in
what
context
anymore,
but
I
just
kind
of
got
stuck
reading
through
it
and
learned
a
bunch
of
new
things
actually,
because
I
I
kind
of
realized
that
I
haven't
really
been
like
involved
in
that
process
that
closely
and
wasn't
even
aware
of
some
of
the
activities
that
seem
quite
important.
B
So
one
is,
for
example,
collaboration
with
marketing,
and
I
personally
haven't
really
been
in
touch
with
the
marketing
team.
Much
and
I'm
not
sure
if
any
of
you
collaborate
with
marketing
or
like
get
on
a
call
with
your
product
manager
and
someone
from
marketing
and
do
you,
leverage
marketing
in
your
work
like
discovery,
work,
whether
it's
more
product
related
or
ux,
because
I
I
like,
I
think
it
can
be
very
beneficial-
and
I
haven't
really
seen
us
do
much
of
that.
But
I
wonder
maybe
other
teams
do.
A
My
I
think
that
the
only
experience
I
had
working
with
marketing
was
in
the
release,
management,
team
and
jackie,
and
I
work
with
them,
but
to
facilitate,
like
the
the
the
release
management
vision,
so
that
three
years
mocks.
You
know
that
we
built
together
and
part
of
the
conversation
with
marketing
was
that,
okay,
how
do
we
use
these
efforts
and
the
vision
that
we're
building
in
in
terms
of
deliverables
and
visuals
to
facilitate
their
conversation
with
potential
customers
right
on
a
day-to-day
basis?
A
Not
recently
not
with
that
team
runner,
because
I'm
not
involved
as
much,
but
when
working
on
a
three-year
vision?
It
was
something
active
that
yeah
we
got
feedback
from
them
and
but
mostly
to
to
understand
how
we
want
to
shape
those
those
assets,
the
mock,
the
videos
and
how
we
want
to
add
them,
for
example,
to
the
the
direction
page,
because
it's
a
marketing
page
right
in
a
way
for
the
release
management
categories.
So
that
was
my
experience.
Maybe
someone
else
has
the
some
insights
to
share.
D
So,
for
example,
I
was
checking
on
our
group
page,
which
is
in
the
handbook
to
see
if
we
have
listed
any
stable
counterparts
from
the
marketing
side,
but
I
see
that
we
don't.
I
think
we
used
too
long
back.
I
don't
know
if
anyone
else
observed
that,
because
I
remember
like
looking
the
marketing
person
in
one
of
the
conversations
like
about
six
months
back
or
so
I
don't
exactly
remember
the
context.
Maybe
it
was
regarding
the
jenkins
importer
nadia.
D
So
I
know
that
we
get
in
touch
with
essays
and
tams
very
often
and
there's
also
a
meeting
a
regular
meeting
that
pipeline
execution
authoring.
I
think
the
whole
verified
team
has,
with
times
and
essays.
B
D
B
Whatever
you
can
skim
through
it
and
like
it
says
that
product
managers
are
supposed
to
practically
reach
out
for
input
when
contemplating
new
features
and
involve
product
marketing
as
early
as
possible,
with
work
and
important
changes
and
since
ux
and
product
work
so
closely
together
on
new
feature
design,
I
would
expect
to
like
be
in
touch
with
product
marketing
if
it's
part
of
our
process,
but
it
seems
like
it's
documented,
but
it's
not
really
happening,
and
I
actually
so
we
do
stay
in
touch
with
tams.
B
That's
true,
maybe
that's
kind
of
the
counterparts
that
they
mean
here
in
the
handbook.
Maybe
it's
just
not
specified,
but
probably
would
be
worth
just
could
reaching
out
to
jk
and
yes.
A
That's
a
very
good
topic.
It
probably
is
happening,
but
we
are
not
in
the
loop
right.
It's
just
like
some
of
the
things
that
yeah
that
happen
in
the
in
the
product
world
that
we
might
see
the
results
of
these
conversations
in
terms
of
deliverables
or
priorities
for
design,
but
not
necessarily.
A
We
are
part
of
the
conversation
and
I
linked
here
our
handbook
page,
the
ci
cd
wax
handbook
page
that
links
to
our
strategic
counterparts
and
yeah
for
product
marketing,
for
I
forgot
about
another
name
that
I
just
read
but
anyways
other
folks,
so
maybe
yeah
just
checking
with
your
pm
how
they
are
collaborating
today,
yeah
go
ahead,
meet
her.
D
I
see
the
name
of
chrissy
on
our
in
the
handbook
page
in
the
verify
section.
Sorry,
where
are
we
in
the
agenda?
I
want
to
paste
this
link
yeah,
so
I
did
collaborate
with
chrissy
on
one
of
the
blog
posts,
some
time
back,
which
was
around
pre-filled
variables,
so
I
remember
doing
that,
but
otherwise
I've
never
had
an
interaction.
Apart
from
that,
we
do,
however,
keep
in
touch
with
the
customer's
success,
their
for
example,
jamie
and
vladimir
for
pipeline
authoring,
as
well
as
execution.
B
Okay,
I
will
reach
out
to
dolph
and
ask
him
and
see
if
he's
been
in
touch
with
marketing,
because
I
think
it
could
be
interesting
to
reach
out
to
them
and
see
like
what
are
they
up
to?
B
Yeah
so,
and
very
quickly,
just
the
other
item
that
I
wanted
to
share
is
that
I've
conducted
a
competitor
evaluation
for
pipeline
authoring
kind
of
following
the
the
process:
the
new
process
for
competitor
evaluations,
though
it's
been
a
bit
tricky,
given
the
experience
that
I'm
testing
is
all
just
like
documentation
based
and
there
wasn't
really
much
to
evaluate
in
the
ui
in
terms
of
the
heuristics
that
we
have
that
we're
supposed
to
use.
B
But
I
did
my
best.
So
if
you
link
through
to
the
issue
you'll
see
that
there
is
a
brief
insight
summary
where
I
summarized
the
user
experience
for
setting
up
a
custom
library
of
ci
templates
or
actions
using
github
actions
and
using
circle
ci.
So
in
circle,
ci
they're
called
orbs
these
kind
of
reusable
pipeline
components
or
jobs.
So
you
can
check
it
out.
They
kind
of
follow
a
similar
process,
but
they
have
their
own
differences
and
yeah.
A
This
is
it's
awesome,
thanks
for
sharing
that
yeah,
I'm
not
sure.
If
I
wasn't
in
the
ux
weekly
yesterday,
I'm
not
sure
if
you
already
shared
this,
I
I
saw
you
share
it
in
slack,
but
make
sure
you
you
know
you
broadcast
this
because
there's
a
conversation
going
about
like
on
how
other
designers
are
conducting
competitive
competitor
evaluation,
and
it's
always
good
to
have
that
reference.
Even
though
yeah
this
is
not
part
of
the
the
main
ux
kr.
So
thanks
for
thanks
for
sharing
with
us
yeah
thanks.
D
All
right,
so
I
just
wanted
to
I
mean
mentioned
once
again
that
we
have
completed
the
evaluation
for
the
ux
scorecard
exercise
for
variables
and
if
you
go
to
this
epic,
that's
linked
there.
Many,
like
all
the
links,
are
in
the
finding
section,
there's
the
heuristic
evaluation
page,
which
has
the
final
heuristic
score
and
how
we
arrived
at
it.
D
Then
the
two
videos
that
I
have
put
link
to
two
videos,
one
is
for
a
shorter,
like
a
shorter
overview
of
the
whole
process,
and
one
is
a
longer
one
where
I
have
actually
performed
each
task
that
we
asked
the
users
to
perform.
So
just
like
very
minutely
touching
upon
every
step
that
they
followed,
whereas
the
shorter
one.
It
only
has
it.
D
It
only
talks
about
the
problems
and
not
necessarily
shows
them
right
there
on
the
screen,
like
them
happening,
and
one
strange
thing
that
I
found
in
the
findings
from
this
exercise
was.
I
was
not
expecting
that
most
of
the
insights
which
we
would
like
get
from
this
research
would
be
tight
tightly.
D
I
mean
they're
very
tightly
associated
with
the
pipeline
authoring
jobs
to
be
done,
and
now
it
kind
of
becomes
very
clear
to
me
why
this
set
of
features
is
being
transferred
to
pipeline
authoring
team,
because
it
totally
makes
sense
because
most
workflows,
which
are
related
to
are
associated
with
variables
in
gitlab
ci,
they're,
very,
very
finely
ingrained
with
the
pipeline
authoring.
Workflow
like
it's
a
part
of
when
you
write
the
camel
definition
for
gitlab
ci
configurations,
so
most
of
the
insights
they
are.
D
They
could
be
variable
agnostic
as
well
like
if
you
just
take
out
the
word
variable
from
there.
They
kind
of
fit
in
other
situations
as
well,
but
we
try
to
look
at
like
what
is
it
that
users
are
trying
to
do
with
variables
specifically
and
for
recommendations.
D
What
jackie
had
suggested
to
me
was
that
I
should
look
at
framing
the
recommendations
from
the
deficit
point
of
view,
because
I
mean,
if
you
just
try
to
translate
the
insights
into
recommendations.
They
might
not
work
very
well.
So
that's
an
approach
that
I'll
be
taking
for
recommendations,
but
this
is
pretty
interesting.
B
D
D
D
Earlier
the
my
earlier
idea
like
why
I
started
writing
this
was
I
thought.
Maybe
there
are
strategies
that
we
have,
that
could
help
save
users
the
ci
minutes,
but
after
doing
my
research,
after
speaking
to
the
backend
engineers,
I
figured
that
that
doesn't
exactly
happen
that
way.
For
example,
they
can
definitely
crunch
the
time
of
the
execution
of
the
pipeline,
but
what
happens
is
like
jobs
happen
to
run
in
parallel
in
those
situations
and
every
minute
is
still
accounted
for.
So
it's
not
like.
D
We
are
making
those
minutes
smaller,
we're
just
trying
to
divide
them
into
different
steps.
So
that
things
are
accomplished
like
quickly
so
here's
the
mr
and
hannah,
so
thank
you
so
much
for
the
very
long
review
that
you
left.
It
was
very
helpful.
It
did.
It
does
make
it
look
so
much
better.
Now
and
now
I
passed
this
to
sarah
for
final
editing,
because
the
decided
date
for
this
to
be
published
was
21st
june,
and
it
was
interesting.
Nadia
also
pointed
out
this,
like.
D
B
I
just
they
just
said
one
question:
like
did
you
have
to
pitch
your
idea
to
them
and
to
justify
that
we
need
to
publish
this
and
what
was
the
process
like
and
how
do
they
evaluate
your
blog
post
like
who
decides
yay
or
nay,.
D
Sure
I
will
put
the
link
for
the
issue
where
I
pitched
the
blog,
so
what
I
had
to
do
was
I
had
to
write
the
page
first.
Where
is
it?
Where
is
it
okay
here?
D
So
in
this
issue,
you'll
see
that
there's
a
template
that
allows
you
to
check
certain
boxes
like
what
all
criteria
does
this
pitch
fulfill
like?
Does
it
help
in
connecting
with
potential
customers?
Does
it
drive
traffic
to
the
website?
Does
it
convert
traffic
into
leads
and
based
on
those
criterias?
D
The
decision
is
made
and
then
the
roles
in
the
responsibilities
section.
It
was
again
filled
by
sarah
who
is
responsible
for
okay,
I'm
not
able
to
find
that,
but
she
was
the
one
to
actually
assign
a
date
to
this
and
then
tell
me
like:
when,
should
I
send
her
the
first
draft
to
be
edited
reviewed,
so
that's
mostly
captured
in
this
issue,
and
then
I
associated
that
merge
request
with
this
issue.
B
A
And
my
question
was
going
to
be
the
same
like
about
the
process
of
really
okay,
not
to
give
a
heads
up.
So
I
looked
in
the
marketing
folks
and
slack
about
what
needs
to
be
done
for
us
to
create
a
ux
category
in
the
blog,
so
they
require
yeah.
There's
something
technical
needs
to
happen
anyways.
A
So
that
should
happen
sometime
soon,
but
we
need
well
either
someone
here
that
wants
to
go
into
the
handbook
code
and
update
that
or
someone
in
a
marketing
team,
someone
technical
to
make
that
update
for
us.
So
it's
in
my
backlog,
but
hopefully
I
yeah-
I
haven't
written
anything
for
the
the
blog
now
that
theater
doesn't
exist
anymore.
That
process
is
dedicated,
but
I
imagine
that
yeah
it
would
be
a
bit
easier
for
us
to
contribute
if
we
have
the
ux
category,
but
thanks
to
exeter
viveka.
A
D
So
I
also
did
like
most
of
the
things
manually
because
there
were
a
lot
of
conflicts
because
it
happened
so
that
you
and
I
we
were
editing
at
the
same
time.
Oh
and
yeah.
C
A
So
ux
blog
category
right,
so
I'm
not.
C
A
Needs
to
happen
so
where
was
we
because
of
ux
block
category?
This
is
my
initial
merge
request
and
it
really
just
adds
a
mention
in
the
handbook
about
a
ux
category.
But
let
me
link
you
to
the
thread
in
the
marketing
channel.
A
Let's
see,
neighboring
explain
what
needs
to
be
done
and
who
needs
to
be
looked
in.
Actually,
that's,
I
think,
that's
most
important,
the
who
is
the
dri
in
marketing
you
can
you
can
open
that
person?
Look
the
person
there
you
go.
C
C
D
Okay,
moving
to
the
last
point
that
I
have
so
I
just
wanted
to
make
another
that
piping
execution
team
is
focusing
on
ci
minutes
for
this
milestone
and
the
focus
for
the
upcoming
milestone
is
going
to
be
working
on
our
availability.
That
means
working
on
a
bunch
of
infrared
issues.
D
That's
just
just
an
update
and
nothing
else.
A
Problem
to
some
good
news,
not
that
which
we're
not
doing
good
news
but
we're
gonna
have
a
designer
joining
our
teams,
so
gina
she's
gonna
join
get
lab
july,
12th
she's,
actually
a
pikachu's
referral,
so
someone
that
comes
highly
recommended
and
she's
going
to
start
in
july
still
some
some
time
to
come
and
I'm
very
excited.
A
This
is
a
it's
such
a
great
time
for
our
team
to
grow
and
also
for
me
to
be
able
to
off-board
helping
a
runner
and
yeah
we're
gonna
have
some
onboarding
process,
but
also
boarding
body
activities
going
on.
A
So
if
any
of
you
wants
to
be
the
buddy
or
wants
to
volunteer
for
other
tasks
as
well,
there's
your
time
but
yeah
feel
free
to
reach
out
to
me,
and
then
we
can
coordinate
that
and
what
I
can
tell
ya
that
this
person
is
also
coming
from
red
hat
like
like
fitika,
and
they
have
experience
working
with
design
systems,
which
is
super
exciting
because
it's
one
of
my
plans,
one
for
a
plan
for
it
for
testing
runners
to
get
someone
that
understands
a
bit
more.
A
A
Very
happy,
as
you
know,
has
been
a
very
long
two,
almost
three
months
interview
having
protests
so
july
beauty,
member
and
on
the
same
notes.
The
package
position
is
open.
It's
not
available
yet
on
on
the
the
hiring,
not
the
the
job
board,
because
you
need
to
do
the
kickoff,
but
it
was
approved.
So
we're
gonna
be
back
feeling
the
package
position.
So,
as
always,
referrals
are
much
appreciated,
so
I'll
work
on
the
criteria
for
that
the
position
when
I'm
back
from
from
my
pto.
A
A
A
So
I'm
not
sure
if
this
is
going
to
be
the
best
way,
but
I
want
to
I
want
your
feedback
and
I
want
to
know
now.
What
do
you
think
is
the
best
way
to
keep
track
of
that,
because
I
know
that,
of
course,
now
we
we
have
a
reduced
ux
researchers
supports
but
at
the
same
time
as
our
team
grows
and
as
we
involve
new
people
etc.
I
want
to
have
about.
A
I
need
to
have
a
better
visualization
of
what's
being
planned
or
what's
coming
next,
and
I
know
that
for
problem
validation,
things
leave
in
place,
solution,
validation,
things
live
here
and
there
but
anyways.
I
need
to
track
those
efforts,
so
I
created
this
epic,
which
is
an
umbrella
epic
and
right
now
it's
it's
pretty
much
empty.
I
think
only
vitica,
I'm
not
sure
if
nadia
has
one
but
another
vehicle
had
that
research
initiatives
for
verify
and
yeah.
A
D
So
one
thing
that
comes
to
my
mind
is
that
in
pipeline
execution,
jackie-
and
I
we
already
use
an
epic,
so
we
assign
whatever
is
the
work
in
progress
to
that
epic.
So,
while
I'm
working
on
that,
I
would
definitely
not
be
able
to
add
to
this.
That's
why
I'm
thinking
like
how
else
can
this
be
done
like?
Could
there
be
a
table
as
well,
where
I
can
just
put
items
in
when
it's
done?
Maybe
I
can
move
it
to
this
epic
altogether.
A
I
think
the
table
would
also
work
so
that
we
can.
We
don't
have
to
stay
locked
because
an
epic
just
moves
to
a
different
epic,
like
what
you
did
for
that
that
research
tracking
issue.
But
the
only
thing
is
that
yeah
we're
gonna
have
to
keep
it
up
to
date.
But
let's
try
in
the
beginning
to
see
how
it
works,
because
if
we
have
let's
say
we
have
just
a
quarterly
plan
for
research
efforts,
I
don't
think
we
are
going
to
play
this
every
day,
but
it
can
be
a
table.
B
Yeah,
for
me
also
for
me
also
epic,
wouldn't
work,
because
the
way
we
organize
all
issues
is
by
feature
or
like
product
category.
So
if
we
have
a
big
feature,
epic,
I
like
to
keep
a
solution-
validation
issue
linked
to
that
epic,
so
it's
accessible
to
the
product
manager
to
the
engineers,
it's
much
easier
for
them
to
find
that
way,
because
then
we
basically
have
issues
for
like
iteration
implementation,
any
design
issues
and
solution
validation
all
right
there.
B
C
A
So
I
was
only
thinking
about
the
new
things,
so
this
quarter
and
upcoming
ones
and
then
yeah.
Maybe
we
can
have
a
place
where
I
say
current
or
upcoming,
research
and
past
research,
india
at
the
bottom,
but
ideally
yeah.
Just
for
the
sake
of
what
needs
to
be
to
retract
right
now,
the
new,
the
new
stuff.
I
do
myth
in
general
also
when
I
was
actively
working
on
validation,
I
did
miss
having
one
place
where
I
could.
A
Of
course
we
have
dovetail,
and
we
have
all
these
insights,
but
that's
the
nice
thing
I
need
to
go
and
search
for
it
and
now,
as
a
manager,
I'm
also
like
okay,
where
where's
the
source
of
truth
for
that
for
our
team.
So
it
could
be
an
issue.
It
could
be
an
epic,
but
it
could
also
be
a
handbook
right.
I
saw
that
her
package.
They
have
a
small
section
in
in
the
package
page
where
they
say
this
is
the
research
that
we
have
planned.
A
A
So
but
well,
I'm
sure
if
you
can
hear
this,
someone
is
working
on
the
back
here,
but
thanks
for
the
thanks
for
the
the
feedback,
I'm
gonna
look
into
this
and
try
to
simplify
a
little
bit.
So
it's
not
yeah
such
a
difficult
process
for.
A
A
B
Sorry,
I'm
a
bit
I'm
freaking
out
a
little
bit
because
there's
a
huge
spider
right
next
to
me
and
it
keeps
moving
closer
and
closer
to
me
just
like
incrementally
now
it's
it's
yeah,
it's
becoming
a
bit
weird,
but
yeah
anyway,
I'm
just
gonna
like
squish
over
to
the
into
the
corner
yeah.
B
Just
I
wanted
to
remind
you
that
we
have
a
ux
book
club
currently
ongoing
and
this
time
it's
in
collaboration
with
the
growth
team
and
we're
all
we're
all
reading
this
book
called
better
on
boarding
to
understand
how
to
create
better
onboarding.
So
I
think
it's
going
to
be
a
really
fun
discussion,
because
the
girls
team
is
participating,
so
they
have
lots
of
ideas
and
insights
to
share,
I'm
sure
so
feel
free
to
join.
I
think
the
discussion
is
in
like
two
weeks
or
something
like
that.
B
Yeah
double
check
in
the
channel.
If
you
go
to
that
channel,
there's
a
date
there
for
the
discussion.
I
think
okay.
A
All
right
now,
I
see
that's
why
jackie
posted
like
an
illustration,
I
think,
of
the
book.
The
book
over
which,
on
the
specific
folks,
saw
it
in
the
the
ux
the
fun
channel,
that
we
have
someone
posted
an
illustration
of
the
cover
of
this
book,
so
maybe
they're
also
reading
it
sorry
random
size.
I
thought.
D
That's
awesome.
So,
since
we
are
talking
about
books,
there
is
another
book
that
I
recently
finished,
which
I
found
it
on
one
of
the
handbook
pages.
I
don't
remember
exactly
which
one
but
so
far,
I
think
it
was
the
best
one
that
I
read
on
product
management
like
even
though
I'm
not
directly
like,
I
don't
associate
with
those
job
responsibilities
directly.
It
was
really
good
to
understand.
D
What's
like
what
goes
on
in
the
head
of
a
product
manager,
it's
called
the
bill
trap
and
I
think
jackie
and
I
would
have
a
coffee
chat
around
it,
because
she
is
also
a
fan
of
that
book.
So
that's
one
and
next
in
line
that
I've
picked
up,
is
unlocking
customer
value
chain,
because
this
particular
quarter,
I'm
trying
to
read
more
about
product
management.
D
I
it's
written
here.
It
says.
A
But
remember
especially
the
things
that
we
see
in
the
handbook,
you
can
expense
those
right
so
yeah.
I
know
that
you
love
reading,
make
sure
that
you
you
taking
advantage
of
of
that
that
benefits
reading.