►
A
Okay,
cool,
so
daniel
mora,
a
product
designer
for
access?
And
today
I'm
going
to
talk
about
groups
and
subgroups
and
the
category
maturity
scorecard
that
we
did
on
those
so
establishing
context
of
the
problem
just
taking
a
while
guys?
How
long
do
you
think
it
would
take
to
build
this
kind
of
org
chart
within
git
lab?
So
we
have
a
couple
of
top
level
and
then
secondary
level
groups
and
then
a
bunch
of
projects
underneath
so
five
respondents
could
not
finish
the
task
in
30
minutes.
A
These
are
all
sort
of
new
gitlab
users,
one
confused
groups
versus
project,
but
they
excavated
the
logic
and
the
architecture
of
the
problem
so
kind
of
work,
but
not
exactly
what
we're
trying
to
go
for.
Only
one
was
able
to
complete
the
task
in
three
minutes
or
less,
and
they
were
pretty
well
knowledged
about
gitlab.
So
a
bit
of
the
problem
we're
seeing
here
is
that
new
user
onboarding
is
a
problem.
New
users
don't
really
have
a
easy
way
of
jumping
in
and
getting
stuff
done.
A
A
The
second
problem
is
sharing.
Objects
is
problematic
due
to
limitations
of
our
architecture,
so
things
that
don't
necessarily
connect
or
don't
make
sense
of
why
they
don't
connect
cross-group
systems
like
I
want
to
share
my
epics
across
different
groups
or
analytics
things
like
this,
that
a
large
organization
might
want
to
have
that
sort
of
insight
into
their
organization.
A
Also
sharing,
as
in
terms
of
inviting
members,
is
kind
of
hidden
for
new
members.
They
didn't
really
understand
how
or
where
to
share
an
object
or
to
invite
new
members
to
the
object
that
they're
trying
to
share
with
so
things
like
bringing
new
members
into
a
project
or
bringing
members
into
a
group
or
sharing
groups
across
different
other
groups.
A
So
we
had
some
recommendations.
Look
what
this
is
it's
the
split
button
like
we
see
again,
so
the
problem
was,
nobody
saw
groups
in
this
drop
down.
They
didn't
even
know
it
was
a
drop
down.
So
in
order
to
get
there
in
order
to
create
a
subgroup,
you
hadn't
know
to
click
on
the
drop
down,
or
at
least
think
about.
Oh
I'm
going
to
click
on
this
drop
down,
so
yeah
sub
projects.
Instead
of
subgroups,
it
was
a
bit
of
a
problem.
A
People
were
making
the
architectural
problem
where
they
would
make
a
project,
not
a
rather
a
group,
and
then
some
people
were
actually
trying
to
come
up
with
creative
solutions
on
how
to
solve
this
problem.
They
wanted
to
go
into
the
terminal
and
start
smashing
out
code
to
try
and
see
if
they
could
build
their
system.
Some
people
thought
about
using
an
import
system
to
try
and
import
a
template
or
some
sort
of
other
method
of
building
their
organizational
structure.
A
So
once
they
got
kind
of
frustrated,
it
wasn't
assuming
that
they
couldn't
figure
out
the
problem
quickly
enough.
They
said
well,
maybe
there's
a
different
way
that
I'm
not
thinking
about
it.
Maybe
I
need
to
import
something
or
do
this
via
the
terminal.
So
this
is
some
of
the
problems
we
had
encountered
with
test
subjects.
A
A
A
So
currently,
what
we
have
done
is
actually
now
live.
We've
split
up
the
button,
so
now
we've
actually
run
another
round
of
cms
testing.
I
did
some
interviews
yesterday
and
the
subjects
were
able
to
do
the
product,
the
task
in
under
two
minutes,
so
it
was
no
big
deal
and
these
are
new
users.
So
this
is
a
good
start.
I
have
a
few
more
interviews
lined
up
during
this
week,
so
this
is
the
initial
mvc
that
we
could
do
really
simple
fix.
Get
rid
of
that
button.
A
The
navigation
concern
is
being
looked
at
across
all
of
us,
our
organization,
there's
a
few
issues
and
epics
that
some
other
folks
have
brought
up
in
regards
to
that
problem.
So
we
know
it's
an
issue
and
we're
trying
to
work
on
that
as
a
team,
which
is
good,
we've
also
been
doing
the
back
end
research,
as
I
discussed
earlier,
about
merging
groups
and
projects
so
within
access
and
within
the
working
group.
I
had
been
a
part
of
previously
where
we
wanted
to
try
and
figure
out
how
we
could
perhaps
merge
groups
of
projects.
A
What's
the
architectural
constraints
on
that,
what's
the
problems
that
we
would
encounter
if
we
were
to
just
smoosh
them
together
and
that's
coming
along
pretty
well,
it
looks
like
we
might
be
able
to
start
bringing
things
over
like
epics
and
issues,
so
that
kind
of
be
would
be
the
first
mvc
for
that
and
yeah.
That's
the
state
of
the
mvc
or
excuse
me,
the
state
of
the
cms
right
now
we're.
B
B
When,
basically
you
didn't,
let
yourself
get
blocked
by
some
big
technical
debt
problems
that
we
know
we
have
and
we're
trying
to
solve,
and
but
those
things
are
like
the
problem
with
groups
and
projects
is
going
to
take
significant
effort
to
solve
kudos
to
you
and
your
pm
for
not
letting
that
make
you
say.
Well,
we
can't
make
it
any
better
for
now.
B
C
To
add
to
that
christy,
I
think
it's
also
worth
considering
the
fact
that
not
everybody
upgrades
their
gitlab
version.
So
at
some
point
in
time
there
might
be
someone
on
this
specific
release
that
doesn't
have
the
new
vision
of
groups
and
projects
and
is
at
least
having
some
small
ui
improvements
that
are
making
them
more
efficient.
So
don't
lose
that
as
well
in
the
mix
of
things.
D
Hey
yeah,
just
a
a
comment
really
in
fyi,
so
the
growth
team
is
working
on
an
onboarding
experience,
they're
actually
calling
it
first
mile
for
smile
is
like
when
you
just
join.
It's
the
whole
experience
from
signing
out
to
getting
into
the
application
logging
in
for
the
first
time
and
actually
doing
something.
So
what
is
that
experience
supposed
to
be
like,
and
one
part
of
it
is
to
somehow
no
solution?
D
A
Yeah
for
sure,
that's
something
that
it
goes
back
to
what
I
was
saying
earlier
about
the
problem
of
that
the
scale
of
ramping
up
a
new
user
is
quite
high
in
our
our
platform,
and
I
think
that
happens
for
all
all
stages
of
the
platform.
And
it's
for
me,
like
I'm
thinking
about
this
as
a
question
of
who
is
our
user?
Is
our
user
gitlab
users
or
is
our
user
new
users
who
don't
necessarily
have
experience
with
the
environment,
and
in
that
the
case
it's
like?
A
D
Yeah
we
can
chat
more,
so
we've
created
a
little
bit
of
a
framework
around
onboarding
that
addresses
different
onboarding
scenarios.
So
onboarding
can
be
a
lot
of
things.
It
can
be
a
brand
new
user
new
to
gitlab.
It
can
be
a
new
user
or
it
could
be
someone
familiar
with
gitlab
joining
a
new
team.
It
can
be
someone
who's
been
using
gitlab
for
a
while
who's,
using
a
new
feature
that
they
haven't
used
before.
D
So
we
have
a
little
bit
of
a
framework
where
we're
kind
of
trying
to
address
all
of
those
different
scenarios
and
kind
of
link
them
together.
So
we
can
have
a
cohesive
set
of
patterns
around
solving
for
those
those
different
scenarios,
but
I
definitely
want
to
hear
all
the
ideas
you
have
around
the
work
we're
going
to
do
with
groups
and
projects,
because
I
think
it
could
be
super
valuable.
My
team
doesn't
have
that
context
that
you
have.