►
Description
Alexis Ginsberg, product designer in the Plan stage walks through a scorecard that is being worked on with Katie Macoy, product designer in the Package stage. ✨
A
A
So
for
this
new
user
at
their
organization,
all
packages
must
be
published
from
main
all
packages
published
from
maine
should
always
be
capped.
The
latest
version
of
a
package
should
always
be
kept
all
packages
except
those
protected
from
rules
one
and
two
by
rules
one
and
two
older
than
two
weeks
old
should
be
removed.
All
image
tags
named
latest
should
always
be
kept
all
image
tags
except
those
protected
from
rule
four
by
rule
four
I
keep
saying
from
well,
then
in
two
weeks
should
be
removed.
A
So
I
have
all
these
rules
and
in
order
to
complete
this
scenario
or
kind
of
evaluate
this
job
to
be
done,
I
first
need
to
try
to
determine
the
storage
used
by
items
in
the
packaging
container
registry
and
then
the
total
storage
you
just
used
by
each
registry,
and
I
also
need
to
remove
unused
items
from
the
registries
based
on
my
organization's
rules,
which
are
listed
above
so
katie
did
a
great
job
going
through
that.
For
me,
it
seems
pretty
clear
what
I'm
going
to
do
now.
A
Actually
what
I
already
did,
but
I
will
show
you-
is
a
walk
through
these
scenarios
in
a
test
environment
she's
created
for
me
for
me
and
kind
of
go
through
this
as
a
new
user.
As
I
mentioned
before
and
record
any
insights,
I
I
see
going
through
this
and
any
maybe
frustrations
or
anything
I
think
is
really
great.
Take
note
of
that
as
well,
so
I
will
commence
that
recording
and
then
I'll
come
back
later
to
go
through
scoring
see
you
soon.
A
A
A
A
A
A
A
A
A
A
A
A
Because
it's
the
version
not
necessarily
the
date,
I
think
that
matters,
but
that
might
be
kind
of
confusing
to
me
as
a
non-expert
okay,
so
but
everything,
okay,
the
latest
one
and
everything
from
maine,
but
everything
else,
two
weeks,
older,
okay!
Well,
I
would
keep
this
because
this
is
the
latest
version.
I'm
assuming
this
is.
A
A
A
Before
tags,
sorry
deciphering,
I
guess
I
don't
know
off
the
bat
what
the
tags
means
by
that.
I
guess
like
how
it
ties
to
releases.
I
guess
I
think
just
because
I
come
from
plan
tags
kind
of
mean
something
different
to
me.
So
I'm
like,
oh
and
like
this
looks
like
a
label.
It's
just
the
icon.
I
know
it's
a
tag
icon,
but
they
look
similar
and
they
kind
of
mean
similar
things,
right
label
and
tag.
A
A
So,
okay,
that
makes
sense
all
right,
so
duh
all
right.
So
it's
saying
all
right,
so
I
could
delete
anything
hold
it
in
two
weeks.
Let's
make
sure
yep
these
are
old
in
two
weeks,
so
I
delete
that.
I
like
that
I
can
bulk
select
like
a
little
skeleton
loaders.
I
like
that
you
said
that
was
successful.
Maybe
it
could
be
more
real
time
and
just
have
like
a
toast
right.
Something
like
that.
So
I
think
I
mean
it.
Might
I
don't
know.
A
A
A
A
And
then
I
can't
again,
I
can't
walk
delete
these,
so
I
I
wonder
why,
like
this
pattern,
is
different
than
what's
not
okay,
for
some
reason,
I
don't
remember
seeing
the
trash
cans
over
here.
I
don't
know
why.
Okay,
I
think,
maybe
also
if
you
added
the
like
a
book
or
just
you
know,
like
a
check
box,
you
could
just
add
delete
up.
You
know
somewhere
up
here
right
as
an
option
and
then
have
it
exposed
either
at
all
times
and
like
not
enabled
until
someone
clicks
the
checkbox
or
just
have
it
appear.
A
A
A
I
don't
know.
If
that's
doing
anything
is
it
did
that
copy
something?
Yes,
okay
would
be
nice
to
have
like
a
indication
or
like
so
okay.
I
didn't
see
that
for
some
reason
I
guess
I
wasn't
hovering
long
enough,
but
maybe
when
you
click
it
there's
some
kind
of
indication
that
it
was
copied
right,
maybe
toast
or
just
like
a
little
micro
interaction
here.
A
A
So
maybe,
like,
I
think,
like
overall,
like
more
hover
interactions
like
maybe
knowing
or
not
confidential.
Sorry,
it's
visible.
I
think
that
I
don't
know
what
that
means.
So
maybe
stuff
like
that
would
be
kind
of
helpful,
like
even
like
everything
just
having
like
a
hover
to
understand
what
these,
what
these
items
mean.
Maybe
even
like
this
right,
just
like
say:
oh
it's
a
version
or
you
could
add
like
a
table.
A
A
A
A
A
A
A
Okay,
there's
a
lot
of
information.
I
don't
know
exactly
what
all
of
it
means
and
I
think,
like
more
tooltips
and
stuff
like
that,
it
would
be
a
little
helpful
or
just
some
help
text
and
all
but
again,
I'm
not
someone
who
uses
this
every
day.
So
it's
not
other
people
may
be
a
little
bit
more
educated
in
what
they're
doing
okay.
Oh,
I
see
you
have
like
a
little
bulk
deletion
thing,
which
is
oh
yeah.
I
mean
I
already
use
that,
but
I
like
that.
A
I
wonder
if
this
should
actually
be
like
an
accordion
icon
like
a
chevron,
I
don't
know
because
this
would
to
me
imply
there's
a
menu
right
like
that's,
going
to
pop
out
this
way
that
doesn't
imply
that
I'm
expanding
and
collapsing
so
maybe
using
expanding
claps
instead,
and
something
like
that
like
here
right,
like
that,
makes
me
think
that
there's
a
menu,
that's
gonna
drop
down.
This
makes
me
think
the
money
is
going
to
drop
out
that
way
or
pop
out,
or
I
don't
know.
A
Words
are
hard
right
now
cool,
but
I
couldn't
complete
the
first
part
because
I
don't
have
access
to
settings,
but
I
could
you
know
I
could
complete
the
job.
It's
just
kind
of
frustrating
right
like
I
have
to
manually.
Do
all
this
and
you
know,
gather
the
storage
information
for
each
object,
but
I
could
do
it.
It's
just
frustrating
when
you
don't
have
the
right
permissions
and
the
second
part
with
tags
was
more
straightforward,
but
kind
of
like
a
lot
of
clicks.
A
Page
at
that
level,
maybe
you
could
even
have
like
tags
like
I
don't
know
like
some
kind
of
pop-over
right
and
then,
when
you
click
it,
you
just
see
the
tag
descriptions
and
maybe
you
could
delete
from
there.
I
don't
know-
that's
probably
like
too
risky,
but
I'm
just
trying
to
think
of
ways
to
expose
this
information.
Or
can
you
like.
A
A
So
based
on
the
scenario
we
walked
through
just
a
moment
ago,
I've
recorded
some
insights
here
using
mural
going
through
kind
of
a
sort
of
a
journey
again
as
a
new
user.
So
if
we
go
through
the
stages
that
we
just
went
through
step
by
step,
first,
we
located
the
packages
in
registries.
Basically,
you
know
section
tried
to
find
those
general
areas
that
was
fairly
easy.
You
know
we
have
this,
this
area
called
packages
and
registries
and
then
within
that
is
package
container,
so
that
was
fairly
straightforward.
A
I
did
note
that
maybe
we
can
make
some
kind
of
more
generic
label
here
or
navigation
item
that
encompasses
more
than
just
package
and
container
moving
on.
Then
we
determined
storage
used
by
singular
items
in
the
packaging
container
registry.
So
I
went
to
each
of
those
items
in
the
navigation
and
then
had
to
look
at
each
sub
item.
I
guess
within
each
page,
so
I
went
to
package
registry
and
I
looked
at
those
items
within
there
and
I
had
to
click
into
each
of
those.
A
I
went
into
the
container
registry
and
I
clicked
into
each
repo
and
looked
at
those
image
tags
as
you
can
see
below
or
above,
and
this
was
a
little
more
difficult.
There
was
some
things
I
noted
like.
I
can't
sort
or
filter
by
item
size
within
this
list
view,
so
I
can't
sort
or
filter
the
sizes
of
the
items
within
the
container
and
package
registries.
A
I'm
also
required
to
click
into
each
item
to
view
the
sizes
of
each
of
these
items.
So,
as
you
can
see
here,
I'm
looking
at
root
image,
I
had
to
click
into
that
to
view
all
this
information,
or
here
I'm
looking
at
this,
the
string,
maven
pg.
I
had
to
click
into
that
from
the
package
registry
list
to
to
view
more
information
about
the
size.
So
you
know
maybe
that's
perhaps
more
clicks
than
necessary.
A
A
Also
there's
account
right
next
to
the
titles
of
these
objects.
In
the
list
view
and
again
like
I
can't
interact
with
that
that
count,
it's
just
a
count,
maybe
when
I
hover
on
that
or
click
on
that,
that's
where
some
more
information
could
pop
up
about,
for
example,
what
tags
are
within
this
repo
or
with
you
know,
rather
than
just
saying,
there's
two:
could
it
say
what
the
title
is
things
like
that
what
the
sizes
of
them
are?
A
Maybe
it
expands,
maybe
it's
a
pop-over
who
knows
so
next
up
again,
we
wanted
to
determine
the
total
storage
used
by
each
registry.
This
was
probably
the
most
frustrating
part
of
this
experience
and
I
think
that
it's
partly
due
to
you
know
just
kind
of
like
a
a
case
encountered
within
the
test
environment
set
up
right.
I
don't
know
how
often
users
would
encounter
this,
but
I
wouldn't
assume
never.
A
A
So
I
kind
of
clicked
around
I
looked
at
the
docs.
I
had
to
google
to
find
information
about
this
right.
There
was
no
contextual
data
there
or
docs
link
I
just
had
to
kind
of
google
around,
but
then
the
the
docs
were
helpful,
but
they
didn't
mention
permissions
for
settings,
so
I
was
still
confused.
Why
I
didn't
have
settings.
A
I
tried
looking
in
analytics
because
that
kind
of
made
sense
right,
like
not
related
to
value
stream
but
like
in
analytics.
I
thought,
maybe
I
would
see
something
related
to
registries
here
so
yeah
I
mean
it
was
kind
of
confusing
and
I
could
have
perhaps
calculated
and
aggregated
all
the
data
myself,
but
that
would
be
a
lot
of
adding.
A
A
Maybe
we
could
just
display
the
aggregate
information
right
outside
of
settings.
Definitely,
I
think
that's
something
it
could
be
explored.
I
don't
know
that
it
needs
to
be
tied
to
permissions.
I
mean
I'm
not
really
sure,
but
maybe
that
you
could
do
a
couple
of
those
like.
Maybe
it
doesn't
really
matter
what
level
you
know
what
permissions
you
have
or
where
you
are
in
the
organization.
A
You
could
still
view
that
information.
Maybe
you
have
contextual
guidance
right
like
on
this,
so
instead
of
having
to
google
the
docs,
I
would
have
information
somewhere
somewhere.
That's
like
okay!
Well,
you
have
to
go
to
settings
to
view
this.
I
mean
probably
not
ideal
but
maybe
nbc,
and
I
think
it
would
be
cool.
Maybe
if
you
could
provide
some
tips
on
like
okay,
like
here's
some
items,
you
can
delete,
or
I
don't
know
like.
Oh
you're,
over
your
storage.
A
You
know
like
recommended
storage
or
I
don't
know-
good
storage
hygiene
quote
unquote
whatever
that
means
giving
some
ideas
there,
but
in
general
it'll
tie
into
a
theme
I'm
going
to
mention.
Probably
a
lot
of
like.
Can
you
just
kind
of
surface
this
data
somewhere
within
the
list
like
just
just
show
me
this
data
within
the
package
registry
or
the
container
registry
there's
already
some
great
metadata
and
like
information
surface
there,
so
just
put
it
there.
A
This
was
again
that
was
it
wasn't
hard,
but
it
was
a
little
confusing.
Some
of
it
was
due
to
iconography,
so
the
main
icon
is
the
same
as
the
merge
request
icon.
So
I
think
I
overlooked
it
at
first.
As
you
can
see
here,
it's
not
totally
apparent
what
main
means
right
within
the
ui
and
how
this
relates
to
publishing.
That
was
another
thing.
I'm
kind
of
like
these
look
like
different
pieces
of
information,
but
really
they're
telling
me.
A
You
know
that
they're
part
of
the
same
kind
of
system
so
like
this
is
telling
me
this
is
published
to
maine.
This
is
telling
me
it's
manually
published,
but
I
wouldn't
assume
that
these
pieces
of
information
were
related,
so
that
was
a
little
confusing
and
also
the
icon
for
maine.
It's
different
in
this
view
versus
the
individual
item
view.
So
if
I
clicked
into
this
or
this
one,
for
example,
this
icon
changes,
so
that
was
a
little
confusing
as
well,
so
again
a
lot
around
like
iconography.
A
Well,
that's
probably
a
small
thing
like.
Can
you
create
something
that
users
would
expect
to
see?
Make
that
a
little
more
obvious
and
decouple
it
from
merge
requests?
If
that
makes
sense,
and
then
also
like,
is
there
a
way
to
kind
of
show
that
these
are
similar
right,
manually
versus
main
or
better
tie
publishing
into
maine
like
published
humane?
Maybe
I
could
say
just
changing
that
that
copy
and
then
also
just
a
side
note.
This
is
related
to
import
and
export
this
icon.
A
A
So
we
navigated
to
the
package
registry.
We
sorted
the
list
by
version
which
I
think
was
great.
It
was
a
little
confusing,
like
I'm,
not
really
sure
what
the
logic
is
but
behind
sorting
by
version.
But
that's
I
don't
know
that's
kind
of
a
complicated
thing,
but
I
was
just
wondering
how
does
this
work
across
different
packages
right?
So
what
does
it
mean
if
you
have
three
different
packages
with
a
bunch
of
different
versions?
A
How
do
you
sort
package
a
versus
package
b
by
version,
so
I
don't
know
like
which
latest
shows
up
first,
I
guess
probably
by
publish,
but
I
don't
know
that's
what
I'm
assuming
anyway.
So
then
we
looked
at
the
the
numbers
in
the
list
right
so
first,
I
kind
of
looked
at
these
and
again.
Another
theme
is
that,
like
there's
a
lot
of
things,
you
can't
really
interact
with,
so
I
was
clicking
and
hovering
and
trying
to
figure
out
what
this
meant.
I
was
assuming.
A
It
meant
a
version
right
so,
like
I
just
looked
at
this.
First,
I
didn't
even
look
at
this.
I
didn't
even
look
at
the
batch.
I
was
just
looking
at
these
numbers
and
and
kind
of
like
correlating
latest
version
there,
but
then
I
did
see
the
badge.
The
badge
I
think
makes
sense,
but
I
don't
really
understand
what
is
the
relationship
between
latest
and
experimental?
A
So
next
we
had
some
issues
with
a
lot
of
clicks
when
we
wanted
to
delete
one
or
many
packages
we
clicked
on
the
trash
can
near
a
package
and
we
clicked
to
delete
it,
and
then
we
had
to
say
yes.
So
if
you
had
to
do
that
many
times
that
could
be
really
frustrating,
because
there's
no
bulk,
select
and
delete-
which
I
think
would
be
helpful-
also
irreversible,
like
some
of
the
language
here
was-
could
be
a
little
confusing.
I
don't
know
I'm
probably
being
picky
but
yeah.
A
I
think
we
could
explore
adding
bulk
deletion
things
like
that,
it's
done
elsewhere
in
the
experience.
So
that's
great,
but
this
could
also
help
with
the
repetition
of
the
trash
can
icon
kind
of
getting
rid
of
that
and
then
also
if
we
do
end
up
doing
a
bunch
of
bulk
deletion,
I
mean.
Maybe
you
could
have
some
kind
of
review
experience
like
show
what's
being
deleted
and
the
user
can
configure
it
in
that
modal
and
then
they
delete
all
at
once,
or
maybe
there's
even
like.
A
I
don't
know
an
archive
where
they
can
undo
stuff.
Who
knows,
but
I
think
the
bulk
deletion
is
the
big
thing
there.
Then
things
just
get
better
from
there,
so
we
identify
image
tag,
names
or
titles,
because
we
want
to
look
for
latest
we've
moved
on
to
the
container
registry,
because
we've
already
deleted
the
packages
we
needed.
A
We
click
into
an
image
repo
and
we
view
the
image
tag,
names
or
titles
in
the
list
view
to
find
latest
so
again.
Kind
of
that,
like
show
me
more
context,
thing
so
hovering
or
clicking
on
the
tag
count
it
didn't
display.
Any
information,
didn't
you
know,
show
me
anything
so
like
I
kept
clicking
or
hovering
here
to
see,
maybe
that
that
could
see
the
list
of
names
things
like
that
or
just
any
information
about
what
tags
are
included.
A
I
also
I'll
mention
it,
but,
like
you
know,
could
that
expand
this
section?
Or
can
you
just
list
this
here
somehow
right,
just
so
just
less
clicks
like
do?
I
need
to
click
into
this
to
view
this
information?
I
don't
know
kind
of
again.
This
is
just
me
being
new,
but
the
title
is
container
registry,
but
everything
I
think
is
pertaining
to
image.
Repos,
not
containers
or
I
don't
know
what
container
exactly
means
it
literally.
Is
it
just
a
container
I
don't
know,
but
anyway
it
could
be
confusing
to
less
advanced
users.
A
Like
me,
maybe
some
description,
but
you
know
you
have
this
saying
for
image
repos,
which
is
great,
but
I
had
to
be
like
okay.
I
guess
these
are
image,
repos,
not
containers
or
whatever.
That
means,
because
there's
four-
and
I
experimented
with
this
to
to
see
if
the
the
count
reduced
when
I
deleted
things,
so
that
could
maybe
be
confusing
like
tag
out
icon
again,
iconography,
it
looks
really
similar
to
our
label
icon
and
then
sometimes
we
call
labels
tags.
A
So
that
was
a
little
confusing
to
me
at
first.
I
mean
I
got
it,
but
I
wonder
if
other
people
would
be
confused
by
that
as
well,
so
yeah
we
could
show
more
information
about
tags
when
hovering
or
clicking,
like
I
mentioned,
maybe
better
emphasize
the
list
items
in
our
image
repos
and
that
correlates
with
the
account
and
metadata.
So
like
again,
what
I
was
saying
here
that
these
that's
this
is
talking
about
this
like
that
was
not
totally
clear
to
me
right
that
these
are.
A
This
is
a
count
of
these.
I
don't
know,
maybe
you
can
even
just
group
it
closer.
I
don't
know,
but
I
like
that
you
do
show
the
count,
that's
awesome
and
then
yeah
just
exploring
icons
again.
So
we
get
even
more
happy
here.
We
had
to
identify
the
age
of
image
tags
because
we
want
to
delete
anything.
That's
I
think
older
than
two
weeks
old.
So
we
open
that
image,
repo
we're
viewing
this
publish
date
right
and
optionally.
A
We
can
click
this
to
learn
more
information,
but
I
don't
think
that
would
be
necessary,
but
that's
I
guess
nice.
You
can
do
so
some
of
the
things
here.
I
think
I'd
expect
to
see
all
this
information
again
within
this
list
like
maybe
I
could
expand
something
to
view
that
information
instead
of
going
to
an
entirely
new
location
or
page,
so
just
less
clicks,
and
then
I
could
like
delete
multiple
image
tags
within
multiple
image
repositories
at
once,
like
more
bulk
deletion,
I
guess
so.
A
Yeah,
like
I
said,
takes
many
clicks
of
drilling
down,
so
I'm
drilling
down
a
lot
like
I've
drilled
down
three
times
here
and
then
latest
here
is
in
a
title
versus
the
badge
that
we
saw
in
packages.
So
that's
kind
of
inconsistent.
I
don't
know
why,
and
I
know,
there's
a
reason
for
it,
but
you
know
as
a
kind
of
novice
user.
It
might
be
a
little
bit
confusing
that
the
experience
is
different.
A
So
you
know,
maybe
we
can
explore
surface
surfacing
again
that
tag
information
in
the
list
right,
make
it
more
contextual,
have
it
maybe
expanded
by
default
this
within
the
tag,
so
I
went
in
here
and
I
expanded
this
latest
to
view
more
information
about
it.
I
don't
know
it
doesn't
need
to
be
collapsed.
Maybe
it
does.
A
Maybe
it
doesn't
one
thing
about
the
icon
here
that
again
I
mentioned
that.
Maybe
it
could
be
a
chevron
because
it's
you
know
expanding
collapsing,
it's
not
showing
more
like
a
menu.
I
did
on
how
to
make
the
latest
in
the
case
in
case
the
indicator
is
more
consistent.
Again.
Like
I
mentioned
in
some
places,
it's
a
badge
some
places.
It's
a
title
and
then
yeah.
We
ended
on
a
high
note
that
I
loved
this.
A
Like
bulk
deletion
experience,
he
gave
many
ways
to
delete,
which
I
think
is
great,
so
we
went
in
and
we
had
to
delete
those
selected
tags
right
that
we
identified.
So
I
clicked
on
the
overflow
menu
of
an
older
tag
right
here
right
and
I
click
the
delete
option
or
you
can
select
many
tags
if
you
had
them
or
up
here
right
and
then
say
delete
here,
and
then
you
have
to
confirm
the
delete
deletion
versus
in
that
modal
again
right.
A
I'm
I'm
thinking,
there's
some
constraint
there,
but
just
as
a
note
and
then
clicking
on
each
of
those
repos
again,
you
know
has
a
lot
of
clicks
just
to
delete
these
tags,
which
is
not
a
big
deal,
but
you
know
again
what,
if
you
just
had
all
the
information
about
tags
for
each
of
these
repos
surfaced
within
the
list,
and
I
could
like
pull
delete
here.
That
might
be
interesting.
A
I
get
oh,
this
is
a
nice
one
that
I
like
the
bulk
delete
experience.
There
was
a
lot
of
nice
ones.
I
you
know
I
just
wanted
to
focus
more
on
the
pain
points
that
we
could
potentially
fix,
but
this
is
great
I'll,
just
note
that
and
then
the
alert
thing
and
then
also.
I
think
this
is
a
bug,
but
the
tag
count.
A
Maybe
we
could
do
this
bulk
delete
like
replicate
that
at
a
larger
scale
here
within
the
list
and
then
ideate
on
again,
more
real-time
feedback,
so
maybe
using
a
toast
instead
of
alert.
So
I
don't
have
to
delete
the
alert
and
then
also
making
sure
that
you
know
things
are
updated
in
every
page
to
reflect
the
actions
I
just
took.
A
A
A
You
know
lower
scores
across
this,
so
across
the
board
we
ended
up
with
a
two,
which
is
a
d
I
think,
if
sheesh,
okay,
I
think
if
we
didn't
have
the
problems
around
permissions
and
settings,
this
would
be
closer
to
a
three
or
like
a
c
right,
which
is
fairly
good.
It
doesn't
exceed
expectations,
but
you
know
you
can
get
the
job
done
versus.
This
is
more
of
a
a
poorer
experience,
but
that's
mostly
due
to
those
permissions
again.
A
A
Just
because
it's
it's
very
frustrating
that
I
can
access
some
of
the
features
or
I
couldn't
view
some
of
the
data
I
needed
to
complete
the
job
as
listed.
So
this
would
be
a
d,
but
I
think
there's
some.
You
know
like,
like
I
said
the
the
settings
thing
there's
a
few
things
that
I
think
can
improve
this
greatly
and
I'm
really
excited
to
see
what
y'all
do,
because
I,
I
think,
you're
doing
a
great
job
so
far.
So
thanks
for
listening,
y'all
talk
to
you
later,
bye.