►
From YouTube: UX Showcase Facilitating Design
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
A
We
had
examined
other
products
workflows
as
part
of
this
design
work
and
we
worked
with
product
and
with
engineering.
And
finally,
we
had
come
up
with
a
proposal
to
offer
a
series
of
integration
options
and
building
the
integration
itself
with
a
new
stepper
component,
which
we
were
also
going
to
build
and
we
did
solution,
validation
on
the
design,
and
we
made
a
series
of
updates
to
the
design,
even
after
that,
based
on
feedback
from
other
stakeholders.
And
finally,
we
had
something
that
we
felt.
A
However,
for
a
handful
of
reasons,
as
has
happened,
sometimes
in
this
work,
that
plan
carefully
laid
plan
did
not
happen.
We
didn't
build
the
design
that
we
had
been
working
on
and
carefully
testing
for
many
months
and
instead
we
opted
for
something
that
would
be
a
kind
of
a
quicker
and
more
mvc
approach
and
why?
Why
did
that
happen?
A
A
A
I
had
a
lot
of
really
big
feelings
about
this
change
and
this
situation
I
felt
like
there
was
a
ton
of
pressure
on
me
at
that
moment,
because
the
entire
team
was
going
to
start
working
on
something
and
we
didn't
know
what
they
were
going
to
be
working
on,
and
it
was
in
just
a
few
days
and
on
you
know,
a
personal
level.
I
was
sad
to
lose
like
many
months
of
work.
A
For
for
me,
I
try
to
put
a
lot
of
time
and
care
into
what
I
do
so
to
not
have
it
be
used
at
the
end
of
the
day
it
was
hard.
It
was
hard
to
lose
that
work,
but
the
biggest
concern
for
me
was
that
I
didn't
have
as
much
confidence
that
the
end
result.
The
the
sort
of
long
form
that
we
were
building
would
be
usable.
A
We
did
have
a
quick
test
of
the
revised
design
with
an
internal
stakeholder,
but
I
hadn't
seen
it
tested
and
seen
it
in
action
in
the
way
I
had
seen
the
other
design.
So
I
didn't
know
if
it
would
all
work
in
the
way
that
we
wanted
to.
So
all
of
these
things
kind
of
combine
combine
to
make
the
situation
kind
of
stressful,
but
thankfully
that
wasn't
the
end
of
the
story
and
that's
why
I'm
here
to
talk
about
this
today.
A
A
A
A
Remarkably,
it
wasn't
just
a
single
engineer
that
was
helping
with
this
work.
The
whole
team
seemed
to
be
joining
in
people
were
actively
proposing
ideas
even
sometimes
designs.
They
were
grabbing
components
from
pajamas
and
making
mockups
in
the
browser
and
posting
them
for
discussion
with
the
team,
and
they
were
advocating
for
various
proposals
and
raising
handfuls
of
excellent
questions
like
together.
A
We
were
all
negotiating
improvements
to
the
future
in
a
way
that
tried
to
balance
the
different
technical
considerations
and
what
people
who
are
actually
using
the
feature
would
need
to
use
the
feature,
and
it
was
kind
of
amazing,
a
situation
that
could
have
been
really
bad
for
our
team
and
for
the
our
feature
turned
out
in
a
way
that
I
didn't
even
expect-
and
this
is
really
great-
and
I
don't
want
to
undermine
that
at
all.
This
was
amazing,
but
I
did
have
a
moment
where
I
sort
of
had
a.
I
had
a
moment's
pause.
A
There
was
a
moment
that
I
thought:
okay,
if
everyone
on
the
team
is
a
designer
now,
and
everyone
helps
with
proposing
ui
solutions
and
even
with
making
mock-ups.
Where
does
that
leave
me
like?
What's
what's
my
role
in
the
team
now,
like
I'm,
not
proud
that
I
have
this
thought
and
I
don't
think
it
aligns
with
how
I
want
to
operate
in
the
world
much
less
on
my
team,
but
I'm
here
when
I
admit
that
I
did
have
that
thought.
A
Something
really
shifted
in
my
head
and
I
feel
like
that.
Experience
was
sort
of
a
good
ego
check
for
me
and
I
really
started
thinking
about
myself
as
more
of
a
design
facilitator
on
my
team.
As
someone
who
works
to
create
spaces
for
collaboration
and
who
facilitates
that
collaboration,
so
that
together
we
can
work
towards
a
solution
as
a
team
and
as
I
was
putting
together
this
presentation
and
and
trying
to
verbalize
this
experience,
I
I
think
that
this
point
about
designers
as
facilitators,
probably
seemed
really
obvious.
A
A
I
previously
thought
of
design
facilitation
as
more
of
a
discrete
activity,
kind
of
like
a
one-off
workshop
that
you
hold
with
post-its
and
whiteboards,
and
you
run
different
activities
and
come
up
with
an
idea.
That's
kind
of
developed
separately
by
the
designer,
but
I
think
this
moment
with
the
team
taught
me
that
design
facilitation
could
be
something
more
than
that
as
designers,
we
can
be
more
than
just
people
who
make
the
mock-ups
and
we
can
instead
help
to
design
a
culture
in
which
people
can
really
show
up
and
share
and
do
their
best
work.
A
I've
also
been
trying
a
few
different
exercises
with
the
team
as
a
way
of
engaging
them
beyond
just
asking
questions
and
issues
for
our
long-term
vision
box.
We
ran
an
async
critique
and
tried
out
an
elevation
exercise
where
people
gave
feedback
on
three
different
levels:
satellite,
very
abstract
level,
airplane
level,
not
too
in
the
weeds.
A
But
still
kind
of
above
the
ground
a
little
bit
and
then
ground
level
very
much
in
the
weeds
feedback,
and
the
goal
here
was
just
to
get
people
thinking
about
and
interacting
with
proposals
in
a
different
way
and
also
to
really
just
help.
The
team
feel
like
they
were
part
of
defining
the
vision
for
a
feature
set.
A
Anyway,
this
experience
felt
important
to
share
this
form
because
I
don't
know
if
we
always
have
the
space
to
talk
about
this
kind
of
stuff.
So
I
wanted
to
share
this
presentation
kind
of
as
a
way
of
asking
all
of
you
to
if
you've
had
experiences
like
this
one
and
also
to
dig
a
little
bit
more
into
how
everyone
else
is
feeling
about
this
idea
of
designer,
as
facilitator,
I'd
really
love
to
hear
all
of
your
thoughts.
A
Also,
you
have
techniques
that
you
successfully
use
to
facilitate
more
of
a
design
culture
within
your
team.
I'd
really
love
to
hear
about
them
as
well,
and
that's
it
for
the
the
presentation,
thanks
for
listening
I'd
love
to
hear
if
you
have
any
thoughts
or
questions
and
if
you
don't
feel
confident
or
willing
or
wanting
to
to
talk
in
this
forum,
please,
like
send
me
a
slack
message
or
make
a
copy
chat,
because
I
definitely
would
love
to
hear
more
about
what
people
think.
So,
that's
that's
it
for
me.
B
Thank
you
amelia.
There
are
questions,
but
there
are
a
lot
of
read-onlys.
I
think
that
it
would
be
pretty
awesome
if,
if
you
read
only
folks
could
maybe
summarize
what
you
were
wanting
to
read
only
because
I
think
there's
some
really
awesome
points
there.
C
Yeah
I'll
go
first.
I
just
think
this
is
so
cool.
I
I
love
the
the
turn
it
took
into
being,
like
you
know,
from
a
project
and
mvc,
and
you
know
very
feature
focused
process
focused
into
this.
You
know
wow
everybody's
a
designer
now
and
where
does
that
leave
me?
I
I
really
respect
and
appreciate
your
your
vulnerability
and
sharing.
C
All
of
that
I
would
have
felt
exactly
the
same
way
and
I'm
sure
that
you
know
all
designers
at
some
point
have
or
will
come
across
a
point
where
it's
like
you
know,
you
feel
a
little
bit
threatened
when
other
people
other
designers,
even
but
engineers,
product
managers.
C
You
know,
come
up
with
ideas
and
I
know
I've
had
this
thought
of
like
oh,
I
should
have
thought
of
that.
I
should
have
been
the
one
because
I'm
the
trained
designer,
and
so
it's
it's
a
hard.
C
It's
it's
humbling
right
when
we
want
other
team
members
to
think
like
designers,
sometimes,
but
then
we
also
want
to
be
the
dri
and
we
want
to
be
like
the
experts
and
so
yeah.
D
C
I
just
really
appreciate
you
sharing
all
of
that
and
I
think
it's
extremely
relatable,
whether
we
all
talk
about
it
or
not,
and
I
think
we
should
be
talking
about
it
more.
So
I
think
a
really
important
lesson
to
learn
on
any
team
is
is
that
flexibility
that
you
kind
of
spoke
to
is
okay.
You
know
they're
running
away
with
with
ideas,
and
this
is
this
is
all
great.
What
can
I
do
here
if
not
make
mock-ups?
C
I
I
just
think
that's
so
cool
and
it's
so
exciting
to
see
how
in
these
showcases,
we
don't
just
always
talk
about
features
and
what
went
right,
because
I
think
this
is
the
most
valuable
lessons
to
learn
is
what
went
wrong
or
how
we
were
challenged,
and
so
I
I
just
think
it's.
This
is
so
cool
that
you
shared
all
of
that.
So
thank
you.
Oh.
A
E
Yeah
I
was
trying
to
catch
up
on
my
okr's
this
week
and
I
just
happened
to
watch
that
course
yesterday
and
it
I
mean
a
lot
of
what
is
suggested
in.
That
course
is
a
lot
of
what
you're
doing
you
know,
building
the
inroads
with
the
engineers-
and
you
know
inserting
yourself
as
part
of
that
team
and
helping
to
build
that
trust
in
that
relationship
and,
ultimately,
like
you
know,
we're
building
one
product,
we're
all
in
the
same
team.
A
Definitely
something
feels
like
it
shifted
into
place,
and
I
do
see
that
in
a
different
way
now
and
it
doesn't,
it
doesn't
matter
where
the
idea
comes
from
and
and
if
I
feel
like
it
has
to
come
from
me
or
something
that's
a
lot
of
pressure
on
me
and
I'm
not
going
to
come
up
with
all
the
right
ideas.
The
team
knows
things
that
I
don't
know
and
I
need
to
make
space
for
that.
But
it
was.
It
took
me
a
moment
for
sure.
B
Then
marcel
linked
to
a
nice
jared
school,
medium
post,
that's
he's
always
worth
reading
daniel.
You
know.
Did
you
want
to
say
something
specific
about
that
marcel?
Go
ahead.
D
No,
I
just
wanted
to
quickly
say
I've
been
previously
in
the
position
of
consultant
and
being
a
design
thinking
facilitator,
and
we
gave
week-long
workshops
for
super
diverse
teams
where
basically,
every
kind
of
function
was
in
the
room
and
really
seeing
them
over
the
course
of
the
week
going
more
and
more
into
thinking
about
the
user
first
and
seeing
how
this
affected
teams
in
the
long
term.
D
F
Yeah,
I
was
just
going
to
add
that
I've
also
felt
this
way,
especially
early
in
my
career.
I
had
you
know
the
feeling
of
somebody
else
is
challenging
me
or
taking
my
job
from
me.
What
reason
do
I
have
to
be
here?
Am
I
going
to
lose
my
job,
but
then,
as
I
grew,
I
realize
it's
not
just
design
that
we're
doing.
We
have
to
take
all
this
work
and
all
this
stuff
that
everyone
else
has
provided
and
try
and
validate
it
and
see.
F
G
Yeah,
I
just
want
to
say
that
it's
really
encouraging
thank
you
for
sharing
and,
like
maybe
something's
helpful,
when
I
facing
those
kind
of
situations,
a
lot
of
feedbacks
I'll.
Just
imagine
myself
as
a
pm
so
like
I
need
to
really
set
up
hard
time
like
guidelines
like
now.
We
gather
feedbacks
and
then
like
we
stop,
and
I
will
make
decisions
like
the
final
decisions
which
design
is
the
best
and
something
just
so
yeah.
A
Yeah
definitely
not
easy
for
me,
and
I
like
that,
that
idea
of
thinking
about
yourself
as
the
vm
and
just
kind
of
just
making
decisions
in
in
that
hat
wearing
that
hat
instead,
maybe
that
helps
shift
things
a
little
bit
in
your
head,
so
it
makes
it
easier
to
make
some
of
those
calls.
I
appreciate
that
thanks.