►
From YouTube: Practicing "Sophisticated Simplicity"
Description
A design exercise in thinking through how I might apply the tenets of sophisticated simplicity described in https://www.youtube.com/watch?v=lvWPY-b7H4M. Note: the exploration is PURELY CONCEPTUAL and not intended to represent any particular design direction or decisions.
A
All
right,
so
in
a
previous
video,
I
put
together
just
some
thoughts
on
sophisticated
simplicity,
I'll
link
to
that
in
the
description,
but
I
wanted
to
just
put
it
in
practice
and
just
go
through
just
an
exercise,
quick,
purely
an
exercise.
Right
so
caveat,
don't
take
any
of
this
literally.
This
is
just
an
exercise
just
to
show
how
I
might
apply
sophisticated
simplicity
and
the
three
kind
of
tenants
of
that
the
structure,
discovery
and
capability
around
that.
So
I'm
going
to
start
with
just
a
screenshot.
A
So
there's
a
screenshot
just
an
issue:
that's
that
is
what
it
is,
I'm
going
to
just
recreate
that
content
in
a
new
form
and
focus
on
these
things.
So
some
of
the
the
well.
Let
me
back
up
here
my
initial
approach
right.
What
am
I
trying
to
do
here?
I'm
trying
to
to
arrive
at
this
sophisticated
simplicity,
and
I
want
to
do
that
by
not
taking
away
any
capability.
That's
really
important!
As
I
go
through
this
exercise.
A
I
don't
want
to
take
away
anything
from
that,
and
what
I
want
to
do
is
re
rethink,
structure,
so
rethink
organization
how
things
are
set
up.
What
is
the
hierarchy?
What
is
the
relationship
between
content?
Are
there
things
that
are
disparate
hint?
Yet
there
are
on
the
page
that
I
can
bring
together
and
and
then
at
the
same
time,
let's
bring
in
this
discovery
piece.
Are
there
things
that
are
that
could
be
progressively
exposed?
A
Are
there
things
that
we're
showing
today
that
don't
need
to
be
shown
in
a
certain
context,
but
that
are
available
within
one
click
or
one
hover?
I
think
the
answer
is
yes
to
all
that.
So,
let's
just
jump
in
really
quick
here
and
like
I
mentioned,
I
have
a
a
screenshot
here,
oven
of
an
issue
just
to
highlight
a
few
things.
You
know
one
of
the
things
about
our
breadcrumbs.
You
know
granted
that
they
can
be
the
length
of
them
can
be.
A
You
know
long
short,
we
have
methods
of
adjusting
that,
but
we
end
up
with
with
a
lot
of
empty
space
over
here,
because
of
that
and
with
that
you
know,
there's
an
opportunity.
That's
prime
real
estate:
this
is
the
top
of
the
page
and
and
we're
leaving
it
just
sit
empty
next
up.
We
have
these
three
different
calls
to
action,
but
they're
on
two
different
lines:
there's
two
different
treatments:
how
can
we?
How
can
we
synchronize
those
up?
You
know
close
issue
and
edit
issue
they're
at
the
same
level.
A
You're
still
doing
something
to
that
issue
at
a
high
level.
Editing
is
no
less
or
nested
of
a
of
an
item.
Once
an
issue
is
created
right,
it's
they're,
they're
kind
of
on
that
same
plane.
We
have
other
things
in
here.
I
won't
go
into
2d,
but
you
know
underlines
on
headings
that
just
create
breaks
and
then
how
about
this
little
guy
here?
This
is
a
little
piece
of
meta
information
that
just
tells
you
about
when
it's
edited.
A
A
Not
to
mention
get
rid
of
that
here
this
at
the
top.
I
know
this
has
been
part
of
discussion,
but,
having
you
know
three
different
ways
to
to
say
issue
in
the
same
context,
we
can,
we
could
potentially
streamline
that
and
there's
a
lot
more
exploration.
Like
I
mentioned,
this
is
all
just
hypothetical,
just
some
of
my
thoughts
as
I'm
approaching
a
page
and
then
at
this
level
here
there
are,
you
know
one
two,
three
four
pieces
of
information
just
about
the
user
that
created
this
is
that
all
necessary
at
this
level.
A
A
So,
at
the
time
of
the
the
issue
being
created,
this
might
not
even
be
relevant
in
the
same
way.
You
know.
Maybe
this
is
I'm
on
vacation
now
did
I
does
anybody
care
if
I
created
it
before
vacation
or
not
whatever
it
doesn't
matter?
It's
it's
one
of
those
pieces
of
information.
That's
probably
not
necessary
here,
developer
or
not.
A
Does
that
have
any
bearing
on
on
you
know
who
created
it?
Perhaps
I
don't
know
enough
about
that,
but
it
is
one
extra
piece
of
information
as
well
as
the
avatar.
So
when
we,
when
we
take
a
look
at
these
different
elements,
there's
just
a
lot
going
on
and
we
haven't
even
jumped
into
the
the
issue
itself
yet
so
some
other
things
on
structure.
A
I
had
a
conversation
earlier
this
week
about
just
some
of
the
the
weight
and
the
heaviness
on
parts
of
the
page,
and
this
is
the
specific
region
that
is
in
question
here.
If
you
do
kind
of
your
squint
test
this,
this
section
is
very
heavy
with
regards
to
the
rest
of
the
page,
but
it's
supplemental
information,
so
the
visual
weight
of
it
is
is
kind
of
stronger
than
what
we're
talking
about
up
here,
the
I'm
going
to
bounce
around
a
little
bit.
A
A
Those
are
questions,
I'm
sure
have
answers,
but
but,
as
I'm
looking
at
this
just
from
a
high
level,
it's
something
that
that
I'm
considering
so
again
back
to
this
area
here
you
know
we
have
well
one
two,
three
sections
of
of
kind
of
these
appended
items
that
are
all
related
to
the
situat
issue
itself.
Is
there
a
way
to
group
them
and
treat
them
differently?
A
Are
these
related
items
they're
on
the
same
plane,
but
is
adding
a
reaction
really
the
same
as
sorting
you
know
is
that
on
the
same
plane
as
sorting
activity,
I
don't
think
so,
and
so
there's
opportunity
there
when
we
think
about
structure
and
then
these
items
too,
you
know
sorting
filtering,
creating
merge,
requests
they're,
not
on
the
same
plane,
they're
they're,
doing
different
things.
This
you
know
in
particular,
are
related
to
all
this
content
below
this
here
is
related
to
this.
So
why
are
they
together?
A
A
Let's
see
what
parts
of
the
structure
need
to
be
reorganized
and
have
hierarchy
adjusted
so
that
we
can
begin
to
build
out
a
different
experience
all
right,
so
I'm
going
to
jump
over
to
to
just
concept
of
and
walk
through
some
of
the
decisions
and
how
I'm
thinking
about
this
again
take
all
of
this
with
a
grain
of
salt,
it's
not
literal
like
here's.
The
direction
this
is
just
somebody
thinking-
and
this
is
just
an
exercise
right,
so
here
is
a
restructured
page
and
with
that
what
I
want
to
want
to
highlight.
A
I'm
going
to
just
turn
on
some
comments
here,
because
I've
left
myself
some
some
little
waypoint
markers
here,
make
sure
I
catch
up
catch
everything
I'll
just
start
top
down.
Okay.
So
let's,
let's
address
this
prime
real
estate
area.
We
have
this
prime
real
estate
and
I
think
we
can
use
it
better
and
something
I
talked
about
was
consolidating
actions
that
all
relate
to
the
issues.
A
So
I've
done
that
with
edit
close,
merge
and
the
more
now
again,
this
is
conceptual
what
these
things
are,
how
they're
presented
that
can
all
change,
but
leveraging
that
hierarchy
and
leveraging
that
prime
real
estate,
I
think,
has
a
a
ton
of
value,
and
I
don't
think
we
treat
it
as
important
as
we
can
so
in
this
one.
I've
had
some
discussion
on
this
right.
A
This
might
be
where,
where,
if
we
look
back
at
our
venn
diagram,
maybe
this
is
trying
to
be
be
too
discoverable
and
it
needs
to
to
lean
a
little
more
towards
you
know,
exposing
those
capabilities,
and
in
that
regard
you
know
maybe
this.
Maybe
this
goes
too
far
in
simplification
right
today,
there's
you
know
it's
a
it's
a
drop
down
that
you
can
change
what
this
primary
action
is,
you
know,
create
merge,
requests,
create
branch,
etc.
A
You
know
this.
This
could
still
function
the
same
way,
but
is
it
too
hidden
at
this
point
right?
Where
it's
it's
two
clicks,
you
click
this
open.
Then
you
choose
what
you
want
to
do
versus
just
a
single
click,
maybe
maybe
not
regardless
placing
this
option
at
the
top
as
something
related
to
the
the
whole
issue
itself,
I
think,
has
a
ton
of
value
and
it
gets
it
up.
The
page
next
up
is
hierarchy
in
general,
just
a
increased
size.
A
This
is
actually
using
the
32
pixel
size,
which
is
our
largest,
but
we
don't
really
even
use
that
in
the
product
today
and
so
being
able
to
actually
fully
leverage
that
provide
a
little
more
hierarchy
on
the
title,
and
you
notice
that
the
meta
information
now
is
is
below
the
title.
So
it's
subject
to,
if
you
think
of
a
blog
post,
an
article,
the
meta
information
is,
is
typically,
you
know,
after
that,
it's
it's
attached
to
that
title.
Once
you
know
what
that
thing
is.
A
A
This
is
just
a
really
quick
solution
here,
when
we,
when
we
discussed
or
when,
when
we
when
I
discussed
the
the
fact
that
there
were
three
different
elements
here,
the
representing
issue,
this
is
a
way
to
tie
it
together,
along
with
status.
So
it
just
says
open
issue.
This
could
say
open
task,
I
could
say
open
incident,
etc
with
an
icon
that
relates
to
those
things.
It's
a
way
to
do
that
in
a
badge
that
is,
has
some
visual
or
some
some
weight
to
it,
but
also
indicates
status
very
quickly
of
this
item.
A
I
know
that
issues
are
listed
in
breadcrumbs,
but
I
think
that's
a
navigation
mindset,
and
this
is
a
content
mindset,
so
there's
just
two
things
there
where,
yes,
it's
repeated
again
up
here,
but
is
that
really
where
you
want
to
learn
about?
What
type
of
of
thing
this
is
that
you're
viewing?
I'm
not
sure
it
is.
So
that's
why
it's
moved
on
content
itself
using
the
enter
font.
You
can
ignore
all
that.
Suffice
it
to
say.
A
I
have
decreased
the
width
of
this
container
to
have
less
line
length
less
measure
so
that
that
helps
to
increase
readability
when
the
eye
is
tracking
from
one
line
to
the
next
added
some
more
white
space,
remove
the
borders
under
the
headings
etc.
I
know
I'm
going
a
little
fast
here,
but
I
want
to
cover
cover
some
ground
and
some
thinking
so
minor
updates
to
the
copy.
You
know
underlining
links
for
accessibility
purposes
in
the
copy
to
help
them
stand
out.
A
A
A
So
just
in
this
exploration,
just
just
tying
it
up
here
and
thinking
about
what
might
be
more
elegant
way
to
to
do
this,
and
you
know
why
have
just
a
small
strip
of
a
of
a
of
a
touch
target.
Why
not
have
something
a
little
larger,
and
so
in
this
regard
you
know
you're
not
limited
just
to
a
single
target.
You
know
what,
if
you
want
to
drag
something
on
the
page
and
hold
on.
I
gotta
get
back
to
my
my
prototype
here,
but
what
it?
What,
if
you
want
to
actually
have
something?
A
A
A
It's
resetting
that,
where
did
you
go
there?
We
go
okay,
so
so
why?
Why
not
have
a
a
larger
drag
target
where,
where
you
can
drag
anywhere
on
the
page,
instead
of
just
a
simple
item,
so
in
that
way
we
reduce
the
visual
obligation
or
call
to
action
of
this
ability
to
upload
the
designs,
but
at
the
same
time
we
provide
more
affordance
for
doing
so.
A
You
know
so
if
you
want
to,
I
just
have
to
find
where
that
indiv
invisible
element
is
you
know,
so
you
drag
something
on
and
what,
if
the
whole
page
has
an
overlay?
This
is
a
way
to
increase
some
of
the
usability,
but
also
uncover
that
capability
without
having
to
worry
about
just
kind
of
a
single
little
area
to
target,
and
then
in
doing
so,
there's
opportunity
here
to
have
an
illustration
or
something
else
that
actually
highlights
some
of
the
use
case
of
the
design
tool
itself.
A
So
you
can
expose
more
of
that
complexity
in
this
interaction.
So
here
very
simple
illustration,
showing
you
know
kind
of
the
indicators
of
where
you
might
leave
a
comment
on
the
design.
So
it's
just
a
way
to
to
add
a
little
more
to
that
discoverability,
but
also
bring
forth
some
of
the
complexity
that
and
the
features
that
lie
behind
there.
A
A
That
makes
sense
in
the
context
of
the
issue
itself
and
not
drawing
too
much
weight.
The
other
benefit
is
that
it
pulls
up
the
activity,
pulls
everything
else
up
to
the
surface
and
allows
it
to
to
live
there.
So
if
we
go
back
over
to
the
prototype
again,
you'll
be
able
to
just
expand
that
okay.
Okay,
I
see
I've
got
a
linked
issue,
a
merge
request.
Oh
here's
something!
You
know
that
I
that's
not
count
not
counted
here,
call
to
action;
okay,
let's
add
something,
etc.
A
So
none
of
that
functionality
or
that
capability
is
is
gone.
It's
all
there,
but
it's
in
a
way
that
doesn't
require
heavy
visual
treatment,
because
now
what
you've
done
is
simplified
it
and
made
it
where
it's
opt-in,
and
so,
as
the
user
interacts
with
this
they're
they're
exposed
to
this,
they
see
it.
It's
not
something
that
you
have
to
try
to
to
announce
to
them
as
as
as
they're
kind
of
driving
down
the
highway,
and
so
in
that
there's
opportunity
to
clean
these
up.
Simplify.
A
I
fully
know
that
I
have
not
explored
multiple
items
and
listing
and
how
that
would
look,
and
you
know
how
all
that
relates.
Obviously
you
could
have
a
section
for
you
know,
blocks
one
blocked
issue,
one
blocking
issue,
whatever
there's
ways
to
tease
this
out,
so
that
we
can
have
related
items
treated
equally
as
just
all
related
items
and
so
simplifying
some
of
the
meta
here,
etc.
A
A
I
guess
I'll
mention
it
where
we're
combining
reactions
that
do
with
the
content
up
here,
we're
introducing
on
the
same
plane,
drop
downs
that
have
to
do
with
the
content
below
or
introducing
a
primary
call
to
action,
which
has
to
do
things
above
I've
done
away
with
that.
So
activity
is
activity,
you
can
filter
and
you
can
sort
and
that's
what
you
get
and
it's
all
activity.
So
there's
nothing
here
that
is
impacting
what
happens
up
here.
A
Let's
see
here,
okay,
a
few,
a
few
changes
to
the
activity
items
themselves.
Today
we
have
a
lot
of
additional
meta
information.
Again
we
have
the
user
status
and
the
user
handle
in
a
a
system.
Note
I've
removed
that
and
that
can
be
simply
found
by
you
know,
maybe
clicking
hovering
whatever
pop
over
content.
A
It
reveals
that
extra
information-
it's
discoverable,
we're
not
removing
any
of
that
capability,
but
is
it
really
necessary
to
see
my
status
repeated
over
and
over
or
my
user
handle
repeated
over
and
over
keep
in
mind
status
can
change
so
in
the
activity
feed
at
the
time.
I
left
this.
Maybe
I
didn't
have
this
status,
but
because
of
the
way
it
dynamically
updates.
Now
I
do
so,
even
when
you
think
about
it
from
a
historical
standpoint,
it's
not
presenting
anything
accurate
necessarily
it
may
be,
but
it
may
not
so
removing
that
information.
A
If
there
are
other
items,
you
still
see
this
indentation
as
an
indication
of
the
hierarchy
as
it
is
today.
It's
it's
one
kind
of
flat
plane
of
of
of
a
timeline.
This
shows
some
nesting.
It
shows
a
little
more
of
that
that
depth
in
their
relationship,
and
if
you
had
discussions
here,
they
can
nest.
Obviously
you'd
probably
limit
the
nesting.
A
You
know
capabilities
or
or
indentation
amount,
but
you
have
an
ability
to
to
tailor
that
and
and
show
those
relationships
more.
Another
side
note
just
related
to
typography,
is
by
reducing
the
width
of
this.
You
help
with
readability
again
by
not
having
the
line
length
tracked
out
so
far,
and
we
have
the
fluid
layout
option
for
preferences.
A
Let's
see
here
make
sure
I
didn't
miss
anything.
One
thing
I
want
to
call
out
again
is
the
meta
information
rather
than
having
this
in
two
places.
I
just
simply
had
it
in
one.
So
when
was
it
created?
Oh,
when
was
it
edited
I've
added
a
another
user
here,
just
to
show
what
that
could
look
like
it
could
just
say
edited
just
now,
if,
if
I
the
same
person
that
authored
it
edited
it
etc,
but
bringing
that
meta
information
all
into
one
place,
consolidates
it
and
helps
with
that
structure.
A
A
Obviously
this
is
exploration,
but
it
just
shows
that
applying
kind
of
that
that
trifecta
of
the
structure,
discoverability
and
capabilities
when
you
think
about
it
in
that
way,
it
shows
kind
of
some
net
gains
that
you
can
really
achieve
with
a
design
and
when
you
approach
it
holistically,
so
I
hope
this
is
helpful
to
show
how
I'm
thinking
about
it.
I'm
thinking
about
the
ui
and
trying
to
again
this
is
purely
conceptual.