►
From YouTube: UX Showcase: Ecosystem Introduction
Description
Presented by Libor Vanc
A
My
name
is
Lamar
Vance
I'm,
the
senior
product
designer
on
the
ecosystem
in
the
ecosystem
group,
which
falls
under
the
enablement
stage
group
and
so
we're
a
fairly
new
group,
so
I'm
not
gonna
so
and
I'm
fairly
new
to
to
the
group
as
well.
So
I
don't
really
have
so.
This
UX
Showcase
is
not
going
to
be
that
much
about
like
necessarily
finished
work
since
nothing
that
we've
worked
on
yet
is
in
production,
so
I'm
gonna,
it's
going
to
be
more
about.
A
You
know
just
an
intro
to
you
know
what
the
ecosystem
team
is
all
about
and
then
I'm
going
to
show
some
of
the
current
things
that
were
kind
of
work
in
progress
and
are
some
of
the
challenges
that
we're
working
through
and
then
I'm
going
to
highlight
some
of
the
like
more
future
work
that
were
that
we're
thinking
through
alright.
So
with
that
an
intro
to
our
team.
So
our
team
is
comprised
of
two
back-end
engineers,
an
engineering
manager,
a
front-end
engineer,
senior
product
manager
and
that
a
researcher
and
one
product
designer
all
right.
A
So
the
vision
for
the
ecosystem
team
is
basically
to
support
a
seamless
integration
between
gitlab
and
other
third-party
products
and
services.
Basically,
expanding
get
allows
market
opportunities
by
empowering
developers
to
contribute.
So
we
have
a
really
great
write-up
for
this.
If
you're
interested
in
learning
more
about
this,
you
can
see
this
just
click
the
link
on
our
handbook
there
and
we
have
a
good
write-up
about
the
the
stage
direction
for
our
stage
group.
A
A
It's
also
you
know
focusing
on
integration
between,
like
obviously
get
lab
and
other
key
external
products,
also
focus
on
the
documentation
and
instructions
and
just
best
practice
guides
for
how
to
use
our
API
and
then
just
best
practice
in
for
external
contributors
looking
to
develop
and
like
develop
their
own
integrations
in
the
get
lab
platform
all
right.
So
again,
just
to
reiterate
you
know
our
focuses
at
the
ecosystem
are
on
integrations.
A
Alright,
so
yeah
now
I'll
dive
into
some.
You
know
the
current
state
and
kind
of
some
of
the
open
things
that
we're
working
on
or
work
in
progress.
So
the
first
so
again
just
to
say
reiterate
that
you
know
we're
a
fairly
new
team,
so
we
don't
have
like
a
lot
of
the
maturity
levels
defined
yet
so
we're
in
the
process
of
creating
scorecards,
the
UX
scorecards
and
putting
together
some
discovery
and
research
into
our
user
groups
and
then
just
getting
ready
to.
You
know
iterate
on
that.
A
A
So
this
first
example
of
what
we're
working
on
second
work
in
progress
is
our
overall
name
nomenclature.
So,
for
example,
you
know
in
this
example,
like
you
know
when
you
referred
to
or
when
we
refer
to
like
an
integration
or
webhook
in
the
platform,
it's
different.
If
what,
depending
on
what
level
you
are
within
the
product,
so,
for
example,
if
you're
an
admin
on
the
instance
level
or
you're
at
the
group
level
or
you're
at
the
project
level,
you
know
those
names
are
kind
of
change
and
are
all
over
the
place.
A
The
next
thing
there
are
a
lot
of
different
flows
in
the
in
the
app
that
can
be
either
like
improved
or
optimized
on
so
here's
one
example
and
I'll
just
I'll
just
share
my
screen,
so
you
can
just
gonna
be
easier,
just
show
it
so,
for
example,
right
now,
I'm
on
the
integrations
page
and
I'm
gonna
scroll
down
to
find
my
Jenkins
and
I'm
gonna
set
up
Jenkins
integration.
So
right
now,
I'll
put
in
my
information
here.
Settings
and
I'll
have
this
button
to
test
the
test.
Whether
or
not
the
settings
worked.
A
So
if
I
click
that
as
it's
thinking
I
was
I
as
the
user
I,
don't
really
know
what
happened.
I
was
kind
of
take
it
out
of
my
context,
right
away
so
I
kind
of
assumed
that
I
would
stay
on
that
page
and
then
I
would
you
know
the
forum
would
validate
and
check
whether
it
worked
or
not?
Instead,
I
was
taking.
You
know
back
to
the
integrations
list
page.
A
So
now,
as
the
is
user,
a
little
frustrating
I
have
to
go
back
down,
find
where
I
even
was
what
I
was
doing
even
go
back
to
that
integration,
and
now
I
could
see
that
it
actually
worked
and
I
see
that
the
you
know
the
recent
delivery
worked
here.
So
there's
a
lot
of
little
frustrating
things
that
were
addressing
right
now
within
within
the
integrations.
Let
me
just
go
back
to
that,
so
that
was
that
example.
A
I
also
have
a
little
little
gift
for
that
same
interaction
here,
if
you're
all
curious
to
revisit
that
next
thing,
is
you
know
we,
you
know,
there's
a
lot.
We
want
to
learn
and
a
lot
of
questions
that
were
seeking
answers
to
so
I'm
really
excited
to
be
working
with
Eileen
on
this.
So
our
goal
is
to
create
some
kind
of
process
where
you
know
we
have
an
ongoing
way
of
collecting
feedback
and
kind
of
sharing
that
back
into
into
our
team.
A
So
one
high-level
question
on
the
right:
there
is,
you
know
how
might
or
how
am
I,
how
will
we
make
get
labs
interaction
or
integrations
easier
for
developers?
So
that's
kind
of
a
high
level
question
that
kind
of
can
be
broken
down
in
a
lot
of
little
sub
questions
so
yeah.
So
that's
where
you
are
with
research
so
still
in
the
planning
phase
there.
A
So
next
I
wanted
to
showcase
or
talk
about
you
know
kind
of
some
future
work
and
then,
where
we're
moving
to
down
the
line
and
this
this
this
future
work
really
aligns
well
with
one
of
them.
Can
I
main
product
opt
themes
which
is
you
know,
being
enterprise
ready
or
Enterprise
readiness,
some
moving
down?
So
here's
one
example:
I'll
just
talk
talk
through
this
scenario
here,
so
there's.
Imagine
that
I'm
like
a
Systems,
Administrator
and
I,
was
tasked
with
moving.
A
You
know
our
company
over
to
get
lab
and
let's
say
you
know,
there's
a
lot
of
companies
out
there
that
have
like
more
than
thousands
of
JIRA
projects.
So
let's
imagine
that
your
assistant
administrator,
you
have
20,000
JIRA
projects
that
you
want
to
move
over
to
get
lab.
So
now,
then
imagine
that
you'd
have
to
do
all
that
manually.
You
know
so.
Thankfully
we
do
have
this
concept
of
service
templates.
That
kind
of
can
help
you
with
that.
So
you
could.
A
What
what
that
does
is,
if
you're,
an
administrator
of
the
account
you
could
set
up
a
service
template,
for
example,
for
JIRA,
and
you
input
the
settings
so
every
new
project
that
you
create
from
that
will
be
created
on
that
instance.
You
know,
will
inherit
those
settings.
You
know
that
works
well,
but
the
problem
is,
you
know
so
now.
Imagine
that
you
know
you.
You
have
older
projects
that
you
need
to
update
the
settings
for
or
you
need
an
update,
a
URL
for
now
20,000,
for
example,
different
projects
that
becomes
a
problem.
A
You
can't
you
can't.
We
don't
have
the
concept
of
like
pushing
down
newer
settings
or
updating
settings
and
vice
versa.
You
know
you
if
you're
on
the
project
level-
and
you
only
have
permissions
for
that
project-
maybe
you
can't
you
might
be
able
to
overwrite
those
settings,
and
so
we
want
to
be
able
to
make
it
so
that
if
you're,
if
you're
an
administrator,
you
have
more
control
and
more
granular
control
over
over
these.
A
So,
for
example,
being
able
to
lock
down
the
you
know
the
project
settings
so
the
projects
that
inherit
that
and
if
you
only
have
access
to
know
a
smaller
project
or
group,
you
might
not
be
able
to
override
certain
settings
or
if
you
do
overwrite
them,
we
want
to
notify
the
administrator
that
they've
been
overwritten.
So
there's
a
lot
of
work
and
playing
that
we're
thinking
about
you
know
and
in
this
space,
so
we
have
an
epic
set
up
for
this.
A
next
thing
that
we're
thinking
about
is
over.
Like
what
is
you
know?
A
What
is
the
gitlab
developer
experience?
So
we
have
a
lot
of
influences
that
we
that
we've
looked
at
and
like
first
right,
Tullio,
salesforce
and
a
bunch
of
others
that
have
you
know
great
developer
experiences,
so
we're
working
on
thinking
about
you
know.
What's
what's
the
ideal
get
lab
experience
and
with
that?
That's
all
I
have
really
to
share
for
you
for
this.
You
know
case,
but
I'm
very
excited
to
share
some
more
concrete,
specific
work.
That's
going
to
be
in
production
for
our
next
ux
showcase,
all
right.
Any
questions.
A
Funny
bring
that
up.
We
were
just
actually
talking
about
that
at
a
meeting
earlier,
so
I,
don't
I,
don't
know
where
we're
at
with
that,
but
I
know.
There's
a
team
right
now,
I
think
his
plan,
that's
also
working
on
graph
QL.
So
we
need
to
figure
out
how
we're
gonna
either
work
together
or
who's
gonna
kind
of
own.
That
but
ya
know
I,
don't
I,
don't
have
any
specific
answers
for
you
on
that
cool
thanks.