►
From YouTube: CI/CD UX Meeting - 2021-05-19
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).
B
Just
quick
fyi
is
update,
so
we
have
friends
and
family
day
next
friday.
Also
chrissy
gave
an
announcement
about
reimbursement.
So
if
you've
been
expensive,
individual
software
subscriptions,
those
are
no
longer
going
to
be
remember,
so
you
can
see
the
commit
and
if
there's
any
tool
that
are
super
necessary
check
the
process.
There
is
not
a
process
for
opening
an
issue
to
have
that
approved,
or
at
least
attentively
approved
for
the
whole
department.
B
My
last
fyi
I'll
be
out
of
office
in
june.
For
two
weeks
I
created
a
coverage
issue.
It's
a
work
in
progress,
but
you
can
check
there
and
valerie
will
be
covering
for
me,
but
just
a
fyi.
It's
a
bit
far
ahead,
but
just
so
you
know
yeah,
even
if
you
want
to
voice
your
comment
before
I
jump
into
the
discussion,
I
think.
C
Yeah,
I
am
back
home
after
traveling
for
what
feels
like
forever,
so
my
schedule
will
go
back
to
its
normal
cadence
for
anyone
that
was
sinking
with
me.
So
things
are
back
to
normal
showers.
B
My
first
discussion
item
is
also
an
announcement,
but
at
this
time
I
need
an
action
from
you.
If
you
haven't
completed
the
survey
yet
to
review
the
current
product
design
responsibilities,
please
do
that
before
friday,
so
valerie
wants
to
have
all
designers
or
product
designers
replying
to
the
survey
and
completing
it.
If
you
have
any
questions.
A
B
C
Yeah,
I
just
wanted
to
give
everyone
an
update
on
the
mr
winters
project,
which
is
a
huge
cross-culinary
stripe,
the
cross-stage
collaboration
effort
that
we're
working
on.
We
did
an
audit
thanks
to
everyone
who
made
sure
we
had
all
the
relevant
screenshots
and
copy
and
all
of
the
stuff
we're
going
to
work
with
the
foundations
team
and
the
tech
writing
team
to
create
patterns
and
standards,
and
then,
hopefully,
in
a
few
weeks,
we'll
be
reaching
out
again
to
all
the
designers
and
say:
hey:
we
have
new
standards.
C
Can
you
review
them
and
can
you
apply
them
so
I
just
want
to
give
everyone
an
update.
D
Thanks
ian
yeah,
I
wanted
to
share
a
quick
update
on
an
unblocker
that
came
up
for
the
manual
allow
and
deny
deploy
actions
issue.
So
some
of
you
may
have
seen
I
wrapped
the
solution.
Validation
to
good
results,
mostly
the
the
workflow,
was
very
understandable
by
the
users.
The
entry
point,
not
so
much,
but
I
would
say
the
core
of
of
the
design
is
succeeding
in
in
explaining
to
users
how
to
allow
or
deny
deploy.
D
However,
it
was
raised
by
by
one
of
the
backend
developers
in
the
team
that
the
way
this
flow
is
set
up
doesn't
really
match
both
the
behavior
of
the
operators
that
that
work
with
deploys
today,
but
also
the
actual
technical
foundation
of
the
merger
quest
right,
there's
a
whole
reason
for
that,
but
essentially
the
way
things
are
set
up
in
this
design.
D
With
the
approval
being
tied
to
the
merge
request,
you
could
reject
the
deploy
of
one
merge
request,
but
then,
since
the
merge
requests
already
already
merged
in
the
next
one,
if
you
approve
it,
you're
also
approving
the
code
from
the
previous
one
that
was
removed
rejected
right.
So
it
was.
It
was
a
bit
shocking
to
figure
this
out
so
late
into
into
solution.
Validation,
especially
considering
the
validation,
was
successful
for
for
the
design
itself
and
how
it
was.
The
feature
was
done,
but
the
feature
was
built
on
top
of
wrong
assumptions.
D
I
would
say
so
at
this
moment
I'm
going
to
have
a
sync
meeting
with
shinya
tomorrow
tomorrow
to
to
better
understand
this
use
case
and
see
how
we
can
adapt
the
embc
with
as
little
effort
as
possible
to
be
implementable
at
a
small
step
but
yeah.
I
wanted
to
hear
from
you
if
you've
faced
the
situation
before,
because
for
me
it's
a
bit
frustrating.
I
spent
one
milestone
designing
this
and
another
validating
only
to
now
realize
the
problem
space
and
the
context
wasn't
very
clear
from
the
beginning.
B
I'll
write,
my
comment
and
I'll
take
notes.
I
think
this
is
a
shame,
of
course
danielle,
but
I
think
also
in
particular,
with
the
release
very
coming
from
so
much
transition.
I
can
imagine
that,
for
example,
shinya
was
not
involved,
so
there
was
no
engineering
looking
to
the
problem,
validation
phase
with
the
pm.
That's
my
assumption.
B
I
think
that's,
that's
a
good,
well,
a
painful
lesson
learned,
but
at
the
same
time
it
shows
how
important
it
is
for
developers
to
be
on
top
of
the
problems
that
we
are
validating
and
giving
input
on
every
every
step
of
the
way.
The
process.
B
Please
add
me
to
that
to
the
call,
because
I
have
context
as
well
or
this,
and
I
would
I
think
I
could
be
helpful
to
you
and
xenia,
but
I
think
moving
forward,
make
sure
that
you
know
vpn
engineering,
of
course,
and
designs
are
aligned
in
whatever
validation
that
we
do
and
I'll
pause
now
in
case
someone
has
hands-on
transfers
experience
with
something
similar.
E
Yeah,
I
don't
have
experience
specifically
with
deployment,
I
know
barely
anything
about
deployments,
but
it's
just
I'm
very
familiar
with
the
problem
of
not
getting
the
workflow
right,
I'm
now
kind
of
really
trying
to
slow
things
down
with
the
new
feature
that
we're
starting
to
work
on,
and
it's
been
a
bit
of
a
struggle
to
get
everyone
involved
in
discussing
the
workflow
specifically
and
hashing
out
all
of
those
questions,
because
I
feel,
like
there's
kind
of
this
urgency,
to
kind
of
move
on
to
actually
creating
like
a
more
specific
solution.
E
So,
like
I
it's,
it
happens
all
the
time,
so
it
sucks
that
it
happened
to
you,
but
don't
feel
bad
about
it.
It's
like,
I
think
it's
just
really
important
that
we
slow
down
and
go
back
to
the
drawing
board.
So
it's
great
that
you
at
least
learned
about
it
would
be
much
worse
if
everyone
just
moved
forward
with
implementing
this,
which
can
also
happen.
I'm
sure
it's
happened
before
so
so
is
the
problem
that
mrs
are
not
part
of
the
workflow
is.
Is
it
what
shiny
is
saying.
D
So
it
it
is,
so
it's
both
right
on
one
hand,
operators.
They
don't
really
work
that
much
on
the
merge
requests
from
from
the
validation
like
they're.
They
are
more
familiar
with
the
pipeline
graph,
but
even
so
pipeline
emerge
requests
is
not
exactly
where
they
work,
which
I
don't
think
it's
it's
the
biggest
problem.
I
always
knew.
D
The
entry
points
were
a
stop
gap
into
a
more
definitive
solution
in
the
future
likely
in
the
environments
page,
but
I
think
the
main
issue
really
is
the
fact
that
the
approval,
the
way
it
works
now
based
on
top
of
the
merge
request,
doesn't
really
work
on
a
technical
level
and
it's
it
was.
It
was
a
huge
surprise,
considering
the
amount
of
feedback
that
that
the
discussion
got
from
everyone,
even
even
chine,
even
other
developers
as
well.
D
Everyone
was
giving
really
good
feedback
in
terms
of
how
the
solution
should
work
and
how
how
the
the
interaction
should
work.
But
the
fact
remains
that
the
problem
space
and
the
context
and
and
the
jobs
to
be
done,
weren't
really
that
well
defined
to
begin
with.
So
so
we
were
building
on
shaking
and
shaking
route.
Essentially,.
B
Yeah,
I
think
this
is
a
similar
situation
that
vitify,
you
just
said,
joined
the
call
where
we
were
talking
about
some
the
solution-
validation
that
was
done
on
top
of,
like
what
danielle
just
said,
shaky
jobs
to
be
done,
shaky
assumptions
that
that,
from
a
technical
perspective-
and
that
makes
me
think
of
merge
strains.
So
I
think
we
were
in
a
very
simple
situation.
B
I
was
in
a
very
similar
situation
with
merge
strains
like
over
a
year
ago
and
vidica
inherited
all
these
problems
of
us
starting
to
validate
the
solution
with
the
problem,
not
very
well
defined,
or
the
technicalities
not
very
well
documented
for
the
future.
Hopefully
you
don't
have
to
voice
anything,
but
I
just
wanted
to
say
that
yeah.
B
It
makes
me
know
that
it's
a
singular
approach,
and
I
think
I
think
that
the
way
that
vitica
solved
that
problem
by
understanding
the
the
developer,
workflow
and
understanding
and
documenting
that
in
the
open
cannot
be
helpful
daniel.
It's
for
you
to
have
conversations,
or
at
least
keep
a
track
of
the
decisions
and
the
educated
blockers
for
the
technical
part
of
this
problem
to
communicate
with
your
developers.
D
Yeah
for
sure,
we'll
take
a
look
into
that.
My
my
feeling
is
that
release
as
a
whole
is
is
working
very
much
on
on
feature
level
and
trying
to
find
feature
parity
with
other
platforms
like
this
has
been
stated
before
right.
We
have.
We
won't
feature
parrot
with
spinnaker
that
kind
of
thing,
but
I
don't
feel
that
we
necessarily
have
a
well-documented
understanding
of
the
user
behavior
and
the
jobs
to
be
done,
and
all
of
that,
so
that
definitely
has
to
be
improved.
B
Yeah
that
that's
really,
that
sounds
not
surprised,
so
a
good
challenge
for
you,
but
keep
me
in
the
loop,
and,
I
think
add
me
to
that,
to
the
call
I
would
love
to
to
be
part
of
it
and
I'll
see,
because
I
work
also
with
jinyoung
for
for
over
a
year
thanks
for
bringing
that
to
the
discussion.
E
Yeah,
so
I
have
the
next
item.
I'm
actually
gonna
share
the
board
because
it's
gonna
be
easier
to
illustrate
what
I'm
currently
working
on.
This
is
like
the
big
thing
that
I'm
working
on
this
milestone
so
we're
starting
to
look
at
creating
an
experience
for
large
enterprise
customers
to
create,
maintain
and
enforce
libraries
of
custom
cic
templates
across
all
of
the
projects
in
their
organization.
E
So,
based
on
all
of
the
customer
interviews
that
dope
and
I
have
had
with
our
large
customers-
and
we
will
be
following
up
with
more
interviews
in
the
next
weeks
so
far-
I've
been
identifying
jobs
to
be
done
and
this
board
is
just
to
kind
of
document
the
existing
workflows.
So
this
is
like
a
typical
workflow
that
a
large
enterprise
organization
has
for
setting
something
like
that
up.
So
the
central
platform
team.
E
They
discuss
the
practices,
a
set
of
like
practices,
cicd
practices
that
they
want
to
follow,
and
then
they
create
a
live,
a
shared
library
of
pipelining
job
components.
They
create
a
documentation
hub
kind
of
like
a
github
handbook.
Basically,
just
usually
they
have
something
like
that
internal
and
then
they,
some
of
them
use
custom
scripts,
so
others
use
third-party
tools
to
enforce
those
pipelines
across
projects.
So
these
scripts
pull
specific
templates
from
the
library
and
they
just
inject
them
into
pipelines
in
those
projects.
E
Let's
say
you
want
to
make
sure
that
all
of
your
projects
run
specific
kind
of
linter
or
like
code,
quality
test
or
accessibility
and
whatnot.
So
on
the
one
hand
you
want
to
enforce
certain
icd
practices
just
for
the
sake
of
maintaining
some
kind
of
standard
and
keeping
everyone
efficient.
On
the
other
hand,
they
also
want
to
be
compliant
so
like
gdpr
compliant,
for
example,
and
there's
all
kinds
of
other
compliance
frameworks
that
large
organizations
need
to
make
sure
they
follow.
E
And
then,
if
they
forget
to
include
something
the
custom
script,
that
the
central
platform
team
wrote
will
send
them
notifications
if
their
project
isn't
compliant
and
some
organizations
even
go
as
far
as
archiving
those
projects
after
a
certain
amount
of
time,
if
they're
still
not
compliant.
So
so.
E
This
is
kind
of
like
what
we've
been
learning
on
our
end
and
we
recently
learned
that
the
compliance
management
team
released
a
very
similar
feature
that
we
knew
nothing
about
that
interacts
with
our
stage
and
we're
now
really
trying
to
play
catch-up
and
collaborate
closely
on
how
we're
going
to
make
their
future
play
well
with
what
we're
building.
So
they
they're
kind
of
solving
a
similar
problem,
but
only
focused
on
compliance
management.
So
there's
the
compliance
manager,
persona
cameron.
E
I
think-
and
this
person
is
mostly
concerned
with
making
sure
that
the
organization
passes
the
audit
and
that
they're
like
gdpr
compliant
and
some
other
compliance
frameworks.
They
have
to
meet
all
of
those
needs
and
they
create
a
pipeline
that
runs
in
a
separate
project
and
it's
it
attaches
itself
to
the
beginning
of
every
other
project
pipeline
if
it
has
like
the
compliance
label
applied.
E
So
it
creates,
like
a
whole,
wide
range
of
things
that
we
need
to
think
about
on
the
pipeline
authoring
side,
because
imagine
you
are
in
charge
of
creating
a
pipeline
or
like
authoring
a
pipeline
for
your
project,
and
you
come
to
the
pipeline
editor
and
you
write
your
configuration
and
then
you
run
the
pipeline,
and
then
you
see
that
there's
actually
a
compliance
pipeline
running
in
front
of
it
overriding
some
of
the
jobs.
E
You
wrote,
for
example,
so
we're
now
collaborating
on
some
on
some
things
around
surfacing
the
compliance
pipeline
inside
the
pipeline
editor
and
things
like
that
and
we're
starting
to
look
into
what
a
better
workflow
would
look
like
in
gitlab
for
creating
that
library
of
shared
templates
and
how
will
it
play
with
the
compliance
team
because,
on
the
pipeline
authoring
team,
like
I've,
never
thought
about
the
cameron
persona,
I
I
know
nothing
about
compliance
management
so
really
through
their
direction,
was
really
eye-opening.
E
So
we
will
be
doing
more
interviews
to
kind
of
fill
the
gaps
in
our
understanding.
Specifically,
we
need
to
learn
how
exactly,
in
those
large
organizations
the
compliance
team
collaborates
with
like
the
central
cicd
team,
like
the
team
that
actually
writes
the
pipeline
configuration,
how
do
they
communicate
and
things
like
that
so
yeah,
that's!
What's
on
my.
E
B
Thank
you
for
sorry
again,
thank
you
for
thank
you
for
sharing
that
says
now
go
ahead
and.
C
C
C
It's
interesting
that
you
bring
up
this
conversation
of
how
those
large
organizations
are
functioning
because
a
lot
of
the
questions
you
seem
to
be
asking
based
on
the
board
and
one
you
just
described-
aligns
with
what
we're
about
to
investigate
on
package,
which
is
how
do
those
non-developer
high
up
people
looking
at
organizing
an
organization
worth
of
stuff
want
to
manage
packages?
How
do
they
want
to
set
up
the
configurations?
C
And
so
not
only
do
I
think
we
have
an
intersect
to
explore
in
terms
of
how
do
we
create
pipeline
authoring
patterns
so
that
organizations
can
use
registries
there's
an
intersection
there.
We
could
explore,
but
just
the
larger
idea
of
how
do
we
take
our
project
group
and
possibly
workspace
organization
and
make
it
work
for
the
top
level
down
on
how
they
want
to
create
patterns
in
the
organization.
E
Yeah
actually,
regarding
package,
I
will
need
to
reach
out
to
you
to
learn
more
about
package
registries,
because
there
is
now
well
actually
we're
collaborating
with
shinya
on
it.
He
came
up
with
this
big
proposal
for
leveraging
package
registries
to
create
these
custom
template
libraries.
So
apparently,
I
have
no
idea
how
exactly
it
works,
even
though
I
spent
one
hour
on
a
call
with
him.
He
was
really
trying
to
explain
it
to
me,
but
maybe
you
can
shed
some
light
on
it.
E
So
if
you
have,
if
you
have
like
a
link
to
a
good
walkthrough
for
package
registry
setup
in
gitlab,
that
would
be
super
helpful,
because
I
had
a
look
at
the
documentation,
but
it
would
be
helpful
to
have
like
a
step-by-step
kind
of
ui
walkthrough.
D
Just
a
very
quick
comment:
nadia
thanks
for
sharing
this,
and
I
me
coming
recently
from
a
large
organization
that
used
gitlab
what
you
described
really
really
matches
my
experience
there
with
they
were
starting
to
have
a
central
team
that
was
going
to
own
like
node.js
pipeline.
So
so
they
were
doing
the
lag
work
by
themselves
to
have
these
templates
and
really
build
this
ownership
model
across
the
organization,
and
I
think
that's
that's
something
different
groups
that
gitlab
can
do
much
better
in
terms
of
supporting
shared
ownership
across
large
organizations.
D
Right
who
owns
pipelines
who
owns
packages
either
it's
small
teams
or
a
centralized
team,
but
sometimes
organizations
are
shifting
from
one
water
to
the
other
and
yeah.
I
probably
can
do
a
much
better
job
supporting
that.
C
I
wonder
if
we
have
an
opportunity
to
take
the
learnings
from
these
couple
different
initiatives
and
push
them
out
to
the
larger
organization.
Afterwards
of
this
is
how
we
learned
large
organizations
want
to
organize
themselves,
especially
when
packages
tend
to
exist
outside
of
individual
projects
or
individual
workflows
and
pipeline
authoring
is
something
that
they
organizations
from
what
I've
heard
want
consistency
and
patterns.
C
B
Yeah,
I
think
we
all
have
insights
and
findings
on
that
also
in
testing
runner.
We're
talking
about
enterprise
management,
personal
medicines,
related
management
as
well.
So
I
know
that
some
of
you
inherited
some
research
and
findings.
That's
a
that's
a
good
one
ian.
B
C
We
certainly
could
my
first
reaction
was
to
wait
as
nadia
kind
of
has
the
first
bout
of
research
focused
on
this,
so
that
there
is
data
and
then
there's
something
we
can
add
to
would
be
a
little
better
than
just
an
amorphous
kind
of,
maybe
not
even
a
nebulous
place
that
doesn't
actually
have
any
structure
to
it.
Yet
we
make
it
hard
to
collaborate
on.
E
Yeah
so
right
now,
austin
and
I
austin
from
the
compliance
management
team
will
be
collaborating
on
these
workflows
that
I
just
showed
you
and
I
think,
once
we
have
that
we
can
kind
of
build
upon
it.
E
I
think
it
would
be
really
cool
to
kind
of
see
all
of
those
workflows
in
one
place,
because
I
definitely
see
a
pattern
emerging
that
in
a
large
organization,
there
are
separate
departments,
kind
of
managing
these
things
and
they
just
have
a
separate
project
that
runs
their
pipeline
like
the
compliance
pipeline
or
like
the
a
project
with
all
of
the
different
cic
templates,
and
then
they
can
kind
of
feed
all
of
those
resources
to
all
of
the
other
projects
within
the
organization
and
the
projects
can
contribute
upstream.
E
So
anyone
can
open
an
issue
in
in
like
the
compliance
project
or
the
cic
templates
project,
for
example,
and
makes
it
make
some
suggestions,
so
they
don't
exist
in
a
silo,
but
there's
definitely
this.
I
think
compliance
management
calls
this
separation
of
duty
or
separation
of
responsibility.
E
If
I
will,
I
will
share
a
link
to
the
compliance
management
category
direction
because
it's
like
a
concept.
They
refer
to
a
lot
and
it's
something
that
large
organizations
are
just
trying
to
achieve.
They
want
a
separation
of
duties
and
they
want
to
be
able
to
like
allow
teams
downstream
to
just
do
their
work
without
worrying
about
the
the
things
that
have
been
set
up
for
them
kind
of
so
yeah.
E
I
will
let
you
know
once
the
workflows
are
defined
for
compliance
management
and
pipeline
authoring
and
then
I'll
share
the
project
with
you.
So
maybe
we
can
kind
of
add
on
to
it.
From
the
package
perspective.
F
Okay,
thank
you
so
much,
I'm
a
little
zoned
out,
so
I
wasn't
able
to
comment
on
most
other
things
but
nadia.
I
really
like
what
you're
doing
okay
so
in
in
ci,
we
are
facing
some
unanticipated
like
non-anticipated
problems,
so
there
was
this
issue
which
you
will
find
that
is
placed
under
the
issue,
one
subset
of.
If
you
go
to
that
it
has
a
history
like
it
was
open
long
back.
F
I
remember
attending
a
meeting
with
the
customer
and
tao
and
where
the
customer
was
explaining
what
kind
of
problem
they
are
facing,
but
how
they
explained
it
and
given
what
the
kind
of
knowledge
that
I
had
about
this
whole
stage
group.
At
that
point
of
time
I
took
it.
F
I
took
their
words
for
it
and
I
provided
a
design
which
was,
it
was
a
very
reactive
design
like
okay,
you
want
this
change
all
right,
we'll
provide
something
of
this
thought
and
the
whole
team
agreed
on
it
and
it
just
went
on
it
was
delayed
because
there
was
a
lot
of
back-end
blockers
that
we'll
we
were
facing
in
the
process.
F
And
finally,
I
think
it
was
this
milestone
which
has
just
passed
when
the
backend
work
had
started
and
alison
asked
a
couple
of
questions,
and
that
pushed
me
into
a
black
hole.
So
I
wasn't
able
to
sleep
so
I
realized
that
we
have
missed
a
very
crucial
piece
of
information
and
I
was
very
hesitant
that,
oh,
my
god,
if
I
bring
this
up
like
we'll,
be
taking
10
steps
back
into
this
very
important
problem
that
we
are
trying
to
solve
here.
F
But
so
the
first
thing
I
did
was,
I
convinced
I
I
did
kind
of
notify
everyone
on
the
gci
that
I
think
we
are
doing
something
wrong
here
and
alison
has
pointed
out
a
problem
that
is
much
deeper
than
what
we
see
on
the
surface.
F
Then
I
had
a
call
with
marcel
I
made
him
go
through
like
he
also
volunteered
to
go
through
all
the
possible
use
cases
in
mr
in
pipe
and
widgets,
and
then
I
kind
of
I
was
able
to
convince
him
like
we
have
a
really
big
problem
like
what
we
are
calling
that
user
user
said
that
they
are
able
to
see
a
merge
immediately
button
when
pipeline
when
merge
trains
are
enabled
and
pipeline
must
succeed,
is
enabled,
and
we
were
just
not
able
to
wrap
our
head
around
it
like
what's
happening
there.
F
It
turned
out
that
what
we
are
we
were
calling
merge
immediately
was
not
merged
immediately.
It
was
something
else,
but
it
was
appearing
as
a
different
button.
So
now,
yesterday
the
whole
proposal
was
flipped
over.
I,
like
I,
I
went
to
also
spoke
to
jackie,
like
what
should
I
be
doing
in
such
a
situation,
because
what
I'm
going
to
propose?
It's,
it's
really
going
to.
F
I
mean,
in
my
opinion
it
was
every
all
the
work
that
was
done
on.
That
issue
would
go
to
waste,
but
I
had
the
support
of
the
team
and
the
team
is
also
coming
up
with
like
really
good
ideas,
so
we're
just
changing
the
proposal
here
and
I
just
created
three
issues
that
I'll
be
adding
to
an
epic,
so
yeah
fingers
crossed
from
here.
F
And
similarly
we
also
had
this
issue
two
which
is
listed
here,
which
was
again
a
very
old
issue,
and
since
this
was
old
and
it
demanded
a
lot
of
changes
in
the
different
states
of
the
widget,
I
went
ahead
and
tried
each
one
of
them.
It
was
tedious,
but
I
found
that
most
of
them
are
not
even
valid
and
in
fact
the
proposal
that
was
kind
of
divided
between
states
could
be
combined.
So
I
went
ahead
and
did
that
as
well.
F
So
most
of
the
proposals
are
now
new
and
ready
to
be
acted
upon,
and
we
are
planning
that
if
we
are
not
able
to
accommodate
those
things
in
this
quarter,
we'll
probably
create
a
new
kr
altogether
to
address
all
the
mr
widget
usability
issues
in
the
upcoming
quarter,
and
this
was
a
little
scary
experience
for
me,
because
I
I
learned
a
lot,
but
I
don't
know
I
I
felt
that
I
felt
like
I
I
just
I
was
seeing
the
tip
of
the
iceberg
and
I
I
was
not
able
to
account
for
what's
underneath
and
there's
a
lot
underneath
and
now
I'm
I.
F
I
have
much
more
knowledge
about
what's
happening
in
the
mr
widget
and
how
many
billions
of
stages
we
have-
I
mean
states,
they
have
there
and
what's
going
on
like
what
are
the
different
points
where
these
states
evolve
and
so
on
so
yeah.
This
was
interesting,
but
this
led
to
something
else
as
well.
So
I
have
created
this
group
with
different
projects
and
each
project
is
actually
focusing
on
a
different
use
case.
F
For
example,
each
project
which
is
listed
in
this
group
has
a
different
setting
which
has
been
enabled,
and
so
if
anyone
wants
to
just
go
ahead
and
take
a
screenshot
or
a
snapshot
of
what
kind
of
widgets
appear
in
well,
let's
say
when
pipeline
must
succeed
and
merge
result
pipeline
is
enabled
they
can
just
click
on
that
particular
project.
Go
to
the
mrs,
which
are
open
and
take
a
screenshot.
F
So
I
try
to
make
it
easier
for
everyone,
because
we
are
having
to
do
this
very
often,
it
was
just
not
making
any
sense
creating
a
new
project
every
time
this
was
required
so
yeah.
This
is
one.
B
B
I
think
it
relates
to
what
daniel
was
talking
about
the
validation
right
about
the
ethically
pointed
the
importance
of
breaking
things
down
to
the
smallest
trans
possible.
I
think
bi.
You
also
had
that
without
you,
both
learning
right
about
the
technicalities,
that's
why
and
I'm
telling
you
this,
because
I
know
I
felt
in
my
skin
when
I
was
working
on
on,
merge
trains.
We
need
to
break
it
down
and
we
need
to
cover
edge
cases
and
document
and
have
these
tough
conversations
with
developers
sooner
than
then.
B
You
know
then
later
he
over
communicates.
So
I
really
appreciate
that
you
both
wrote
these
examples
of
not
so
happy
endings
or
the
happy
stories
and
the
real
challenges
that
we
face
here,
but
it
shows
how
it's
crucial
that
we
understand
the
technology
as
well
right.
That's
why
in
the
ux
the
product
designer
role?
The
first
item
is
understand.
The
technology
understand
the
product
area
you
are
assigned
to.
B
So
I'm
I'm
happy
that
you
both
share
this
these
examples,
and
I
think
it's
also
an
opportunity
for
you
to
maybe
collaborate
and
start
talking
about.
You
know
how
you're
solving
these
problems
in
two
different
age
groups
and
yeah
just
learn
together
and
reach
out
to
other
teams
where,
for
example,
there
is
a
higher
maturity
in
terms
of
research.
B
So
I
think
daniel,
for
example,
can
learn
a
lot
from
jackie
right
and
then
levitica
can
share
those
learnings
and
at
the
same
time
we
can
talk
about
how
you're
breaking
down
problems
and
documenting
your
your
technical
issues
and
show
that
to
daniel.
So
just
want
to
avoid
that,
because
I
think
you
you
both
brought
up
a
very
good
point
today.
F
Thanks,
okay,
so
I
think,
because
we're
already
over
time,
could
I
go
to
the
next
point?
Is
it
fine
with
everyone
yeah,
no
quickly,
okay,
so
yeah?
So
there's
this
project
that
has
the
notes
from
the
bad
conference
that
we
attended
via
nadia,
and
I
mean
I
later
realized
after
I
was
watching.
F
I
I
watched
the
recordings
that
it
actually
had
a
lot
of
good
insights
and
I
figured
that
there
are
certain
behavioral
change,
templates
and
techniques
which
are
which
already
exists
and
they
are
actually
very
complex
to
handle,
and
I
saw
in
one
of
the
talks
where
they
talked
about
how
you
could
club
those
techniques
with
your
with
the
day-to-day
process,
for
example
in
journey
maps
in
opportunity,
mapping
like
taking
some
parts
of
the
behavioral
technique,
mapping
and
then
putting
that
over
your
usual
processes,
creating
a
hybrid
process.
F
Out
of
that,
that's
something
that
we
can
definitely
try
to
do
and
in
fact
I
would
definitely
try
to
use
this
the
next
time
I
analyze
something
and
share
with
the
team
but
yeah.
F
That
was
my
takeaway,
which
I
haven't
typed
out
yet
and
the
last
one
which
is
read
only
is
the
ux
scorecard
we
are
about
to
conduct
like
we
are
about
to
start
off
with
the
interviews
next
week
and
it's
progressing
well.
It
was
again
a
very
technical
thing
that
we
are
going
to
try
this
time,
which
is
passing
variables
between
upstream
and
downstream,
and
I
feel
that,
besides
kind
of
evaluating
this
particular
use
case
of
passing
variables,
it
also
would
help
us
validate
a
few
things
about
upstream
and
downstream.
F
Maybe
I
wouldn't
analyze
them
directly,
but
I
will
definitely
pass
on
the
information
to
nadia
so
that
she
could
also
use
that
in
whichever
way
she
wants.
B
Very
very
fast:
well,
thank
you
so
much.
We
are
over
time.
If
you
have
any
questions,
please
reach
out
in
the
in
the
channel
and
thanks
everyone
for
joining.
This
was
really
really
really
helpful
to
me.