WEBVTT

00:00:05.210 --> 00:00:08.089
We kind of touched on this too, but I think the

00:00:08.089 --> 00:00:10.130
best thing that data teams and marketing teams

00:00:10.130 --> 00:00:13.029
can do is to work more collaboratively together.

00:00:13.990 --> 00:00:16.629
I think in my experience, I feel like a lot of

00:00:16.629 --> 00:00:19.429
times people who work on data teams, like they

00:00:19.429 --> 00:00:23.589
want to kind of go off and fix and build and

00:00:23.589 --> 00:00:26.929
come back with like the solution. Right. But

00:00:27.239 --> 00:00:29.980
I don't think marketers always know exactly what

00:00:29.980 --> 00:00:32.740
they need or what they're looking for. It's like

00:00:32.740 --> 00:00:35.619
an iteration of seeing the data. So like we might

00:00:35.619 --> 00:00:37.939
ask for something and then we're like, wait a

00:00:37.939 --> 00:00:40.179
second, that doesn't look like how I thought

00:00:40.179 --> 00:00:42.700
it was going to look. There must be something

00:00:42.700 --> 00:00:44.780
else I'm missing. What if we look at it this

00:00:44.780 --> 00:00:50.579
way? And so I think when teams can work very

00:00:50.579 --> 00:00:54.299
collaboratively to not like build, you know,

00:00:55.560 --> 00:00:59.259
this fully baked automated report but to start

00:00:59.259 --> 00:01:01.899
to dig into like what are the questions we really

00:01:01.899 --> 00:01:04.140
need to know and how do we want to answer them

00:01:04.140 --> 00:01:08.260
and how do we want to visualize that and come

00:01:08.260 --> 00:01:11.280
to some sort of agreement before like the full

00:01:11.280 --> 00:01:14.859
mechanics start happening I think I think teams

00:01:14.859 --> 00:01:16.500
can work better because then there starts to

00:01:16.500 --> 00:01:18.359
get this like well that's not what you asked

00:01:18.359 --> 00:01:21.420
for and it's like no it's not sorry can I have

00:01:21.420 --> 00:01:22.239
something else