►
From YouTube: UX Group Conversation (Public Livestream)
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
Hi
everyone,
so
it's
ten
o'clock
my
time
anyway,
so
we'll
go
ahead
and
get
started
top
of
the
hour,
and
so
thank
you
for
coming
to
the
UX
group
conversation
I'm,
Christy
Linville,
the
director
of
UX
and
happy
to
have
everyone
here,
everyone.
So
it's
ten
o'clock
my
time
anyway,
so
we'll
go
ahead
and
get
started
top
of
the
hour,
and
so
thank
you
for
coming
to
the
UX
group.
Conversation
I'm
Christy
Luna
bill
the
director
of
us
and
happy
everyone
here.
A
This
is
my
first
time
live
streaming
so
and
okay,
so
we've
got
one
question
already
on
the
list
here.
So
someone
asks
Sara
Dee
asked
what
is
the
roadmap
for
the
UX
team?
Are
there
any
plans
to
expand
UX
beyond
product
thinking,
specifically
about
us
for
about
get
lab,
calm
and
so
I'll
start
with
the
first
question,
which
is
around
roadmap?
So
our
UX
roadmap
really
aligns
with
products
right
Maps.
We
do
have
some
UX
led
initiatives,
but
those
aren't
at
a
roadmap
level.
A
Those
are
things
that
we
are
doing
to
actually
help
PMS
build
out
their
own
roadmaps.
We
do
have
some
somatic
things
that
we
were
working
on
again,
trying
to
just
improve
the
experience,
but
we
don't
have
specific
roadmaps
for
those
things
at
this
point,
but
we
do
align
to
the
product
teams
right
maps.
A
The
second
question
was
about
any
plans
to
expand
us
beyond
product
and
the
answer
there
is
there
is
UX
for
about
get
lab
comm.
We
have
a
great
team
that
works
on
on
the
marketing
website
and
and
believe
that
team
is
being
built
out.
Also
as
we
speak.
So
it's
a
very
small
team
right
now.
They
do
a
lot
of
really
great
work
for
being
such
a
small
team
and
I
bill
they'll
have
more
support
going
forward.
A
B
A
A
great
question,
thank
you
so
much
for
that.
So
the
three
roles
that
we
hired
for
in
the
UX
department
are
UX
research,
product
design
and
technical
writing
and
for
the
research
team,
I
think
we're
pretty
much
full
on
that
team,
which
is
exciting
and
wonderful
for
product
design
and
technical
writing,
though,
we're
still
very
actively
hiring
on
the
product
design
side.
A
So
we're
looking
for
strong
product
designers
who
understand
the
end
to
end
a
life
cycle
of
how
Design
Thinking
happens
across
a
project,
so
people
who
have
experience
conducting
user
research
at
least
evaluative
user
research,
so
testing
their
own
designs,
participating
in
generative
research.
So
that's
you
know
around
problem,
validation,
doing
UX
strategy
work
and
then
also
design
work
in
wireframes
and
prototyping.
A
Ideally,
for
some
of
these
last
positions
that
we
have
left
there's
some
of
our
most
deeply
technical
subject
matter.
So
we
are
trying
to
identify
people
who
come
in
with
some
level
of
subject
matter
expertise.
So,
for
example,
we
have
an
intermediate
role
open
for
a
product
designer
on
the
configure
team,
we'd
love
to
bring
on
someone
who
has
some
level
of
experience
with
kubernetes
and
container
based
deployments.
A
They
don't
need
to
be
an
expert,
but
it'd
be
really
helpful
if
they
understand
what
that
is
and
what
it
means
on
the
tech
writing
side,
we
could
use
absolutely
use
some
help,
Recruiting's
and
great
tech
writers.
We're
working
really
hard
on
that
and
actually
mike
lewis
is
on
the
call,
I
think
so,
if
mike,
if
you
want
to
jump
in
and
talk
about
what
you're
looking
for
there.
C
C
So
really
anyone
that
you
have
in
your
network,
who
is
a
strong
technical
writer
or
has
been
a
tech
writer
in
the
past,
oftentimes
tech
writers
are
able
to
take
on
different
kinds
of
roles,
feel
free
to
ping
me
or
refer
them
directly
or
or
let
me
know
if
you
have
any
questions,
we
also
have
it's
worth:
checking
the
tech
writer
Job
Description.
We
have
different,
you
know,
descriptions
for
what
is
intermediate
versus
senior
versus
staff,
so
we
have
a
couple
of
senior
and
intermediate
open
right
now.
D
F
A
That's
a
great
question,
so
the
short
answer
is
no
we're
not
planning
some
big.
You
know
release
it
all
at
once
overhaul
and
but
there's
a
lot
of
work.
That's
happening
on
the
UI
right
now,
so
there's
there's
two
different
tracks
of
that.
One
is
around
just
refining.
What's
there
so
recently
we
hired
a
senior
visual
designer
named
Jeremy
elder
and
he's
been
fantastic,
he's
been
going
through
and
really
looking
at
the
look
and
feel
of
our
product
and
working
on
refining
that
starting
with
iconography
and
some
other
things
and
Jeremy.
H
A
I
A
Yeah,
that's
a
great
question,
so
there
are
a
lot
of
things
that
we're
doing
to
try
to
increase,
assess
for
the
experience
baseline
effort,
which
you
can
see
on
the
last
three
slides
of
the
deck,
is
one
way
that
we're
trying
to
do
that.
So
in
that
effort,
what
we
do
is
we
go
back
and
take
a
look
at
some
of
the
most
impactful
workflows
and
the
product,
and
we
identify
those
by
working
with
product
because
they're
really
the
ones
who
know
what
the
most
impactful
workflows
are
and
then
we're
doing.
A
Heuristic
reviews
of
the
existing
experience
against
industry
standards,
industry
usability
standards
and
then
working.
So
we've
created
issues
from
that
and
we
are
actively
working
to
raise
those
scores.
If
we
can
raise
those
scores
on
our
most
important
workflows,
then
this
the
usability
of
the
system
overall,
should
come
up
so
now
I'm
going
back
specifically
to
the
sus
and
when
we
run
the
sus
survey.
What
if
that
is,
is
a
score
of
the
entire
system
from
end
to
end,
so
it
is
not
meant
to
be
actionable
per
se.
A
It's
meant
to
say,
like
here's,
how
you're
doing
here's
a
trend,
here's
how
you
can
just
know
what
your
performance
looks
like
over
time.
That
being
said,
we
do
also
add
some
questions
into
the
survey
that
go
beyond
just
a
standard.
It's
us,
and
so
one
of
those
is
just
a
free-form
free
text.
Is
there
anything
else,
you'd
like
to
tell
us
about
our
usability
and
some
of
the
other
questions?
We've
run,
it's
been
around
mobile
usage,
so
for
the
free
text.
A
So
if
there
are
some
things
that
come
in
that
are
very
specific,
like
basically
bug
reports,
when
we
see
things
like
that,
yeah
absolutely
a
Katherine
ran
the
lasts
us
and
she
created
issues
for
those
and
by
and
large,
though,
the
feedback
that
comes
in
in
that
format.
We
try
to
look
at
that
as
directional.
It's
not
necessarily
it's
not
usually
directly
actionable,
but
we
can
see
trends
coming
out
of
that
and
then
based
on
those
trends.
We
know
where
to
go
dig
in
and
to
learn
more
through
research
for
the
mobile
usage.
A
What's
interesting
found
because
we
ran
questions
across
both
the
q1
and
the
Q
to
suss
in
q1
we
asked
how
frequently
I'm
paraphrasing
basically,
how
frequently
do
you
use
get
lab
on
mobile
devices
and
what
we
found
was
yeah,
not
not
real
frequently
in
the
q2
SS.
We
asked
how
important
is
you?
Is
it
for
you
to
be
able
to
use,
get
lab
on
mobile
devices?
We
broke
it
out
by
both
phones
and
tablet,
and
what
we
found
out
is
it's
real
important
for
people
to
be
able.
D
A
A
I
If
no
one
else
has
a
question
out
another
one,
we
recently
kind
of
refactored
the
docks
navigation.
So
I
don't
know
if
this
is
maybe
more
of
a
question
for
Mike,
but
I
think
it
kind
of
spans
both
UX
and
docks.
Where
I'm
wondering,
if
there's
any
plans
to
do
any
UX
research
around
how
like
how
that's
affected
a
ssin
of
docks
and
like
where
we
might
improve
the
overall
navigation,
yeah.
A
That's
a
great
question,
so
two
things
one
is
it
might
let
him
shine
in
on
this
as
well,
but
he
and
I
agree.
The
docks
site
needs
usability
improvements
across
the
board.
We
do
have
an
open
issue
for
that.
A
lot
of
them
are
just
back
to
industry,
standard
improvements
that
we
don't
even
need
to
research.
A
So
some
of
the
ways
that
we're
visually
organizing
our
content
hierarchy
just
aren't
effective
and
we
know
it
and
we
just
need
to
go
in
and
fix
it,
and
so
that
is
on
on
the
list
of
priorities
in
terms
of
the
recent
refactoring
of
the
navigation
that
was
awesome
I'm,
so
so
thankful
for
the
folks
who
joined
in
to
do
that.
I
think
it
made
such
a
big
difference
and
again
that
was
one
of
those
things
where
we
didn't
necessarily
need
to
research
it.
A
We
could
look
at
just
industry
standards
for
how
navigation
works
and
go
and
our
interaction,
because
that's
the
way
we
change
there
was
the
interaction
patterns
are
you
know,
interaction
patterns
were
ineffective.
That
being
said,
we
do
think
that
we
also
need
some
inferences.
An
information
architecture
work
on
the
docks
site
and
that
is
a
much
bigger,
much
more
complicated
effort.
And
so
that's
what
we're
going
to
need
to
do
some
user
research
on
that
and
that's
something
that
Mike
and
I
have
also
been
talking
about
and
Mike.
Do
you
want
to
China.
C
We
have
open
issues
around
UX
research
that
we're
going
to
be
doing
more
of
I.
Think
generally,
the
trend
has
been
improving
the
relationship
between
tech
writing
and
the
various
UX
roles,
and
also
tech,
writing
and
engineering.
So
that's
why
you've
seen
things
like
the
new
left,
nav
and
other.
We
have
a
process
now
for
for
engaging
engineering
to
get
more
consistent,
help
with
initiatives
that
are
high-impact
like
that.
So
there
are
different
initiatives
going
on
that
kind
of
all
speak
to
two
dots,
UX
I
think.
J
A
And
so
the
jobs
to
be
done
actually
ties
back
to
the
experience
baselines
that
I
was
talking
about
earlier.
So
though,
the
most
impactful
workflows
are
the
jobs
to
be
done,
that
we
know
users
are
using
our
arms
our
product
to
complete
and
what
we,
as
a
UX
team,
really
try
to
do
is
try
to
abstract
back
from
features
and
solutions
and
think
about
what
our
users
trying
to
achieve.
What
is
the
job
that
they
need
to
get
done
in
the
course
of
their
work,
so
that
we
don't
presume
that
we
know
the
answer.
A
We
don't
presume
that
we
know
the
solution.
We
can
really
be
more
creative,
diverge
and
our
ideas
so
that
we
can
research
those
and
then
converge
on
the
right
solution
and
so
yeah
those
jobs
to
be
done.
The
way
that
that
worked
was
we
identified
those
and
then
those
are
the
things
that
we're
looking
at
to
make
specific
improvements
on
and
I
will
share
the
screen.
Let's
see.
A
Seven
are
the
scores
that
those
workflows
God
and
there
is,
if
you
read
about
it
in
the
handbook,
there's
a
grading
rubric
that
we've
used
to
say
what's
in
a
what
to
be,
what
to
see
what's
a
D
what's
in
F,
and
so
one
of
our
okay
ours,
for
this
third
quarter,
is
to
raise
the
score
of
seven
of
these
workflows
by
one
grade
level.
So
what
you
should
start
to
see
is
some
of
these
workflows.
Move
moving
into
a
B
to
B
is
a
good
score.
A
J
A
A
K
Hi,
this
is
Jim
Riley
I'm,
a
salesperson
in
DC,
just
a
question:
what's
the
best
way
to
provide
feedback,
I
think
there's
some
slack
channels
and
I'd
provided
feedback
on
one
slack
Channel
and
someone
suggested
providing
on
another?
Is
that
a
good
way
to
provide
feedback?
Or
what's
your
preferred
communication
method?
Yeah.
A
It
can
be,
their
site
can
be
a
good
way,
and
apparently,
if
you
have
a
question,
the
UX
Channel
on
slack
is
is
very
active
and
you
should
get
a
response
pretty
quickly.
If
you
see
something
that
it's
an
obvious
UX
bug
and
issue
is
honestly
the
best
way
to
communicate
with
us,
because
the
product
team
prioritizes
the
work
that
the
UX
team
does
and
an
issue
is
a
way
to
get
that
visibility
to
that
issues
of
the
product
also
knows
that
this
is
something
that
they
might
want
to
consider.
Okay,.
L
Are
there
any
companies
or
other
products
that
you
look
at
and
say
and
I
say
this
a
little
bit
because,
while
we're,
if
you're
not
a
UX
and
history,
we're
all
learning
a
bunch
but
we're
gonna
have
a
harder
time,
there's
a
lot
of
nuances
to
it
that
are
easy
to
miss
and
that
we
won't
be
able
to
verbalize
or
understand
the
way
you
all
do.
A
I'm
gonna
answer
it
slightly
differently
than
how
you're
at
this
is
part
of
our
design
process,
and
so
this
is
kind
of
stage
group-specific
right,
because
gitlab
is
a
product.
Now
covers
many
different
types
of
tools,
so
the
stage
groups
are
looking
at
their
own
sets
of
products
to
do
that
competitive
analysis
and
we're
looking
at
that
one
to
understand
just
what's
happening
in
the
market
today.
What
types
of
features
are
there
are
they're
super
common
patterns
for
how
these
tools
are
handling
a
particular
workflow
or
use
case?
A
Then
it
becomes
well
if
everyone's
doing
it.
That
way,
then
that's
probably
the
expectation
for
how
that
will
happen
and
probably
start
is
a
good
starting
place
for
us
to
do
our
own
design
work.
It's
also
an
opportunity
for
us
to
look
and
see
where
things
aren't
going
so
well.
We
go
wow
they're
doing
this
and
doesn't
make
sense,
and
this
is
a
lot
of
clicks.
Why
are
they
doing
that?
A
So
that's
definitely
a
part
of
our
process,
so
you
asked
us,
like
person,
said,
like
everybody,
has
their
own
personal
sites
and
tools
that
they
just
love
I'm
not
going
to
make
mine
specific
the
devil
say
one
of
the
that
I
had
a
really
good
experience
with
lately
was
better
calm.
It
is
a
tool
for
getting
a
mortgage,
and-
and
it
was
so
beautifully
like
the
information
architecture
was
just
beautiful.
It
was
so
clearly
stepped
out.
A
I
knew
exactly
where
to
go
to
do
what
I
needed
to
do
and
when
there
was
an
action
for
me
to
take,
it
was
so
clearly
visible
within
the
tool,
their
cut.
Their
visual
content
hierarchy
was
beautiful.
My
I
knew
exactly
where
to
go.
I
I
never
had
to
dig
around
and
search
for
the
information
that
I
needed,
and
those
are
the
types
of
things
that
the
users
want
across
the
board.
A
Now
what's
interesting
for
us
at
box
tool
is
that's
very
different
from
a
consumer
tool
in
terms
of
the
amount
of
information
that
a
user
is
going
to
want
on
a
screen.
So
we
really
think
a
lot
about
data
density
and
supporting
our
users
with
making
sure
that
they
don't
have
to
scroll
a
whole
lot.
They
don't
have
to
click
too
much
and
data
density
and
the
type
of
tool
that
we
rebuild
is
usually
much
more
for
than
in
a
consumer
tool,
but
those
those
basic
foundational
principles
are
the
same.
Thank
you.
M
A
N
Yeah
yeah,
those
include
things
like
commenting
on
issues
creating
an
issue.
Monitoring
pipelines
was
something
that
came
up.
I
get
the
sense
that
I'm
not
sure
to
what
extent
they're
currently
doing
code
review,
but
cold
review
did
come
up
as
something
they
would
like
to
do
on
mobile
as
well,
so
that
I
think
I
guess
I'd
stay
mainly
in
the
planning,
create
and
see
ICD
air.
This
is
what
I
saw
mostly,
but
there
could
be
able
to
use
cases
as
well.
N
M
I'd
be
I'd
be
curious
because,
like
especially
things
like
pipeline
status
like
that,
might
be
interesting
through,
like
I,
don't
I
haven't
used
some
full
transparent,
used,
get
fox
or
get
get
a
lab
coat,
but
yeah
I
can
see
like
pipeline
status
as
a
push.
Notification
in
my
phone
can
be
kind
of
a
cool
experience.
Yeah.