►
From YouTube: 3 04a Find the Yes Examples
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
C
Yeah,
it's
it's
definitely
a
risk
to
consider
right.
Will
we
get
ourselves
into
an
endless
situation
where
we
simply
can't
provide
something
that
they
need?
You
know
and
maybe
that
maybe
that
modifies
my
original
declaration
that
there's
always
something
we
can
can
suggest,
but
I'd
love
to
to
be
presented
with
a
specific
situation
and
see
if,
if
we
could
come
up
with
what
a
yes
would
be-
and
I.
A
Think
that
go
ahead,
I'm
thinking
more
like
you're,
the
customer
you
are
asking
me,
I
don't
know,
is
there
a
way
that
I
can
connect
girl
up
to
my
tv.
I
don't
know-
and
I
say
I
don't
know,
but
I
will.
I
will
talk
to
the
sales
team
and
I
will
talk
to
the
technical
teams
and-
and
I
will
see
I
will
see
what
we
can
do
to
to
help
you.
A
You
know,
then,
maybe
after
some
time
and
after
the
customer
asking
for
a
reply,
we
come
back
saying
like
I
haven't,
find
an
answer
and
I
think
that
it
might
not
be
possible
with
the
current.
You
know
setup
that
we
have,
but
then
the
reason
why
I'm
asking
is
because
I
am
I
I
remember
situations
where
the
customer
in
a
case
like
that,
will
come
back
and
say
like
hey,
but
you
said
you
were
going
to
help.
A
You
are
not
you
know
like,
and
that
is
the
that
is
for
me
the
the
danger
of
the
rabbit
hole.
It's
not
even
that
that
we
get
deeper
and
deeper
and
asking
several
things,
but
it
might
be
that
the
fact
that
we
are
trying
to
help
the
customer
backfire.
C
I
completely
understand
what
you're
saying
I
do
and
I
I
have
to
offer
that
first,
my
answer
the
customer
would
have
been.
Oh
you
want
to
hook
up
get
lab
to
your
tv.
You
just
need
a
pair
of
get
labbot
ears
and
then
okay,
so
bad
pun
aside,
I
think
that
the
most
important
thing
to
do
in
that
type
of
situation
to
avoid
creating
a
problem
for
ourselves,
is
to
be
very
clear
at
the
beginning.
C
What
you're
saying
right,
if
you
just
say,
oh
sure,
I
can
look
into
that
for
you
now
you're,
probably
stuck
right,
but
in
your
example
I'd
be
I'd,
be
much
more
tempted
to
say
we
don't
have
any
feature
of
the
product
that
does
that
right.
Now,
oh,
in
fact,
here's
a
very
simple
answer
for
that.
One
right
our
product
doesn't
do
that.
C
C
That's
a
yes!
So
there's
judgment
involved
right
now.
I
was
able
to
take
advantage
of
your
example
where
I
know
that
product
doesn't
do
it,
but
that
that
is
an
example
where
we
might
sometimes
be
tempted
to
keep
working
with
the
customer
when
really
the
answer
is
shorter
and
simpler.
Just
here
is
the
the
path
forward.
It's
the
enhancement
request
and
I
see
it
frequently
in
tickets.
C
A
support
engineer
will
say:
oh
this
thing
that
you're
trying
to
do
is
out
of
scope
for
support.
But
would
you
try
these
steps
for
me,
so
they
just
got
the
door
90
closed
and
then
reopened
it
wide
and
said.
I'm
here
to
help
you
so
we
created
a
problem.
So
we
need
to
deliver
a
very
clear
message
about
what
we
will
and
won't
do,
what
we
can
and
can't
do,
and
then
we
can
talk
about
what
are
the
options
for
the
customer
and
the
option?
Sometimes,
is
you
can't
get
exactly
what
you
want?
C
B
I
have
a
real
life
example
of
this
that
I
think
I
handled
fairly
well.
I
was
in
a
call
with
a
customer
over
updating,
ssl
certificates
and
they
and
that
all
went
fine
and
then
they're
like
okay.
We
have
matter
most
integrated
with
gitlab
we'd
like
to
update
the
ssl
stripping
on
that
too,
and
so
okay.
Well,
let's
look
into
this
turns
out.
B
A
C
Right
and
I
would
have
said,
hey
right
at
the
beginning
when
they
started
the
matter
most
talk,
you
say
you
know:
that's
definitely
not
something.
That's
within
our
scope
of
support
here.
We
can
only
help
you
with
get
lab
problems,
and
I
wouldn't
want
to
create
any
problems
in
that
system
by
even
trying.
C
So
do
you
have
matter
most
support?
Can
you
work
with
them?
So
you
know
you
open
that
door
for
them
and
suggest
it
then
when
they
say
they
do.
You
know
perfect.
Please
talk
to
them.
If
anything
turns
up
to
be
still
a
problem
here.
Let
us
know
we'll
be
back
to
help
you.
So
we
have.
We
have
a
really
strong
tendency.
I
support
people
getting
a
second
tom
to
to
want
to
help
right
anytime.
Someone
asks
us
for
help.
C
We
go,
I
can
help,
and
so
we
have
to
just
sort
of
restrain
ourselves
for
just
a
moment
long
enough
to
say
I'd
like
to
be
able
to
help,
but
really
here's
the
right
thing
to
do
and
then
do
that
right
thing
before
you
get
in
trouble.
Tom.
D
Yeah
to
follow
up
on
ronnie's
point
about
the
whole
rabbit
hole
thing
like
the
tv
example
you
know
get
lab
is
a
constantly
moving
target,
it's
impossible
for
any
one
person
to
know
every
little
thing
to
do,
because
there's
so
many
pieces,
there's
even
senior
engineers
who
are
like.
Oh,
it
does
a
thing
now
they
had
like
two
months
ago.
We
didn't
know
about
that.
D
You
know
and
they're
like.
Oh,
it
doesn't
know
like
so
you'd,
be
like
yeah
hooks
for
tv
now.
Somebody
else
says
we
can't
do
that
or
I
had
a
feature
of
like
yeah.
We
just
added
that
last
portrait
bro
it's
right
there.
You
know.
Oh,
so
it's
a
moving
target.
So
it's
hard
to
definitely
say
yes
or
no
or
I'll
put
a
feature
request,
because
then
you
got
to
call
them
through
everything.
It
can
do
and
pray
someone
you
know
made
about
this
new
feature,
that's
hard
when
it's
continuously
proving
every
single
iteration.
C
D
D
Would
be
like
gitlab
is
always
striving
to
improve
our
product,
add
new
features
whenever
we
find
it
to
be
reasonable
and
we
and
we're
constantly
adding
and
improving
our
product.
I
don't
know
this
time,
that's
capable,
but
I
can
look
into
it
and
let
you
know
if
you
feel
like
something
you
we
don't
have.
D
If
you
want
to
add
business
feasibly,
you
can
open
a
future
request
if
it's
something
within
the
scope
of
support
or
we've,
we've
talked
to
others
like
I'm,
going
to
confirm
my
resources
and
look
into
that
for
you
and
see
what
the
whatever
my
resources
will
say
about
that
and
we'll
get
back
to
you
on
that.
C
C
If
so,
let
me
know-
and
I
will
I
will
look
further
into
that
for
you.
Otherwise
I
will
check
just
to
be
sure
that
that
that
feature
isn't
there
right.
So
so
you
can
provide
some
extra
steps
at
the
beginning.
You
can,
you
can
even
go
the
short
route
like,
oh,
I
haven't
heard
of
that.
Did
you
read
that
somewhere
and
just
just
ask
them
to
let
you
know
if
they
did
you
just
say.
I'm
sorry
that
I
wasn't
aware
of
that,
that
you
know.
Let
me
let
me
dig
into
that,
for
you.
D
And
they
gotta,
you
would
have
to
probably
qualify
saying
you
know,
please
refer
to
get
live
documentation
because
it
knows
to
be
like
the
ceo's
blog
said
this
thing
they're
like
well,
that's
more
of
a
wishlist
thing,
something
you
would
like
to
see.
People
will
reference.
D
C
Yep,
so
I
think
what
we
have
here,
some
good
examples
of
how
you
can
how
you
can
handle
those
situations,
remembering
that
you
do
have
to
exercise
good
judgment
and
you
do
have
to
prevent
the
the
eager
support
engineer
inside
each
of
us
from
just
saying.
Yes
to
start
with,
you
want
to
find
the
yes,
not
just
blurt
it
out.