►
From YouTube: UX Showcase Customer Portal Pajamas Migration
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
So
just
to
give
you
an
idea,
I'm
going
to
be
talking
about
the
problem,
what
we
did
and
in
the
length
very
high-level
and
thanks
to
figma,
incredibly
bold
and
so
first,
the
the
problem
so
before
I
talk
about
the
problem
is
specifically
it's
good
to
look
at
the
types
of
people
that
are
actually
using
the
customers
portal.
I've
just
listed
out
some
personas
there
for
you,
the
dev
manager
team
lead.
A
They
were
director
and
architect,
I'm,
their
VP
and
chief
information
security
officer,
along
with
a
VP
of
infrastructure,
which
is
still
being
determined
and
as
people
managers,
high
level
and
majority
of
the
time,
what
they're
purchasing
be
hot
or
calm
or
self-managed.
They
have
time
limitations
and
it's
really
important
that
they're
able
to
and
conduct
transactional
things
and
as
quickly
as
possible
and
it's
an
efficiently
efficient
as
possible,
and
that
was
one
of
the
problems
that
we
saw
with
the
the
current
customers
portal.
A
So
the
challenges
with
the
previous
design
and
the
reason
that
sparked
this
when
we
were
actually
going
through
user
interviews
on
another
issue
and
a
lot
other
questions
pointed
back
to
the
customers
portal
and
what
we
found
was
through
incorrect
product
purchases.
So
people
were
buying
two
of
the
same
products,
because
the
UI
interactions
went
as
robust
as
they
needed
to
be
multiple
purchases
for
multiple
purchase,
step
story
for
something
that
could
be
done
on
a
single
page.
A
We
were
kind
of
leading
people
through
two
to
three
steps
and
unlike
a
visual
consistency,
that
was
one
of
the
big
ones.
Actually,
it
was
really
important
to
make
sure
that,
when
someone
rounds
on
the
customers
portal
date,
they
feel
familiar,
it
feels
intuitive
and
it
aligns
with
the
patterns
that
the
we
have
across
our
complete
and
product
suite,
and
that
kind
of
led
me
to
this
crossroads.
That
I
believe
the
customers
portal
was
in
and
it
could
go
left
and
be
more
aligned
with
the
about
marketing
website.
A
It
could
be
its
own
standalone
product
with
its
own
design,
history
or
it
could
align
with
patents
and
the
foundation
would
be
pajamas
components
being
implemented
inside
of
the
the
customers
portal,
and
that
was
the
route
that
we
chose
and
thanks
to
you,
help
from
Tory
and
a
number
of
different
engineers
and
designers,
and
we
landed
on
through
iterative,
iterates
iterating,
and
we
landed
on
a
succinct
approach
to
tackle
this.
This
problem,
so
what
we
did.
A
Firstly,
it
was
a
heuristic
event,
evaluation
and
that's
just
a
very,
very
technical
way
of
saying
we
identified
usability
problems
in
the
user
interface
and
then
went
about
seeking
how
we
might
solve
them.
So
an
example
of
this.
This
is
the
previous
design
of
the
customers
portal
and
specifically
the
managed
purchases
page
and
upon
immediate
kind
of
bisect.
On
this
page,
you
can
kind
of
see
where
there
are
some
low-hanging
fruit
that
we
can
improve
here
and
that's
kind
of
the
basis
of
the
heuristic
evaluation.
A
It
was
to
look
at
the
navigation,
so
this
was
kind
of
an
in-between.
I
spoke
about
a
crossroads.
Previously
it
was
an
in-between
between
the
marketing
website
and
pajamas
and
didn't
really
live
anywhere
and
so
I
thought
that
could
definitely
be
worked
on
to
introducing
patterns
that
were
familiar
across
the
product
information
architecture,
so
why
CTAs
are,
above
others,
the
positioning
of
cards
and
the
actual
presentation
of
the
licensing
component
on
the
page,
really
kind
of
bisecting.
A
What
bits
of
information
should
be,
above
others,
and
what
should
be
given
more
prominence,
an
example
of
that
for
this
section
going
into
the
component
and
that
to
me
so
the
actual
anatomy
of
the
license
description
box
itself.
Why
is
the
subscription
ID?
The
title
are
hidding
and
shouldn't
it,
be
the
actual
product
itself
and
potentially
leaving
ideas
and
metadata,
underneath,
if
so,
it's
easier
to
identify
the
products
that
you
have
and
they
aligned
with
calm
or
the
aligned
with
the
self-managed.
A
And
to
the
front-end
team,
we
also
did
a
component
review
so
and
along
with
the
heuristic
evaluation,
that
was
a
page-by-page
conducting
of
research.
The
compounding
review
was
also
a
page-by-page
conducting
research
and
we
really
wanted
to
see
where
there
were
some
quick
links.
So
we
can
draw
some
alignment
with
the
pajamas
and
get
wi
so
for
phones
and
for
buttons
it
was
a
pretty
simple
one-to-one
ratio.
A
It
became
a
little
bit
more
tricky
when
you
start
tackling
and
digging
deep
into
licensed
component
sections
and
all
of
the
different
edge
cases,
but
this
was
a
worthwhile
experiment
to
undertake
and
it
really
helped
us
to
pinpoint
where
we
could
break
this
process
down
into
phases
and
which
ones
a
phased
approach.
This
goes
all
the
way
back
to
even
before.
At
all
point
six.
To
be
honest
with
you,
the
first
phase
was
typography
using
OS
font
stacks.
A
So
when
lining
that,
with
what
we
currently
doing,
get
WI
the
colors
and
also
spacing
so
the
colors
being
what
we
have
in
a
global
area
and
also
spacing
being
the
eighth
and
display
pixels
that
we're
currently
using
phase
two
was
going
to
be
the
navigation,
templating
structures
and
integration
of
get
lab.
B1
and
the
full
integration
of
getting
up
your
I
should
say.
And
then
lastly,
it
would
be
the
beautification
stage
and
just
to
give
you
an
idea
where,
at
the
end
of
phase
two
going
into
Phase
three.
A
Just
if
she
wanted
to
know
where
we
are
in
the
current
implementation.
So
it
was
iterative
design
process
and,
for
the
sake
of
time,
I'm
just
giving
you
an
example
of
one
page.
This
is
the
my
account
page
and,
as
you
can
see,
they're
splitting
up
information
across
the
page
and
different
compartmentalize
boxes,
and
we
really
wanted
to
break
that
out
into
a
pattern
that
we
currently
see
being
used
on
github.com
and
so
at
the
start
of
the
process.
And
this
is
the
first
iterative
design.
A
You
can
see
that
there
are
some
thinking
around
how
we
might
tackle
the
navigation
and
draw
it
more
in
line
with
the
product
also
boring
patterns,
what
we
have
currently
in
the
product.
So,
specifically
speaking
of
the
settings
general
page,
where
we
list
out
these
different
and
different
lists
performs,
and
so
this
was
just
an
experimentation
of
what
we
could
do
and
at
the
end
of
each
of
these
design
cycles
and
it
was
tested
with
some
users
and
then
also
the
feedback,
Totti
bound
and
reworked
into
later
iterations
and
I'm
writing
the
product.
A
I
thought
was
important
that
we
had
a
title
for
each
of
one
of
the
pages
that
we're
going
to
be
implementing
mainly
because
on
the
product,
it's
the
navigation
and
the
breadcrumbs
that
are
used
to
signify
where
you
are
on
any
given
page,
but
for
something
that
is
kind
of
rudimentary
and
straightforward.
There's
the
port
or
I
thought
was
important
to
give
it
a
h1
to
make
sure
people
are
grounded,
know
where
they
are,
and
then
second
phase
artists
and
more
texting
and
looking
at
currently
what
we
currently
have
on
offer
on
the
product.
A
In
terms
of
the
different
preferences
for
the
navigation
system,
we
landed
them
on
this
specific
design
and
then
also
integrated
the
expand
and
collapse
modules
to
show
different
parts
of
your
journey
along
the
account
details
page,
and
so
it
ties
in
in
a
more
fulfilled
fulfilling
way.
What
you're
saving
instead
of
saving
a
big,
big,
long
form,
you're
saving,
individual
sections
and
the
Save
Changes
attaches
itself
to
those
individual
section
so
very
quickly.
A
Some
further
examples
and
I
can't
go
into
extreme
detail
on
how
these
works,
but
this
is
the
previous
design,
as
I
showed
you
before,
and
this
is
some
of
the
reworkings
and
just
some
high-level
thinking
here
again.
The
page
titles,
the
the
I,
the
the
lifting
up
of
the
product
name
and
then
placing
the
metadata
underneath
the
product
name
and
data
that
wasn't
previously
available,
so
the
C
count
and
the
and
when
it
expired
in
in
easier
terms
and
and
a
better
way
of
segmenting
your
purchase
for
a
subscription
or
a
license
with
add-on
products.
A
And
for
that
we're
just
using
the
club's
approach
from
my
pajama
system.
And
lastly,
I
spoke
about
double
steps.
To
do
something
that
can
be
done
in
one
phase.
This
is
a
example
of
adding
more
seats
to
your
to
your
self-managed
license.
You
have
to
go
a
few
steps,
so,
firstly,
you
decide
how
many
seats
you
want
to
add
them
in
there's
another
section
where
you
have
to
decipher
what
kind
of
translates
into
the
discounts
that
you're
all
rebates
that
you're
going
to
do
so.
A
This
is
then
led
to
thinking
along
the
lines
of
one
page,
with
a
select,
more
seat
section
purchase
summary
where
you
can
see
an
overview
of
what
you're
going
to
be
playing,
and
then
the
billing
information
and
the
billing
information
with
gives
you
the
affordance
to
change
your
payment
card
details
and
which
you
won't
originally
allowed
to
do.
You
have
to
stick
with
your
default
method,
so
just
some
thinking
along
those
lines.
A
The
website
reduce
steps
in
the
EDC
model,
an
EDC
meaning
entry
decision,
confirmation
really
kind
of
key
significant
role
in
making
sure
that
the
funnel
is
as
succinct
as
possible
and
familiar
product
patterns.
So
when
people
land
on
the
customers
portal,
they
don't
feel
like
they're
in
the
foreign
land.
They
do
feel
that
they're
at
home,
but
in
our
our
suite
of
design,
Jonnie
and
internal
observations,
better
understanding
of
what
the
pedometers
components
from
team
members-
and
this
has
helped
us
to
facilitate
some
of
the
some
design-
is
a
foundation
for
internal
tuning.
A
This
allows
us
to
be
able
to
build
out,
maybe
the
licensor
or
the
version,
with
the
same
structure
as
we
have
done
with
the
customers
portal
easier
to
build
experiments
or
for
the
growth
team
as
a
whole.
So
meta
has
been
helping
me
translate
all
of
the
sketch
files
into
thigma
for
future
future
proofing,
and
this
helps
designers
to
take
over
and
to
build
layered
experiences
on
top.
This
helps
them
also
the
performing
q2
plans
and
to
improve
stability
and
reliability
of
purchasing
systems.
A
This
is
another
layer
on
top
of
that,
and
I
think
helps
facilitate
that
plan
and
frustr
in
deeper
collaboration.
So
just
an
example
on
that
I
managed
to
stumble
across
Germany's
navigation
designs
and
for
docs
inside
the
Sigma
and
I
duplicated
and
then
shared
some
kind
of
shared
learning
with
him
around,
maybe
aligning
navigation
systems,
so
the
subtext
and
navigations
so
that
they
will
feel
like
they
belong
to
the
same
suite
of
products
and
family,
and
that
is
a
party
part
and
a
GT.
A
The
move
to
FEMA
so
yeah
I'm
on
the
Sigma
lecturing
and
information
event
and
once
I've
come
to
full
complete
I.
Don't
need
to
say
that
the
teamwork
makes
the
dream
work.
This
one
has
been
possible
without
the
help
of
Tori,
my
Luca
Emily
Maher
of
Italy
Ragnar
and
Chris
and
Amanda,
of
course,
on
fulfilment.
Your
help
has
been
tremendous
and
I
really
appreciate
the
the
first
turn
around
some
of
those
odds.