►
From YouTube: Workspace iteration discussion
Description
Mike (Product Designer - Editor) and Daniel (Product Designer - Access) discuss concerns around first iteration of Workspaces in regards to navigation and MVCs.
See related epic for more detail: https://gitlab.com/groups/gitlab-org/-/epics/4257
A
Awesome
so
I
I
need
a
little
bit
help
of
understanding.
What's
going
on
between
the
two,
because
yeah
one
of
them
feels
like
it's
a
bigger
thing
and
then,
like
the
other,
one
was
like
a
first
iteration
where
you
only
had
like
users
under
the
admin.
So
I
was
like
one
conversation
is
happening
at
a
really
like
high
high
level,
and
it's
like
I'm
gonna
change.
Admin
completely
and
another
one
is
like
here
is
the
link
so
yeah.
I
couldn't.
B
B
And
as
an
mvc
we're
just
going
to
have
the
users,
so
that's
a
part
of
admin
right,
so
my
problem
is
well.
What
should
the
works,
workplace
or
excuse
me
workspace
be?
Is
it
going
to
be
long-term
thinking?
I
want
it
to
be.
Jesus
thing
has
taken
forever
the
top
nav
excuse
me.
I
wanted
to
be
a
place
where
an
organization
can
go
and
look
and
see
all
of
their
objects,
all
their
groups,
all
of
their
issues.
B
Boards
milestones
et
cetera,
et
cetera,
which
I
was
describing
here
that
we've
had
previous
discussions
about,
don't
necessarily
live
in
a
screen
or
don't
have
a
an
interface
or
an
interaction
point
apart
from
this
menu,
you
don't
understand,
or
we
don't
see
how
they
exist
as
part
of
an
organization.
So
you
click
on
security,
and
it
just
exists
as
security.
B
B
Am
I
setting
myself
up
for
a
problem
in
defining
the
navigation
by
not
creating
an
object
for
that
menu
drop
down
and
saying?
This
is
where
all
these
things
will
exist
in
the
future
and
we're
only
going
to
manifest
overview
users
under
the
admin
drop
down
for
the
time
being,
or
am
I
over
complicating
it
and
that's
kind
of
what
the
proposal
was
or
the
feedback
issue
that
I
tagged
everyone
in
to
see.
Would
that
help
or
would
that
cause
more
problems?.
B
A
A
B
B
B
B
B
B
A
B
Is
that
if
we
do
that?
Does
that
cause
confusion
in
the
future?
So
the
idea
is
that
this
would
be
the
first
iteration.
Second
iteration
we
bring
over
groups
the
next
iteration.
We
bring
over
things
like
issues
whatever,
but
this
is
where
the
problems
start
becoming
apparent
is
because
if
we
look
at
the
current
nav.
B
B
A
B
Yeah
and
that's
kind
of
what
I
I
tagged,
the
plan
team
about
is
like
what
are
they
thinking
about
this?
If
we're
talking
about
this
topic,
how
does
this
logic,
or
this
visual
break
our
environment
or
break
our
navigation?
And
so
that's
so
that's
so
that's
so
that's
so
that's
so
that's
so
that
feedback
from
the
rest
of
the
organization
say:
hey,
am
I
thinking
about
this
wrong?
Am
I
trying
to
go
too
small
of
an
mvc
by
just
doing
this?
B
A
In
the
top,
most
top
left
yeah,
so
I
explored
that
idea
for
this,
where
it
was,
on
the
left,
hand,
side,
yeah,
and
the
reason
I
was
thinking
about
this
was.
I
was
also
thinking
about
you.
Remember
that
other
crazy
navigation
I
had
where
I
had
like
just
the
icons
and
when
you
clicked
on
it
the
whole
panel,
so
it
would
be.
B
A
A
B
A
B
A
Jumped
into
that,
it
would
be
like
here
and
we
did
we
didn't.
We
didn't
make
the
change,
because
we
we
basically
did
the
solution-
validation
for
this-
maybe
like
two
weeks
before
launch-
and
we
were
just
like-
let's,
let's
keep
that
we
can
always
iterate
later.
But
let's
get
some
stuff,
though
feedback
from
customers
and
see
where
we
go
from
here.
B
B
So
I
do
quite
like
this
a
bit.
It
keeps
things
simple.
It's
just
that
we
don't
have
that.
I
haven't
prepared
or
investigated
that
dashboard
or
homepage
nbc,
but
I
do
keep
on
bringing
it
up.
I've
spoken
with
growth
and
I've
spoken
with
the
plan.
Folks
about
that,
because
there's
discussion
about
that,
I
had
you
know
conversation
with
you
a
bit
about
it
when
we
were
talking
about
your
changes
to
the
menu
nav,
the
top
nav.
So
it's
been
something
that's
been
on
my
mind.
A
B
A
Makes
a
lot
of
sense.
It's
like
admin
projects,
groups
usage
on
those
dashboards-
I
don't
know
so
I
feel
like
it.
It's
a
good
place
to
start,
because
the
main
and
the
valley
add
you're
doing
is
like
looking
at
issues.
I
think
there's
a
bigger
question
about
what
that
navigation
is,
and
I
think,
from
a
ux
standpoint.
That's
the
heart.
That's
like
the
conflicting
part
of
your
soul.
Right
now
is
like.
A
A
I
feel
like
that's
the
part.
We're
just
saying.
Did
I
complicate
things
by
putting
this
one
thing
in,
but
I
think
deep
down
that
one
thing
is
actually
pushing
the
right
conversation,
but
maybe
it's
getting
lost
amongst
all
these
other
things
it's
getting
lost
amongst
like.
Is
there
a
navigation
from
top
nav?
Is
it
like
just
a
label
change?
Is
it
just
that,
because
I
think
in
the
position
that
you're
in
you
may
not
have
enough
information
to
say
yeah
we're
doing
this
ibm
cloud
parent
level,
menu
thing.
A
Pm
is
going
to
stay,
no
we're
not
doing
that,
because
we
only
have
so
much.
We
have
a
billion
things
to
do
and
editor
group
is
not
really
taking
on
too
many
new
navigation
things
we're
like
fielding
them,
but
I
think
everyone's
just
waiting
for
foundations
to
take
over
soon,
but
they're
still
hiring
front-end
engineers
and
all
that
stuff
and
getting
their
team
up
to
speed
in
their
pm
to
prioritize,
etc.
So
yeah,
I
think,
you're
in
a
that's,
why
it's
tricky.
A
A
Yes,
yes,
yes,
no!
No,
it
clarified
a
lot
cool
it
also
like
yeah.
A
group
was
thinking
about
because
a
part
of
me
has
always
wanted
to
revert
back
like
the
menu
to
like
projects
and
groups
just
because
of
different
backlashes.
But
people
like
marcel
and
like
my
piano
is
saying
like
like
there
was
one
talk
of
like
consolidating
this
menu
to
like
have
a
single
platform
for
a
high
level
view.
We
actually
achieved
that
because
people
were
like,
oh
it's
easier
to
get
through
these
things,
but
I
never
use
these
things.
B
A
A
A
There's
probably
a
better
way
to
service
them,
and
maybe
like
one
idea
I
had
was
talking
all
of
them
into
another
sub
menu
called
dashboards
and
like
milestone
snippets
and
all
that
would
be
there,
and
that
opens
up
the
space
for
more
useful
stuff,
potentially
but
yeah.
I
don't
know
how
big
workspaces
is
going
to
get
because
from
what
you've
shown
me
with
admin.
It's
huge
right,
like
it's
essentially
parody
of
admin,
right.
B
Yeah
and
think
about
workspaces
as
part
of
the
step
to
re-architect
the
entire
environment,
because
we
want
to
emerge
groups
and
projects
on
the
back
end
in
terms
of
their
technological
behaviors,
to
try
and
reduce
some
of
the
confusion
of
the.
Why
these
things
look
or
behave
differently
like.
Why
can't
I
just
put
issues
in
a
group
or
why
can't
I
just
have.
B
In
one
project,
or
vice
versa,
so
yeah-
this
is
all
part
of
the
problem,
a
lot
of
us
so
access
and
plan
gabe
weaver
has
been
doing
a
lot
of
research
around
this
melissa
ushkov,
my
old
pm.
She
was
doing
a
lot
of
work
around
this
also
but
yeah.
Most
of
the
problem
right
now
is
back
end
stuff
because
we
just
have
to
break
that
technological
debt
and
the
wall
that's
been
defined
there.
B
So
that's
the
real
backlog
for
us
so
which
gives
me
time,
because
I
can
still
investigate
or
play
with
this
before
it
moves
forward.
But
the
workspace
is
the
kind
of
theoretical,
first
iteration,
because
it's
giving
the
environment
a
container
to
say
now
we
can
interact
within
this
environment
in
both
selfmanagedand.com.