►
From YouTube: 2022-03-07 Plan/Manage/Ecosystem weekly design review
Description
A
So
thinking,
okay,
how
can
we
simplify
it
rather
than
a
bigger
piece
to
expand
the
pop
over
what
if
there
was
a
boring
solution
that
involved
just
displaying
things
in
the
table?
No
progressive
disclosure
and
so
thought?
Okay,
if
we
just
list
them
all
out,
what
does
that?
Look
like?
Okay,
that's
a
bit
unwieldy!
A
Is
there
some
way
we
can
simplify?
It
is
the
numbers
important
should
they
be
revealed
through
a
popover,
or
do
we
have
a
show
and
hide
mechanism
for
it
and
was
thinking
about
lots
of
these
different
things?
Okay,
what
if
it
they're
all
just
displayed
rather
than
let's
eliminate
the
show
and
hide-
and
I
was
thinking,
oh
okay,
where
what
what
patterns
is
similar
to
this?
What
what
else
is
it
we?
Oh
sorry,
if
we
remove
the
labels,
it's
that
extent
like
too
much
information
again.
A
A
At
the
same
time,
they're
not
always
bound
to
an
order,
and
I
was
just
wondering
if
conceptually
pipelines
end
up
being
like
if
they
need
there
should
be
like
a
level
of
extraction
above
this
sort
of
view
that
says
oh
and
then
there's
an
a
to
a
b
with
distinct
steps.
Here's
how
we
can
display
that
information
and
that's
the
sort
of
distinct
descent
into
our
at
an
abstract
level,
our
pipelines,
this
way
of
visualizing
a
pipeline
and
visualizing
an
import
end
up
being
the
same
thing.
B
Fun,
what
is
really
useful
sort
of
for
us
to
understand
and
judge
like
an
appropriate
approach,
would
be
having
a
better
understanding
of
what
the
job
to
be
done
would
be
and,
like
any
sort
of
user
stories
is
associated
with
it.
So
do
you
do?
Do
you
know
what
the
the
user
user
story
is
or
the
the
job
to
be
done,
and
and
that
that
should
help
us
to
sort
of
better
prioritize?
Whatever
solution,
yeah.
A
A
A
B
Sure,
let's
break
that,
I
just
tried
to
capture
that
so
when
imported
from
github,
I
want
to
know
whether
my
import
is
happening
and
if
it
hasn't
why
and
if
it
hasn't
why
it
hasn't
yeah
it
hasn't
so
that
I
can
so
we
have
like
a
little
bit
of
the
context.
We
have
a
little
bit
of
the
the
action
and,
what's
what's
the
sort
of
outcome
that
we
want
from
this.
C
A
B
Okay,
yeah
so
like
I
can.
I
can
so
that
I
can
start
using
my
project
so
when
importing
from
github,
I
want
to
know
whether
my
import
is
happening
and
if
it
had
and
if
it
hasn't.
Why
hasn't
it,
why?
It
hasn't
that's
grammatically
that
seems
weird,
but
so
that
I
can
start
using
my
project
as
soon
as
possible.
B
If
it
hasn't
so
the
complete
I
mean
from
what
it
seems
right
there
there's
like
two
aspects:
right,
there's
the
the
aspect
where
imports
and
it
just
work
it
works
well
and
then
basically
the
stuff
that
you've
imported.
It's
all
green
checks,
and
you
don't
really.
I
I'm
assuming
you-
don't
really
care
all
that
much
because
you're
like
it's
important,
so
I'm
assuming
it's
all,
it's
all
working
and
then
there's
the
partial
import
where
something
doesn't
work
properly.
And
then
you
need
to
dive
into
the
the
details.
A
I
from
the
I
think,
it's
I
think
I
think
it's
it's
a
sensible
assumption,
but
I
think
it's
a
relatively
risky
one
at
the
same
time,
if
that
makes
sense,
I
think
there's
for
me
there's
a
lot
of
unknowns
about
it,
but
yeah.
I
think
it's
more
important
to
know
which
bits
have
or
haven't
worked
if
it
if
it
hasn't
worked,
so
that
you
can
go
in
and
start
to
fix
any
problems
that
may
have
occurred.
A
B
So,
based
on
that
user
story
of
showing
progress
of
of
of
your
import
or
notifying
you
if
something's
gone
wrong
with
your
import,
we
go
back
to
the
solution
here
and
sort
of
talk
about
like
how
that's
that
sort
of
approach.
How
that's?
How
your
solution
is
sort
of
addressing
that
job
to
be
done
effectively
compared
to
to
other
potential
solutions.
A
Yeah
sure
so
I
think
happy
path
if,
if
we
just
ignore
all
of
these
things,
I
think
this
happy
path
of
just
a
status
can
hit
hit.
The
first
point
that
that
we've
written
in
the
dock
that
the
import
has
happened-
and
it's
worked
well
same
for
this-
it
doesn't
show
but
yeah
the
bits
where
it
lacks
is
showing
progress.
If
we
have,
I
got
a
view,
that's
got
it
so
we've
yeah
like
this.
If
the
viewer
is
just
like
this
or
have
I
got
one
in
progress,
no
yeah.
A
B
So
what
job
touch
me
here
is
like
a
pipeline.
It's
definitely
doing
that
job
of
showing
you
that
there's
progression
happening,
and
it's
showing
you
that
there's
you
know,
steps
in
the
sequence
and
so
on.
Yeah.
What's
missing
here
is
there's
no
immediate
indication
of
like
what
that
step
is.
Apart
from
that
tool
tip
and
whether
you
could
perform
you
could
show
a
little
bit
more
of
a
hint
around
what
that
could
be.
So,
for
example,
could
you
show
some
icons
with
with
issues
and
mrs
and
stuff
in
there?
B
B
A
A
B
B
From
my
experience
with
pipelines,
although
I'm
not
a
proper
developer
or
anything
typically,
I
don't
look
into
them
unless
they've
gone
wrong
and
the
pipeline
experience
is
quite
nice
for
that,
because,
basically,
if
they
they
work
well,
you
just
see
a
green
tick
and
you
you're.
Like
okay,
that's
worked.
I
don't
need
to
worry
about
anything
else.
If
they
go
wrong,
you
get
like
an
annoying
email
message.
Saying
look
at
this:
here's
an
error
message.
B
This
is
where
it's
gone
wrong,
all
that
sort
of
stuff,
so
I
suppose
yeah
experience
right
experience
wise
if
you
want
to
align
it
more.
Similarly,
with
with
pipelines,
it
may
also
be
worth
investigating
not
just
that
little
component
thing
but
like
how
pipelines
potentially
get
you
to
take
action
as
well.
A
A
C
B
A
Have
a
nosey
around
have:
did
any
of
them
stand
out
as
a
oh,
this
this
seems
like
a
really
good
good
angle
to
start
looking
at
for
mvc,
considering
the
original
plan
of
popovers
looks
like
it's
not
going
to
be
not
going
to
be
suitable
or
I
don't.
I
guess,
as
a
follow-on
question
and
that
we
may
be
answered
separately
is
what
what
what
happens
when
how?
How
how
do
we
break
out
of
pajamas
if
at
all,
and
what?
What
does
that
look
like
and
when
is
it
okay?