►
From YouTube: Retro sprint 6 marketing design system
Description
Related epics, issues, and merge requests :
Related OKR: https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/92
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
A
Oh
sorry,
I'm
not
sharing
my
screen.
I'm
still
getting
used
to
this
soon,
zoom
leadership
thing
here:
okay,
there
you
go
so
yeah,
some
things
that
we
feel
went
well,
it's
good
to
well
I'll.
Have
everyone
who
wrote
the
comment
I'll
I'll?
Have
you
read
the
comment
and
then
we
can
read
the
discussion
a
bit
too
so
yeah,
let's
start
with.
B
Tyler
awesome.
Thank
you,
yeah
things
that
really
came
to
mind
about
things
that
went
well
this
sprint
and
we've
got
like
deliverables
and
releases
to
talk
about
in
the
release
video.
So
I'm
just
going
to
focus
on
like
the
the
workflow
that
went
well
and
I
think
that
it
was
awesome
javi,
and
I
really
like
did
some
collaborative
work,
which
was
just
like
very
exciting,
and
it
like
felt
good
to
like
have
that
momentum
and
related.
B
My
next
bullet
point
is
it
also
felt
good
to
we
got
the
new
production
digital
experience,
production
template
a
week
or
two
ago,
and
I
found
that
really
useful.
I
started
making
issues
in
the
growth
growth
marketing
issue
tracker.
I
know
we
probably
still
have
some
discussion
about
like
where
slippers
issues
should
end
up,
but
starting
from
issues
with
good
production
templates
just
made
things
feel
a
lot
better
right.
I
felt
like
I
had
a
good
handle
on
articulating
my
thoughts,
so
I
just
yeah.
B
I
thought
that
a
lot
of
the
workflow
stuff
went
really
well.
The
collaboration
the
iteration
started
to
kind
of
come
together
here.
I
know
someone
commented
on
this.
Oh
yeah.
C
B
And
I
were
just
talking
about
where
to
find
that
and
I
dropped
a
link
or
I
dropped
the
name
of
the
the
template,
and
perhaps
we
can
address
our
own
templates
or
this
sort
of
strategy
in
a
later
sprint.
But
yeah
felt
really
good
about
the
work
done.
This
sprint.
D
A
D
Yeah
yeah,
so
the
pricing
page
went,
live
and
that's
awesome
and
brandon.
You
did
an
awesome
job,
bringing
that
to
life
so
good
job.
Also,
we
got
access
to
some
user
research
tools.
D
Finally,
so
we
have
usertesting.com
now
and
we've
been
I've
been
working
on
that
for
the
last
week
and
a
half
ish
should
also
be
getting
optimal
workshop
starting
around
february
first
so
next
week,
and
this
will
just
give
us
like
a
ton
of
opportunity
to
kind
of
evaluate
our
designs
and
our
development
and
make
sure
it's
actually
working
for
our
users.
That'll,
give
us
great
feedback
and
just
make
our
products
even
better.
D
I
think
yeah
yeah
yeah,
so
thanks
to
a
lot
of
the
pricing
page
improvements
that
brandon
was
coding
out,
I
was
able
to
steal
a
lot
of
his
components
that
he
was
doing
for
buttons
and
for
some
of
the
textiles,
and
a
lot
of
that
was
already
existed.
So
I
was
able
to
update
some
of
the
marketing
pages.
Some
of
those
pages
touch
other
pages
which
are
automatically
getting
updated
as
soon
as
we
have
those
class
names
in.
D
So
I
think
it's
been
really
nice
seeing
how
quickly
these
these
kind
of
global
styles
from
the
design
system
can
take
effect,
and
I
think
stephen
next.
E
Yeah,
just
on
our
storybook
repo,
it's
beginning
to
get
filled
up
a
little
bit
so
we're
beginning
to
see
the
fruits
of
our
labor
and
a
little
bit
more
of
a
showcase.
So
we're
able
to
point
to
this.
If
people
ask
about
it
and
which
is
great-
and
our
working
group
is
also
beginning
to
show
promise,
we
get
everybody
into
the
one
spot.
We
begin
to
think
about
things
and
develop
empathy
for
each
other.
We
see
things
from
other
people's
viewpoints,
which
is
always
fantastic,
especially
when
we're
at
such
an
early
stage.
E
In
developing
a
system
like
this
and
seeing
then
the
foundations
package
that
we've
been
working
on
being
used
on
the
blog,
which
is
you
know,
quite
a
lot
of
pages
that
gets
updated
so
seeing
how
that
looks
as
well
gives
us
the
first
pass,
but
also
having
that
infrastructure
built
in
again
as
well,
which
helps
us
for
any
future
changes
that
may
or
may
not
happen,
and
and
then
I
passed
to
sammy.
C
Thank
you
steven,
so
I'm
gonna
be
talking
about
the
topics
pages
that
I
was
working
on
during
the
last
sprint.
Our
design
system
is
really
really
paying
off
because
I
was
working
on
multiple
pages.
At
the
same
time,
I
think
15
of
them
that
if
I
apply
this
type
to
one
page,
I
need
to
check
across
every
other
single
pages,
so
now
that
we're
using
the
design
system.
If
I'm
doing
anything
about
spacing,
I
already
have
the
first
side
of
eyes.
C
Gonna,
look
like
side
wide,
so
the
iteration
of
those
pages
actually
took
a
long
time,
but
our
design
system
is
really
really
paying
off,
I'm
so
excited
for
the
future.
Thanks
a
lot
to
steven
and
tina
and
everybody
working
on
the
design
system.
In
the
background,
and
for
some
of
us
that
are
writing
clothes
on
the
front
and
everything
is
coming
together
like
a
very
big
puzzle
and
it's
making
a
lot
of
sense
thanks
a
lot
now
straight
to
avi.
F
Thank
you
sami.
I
just
wanted
to
call
out
that
tyler
is
a
monster,
and
what
I
mean
by
that
is
that
he's
a
lot
he's
really
good
at
a
lot
of
the
things
that
I'm
really
bad
at
so
having
him
on.
The
team
has
been
a
blessing
just
because
we
have
someone
to
consult
with
that
kind
of
stuff.
F
I
really
liked
our
ui
office
hour,
just
because
I
had
a
lot
of
very
particular
questions
that
I
wouldn't
bring
up
without
grouping
them
all
together,
just
because
they're,
very
subtle
and
things
that
maybe
we
don't
think
about
on
a
day-to-day
basis.
But
it's
nice
to
get
alignment
on
that
kind
of
stuff,
and
we
have
a
new
system
for
releasing
slippers,
which
is
awesome,
having
semantic
versioning
and
having
more
of
an
alignment
on
what
that
looks.
F
A
Cool
thanks
everyone.
Now
we
can
appreciate
all
the
the
things
that
went
well
during
this
sprint,
and
you
know
it's
always
good
to
see
the
progress.
So,
let's
go
over
next
step.
Some
of
the
things
we
think
we
can
improve
on.
B
Yeah,
I
can
start
this
off.
I
created
maybe
like
three
or
four
issues
over
the
course
of
the
sprint
handful
of
mrs
and
the
templates
were
useful
because
they
prompted
me
to
like
think
about
racy
charts,
but
there
was
a
gap.
B
I
think
part
of
this
is
probably
still
me
being
new
and,
like
you
know,
newt
and
like
us,
the
team
being
new
and
the
working
group
being
new,
but
I
didn't
always
consider
like
when
I
thought
about
racy
like
who
filled
what
letter
right
beyond
folks
that
I
was
directly
working
with.
So
as
an
example
I
was
reviewing,
hobby
was
putting
in
one
of
the
blocks
into
the
slippers
ui
repository.
B
B
For
so,
I
think
just
things
that
we
can
improve
on
is
writing
down
like
figuring
out,
and
it
doesn't
have
to
be
like
formal
racy,
as
we
were
talking
about
this
before
the
recording,
but
like
a
little
bit
about
that
process
that
is
racy
like
and
also
some
place
to
document
who
fills
what
roles
for
that
as
well.
Even
if
it's
kind
of
just
a
loose
framework
or
prompting
questions
to
say,
like
hey,
did
you
consider
pulling
in
these
folks
to
ask
their
opinion
about
this
thing
that
might
affect
them?
B
So
anyways,
that's
on
me
and
I
just
wanted
to
bring
that
up
as
a
thing
we
can
maybe
get
some
clarity
on
moving
forward.
A
Cool,
I
think
jess
has
an
item
up
next.
D
Yeah
mine's
actually
a
little
bit
in
the
same
vein.
So
there's
a
lot
of
last
minute
or
even
after
the
fact
after
we
launched
copywriting
changes
to
our
our
pricing
page
and
we
don't
have
a
copywriter
anymore
since
erica
left,
and
I
don't
know
if
they're
replacing
her
or
that's
going
to
be
a
while,
but
I
feel
like
part
of
the
confusion
around
the
copy
was
like
who
owned
it.
D
There
was
like
a
lot
of
input
from
different
people,
and
it
wasn't
at
least,
I
wasn't
sure
like
who,
in
this,
in
the
vein
of
like
a
racy
like
who
should
we
console
who
should
we
inform
who's
actually
accountable
for
this
in
the
end
so
yeah?
For
me,
there
was
just
confusion
about
like
who
should
be
in
charge
of
the
copy,
and
perhaps
also
we
should
think
about
like.
D
Is
this
something
we
need
earlier
on
in
the
process
like
if,
if
we
do
want
to
consult
other
people
on
a
copy,
we
probably
should
do
it
before
it's
like
already
launched
into
the
world.
So
just
some
things
things
further.
A
Yeah,
I
just
want
to
note
that
we
do
still
have
a
a
you
know:
copy
group
and
a
copywriting
team
and
brie
kind
of
owns,
or
is
the
lead
for
that
sort
of
group.
Now,
as
far
as
I
understand
it,
but
yeah
it's
it's
hard
when
there's
a
lot
of
there
are
a
lot
of
hands
in
the
cookie
jar
that
are,
you
know
wanting
to
make
changes
like
todd
and
sid
and
samya,
and
you
know
product
marketing,
and
you
know
all
these
other
groups
so
but
yeah.
A
It
is
unfortunate
that
you
know
a
lot
of
that
happened
after
the
fact,
and
so
that's
definitely
something
we
can
look
to
improve
upon
next
time
around.
A
And
it
looks,
let's
see
who's
that.
E
Pardon
me
yeah
naming
conventions.
So
definitely,
I
think
understanding
her
nomenclature
across
different
skill
sets
on
the
team
is
probably
a
good
thing
to
get
ahead
of,
so
that
we
know
that
we're
all
speaking
the
same
language.
So
if
someone
calls
something
a
cta,
someone
else
refers
to
it
as
a
button,
and
it's
named
in
different
places
like
that
as
well.
That
doesn't
really
help
the
system
scale
or
become
usable.
So
I
would
like
for
us
to
get
ahead
of
that
and
adopt
different.
E
You
know
there
can
be
different
states
that
can
be
involved
and
as
we
get
into
blocks,
some
of
the
complications
can
kind
of
present
themselves
and
then
so
it'd
be
good
to
have
a
good
practice
before
we
get
to
a
stage
where
we
have
a
lot
of
discrepancies
and
a
lot
of
confusion,
and
then
we
have
to
go
back
and
change
everything.
F
F
Stephen
made
this
awesome
analogy
that
it's
our
get
out
of
jail
free
card,
essentially
for
defending
our
own
decisions.
And
so
I
would
hate
to
be
in
a
position
where
someone
pushes
back
on
something
that
we
release
and
we
don't
have
a
way
of
showing
that
our
work
has
been
thought
through
and
people
have
approved
that
kind
of
work.
F
So
I
just
wanted
to
make
sure
that
we
had
like
something
set
in
place
to
make
sure
that
we're
efficient
in
that
sort
of
way,
because,
like
I
mentioned,
that's,
not
something
that
any
of
us
particularly
like
to
like
to
do
so.
Just
trying
to
be
better
about
that
tyler.
You
have
another
point
on
things
to
improve
on.
B
Yeah-
and
I
think
this
is
tangentially
related
to
just
the
project
management
piece,
and
I
know
that
there's
like
conversations
happening
sort
of
like
they
feel
tied
to
the
cms
sprint
system,
because
lauren
had
been
making
the
issues,
but
I
know
it'll
impact
like
the
scheduling
for
all
the
sprint
systems.
I
had
trouble
this
sprint
and
I
think
I
will,
in
the
continuing
cms
print,
both
like
prioritizing
and
balancing
the
two
working
groups
and
also
like
there's
a
logistic
there's
like
a
cognitive
thing
about,
like
the.
B
I
think
the
alternate
schedules
like
make
sense
right.
It
would
be
a
lot
to
have
two
concurrent
sprints
doing
the
same
things
every
day
but
like
I
I'm
losing
track
of
when
one
starts
in
the
other
end,
because
they
are
like
rolling
into
each
other,
and
I
have
to
like
you.
I
have
to
refer
to
my
calendar
pretty
frequently
to
say
like.
Oh,
no,
no,
like
sprint
planning
for
design
system
is
next
week
and
end
of
sprint
for
cms
is
that
we
right,
like
I'm
kind
of
finding
myself
struggling
there.
B
So
I
hope
that
whatever
changes
michael's
making
to
the
calendar
next
week,
maybe
add
some
clarity
there.
I
know
we've
already
had
discussions
there,
but
that
that
still
came
up
this
week,
for
me,
is
the
the
balancing
both
of
them-
and
I
know
pretty
much
everyone
on
this
team
is
like
taken
work
from
both
working
groups.
So
I
imagine
that
this
is
something
that
we're
all
encountering
in
some
form
you're
right.
A
Cool
so
yeah.
I
think
it's
always
hard
to
balance
all
the
work
in
the
meetings
and
everything
else.
I
I'm
still
pondering
our
meetings
and
how
we
can
improve
them
and
that
sort
of
thing-
and
I
encourage
us
all
to
continue
thinking
about
it,
because
you
know
it's
a
significant
part
of
our
lives
at
work,
so
yeah.
Moving
on
to
the
action
items,
it
looks
like
y'all
have
some
outlined
here
and
I'd
love
to
hear
the
thoughts.
B
B
It
looks
a
little
more
official,
but
it
also
gives
the
organization
control,
like
the
big
thing,
is
making
sure
that
gitlab,
the
company
controls
this
code
base,
because,
right
now
the
package
is
published
through,
like
javi's
npm
account
like
I
have
access,
and
so
I
think
that
there's
some
stuff
we
need
to
do
to
to
get
all
that
back
into
git
labs
hands.
I
think-
and
anyone
correct
me
so,
like
I
signed
up
for
an
npm
account
using
mygitlab.com
email,
and
it
mentioned
something
like
there
was
a.
B
There
was
a
quick
message
when
I
did
the
npm
authentication
in
my
terminal.
That
said,
like
you
have
access
to
the
gitlab
scope
or
namespace.
I
don't
know
if
anyone
here
knows
about
that,
I
can
go.
Do
some
research
async,
but
I
got
to
figure
this
out
next
week.
A
Yeah,
I
think
a
lot
of
that
kind
of
stuff
has
happened
over
the
years,
and
people
have
come
and
gone
from
the
company
and
in
the
early
days
we
didn't
have
a
lot
of
records.
Necessarily
of
you
know,
who's
responsible
for
what
and
that
sort
of
thing
we've
gotten
better
over
time.
But
if
you
have
any
trouble
digging
some
of
that
stuff
up,
you
know
my
my
recommendation
is
to
look
into
the
originating
issues
which
I
I
know
you
did,
and
I
saw
you
ask
for
help
on
one
of
the
questions
channels.
A
In
slack
I
don't
know
if
you
ever
got
a
response
to
that,
but
the
the
second
option
is
to
kind
of
find
out
who
the
account
owner
is.
If,
if
we
have
access
to
that
email
address-
and
you
know,
we
can
kind
of
get
marketing,
ops
involved
or
other
ops
teams
and
see
if
they
can
help
us
recover
accounts,
and
things
like
that.
So.
D
Yeah,
so
mine
is
related
to
that
copywriting
issue,
and
I
was
just
proposing
that
we
actually
create
or
like
when
I
said
copywriting
issue
before
I
mean
like
copyrighted
problem.
My
proposals
would
create
copywriting
issues
for
our
projects,
just
to
keep
track
of
everything.
One
particular
thing
with
the
pricing
page
two
like
as
I
was
designing
it.
There
was
a
lot
of
disparate
copy
things
happening
like
there's
an
a
b
test
that
was
actively
running.
I
think
there
was
one
that
was
already
done.
D
There
were
like
a
couple
of
like
word
docs
that
had
people
had
collaborated
on,
and
I
had
pulled
some
stuff
from
that
and
then,
when
our
page
kind
of
got
built
out,
people
were
like
oh
where'd.
This
copy
come
from.
Oh
it
came
from
over
here
and
it
turns
out
that
wasn't
the
right
copy,
so
just
having
some
place
where,
like
everything
can
be
consolidated
and
someone
owns
it
and
can
like
figure
that
out,
would
be
super
helpful.
So
my
question
also
was
like
who
would
own
that?
I
know
brandon
you
just
mentioned.
D
That
is
it.
Brienne
is
missing
that
right.
Is
there
a
copywriter
yeah?
So
maybe
we
can
work
with
her
on
that,
but
yeah
ideas
too.
A
Yeah,
no,
I
think
it's
a
good
idea
to
have
a
copy
issue.
Unfortunately,
a
lot
of
the
stuff
has
kind
of
been
happening
fast
and
loose
with
the
pricing
project,
but
you
know
certainly
as
we're
doing
research
into
some
of
these
things
yeah.
She
we
we
can
get
help
from
other
teams.
We
used
to
do
copy
issues
a
while
back,
but
they
were
more
of
like
this
page
needs
copy
updated
rather
than
like
a
you
know
that
was
sourced
from
tended
to
be
sourced
from
them
and
then
there'd
be.
A
You
know,
stakeholder
bouncings
and
you
know
hey.
Does
this
copy
work
in
this
spot
on
the
page
or
for
design
or
something
like
that
so
but
moving
forward?
I
think
it's
a
good
idea
for
us
to
source
when
we
have
any
questions
about
copy
as
well
like
an
issue
that
we
can
track
those
decisions
in,
like
I
said
so
or
or
even
we
can
one
of
the
things
that
we've
done
in
the
past.
A
I
don't
remember
if
it
was
my
previous
company
or
this
one
that
I'm
getting
confused
with,
but
you
can
start
by
making
the
suggestion
as
the
ux
person
and
say
hey.
I
think
this
would
be
good,
but
I'm
not
a
cop
copywriting
is
not
my
specialty.
I
don't
know
the
discussions
that
have
been
going
on
around
x,
y
and
z.
You
know,
for
example,
on
the
pricing
page.
We
got
copy
recommendation
from
todd
and
then
there
was
a
review
that
said.
A
Oh
sid
wants
us
to
do
or
likes
to
avoid
certain
terms
or
in
certain
contexts,
or
you
know
so
so
having
that
conversation
somewhere,
like
you
said,
is
a
good
idea,
I'm
starting
to
meander
so
moving
on.
E
F
Some
things
that
I
wanted
to
work
on
myself
personally
is
just
to
try
to
find
insights
from
the
repo
something
that
I've
done
just
as
an
nvc
for
this
sprint
is
just
to
commit
to
downloading
the
csv
that
holds
all
of
our
issues
commits
and
mrs
because
gitlab
allows
you
to
do
that.
So
I've
just
been
pulling
those
in
and
setting
up
a
little
environment
for
myself
that
I
can
work
on
those
and
trying
to
see
if
I
could
find
any
sort
of
insight.
F
I
have
some
questions
that
I've
posed
for
myself
that
I'm
interested
to
discover
more
on
a
deeper
level.
So
I
think
that's
like
a
good
starting
place
for
that
and
just
kind
of
as
time
permits
and
whenever
there's
like
little
lulls
between
work
to
spend
some
time
to
do
that,
because
I
think
that
we
have
a
lot
of
history
and
data,
unknowingly
and
accidentally
from
having
a
repo
that's
been
around
for
so
long,
and
so
many
people
could
collaborate
on.
So
I'm
curious
to
see
if
we
can
deliver
some
insights
on
that
avenue.
F
Something
else
that
I
wanted
to
talk
about
is
just
building
out
the
storybook.
I
created
an
epic
for
adding
elements
and
blocks
to
that
instance,
so
that
we
can
have
that
displaying
across
and
that
can
be
implemented
in
the
right
format
so
that
we
can
start
using
it.
Essentially,
whenever
it's
ready
and
just
looking
about
how
to
look
into
and
then
looking
into
how
css
is
being
used
on
about,
so
that
I
can
just
try
to
see
the
patterns
that
we're
using
and
try
to
bring
some
of
that
over.
F
I
know
we've
been
working
a
lot
on
that
in
the
repo
itself
as
a
kind
of
a
temporary
solution,
and
I
want
to
just
lose
all
of
that
work.
I
want
to
make
sure
that
we
can
bring
it
over
for
things
that
make
sense.
At
least
the
thought
process
would
be
great,
and
I
think
that
would
leave
us
at
a
good
spot.
A
Yeah
and
I
think
some
of
that
sort
of
stuff
we've
been
discussing
in
the
the
recent
ui
to
code
working
group
meetings
with
all
those
questions
like
you
mentioned
earlier
so
and
you
know
recently,
I
updated
the
font
stack
to
kind
of
align
with
those
discussions
which
was
you
know
your
your
tailwind
sort
of
implementation
into
storybook,
so
I
think
we're
moving
in
a
good
direction
there
but
yeah.
I
appreciate
you
taking
the
time
to
look
into
this.
B
I'll
take
excuse
me
last
quick
one
just
following
up
with
michael
about
the
new
calendar
stuff
for
sprint
structure.
I'll
just
make
sure
to
do
that
next
week.
Out
of
a
personal
curiosity
for
clarity
and
also,
hopefully
to
bring
that
bring
the
answers
back
here,
as
we
start
planning
out
next
sprint.
So.
A
Cool
sounds
good
unless
there
are
any
last-minute
thoughts
here,
looks
like
end
of
the
meeting,
all
right
cool
thanks,
everyone
and
where's
that
button.