►
From YouTube: You're Doing UX Unconsciously, Now Let's Make it Conscious and Intentional - Maurice Hayward
Description
You're Doing UX Unconsciously, Now Let's Make it Conscious and Intentional - Maurice Hayward, Ferguson Enterprise
UX (User Experience) is a vast field that touches all aspects of product development from research, design, and implementation. Understanding UX and why it’s important can be very daunting. However, it may be the case that you are already doing UX without realizing it!
In this presentation, you’ll find out about Maurice's experiences learning UX, see how he increased UX awareness in his team and how his team went from doing unconscious UX to doing it intentionally and with purpose!
You will walk away with a clear understanding on how to apply UX principles to your projects. Along with that, you will have new methods for introducing UX to your team.
A
Okay,
y'all
we're
going
to
get
this
party
started
so
hi.
My
name
is
Maurice
Hayward
I'm,
a
UI
developer
at
Ferguson
enterprise
in
the
United
States
I
think
here
in
Canada,
is
called
Wasley
Canada
and
I
work
on
internal
applications,
internal
web
applications,
and
so
I
would
like
to
talk
to
you
all
about
how
I
learned
about
user
experience
and
what
happened
when
I
started
talking
to
my
teammates
about
it.
So,
while
I
was
creating
this
slide,
deck
I
was
watching
Beyonce
homecoming.
A
So
that's
gonna
jump
out
on
y'all,
so
so
user
experiences
about
the
experience
a
product
creates
for
the
people
who
use
it.
So,
let's
say,
for
example,
a
product
is
slow,
cumbersome
or
unreliable.
Then
most
likely
it
will
create
a
bad
experience.
On
the
other
hand,
if
a
product
is
reliable,
if
it's
usable
and
very
intuitive,
it
can
most
likely
create
a
good
experience
for
the
people
who
use
it
so
before
revolution
coughs.
So
this
is
a
conference.
Last
year,
2018
I
had
no
idea
what
that
term
meant
user
experience.
A
So
I
would
like
to
first
talk
about
my
experience
at
that
conference
and
before
I.
Do
that
I'm
just
gonna
just
talk
mentioning
about
just
talk
a
little
bit
about
rep
comp,
so
it
is
a
language
agnostic
conference
in
Virginia,
Beach
Virginia
in
the
United
States,
and
it
was
my
very
first
conference
I
went
to
in
2017
and
I
try
to
go
to
it
every
year,
I
call
it
my
home
conference,
so
I
really
love
it.
So,
let's
talk
about
that
conference.
A
So
the
very
first
talk
I
went
to
was
by
Chris
Tamar
and
it
was
called
focusing
on
focus-
and
this
quote
right
here
that
he
mentioned
during
the
talk
floored
me
y'all.
So
it
says:
20%
of
people
have
a
disability,
so
accessibility
is
a
must
even
for
internal
applications.
So
after
this
was
said,
I
actually
felt
personally
attacked
a
reason
being
is
I
worked
on
again
internal
web
applications
and
I
believe
at
one
point,
I
reasoned
within
myself.
A
A
So
a
fan
couldn't
use
Beyonce's
comm
using
their
screen
reader
and
this
led
to
a
lawsuit
and
so
I'm
going
to
spill
some
tea
and
read
an
excerpt
here.
So
it
says
defendants
are
denying
blind
and
visually
impaired
persons
throughout
the
United
States,
with
equal
access
to
the
goods
and
services
Parkwood
provide
to
their
non-disabled
customers
through
wwe.com.
A
A
The
next
talk,
I
really
appreciate
it
was
by
John
and
it
was
called
UX
for
developers
and
I
really
appreciated
this
boat.
It
says
you
UX
user
experience,
the
debt
is
technical
debt,
and
this
is
very
true.
So
let's
say
we
don't
make
user
experience
a
priority
on
our
team.
We
can
slowly
be
introducing
small
usability
user
experience
issues
and
all
these
small
issues
together
can
make
our
whole
product
really
unintuitive
are
hard
to
use.
It
can
create
a
bad
experience.
A
On
the
other
hand,
if
we
decide
to
tackle
some
low-hanging
fruit,
some
really
easy
user
usability
issues
and
we
try
to
go
ahead
and
fix
those
really
easy
ones.
They
can
greatly
improve
the
usability
of
our
product
and
another
quote
from
this
talk.
Ux
is
everyone's
problem,
so
everyone
on
the
team,
whether
you're
a
be
a
Quality
Assurance
analyst,
a
developer
which
we
are
are
here
and
or
a
designer.
You
have
a
responsibility
to
think
about
the
experience
your
product
creates
and
the
last
talk
I
really
appreciate
it
from
that
conference
was
by
Aisha.
A
It
was
on
web
accessibility,
and
this
talk
was
full
of
gems,
so
she
went
over
some
practical
guidelines
and
checklists
to
follow
in
order
to
improve
the
accessibility
health
of
your
website.
But
what
I
also
really
appreciate
it
was.
This
quote:
accessibility
make
life
better
for
everyone,
so
this
is
very
true.
So,
let's
kind
of
illustrate
this,
so
they
all
remember
this
dress
yike.
A
So
let's
say
in
that
same
article
and
we
just
simply
add
a
caption
to
that
image.
The
caption
reads:
the
actual
colors
of
this
dress
are
blue
and
black,
but
many
people
see
it
as
white
in
gold
just
by
simply
adding
a
caption
everyone,
including
those
who
use
screen
readers
and
those
who
don't
will
be
able
to
understand
the
author's
intent
for
this
image,
which
was
hard
before
because
of
the
optical
illusion.
So
this
is
just
like
one
of
the
many
examples
of
how
just
thinking
about
accessibility
helps
everyone.
A
A
So
before
I
do
that
I'm
just
gonna
talk
about
the
makeup
of
my
team
at
that
time.
So
again
we
work
on
internal
web
applications
for
organization.
We
had
a
BA.
His
job
is
to
take
business
goals
and
turn
them
into
requirements.
He
also
created
our
project
mock-ups
and
he
did
him
in
Microsoft
Paint
and
they
looked
awesome
so
yeah.
A
We
also
had
a
Quality
Assurance
analyst
QA,
so
she
takes
those
requirements
and
then
create
some
test
cases,
and
then
she
ran
through
them
using
a
combination
of
automated
and
manual
testing,
and
at
that
time
we
had
three
developers,
including
myself.
We
take
those
requirements
and
we
implement
them
using
web
technology,
so
HTML,
CS,
c
c
c,
SS
and
javascript
angler,
GS
and
so
on.
So
these
are
my
teammates.
So
after
the
conference
I
told
my
team
pretty
much
everything
I
learned
about
UX
and
accessibility,
but
also
mention
this-
that
I
think
use
a
user.
A
Ux
and
accessibility
should
be
a
priority
on
our
team
moving
forward
and
we
should
allow
time
for
it.
So
surprisingly,
they
were
actually
really
excited
and
they
agreed
and
I
got
to
hear
about.
So
many
different
experiences
that
they
had,
for
example,
one
of
the
other
developers
he
used
to
be
he
used
to
work
at
a
bank
and
he
was
a
developer
for
them.
He
had
to
make
sure
that
the
website
followed
the
government
web
accessibility
guidelines
so
just
write
on
my
team.
They
were
already
a
wealth
of
knowledge
on
this
subject.
A
So
the
next
thing
I
needed
to
do
was
talk
to
my
manager,
so
again
shared
my
thoughts.
What
I
learned
at
the
conference
and
I
said
sorry,
yeah
and
I
mentioned
how
I
think
accessibility
in
UX
should
be
a
priority
and
she
agreed
so
I
was
like
a
cool
but
notice
what
she
mentioned.
Yet
next,
it's
just
like
hey
Maurice.
You
know
you
already
been
doing
some
user
experience
work
right.
You
already
been
doing
that
and
I
was
like
wait.
What
what
do
you
mean
by
that?
A
I
was
already
doing
some
new
UX
and
she
mentioned
yeah
when
you
were
working
on
making
sure
that
the
application
was
responsive.
You
were
thinking
about
the
users
you
were
doing.
Ux
and
I
was
mind
blown,
so
that
was
very
true.
So
when
I
first
started
working
on
the
project,
I
noticed
that
the
application
worked
really
well
on
desktop,
but
when
I
switched
to
my
laptop
everything,
didn't
look
as
good.
A
So
later,
another
front-end,
developer
and
I
took
the
initiative
and
convinced
the
business
owners
to
allow
us
more
time
to
refactor
the
UI
into
components
and
update
the
styles
to
allow
for
a
responsive
design.
So
by
doing
this
we
were
letting
the
users
be
able
to
use
the
application
in
all
screen
sizes,
desktop
laptop
tablet
and
even
on
mobile
screen
sizes.
Another
use
case
was
just
be
able
to
take
the
application
and
put
it
in
half
screen
mode,
so
we
were
improving
the
user
experience
of
the
application.
A
A
So
now
that
our
team
was
more
conscious
of
why
user
usability
and
accessibility
was
important,
we
needed
to
go
ahead
and
just
be
more
intentional
about
it.
Moving
forward,
so
I
try
to
take
the
lead
in
that
I
write.
Some
resources
on
UX
and
design
and
I
will
talk
a
little
later
about
some
of
those
resources
that
I
really
appreciate
it.
A
A
I
was
like
I,
didn't
know
that
so
I
was
able
to
schedule
a
meeting
with
them
and
invite
my
whole
team
and
I
hope
bunch
of
people
from
their
team
and
they
just
went
through
a
whole
application
and
just
gave
us
a
whole
bunch
of
tips
and
tricks
and
actionable
advice,
and
everyone
took
something
from
that
on
on
my
team.
So
I'm
gonna
go
through
what
we
learned.
So
first,
let's
talk
about
the
BA.
A
So
again,
the
vise
that
we
got
about
usability
and
UX
was
very
helpful
for
him
because
again,
if
you,
if
y'all
remember,
he
creates
our
mock-ups
so
now
he's
more
conscious
of
making
sure
interactions
on
their
site
are
consistent.
So
what's
the
interaction,
this
is
probably
bad
definition,
but
anytime,
a
user
interacts
with
your
website.
So
some
common
interactions
clicking
things
clicking
buttons
type
in
any
input
form.
Those
are
some
common
interactions
we
have
on
a
website.
So
let's
go
over
an
example
of
this.
A
So
let's
say,
for
example,
you
have
a
e-commerce
site
and
you
have
the
user
submit
their
product
to
the
cart,
and
so
they
look
at
the
product.
They
click
the
submit
button
and
adds
it
to
the
cart.
Let's
say
on
one
part
of
the
website:
it
is
a
blue
button
and
on
the
other
side,
other
part
of
the
website
is
a
red
button.
They
do
the
same
thing:
they
have
the
same
functionality
and
they
use
for
the
same
purpose,
but
they
have
two
different
colors
for
some
reason.
Well,
in
this
case
the
style
isn't
consistent.
A
A
That's
scary,
y'all,
we
didn't
know
no
better,
so
or
dot
Apache
Solr
dot,
common
solar
exception,
:
error
during
request
authentication.
So
like
again,
if
you're
a
user,
this
is
not
helpful.
It's
really
scary,
so
we
were
able
to
change
it
from
something
like
this
to
this
unable
to
retrieve
product
info
:,
Solar,
server
error.
So
again,
the
user
is
able
to
see
ok,
we're
not
able
to
get
the
product
information
and
there's
some
type
of
error
with
the
server
and
as
a
developer.
A
If
we
need
more
information,
while
we
log
everything-
and
we
can
also
have
use
the
developer
console
in
our
browser
to
dig
deeper
if
we
need
to-
and
this
was
just
actually
the
first
iteration
of
it-
we
later
found
out
that
we
can
improve
on
it
even
more
so
these
were
pop-ups
later
on.
We
decided
to
make
your
main
page
messages
and
be
more
useful
for
the
for
the
user.
So,
like.
Oh
you
see
this
error.
A
A
A
So
one
thing
he
worked
on
if
the
column
is
not
important
in
this
scenario
or
if
the
element
is
not
important
in
this
scenario,
don't
show
it,
and
this
is
a
very
key
when
you
look
at
working
with
different
screen
sizes
and
that's
a
lot
of
people.
That's
another
reason
why
a
lot
of
people
like
the
mobile
first
approach,
because
it
forces
you
to
think
about
what's
really
important.
A
Another
thing
he
worked
on
was
making
sure
that
everything
was
concise.
So,
for
example,
we
had
a
shopping
cart.
So
this
is
very
easy
to
understand.
If
you
see
it
at
the
top
of
your
screen,
it
has
a
shopping
cart.
It
has
the
word,
cart
and
it
says
two
items,
so
your
shopping
cart
have
two
items
in
it.
So
this
is
fine
when
you
have
bigger
screen
sizes,
but
if
you're
moving
smaller
to
mobile
device.
A
This
takes
up
a
lot
of
real
estate
that
we
can
use
for
other
things,
so
he
was
able
to
change
this
to
that.
So
it's
just
a
shopping,
cart,
icon
with
a
badge
above
it
that
has
the
number
of
items
in
the
cart
and
so
at
first,
what
we
did
was
in
bigger
screen
sizes.
We
showed
this
version
and
in
smaller
screen
sizes
we
showed
this.
But
later
we
were
like
you
know
it
does
the
same
thing.
Why
maintain
both
of
them?
We're
just
going
to
show
this
icon
for
all
screen
sizes?
A
And
let's
talk
about
me,
what
did
I
do
so?
The
first
thing
I
worked
on
was
making
sure
we
only
show
relevant
information.
Well,
we
show
relevant
information
as
soon
as
possible.
So
one
thing
I
noticed
with
the
application
is
that
we
waited
for
all
the
data
that
we
got
from
different
api's
to
load
successfully
did
in
order
to
render
the
page
correctly
and
that
made
the
application
be
perceived
as
slower
than
it
really
was.
So
let
me
just
visualize
how
it
kind
of
looked
so
we
got.
We
called
the
product
API.
A
If
that
data
load
successfully,
then
we
called
the
inventory
API.
If
that
law
was
successfully,
then
we
call
the
pricing
API
and
if
that
render
successfully
I
mean,
if
that
is
loaded
successfully,
then
we
actually
render
the
page
correctly
so
I'm
just
going
to
show
y'all
a
little
code.
This
is
not
exactly
how
it
was,
but
it
just
it'll
give
you
out
of
idea
so
again
recall
the
product
API.
That
returns
a
promise.
So
then
we
can
chain
it
with
the
din
function.
We
call
the
inventory
API
that
returns
a
promise.
A
We
can
chain
it
with
the
din
function
and
then
we
call
the
price
in
API,
but
we
can
also
see
another
problem
with
this.
So
let's
say,
for
example,
the
inventory
API
just
decide
not
to
work
today
the
server
is
down
well.
If
the
server
is
down,
then
we're
gonna
get
an
error
in
the
inventory.
Api
promise
and
that's
gonna
go
all
up.
A
Next,
there's
gonna
go
to
the
kept
statement
and
we're
not
going
to
call
the
pricing
API,
so
the
page
is
not
going
to
render
correctly
and
we're
not
gonna
get
any
pricing
information
on
the
page,
so
this
is
pretty
unnecessary,
so
I
was
able
to
switch
it
from
this
kind
of
configuration
to
this
so
what's
happening
here.
So
all
the
elements
on
the
page
that
don't
rely
on
the
product
information,
let's
go
ahead.
A
If
it's
important,
let's
go
ahead
and
show
them
as
soon
as
possible,
then
once
that's
shown
we're
gonna
go
ahead
and
call
the
product
API,
and
since
the
pricing
API
in
the
inventory,
API
relies
on
data
from
the
product
API
we're
just
going
to
call
them
when
the
product
API
is
successful,
but
instead
of
chaining
them
we're
just
gonna,
go
ahead,
call
them
independently.
So
let's
see
how
that
kind
of
looks
code
wise,
so
again,
not
exact
code
but
just
a
representation.
So
we
called
the
product
API.
A
If
that's
successful,
then
we
call
the
inventory
API
in
a
price
and
API
separately,
and
it
solves
our
problem
with
the
arrow
problem
that
we
had
before.
So,
let's
say,
for
example,
the
inventory
API
fails.
Well,
we
have
a
catch
statement
associated
with
it
already.
So
it's
not
going
to
stop
the
pricing
API
from
being
called,
and
you
can
also
see
that
I
set.
A
The
promise
is
equal
to
two
variables
with
that
I
can
check
to
see
if
these
promises
are
still
pending,
if
they
are
where
that
data
will
be,
I
can
just
have
a
loading
icon'
they're.
Just
again
just
tell
the
user:
it's
still
loading,
so
I
really
like
this
project.
I
had
to
get
up
close
and
personal
with
the
event
loop
in
JavaScript
and
learn
about
promises.
I
didn't
know!
You
can
do
that
before
so
next
I'm
going
to
talk
about
the
Quality
Assurance
analyst.
What
did
she
do
so
one
thing
she
did.
A
It
was
login
Amy,
UX
issues
we
saw
inside
of
the
QA
records,
so
we
can
keep
track
of
them.
Another
thing
she
did
was
actually
test
the
usability
of
our
product,
so
she
noticed
that,
based
on
our
users,
we
needed
to
be
able
to
tab
through
our
whole
application
so
because
it
was
essential.
She
created
automated
tests,
autom
automated
testing
for
it.
So
it's
now
part
of
the
regression
testing.
A
A
So
I
appreciate
this
book.
Don't
make
me
think
by
Steve
Krug.
It
really
gets
to
the
meat
of
accessibility
and
usability.
It
has
sections
that
talk
about
buttons
like,
for
example,
how
to
style
a
button
to
make
it
look
clickable
and
what
text
you
should
put
in
your
button
to
make
it
look
up
to
make
the
action
clear.
So
that's
interesting
you!
This
is
a
good
resource,
so
also
the
Mozilla
developer,
Network
web
Docs.
It's
free
and
I-
think
it's
a
really
good
resource.
A
If
you're
trying
to
learn
or
review
web
technologies,
JavaScript
HTML
CSS
and
it
teaches
those
technologies
with
accessibility
in
mind.
So,
for
example,
on
the
page
that
talks
about
the
image
tag,
the
HTML
image
tag.
It
also
talks
about
why
using
an
alt
tag
is
important
and
then
it
talks
about
how
you
can
write
meaningful,
alt
tags
and
then
goes
over
a
scenario
where
you
will
want
to
have
an
alt
tag
with
an
empty
screen.