►
Description
Check out what we accomplished in Growth Marketing this week
A
B
B
And
you
can
see
that
we
are
on
track
for
website
traffic
growth.
Our
goal
is
20
year-over-year,
so
for
new
users.
So
that's
google
analytics
tracks
those
users
for
us,
and
then
we
have
users
year-to-date
and
then
new
users.
So
you
know
right
on
track
with
both
of
those
dropped
a
little
bit
week
over
week.
But
I
think
that's
that's
not
too,
concerning
it's,
not
a
massive
change
and
then,
if
you
you
have
us,
you
can
also
click
on
this
link.
C
Thank
you
for
that
shane.
I
don't
like
following
shane
and
presentations
because
of
his
radio
voice.
I
told
him
he's
lucky,
I'm
not
ursula.
I
would
definitely
steal
his
voice
so
yeah.
This
is
an
opportunity
for
us
to
show
and
tell
what
we've
completed
this
week.
So
I
will
go
ahead
and
pass
it
to.
The
first
looks
like
pear
on
the
list:
siri
and
brie.
D
I
actually
don't
think
suri
is
on
the
call
because
she's
having
computer
issues,
but
I
will
share
in
a
second
that
the
epic
that
I've
created
niall
and
siri
and
I
have
been
working
together
to
basically
come
up
with
better
seo
strategies
and
topic
cluster
organizations,
so
niall
has
created
or
he's
working
on,
creating
an
seo
best
practices
resource
for
the
content
team.
He
hasn't
actually
fully
finished
it.
Yet.
He
also
has
two
tools
that
he's
working
on
and
again
they're
not
finished.
D
So
the
epic
is,
you
know,
a
work
in
progress
still,
but
the
optimization
tools
are
primarily
for
topic
clusters
and
ensuring
that
there's
keyword,
cannibalization,
isn't
happening
and
we're
trying
to
avoid
duplication
of
content
moving
forward
and
also
trying
to
show
figure
out
how
to
include
this
in
the
handbook
and
how
to
document
it.
Do
you
need
to
see
my
epic?
Should
I
share
it
still?
What
do
you
think
I
could.
D
G
Thank
you
so
today
what
I'm
gonna
be
sharing
is
the
devsec
ops
campaign
design.
This
is
my
first
project
with
gitlab,
so
it
was
either
luke
was
gonna,
be
happy
that
he
hired
me
or
very,
very,
very
sad
that
he
hired
me.
The
feedback
has
been
great
we're
moving
forward
with
it.
So
I
think
job
security
is
here
for
at
least
another
week,
so
I'll
just
bring
it
up
on
my
screen.
G
One
second,
so
part
of
the
rationale
for
this
campaign
for
the
theme
was
to
represent
data,
as
well
as
the
people
who
generated
the
data
within
within
a
way
that
that
connects
with
the
gitlab
vibe
but
also
represents
the
community
and
development
and
code.
Part
of
the
interesting
thing
about
these
graphics
is
that
I
actually
use
code
to
create
them
via
the
d3
jquery
library.
So
I
found
an
example
that
I
thought
was
working.
I
tweaked
the
code,
so
I
could.
G
I
could
affect
the
radiating
blob
lobby
circle
things
and
all
that
and
colored
them
made
them
all
dash
you
like
code
and
then
the
intent
was
as
we
get
down
to.
The
next
section
is
to
represent
the
data
with
kind
of
with
data
with
with
code,
so
each
one
of
these
graphics
is
produced
by
code
and
colored
by
us.
You
know
styled
all
put
together.
G
The
iconography
is
the
final
icons
are
being
delivered
by
vic
and
they're.
Looking
great
so
yeah
so
example,
this
one
is
fifty-nine
percent
of
companies
deploy
multiple
times
a
day,
etc.
So
what
I've
done
is
use
59
as
the
number
to
generate
this
graphic
and
it
generates
it
randomly
kind
of
like
a
jellyfish
or
a
tree
or
whatever
nature
does
what
it
does
within.
You
know
some
constraints
so
using
that
to
show
you
know,
data
has
life
to
it.
It's
not
just
code,
it's
not
just
engineers,
it
has.
It
has
a
vibe.
G
It
has
a
feeling
and-
and
all
this
data
was
generated
by
the
community
and
by
by
folks
that
took
the
devsecops
survey,
so
it
felt
like
we
should.
You
know
kind
of
reward
them
for
giving
up
their
time
and
their
possibly
sensitive
information
and
and
give
them
something
that
is,
you
know,
kind
of
fun
to
look
at
something
that
you
know
could
carry
through
possibly
do
another
year,
or
maybe
it's
just
fun
for
this
one
but
yeah
it
was
fun
to
make
and
I'm
looking
forward
to
see
the
the
finished
product.
H
H
Oh,
I
have
to
sorry
I
have
to
go
into
my
security
settings,
but
I
did
include
the
link
in
the
agenda.
So
basically,
if
you
want
to
click
into
the
link,
it's
to
the
pdf,
the
first
link
is
to
the
pdf
that
monica
created
for
our
remote
devops
guide
and
what
we're
doing
or
what
we've
been
working
on
over
the
past
two
weeks
is
updating
the
content
to
make
it
more
valuable
to
devops
practitioners.
H
H
C
Thanks
vanessa,
very
cool
to
see
the
next
iteration
of
the
devops
playbook
taking
shape
and
just
everything
that
everybody's
been
sharing.
It's
super
exciting
today.
I
just
wanted
to
take
a
moment
to
share
some
learnings
and
some
new
tools
and
techniques
that
I
think
we
can
all
use
and
I'll
do
that
talking
a
little
bit
about
the
work
that
I've
done
with
strategic
marketing
and
stephen
on
the
comparison
campaign.
C
C
We
we
get
lab,
wanted
to
basically
iterate
them
and
and
try
to
get
them
to
be
a
bit
more
high
performing
I've
done
similar
work
in
my
prior
role
and
company,
and
so
I
jumped
right
in.
I
just
wanted
to
share
some
of
the
tools
I
used
and
techniques,
because
I
think
we
can
apply
them
to
a
lot
of
our
work.
Not
just
in
design
but
cross-functionally,
so
the
first
thing
I
did
is
I
this
being
a
comparison
effort.
C
C
What
were
the
sort
of
conventional
ways
of
doing
things
across
all
those
sites?
You
know
that
that
just
everybody
seemed
to
be
doing
the
same
thing
so
that
I
could
embrace
those
quote:
unquote:
boring
solutions
under
the
assumption
that
if
a
lot
of
folks
are
doing
them,
it's
for
especially
industry
leaders
that
do
this
exclusively.
C
If
they're
using
them,
then
there's
probably
good
reason
for
that
so
and
I
reached
out-
and
I
asked
folks
to
let
me
know
if
they
had
competitive
sites,
that
they
thought
I
should
look
at.
So
that
was
just
a
quick
sort
of
iteration
zero.
You
know
to
screen
cap
a
bunch
of
other
solutions
and
use
those
to
just
brainstorm
off
of
and
identify
these
industry
conventions
from
there.
C
I
went
ahead
and
I
took
screen
caps
of
the
experience
of
our
experience,
current
state
from
google,
what
it
looks
like
when
I
type
in
things
like
compare
git
lab,
for
example,
the
home
page,
the
home
comparison
page
and
then
the
actual
product
to
product
comparison
pages,
and
I
went
in
and
added
these
notes
in
figma.
Just
noting
where
I
thought
there
was
opportunity
for
improvement
and
why
and
used-
and
once
I
had
done
this
and
again,
this
is
a
very
rapid
effort.
C
Maybe
four
hours
total
up
to
this
point,
then
I
was
able
to
share
both
of
these
with
stakeholders
like
todd
and
others
and
and
share
what
I
thought
and
get
their
thoughts,
both
synchronously
and
async,
and
I
think
the
visuals
really
help
you
know
spawn
a
lot
richer
feedback
and
richer
conversations
from
there.
Are
you
sharing
your
screen?
Are
you
intending
to
share
your
screen?
Yeah,
sorry
about
that.
C
Here's
the
screenshots
of
our
experience
from
google
to
the
home
page
to
the
detail
pages
and
the
notes
that
I
added-
and
this
is
all
linked
from
the
issue
as
well-
just
identifying
opportunities
for
improvement
and
then
meeting
with
stakeholders
and
having
conversations
with
them
about
what
they
see
and
where
they
see
opportunities
for
improvement.
Do
they
agree
or
disagree
with
me
as
they
share
their
feedback?
I'm
adding
notes.
C
You
know
a
low-fi
mvc
of
what
these
comparison
pages
might
look
like
in
the
future
and
then
have
a
quick
discussion
around
those
iterate
that
so
it's
just
these
very
short
bursts
like
hour,
two
hours
of
iterating,
a
lo-fi
design
have
another
conversation.
Another
hour
have
another
conversation,
long
story
short.
C
C
This
is
a
great
way,
I
think,
to
approach
any
solution
have
conversations.
For
example,
we
could
do
this
with
the
devops
playbook.
We
could
do
this
with
landing
pages.
We
could
have
these
sort
of
rapid
design
sessions
with
content,
marketing
stakeholders,
you
name
it.
So
that's
what
I
wanted
to
share
today,
because
I
thought
this
pattern
could
be
applied
to
many.
C
I
I
Okay,
so
yeah,
just
building
upon
what
shane
was
saying
going
from
kind
of
low
fi
to
y5.
I
put
a
link
to
the
design
in
here
and
then
I'll
just
share
it
on
my
screen,
but
this
is
kind
of
building
on
shane's
initial
wires,
we're
starting
these
new
yeah
comparison
pages,
and
essentially
you
know
this
is
kind
of
a
high-five
version
of
that
and
the
goal
is
to
get
to
a
point
where
we
can
scale
it
out
to
any.
I
You
know
any
company
any
platform
this
chart
could
be
three
wide
or
four
wide,
theoretically,
but
anyways
I'll,
just
kind
of
race
through
it
a
little
bit.
But
I'm
trying
to
kind
of
draw
some
visual
interest
to
these
here
and
really
get
eyeballs
on
the
the
differences
and
highlight
kind
of
the
the
scoring
between
these
two
so
I'll
kind
of
scroll
through.
But
these
are
collapsible
tables
and
then
within
the
collapsible
tables.
I
You
know
there's
more
text
available
here.
Just
so
you
know
this
once
it's
live,
this
heading
will
actually
scroll
with
you
down
the
table,
so
you
can
keep
track
of
who's.
Who,
from
there
there's
you
know,
download,
pdf
call
to
action.
This
study
is
actually
by
a
third-party
company,
so
we're
trying
to
highlight
that.
But
it's
not
us
just
saying:
hey
we're
better
than
someone.
It's
actually
a
third-party
company.
I
I
It's
kind
of
a
new
feature,
we're
working
with
another
vendor
to
help
build
out
this
position,
specifically
just
from
a
resourcing
standpoint.
But
again
this
is
kind
of
based
off
shane's
wires
and
then
this
would
we're
essentially
trying
to
build
out
components
throughout
the
site
that
we
could
reuse
anywhere.
So
you
know
a
comparison
table,
a
video
carousel.
I
These
are
not
things
that
we're
just
trying
to
isolate
on
one
page,
but
that
we
could
theoretically
drop
in
anywhere,
so
the
page
is
actually
being
built
where
the
data
comes
in
via
yaml.
So
that
know,
theoretically,
anyone
could
come
in.
Add
this
component
to
the
page
drop
some
content
in
a
yaml
file,
and
then
it
would
kind
of
spit
this
out.
So
again,
there's
just
some
credibility,
boosting
content
on
here,
I'm
to
kind
of
back
up
the
table
and
then
at
the
bottom.
This
is
like
a
sticky
footer.
I
That's
actually
going
to
stay
with
the
user
through
the
whole
page,
so
yeah,
nothing
too
crazy,
but
we're
trying
to
kind
of
streamline
these
designs
like
shane,
said
start
using
kind
of
a
modular
approach
to
building
out
pages
so
that
it's
easier
to
build
pages
rapidly.
You
know
across
the
site,
so
that's
it
from
me.
Let
me
jump
in
here
and
see
who's
next,
luke
I'll
pass
it
to
you.
J
Yep
awesome
thanks
steven.
Let's
see
here
just
want
to
share
one
thing:
I'm
working
on
this
week.
I
can
find
the
right
tab-
okay,
cool
so
hopefully
you'll
kind
of
start
to
see
a
common
theme
here
with
shane
going
before
me.
But
so
this
is
where
I
was
gonna
share
about
the
git
ups
use
case
campaign
or
infrastructure,
as
code
is
kind
of
the
other
name,
so
in
kind
of
sharing
how
we
kind
of
arrive
at
these
concepts
and
generate
them.
J
So
really
rudimentary
kind
of
google
image
search
of
git,
ups
and
kind
of
different
phrases
and
seeing
what
comes
up
so
there's
a
lot
of
kind
of
very
complex
sort
of
diagrams.
As
you
can
kind
of
see,
and
then
you
know
kind
of
diving
into
like
the
infrastructure
component
here,
so
it's
really
kind
of
doing
a
survey
of
what's
out
there.
J
What
others
are
doing,
you'll
see
a
few
that
are
kind
of
more
iconic
and
given
these
campaigns
span
display
banners,
social
email,
landing
pages,
you
have
to
kind
of
consider
all
those
applications
and
specifically
display
banners
and
they're
limited
real
estate.
So
we
kind
of
try
to
go
to
more.
I
can
iconographic
route
with
those
so
obviously
kind
of
these
more
complex,
diagrams
infographics,
don't
necessarily
work.
So
there
wasn't
a
whole
lot
out
there
in
terms
of
get
ops.
J
J
With
the
caveat
of
you
know,
there
will
be
supporting
copy.
That
kind
of
further
strength
strengthens
the
visual,
so
kind
of
keeping
that
in
mind,
so
just
different
concepts
where
here
was
kind
of
like
single
source
of
truth,
which
was
kind
of
a
big
training
for
the
words
but
essentially
kind
of
whittling
down.
J
What
git
ops
is
as
being
a
single
source
of
truth,
so
being
inspired
by
get
utilizing
git
for
that
sort
of
single
source
of
truth
and
kind
of
having
the
infrastructure
not
be
a
separate
part
but
kind
of
integrated
into
the
code
and
sort
of
the
devops
side
of
things
and
how
they
work
again.
Here:
kind
of
getting
metaphorical
with
infrastructure,
kind
of
referencing
construction.
J
So
yes,
that's
what
I've
got
so
from
here,
we'll
kind
of
gain
consensus
from
the
campaign
team
might
iterate
a
little
bit
further,
but
then
we'll
generate
kind
of
final
assets.
That
would
be,
you
know,
like
I
said,
display
banners,
social
landing,
page
ebooks,
the
whole
spread.
So
that's
what
I've
got
and
I
will
throw
it
over
to
monica.
K
K
There's
still
a
lot
of
changes
to
make,
so
I
won't
dive
too
deep,
especially
because
I
think
we're
trying
to
keep
it
like
a
surprise,
but
just
trying
to
bring
that
those
visuals
over
into
the
pdf
and
some
of
the
like
graphs
and
data
that
we
have
going
a
little
deeper
with
those
and
just
laying
everything
out.
But
the
rest
is
secret.
You
can
see
in
the
issue
that's
linked
in
the
agenda.
E
E
So
you
can
see
the
screen
here
so
get
ops
is
sort
of
a
new
area
for
us.
Sarah
kasabian
wrote
a
really
nice
series
of
blogs
late
last
year
about
get
ops
and
so
now
we're
running
a
campaign
on
it.
So
what
we're
trying
to
do
is
really
get
our
name
out
in
the
gitops
space.
So
here
are
some
of
the
core
ideas
that
I
came
up
with
for
messaging
and
william
chia
has
been
really
instrumental
in
coming
up
with.
You
know
some
of
these
usage.
E
Like
some
of
these
words,
I
can
actually
show
you.
There
is
a
handbook
page
that
is
live,
so
I
will
click
on
that
if
you
can
see
it,
so
we
have
we've
been
working
on
the
get
ops
and
is
code
use
cases.
So
this
is
where
a
lot
of
this
language
is
living
right
now
and
we
have
plans
to
create
a
topic
page
for
it.
So
this
is
findable
right
now.
E
So
let
me
go
back
to
this,
so
we
have
basically
four
key
points
with
get
ops
messaging
is
single
source
of
truth,
a
lot
of
git
ops
right
now.
Well,
a
lot
of
infrastructure
is
done
right
now
manually
and
it's
pretty
time
intensive
and
if
you
need
to
make
any
changes,
you
pretty
much
have
to
start
from
scratch.
So
get
ops
provides
a
single
source
of
truth
for
all
of
your
infrastructure,
definitions
and
changes,
and
then
infrastructure
automation.
E
So,
instead
of
manually
doing
infrastructure,
you
know
you
can
do
it
through
us
through
merge
requests,
so
merge
requests.
That
is
the
process
for
managing
infrastructure
and
then
visibility
and
collaboration.
Of
course,
gitlab
is
all
about
visibility
and
now,
instead
of
infrastructure
living
with
this
little
team,
that
just
kind
of
does
it
manually
and
nobody
knows
how
it
works.
Now,
it's
in
a
tool
where
everyone
can
see
how
to
do
it
and
then
repeatable.
E
That's
one
of
the
big
key
points
of
infrastructure
as
code
and
git
ops
is
that
infrastructure
definition
is
codified
and
repeatable.
So
it's
not
just
this
manual
process
managed
by
like
this
little
team
and
they
kind
of
work
in
secret
and
everything's
just
with
them.
So
they're,
like
the
keepers
of
the
truth.
Now
it's
something
that's
accessible
to
everyone
and
also
gitlab
plays
well
with
others.
E
So
we
have
a
tight
integration
with
industry-leading
infrastructure,
automation,
tools
like
terraform
and
ansible,
and
we
are
going
to
be
doing
some
webcasts
with
some
of
these
tools
in
june.
I
believe
so
you
know
really
reinforcing
that
message
that
get
lab
is
a
great
resource
for
doing
git,
ops
and
for
infrastructure
as
code,
so
we're
still
iterating
on
this
and
we're
going
to
be
having
a
topic
page
going
over
some
of
these
concepts
and
putting
that
definition
out
there,
but
really
exciting
stuff.
And
now
we
have
words,
and
now
we
have
visuals.
L
Sure
so
I
will
go
quickly
because
we're
coming
towards
the
end.
We
have
a
handbook
page
for
growth
marketing
right
now.
So
quick
things
to
note
on
here
is
that
there
are
a
lot
of
updates
that
we
need
to
do
throughout
the
handbook.
So
there's
an
epic
that
I
started
so
we
can
put
individual
issues
for
there
and
getting
these
things
organized
the
audience
for
this
page
is
really
outside
of
growth
marketing.
L
We,
how
we're
going
to
communicate
with
people
so
that
they
know
what's
going
on
in
the
stages,
and
it
has
a
few
specifics
for
process
and
just
for
just
for
everybody
to
know
I
put
on
here
that
I
started
a
like
production,
epic,
there's
going
to
be
a
bunch
of
things
in
there,
including
templates
I'm
going
through
issues
right
now
and
kind
of
being
the
bad
cop
and
saying
like.
I
guess
it's
not
bad
cop,
but
asking
for
more
information.
L
So
when
people
send
you
issues
and
they're
really
high
level,
I'm
going
to
be
like
you,
please
clarify
what
the
deliverable
is
here.
Can
you
please
break
this
up
into
multiple
different
issues,
because
we
don't
really
know
what's
happening
here
so
you're
going
to
see
me
doing
that
for
the
next
few
weeks?
So
that's
why?
I'm
in
all
your
issues,
just
trying
to
help
you
guys
get
everything
sorted
in
the
information
that
you
need.
So
I
will
hand
it
off
to
shane
rice.
B
Thanks
meg,
so
my
update's
gonna
be
really
short.
We
made
an
update
to
10
pages
to
add
ctas
that
follow
along
with
use
case
or
mastering
ci
cd.
What
we
did,
though,
is
we
made
sure
that
these
pages
all
have
a
cta
that
ties
back
to
the
topic
of
ci,
so
these
awareness
pages
now
all
have
a
call
to
action
that
sends
people
onto
a
resource
that
matches
the
content
they
started
on.
A
All
right,
this
is
super
quick,
there's
going
to
be
a
product
growth
group
conversation
on
monday
morning.
It's
great!
There
are
partners
in
the
product
side
of
the
house.
So
if
you
can
attend
or
check
out
the
agenda,
async
that
would
be
lovely,
so
becky
take
it
away
to
run
the
shout
outs.
Sure,
okay,.
L
J
Yep
awesome,
becky
I'll
talk
super
fast,
so
quick,
shout
out
to
matt
he's
guaranteed
at
least
two
to
three
more
weeks
here
with
us,
based
on
the
dubstep
officer.
It's
an
awesome
job
there
and
taking
that
on
on,
like
your
second
third
week
and
then
also
monica
and
vic,
for
their
willingness
to
jump
in
on
that
project.
I
thought
it
was
an
awesome
collaboration
and
we
should
definitely
do
more
of
it.
So
thanks
all
three
of
you
appreciate
it
over
to
matt.
G
Great
yeah
thanks
luke,
so
thanks
back
to
you
for
your
help
on
all
this,
thanks
to
luke,
monica
vic,
val
siri,
brandon
and
shane
b.
For
all
the
the
help
this
be
my
first
project,
your
insight
and
feedback
and
turnaround
time
was
was
awesome.
Super
quick
and
I'm
stoked
to
do
another
one.
So
the
next
is
over
to
becky.
L
Sure
I
just
want
to
do
a
quick
shout
out
to
brandon
and
luke,
who
are
we're
already
doing
a
bunch
of
work
on
trying
to
get
a
process
in
place
for
their
teams
and
getting
things
sorted.
It's
really
helpful
and
I've
been
adding
it
to
the
stuff
that
I've
been
doing
and
then
shane
rice
for
helping
me
get
that
handbook
page
up
over
to
erica.
F
Becky,
I
just
want
to
give
a
quick
shout
out
to
val
who
has
been
working
on
this
developer
or
as
we're
calling
it
now
devsecops
report
for
six
or
more
months
now,
but
it
launches
on
monday,
and
it's
just
really
exciting
to
see
all
of
that
hard
work
come
to
fruition
and
everybody
who
collaborated
on
it.
Here
we've
been
running
this
survey
for
about
four
years
and
every
year
it
gets
a
little
bit
better
and
this
year
it
got
a
lot
better,
so
just
really
great
job
to
val
and
the
team
here.
A
C
I
know
there's
a
discussion
underway
around
strategic
marketing
and
what
they
write
and
and
then
content,
depending
on
where
we
are
in
the
funnel.
That's
unfolding,
not
sure
where
that's
landed.
What
I
can
say
is
there
is
a
need
for
content
support.
I
don't
think
it's
a
big
lift.
Most
of
the
content
is
being
the
comparison
content
that
you
saw
in
the
comparison
table
and
then
the
comparison
takeaway,
that's
all
being
authored
by
a
third
party
acceleration
strategies.