►
From YouTube: Retro: Integrated Campaigns & Design Processes
Description
Integrated campaign retrospective openly discussing design processes, single source of truth, timelines, and DRIs to improve process moving forward. Follow up conversations to come.
FY21 integrated campaigns retrospectives epic: https://gitlab.com/groups/gitlab-com/marketing/-/epics/1097
A
So
yeah
again
thanks
for
joining
just
we
have
30
minutes.
I
want
to
make
sure
we
get
through
everything
but
wanted
to
circle
back
in
terms
of
feedback
from
the
integrated
campaign
process,
to
make
sure
that
everyone's
working
as
cohesively
and
like
on
the
right
timelines
as
possible
in
terms
of
design
requests
where
the
single
source
of
truth
is
any
clarifications.
We
need
to
made
to
the
issue
template
to
make
sure
that
luke
you're
getting
what
you
need
and
what
your
team
needs
from
all
the
individuals
requesting
design
and
creative
assets.
A
A
With
the
growth
marketing
no
just
wanted
to
clarify,
there
was
some
feedback
just
about
making
sure
that
everyone
had
the
right
assets
to
and
making
sure
that
it
was
in
the
timeline
needed
to
be
able
to
execute-
and
you
know
turn
those
around
in
the
required
timeline
so
kristin.
Well,
I
don't
know
if
you
want
to
speak
to
a
little
bit
any
questions
that
you
have
about
the
design.
B
Yeah,
so
on
that
meeting
I
had
just
brought
up
how
in
different
integrated
campaigns,
I
started
to
see
different
formats
of
how
we
request
assets,
and
I
also
think
that
maybe,
like
my
definition
of
what
like
specs,
are,
could
differ
from
others
at
get
lab
like
for
me
for
organic
social
effect
to
me
is
like
an
image
size,
but
I
was
seeing
that
I
was
by
the
same
mpms
being
asked
like
on
multiple
occasions
like
no
like.
We
still
need
the
specs
and
I'm
like,
but
but
these
are
the
specs.
B
C
Yeah
good
point-
and
I
think
we
had
sort
of
like
made
a
shift
like
a
mid,
I
think-
for
the
ci
campaign
or
something
so
originally.
We
had
a
template
where
there
were
for
the
design
requirements.
There
were
tables
within
the
issue
and
that
just
kind
of
created
a
mess.
So
then
we
shifted
to
a
spreadsheet,
but
didn't
really.
I
think
we
went
back
and
updated
the
template,
but
then
others
had
already
created
it
with
the
old
issue,
template
that
makes
sense
yeah.
C
I
think
we
should
be
on
the
same
page
as
far
as
like
I
feel
like
the
spreadsheet
is
going
to
be
a
little
bit
more
cut
and
dry
in
terms
of
like
here's.
The
channel
here
are
the
dimensions
or
specs,
as
you
call
them,
and
then
here's
any
like
copy
cta.
If
that
is
necessary
for
the
design
side
of
things
and
then
who
it's
requested
by.
C
B
D
You
know
the
bar
that
it
needs
to
in
the
exact
opposite
sense
for
organic
social.
We
want
people
and
build
words
and
bold
colors
and
whatever
we
can
do
to
kind
of
draw
out
the
branding
of
things,
because
we
rely
on
it
being
eye
catchy
versus
the
dollars
to
spend
on
the
targeting
side.
So
usually,
what
works
for
paid,
very
simple,
graphics
and
text?
Not
being
on
the
image
is
the
exact
opposite
that
we
need
for
organic.
D
However,
if
we're
linking
to
a
gitlab
owned
page-
and
this
is
not
100
yeah-
because
I'm
still
working
page
by
page
format,
if
we
can
get
the
design
request
to
have
an
open
graph
added
to
be
custom,
an
open
graph
image
customized
into
the
front
matter
of
each
page
that
we're
linking
to
that
image
can
be
created
along
with
the
page
and
by
the
time
the
link
is
live
and
any
other
marketers
that
we're
working
with
are
saying.
Okay,
you
can
go
with
this
now.
D
If
we
have
time
to
you
know
we
have
open
slots
this
week
or
next
week
to
schedule
things
out
with.
We
can
do
so
and
we're
not
waiting
on
the
oh.
This
doesn't
have
a
custom
image
either
we
need
to
create
one
ourselves
which
we
can
do
or
we
need
to
go
back
to
the
design
team
or
somebody
else
to
find
where
the
visuals
may
be
representing
something
that
are
a
part
of
the
campaign,
so
it
wasn't
integrated
marketing,
but
as
an
example.
D
The
devsecops
survey
that
launched
this
week.
Obviously
that
was
a
completely
separate
design
process
and
branding
behind
that
and
all
of
those
visuals.
We
would
not
have
wanted
to
take
our
own
liberties
and
creating
something
if
it
wasn't
going
to
follow
the
visual
branding
that
the
design
team
had
already
put
together.
So
I
think
that
one
open
graph
connection
and
putting
that
in
the
workflow
eliminates
duplicate
asks
needing
to
have
multiple
varieties
of
images,
because
you
only
need
it
in
the
one
size.
D
That
is
a
trying
and
continuous
challenge
because,
as
I'm
learning,
a
lot
of
our
pages
are
formatted
differently
through
both
markdown
html
yaml
files,
and
I'm
learning
a
lot
about
what
these
things
mean
and
how
they
work.
And
some
of
them
don't
have
the
ability
to
pull
that
info.
Yet,
but
it's
in
the
like
it's
it's
capable.
D
D
How
do
we
get
designs
for
organic
to
work
in
this
campaign,
but
more
about
how
do
we
make
sure
that
we
have
it
documented
in
the
way
and
organized
that
for
every
time
another
epic
is
opened
or
a
particular
issue
is
open
to
work
through
this
that
it's
a
part
of
that
existing
workflow?
So
by
the
time
the
link
is
live
when
we
can
go,
we
have
everything
we
need
up
front.
We
don't
have
to
ask
anybody
else
for
additional
assets.
C
Cool.
Okay!
No!
That's
awesome.
Thanks
for
clarifying
the
difference
there,
I
either
overlooked
that
in
some
of
the
campaigns
or
just
thought
they
were
kind
of
one
of
the
same.
So
that's
super
helpful
and
kind
of
getting
a
two
for
one
out
of
the
open
graph,
I
think,
is
awesome
one.
It
looks
better
when
we
share
links
and
then
two
you
know
it.
It
gives
you
that
visual
asset
that
you're
looking
for
as
well
right.
D
D
That
previously
was
not
able
to
pull
meta
data
from
the
front
matter
area
specifically
for
social
sharing
cards,
but
brandon
lyon.
Who's
been
really
a
good
partner
in
kind
of
identifying
what
pages
are
working
and
which
ones
aren't
helped
us
connect
that
on
the
back
end,
I
don't
know
what
he
did,
but
now.
B
E
A
A
Is
that
something
that
we
might
want
to
venture
into
where
the
in
this
spreadsheet
that
we're
using
as
a
single
source
of
truth,
we
have
all
of
those
specs
outlined,
and
it's
a
it's
simply
adding
the
copy
per
campaign-
and
I
say
simply
but
like
that-
could
take
some
time,
especially
diving
through
all
the
messaging,
but
so
that
we
have
these
assets
for
every
every
resource.
That's
onlining,.
B
A
My
internet
is
so
unstable
today,
but
so
repeat
so
it's
like.
Would
it
make
sense
to
have
kind
of
a
package
per
campaign
where
that
single
source
of
truth
spreadsheet
is
it
has
like
the
general
specs
and
specs,
meaning
the
like
the
image
sizes
and
the
resolution
that's
necessary
and
then
it's
a
matter
of
adding
the
copy
for
each
campaign,
so
it's
kind
of
like
a
package
deal.
I
think
I
was
talking
with
erica
about
this
as
well
luke.
I
don't
know
if
you
talked
with
her
about
that
for
each
piece.
A
D
A
Okay,
I
think
I
like
basically
understand
like
when
you
hit
a
social
share.
It's
pulling
some
image,
but
instead
just
any
image,
it
would
choose
if
it's
twitter
it'll
pull
in
twitter.
So
you
have
to
have
that
library
of
images
across
the
platforms
all
right
and
is
it?
Is
it
like
a
package
for
where
you
place
a
code
on
every
landing
page
and
it
pulls
from
a
library,
or
do
you
have
to
manually
edit
each
page
to
say
this?
Is
the
image?
D
So
it
could
be
both
there's
a
lot
right
now
that
I'm
sure
you
see
like
through
slack
it'll,
just
pull
like
the
get
lab
generic
logo
with
like
that.
That
bluish
purple
background.
So
somebody
somewhere
upstream
made
that,
like
the
generic
role
that,
if
it
can't
for
everything,
you
know
a
unique
one
for
this
particular
page
it'll,
pull
that
instead,
which
is
a
good
you
know
safe
haven,
so
there's
at
least
something.
D
But
we
want
to
get
more
granular
and
have
individual
custom
images
per
pages,
especially
when
it's
something
that
we
want
to
link
on
organic
social,
because
we
don't
have
the
ability
like
on
the
paid
side
where
you
can
choose
the
image
individually
different
from
what's
on
the
landing
page.
Because
that's
that's
the
feature.
We
lack
on
organic
that
we
can't
control
for
other
than
if
it's
already
embedded
in
the
page.
D
B
D
And
I
think
it
could
be
either
now
that
I
I
mean
I
have
the
maintainer
rights
for
our
project,
so
I
could
do
that
and
get
it
done.
So
if
somebody
tags
me
with
the
finished
asset,
I
can
immediately
take
that
upload
it
to
the
image
folder.
You
know,
wait
until
that's
merged
and
then
provide
the
url
in
the
front
manner.
So
as
an
example,
I've
done
that
for
we're
doing
that
for
rpr
press
releases
as
well,
because
they
had
no
images
associated
with
them.
Sometimes
we
do
share
them.
D
So
christina
weaver
will
tag
me
in
the
merges
to
add
that
particular
url
to
the
front
matter
so
that
it
pulls
the
social
image
and
again
it
only
takes
a
few
minutes
other
than
for
the
actual
merge
process,
which
we
know
can
maybe
sometimes
take
a
while,
depending
on
what's
on
the
train,
but
it
isn't
a
large
task.
So
I
think
it
is
something
that
I
can
be
assigned
and
be
done
with.
We
just
have
to
make
sure
we're
documenting
that
somewhere.
C
Yeah,
so
I
was
just
commenting
about
sorry,
okay,
okay,
I
was
just
commenting
about
kind
of
the
tag.
Will
whenever
the
open
graph
image
is
there,
so
maybe
we
could
add
that
as
a
component
to
the
design
requirements
issue,
because
I
think
maybe
that's
a
question
for
the
group
too,
like
does
it
work
well
to
collect
the
requirements
in
one
one
issue
and
then
deliver
them
in
the
same
issue?
Does
that
I
mean
it
doesn't
make
a
difference
to
me?
A
Thinking
from
like
a
project
management
standpoint,
I
think
one
challenge
with
this
current
process.
Is
that
and
I'll
admit
like?
I
think
I
created
those
back
in
the
day
so
like
judging
that,
if
we
have
multiple
dris
for
an
issue,
it's
much
more
difficult
to
know
that
whatever
the
delivery
output
is
is
complete.
So
when
we
have
like
seven
people
delivering
their
requirements,
I
think
it
may
make
it
a
bit
more
difficult
or
not
follow
like
best
practice.
A
E
E
B
Yeah,
I
mean
the
other,
I
think
could
be
like.
Obviously
everything
lives
in
the
spreadsheet,
but
it
could
be
like
there's
like
this
like
golden
date
of
like
this
spreadsheet
is
complete
and
the
dri
is
the
one
who
says
hey,
like
all.
The
images
are
complete.
Go
to
this
document
to
find
your
individual
assets.
A
Well-
and
it's
also
that
I
know
matt
you're
using
more
assets
than
just
the
specific
campaign,
landing
page
like
things
that
are
aligned
to
the
campaign,
we're
going
to
use
them.
So
if
you
have
the
ci
use
case
campaign
you're
not
just
going
to
only
drive
to
the
campaign
landing
page,
you
may
drive
to
other
webcasts
that
are
aligned
to
the
use
case.
So
I
don't
know
if
we
also
need
to
just
have
like
if
we
want
to
keep
it
all
in
one
and
just
have
one
single
source
of
truth.
E
A
Yeah,
let's
see,
okay,
let
me
think
okay,
so
going
back
to
what
actually
I
just
had
open
this.
This
is
what
luke
has
created,
which
is
like
this
is
what
he
needs.
He
needs
the
channel
the
dimensions
graphic
copy,
the
cta
button
and
listing
who
who's
requesting
it
so
for
target
one.
I
was
kind
of
curious.
What
is
what
does
the
target
mean
versus
having
like?
Does
that
mean
asset.
C
A
So
what
if
we
have
just
like
I
mean
this
could
get
insane,
but
a
single
google
doc
that
has
every
asset
and
all
of
the
design
requests
and
output
in
one
spot.
So,
for
example
like
where
I
have,
I
think
we
have
like
60
different
assets.
We'd
have
like
60
different
tabs,
or
maybe
we
break
it
out
by
use
case,
but
try
and
try
putting
it
in
a
separate
dock.
A
A
I
know
it's,
I
that's
why
I
was
thinking
if
you
have
the
the
asset
along
the
left,
then
you'd
be
able
to
maybe
have
different
filter
views
for
each
asset
type.
So
if
you
said
the
asset
is,
let's
say,
master
mastering
ci
cd
whatever,
and
you
have
that
for
like
oops,
you
have
that
for
like
the
next
40
requests,
and
then
you
have
modernized
your
ci
cd,
like
I'm
just
using
the
two
that
are
off
the
top
of
my
head
and
you
have
those
across
and
we
have
these
all.
A
A
And
we
have
a
filter
view
for
each
asset
type
aligned
to
the
use
case,
because
typically
we
shouldn't
see
new
assets
being
created
or
new
webcast
being
created
that
don't
align
purpose
driven
to
a
use
case
or
a
partner
or
some
sort
of
integrated
campaign.
I
mean,
I
think,
if
we
have
those
it's
a
one-off
and
we
should
be
avoiding
that
because
it
should
line
up.
But
what
do
you
think
of
that
format
so
that
we
don't
have
40
tabs?
A
I
don't
know
how
many
lines
we
expect
for
each
campaign
type,
but
we
would
have
those
general
hey.
We
have
these
requests
for
every
single
asset
and
that
way,
the
columns
b
through
d
are
package
deals
and
we
know
we
need
that
for
every
asset
and
then
it's
a
matter
of
dropping
in
the
content
copy
and
knowing
who
the
requester
will
likely
be.
A
And
then
I
don't
know
if
I
don't
know
where
you
would
like
to
put
the
asset,
but
I
do
think
it
was
helpful
to
have
a
link
directly
to
where
it
was
in
the
lab
repository
like
for
the
actual
asset.
Look.
I
think
we
did
that
with
some
of
the
old
integrated
campaigns.
I
don't
know
if
that's
still
the
process,
but
I
I
think
we
went
away
for
that
from
that.
For
a
reason,
I
can't
remember.
E
Here,
because
I'm
going
to
have
a
lot
more
assets
than
a
lot
of
people,
so
I
can
see
luke
and
monica
and
whoever
else
spending
a
lot
of
time.
Just
pasting
links
into
this
thing
right.
So
it's
it's
totally
fine
for
at
least
maya
and
just
like
have
a
general
link
like
and
luke
says:
hey
here
are
all
your
assets
in
this
folder
and
then
I
just
go
find
them.
I
don't
know.
I.
E
E
As
far
as
the
spreadsheet
format
like
and
my
preference
is
to
have
separate
tab,
it's
either
going
to
be
like
a
long
spreadsheet
or
it's
going
to
be
a
bunch
of
different
tabs.
So
I
guess
whatever's
easier
for
luke.
I
personally
like
separate
tabs,
because
I
can
just
go
pay
this
this
asset,
but
the
filters
work
too.
D
Question
about
this,
and
I
don't
have
a
particular
I'm
sorry
when
you
hear
yourself
talk,
it's
apparently
an
actual
form
of
torture.
So
I'm
sorry
I
had
to
pause.
I
don't
know
where
it
is
in
the
process
luke,
but
I
wonder
obviously
iterating
on
this
is
important
and
making
sure
it
works
for
your
team
as
more
as
long
as
everybody
else
as
well,
but
I
know
somewhere
on
our
timeline.
D
The
team
is
looking
at
like
an
asset
manager
and
going
through
what
that
might
look
like
and
which
vendors
to
work
with,
and
that
kind
of
thing
is
that
something
that's
probably
happening
this
calendar
year
based
off
of
where
you
guys
are
because
I
think
finding
just
the
right
iteration
on
this
and
knowing
that's
gonna
be
coming
down.
The
line
is
probably
what
our
next
step
is.
If
that's
something
that's
like
in
the
foreseeable
future,
and
if
it's
not,
then
maybe
we
do
keep
working
on
this
every
integrated
campaign
we
have.
D
Maybe
you
know
every
couple
of
months
we
get
back
together
and
figure
out
how
to
make
this
look
right,
because
this
is
obviously
important,
but
I
don't
want
to
throw
that
away.
Thinking
like
we
actually
have
a
digital
solution
where
we're
going
to
have
people
have
logins
and
comments,
and
all
this
other
stuff,
that's
featured
in
those
knowing
that
that's
coming.
C
As
far
as
I
know,
it's
just
kind
of
conversations-
and
I
know
from
shane
bouchard
like
we
were,
we
sort
of
started
to
develop
these
asset
libraries
and
so
we're
doing
those
on
google
drive
and
kind
of
the
ideas
that
we
can
essentially
build
a
case
around
that
that
maybe
that
doesn't
necessarily
work
for
a
number
of
reasons.
And
then
we
can,
like,
I
said,
build
our
case
towards
adopting
some
sort
of
platform.
But
I
don't
really
have
any
idea
on
kind
of
timeline
for
that
at
the
moment,.
D
Okay,
I
mean
feedback
on
that
too.
You
guys,
I
think,
monica
helped
lead
to
the.
It
was
not
tied
to
a
campaign,
an
integrated
marketing
campaign
but
tied
to
just
remote
assets
right
that
you
all
had
put
together,
and
that
was
a
really
at
least
for
us.
It
was
great
to
kind
of
have
this
like
pick
and
choose
library
of
things
to
put
together,
and
I
don't
know
if
there's
maybe
learnings
from
the
way
that
you
guys
did
that
that
we
can
apply
in
this
too
gotcha.
C
A
C
I,
as
long
as
someone
creates
as
long
as
a
filter
gets
created.
I'm
fine
with
that
yeah
I
mean
either
way.
I
think,
like.
I
feel
like
we're
accomplishing
the
same
thing.
It's
just
a
matter
of
like
making
sure
that
I
feel
like
the
filter
is
maybe
a
little
more
hidden,
so
making
sure
that
people
create
that
versus
like
creating
tabs
a
little
bit
easier,
but
yeah
either
way
it's
fine,
because
I
just
get
a
single
view
of
what's
needed
for
that
specific
asset.
So.
B
A
B
E
B
B
D
E
C
A
Yeah,
so
thank
you
for
your
feedback,
I'll
post,
the
recording
into
the
calendar
invite
and
into
this
meeting
doc.
I
think
we
might
want
to
circle
back
on
this.
I
think
there's
a
lot
of
because
this
is
a
really
integral
process
and
we
do
have
two
new
use
cases
coming
out.
They
have
a
lot
less
content,
so
it'll
be
more
like
regimented
over
time,
kristen
how
we
spoke
about.
A
So,
let's
make
sure
that
this
is
like
the
optimal
before
we
move
forward
and
have
it
employed
for
the
get
ops
and
version
control
and
collaboration
collaboration,
integrated
campaigns.
I
might
find
a
quick
some
quick
time
on
friday,
maybe
or
thursday,
and
also
bring
in
the
mpms
that
are
aligned
to
those
case
or
use
cases.
You
get
some
feedback
as
well
I'll
have
them
record
watch.
A
E
C
E
Because
I
know
that's
something
that
we've
talked
about
it's
just
time:
we
haven't
gotten
around
to
it.
So
I
would
like
that
to
somehow
get
incorporated
into
this,
because
I
know
that
npms
have
reached
out
in
the
past
and
said,
like
hey,
let's
test
something,
this
other
message,
so
I
just
want
to
create
a
process
where
we
can
leverage
that
into
what
we're
creating
here
as
well.