﻿WEBVTT

00:00:10.639 --> 00:00:11.651
What?

00:00:11.691 --> 00:00:13.307
They involved you...

00:00:13.426 --> 00:00:15.354
I was gonna get back to them.

00:00:15.473 --> 00:00:16.995
It sounds like Kristi from Marketing

00:00:17.021 --> 00:00:19.855
has been waiting two weeks to hear
back on the report they needed

00:00:19.886 --> 00:00:22.464
to make our corporate
ad buying decisions...

00:00:22.723 --> 00:00:23.613
They missed their deadline.

00:00:23.651 --> 00:00:27.214
Well... I told her when it was ready,
I would let her know.

00:00:27.307 --> 00:00:30.260
Besides, I was waiting on some
new data from Chris

00:00:30.307 --> 00:00:32.104
to run the reports.

00:00:32.207 --> 00:00:34.207
But did you let Kristi know that?

00:00:40.404 --> 00:00:42.979
Great! Another
fire I have to put out.

00:00:43.051 --> 00:00:45.370
Seems like that's my
fulltime job, nowadays!

00:00:45.817 --> 00:00:46.754
You know,

00:00:46.801 --> 00:00:48.270
it never ceases to amaze me

00:00:48.280 --> 00:00:52.274
how we all need to be reminded about
the importance of good communication.

00:00:52.504 --> 00:00:53.354
I get it...

00:00:53.385 --> 00:00:54.698
delays happen.

00:00:54.732 --> 00:00:56.732
But Steve needs to understand

00:00:56.742 --> 00:00:59.635
that the lack of communication
can cause disruptions that...

00:00:59.660 --> 00:01:02.073
honestly... none of us need.

00:01:02.598 --> 00:01:03.464
No.

00:01:03.551 --> 00:01:05.245
No, I did not.

00:01:05.982 --> 00:01:07.698
It was on my list of things to do,

00:01:07.709 --> 00:01:10.932
but I got bogged down handling
all the new accounts.

00:01:11.051 --> 00:01:13.745
You do a great job with
our external clients.

00:01:13.863 --> 00:01:15.863
But we have internal customers, too.

00:01:16.122 --> 00:01:18.510
Well... I... I... couldn't do anything
about the delay.

00:01:18.552 --> 00:01:20.461
Oh, I'm not questioning that but...

00:01:20.577 --> 00:01:23.312
When that happens, we need
to be communicating internally...

00:01:23.323 --> 00:01:25.042
as well as we do externally.

00:01:25.211 --> 00:01:26.354
When we don't,

00:01:26.392 --> 00:01:27.604
that's when we get
the kinds of issues

00:01:27.636 --> 00:01:29.714
that Kristi and her team
brought to me.

00:01:30.442 --> 00:01:31.729
Makes sense.

00:01:32.004 --> 00:01:34.276
I didn't mean
to frustrate the team.

00:01:34.380 --> 00:01:35.510
I know you didn't.

00:01:35.551 --> 00:01:37.135
All I'm saying is that next time,

00:01:37.146 --> 00:01:39.926
use the same level of follow-up
with our internal team

00:01:39.937 --> 00:01:41.760
as you do with our clients.

00:01:44.128 --> 00:01:45.229
Hey, Kristi.

00:01:45.325 --> 00:01:46.651
Hey. Yah.

00:01:46.692 --> 00:01:50.682
I just wanted to follow up with you.
Ah... I don't have the best news.

00:01:50.754 --> 00:01:51.784
Yah.

00:01:51.833 --> 00:01:54.854
We're running new data
for that quarterly report.

00:01:55.301 --> 00:01:56.479
When?

00:01:56.863 --> 00:02:00.214
Well... that's a good question.
Ah, I'm hoping for tomorrow.

00:02:00.263 --> 00:02:01.089
But...

