►
From YouTube: Learning Experience Working Group Meeting 2022 01 26
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
One
all
right,
thank
you
right,
so
good
time
of
the
day,
everybody
I
will
do
my
best
to
keep
brian's
level.
So
here
we
go.
Welcome
to
the
learning
experience
working
group
today
is
january
26
and
we
have
a
special
guest
so
sandra.
Thank
you
so
much
for
for
joining.
I
was
hoping
we
could
go
through
our
normal
agenda
and
I've
added
point.
Four.
There
dedicated
to
the
questions
the
group
would
like
to
ask
cinder
so
feel
free
to
add
anything.
There
hi
sean
hi,
michael.
A
E
A
Okay
from
deliverables
from
last
week
from
last
meeting
sorry,
there
was
an
action
for
me
to
create
a
more
visual
timeline
in
an
added
to
apparent
epic.
The
link
is
in
the
agenda
there
and
I'd
like
to
take
the
opportunity,
since
we
have,
we
have
everyone
here
to
review
it
together.
If
that's
okay,
I
can
share
my
screen
because
I
was
reviewing
it
with
brian
yesterday.
B
A
All
right,
so
let
me
just
open
the
calendar,
so
I'm
aligned
okay,
so
we
right
now
we're
here.
We
had
the
business
call
last
week
and
now
this
week,
we've
given
the
vendors
an
a
week
to
come
back
with
their
with
their
answers
from
the
requirements
and
all
so
right
now
we're
here
and
then
starting
on
the
week
of
january
31st
we'll
have
the
four
vendor
demos
and
then
here
this
is
where
I've
done
a
small
update
to
the
to
the
timeline,
because
we
didn't
have
this
this
step
here
before.
A
I've
added
february
9,
because
this
is
where
we
have
the
next
working
group
following
the
demos
to
do
kind
of
like
a
down
select,
so
we're
gonna
watch
them
of
four
vendors.
But
then
we
really
want
to
select
two,
and
that
is
to
do
the
the
poc
so
moving
here
for
the
we're
allowing
pretty
much
two
weeks.
So
everyone
can
watch
the
recordings
and
ask
questions
and
all
of
that.
A
So
the
goal
really
is
to
have
the
pocs
completed
by
the
21st
of
february
and
then
again
I
think
at
march
2,
just
because
it's
when
we
have
the
working
group
this
meeting,
so
we
can
really
select
the
platform
and
then
to
review
that
go,
no
go
decision
and
then
hopefully
we
can
create
the
implementation
plan
by
the
week
of
march
7th.
So
I
just
want
to
pause
here
for
a
second
and
see
if
you
have
any
comments
feedback.
This
is
a
feasible
timeline
for
everyone.
D
Yeah-
and
so
I
do
know-
and
so
this
is
where
I
was
looking
for-
for
sunders
feedback.
As
far
as
you
know,
this
is
this
is
an
aggressive
timeline
right.
We
are
in
what
I
would
consider
more
of
a
you
know,
moving
fast
trying
to
get
to
a
decision
quickly,
based
on
the
fact,
too,
that
a
lot
of
us
have
been
through
this
before
a
lot
of
us
have
been
through
this
together
before,
and
so
I
just
wanted
to
see
sunder.
What
do
you
see
is
the
the
risk
for
moving
this
quickly.
C
One
of
the
things
that
I
had
suggested,
I
think
again,
I
put
a
very
high
level
couple
of
slides
on
this
that,
after
you
get
all
the
requirements
pieces,
there
are
other
factors
that
come
into
play.
Are
there
special
relationships
that
you
know
is
one
of
the
vendors
you
know
in
a
deeper
partnership
with
gitlab
in
some
manner
I
mean
so
those
things
all
come
into
play
also
in
your
decision
process
right.
So
you
may
want
to
think
about
some
parallel
lines
around
hey.
C
Okay,
otherwise
I
I
think
again,
we
if
you
have
already
submitted
the
rfp
to
the
vendors,
we
know
what
we
want
going
through
the
demos
might
be.
I
would
say
that
selection
process
and
the
proof
of
concept,
perhaps
two
three
more
weeks
of
cushion,
would
be
helpful
that
that's
probably
where
I
would,
if
we
had
to
add
anything
here,.
D
And
you
bring
up
a
good
point,
I
mean
part
of
this.
Is
you
know
what
we're
driving
to
is?
We
do
want
to
get
a
very
robust
proof
of
concept
around
the
technical
certification
so
that
we
are
truly
taking
some
key
use
cases
that
we
would
then
immediately
flip
into
you
know
more
of
a
production
mode
that
would
go
into
our
beta
test
that
we're
targeting
around
the
may
timeline.
D
D
F
F
C
So
we're
going
to
have
to,
I
think
we
have
to
look
at
multiple
work
streams
as
we
go
through
this
piece
in
here
right,
so
the
biggest
piece
with
content.
Is
we
don't
want
garbage
in
garbage?
I
mean
we
don't
want
to
take
garbage
and
move
it
out
there.
I
I
hate
to
use
the
term,
but
there's
a
lot
of
legacy,
content
or
content.
That
is
that
we
expect
to
change
quite
quickly,
so
we
we
have
to
take
the
catalog
and
make
a
decision
on
what
we
are
going
to
migrate
over
that.
C
C
We
need
to
start
putting
together
some
use
cases
so
that
the
demo,
the
vendors,
can
provide
how
that
will
manifest
itself
in
there
in
their
products
and
platforms,
so
that
we
can
then
begin
to
think
about
how
do
we
need
to
look
at
this
right,
so
that
will
need
a
little
bit
of
platform,
specific
alignment,
but
we
need
to
be
thinking
about
that
part
also,
but
content
specifically,
I
really
think
just
thinking
about
what
exactly
are
we
going
to
move?
That's
the
most
important
thing.
G
E
Yeah
so
on
the
working
group
for
this
meeting
last
week,
we
had
discussed
how,
when
we're
going
through
the
content
at
the
same
time,
review
if
something
is
updated
or
outdated
and
at
that
point
decide
whether
it
needs
to
be
moved
over.
So
we
don't
move
over
a
lot
of
content
that
isn't
necessarily
needed,
or
we
could
also
remove
duplication
of
effort
at
that
time.
So,
content
that
covers
the
same
topics.
Let.
E
Yeah,
I
think
an
easy
way
to
do
that
is
solidifying
our
naming
convention
that
we're
going
to
be
using
for
the
content
moving
forward.
We
have
no
solidified
naming
convention
currently,
so
I
think,
having
those
kind
of
standards
when
we
move
to
a
new
platform
will
be
very
helpful
for
not
only
one
determining
who
the
dri
is
as
far
as
the
department
wise,
but
also
ensuring
that
we
have
that
audience
clearly
defined
in
the
content.
Title.
H
Can
I
just
add
as
well
kendra,
you
might
already
have
a
solution
for
this,
but
are
we
considered
if
I'm
a
user,
that's
50
of
the
way
through
a
certification
on
edcast?
Do
we
need
to
put
some
plan
in
place
to
make
sure
that
that
progress
carries
on
or
how
we
plan
to
notify
them?
If
that
certification
is
going
to
move
from
one
platform
to
another.
C
Extreme
that
should
be
a
separate
work
stream
that
we
need
to
build
out
in
here
for
users
and
their
experience,
and
when
the
cut
off
from
it
cast
to
this
would
happen
right.
So
that
would
be
because
I
don't
think
we're
just
going
to
completely
turn
off
at
cast.
While
we
go
through
this
right,
that's
a
separate
work
stream,
we'll
need
to
build
out.
E
Yeah,
as
far
as
switching
between
the
two,
I
don't
think
it
would
be
an
issue
for
a
user
perspective
because
they
wouldn't
lose
progress.
All
of
the
certification
pathways
in
our
scoring
courses
have
free
form
navigation,
which
means
they
only
have
to
complete
the
written
and
the
hands-on
exam
in
order,
the
other
all
of
the
actual
learning
modules
they
can
complete
at
any
time.
A
E
E
And
my
initial
thought
josh
to
make
this
a
lot
easier.
Is
we
have
that
master
spreadsheet
where
we
had
already
compiled
all
of
the
content?
That's
in
gitlab
learn
and
we
identified
who
was
the
dri
for
each
content.
I
think
if
we
continue
to
use
that
master
sheet
and
then
just
add
additional
columns
to
mark
whether
it's
outdated
or
it's
moving
over
and
then
we
that
has
the
audience
listed
on
it
on
that
sheet
and
then
list
out
the
new
naming
convention.
E
So
what
the
title
will
be
when
it
moves
to
the
new
platform
would
be
super
helpful
because
then
it
would
make
it
easy
not
only
for
all
of
the
different
departments
to
migrate
the
content
over,
but
it
also
would
be
easy
for
us
to
sort
and
say:
okay,
all
of
this
is
being
depreciated
and
we
can
actually
count.
You
know
200
and
whatever
line
items
are
not
going
to
be
moved
over,
and
that
would
be
an
easy
reporting
thing
to
to
bounce
up
to
sit.
If
you
ask
for
it.
I
I
think
the
other
piece
of
that
is
is
starting
to
you
know.
We
talk
about
who's
that
who
the
dri
is
for
some
of
that
content,
but
also
migrating
the
content
owner
for
some
of
those
things
right.
So
the
purpose
of
it,
depending
on
what
the
purpose
of
that
content
is.
Should
that
be
something
that
is
owned
by
the
education
services
team
versus
whoever
whoever
it
is
that
develop,
that
content
right
and
specifically
we're
talking
about
the
the
product
enablement
content,
some
of
the
other
content
in
there.
I
A
G
A
Okay
c
1.2,
so
this
point
b
then,
is
for
brian
to
check
with
ellen
about
current
at
cast
allocation.
I
haven't
spoke
to
him
about
this,
so
pick
it
up
and
the
other
two
is
just
to
review
the
requirements
which
I
know
that
the
team
was
reviewing
it
and
bringing
out
a
lot
of
questions.
So
there
was
ongoing
discussions
there
and
then
there's
a
video.
C
G
A
F
No,
no
risks,
apologies
for
the
delay,
but
finally
did
provide
feedback
in
the
doc.
The
tldr
there
is
like
a
no
no
new
requirements.
We
feel
like
the
list
is
comprehensive.
The
only
I
did
tag
ed
sepulus
because
they
have
a
requirement.
One
requirement:
that's
not
captured
about
a
sales
force,
integration
and
porting
over
certs
and
credentials
into
to
be
accessible
and
visible
at
the
contact
record
within
salesforce,
but
I've
asked
ed
to
provide
more
context
there.
F
G
A
D
D
You
know
a
hundred
and
fifty
thousand
dollars
a
hundred
more
for
subscription,
so
got
us
to
two
hundred
thousand
and
got
us
a
hundred
fifty
thousand
for
implementation.
But
I'm
not
sure
that
that's
enough,
and
so
I
wanted
to
try
and
see
where
we
were
with
that
to
ensure
that
we're
feeding
them
data.
D
Yes,
it
is
so
so
sorry
I
I
know
that
we
had
been
getting
you
some
usage
numbers
and
then
I
think
there
was
some
pricing
pieces,
so
we
may
have
the
pieces
and
we
may
need
to
go.
Do
the
math
ourselves,
I'm
just
trying
to
understand.
I
know
we're
sort
of
in
process.
You
know
partnering
to
try
and
again
get
sort
of
budgetary
quote
items
so
that
we
didn't
have
to
go
to
the
individual.
D
C
So
I
propose,
I
think,
at
this
point
I've
given
some
suggestions
on
how
vendors
look
at
the
what
pricing
models
exist.
I
I
have
not
taken
this
and
done
an
actual
calculation
of
what
the
ranges
might
be
etc.
Based
on
this,
I
can
go
back
and
look
at
some
of
that
and
come
back
to
you
guys
with
with
just
sort
of
ballpark.
Are
you
in
the
right
ballpark
with
the
numbers
you
submitted?
Okay,.
A
F
I
added
a
couple
others,
I
don't
know
if
this
is
for
the
team
or
for
sundar,
so
number
five
said.
Thank
you
barbara,
for
creating
that
agenda.
When
should
we
aspire
to
have
to
build
out
the
the
timeline?
Sorry,
not
agenda
timeline
to
build
out
the
timeline
even
further.
Is
that
something
we'll
we'll
be
in
a
better
position
to
look
at
in
end
of
february
or
into
march?
F
D
If
you
know
the
partners
are
gonna,
tell
us
number
one
and
then
also
number
two
is,
I
think,
as
we
get
down
the
path
and
we're
working
on
the
certification
program
as
well
too,
I
think
that
we're
going
to
have
to
focus
our
efforts
on
that
certification
program
to
meet
that
project,
so
to
get
that
done
and
folding
that,
in
that
may
then
create
delays
on
some
of
the
you
know.
People
like
yourself
who
aren't
in
that
primary
position
for
that
launch
yeah.
D
C
Yeah,
it's
a
very
good
point
at
christopher,
says
right:
each
vendor
is
going
to
have
and
again
the
complexity
of
some
platforms
versus
others.
The
integration
with
your
systems,
all
those
things,
will
sort
of
come
into
play
just
a
little
too
early
to
get
into
a
detailed
implementation
plan.
Right
now,.
F
Yep,
fair
enough
one
other
tactical
question
for
the
demos
that
we're
scheduling
next
week,
I
imagine
all
of
us
may
have
some
additional
team
members
that
would
be
interested.
How
do
we
want
to
approach
that?
Can
we
invite
those
folks
to
the
demos?
Do
we
want
to
record
and
make
them
available
for
async.
F
D
I
mean
participate
is
like
we're
happy
to
have
you
attend,
but
we're
also
very
sensitive
too.
We
have
an
hour
and
a
half.
That's
going
to
be
a
lot
of
focus,
so
yeah
super
focused
and
we
would
just
say
like
if,
if
all
of
a
sudden
you
know
you,
you
see,
you
know
kendra
and
jamie
and
sean
expire
of
questions,
and
you
want
to
interject
something
I
think
that's
completely
appropriate,
but
we're
just
trying
to
again
operate
from
that.
You
know.
F
D
And
actually-
and
so
it's
a
great
point
david,
because
I
think
our
our
goal
is-
that
is
as
you're
getting
questions
or
you're
seeing
things
that
you
get
those
and
then
we
would
be
able
to
manage
a
breakout
meeting
where
we're
not
again.
Where
we're
you
know,
taking
the
vendor
and
saying
hey,
let's
get
more
time
around
this
subject,
but
we're
not
impacting
that
sort
of
main
delivery.
Does
that
make
sense.
F
B
C
F
C
Great
question,
I
I
think
the
I
mean
we
do
have
the
proof
of
concept
where
we
can
get
more
specific
I,
but
I
think
we
have
to
give
them
some
guidance
as
to
that
initial
focus
where
we
are
etc
and
because
they
can
start.
You
know
saying:
oh
we,
you
know
they
can
all
walk
through.
How
somebody
sell
you
know
signs
up
for
a
course
how
they
register.
C
I
mean
the
experience
part
is
going
to
be
important
as
we
look
at
that
navigation
and
some
high
level
feature
functionality,
but
is
there
a
specific
couple
of
areas
that
we
want
all
of
them
to
make
sure
that
addresses
our
specific
audience
needs
for
the
initial
rollout
right?
So
we
just
don't
want
them
to
go
off
into
too
many
areas
and
then
sort
of
come
back
to
this.
Just
without
addressing
the
details
here.
C
And
I
think
we
should
also
have
them
touch
upon.
If
I'm
an
employee,
I
want
to
have
a
different
experience
versus
from
a
customer
part
that
that
part,
I
think
we
have
to
get,
because
we
are
going
to
have
the
system
across
all
audiences
right.
So
there
may
be
two
three
areas
that
we
definitely
want
to
make
sure
that
they
showcase
their
demos.
B
E
And
one
thing
that
I
that
I
would
love
to
see
that
we
didn't
get
to
see
from
edcast
is
successful,
use
cases
for
other
clients
like,
in
particular
like
kind
of
skill
jar
with
with
linkedin,
so
successful
use
cases
where
they've
actually
implemented
these
things
with
other
clients
that
they'd
be
willing
to
share.
So
it
with
those
examples
would
be
very
helpful
for
me
to
see.
I
I
C
We
a
lot
of
these
folks,
will
end
up.
You
know
trying
to
jump
into.
Oh,
we
have
the
badges.
We
have
this.
The
points
I
mean
gamification,
so
they'll
go
into
all
the
buzz.
You
know
the
hot
areas,
but
the
core
capability.
We
we
want
to
make
sure
we
don't
have
them
distract
us
by
not
going
through
that
part.
I
D
So
is
there
a
way
that
we
could
then
get
some
input,
michael
from
you
and
the
team
on
you
know
what
I
would
like
to
do
is
get
to.
You
know
just
sort
of
a
crisp
one
pager
of
here
are
the
scenarios
that
we
want
to
be
able
to
provide
to
the
vendors,
because
we
could
then
brief
them
and
tee
them
up
and,
in
my
mind,
they're
sort
of
hey
here's
some
key
scenarios.
We
really
want
you
to
walk
through.
D
You
know
end
to
end
and
then
here's
you
know
I
think
some
overviews
like
okay,
what's
external
versus
internal
view,
here's
some!
You
know
how
do
these
reports
look?
You
know
that
we
could
just
have
them
sort
of
check
off
and
dig
in,
but
could
we
solicit
that
input
so
that
we
could
deliver
that
to
the
to
the
vendors
and
allow
them
time
to
prep
for
next
week.