►
From YouTube: UX Showcase Making Maps
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
Name
is
nick
post,
I'm
a
designer
in
the
manage
optimized
team.
I
I
paused
there
because
I
always
get
confused,
because
we
had
a
name
change
the
other
a
couple
months
ago,
so
nick
post,
optimized
team
and
today
I
want
to
talk
about
making
maps
and
my
process
for
making
maps
and
all
that
good
stuff.
A
So
before
I
get
started,
this
is
a
public
server
service
announcement.
I
did
not
design
any
of
these
slides.
Jackie
said
just
to
make
sure
that
everyone
knew
that
I
didn't
have
the
time
to
create
these.
Nor
do
I
have
the
capability,
so
it's
stuff
that
I've
stolen
off
the
internet
and
I'm
relaying
to
you,
rather
than
actually
creating
for
the
specific
purpose
of
the
ux
showcase,
so
making
maps.
In
my
previous
job,
we
we
had
some
design,
thinking,
material
and
one
of
the
core
principles
of
this
design.
A
Thank
you,
material
was
was
the
principle
of
dimension
and
diagram,
and
I
want
to
talk
a
little
bit
about
the
principle
of
dimension
and
diagram
and
how
I
use
it
in
my
work
every
day
and
sort
of
talk
about
a
little
bit
how
I've
applied
it.
In
some
planning
sessions
and
some
of
the
outcomes
that
have
come
about
from
actually
using
this
work
and
how
it's
impacted,
my
team
and
me,
but
first
I'm
gonna,
go
into
this
and
talk
about
dimension
and
diagram
for
a
bit.
A
So
in
school,
we're
often
taught
to
structure
our
work
in
a
very
particular
way.
A
It's
it's
very
easy
to
structure
your
work,
not
sort
of
jig
it
about
and
basically
go
down
a
very
linear
path,
with
the
way
that
you
think
about
a
particular
problem,
but
there's
actually
a
lot
of
room
and
opportunity
for
using
visualization
and
design
skills
to
think
about
problems
in
unique
ways.
A
So
a
lot
of
people
tend
to
think
that
strategy
is
the
domain
of
product
managers,
but
I
think
that
designers
have
a
a
big
opportunity
to
use
or
or
help
out
with
strategy
with
product
strategy
because
of
our
visual
skills,
in
the
way
that
we
think
about
problems,
and
this
principle
is
sort
of
one
of
the
reasons
why
I
think
that
we
can.
You
can
really
help
out
with
strategy
and
I'll,
give
you
an
example.
So
in
in
my
previous
job,
we
were
working
with
a
pharmaceutical
company
and
they're
saying:
look.
A
We
want
to
help
out
and
create
a
new
sort
of
solution
for
cold
care.
So
when
we
are
going
through
the
process
of
understanding
the
problem,
space
and
stuff,
a
lot
of
the
general
questions
came
up
around.
What's
the
problems
face,
look
like
who
who's
it?
For
what
constraints
have
we
got
around
the
solution
and
and
what
we
did
is
we
were
actually
able
to
take
some
of
the
attributes
that
came
from
these
questions
and
plot
them
against
each
other
in
particular
ways
and
by
plotting
them
against
each
other.
In
particular.
A
One
ways
we
came
up
with
this
diagram
and
this
diagram
on
the
x-axis
is
showing
you
the
various
stages
of
your
cold
journey.
So
what
it's
like
to
to
go
through
a
cold,
so
something
different,
you
sort
of
feel
like
there's
a
little
scratch
in
your
throat
getting
a
cold.
You
know,
oh
yeah,
I'm
definitely
coming
down
with
something.
What
should
I
be
doing
now
having
a
cold
as
yeah?
A
I've
got
the
cold,
I'm
sort
of
on
the
couch,
I'm
in
a
blanket
or
whatever,
and
then
getting
over
a
cold
is
the
final
one
and
then
there's
ways
that
you
can
go
about,
treating
it.
So
there's
solutions
for
it,
so
you
can
mask
stuff
you
can
you
can
change
the
environment
that
you're
in
you
can
flush
stuff?
A
You
can
comfort
and
by
creating
this
diagram,
we're
able
to
see
that
most
of
the
stuff
out
there
currently
in
the
market
focuses
on
this
one
little
bitty
segment
of
types
of
products
that
you
can
work
with
and
there's
all
these
gaps
that
we
could
actually
use
to
address
the
the
the
cold
in
whatever
way
that
we
wanted.
A
In
order
to
find
relationships
and
solutions
to
those
things,
so
we
do
this
a
lot
already,
I'm
not
going
to
go
into
that
section
and
there's
a
number
of
things
that
you
can
do
to
sort
of
get
this
information.
So
a
lot
of
the
dimensions
and
things
that
we
talk
about
basically
come
from
good,
good,
solid
user
research.
A
So
after
you've
done
your
user
research,
you'll
have
a
bunch
of
artifacts
and
things
describing
what
a
particular
user
experience
is
like
and
from
there
you're
able
to
plot
out
just
a
number
of
different
data
points
of
what's
actually
happening.
A
Within
that
experience
and
off
the
back
of
this,
you
can
then
start
to
cluster
these
data
points
together,
in
particular,
themes
to
understand
what
is
actually
going
on,
and
how
can
we
make
more
sense
of
it
and
from
this
you
can
use
these
data
points
and
you
can
use
these
themes
and
you
can
plot
them
together
in
unique
ways.
Not
all
these
diagrams
are
going
to
be
useful,
but
you
can
start
to
find
interesting
relationships
off
the
back
of
it.
A
So
some
of
the
key
dimensions
that
typically
come
out
of
this
user
research
are
things
like
triggers,
so
things
that
happen
that
spark
a
particular
action
pain
points.
The
values
that
you're
bringing
to
a
user
activities
use
cases
modes.
There's
lots
of
different
things
that
you
could
you
can
consider
as
a
dimension.
That's
useful,
so
activities
like
user
journey
mapping
is
sort
of
a
manifestation
of
this
of
this
dimension
and
diagram
principle
and
there's
different,
simple
ways
that
you
can
start
to
to
to
visualize
this
stuff.
A
A
So
only
pay
attention
to
these
right
now,
you're
able
to
find
the
four
key
jobs
to
be
done,
which
were
across
the
top
here
on
the
x-axis,
and
we
were
able
to
sort
of
talk
about
the
different
levels
of
abstraction
or
hierarchy
that
exist
within
value
stream,
which
is
the
category
in
which
I'm
working
on
and
by
plotting
these
two
different
dimensions,
together
of
levels
of
abstraction,
with
the
value
stream
and
jobs
to
be
done.
We're
able
to
sort
of
figure
out.
A
A
I
could
go
into
the
whole
exercise,
but
basically
we
use
this
as
a
nice
canvas
to
frame
the
conversations
that
we
had
within
some
synchronous
meetings
and
also
some
async
critics
collaboration
as
well
and
out
there
out
the
back
of
this
exercise.
This
planning
exercise
I've
created
a
number
of
different
diagrams,
I'm
not
going
to
go
into
each
and
every
one
of
them,
but
we're
able
to
use
this
dimension
and
diagram
principle
to
sort
of
disambiguate.
A
A
number
of
the
things
that
tend
to
crop
up
when,
when
talking
about
value
stream,
so
value
stream
is
obviously
can
mean
a
lot
of
different
things
to
a
lot
of
different
people.
A
And
one
of
the
challenges
that
we
had
before
this
exercise
was
that
we
typically
needed
to
spend
10
to
15
minutes
when
speaking
with
other
stage
groups
with
users
or
customers
around
what
value
stream
is
as
well
as
what.
What
are
the
different
aspects
or
ways
that
you
can
consider
value
stream.
A
So
I
hope
that
wasn't
too
abstract
I
left
out
a
whole
heap
of
stuff
with
regards
to
the
methodology
and
the
process
for
how
I
actually
came
up
with
the
stuff
here.
So
if
people
are
interested
in
that,
please
ask
away
with
regards
to
any
anything
like
that
or
I
could.
I
could
follow
up
with
a
blog,
a
blog
post
or
or
whatever
to
to
clear
up
some
some.
B
A
So
this
this
was
I'm
not
going
to
go
into
into
salesforce's
design.
Thinking
methodology
too
much,
but
okay,
the
dimension
and
diagram
is
like
a
principle.
So
we
we,
we
used
to
think
about
principles
as
being
something
underneath,
like
the
process
level,
basically
a
particular
type
of
mindset
that
you
employ
when
doing
creative
problem
solving.
A
So
what
a
lot
of
other
design
thinking
methodologies
did
is
tended
to
display
or
represent
design
thinking
as
a
linear
process
which
isn't
typically
how
the
the
creative
problem
solving
approach
works.
A
So
the
diverge
like
diverging
and
converging
the
double
diamond
stuff
is
a
good
representation
for
like
divergent
thinking,
convergent
thinking
and
also
showing
and
separating
out
the
problem
safe
space
and
solution
space,
but
this
is
like
basically
think
of
it
as
a
hat
that
you
use
in
the
creative
problems
solving
space
to
like
figure
out
or
work
out,
some
thing
that
may
crop
up
in
the
well.
It's
I
don't
know
what
I'm
trying
to
say
here.
A
D
B
A
Very
good
question,
so
up
into
this
point,
we've
basically
had
our
feature
for
value
stream,
focused
predominantly
on
mapping
out
what
your
value
stream
is
so
saying.
These
are
the
different
stages
that
fit
within
my
value
stream,
and
this
is
how
long
each
one
of
the
stages
is
taking.
That
has
some
level
of
value,
but
there's
then
some
things
that
you
can
do
once
you've
mapped
out
the
stages
that
give
people
a
little
bit
more
insight
around
their
value
stream.
A
A
There's
another
way
to
think
about
value
stream
in
terms
of
optimizing,
your
workflows
and
your
processes
of
reflecting
on
how
your
value
stream
is
working
currently
and
seeing
how
you
can
make
any
adjustments
to
that
and
then
finally,
think
about
value
stream
in
terms
of
how
much
value
is
delivering
so
actually
connecting
it
to
some
of
the
things
like
understanding
how
much
it
costs
to
implement
a
certain
feature
and
all
that
sort
of
stuff.
A
So,
by
identifying
the
different
jobs
to
be
done
after
this
exercise
and
plotting
them
at
the
different
levels
of
value
stream
abstraction,
we
are
able
to
say
that
we
want
to
focus
specifically
right
now
on
the
optimize
side
of
value
stream.
So
that's
reflecting
on
your
workflows
and
reflecting
on
how
you
can
actually
optimize
them
to
be
a
little
bit
more
effective
and
and
produce
the
time
within
your
value
stream,
and
leave
the
delivery
side
and
leave
the
evaluation
side
for
a
little
bit
later.
A
So
we
were
able
to
prioritize
what
our
focus
was
and
and
what
we
wanted
to
focus
on
in
the
near
term.
E
Yeah
and
then
I'll
write
it
down.
Do
you
see
any
opportunities
for
us
to
use
any
kind
of
like
journey
mapping
or
diagrams,
where
we're
not.
E
Like
to
you
know,
help
with
you
know,
pajamas
life
cycle
component
life
cycle,
or
is
there
anything
that
I'm
wondering
if
we
can
help
build
empathy,
even
in
these
showcases
by
you
know,
starting
with
a
journey
map,
because
we
we
all
touch
on
different
personas
or
what
yeah?
What
opportunities
do
you
see,
because
I
think
this
is
this
is
really
interesting.
I'm
just
trying
to
think
about
in
what
ways
we
can
apply.
It.
A
Very
good
question,
something
something
that
strikes
dear
to
my
heart
as
well,
so
yeah
personas
journey
maps
they're
all
really
useful
for
providing
additional
context
around
how
gitlab
works
and
how
it
should
work
and
all
that
sort
of
stuff.
I
think
one
of
the
key
opportunities
that
we
have
within
gitlab
is
actually
the
use
of
objects
and
mapping
out
our
conceptual
model.
A
So
if
you
think
about
the
way
that
we
structure
ourselves
at
gitlab,
currently
we
are
structured
based
on
stage
groups
and
each
stage
group
has
a
particular
category,
and
categories
are
a
way
for
us
to
represent
the
types
of
features
that
we're
actually
presenting
to
the
market.
So
it's
a
way
for
analysts
and
and
people
to
sort
of
understand
what
is
the
stuff
that
we're
selling
to
you
and
how?
How
are
we
perceived
within
the
market
so
something
that
really
tends
to
align
more
with,
like
our
buyer
personas?
A
So,
if
you
think
about
how
a
user
actually
perceives
git
lab
as
a
as
a
product
like
an
average
developer,
when
they're
actually
using
gitlab,
they
don't
tend
to
think
about
gitlab
in
terms
of
categories.
They
don't
say:
oh
I'm,
currently
working
on
some
source
code
management,
I'm
currently
working
on
on
issue
management
or
value
stream.
They
typically
think
I'm
currently
in
an
mr
I've
got
to
commit.
I'm
going
to
push
that
commit
to
an
mr
and
I'm
going
to
then
say
in
this
issue
that
I've
finished
this,
mr
or
whatever
is
going
on.
A
So
when
we're
able
to
create
and
map
out
how
the
object
interactions
should
work,
there's
this
level
of
experience
that
we'll
be
able
to
create
underneath
this
category
segmentation
that
we
already
have
that
will
fill
in
some
of
the
the
gaps
of
where
our
experience
is.
So,
if
you
think
about
our
teams
tend
to
optimize
towards
categories
and
then
hopefully,
pajamas
and
some
other
design
system
stuff
will
able
to
optimize
towards
objects
and
some
of
those
sort
of
broader
experiential
concepts
that
we
hope
to
get
from
from
gitlab.
E
Yeah,
I
think
I'm
going
to
put
some
time
on
the
calendar
with
you
if
it's
all
right,
because
I've
started
a
couple
maps
and
then
I
kind
of
get
lost.
I
feel
like
I
start
to
try
to
show
too
much
in
one.
So
I
I'm
curious
and
learning
more
about.
You
know
the
scope
of
one
diagram,
because
sometimes
I'm
trying
to
show
you
know
different
ui,
like
oh
you're,
taken
from
this
page
to
this
page.
E
In
addition
to
kind
of
the
emotion
that
the
customers
or
the
user
is
going
through,
in
addition
to
just
a
a
layer
of
things
and
so,
rather
than
like
an
x
y,
it
turns
into
an
x
y
z,
q.
I
feel
like
there's
so
many
axes
going
on
at
once,
so
maybe
we
can
meet
and
even
record
that
session
for
anybody
else
who
may
struggle
with
scope
in
these
days.
A
Sure
yeah,
I'm
always
happy
to
talk
about
this
stuff.
I
really
enjoy
it
and
like
a
really
quick
tip
is
with
these
maps
is,
like
start
start
at
the
end,
think
about
what
who
who's
it
for
and
what's
it
for
and
that
helps
to
prioritize
and
strip
down
the
dimensions
that
you
actually
include
in
the
maps.
I
think
designers
have
like
this
tendency
to
want
to
like
create
the
one
ultimate
map
to
solve
it
all,
but
really
a
series
and
a
library
of
smaller
maps
help
to
serve
the
purpose.
E
B
Relates
a
lot
to
what
we're
working
on
foundations
right
now
improving
the
component
life
cycle-
and
I
started
this
new
diagram
for
that.
So
it's
funny
that
you
mentioned
that
back
up,
but
I'm
trying
to
make
it
like
very
straightforward
and
easy
to
follow.
B
There's
a
merge
request
that
I
linked
in
the
agenda
so
nick
that
guy
would
be
really
awesome
if
he
took
a
look
and
gave
some
feedback
because
we
want
to
make
it
simple
but
same
thing
as
becca
said,
like
there's
just
kind
of
multiple
dimensions,
and
I
think
it
can
be
probably
scaled
down
and
and
easier
to
go
through,
but
haven't
figured
out
how
to
do
that.
Yet
so
would
be
interested
in
your
feedback
for
sure.
D
So
I
think
we
have
so
many
opportunities
any
time
we
want
to
like
sell
an
idea,
especially
to
people
outside
ux
or
communicate
really
quickly.
What
an
experience
is
like
these
are
super
powerful
and
then
and
then
another
thing
journey
maps
do.
Is
they
help
us
understand
different
channels?
So
when
we
think
about
an
experiment,
an
experience
like
a
workflow
that
is
in
our
ui
just
in
our
ui,
but
that
person
might
be
hopping
to
a
terminal.
D
They
might
be
hopping
over
to
some
docs
and
git
lab,
or
some
docs
stack
overflow
external
to
gitlab.
They
might
be
using
all
these
different
channels,
slash
tools
at
once,
and
a
journey
map
can
kind
of
like
condense,
that
so
that
we
can
understand
how
people
go
from
one
thing
to
the
next
and
then
we
can
learn
from
that
and
identify
like
opportunities
to
leverage
those
things
to
make
the
experiences
better.
So
I
just
I
love
all
these
visual
things.