►
From YouTube: UX Research 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
A
A
A
If
there's
no
questions
to
get
me
started,
I
can
talk
a
little
bit
about
what
we've
been
doing
within
the
department.
So
our
focus-
and
this
quarter
are
okay,
our
ISM
and
building
training,
materials
for
product
managers
and
product
designers
and
and
anyone
really
across
the
organization
that
would
like
to
to
do
some
UX
research
and
we're
doing
this.
B
C
Key,
you
may
be
Sarah
key,
maybe
talk
a
bit
to
how
good
we
are
as
an
organization
as
a
whole
to
follow
up
on
research
findings,
talk
with
you
XD
signers
yesterday,
and
we're
generating
a
lot
more
issues
that
are
being
handled
either
by
closing
them
as
not
important
enough
for
things
that
need
to
be
done.
How
is
that
for
UX
research,
specifically?
How?
How
are
we
following
up
quickly
enough
in
Muslim
product
on
the
findings?
Yes,.
A
I
think
it's
changed
a
lot
and
I
think
a
lot
of
us
juice.
The
fact
that
a
lot
more
closely
with
product
and
designers
as
well,
and
so
the
kind
of
process
that
we
used
to
go
through
before,
is
that
when
we
had
a
much
smaller
research
team,
we
will
kind
of
manage.
You
know
the
requests
that
came
in
to
us
and
we
would
go
and
do
a
lot.
These
studies
in
isolation.
A
A
They
are
leaving
those
interviews
with
that
with
the
support
of
researchers,
and
we
also
have
product
designers
who
have
conducted
solutions,
validation,
work,
which
is
things
like
usability
test
in
design
preference
tests,
and
things
like
that
again
with
the
support
of
the
researcher
and
and
I
think
that
that's
making
a
difference
and
I
think
it's
much
better.
When
a
designer,
a
PM
can
hear
firsthand
that
the
problems
that
users
are
facing
so
I
do
think
that
a
lot
more
of
our
findings
have
being
incorporated
in
some
will
being
acted
upon.
C
Thanks
I
got
the
next
question
to
slide.
Five
talks
about
feature
flags
and
I
noticed
Laurie
is
in
the
call
I
think
that
would
feature
Flags.
One
of
the
things
I've
seen
happening
in
companies
is
that
they
get
added
and
then
they
at
a
certain
point.
They
are
dialed
up,
but
then
at
some
point
you
need
to
remove
the
code
like
the
feature
flag
has
proven
itself.
C
There's
no
need
to
kind
of
keep
that
extra
complexity
in
the
code
to
make
the
feature
flag
work,
and
that's
always
struck
me
as
something
whether
the
application
should
really
help
you
like
identify,
which
feature
flags
have
been
at
like
a
hundred
percent
for
a
long
time
suggests
where
that
code
lives,
and
even
at
some
point,
maybe
offer
to
like
make
America's
to
remove
that
code
automatically
and
then
now
that's
a
three-step
process
like
which
ones.
Where
does
the
code
live
offered
to
fix
the
code?
D
Definitely
something
that
came
out
of
our
research
said
we
I
talked
to
quite
a
few
people
who
are
like.
Please
help
me
manage
this.
It
is
unmanageable
when
we
have
thousands
of
them
and
then
they
just
become
part
of
the
code
like
you
said.
So
what
are
the
findings
was
that
we
really
need
to
look
into
ways
to
help
them
manage
and
some
of
the
things
that
we
discovered
were.
How
long
has
it
been
used
and
how
frequently
is
it
being
used?
How
frequently
is
it
being
accessed
so
not
just
that?
D
Maybe
it's
been
out
there
for
a
month
or
year,
but
how
many
people
are
accessing
it
and
how
frequently
so
they
can
make
that
decision
internally,
that
that
needs
to
be
merge
request
make
it
a
feature
to
stop
it
with
the
the
feature
flags
and
then
they
can
manage
their
code
properly,
and
they
do
want
help
doing
that.
They
want
some
automation
around
that
they
don't
they
can't
do
it
manually,
it's
just
too
much
to
handle
so
you're
spot
on
and
that
definitely
came
out
of
the
research
and.
C
Is
our
there
mate?
Are
there
issues
for
that?
We're
we're
looking
at
that
or
are
there
and
then
what
is
they?
Do
you
by
any
chance
know
what
the
competition
there
is
like
our
people,
I,
think
I.
Think
people
are
saying
to
like
show
flag
start.
Our
unused
I
think
the
best
thing
class
application
are
identifying
to
cope
with
those
flags,
I've
not
seen
anybody
who
can
automatically
generate
the
code
to
remove
the
feature
flag.
What's
your
take
on
the
industry,
we.
D
Talked
to
a
couple
people
who
are
using
launched,
darkly
and
Heroku,
and
neither
of
those
mentioned
any
help
that
they
were
giving
with
feature
flags
at
all.
So
definitely
is
not
a
thing
yet,
but
definitely
is
something
that
they
they
need.
Help
with
and
or
eats.
Our
product
manager
has
been
out
on
at
a
conference,
so
I'm
not
sure
where
she's
gonna
take
the
issues,
but
there
has
been
research
issues
raised
for
this
particular
piece
that
she
has
reviewed,
I've
gone
through
them
with
her
and
the
design
team.
E
Recently
I've
been
using
github
issues
a
lot
on
my
mobile
browser,
so
I
was
curious,
so
any
work
being
done
also
I
had
dated
him
made
this
periscope
chart
which
I
linked
and
I
see
like
four
percent
in
winter
and
eight
percent
in
summer
usage
for
mobile
phone
on
github.com,
but
on
the
sign-in
page,
it's
more
like
40
percent,
or
so
people
try
to
sign
in
on
mobile
smartphones.
That
may
or
may
not
mean
something.
E
A
F
So,
to
put
it
in
the
short
way,
there
is
no
current
work,
but
I
just
wanted
to
highlight
that.
There's
a
new
issue
where
designers
are
discussing
creating
guidelines
for
how
gait
lab
should
scale
on
different
screen
sizes
and
from
our
previous
system
to
the
OTP
scale
survey.
We
got
some
insight
on
the
current
usage
versus
what
people
are
looking
to
use
mobile
for,
and
so
what
our
current
thinking
around
that
is
usage
is
lower.
But
that's
perhaps
because
it's
not
optimized
for
the
workflows
that
people
are
trying
to
carry
out
on
mobile.
E
F
Yeah
so
I've
definitely
heard
about
it,
and
there
are
two
issues
that
I'll
link
there
and
I'd
say:
we've
heard
about
it,
but
it's
a
question
of
priority
and
I
think
that's
the
decisions,
that's
probably
wider
than
the
UX
team,
which
would
bring
in
product
and
more
leadership
as
well,
but
I
think
it's
an
interesting
idea.
I
personally
would
have
interest
in
checking
my
issues
aren't
looking
at
merchants
less
than
such
on
my
home,
so
I
would
really
be
interested
in
it.
But
it's
not
something.
We've
done
a
coordinated
research
study
about
yeah.
E
E
F
C
C
So
a
few
things,
first
of
all,
there's
the
potential
of
mobile,
slowing
down
development
like
we
cannot
release
that
feature
until
our
mobile
app
deploys
supports
it.
So
that's
that's
something
we
should
never
do.
We
should
never
jeopardize
our
for
velocity.
Second,
there's
a
there's,
a
lot
of
enthusiasts
making
mobile
apps
forged
lamp
and
that's
a
potential
way
to
do
something
for
the
relatively
low
investment.
Take
someone
who's
built,
a
great
mobile,
app,
forget
lap
and
it's
in
their
spare
time
and
paid
him
to
work
on
that
full-time
I'm.
Very
supportive
of
something
like
that.
C
Mobile
is
the
future
like
iPad
things
like
that
should
be
supported.
Fact
that
our
web
IDE
doesn't
work
well,
no
I
pad
I
think
it
is
a
big
detriment
to
to
to
our
future
strategy
for
mobile
apps.
They
tend
to
work
better
if
you
have
a
SAS
application,
because
then
it's
easy
to
like
set
up
to
push
messages
and
everything
else
we
have
90
percent
of
our
users
are
in
self-managed
instances
and
it's
harder
to
kind
of
make
those
things
work.
C
Well,
so
it's
paramount
that
we
make
sure
that
our
progressive
web
app
are
like
our
regular
application
skills.
Well,
two
mobile
screens.
That
should
be
our
first
and
foremost
focus
and
the
last,
maybe
a
bit
of
a
note.
I
think
I
thought
it
was
a
question
of
time
before
we
were
forced
to
make
a
mobile
app
and
I've
been
amazed
that
so
far
we've
never
lost
the
deal
because
of
it
we've
never
had
it.
It
doesn't
come
up
with
customers
like
you,
should
have
a
mobile
app.
C
That
doesn't
mean
it's
not
needed,
but
just
the
amount
of
time
that
it
comes
up
have
been
surprisingly
low
and
I
can't
believe
that
we're
in
2019
so
in
2020,
and
we
still
don't
have
a
mobile
app
and
we
seem
to
kind
of
get
away
with
it
now
getting
away
with.
It
doesn't
mean
it's
the
right
right
decision,
but
I've.
It's
been
very
surprising
to
me.
E
Would
it
make
sense
to
just
narrow
down
a
movie?
Let's
say
a
web
browser
focused
or
even
application
just
to
the
issue
management
or
some
things
which
people
do
on
mobile
phones,
solid,
like
JIRA
I,
think
has
it
for
if
I'm
not
mistaken,
for
users,
and
it
will
enable
maybe
any
kind
of
usage,
just
just
I'm,
not
talking
for
all
the
stages.
Just
for
a
particular
issue.
G
I,
just
I
just
added
one
meta
question
to
the
document:
if,
if
the
previous
question
is
over,
I
can
verbalize
migration
now.
Is
it
Quran.
C
G
G
We
just
had
and
I
remember,
like
a
colleague
a
sales
colleague
of
mine
last
week
sharing
some
findings
about
a
customer
who
has
been
a
customer
for
about
a
year,
not
a
large
customer,
maybe
about
hundred
premiums,
but
they
did
bring
up
this
point
about
not
having
a
by
lab
now
that
github
has
one.
So
that's
the
background
and
the
question
is:
how
can
we
best
contribute
and
how
do
these
findings
become
roadmap
items.
A
So
I'll
take
that
question,
but
so
the
research
findings,
what
tends
to
happen
is-
and
we
go
through
like
at
a
stage.
We
start
with
problem
validation
and
that's
where
we
come
together
as
a
team,
that's
designer
researcher
and
product
manager,
and
we
discuss
like
a
problem
space
and
we
might
delve
into
that
more
than
customer
interviews.
A
As
such,
they
kind
of
just
built
into
the
product
development
roadmap
and
then
the
second
half
of
that
question.
And
how
can
you
help
we
have
in
something
called
get
our
first
look,
which
is
our
research
panel
and
you
can
visit
it
by
going
to
CX
r
I.
Think
that's
right.
I
have
a
little
record
up
it
live.com
and
we've
just
kind
of
got
a
shot
and
URL
for
it,
and
basically
asked
us
to
mr.
sign
up
to
that,
and
they
can
take
part
in
any
of
the
research
studies
that
we
do.
A
That's
normally
our
first
point
of
recruitment
and
after
taking
part
in
studies
as
well,
we
do
compensate
we
give
away
things
like
it
looks,
work
and
there's
a
gift
cards
and
things
like
that
as
well,
and
we're
always
kind
of
doing
research.
So
it
wouldn't
be
very
long
until
they
received
a
research
invite
from
one
of
the
researchers
on
the
home
team.
G
Great
thanks
and
just
another
follow-up
to
my
follow-up.
In
case,
let's
say
during
the
sales
cycle,
I
learned
that
a
prospect,
let's
say,
for
example,
one
of
my
past
prospects
found
the
project
management
side
of
gate
lab
not
very
visually
appealing
compared
to
some
of
the
other
two
out.
There
should
I
be
contributing
my
feedback
to
the
UX
research
group,
or
should
I
be
going
to
the
product
owners
and
the
product
managers
of
that
part
of
gate
lab.
What
is
the
best
way
for
me
to
put
that
feedback
in
yeah.
A
Sure
you
can
definitely
reach
out
to
a
researcher,
so
each
of
the
research
is
at
a
kind
of
over
intersection
of
the
progress
if
it
was
to
do
project
management,
that
research
will
be
Catherine
at
the
moment
and
hopefully
what
we're
going
to
be
increase
the
research
headcount
next
year,
so
researchers
will
have
a
smaller
scope,
but
you
should
be
able
to
reach
out
to
a
researcher
and
they
will
always
pass
that
information
on
to
product
managers
as
well
and
but
yeah
researchers.
It's
absolutely
finest
first
block
or
great
X.
A
Dooba
thing
that
you
might
find
interesting
and
if
you
want
to
kind
of
look
at
the
research
that
we
have
in
process,
we
have
the
u.s.
research
project,
which
is
where
we
open
all
our
issues,
and
we
start
tracking
that
the
work
that
we
kind
of
do
it.
And
then
we
also
have
at
the
insights
repository,
which
is
where
we
put
all
our
findings
into
as
well.
A
And
so
again,
if
you
think
your
customer
is
having
problems,
if
you
go
into
the
insight,
repository
probably
found
that
there's
other
kind
problems
in
there
as
well,
which
again
is
great
and
the
more
people
that
you
know
have
had
a
similar
problem.
The
more
likely
it
is
that
we
do
something
about
it
as
well.
Yeah.
G
For
sure,
just
just
to
clarify
I
speak
to
prospects
more
than
customers,
so
it
could
be
that
my
feedback
or
the
feedback
that
I
hear
from
the
prospect
is
not
worth
much.
So
maybe
you
should
not
act
on
it,
but
I
just
want
to
make
sure
I
have
somebody
to
share
it
with
and
they
can
validate
whether
it's
actually
valid
or
not.
Yeah.
A
Really
good
to
us
as
well,
we
do
a
lot
of
testing
with
non
get
love
users
as
well,
and
especially
because,
obviously
they
come
from
other
tools
and
then
they
come
to
work
on
get
web,
and
it
could
be
very
different
from
the
experience
that
they've
had
before.
So
we
need
to
work
out
like
where
those
gaps
are
and
where
we
can
improve
that
experience
for
them.
Yeah
thanks.
A
Put
it
anything
you,
every
research
project
and
I
will
put
that
into
the
document
office
already
begin
to
it,
but
that
you
stopped
link
in
the
document
and
an
open,
an
issue
there.
We
have
a
research
request,
template
just
put
your
can
of
ideas,
and
so
that
and
then
the
relevant
research
will
pick
you
up
perfect
thanks.