►
From YouTube: Coalesce Pitch: Data as a Product
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi,
my
name
is
Emily.
Sherry,
oh
and
I'm
excited
to
tell
you
about
data
as
a
product.
Like
I
said,
my
name
is
Emily
sherry,
oh
I'm,
an
internal
strategy
consultant
etiquette
lab
I'm,
the
chief
of
staff
chief
I
started
I
get
lab
almost
two
years
ago,
as
our
first
data
analyst
moved
into
a
data
engineering
role
and
today
I
work
on
that
she's,
a
staff
team
in
a
strategy.
My.
B
Name
is
Taylor
Murphy
and
I'm.
A
staff
in
engineering
get
lab,
I
joined,
meet
lab
just
over
two
years
ago.
As
a
data
engineer,
I
managed
the
data
team
for
one
year
and
was
the
manager
who
hired
Emily
and
now
I'm
back
as
an
individual
contributor
on
the
data
team.
As
a
staff
data
engineer,
one
of
the
ideas
that
we've
been
thinking
about
a
lot
is
this
idea
of
zombie
apocalypse
proof
whether
or
not
your
data
teams
output
is
zombie
apocalypse
proof
and
what
that
means
is.
B
If
everybody
on
your
team
are
in
the
company,
we're
turned
into
zombies
overnight.
How
long
could
they
maintain
their
output
for
so
Google?
We
would
think
could
probably
do
this
for
quite
a
while,
maybe
a
month
or
a
week
or
a
month.
But
how
long
do
you
think
your
company
could
survive
for
a
week
a
couple
days?
B
What
about
your
data
team's
reports
and
a
way
to
think
about
this
is
how
many
days
has
it
been
since
the
last
failure
that
you've
seen
whether
from
extraction
and
loading
point
of
view
or
from
some
sort
of
sequel
error
on
your
report?
How
many
days
has
it
been
since
a
failure
that
didn't
work
itself
out
in
the
next
day
and
actually
had
to
do
something
with?
And
we
think
this
is
an
interesting
idea,
because
it
gets
at
a
lot
of
the
underlying
problems
that
data
teams
see
from
data
integrity,
data
quality
data,
reliability,
organizations.
B
A
So
we're
presenting
this
idea
of
data
as
a
product
and
treating
how
you
build
the
things
that
your
data
team
builds
just
like
you
build
your
application,
bringing
in
UX
and
product
management
and
understanding,
not
what
dashboard
or
what
report
or
what
chart
someone
is
asking
for,
but
really
what
is
the
problem
that
they're
looking
to
solve?
Instead
of
giving
your
team
members
faster
horses,
we're
suggesting
you
give
them
cars
today,
most
organizations
think
of
their
data
team
as
a
service
or
a
supporting
function.
A
So
we
care
about
this
problem
a
lot
because
we've
been
there
most
Taylor
and
I
have
pulled
off
incredible
feats
of
heroic
trying
to
keep
things
up
and
running,
and
we
have
deeply
felt
this
pain.
We've
come
to
realize
that
thinking
about
changing
our
own
mindset
has
led
to
an
efficiency
in
the
way
we
work
in
the
way
we
solve
this
problems.
We
worked
on
underperforming
and
undervalued
teams.
A
We're
really
looking
to
to
elevate
all
of
the
data
folks
who
are
working
in
our
sphere,
and
this
is
important
not
just
to
us
as
individuals
but
to
the
greater
community.
The
way
we
think
about
solving
the
problems
that
data
teams
are
facing
today
is
really
going
to
have
a
lot
of
impact
for
a
long
time.
If
we
can
change
mindsets
as
people
move
through
their
career,
we
make
sure
that
these
sorts
of
messages
permeate
across
it
works.
A
The
other
thing
to
note
here
is
that
we
haven't
really
heard
this
idea
thrown
around
that
often
before,
and
we
think
that
colas
is
a
perfect
place
to
get
feedback
on
it.
Why
us
I
mentioned
our
experience
a
cute
lab,
but
we
also
have
over
a
dozen
companies
that
we've
worked
with
helping
build
out
a
data
function.
To
date,
we
watched
get
lab
for
X
and
size
and
we're
active
communities
active
community
members
in
the
data
space,
especially
in
DBT
in
the
DB
T
community.