►
Description
Presented by Jarek Ostrowski.
A
Hi
everyone,
my
name,
is
Jarek
Ostrowski
I
am
a
product
designer
on
the
create
team,
I
work
on
design
management
and
wiki.
Today,
I
want
to
talk
about
design
management
because
I
think
it's
a
really
exciting
space
right
now.
For
us,
it's
really
some
it's
it's
growing
and
we're
all
designers.
So
it's
really
cool
to
talk
about
where
we
were
and
then
where
we're
headed.
That's
kind
of
the
direction.
A
I
want
to
go
with
this
presentation,
so
the
knowledge
group
myself
as
a
product
designer
and
a
bunch
of
other
great
teammates
kristen
dubenko
was
is
the
new
product
manager.
She
was
added
a
few
months
ago
and
she's
really
worked
with
me
to
develop
a
stronger,
both
short-term
vision
and
long-term
vision
and
roadmap,
and
it's
been
really
exciting
to
work
with
her
and
all
the
engineers
and
everybody
involved.
A
So
I
want
to
talk
about
the
goals,
so
we
have
the
business
goals
for
design
management.
You
know,
of
course,
designers
are
an
integral
part
of
the
product
development
workflow,
as
we
all
know,
we
work
hand
in
hand
with
developers,
product
managers
to
design
and
develop
great
products.
The
total
market
of
design
tools
right
now
is
over
four
billion
and
growing
it's
almost
every
day.
We
see
a
new
design
tool,
come
out
envision:
five
million
users
sketch
a
million
figma
a
million.
A
It's
unlikely
that
we're
going
to
take
designers
completely
out
of
their
tools.
It's
so
really.
The
emphasis
is
on
you
know
we
need
to
work
with
developers
and
other
stakeholders
that
are
already
and
get
labs.
So
what
can
we
not
substitute
for
them,
but
you
know
build
off
of
what
they
have
and
what
they
need.
When
they're
inside
of
gitlab
customer
to
customer
goals,
I
mean
we're
a
single
application
for
the
complete
DevOps
lifecycle.
We've
all
heard
it
and
it
rings
true
for
all
of
our
product
and
we
all
live
here.
A
Fidelity
was
one
of
the
items
that
was
asked
to
be
in
here
and
that's
sorry.
My
cat
was
just
like
climbing
up
a
wall
or
something
and
fell
down.
I,
don't
know
what
what's
going
on.
So
the
fidelity
is
high
fidelity
because
we
have
the
awesome,
UI
kit
for
our
design
system.
So
it's
easy
enough
to
just
put
buttons
and
components,
putting
these
mock-ups
together
and
we're
trying
to
increase
the
maturity
to
viable.
It's
currently
amenable,
but
this
should
be
increasing
soon,
with
all
of
what
we're
and
I'm
gonna
be
talking
about.
A
Today,
I
also
put
a
link
there
if
you'd
like
to
check
out
the
direction
for
design
management
which
I'll
link
in
the
doc
too
so
sometimes
going
forward
starts
with
a
step
back.
It's
really
about
you
know.
When
I
came
onto
the
design
management
team
last
year,
I
wanted
to
get
a
bigger
picture
of
what
it
was
and
where
we
were
heading.
So
it
starts
with
a
step
back.
A
So
that's
something
we're
focused
on
and
then
everyone
else
all
other
stakeholders
will
view
and
comment
on
designs
and
go
through
that
iterative
process.
So
it's
important
to
separate
personas
and
look
at
each
of
the
features,
saying:
ok,
we're
gonna
focus
on
this
persona
for
creating
reading
and
updating
and
then
others
have
different
needs.
A
So
that
was
really
one
thing
that
I
noticed
was
you
need
to
think
of
it
in
that
way,
when
we're
designing
new
features
and
designers,
don't
work
or
think
like
developers,
which
is
why
I'm
so
confused
by
the
concept
of
yet
for
designers,
I,
it's
it's
just.
We
as
designers
think
differently
than
developers
and
developers
think
differently
than
designers,
and
that's
something
that
we're
thinking
about
too
every
step
of
the
way
so
and
as
I
management.
What
we
started
with
is
its
get
based
under
the
hood,
which
has
its
advantages
and
disadvantages.
A
You
could
upload
PNG
or
JPEG
images
as
designs
and
issues.
You
could
comment
pins
place,
comment,
pins
on
design
and
comment
on
those
designs.
You
could
cycle
through
them
going
to
previous
or
the
next
design
in
that
batch
and
it's
all
under
a
designs
tab
which
started
as
a
interesting
problem
to
have,
because
almost
nobody
knew
it
was
there,
and
here
is
the
best
part.
We
have
the
best
designers
in
the
world
so
and
yeah.
There's
no
picture
here,
because
I
couldn't
fit
us
all
in
one
picture.
A
Yeah
sorry
I've
tried
to
do
something,
but
it
was
taking
too
much
time.
So
the
best
part
is
that
we
can
all
work
together,
we're
all
designers.
We
can
tap
into
our
design
team
to
help
design
and
build
this
tool.
So
here's
an
image
of
a
part
of
an
issue
that
we
created
on
providing
feedback
in
gitlab,
but
also
I've
tried
to
and
I've
spoken
with
a
lot
of
you.
So
thank
you.
A
First
of
all,
for
all
of
you,
who've
spoken
with
us
about
improving
design
manual,
so
we've
been
doing
that
more
and
more
and
that's
been
a
big
emphasis
for
us
to
you
know
ping,
the
UX
team
in
issues
or
on
slack,
and
you
know
we
can
all
contribute
to
making
this
a
great
tool
and
feature
for
all
designers,
including
us.
So
thank
you
for
all
of
you,
who've,
given
feedback
and
I
hope.
We
continue
to
do
that
because
it's
all
something
we
are
using
from
what
I'm
saying.
A
So.
Here's
just
a
couple
of
items
for
feedback
so
far
that
we've
gotten
there's
a
little
bit
of
confusion
around
the
versioning
of
collection,
so
you'll
upload,
a
design
and
you'll
have
now
a
collection,
even
if
it's
only
one
or
two,
and
even
if
you
add
a
single
design,
it'll
create
a
new
collection,
nothing
else,
even
though
nothing
else
changed.
It
considers
that
addition
to
be
a
change,
a
little
create
a
new
version.
There's
a
little
bit
of
confusion
around
this.
A
So
if
you
were
to
go
back
in
time
to
see
different
versions
of
your
designs,
these
are
these
are
versions
of
collections.
So
there's
a
little
bit
of
confusion
here
and
is
a
get
base
to
workflow
right.
You
create
a
branch
you
merge,
it
there's
a
new
version
of
that.
So
there's
been
a
big
refocus
personally
I
want
to
focus
on
individual
design
versions
rather
than
the
versioning
of
collections
themselves.
A
A
Deleting
designs
doesn't
actually
delete.
Yes,
it's
kind
of
interesting
when
we
were
going
down
this
road
and
didn't
realize
that
what
we
were
doing
when
you
delete
is
actually
archiving
so
we're
gonna
be
readjusting
deleting
to
be
archiving
and
looking
into
actually
deleting
designs,
because
who
knows
you
could
have
put
in
some,
you
know
somebody
could
have
put
something
confidential
or
something
accidentally
that
they
want
removed
and
that's
going
to
persist
in
previous
versions,
because
we're
not
actually
deleting
them.
So
that's
something
you
can't
see
the
small
details
and
vertical
design.
A
So
this
is
a
great
example
that
Jeremy
had
put
in.
As
you
can
see,
you
cannot
see
anything
on
that
design,
so
that
was
an
obvious
first
issue.
When
we
were
looking
at
how
we're
gonna
format
designs
when
they
first
load
into
the
view,
so
we
actually
did
just
ship
zooming.
So
in
this
case,
if
you
were
to
go
back
to
that
example
Jeremy,
you
now
have
zooming
where
you
can
zoom
into
those
awesome
icons
that
you
put
together
right
now.
A
You
can't
resolve
design,
so
designs
will
sort
of
just
always
be
there
and
when
something
is
complete
or
resolved,
there's
no
way
to
actually
denote
that
as
resolved.
So
we
went
through
a
long
problem,
validation
issue
around
this
around
design,
reviews
and
approvals.
We
interviewed
about
15
people
during
this
process.
A
Catherine,
who
helped
us
out,
did
a
fantastic
job
and
we
were
looking
into
how
people
review
and
approve
designs,
and
so
we're
currently
working
on
doing
this
in
design
management
and
get
lab,
so
how
we're
focusing
going
forward
really.
My
mindset
and
philosophy
around
this
is
to
look
harder
at
design
tools
as
inspiration,
but
not
as
a
prescription.
I
know.
Sometimes
we
look
at
examples
and
say:
ok,
that's
the
way
to
do
it
we'll
do
it
that
way,
but
in
gitlab
you
know
our
certain
use
case.
A
Designers
have
different
needs,
and
so
you
know
we
want
to
create
a
comfortable
place
for
designers
to
manage
their
designs.
That's
simple
concept:
to
go
by
to
also
utilize
our
design
team,
but
don't
forget
about
other
designers,
because
we
can't
lab,
as
we
all
know,
coming
from
different
companies
before
this.
We
work
very
differently
here
with
issues
and
merger
quests
and
get
lab
itself.
A
Another
emphasis
is
to
focus
on
designers
and
be
designed
first
when
it
comes
to
creating
and
updating
and
deleting
but
don't
overlook
the
other
personas,
because
they
will
also
be
interacting
with
design
management
for
certain
things
and
to
focus
on
details
and
I've
always
been
about
personally
as
a
designer
focus
on
quality
over
quantity.
So
that
means
looking
at
the
existing
features
we
have
and
making
them
the
best
that
they
can
possibly
be
and
not
just
shipping
a
bunch
of
features,
because
we
want
to
pack
more
and
more
into
that.
A
So
it's
really
important
that
we
focus
on
quality,
make
sure
it
works
and
having
good
quality
in
the
design,
manage
future
and,
of
course,
design.
First
mentality,
which
I've
mentioned
so
the
bigger
vision
of
where
we're
headed,
which
is
there's
a
link.
There
is
to
bring
designs
into
review
apps,
which
were
really
excited
about.
This
is
getting
closer
to
the
ultimate
vision
of
the
true
designer
developer,
handoff,
where
a
developer
can
be
in
a
review
app
looking
at
a
staging
environment
and
putting
those
designs
that
were
initially
created
around
that
side-by-side
overlay.
A
We
haven't
really
determined
that
yet
when
that
is
a
vision
that
we're
looking
into
we're,
also
looking
to
integrate
closer
with
UI
design
tools.
If
you
haven't
seen,
Marcel
put
a
great
plug-in
together
for
sketch
plug-in
to
integrate
into
the
design
management
feature,
you
can
select
your
artboards
and
then
use
the
sketch
plug-in
to
directly
import
those
into
the
issue
you
select.
We
also
want
to
make
design
a
first
designer
sorry.
This
is
a
typo,
make
design
our
first-class
citizen
and
then
go
beyond
issues.
A
It's
not
just
about
putting
designs
and
issues
and
then
the
issues
closed
and
then
the
designs
are
gone.
We
actually
want
to
move
beyond
issues
and
make
designs
themselves
yet
lab
wide
and
then
design,
reviews
and
approvals
which
I've
talked
about.
So
if
you
have
feedback
or
an
idea,
there's
a
slack
the
feedback
issue,
and
then
you
can
ping
me
on
either.