﻿WEBVTT

00:00:09.402 --> 00:00:13.245
Okay, so the last time we met we
agreed that the best course of action

00:00:13.246 --> 00:00:15.585
was to make sure to find a
way to get more buy-in

00:00:15.610 --> 00:00:18.178
from sales and distribution
on the front end.

00:00:18.203 --> 00:00:19.844
Today, we're going to talk about the

00:00:19.869 --> 00:00:23.029
actual execution and
implementation of that plan.

00:00:23.056 --> 00:00:25.601
Right.
Sorry?

00:00:25.626 --> 00:00:27.330
Nothing. Go ahead.

00:00:27.372 --> 00:00:29.699
Okay. Let's start with sales.

00:00:30.990 --> 00:00:33.705
I think if we give them enough
lead-time that should work.

00:00:33.730 --> 00:00:35.558
More lead-time. Good idea.

00:00:35.882 --> 00:00:38.667
Any other thoughts before we
move on to distribution?

00:00:39.449 --> 00:00:42.566
Frank? What do you think?
Sure. Whatever.

00:00:42.939 --> 00:00:45.693
All right. Let's talk about distribution.

00:00:46.790 --> 00:00:50.298
I guess my question is, what kind
of information does distribution

00:00:50.299 --> 00:00:52.578
need upfront for them to give us an answer?

00:00:52.603 --> 00:00:54.509
Good question. Any ideas?

00:00:55.589 --> 00:00:58.718
Frank, you’ve probably worked with
distribution more than the rest of us.

00:00:58.743 --> 00:01:04.189
Yeah, I do. And I told you before this
isn't going to work. But, what do I know...

00:01:11.335 --> 00:01:15.427
We all come into a meeting with our
own ideas, filters and perceptions.

00:01:15.452 --> 00:01:19.000
And there are going to be times when you
run into an honest difference of opinion.

00:01:19.025 --> 00:01:22.836
So, how do you manage those kinds of
discussions and still keep things on track?

00:01:22.861 --> 00:01:25.196
Well, you want to acknowledge the concern.

00:01:25.221 --> 00:01:27.988
Ask clarifying questions to
make sure everyone understands

00:01:28.013 --> 00:01:29.718
where the person is coming from.

00:01:29.743 --> 00:01:32.159
And then get a commitment to move forward.

00:01:32.184 --> 00:01:34.029
Good question. Any ideas?

00:01:35.039 --> 00:01:38.456
Frank, you’ve probably worked with
distribution more than the rest of us.

00:01:38.481 --> 00:01:44.602
Yeah, I do. And ah, I told you this is not
going to work. But, what do I know...

00:01:45.490 --> 00:01:48.488
I realize that you didn't come
into this meeting thinking

00:01:48.489 --> 00:01:49.856
that this was the best approach.

00:01:49.881 --> 00:01:51.948
But last time, you agreed to give it a try.

00:01:51.949 --> 00:01:55.799
You're right, I did. But something
about it still bugs me.

00:01:56.161 --> 00:01:59.334
Has something changed between
now and our last meeting?

00:01:59.359 --> 00:02:02.454
No! I just don’t think it’s going to fly.

00:02:02.479 --> 00:02:07.190
Can you be more specific? Is there a
way we can tweak this so it will work.

00:02:08.308 --> 00:02:10.402
So, just to make sure I understand...

00:02:10.427 --> 00:02:14.989
if we increase lead-time to four weeks
instead of three - that will work?

00:02:15.122 --> 00:02:15.993
It helps.

00:02:16.582 --> 00:02:20.161
Listen, I can see why you'd still
have some reservations about this.

00:02:20.186 --> 00:02:22.968
But, today we really need to
stay focused on figuring out

00:02:22.969 --> 00:02:24.430
how to get this implemented.

00:02:24.455 --> 00:02:27.635
So, are you okay with moving forward?
Sure.

00:02:28.334 --> 00:02:32.656
Great. All right. We were
talking about distribution.

00:02:32.681 --> 00:02:36.566
So, what do you think is the best
way to keep them in the loop?

