WEBVTT

00:00:11.720 --> 00:00:15.060
Breaking free from the chains of the past Where

00:00:15.060 --> 00:00:18.820
truth moves faster than a Holstein calf No law

00:00:18.820 --> 00:00:21.660
waiting on some printed page We're charting new

00:00:21.660 --> 00:00:25.300
ground in the digital age From genomic codes

00:00:25.300 --> 00:00:29.120
to robot facts We cut through the noise, no hold

00:00:29.280 --> 00:00:32.460
them back not your daddy's dairy news tonight

00:00:32.460 --> 00:01:02.460
we're sparking Welcome back to the Bullvine Podcast,

00:01:02.899 --> 00:01:04.739
where we cut through the dairy industry noise

00:01:04.739 --> 00:01:07.200
to get you the insights that actually matter

00:01:07.200 --> 00:01:10.599
for your operation. And today, we're diving deep

00:01:10.599 --> 00:01:13.340
into a feature piece that's been generating some

00:01:13.340 --> 00:01:16.799
serious buzz. This one, it's got layers and,

00:01:16.900 --> 00:01:19.280
well, some surprises that are going to make producers

00:01:19.280 --> 00:01:21.700
rethink how they've been approaching management

00:01:21.700 --> 00:01:23.939
infrastructure. Yeah, we've spent years talking

00:01:23.939 --> 00:01:27.299
about genetics, the latest feed additives, technology

00:01:27.299 --> 00:01:30.500
upgrades, you name it. Right. All the usual suspects.

00:01:30.680 --> 00:01:32.219
But the key takeaway right out of the gate with

00:01:32.219 --> 00:01:35.500
this one is this. The best, most profitable upgrade

00:01:35.500 --> 00:01:38.280
for most dairies right now. It isn't equipment.

00:01:38.680 --> 00:01:41.400
It's human communication and process clarity.

00:01:41.799 --> 00:01:44.000
That's a bold claim right up front. communication

00:01:44.000 --> 00:01:46.299
over a new robot. Well, the data backs it up.

00:01:46.359 --> 00:01:48.420
We are going to break down the hard numbers showing

00:01:48.420 --> 00:01:50.599
exactly how much inconsistency is costing you

00:01:50.599 --> 00:01:53.260
per employee. And some simple visual systems

00:01:53.260 --> 00:01:56.840
that get this cut Scour's treatments by a staggering

00:01:56.840 --> 00:02:00.680
50 to 70 percent. Whoa. OK. 50 to 70 percent

00:02:00.680 --> 00:02:02.980
just from clearer communication. That's what

00:02:02.980 --> 00:02:05.099
the research suggests. This isn't just, you know,

00:02:05.099 --> 00:02:07.439
management theory fluff. This is about optimizing

00:02:07.439 --> 00:02:10.800
dollars and cents on your farm. At 50 to 70 percent

00:02:10.800 --> 00:02:14.280
figure alone. I mean, if that holds up, that

00:02:14.280 --> 00:02:17.020
should compel every farmer listening to pull

00:02:17.020 --> 00:02:19.400
over and really pay attention. Yeah. We definitely

00:02:19.400 --> 00:02:21.960
need to dissect that number. How can something

00:02:21.960 --> 00:02:26.460
seemingly soft like clarity generate that kind

00:02:26.460 --> 00:02:29.750
of ROI? Okay, let's unpack this setup then. We're

00:02:29.750 --> 00:02:31.810
looking at sources, multiple studies actually,

00:02:32.030 --> 00:02:34.370
arguing pretty persuasively that the biggest

00:02:34.370 --> 00:02:37.250
drag on operational performance today isn't the

00:02:37.250 --> 00:02:40.050
traditional nutrition or genetics bottleneck

00:02:40.050 --> 00:02:41.669
anymore. Which we've gotten incredibly good at

00:02:41.669 --> 00:02:43.960
managing, haven't we? Exactly. Producers have

00:02:43.960 --> 00:02:46.219
fine -tuned the cow's physical environment, her

00:02:46.219 --> 00:02:48.960
ration, her genetic potential. The weak link

00:02:48.960 --> 00:02:51.259
now, the sources argue, is that interface between

00:02:51.259 --> 00:02:53.840
the human employee and the operational protocol.

00:02:54.060 --> 00:02:56.560
It's a people and process problem. And that right

00:02:56.560 --> 00:02:58.500
there, that's the central tension, isn't it?

00:02:58.500 --> 00:03:00.580
Because for the producer listening right now,

00:03:00.740 --> 00:03:03.979
they're constantly barraged with pitches. Prioritize

00:03:03.979 --> 00:03:06.860
this TMR tweak. Buy this expensive semen. Install

00:03:06.860 --> 00:03:09.240
this new monitoring system. Things you can touch

00:03:09.240 --> 00:03:13.120
and see. Tangible investments. Yeah. So why should

00:03:13.120 --> 00:03:14.759
they take a step back from all that, from those

00:03:14.759 --> 00:03:17.759
high cost inputs that feel solid, and dedicate

00:03:17.759 --> 00:03:20.900
time and, frankly, resources to a communication

00:03:20.900 --> 00:03:23.960
plan? It feels less concrete. Because the high

00:03:23.960 --> 00:03:27.259
cost of inconsistency is literally draining the

00:03:27.259 --> 00:03:29.639
economic value out of those expensive investments

00:03:29.639 --> 00:03:32.330
you just made. Think about it. Okay. You pour

00:03:32.330 --> 00:03:35.949
thousands into premium feed additives, right?

00:03:36.090 --> 00:03:39.050
Into the best genetics money can buy, into advanced

00:03:39.050 --> 00:03:41.189
monitoring systems, all that capital, all that

00:03:41.189 --> 00:03:44.669
potential. It's fundamentally undercut if the

00:03:44.669 --> 00:03:46.909
protocol implementation, the human execution

00:03:46.909 --> 00:03:50.199
is inconsistent across chefs. Day after day.

00:03:50.379 --> 00:03:52.599
So if the evening milker preps cows differently

00:03:52.599 --> 00:03:55.000
than the morning crew. Or if the colostrum protocol

00:03:55.000 --> 00:03:57.500
isn't followed exactly the same way every single

00:03:57.500 --> 00:03:59.259
time, depending on who's working the calf barn

00:03:59.259 --> 00:04:01.180
that day. Then you're basically neutralizing

00:04:01.180 --> 00:04:03.780
the benefit of the expensive feed or the top

00:04:03.780 --> 00:04:05.759
tier genetics you paid for. Precisely. You're

00:04:05.759 --> 00:04:08.139
actively canceling out your own investments through

00:04:08.139 --> 00:04:13.180
inconsistent execution. It's like. OK, it's like

00:04:13.180 --> 00:04:15.460
you bought this incredibly expensive, finely

00:04:15.460 --> 00:04:18.959
tuned race car, the genetics, the feed. And you

00:04:18.959 --> 00:04:21.339
wrote the perfect driving instructions, the protocols.

00:04:21.639 --> 00:04:24.379
Good analogy. But if the drivers keep changing

00:04:24.379 --> 00:04:26.980
and half of them haven't really read the instructions

00:04:26.980 --> 00:04:29.060
or they interpret them differently or maybe they

00:04:29.060 --> 00:04:30.779
can't even read the language the instructions

00:04:30.779 --> 00:04:34.019
are in, the car's performance is going to be

00:04:34.019 --> 00:04:35.319
all over the place. You're not going to win the

00:04:35.319 --> 00:04:37.980
race. And the financial leakage, this is key.

00:04:38.399 --> 00:04:42.079
It doesn't usually happen from one big visible

00:04:42.079 --> 00:04:45.160
breakdown, not like a tractor dying in the field.

00:04:45.259 --> 00:04:47.579
No, it's quieter than that. It's the slow drip,

00:04:47.740 --> 00:04:52.040
the daily compounding micro errors, unclear instructions,

00:04:52.459 --> 00:04:55.720
undocumented knowledge, just a lack of consistent

00:04:55.720 --> 00:04:57.740
systems that everyone understands and follows.

00:04:57.899 --> 00:05:00.120
That's where the money disappears. Okay, so this

00:05:00.120 --> 00:05:01.540
is where it gets interesting and maybe a bit

00:05:01.540 --> 00:05:03.680
controversial. Right. Because you're challenging

00:05:03.680 --> 00:05:06.160
how managers think they're operating. Definitely.

00:05:06.319 --> 00:05:08.459
We'll be digging into research that actually

00:05:08.459 --> 00:05:11.300
quantifies this. It shows that documenting just

00:05:11.300 --> 00:05:14.399
five key tasks, we're not talking about a massive

00:05:14.399 --> 00:05:17.680
100 -page binder. Nobody reads just five core

00:05:17.680 --> 00:05:21.379
critical tasks. That alone can speed up training

00:05:21.379 --> 00:05:25.579
by 25 % to 40%. 25 % to 40 % faster training.

00:05:26.180 --> 00:05:29.399
Just from documenting five things, clearly. Yeah.

00:05:30.750 --> 00:05:33.290
The biggest hurdle, the controversy maybe, and

00:05:33.290 --> 00:05:35.110
why I think a lot of producers might initially

00:05:35.110 --> 00:05:37.290
push back on this whole idea. I can see it coming.

00:05:37.470 --> 00:05:39.870
It's that most producers genuinely believe they

00:05:39.870 --> 00:05:41.649
already communicate well. They talk to their

00:05:41.649 --> 00:05:43.610
people every day. They walk the barns. I tell

00:05:43.610 --> 00:05:45.129
my guys what to do. We have morning meetings.

00:05:45.410 --> 00:05:47.990
That's what you hear. Exactly. But the data,

00:05:48.129 --> 00:05:50.990
it tells a different story, a much, much more

00:05:50.990 --> 00:05:53.370
expensive story about what real clarity actually

00:05:53.370 --> 00:05:55.870
requires versus just talking at people. Yeah,

00:05:55.889 --> 00:05:57.810
I have to agree with that potential pushback.

00:05:57.949 --> 00:06:00.860
As an operator myself. You know, you look at

00:06:00.860 --> 00:06:02.839
it, your crew, you have those conversations and

00:06:02.839 --> 00:06:04.480
you feel like you're communicating effectively.

00:06:04.620 --> 00:06:06.879
We discussed the plan for the day. Right. It

00:06:06.879 --> 00:06:09.139
feels like communication is happening. But what

00:06:09.139 --> 00:06:11.519
this deep dive seems to be emphasizing is that

00:06:11.519 --> 00:06:15.680
what we think is clear communication is often

00:06:15.680 --> 00:06:19.720
just, well, it's oral tradition. It's institutional

00:06:19.720 --> 00:06:22.319
memory locked up in one or two key people's heads.

00:06:22.420 --> 00:06:25.120
It's not a documented, reliable structure. And

00:06:25.120 --> 00:06:26.740
that lack of structure is the vulnerability.

00:06:27.220 --> 00:06:29.800
Absolutely. Because documentation is the only

00:06:29.800 --> 00:06:32.720
thing that makes consistency scalable and, frankly,

00:06:32.800 --> 00:06:35.459
reliable across the board. If I can't leave the

00:06:35.459 --> 00:06:37.579
farm for two weeks for a family thing or even

00:06:37.579 --> 00:06:40.699
just a weekend and know with 100 percent certainty

00:06:40.699 --> 00:06:42.660
that the calf care protocol is being followed

00:06:42.660 --> 00:06:46.110
precisely the same way I want it done. then I

00:06:46.110 --> 00:06:47.949
don't really have a system, do I? No, you have

00:06:47.949 --> 00:06:51.110
a dependency, a dependency on specific individuals.

00:06:51.449 --> 00:06:54.110
Exactly. I have a dependency on maybe one key

00:06:54.110 --> 00:06:56.430
person, and that's a huge risk. Okay, let's dive

00:06:56.430 --> 00:06:57.990
straight into the economics then. Let's put a

00:06:57.990 --> 00:06:59.910
price tag on this ambiguity we're talking about.

00:07:00.069 --> 00:07:02.829
We've kind of established that most modern dairies,

00:07:02.889 --> 00:07:05.370
they've got the hardware down, pat parlors, storage,

00:07:05.509 --> 00:07:08.509
feeding equipment, you know. And the inputs feed,

00:07:08.649 --> 00:07:11.029
genetics are top notch. Yeah, the physical stuff,

00:07:11.129 --> 00:07:13.629
the biological stuff, we've optimized that relentlessly

00:07:13.629 --> 00:07:16.139
for decades. Right. So the real missing link,

00:07:16.220 --> 00:07:18.459
the thing dragging performance down now, it seems,

00:07:18.639 --> 00:07:21.560
is consistency. And that's rooted directly in

00:07:21.560 --> 00:07:23.600
poor communication structure. It's a paradigm

00:07:23.600 --> 00:07:26.399
shift, really. For years, the industry solution

00:07:26.399 --> 00:07:30.019
to almost any problem was test your feed, call

00:07:30.019 --> 00:07:33.120
your vet, check your facilities, fix the physical.

00:07:33.300 --> 00:07:35.540
Always the physical. Now we're being forced to

00:07:35.540 --> 00:07:37.740
recognize that maybe the biggest variable impacting

00:07:37.740 --> 00:07:40.399
how those systems perform. Yeah. It's the human

00:07:40.399 --> 00:07:42.680
execution of the protocols we designed for those

00:07:42.680 --> 00:07:46.160
systems. The cow, she doesn't deviate much from

00:07:46.160 --> 00:07:48.379
her biology. No, she does what cows do. It's

00:07:48.379 --> 00:07:50.600
the human operating the system around her that

00:07:50.600 --> 00:07:53.720
introduces the variation, the inconsistency.

00:07:53.759 --> 00:07:56.620
And the cost of that failure to execute flawlessly.

00:07:57.060 --> 00:07:59.680
It's quantifiable and it's, frankly, massive.

00:07:59.920 --> 00:08:02.620
Let's get specific. Look at this data point from

00:08:02.620 --> 00:08:05.720
Michigan State University Extension. They analyzed

00:08:05.720 --> 00:08:08.779
the price of employee turnover. Ah, turnover.

00:08:09.319 --> 00:08:11.339
The revolving door cost. And it's staggering.

00:08:11.620 --> 00:08:13.519
They report that replacing one employee, just

00:08:13.519 --> 00:08:15.459
one person, could be a milker, could be a feeder.

00:08:15.540 --> 00:08:17.060
It doesn't matter. It costs between $15 ,000

00:08:17.060 --> 00:08:20.819
and $25 ,000. Wait, wait. Hold on. $15 ,000 to

00:08:20.819 --> 00:08:25.300
$25 ,000 for one employee. We need to break that

00:08:25.300 --> 00:08:27.360
down. Because I guarantee you, a lot of producers

00:08:27.360 --> 00:08:30.600
hear that number and think, no way. I paid maybe

00:08:30.600 --> 00:08:33.299
$50 for a help -wanted ad, spent a couple hours

00:08:33.299 --> 00:08:35.759
showing the new guy the ropes. Where on earth

00:08:35.759 --> 00:08:38.919
does $25 ,000 come from? It comes from the hidden

00:08:38.919 --> 00:08:41.419
costs. The stuff you don't write a direct check

00:08:41.419 --> 00:08:43.740
for, but it drains your resources just the same.

00:08:43.919 --> 00:08:48.240
That 15K to 25K, it covers way more than just

00:08:48.240 --> 00:08:50.179
the recruitment ad. Okay, so what's in that number?

00:08:50.340 --> 00:08:53.740
You've got the measurable sunk costs like HR

00:08:53.740 --> 00:08:56.100
time spent sifting resumes, doing interviews,

00:08:56.259 --> 00:08:59.059
background checks, maybe agency fees if you use

00:08:59.059 --> 00:09:01.299
a recruiter. That's part of it. The admin overhead.

00:09:01.500 --> 00:09:04.039
Got it. But the bulk of that expense, the really

00:09:04.039 --> 00:09:06.740
big chunk, comes from lost productivity. That

00:09:06.740 --> 00:09:09.480
includes the time your existing experienced crew

00:09:09.480 --> 00:09:12.179
spends training the new hire instead of doing

00:09:12.179 --> 00:09:14.620
their own job efficiently. Okay. Pulling good

00:09:14.620 --> 00:09:17.000
people off their tasks to train. Right. Then

00:09:17.000 --> 00:09:18.860
there's the reduced efficiency of the new person

00:09:18.860 --> 00:09:20.679
during that whole onboarding phase, which can

00:09:20.679 --> 00:09:23.220
last weeks or even months. They're slower. They

00:09:23.220 --> 00:09:25.639
need more supervision. Makes sense. The learning

00:09:25.639 --> 00:09:28.919
curve. And maybe most critically and often hardest

00:09:28.919 --> 00:09:31.340
to track, are the inevitable dips in operational

00:09:31.340 --> 00:09:34.480
quality. Maybe a slight uptick in somatic cell

00:09:34.480 --> 00:09:36.919
count. Slightly lower breeding efficiency for

00:09:36.919 --> 00:09:39.500
a bit. Maybe a few more cases of calf scours

00:09:39.500 --> 00:09:41.500
while the new person is learning the ropes in

00:09:41.500 --> 00:09:44.700
the calf barn. Ah, so the mistakes. The small

00:09:44.700 --> 00:09:47.820
inconsistencies that add up while someone's learning.

00:09:48.309 --> 00:09:51.470
Exactly. Those quality dips, they often aren't

00:09:51.470 --> 00:09:53.769
immediately chalked up to turnover, but they

00:09:53.769 --> 00:09:56.169
are a direct financial consequence. That's lost

00:09:56.169 --> 00:09:58.250
milk quality premiums. That's extra vet bills.

00:09:58.309 --> 00:10:00.649
That's lower future production. It adds up fast.

00:10:00.889 --> 00:10:02.590
Okay. All right. So let's put that into context

00:10:02.590 --> 00:10:04.509
then. Let's say you're running a mid to large

00:10:04.509 --> 00:10:07.990
farm, maybe 1 ,500 cows, and you lose just five

00:10:07.990 --> 00:10:10.419
people a year. Which, let's be honest, isn't

00:10:10.419 --> 00:10:11.860
uncommon, especially if you're running multiple

00:10:11.860 --> 00:10:14.159
shifts. Absolutely not uncommon. Five is probably

00:10:14.159 --> 00:10:16.820
conservative for some larger places. So using

00:10:16.820 --> 00:10:18.740
their numbers, you're looking at a conservative

00:10:18.740 --> 00:10:24.120
baseline cost of five times $15 ,000 is $75 ,000.

00:10:24.379 --> 00:10:28.039
Up to maybe five times $25 ,000. $125 ,000. Sure.

00:10:28.100 --> 00:10:31.120
Just in turnover costs. Sunk costs. That's right.

00:10:31.279 --> 00:10:36.860
$75 ,000 to $125 ,000. Just gone. pure capital

00:10:36.860 --> 00:10:38.960
outflow. Money that's essentially just been set

00:10:38.960 --> 00:10:41.899
on fire, poof. Pretty much. It provides zero

00:10:41.899 --> 00:10:44.059
return to the operation. It's like this invisible

00:10:44.059 --> 00:10:46.720
tax you pay for instability. And because it's

00:10:46.720 --> 00:10:50.000
not a single check you write for $125 ,000, it's

00:10:50.000 --> 00:10:52.399
kind of hidden. It's spread out through, you

00:10:52.399 --> 00:10:54.779
know, $1 ,000 here and decreased milk quality,

00:10:55.139 --> 00:10:58.519
100 hours there and wasted supervisor time, months

00:10:58.519 --> 00:11:01.460
of slightly slower operational metrics. But the

00:11:01.460 --> 00:11:05.289
cost is very, very real. theoretically largely

00:11:05.289 --> 00:11:08.110
avoidable if you can improve retention through

00:11:08.110 --> 00:11:10.409
clearer systems and less stressful work environments.

00:11:10.649 --> 00:11:12.570
That's the argument. And we haven't even really

00:11:12.570 --> 00:11:15.129
factored in the compounding cost of the actual

00:11:15.129 --> 00:11:17.809
mistakes made by new or poorly trained staff

00:11:17.809 --> 00:11:20.429
beyond just that initial learning curve dip.

00:11:20.570 --> 00:11:23.809
Right. A new hire who doesn't quite grasp the

00:11:23.809 --> 00:11:27.389
nuances of your fresh cow protocol. That mistake

00:11:27.389 --> 00:11:29.389
doesn't just cost you in that moment. No, it

00:11:29.389 --> 00:11:31.210
can cost you far more than their salary down

00:11:31.210 --> 00:11:33.929
the line. If a fresh cow's transition is mishandled,

00:11:33.929 --> 00:11:36.289
even slightly, and her lactation peak gets pushed

00:11:36.289 --> 00:11:38.429
back by just a few days or doesn't reach its

00:11:38.429 --> 00:11:41.330
potential. That's lost milk revenue. Not just

00:11:41.330 --> 00:11:44.149
for that day, but potentially impacting the entire

00:11:44.149 --> 00:11:46.529
lactation curve for that animal. Yeah. And multiply

00:11:46.529 --> 00:11:48.629
that across even a small percentage of the herd.

00:11:49.580 --> 00:11:51.879
Yeah, it adds up. Which brings us directly to

00:11:51.879 --> 00:11:54.059
this really powerful concept we found in the

00:11:54.059 --> 00:11:56.100
source material. It's a quote from Dr. Robert

00:11:56.100 --> 00:11:57.879
Hegevoort. He's at New Mexico State University.

00:11:58.360 --> 00:12:01.620
Simple quote, but it hits hard. He says, every

00:12:01.620 --> 00:12:04.019
time someone does the right job the wrong way,

00:12:04.159 --> 00:12:08.289
the farm pays tuition. Tuition. I like that.

00:12:08.330 --> 00:12:10.610
That framing really works. It puts the onus back

00:12:10.610 --> 00:12:12.870
on management, doesn't it? It acknowledges that

00:12:12.870 --> 00:12:14.830
the owner, the manager, you are the one paying

00:12:14.830 --> 00:12:17.250
for that learning curve. And if your systems,

00:12:17.269 --> 00:12:20.370
your communication are ambiguous. Well, that

00:12:20.370 --> 00:12:22.450
tuition fee never really stops. You keep paying

00:12:22.450 --> 00:12:24.850
it. And the tuition isn't usually for the big

00:12:24.850 --> 00:12:27.230
catastrophic failures. It's for those invisible

00:12:27.230 --> 00:12:30.570
daily inefficiencies that just chip away at your

00:12:30.570 --> 00:12:32.549
margins. The small stuff that drives you crazy.

00:12:32.750 --> 00:12:35.210
Oh, yeah. It's the slightly inconsistent dip

00:12:35.210 --> 00:12:37.970
time on 100 cows that leads to those subtle mastitis

00:12:37.970 --> 00:12:40.509
flare -ups later. It's the calf getting milk

00:12:40.509 --> 00:12:43.070
that's maybe five degrees too cool, stressing

00:12:43.070 --> 00:12:45.850
its gut, leading to a higher risk of scours down

00:12:45.850 --> 00:12:48.330
the road. Or maybe the TMR push -up that happens

00:12:48.330 --> 00:12:50.360
30 minutes late. during that critical feeding

00:12:50.360 --> 00:12:52.980
window, messing with intake and digestibility

00:12:52.980 --> 00:12:55.639
for the whole pen. Exactly. None of those individually

00:12:55.639 --> 00:12:58.240
feels like a disaster, but each one is a fee.

00:12:58.580 --> 00:13:01.620
It's tuition paid to the ambiguity of your communication

00:13:01.620 --> 00:13:04.259
system. And if that adds up to just, say, five

00:13:04.259 --> 00:13:06.840
cents per cow per day across your herd. Which

00:13:06.840 --> 00:13:09.179
doesn't sound like much. But do the math. Five

00:13:09.179 --> 00:13:13.100
cents times a thousand cows times 365 days. That's

00:13:13.100 --> 00:13:16.159
over $18 ,000 a year lost to simple structural

00:13:16.159 --> 00:13:19.509
communication -based errors. And we spend Hours,

00:13:19.509 --> 00:13:22.370
hours trying to optimize feed costs by maybe

00:13:22.370 --> 00:13:24.929
half a cent per cow per day, which we should.

00:13:25.169 --> 00:13:27.590
But if poor training, insisting ambiguity is

00:13:27.590 --> 00:13:30.330
potentially costing us five, ten, maybe even

00:13:30.330 --> 00:13:32.549
more cents per cow per day in lost consistency.

00:13:33.179 --> 00:13:35.480
turnover costs, extra treatments. Which the data

00:13:35.480 --> 00:13:37.679
suggests is entirely possible. Then maybe the

00:13:37.679 --> 00:13:40.720
answer to what should I focus on next isn't just

00:13:40.720 --> 00:13:43.759
the feed bunk. It requires a fundamental shift,

00:13:43.879 --> 00:13:47.179
maybe, in management thinking. Viewing your people

00:13:47.179 --> 00:13:50.419
systems with the same analytical rigor you apply

00:13:50.419 --> 00:13:53.190
to your TMR calculations. Okay, let's shift gears

00:13:53.190 --> 00:13:56.350
a bit to an industry reality check. Because when

00:13:56.350 --> 00:13:59.370
many producers hear communication problem, their

00:13:59.370 --> 00:14:01.710
mind immediately jumps to one thing, language

00:14:01.710 --> 00:14:04.509
barriers. English versus Spanish, usually. That's

00:14:04.509 --> 00:14:06.730
the default assumption. Right. And look, language

00:14:06.730 --> 00:14:09.470
barriers are a massive factor. The data proves

00:14:09.470 --> 00:14:11.610
it. We'll get into that. But the problem is actually

00:14:11.610 --> 00:14:13.929
far more nuanced than just needing a Spanish

00:14:13.929 --> 00:14:16.570
translator on staff. That's a really crucial

00:14:16.570 --> 00:14:19.429
distinction because too often we operate under

00:14:19.429 --> 00:14:21.250
the assumption that, OK, I've got someone on

00:14:21.250 --> 00:14:23.549
staff who speaks Spanish. Check that box. We're

00:14:23.549 --> 00:14:26.409
covered. But that can be a dangerous oversimplification.

00:14:26.409 --> 00:14:28.830
It might actually create new risks. It creates

00:14:28.830 --> 00:14:31.789
enormous risk. Look at the NMSU research again.

00:14:31.830 --> 00:14:34.889
It shows roughly 60 percent of U .S. dairy employees

00:14:34.889 --> 00:14:38.299
speak limited English. 60%. That number alone

00:14:38.299 --> 00:14:41.759
tells you that relying purely on spoken English

00:14:41.759 --> 00:14:44.539
instructions or even just written English protocols

00:14:44.539 --> 00:14:47.159
is going to fail for a majority of your workforce.

00:14:47.440 --> 00:14:50.399
You need a systematic visual approach almost

00:14:50.399 --> 00:14:53.259
by default. Absolutely. But let's dig into the

00:14:53.259 --> 00:14:55.179
nuance of language that often gets completely

00:14:55.179 --> 00:14:57.940
missed, especially out West. In certain regions,

00:14:58.120 --> 00:15:01.710
particularly the Southwest, the complexity deepens

00:15:01.710 --> 00:15:04.610
dramatically. The research shows up to a third

00:15:04.610 --> 00:15:07.490
of employees in some areas speak Quiche. Quiche,

00:15:07.710 --> 00:15:09.809
right? That's a Mayan dialect spoken primarily

00:15:09.809 --> 00:15:12.570
in Guatemala, not Spanish. Exactly. It's not

00:15:12.570 --> 00:15:14.409
Spanish. It's a completely different language

00:15:14.409 --> 00:15:17.529
family. So if your training materials, your SOPs,

00:15:17.610 --> 00:15:19.950
your safety warnings are only in English and

00:15:19.950 --> 00:15:22.529
maybe standard Latin American Spanish, you are

00:15:22.529 --> 00:15:25.110
fundamentally missing potentially a full third

00:15:25.110 --> 00:15:27.389
of your crew in those specific regions. They

00:15:27.389 --> 00:15:29.830
might nod when given instructions in Spanish,

00:15:30.009 --> 00:15:32.350
trying to be agreeable or maybe picking up some

00:15:32.350 --> 00:15:35.139
cognates. Right. But they're likely processing

00:15:35.139 --> 00:15:37.600
the information, thinking through the task, and

00:15:37.600 --> 00:15:40.460
communicating amongst themselves in Quiche. This

00:15:40.460 --> 00:15:43.220
just highlights how complex multilingual really

00:15:43.220 --> 00:15:45.759
is on the ground. It's not just two languages.

00:15:46.059 --> 00:15:48.240
You need to consider all the primary languages

00:15:48.240 --> 00:15:50.659
spoken by your team. Which often means visual

00:15:50.659 --> 00:15:53.379
communication becomes even more critical, because

00:15:53.379 --> 00:15:55.659
pictures can bridge those diverse language gaps

00:15:55.659 --> 00:15:59.460
better than text ever could. Precisely. And this

00:15:59.460 --> 00:16:02.340
complexity leads directly to that inherent risk

00:16:02.340 --> 00:16:04.919
we touched on earlier. The risk of having the

00:16:04.919 --> 00:16:08.220
system reside entirely in the head of one key

00:16:08.220 --> 00:16:11.179
translator or one long -term crew leader. The

00:16:11.179 --> 00:16:13.879
indispensable employee. The one person everyone

00:16:13.879 --> 00:16:16.360
relies on to bridge the gap. As a manager, you

00:16:16.360 --> 00:16:18.559
assume, okay, Maria's been here seven years.

00:16:18.639 --> 00:16:20.600
She's bilingual. She understands my protocols

00:16:20.600 --> 00:16:22.679
inside and out. She'll make sure everyone on

00:16:22.679 --> 00:16:25.039
her shift gets it. you trust her to convey all

00:16:25.039 --> 00:16:27.379
the critical details the nuances of the calf

00:16:27.379 --> 00:16:30.080
feeding protocol the exact steps for the milking

00:16:30.080 --> 00:16:33.100
procedure but that person maria in this example

00:16:33.100 --> 00:16:36.220
she's now become a single point of failure a

00:16:36.220 --> 00:16:40.220
highly skilled highly valuable but also highly

00:16:40.220 --> 00:16:43.779
risky single point of failure the stability the

00:16:43.779 --> 00:16:46.399
consistency of your entire operation might be

00:16:46.399 --> 00:16:48.840
resting precariously on her memory and her continued

00:16:48.840 --> 00:16:51.830
presence and that is Frankly, terrifying from

00:16:51.830 --> 00:16:53.990
a management perspective. Because what happens

00:16:53.990 --> 00:16:55.830
when that single point of failure walks out the

00:16:55.830 --> 00:16:59.169
door? Whether they quit, get sick, move away.

00:16:59.330 --> 00:17:01.549
The whole system can collapse, often immediately.

00:17:01.710 --> 00:17:03.889
We saw a compelling case study on this in the

00:17:03.889 --> 00:17:06.609
source material. A 900 cow operation in Minnesota.

00:17:06.670 --> 00:17:09.710
They lost their key bilingual milker suddenly,

00:17:09.930 --> 00:17:12.470
unexpectedly. Okay, walk us through what happened.

00:17:12.569 --> 00:17:14.190
What were the immediate operational impacts?

00:17:14.490 --> 00:17:16.769
Because that's what producers understand, metrics

00:17:16.769 --> 00:17:19.150
hitting the ditch. The deterioration was fast

00:17:19.150 --> 00:17:21.769
and measurable. Within days, their somatic cell

00:17:21.769 --> 00:17:23.569
count, which is like the universal barometer

00:17:23.569 --> 00:17:26.230
for herd health consistency and proper milking

00:17:26.230 --> 00:17:28.549
procedure adherence. The number everyone watches.

00:17:28.829 --> 00:17:32.410
It spiked past 300 ,000. That's a major hit to

00:17:32.410 --> 00:17:35.230
milk quality premiums, obviously. But it's also

00:17:35.230 --> 00:17:37.930
a clear indicator that systemic issues, likely

00:17:37.930 --> 00:17:40.809
mastitis, were emerging rapidly because procedures

00:17:40.809 --> 00:17:42.789
weren't being followed consistently anymore.

00:17:43.089 --> 00:17:47.470
Ouch. Over 300k SCC almost overnight. And what

00:17:47.470 --> 00:17:50.970
about efficiency? That suffered too. Operationally,

00:17:50.970 --> 00:17:52.809
their milking shifts started running nearly an

00:17:52.809 --> 00:17:55.910
hour longer. Just chaos. An hour longer per shift,

00:17:56.049 --> 00:17:58.430
multiplied by how many employees are on that

00:17:58.430 --> 00:18:01.490
shift, times how many shifts per day. Yeah, that's

00:18:01.490 --> 00:18:03.569
hundreds of dollars in unplanned labor costs

00:18:03.569 --> 00:18:05.869
instantly appearing on the books every single

00:18:05.869 --> 00:18:08.130
day. Plus, think about the stress on the remaining

00:18:08.130 --> 00:18:10.230
employees. Oh, absolutely. Knowing they're running

00:18:10.230 --> 00:18:12.930
behind, feeling the pressure, that immediately

00:18:12.930 --> 00:18:15.319
causes people to rush, which... then leads to

00:18:15.319 --> 00:18:17.740
more errors, probably making the SEC even worse.

00:18:17.759 --> 00:18:20.000
It becomes a downward spiral. It proves that

00:18:20.000 --> 00:18:21.960
the crew leader wasn't just translating words.

00:18:22.140 --> 00:18:24.299
They were translating consistency. They were

00:18:24.299 --> 00:18:26.599
the keepers of the procedure, the pace, the flow.

00:18:26.759 --> 00:18:29.500
When they left, all that tacit knowledge left

00:18:29.500 --> 00:18:32.200
with them. Okay, so how did they fix it? What

00:18:32.200 --> 00:18:35.180
was the structural solution? Because just hiring

00:18:35.180 --> 00:18:37.140
another bilingual person doesn't necessarily

00:18:37.140 --> 00:18:39.859
solve the underlying systemic risk. Exactly.

00:18:40.039 --> 00:18:42.819
They needed to rebuild the foundation. With help

00:18:42.819 --> 00:18:45.160
from UW -Madison Extension, they didn't just

00:18:45.160 --> 00:18:47.759
try to find a replacement translator. They implemented

00:18:47.759 --> 00:18:50.900
bilingual photo SOPs, standard operating procedures

00:18:50.900 --> 00:18:53.640
with pictures and clear shift checklists for

00:18:53.640 --> 00:18:56.759
critical tasks. Ah, so they took the knowledge

00:18:56.759 --> 00:18:59.480
out of that one person's head and made it visible,

00:18:59.660 --> 00:19:02.160
accessible, and standardized for everyone. Precisely.

00:19:02.160 --> 00:19:04.940
They visualized the critical processes. They

00:19:04.940 --> 00:19:07.119
documented the system so it wasn't dependent

00:19:07.119 --> 00:19:10.400
on any single individual anymore. And the result?

00:19:10.519 --> 00:19:13.529
Did it work? The results validate the effort

00:19:13.529 --> 00:19:17.269
completely. Pure ROI. The SEC was back below

00:19:17.269 --> 00:19:20.609
$200 ,000 within 30 days. 30 days. That's a rapid

00:19:20.609 --> 00:19:22.869
recovery. That's saving money fast. And maybe

00:19:22.869 --> 00:19:24.670
even more importantly for the long term. Their

00:19:24.670 --> 00:19:27.150
employee turnover rate significantly slowed down

00:19:27.150 --> 00:19:29.369
afterwards. Why do you think that is? Just the

00:19:29.369 --> 00:19:32.549
clear instructions? It seems so. When work instructions

00:19:32.549 --> 00:19:35.029
are clear, when they're documented, when they're

00:19:35.029 --> 00:19:38.039
visual and easy to access. the work environment

00:19:38.039 --> 00:19:40.680
becomes less stressful it feels more professional

00:19:40.680 --> 00:19:43.740
more organized people feel more competent less

00:19:43.740 --> 00:19:45.859
likely to make mistakes they'll get yelled at

00:19:45.859 --> 00:19:48.680
for the farm is no longer dependent on a hero

00:19:48.680 --> 00:19:52.140
saving the day it's dependent on a reliable system

00:19:52.140 --> 00:19:55.079
that everyone can understand and use that builds

00:19:55.079 --> 00:19:58.059
confidence that structure builds team stability

00:19:58.799 --> 00:20:00.900
And that stability is often the most critical

00:20:00.900 --> 00:20:03.180
factor in employee retention, sometimes even

00:20:03.180 --> 00:20:05.059
more important than a marginal pay increase.

00:20:05.480 --> 00:20:08.579
People often stay longer, work harder, be more

00:20:08.579 --> 00:20:11.440
engaged if they feel competent, supported, and

00:20:11.440 --> 00:20:13.839
less stressed because the expectations are crystal

00:20:13.839 --> 00:20:16.299
clear. It makes perfect sense. If the system

00:20:16.299 --> 00:20:18.480
supports you, you're more likely to stay. And

00:20:18.480 --> 00:20:20.380
we have more data on that stability connection,

00:20:20.559 --> 00:20:23.000
too. This comes from Cornell's Pro -Air Dairy

00:20:23.000 --> 00:20:25.099
program. They tracked farms that implemented

00:20:25.099 --> 00:20:27.839
really simple, short daily huddles. Just quick

00:20:27.839 --> 00:20:30.410
check -ins. Yeah, like five to ten minute check

00:20:30.410 --> 00:20:32.609
-ins at the start of each shift. Here's the focus

00:20:32.609 --> 00:20:35.309
today. Any issues from yesterday, any questions,

00:20:35.529 --> 00:20:38.609
simple stuff. Those farms saw turnover fall by

00:20:38.609 --> 00:20:42.410
30 -50%. 30 -50 % reduction in turnover just

00:20:42.410 --> 00:20:44.769
from adding a quick daily huddle. It reinforces

00:20:44.769 --> 00:20:47.009
the whole thesis, doesn't it? Yeah. Clarity builds

00:20:47.009 --> 00:20:50.059
stability. Stability reduces turnover, and it's

00:20:50.059 --> 00:20:52.019
often cheaper and more effective than just throwing

00:20:52.019 --> 00:20:53.920
money at the problem through endless pay raises

00:20:53.920 --> 00:20:56.859
because you're addressing the root cause, operational

00:20:56.859 --> 00:21:00.299
stress, confusion, and lack of confidence. It

00:21:00.299 --> 00:21:02.319
really is the difference between walking into

00:21:02.319 --> 00:21:04.779
work, feeling anxious, having to guess what's

00:21:04.779 --> 00:21:07.680
expected, relying on fragmented, rushed, maybe

00:21:07.680 --> 00:21:10.660
unclear verbal instructions, versus walking in,

00:21:10.680 --> 00:21:13.099
seeing a clear checklist or a visual guide, and

00:21:13.099 --> 00:21:15.119
knowing exactly what success looks like for your

00:21:15.119 --> 00:21:17.559
shift. One feels like chaos. The other feels

00:21:17.559 --> 00:21:21.019
like a system you can actually master. That's

00:21:21.019 --> 00:21:24.500
empowering. Okay, let's tackle the skepticism

00:21:24.500 --> 00:21:27.460
head on now. Suppose a manager is listening,

00:21:27.539 --> 00:21:29.920
and maybe they're partly convinced, but they

00:21:29.920 --> 00:21:31.819
still feel like, yeah, but I think my systems

00:21:31.819 --> 00:21:33.880
are pretty good. They're not seeing massive SEC

00:21:33.880 --> 00:21:36.599
spikes or huge turnover, but maybe they still

00:21:36.599 --> 00:21:39.859
feel that. Creeping inconsistency. You know,

00:21:39.880 --> 00:21:42.440
little calf scour outbreak here, temporary dip

00:21:42.440 --> 00:21:44.799
in conception rates there. Things aren't quite

00:21:44.799 --> 00:21:47.200
perfect. The nagging feeling that things could

00:21:47.200 --> 00:21:50.140
be smoother, more predictable. Exactly. If managers

00:21:50.140 --> 00:21:51.900
are maybe overlooking some of these system gaps,

00:21:52.140 --> 00:21:54.279
how do they find them without launching some

00:21:54.279 --> 00:21:57.839
kind of major, disruptive, costly audit? You

00:21:57.839 --> 00:21:59.660
know, shutting down the barn for a week, hiring

00:21:59.660 --> 00:22:02.440
outside consultants. Nobody wants to do that.

00:22:02.559 --> 00:22:04.519
Right. You don't necessarily need a full -blown

00:22:04.519 --> 00:22:06.900
expensive audit. You need a diagnosis first.

00:22:07.099 --> 00:22:09.359
And the best diagnosticians, they're usually

00:22:09.359 --> 00:22:11.240
the people doing the actual work every single

00:22:11.240 --> 00:22:13.039
day. Okay. So how do you get that diagnosis from

00:22:13.039 --> 00:22:16.059
them? The sources suggest a really simple, actionable

00:22:16.059 --> 00:22:18.339
starting point. Just one strategic question.

00:22:18.980 --> 00:22:21.400
Tomorrow morning, find your longest standing

00:22:21.400 --> 00:22:24.160
employee, the veteran, the one who's seen it

00:22:24.160 --> 00:22:26.480
all, remembers how things used to be done, knows

00:22:26.480 --> 00:22:28.759
all the little tricks and workarounds. The person

00:22:28.759 --> 00:22:31.779
who really knows where the bodies are buried,

00:22:31.920 --> 00:22:35.599
so to speak. Yeah, maybe. And you ask them this

00:22:35.599 --> 00:22:38.440
question sincerely. If someone brand new started

00:22:38.440 --> 00:22:41.759
on this farm tomorrow, what is the single hardest

00:22:41.759 --> 00:22:43.920
thing for them to learn correctly that is not

00:22:43.920 --> 00:22:46.859
clearly written down or shown somewhere? That's

00:22:46.859 --> 00:22:49.130
a great question. What's the hardest thing to

00:22:49.130 --> 00:22:51.609
learn that isn't written down? It's surgically

00:22:51.609 --> 00:22:53.589
brilliant, like you said earlier about a different

00:22:53.589 --> 00:22:56.069
point, because it completely bypasses the manager's

00:22:56.069 --> 00:22:58.789
own assumptions about what's important or what's

00:22:58.789 --> 00:23:00.869
already clear. Yeah, the manager assumes, oh,

00:23:00.890 --> 00:23:02.730
the hardest thing is learning the milking machine

00:23:02.730 --> 00:23:05.369
startup sequence, but that's in the manual on

00:23:05.369 --> 00:23:08.329
page 12. Right, but that veteran employee, the

00:23:08.329 --> 00:23:10.490
one knee -deep in it every day, they might come

00:23:10.490 --> 00:23:12.950
back with something completely different. Real,

00:23:12.970 --> 00:23:16.390
practical, tribal knowledge. Like? No, boss.

00:23:16.450 --> 00:23:18.970
The hardest thing is knowing exactly which specific

00:23:18.970 --> 00:23:21.710
wrench fits the calibration valve on the feed

00:23:21.710 --> 00:23:24.250
mixer without stripping the damn threads. Because

00:23:24.250 --> 00:23:27.170
that wrench isn't in the main toolbox. It's hidden

00:23:27.170 --> 00:23:29.849
in that rusty bucket next to the silo base. And

00:23:29.849 --> 00:23:31.970
if you use the wrong one, the calibration drifts

00:23:31.970 --> 00:23:34.430
and you waste expensive minerals. Exactly. That's

00:23:34.430 --> 00:23:35.829
the kind of gold you're looking for. That's the

00:23:35.829 --> 00:23:38.880
analyst angle on this. Asking that question does

00:23:38.880 --> 00:23:42.400
two things immediately. It exposes where assumptions

00:23:42.400 --> 00:23:45.059
and undocumented workarounds are replacing actual

00:23:45.059 --> 00:23:48.460
documented structure. And second, just by asking

00:23:48.460 --> 00:23:50.700
sincerely and listening without interrupting.

00:23:51.019 --> 00:23:53.900
You build trust. Huge trust. You build immediate

00:23:53.900 --> 00:23:56.140
trust. The workers realize that their practical,

00:23:56.359 --> 00:23:59.519
hands -on, tacit knowledge, the stuff that actually

00:23:59.519 --> 00:24:01.339
keeps the operation running smoothly despite

00:24:01.339 --> 00:24:03.900
the official procedures, sometimes actually matters

00:24:03.900 --> 00:24:06.480
to management. It shifts their perspective from

00:24:06.480 --> 00:24:08.859
just being, you know, cogs in a machine. To being

00:24:08.859 --> 00:24:11.819
recognized as operational experts, problem solvers.

00:24:11.980 --> 00:24:15.420
And that transition from just relying on tacit

00:24:15.420 --> 00:24:17.579
knowledge to actually getting it documented and

00:24:17.579 --> 00:24:21.119
turn into a reliable system, that leads directly

00:24:21.119 --> 00:24:23.880
to the economic impact of documentation we talked

00:24:23.880 --> 00:24:25.819
about earlier. Right, because producers here

00:24:25.819 --> 00:24:28.940
document procedures, write things down, and they

00:24:28.940 --> 00:24:31.599
often groan. They think of bureaucratic paperwork,

00:24:31.839 --> 00:24:34.039
more stuff they don't have time for. Understandable.

00:24:34.059 --> 00:24:36.799
But Penn State Extension actually quantified

00:24:36.799 --> 00:24:38.980
the benefit of this seemingly simple administrative

00:24:38.980 --> 00:24:42.819
task and the results. They're just too financially

00:24:42.819 --> 00:24:45.480
compelling to ignore, even if you hate paperwork.

00:24:45.880 --> 00:24:48.019
OK, what did Penn State find? Give us the numbers.

00:24:48.440 --> 00:24:50.980
They quantified it pretty precisely. They found

00:24:50.980 --> 00:24:53.319
that farms that took the time to implement systems

00:24:53.319 --> 00:24:56.059
for documenting even just five key tasks, they

00:24:56.059 --> 00:24:58.460
focus on things like feeding order, colostrum

00:24:58.460 --> 00:25:01.519
preparation, the main milking procedures, critical

00:25:01.519 --> 00:25:04.759
machinery setup like the parlor wash, and basic

00:25:04.759 --> 00:25:07.299
calf care protocols. So the big hitters, the

00:25:07.299 --> 00:25:10.440
really critical daily tasks. You know, not everything,

00:25:10.539 --> 00:25:13.390
just... the top five most crucial ones. Those

00:25:13.390 --> 00:25:16.309
farms reported training times that were 25 to

00:25:16.309 --> 00:25:18.970
40 percent faster within just six months of getting

00:25:18.970 --> 00:25:20.950
those visual documented procedures in place.

00:25:21.089 --> 00:25:25.539
25 to 40 percent faster training time. Okay,

00:25:25.559 --> 00:25:27.140
let's translate that back into that turnover

00:25:27.140 --> 00:25:29.980
cost we discussed, that $15 ,000 to $25 ,000

00:25:29.980 --> 00:25:32.660
hit every time someone leaves. Do the math. If

00:25:32.660 --> 00:25:35.059
I can cut the time it takes for a new hire to

00:25:35.059 --> 00:25:37.539
get up to speed, to reach full productivity where

00:25:37.539 --> 00:25:39.380
they're not making those costly tuition mistakes

00:25:39.380 --> 00:25:42.400
anymore, if I can cut that time by, say, a third.

00:25:42.759 --> 00:25:45.839
That's pure measurable savings right there. You're

00:25:45.839 --> 00:25:47.819
not only getting a functional, high -quality

00:25:47.819 --> 00:25:49.960
employee contributing positively much sooner,

00:25:50.119 --> 00:25:52.400
but you're also saving on the trainer's wages

00:25:52.400 --> 00:25:55.359
during that extended hand -holding period. And

00:25:55.359 --> 00:25:57.519
crucially, you're minimizing the duration of

00:25:57.519 --> 00:26:00.339
that vulnerable, low -quality tuition phase where

00:26:00.339 --> 00:26:02.740
costly errors happen. It pays for the effort

00:26:02.740 --> 00:26:05.019
of documentation very quickly. And it goes beyond

00:26:05.019 --> 00:26:07.339
just cost avoidance. It connects that crew knowledge

00:26:07.339 --> 00:26:10.569
directly to actual dairy output. Tangible revenue

00:26:10.569 --> 00:26:12.769
generation. Think about that Idaho producer mentioned

00:26:12.769 --> 00:26:14.809
in the sources. The one with the dry erase board.

00:26:14.930 --> 00:26:17.589
Yeah, such a simple idea. He gave his milkers

00:26:17.589 --> 00:26:20.190
a basic dry erase board right there in the parlor

00:26:20.190 --> 00:26:23.589
and asked them to just log claw fall -offs. Which

00:26:23.589 --> 00:26:26.369
unit, which cow, what time. Simple data capture.

00:26:26.670 --> 00:26:30.829
Okay, logging claw fall -offs. Low -tech. But

00:26:30.829 --> 00:26:33.190
powerful. Because the data is being captured

00:26:33.190 --> 00:26:36.650
by the people doing the work. In real time, right

00:26:36.650 --> 00:26:39.390
at the moment the issue occurs. Not relying on

00:26:39.390 --> 00:26:42.309
memory later. Exactly. And the crew used this

00:26:42.309 --> 00:26:44.690
simple feedback loop, just seeing the patterns

00:26:44.690 --> 00:26:46.490
emerge on the board day after day, to quickly

00:26:46.490 --> 00:26:48.910
identify they had a prep timing issue in one

00:26:48.910 --> 00:26:51.529
specific string of cows. Maybe they were waiting

00:26:51.529 --> 00:26:53.589
too long between prepping the udder and actually

00:26:53.589 --> 00:26:55.930
attaching the unit. Or maybe the stimulation

00:26:55.930 --> 00:26:58.230
wasn't consistent across all milkers. So they

00:26:58.230 --> 00:27:00.430
pinpointed the inconsistency. themselves. They

00:27:00.430 --> 00:27:02.789
did. They adjusted their timing based on the

00:27:02.789 --> 00:27:04.789
data they were seeing, got everyone on the same

00:27:04.789 --> 00:27:07.789
page for that string, and the result, they immediately

00:27:07.789 --> 00:27:11.069
boosted Butterfat performance by 0 .1 to 0 .2

00:27:11.069 --> 00:27:14.109
points specifically in that string. Hold on.

00:27:14.349 --> 00:27:18.829
0 .1 to 0 .2 points on Butterfat. Let's make

00:27:18.829 --> 00:27:20.670
sure everyone listening understands the significance

00:27:20.670 --> 00:27:22.829
of that. That's not just an academic number.

00:27:22.950 --> 00:27:25.480
No, that's real money. That is real revenue right

00:27:25.480 --> 00:27:28.839
now on every single hundred weight of milk sold

00:27:28.839 --> 00:27:31.900
from that group of cows. That translates directly

00:27:31.900 --> 00:27:35.259
into higher milk check premiums. And that extra

00:27:35.259 --> 00:27:38.200
revenue was generated purely from structuring

00:27:38.200 --> 00:27:40.740
the crew's input and improving the consistency

00:27:40.740 --> 00:27:43.119
of execution. The manager didn't have to buy

00:27:43.119 --> 00:27:45.720
a new software package, didn't have to cull cows

00:27:45.720 --> 00:27:48.460
or change genetics, didn't even have to tweak

00:27:48.460 --> 00:27:50.700
the feed commodity. They just formalized the

00:27:50.700 --> 00:27:52.779
feedback loop and helped the team improve their

00:27:52.779 --> 00:27:55.660
own execution. The cost -benefit analysis here

00:27:55.660 --> 00:27:58.200
seems like a no -brainer. Documenting key procedures,

00:27:58.480 --> 00:28:00.920
creating simple feedback loops, it costs virtually

00:28:00.920 --> 00:28:02.859
nothing compared to other investments. Maybe

00:28:02.859 --> 00:28:05.819
a bit of time, a camera for photos, a printer,

00:28:06.019 --> 00:28:09.079
a laminator. Pennies, really. But it saves significant

00:28:09.079 --> 00:28:12.380
training time, demonstrably reduces costly errors

00:28:12.380 --> 00:28:15.420
like mastitis or inconsistent feeding, and, as

00:28:15.420 --> 00:28:18.160
the Idaho example shows, can directly generate

00:28:18.160 --> 00:28:20.859
higher, more consistent product quality and revenue.

00:28:21.470 --> 00:28:25.430
The ROI on a simple visual SOP, it's got to be

00:28:25.430 --> 00:28:28.990
measured in weeks or months, not years. Okay,

00:28:29.049 --> 00:28:31.390
so we've hammered home the cost of ambiguity,

00:28:31.509 --> 00:28:33.970
the benefits of clarity, and we've touched on

00:28:33.970 --> 00:28:36.390
the, what, identifying knowledge gaps, documenting

00:28:36.390 --> 00:28:39.009
key tasks. Now let's get really practical about

00:28:39.009 --> 00:28:41.210
the how. Specifically, let's talk more about

00:28:41.210 --> 00:28:44.470
why these laminated photo SOPs seem to be so

00:28:44.470 --> 00:28:46.809
much more effective than, say, the traditional

00:28:46.809 --> 00:28:49.349
three -ring binder full of text, especially when

00:28:49.349 --> 00:28:51.990
you've got multilingual crews or just need quick

00:28:51.990 --> 00:28:54.130
reference in a busy environment. Right, the classic

00:28:54.130 --> 00:28:56.890
binder approach. It has its place, maybe for

00:28:56.890 --> 00:28:58.869
detailed maintenance logs or safety data sheets

00:28:58.869 --> 00:29:01.529
in the office, but for daily operational procedures,

00:29:01.809 --> 00:29:04.750
it often fails. Why? What's the fundamental flaw?

00:29:05.069 --> 00:29:07.109
Well, first, the traditional paper binder usually

00:29:07.109 --> 00:29:09.150
ends up on a shelf somewhere collecting dust,

00:29:09.289 --> 00:29:11.250
maybe in the break room, maybe in the farm office.

00:29:11.369 --> 00:29:13.130
It's not where the work actually happened. Out

00:29:13.130 --> 00:29:16.170
of sight, out of mind. Exactly. And in a wet,

00:29:16.230 --> 00:29:19.230
busy, often dimly lit dairy environment, think

00:29:19.230 --> 00:29:22.309
the parlor pit at 4 a .m. or the calf barn during

00:29:22.309 --> 00:29:25.049
feeding time. If the guide isn't easily accessible

00:29:25.049 --> 00:29:27.130
and usable right there at the point of work,

00:29:27.269 --> 00:29:29.470
it's essentially useless in the moment you need

00:29:29.470 --> 00:29:31.869
it most. Yeah, I can't stress that point of work

00:29:31.869 --> 00:29:34.730
concept enough. If I'm standing in the calf barn,

00:29:34.910 --> 00:29:37.509
maybe dealing with a sudden scours case, trying

00:29:37.509 --> 00:29:39.769
to remember the exact electrolyte mixing ratio,

00:29:39.990 --> 00:29:43.269
I don't have time nor the inclination to walk

00:29:43.269 --> 00:29:45.509
back to the office, find the binder, flip through

00:29:45.509 --> 00:29:48.170
20 pages of text. Forget it. No way. You need

00:29:48.170 --> 00:29:50.049
that information right there next to the mixing

00:29:50.049 --> 00:29:52.670
station, next to the buckets. And second, even

00:29:52.670 --> 00:29:54.710
if the binder was right there, if you have employees

00:29:54.710 --> 00:29:57.569
with literacy challenges or significant language

00:29:57.569 --> 00:30:00.849
barriers beyond just simple Spanish, text -heavy

00:30:00.849 --> 00:30:03.430
instructions are immediately defeated anyway.

00:30:03.849 --> 00:30:06.430
A picture is worth a thousand words, especially

00:30:06.430 --> 00:30:08.289
if those words are in language you don't fully

00:30:08.289 --> 00:30:10.670
understand. Research backs this up strongly.

00:30:10.930 --> 00:30:13.230
Studies from places like Iowa State and the University

00:30:13.230 --> 00:30:16.000
of Illinois have confirmed it. Visual direction

00:30:16.000 --> 00:30:18.460
significantly improves retention, comprehension,

00:30:18.839 --> 00:30:21.440
and reduces errors, especially when you're dealing

00:30:21.440 --> 00:30:24.640
with complex, multi -step procedures like milking

00:30:24.640 --> 00:30:28.099
prep or equipment sanitation. A photograph, especially

00:30:28.099 --> 00:30:31.599
if it clearly shows our familiar equipment, maybe

00:30:31.599 --> 00:30:34.279
even our actual co -workers performing the task

00:30:34.279 --> 00:30:37.220
correctly, that transcends language barriers.

00:30:38.089 --> 00:30:41.170
In a way, text just can't. If I see a clear photo

00:30:41.170 --> 00:30:43.890
sequence, step one, put on gloves. Step two,

00:30:44.009 --> 00:30:46.730
use this specific blue pre -dip. Step three,

00:30:46.809 --> 00:30:48.890
wipe with this type of towel. I get it instantly,

00:30:49.049 --> 00:30:51.029
regardless of my native language. Yeah, if I

00:30:51.029 --> 00:30:52.950
see a picture of the exact cleaning chemical

00:30:52.950 --> 00:30:55.670
bottle we use being poured into the specific

00:30:55.670 --> 00:30:57.950
measuring container we have, and that laminated

00:30:57.950 --> 00:30:59.630
picture is hanging right next to the chemical

00:30:59.630 --> 00:31:02.089
mixing station, I don't need a four -page explanation

00:31:02.089 --> 00:31:04.509
in three different languages. The image is the

00:31:04.509 --> 00:31:06.970
instruction. It's immediate. It's unambiguous.

00:31:07.470 --> 00:31:11.349
OK, so let's detail that proven four step visual

00:31:11.349 --> 00:31:14.029
SOP approach again, because this isn't complicated.

00:31:14.410 --> 00:31:17.170
This is an entirely actionable playbook that

00:31:17.170 --> 00:31:19.210
any farm listening can start implementing this

00:31:19.210 --> 00:31:21.410
week, regardless of their size or tech level.

00:31:21.470 --> 00:31:23.670
Give us the operational steps, step by step.

00:31:23.750 --> 00:31:26.849
Step one, photograph each critical step of the

00:31:26.849 --> 00:31:29.190
task exactly the way you want it done. And this

00:31:29.190 --> 00:31:32.579
is key. Use your real employees. your specific

00:31:32.579 --> 00:31:35.539
actual equipment in your barn environment. Not

00:31:35.539 --> 00:31:38.099
generic stock photos. Make it relevant. Absolutely.

00:31:38.440 --> 00:31:40.339
This builds immediate recognition and relevance.

00:31:40.660 --> 00:31:43.220
Seeing their coworker, their barn, their tools

00:31:43.220 --> 00:31:45.599
makes it instantly relatable and easier to follow.

00:31:45.900 --> 00:31:48.779
Use a picture of your calf barn, not some idealized

00:31:48.779 --> 00:31:51.660
drawing. Okay, step one, relevant photos. What's

00:31:51.660 --> 00:31:55.420
step two? Step two, write short, crystal clear

00:31:55.420 --> 00:31:57.900
captions for each photo. Keep it incredibly brief.

00:31:58.349 --> 00:32:00.809
One simple sentence or even just a key phrase

00:32:00.809 --> 00:32:03.730
per photo, maximum. Why so short? Because the

00:32:03.730 --> 00:32:05.509
photo should be doing 90 % of the communication

00:32:05.509 --> 00:32:08.329
work. The text is just there to clarify the action

00:32:08.329 --> 00:32:10.470
or highlight a critical detail, wait 30 seconds,

00:32:10.529 --> 00:32:14.609
or use one scoop. Minimal text. Got it. Photo

00:32:14.609 --> 00:32:17.569
carries the load, text clarifies. Step three.

00:32:17.809 --> 00:32:21.079
Step three. Translate those short, simple captions

00:32:21.079 --> 00:32:23.720
accurately into every primary language spoken

00:32:23.720 --> 00:32:26.279
by your crew. And this is crucial. Don't just

00:32:26.279 --> 00:32:28.579
rely on a quick Google Translate job, especially

00:32:28.579 --> 00:32:31.400
for technical dairy terms. Yeah, automated translations

00:32:31.400 --> 00:32:34.200
can be notoriously bad for specific industry

00:32:34.200 --> 00:32:36.799
jargon. Pre -dip might come out as something

00:32:36.799 --> 00:32:40.000
nonsensical. Exactly. It's worth the small effort

00:32:40.000 --> 00:32:42.460
to work with your local extension office or perhaps

00:32:42.460 --> 00:32:45.000
a trusted native -speaking employee or community

00:32:45.000 --> 00:32:48.690
member to get accurate, context -specific translations

00:32:48.690 --> 00:32:51.589
that make sense for terms like forest stripping,

00:32:51.630 --> 00:32:54.210
colostrum pasteurization, or specific chemical

00:32:54.210 --> 00:32:56.410
names. Get the translation right. Makes sense.

00:32:56.450 --> 00:32:58.930
Accurate translation is key. The final step,

00:32:59.029 --> 00:33:01.430
step four. Step four, and this is probably the

00:33:01.430 --> 00:33:03.569
most critical step for actual day -to -day usage.

00:33:03.769 --> 00:33:06.269
Hang the finished laminated cards exactly where

00:33:06.269 --> 00:33:08.369
the work is performed. Point of use. Point of

00:33:08.369 --> 00:33:11.450
work. Right there. Laminated, obviously, for

00:33:11.450 --> 00:33:14.230
durability against water, manure, and general

00:33:14.230 --> 00:33:17.380
wear and tear. Make them visible. Easily accessible.

00:33:17.859 --> 00:33:20.359
Calf feeding procedures go in the calf barn,

00:33:20.500 --> 00:33:22.480
maybe right by the pasteurizer or the feeding

00:33:22.480 --> 00:33:25.059
station. Parlor cleaning checklists go right

00:33:25.059 --> 00:33:27.180
next to the chemical station or the control panel.

00:33:27.339 --> 00:33:30.420
The consistency of placement is also key. So

00:33:30.420 --> 00:33:33.039
people build the habit of looking in that specific

00:33:33.039 --> 00:33:36.720
spot for guidance. Photos, captions, translate,

00:33:36.880 --> 00:33:39.420
hang. Seems straightforward enough. And this

00:33:39.420 --> 00:33:42.220
simple system yields results fast. We saw that

00:33:42.220 --> 00:33:44.539
measurable example from the sources. The Wisconsin

00:33:44.539 --> 00:33:47.380
dairy that used this exact visual aids approach.

00:33:47.640 --> 00:33:50.039
They reduced their parlor change over time, the

00:33:50.039 --> 00:33:51.940
downtime between shifts for cleaning and setup

00:33:51.940 --> 00:33:54.980
by nearly 20%. 20 % reduction in that idle time.

00:33:55.099 --> 00:33:57.480
That's huge. If you're milking three times a

00:33:57.480 --> 00:34:00.220
day, saving, say, 15 minutes between each shift,

00:34:00.359 --> 00:34:02.859
that's 45 minutes more available parlor time

00:34:02.859 --> 00:34:05.500
every single day. Or, maybe more importantly

00:34:05.500 --> 00:34:07.640
for morale, it allows the crew to finish their

00:34:07.640 --> 00:34:09.880
shift on time. consistently. Which, as we know,

00:34:09.940 --> 00:34:12.360
is massive for quality of life and employee retention.

00:34:12.679 --> 00:34:15.320
And beyond just the efficiency gains, the same

00:34:15.320 --> 00:34:18.019
process strengthened morale on that farm. When

00:34:18.019 --> 00:34:20.460
everyone knows the expectations clearly, visually,

00:34:20.780 --> 00:34:24.039
the confusion disappears, the frustration decreases,

00:34:24.159 --> 00:34:26.679
the blame game when something goes wrong tends

00:34:26.679 --> 00:34:28.760
to vanish because the standard is right there

00:34:28.760 --> 00:34:32.039
for everyone to see. Okay, so visual SOPs are

00:34:32.039 --> 00:34:35.630
powerful. Yeah. But having the SOP isn't enough

00:34:35.630 --> 00:34:37.989
if people aren't trained on it properly, right?

00:34:38.289 --> 00:34:40.730
This brings us to training verification. Yes.

00:34:40.889 --> 00:34:43.710
This is the other major failure point for management,

00:34:43.829 --> 00:34:46.730
even if they've created perfect visual SOPs.

00:34:46.949 --> 00:34:49.389
We fall into that incredibly common management

00:34:49.389 --> 00:34:52.469
trap. We explain the procedure, maybe even demonstrate

00:34:52.469 --> 00:34:54.489
it once, and then we ask the new employee, got

00:34:54.489 --> 00:34:56.409
it, do you understand? And they almost always

00:34:56.409 --> 00:34:58.769
nod yes. They almost always nod yes, especially

00:34:58.769 --> 00:35:01.900
across... language or cultural barriers, that

00:35:01.900 --> 00:35:04.139
nod often just means, yes, I understood your

00:35:04.139 --> 00:35:06.199
question. Or maybe, yes, I don't want to look

00:35:06.199 --> 00:35:08.820
stupid by saying no. It rarely means, yes, I

00:35:08.820 --> 00:35:11.239
have fully internalized every single step of

00:35:11.239 --> 00:35:13.519
that complex, multi -stage procedure you just

00:35:13.519 --> 00:35:15.400
rushed through. We've all done it. We're busy.

00:35:15.500 --> 00:35:17.349
We're rushed. We want to check the... training

00:35:17.349 --> 00:35:19.889
complete box on our mental checklist and move

00:35:19.889 --> 00:35:22.190
on to the next fire. And then a week later, you

00:35:22.190 --> 00:35:24.449
find out they've been doing a critical task like

00:35:24.449 --> 00:35:27.309
stripping the foremilk before attaching the unit

00:35:27.309 --> 00:35:31.250
or mixing the disinfecting completely wrong the

00:35:31.250 --> 00:35:34.610
entire time because they misunderstood one subtle

00:35:34.610 --> 00:35:37.510
but crucial step. And boom, there's that tuition

00:35:37.510 --> 00:35:40.530
Dr. Hagevord talked about biting you again. You're

00:35:40.530 --> 00:35:42.369
paying for that misunderstanding with higher

00:35:42.369 --> 00:35:45.309
SCC or equipment damage. So what's the better

00:35:45.309 --> 00:35:47.269
way? The sources highlight the gold standard

00:35:47.269 --> 00:35:50.349
used in adult education, health care, aviation,

00:35:50.889 --> 00:35:53.190
any high -stakes industry where mistakes are

00:35:53.190 --> 00:35:56.320
costly. It's the teach -back method. TeachPack.

00:35:56.360 --> 00:35:58.260
Okay, explain that. How does it work? It's simple

00:35:58.260 --> 00:36:01.260
in concept, but powerful in practice. You replace

00:36:01.260 --> 00:36:03.219
passive listening and hopeful guesswork with

00:36:03.219 --> 00:36:06.619
active, mandatory demonstration. Instead of asking

00:36:06.619 --> 00:36:09.699
if the employee understands the procedure, you

00:36:09.699 --> 00:36:12.659
ask them to show the procedure back to you, the

00:36:12.659 --> 00:36:15.159
trainer. Ah, so they have to perform the task

00:36:15.159 --> 00:36:17.880
themselves right there. Exactly. Step by step.

00:36:17.980 --> 00:36:21.019
And ideally, they should also explain why they

00:36:21.019 --> 00:36:23.619
are doing each step as they go. Okay, first I

00:36:23.619 --> 00:36:26.119
put on gloves because, then I dip with this because,

00:36:26.420 --> 00:36:29.280
then I wait 30 seconds because. That forces them

00:36:29.280 --> 00:36:32.059
to process it, not just mimic. It's the difference

00:36:32.059 --> 00:36:35.280
between passively watching a YouTube video and

00:36:35.280 --> 00:36:37.780
actually having to assemble the IKEA furniture

00:36:37.780 --> 00:36:41.360
yourself. You learn by doing. It's entirely about

00:36:41.360 --> 00:36:43.559
ownership and active processing. We saw that

00:36:43.559 --> 00:36:45.559
quote from the Ontario Herdsman in the materials,

00:36:45.820 --> 00:36:48.380
capturing the psychology perfectly. He said something

00:36:48.380 --> 00:36:50.579
like, When you ask me to show you and explain

00:36:50.579 --> 00:36:52.860
why I'm doing each step, I pay attention completely

00:36:52.860 --> 00:36:54.820
differently than if I'm just standing there watching

00:36:54.820 --> 00:36:57.059
someone else demonstrate. It sticks better because

00:36:57.059 --> 00:36:59.059
you have to engage your brain and your body.

00:36:59.179 --> 00:37:01.760
It builds deep ownership, confirms understanding,

00:37:02.099 --> 00:37:04.159
and builds their confidence because they've successfully

00:37:04.159 --> 00:37:07.300
demonstrated competence. And crucially, multiple

00:37:07.300 --> 00:37:10.300
studies confirmed by researchers at MSU, Gulf,

00:37:10.460 --> 00:37:12.780
Cornell show that consistently using the teach

00:37:12.780 --> 00:37:15.380
-back method significantly reduces those repeated

00:37:15.380 --> 00:37:17.139
errors that stem from initial misunderstanding.

00:37:17.980 --> 00:37:19.920
Okay, so it makes training more effective, reduces

00:37:19.920 --> 00:37:22.880
mistakes. That makes intuitive sense. But does

00:37:22.880 --> 00:37:25.539
it have a measurable impact on herd health, for

00:37:25.539 --> 00:37:27.920
example? This leads us right back to that most

00:37:27.920 --> 00:37:30.440
quantifiable health impact we teased at the very

00:37:30.440 --> 00:37:32.639
beginning. The one that I think is probably the

00:37:32.639 --> 00:37:35.159
most compelling single piece of data in this

00:37:35.159 --> 00:37:37.539
entire deep dive. The scours reduction number.

00:37:37.719 --> 00:37:39.780
Exactly. When University of Wisconsin researchers

00:37:39.780 --> 00:37:43.320
specifically applied this system, visual SOPs

00:37:43.320 --> 00:37:45.840
combined with mandatory teach -back training

00:37:45.840 --> 00:37:49.769
to calf... feeding protocols, which, as you know,

00:37:49.809 --> 00:37:53.010
rely so heavily on perfect, precise consistency,

00:37:53.389 --> 00:37:56.250
especially with colostrum handling. Yeah, colostrum

00:37:56.250 --> 00:37:58.550
is ground zero for calf health. Get that wrong,

00:37:58.630 --> 00:38:00.469
and you're fighting an uphill battle. What they

00:38:00.469 --> 00:38:04.550
found was dramatic. Game -changing, really. Farms

00:38:04.550 --> 00:38:06.710
that implemented the teach -back method rigorously

00:38:06.710 --> 00:38:08.989
for colostrum handling and general calf feeding

00:38:08.989 --> 00:38:12.789
procedures saw 50 to 70 percent fewer scours

00:38:12.789 --> 00:38:16.289
treatments needed. 50. To 70%. Fewer vet calls,

00:38:16.449 --> 00:38:18.869
less medication, fewer sick days for those calves.

00:38:19.150 --> 00:38:22.789
That is not a small marginal gain. That's a fundamental

00:38:22.789 --> 00:38:24.889
transformation in calf health outcome. It's huge.

00:38:24.989 --> 00:38:26.710
Let's quickly analyze the financial implications

00:38:26.710 --> 00:38:29.769
of that. A single scours case isn't cheap. You've

00:38:29.769 --> 00:38:32.170
got the immediate labor cost extra care, maybe

00:38:32.170 --> 00:38:34.349
separation. You've got the potential vet visit

00:38:34.349 --> 00:38:36.889
cost. You've got the medication cost. Easily

00:38:36.889 --> 00:38:40.369
$50, $100 per case, sometimes more. Right. But

00:38:40.369 --> 00:38:42.710
the long -term cost is often even higher, isn't

00:38:42.710 --> 00:38:46.750
it? A calf. that battles severe scours, even

00:38:46.750 --> 00:38:49.469
if it survives. Yeah. It often is delayed growth,

00:38:49.750 --> 00:38:52.150
lower weight gain, compromised gut development.

00:38:52.309 --> 00:38:54.849
Which can translate directly into lower first

00:38:54.849 --> 00:38:56.929
lactation milk production, maybe delayed breeding,

00:38:57.130 --> 00:39:00.010
lower lifetime potential for that animal you've

00:39:00.010 --> 00:39:02.610
invested so much in raising. So cutting the incidence

00:39:02.610 --> 00:39:06.000
of scours by up to 70%. You're not just saving

00:39:06.000 --> 00:39:07.659
those immediate treatment costs. You are saving

00:39:07.659 --> 00:39:09.840
thousands of dollars in current expenses and

00:39:09.840 --> 00:39:11.719
you are fundamentally securing the long -term

00:39:11.719 --> 00:39:13.980
productivity and profitability of your entire

00:39:13.980 --> 00:39:16.519
replacement heifer pool. It effectively purrs

00:39:16.519 --> 00:39:18.860
the point. Inconsistent colostrum management,

00:39:19.119 --> 00:39:21.699
which is almost always a direct result of communication

00:39:21.699 --> 00:39:24.380
and training failures, is likely one of the single

00:39:24.380 --> 00:39:26.900
most expensive hidden costs on many dairy farms.

00:39:27.119 --> 00:39:30.760
And fixing that one critical procedure through

00:39:30.760 --> 00:39:33.500
clear visual SOPs and verifying understanding

00:39:33.500 --> 00:39:37.679
with a teach back method delivers massive quantifiable

00:39:37.679 --> 00:39:40.280
returns, both in immediate savings and in future

00:39:40.280 --> 00:39:42.480
farm profitability. It's hard to argue with numbers

00:39:42.480 --> 00:39:44.889
like that. Okay, so we've established how to

00:39:44.889 --> 00:39:47.429
build the system visual SOPs. We know how to

00:39:47.429 --> 00:39:49.750
train the people effectively, the teach -back

00:39:49.750 --> 00:39:53.110
method. But systems, just like equipment, they

00:39:53.110 --> 00:39:54.809
need maintenance, right? They're not static.

00:39:55.130 --> 00:39:57.989
Absolutely. Even the best, most beautifully laminated

00:39:57.989 --> 00:40:01.130
SOPs can get dusty. Or worse, they get ignored.

00:40:01.530 --> 00:40:04.050
Or maybe most commonly, they simply become outdated

00:40:04.050 --> 00:40:06.750
without anyone realizing it. How does that happen?

00:40:06.829 --> 00:40:09.199
Well, the farm changes. You introduce a new cleaning

00:40:09.199 --> 00:40:11.280
chemical that requires a different contact time.

00:40:11.400 --> 00:40:13.719
You rearrange the layout of the calf barn so

00:40:13.719 --> 00:40:15.800
the old procedure photos don't quite match reality

00:40:15.800 --> 00:40:18.059
anymore. You replace a piece of equipment and

00:40:18.059 --> 00:40:20.219
the startup sequence is slightly different. Small

00:40:20.219 --> 00:40:22.699
changes add up. And if the SOPs aren't updated

00:40:22.699 --> 00:40:25.179
to reflect those changes, they lose credibility.

00:40:25.929 --> 00:40:28.050
Exactly. That's compliance fatigue setting in.

00:40:28.110 --> 00:40:30.530
It's a killer for long -term consistency. You

00:40:30.530 --> 00:40:32.710
put in all this effort up front to create the

00:40:32.710 --> 00:40:35.329
perfect laminated protocol. Everyone feels good

00:40:35.329 --> 00:40:37.670
about it for a while. Check the box. Done. Yeah.

00:40:37.929 --> 00:40:41.730
And then six months, a year later. It's just

00:40:41.730 --> 00:40:43.889
become background noise, wallpaper that the crew

00:40:43.889 --> 00:40:47.369
walks past every day. And slowly, subtly, people

00:40:47.369 --> 00:40:49.550
start reverting back to doing things the old

00:40:49.550 --> 00:40:52.349
way, the comfortable way, the potentially inconsistent

00:40:52.349 --> 00:40:56.449
way again. The system decays. So how do you combat

00:40:56.449 --> 00:40:59.010
that inevitable entropy? How do you keep the

00:40:59.010 --> 00:41:01.550
system alive and relevant? The source material

00:41:01.550 --> 00:41:04.190
highlighted a recommendation from Cornell's ProDairy

00:41:04.190 --> 00:41:06.150
program that I really liked. They suggest implementing

00:41:06.150 --> 00:41:08.760
short, regular. Protocol walks. Protocol walks.

00:41:08.820 --> 00:41:10.579
Okay, what does that entail? Is it another meeting?

00:41:10.820 --> 00:41:13.219
No. And that's the beauty of it. It's specifically

00:41:13.219 --> 00:41:16.059
designed not to be another long, formal sit -down

00:41:16.059 --> 00:41:18.579
meeting that everyone dreads. Good. Keep it practical.

00:41:18.800 --> 00:41:20.719
It's meant to be short and action -oriented.

00:41:21.159 --> 00:41:23.539
Maybe just 10 to 15 minutes once every quarter

00:41:23.539 --> 00:41:27.219
or so. Management literally walks the barn with

00:41:27.219 --> 00:41:29.820
the relevant team members for a specific process,

00:41:29.920 --> 00:41:33.059
say the milking crew in the parlor. Okay, walking

00:41:33.059 --> 00:41:35.679
the process area, what's the purpose? The core

00:41:35.679 --> 00:41:38.780
purpose is to look at the posted visual SOP for

00:41:38.780 --> 00:41:41.760
that area together and ask one simple, critical

00:41:41.760 --> 00:41:45.199
question. Okay team, looking at this procedure

00:41:45.199 --> 00:41:48.239
card from three months ago, what, if anything,

00:41:48.440 --> 00:41:51.170
has actually changed? in how we do this job since

00:41:51.170 --> 00:41:54.090
then. Ah, so it's a direct reality check against

00:41:54.090 --> 00:41:57.050
the documented standard. Exactly. Have we switched

00:41:57.050 --> 00:41:59.570
the brand of pre -dip sanitizer? Does it require

00:41:59.570 --> 00:42:02.090
a different contact time now? Is this vacuum

00:42:02.090 --> 00:42:04.170
pump making a weird noise lately that affects

00:42:04.170 --> 00:42:06.710
the procedure? Did we change how we dump the

00:42:06.710 --> 00:42:08.849
waste milk because of the new tank? It's about

00:42:08.849 --> 00:42:11.030
identifying those small drifts from the standard.

00:42:11.250 --> 00:42:13.710
The psychology of doing it as a walk right there

00:42:13.710 --> 00:42:15.429
in the work environment seems important too.

00:42:15.710 --> 00:42:17.789
I think it's brilliant. It avoids that meeting

00:42:17.789 --> 00:42:20.210
fatigue. and the feeling of being lectured at

00:42:20.210 --> 00:42:23.070
in an office. Management is showing they care

00:42:23.070 --> 00:42:25.210
enough to come out, look at the process with

00:42:25.210 --> 00:42:27.429
the team, and acknowledge that things change.

00:42:27.789 --> 00:42:29.889
It shows that protocols are meant to be updated

00:42:29.889 --> 00:42:32.849
collaboratively, not just enforced rigidly from

00:42:32.849 --> 00:42:36.489
the top down. It validates the crew's daily reality

00:42:36.489 --> 00:42:39.170
and acknowledges that the system has to adapt

00:42:39.170 --> 00:42:41.630
to the ground -level changes that they experience

00:42:41.630 --> 00:42:44.650
every single day. They're the ones who know if

00:42:44.650 --> 00:42:46.590
the new sanitizer bottle has a different cap

00:42:46.590 --> 00:42:49.329
that's harder to open. Right. And this whole

00:42:49.329 --> 00:42:52.130
shift from just documenting once to proactively

00:42:52.130 --> 00:42:55.010
reviewing and updating together, it fundamentally

00:42:55.010 --> 00:42:56.869
changes the role of the employee, doesn't it?

00:42:56.909 --> 00:42:59.789
It moves them from just being labor who follows

00:42:59.789 --> 00:43:02.090
instructions. Towards leadership or at least

00:43:02.090 --> 00:43:04.349
ownership of the process. Exactly. You're no

00:43:04.349 --> 00:43:06.329
longer just asking them to follow orders blindly.

00:43:06.690 --> 00:43:09.329
You're implicitly asking them to help manage

00:43:09.329 --> 00:43:11.829
the integrity of the system itself, to be the

00:43:11.829 --> 00:43:14.969
eyes and ears that notice when the SOP doesn't

00:43:14.969 --> 00:43:17.579
match reality anymore. You're essentially investing

00:43:17.579 --> 00:43:20.219
in their brain power, their observational skills,

00:43:20.460 --> 00:43:23.760
their on -the -ground expertise, which frankly

00:43:23.760 --> 00:43:25.699
is far more valuable in the long run than just

00:43:25.699 --> 00:43:28.460
their physical output. You're cultivating a culture

00:43:28.460 --> 00:43:31.139
where improvement ideas can actually surface

00:43:31.139 --> 00:43:33.909
from the bottom up. rather than always having

00:43:33.909 --> 00:43:36.170
to be dictated from the top down. And there's

00:43:36.170 --> 00:43:38.530
data to support this shift in investment, too.

00:43:38.670 --> 00:43:41.750
More research from Cornell. They found that farms

00:43:41.750 --> 00:43:43.929
that actively allowed employees to participate

00:43:43.929 --> 00:43:46.630
in protocol revisions, farms where employees

00:43:46.630 --> 00:43:49.650
could actually say, hey, the new sanitizer needs

00:43:49.650 --> 00:43:53.369
15 seconds contact time, not 10. So we need to

00:43:53.369 --> 00:43:56.099
adjust step three on the card. So giving them

00:43:56.099 --> 00:43:58.820
real input into the system design. Those farms

00:43:58.820 --> 00:44:00.880
saw adoption rates for the revised protocols

00:44:00.880 --> 00:44:03.880
jump by nearly one -third. Wow, a third higher

00:44:03.880 --> 00:44:06.260
adoption just by involving them in the update.

00:44:06.500 --> 00:44:08.760
It makes perfect sense psychologically. People

00:44:08.760 --> 00:44:11.460
fiercely respect, defend, and adhere to processes

00:44:11.460 --> 00:44:13.460
that they feel they helped create or improve.

00:44:13.880 --> 00:44:16.219
That is the absolute core principle of ownership,

00:44:16.360 --> 00:44:19.840
isn't it? If I feel like my experience, my suggestion,

00:44:20.019 --> 00:44:22.780
was actually heard and incorporated into how

00:44:22.780 --> 00:44:25.880
we handle fresh cows now. I'm going to make damn

00:44:25.880 --> 00:44:27.940
sure that process is followed correctly. I'll

00:44:27.940 --> 00:44:30.079
train the new hires on it properly. I'll speak

00:44:30.079 --> 00:44:32.380
up immediately if I see someone deviating from

00:44:32.380 --> 00:44:34.940
it. It becomes our process, not just the boss's

00:44:34.940 --> 00:44:38.139
process. That Idaho producer logging the claw

00:44:38.139 --> 00:44:40.559
fall -offs on the whiteboard is another perfect

00:44:40.559 --> 00:44:44.179
example of this wider view in action. He empowered

00:44:44.179 --> 00:44:46.400
his team to collect data and identify problems.

00:44:46.880 --> 00:44:49.139
It all comes back to communication being the

00:44:49.139 --> 00:44:51.599
fundamental backbone. It supports every other

00:44:51.599 --> 00:44:53.760
operational improvement effort you might undertake,

00:44:53.960 --> 00:44:56.039
whether it's fine -tuning fresh cow management,

00:44:56.280 --> 00:44:58.619
adjusting nutrition based on performance, or

00:44:58.619 --> 00:45:01.139
implementing new health protocols. You can't

00:45:01.139 --> 00:45:03.539
effectively improve what you can't measure accurately,

00:45:03.760 --> 00:45:06.019
and you absolutely cannot measure accurately

00:45:06.019 --> 00:45:08.239
if your team isn't executing procedures consistently

00:45:08.239 --> 00:45:10.739
or isn't comfortable giving you honest feedback

00:45:10.739 --> 00:45:13.699
through clear, formalized channels. If the crew

00:45:13.699 --> 00:45:15.599
is consistently applying the right protocols

00:45:15.599 --> 00:45:18.440
because they're clear and own and they feel comfortable

00:45:18.440 --> 00:45:20.599
reporting issues accurately, like logging those

00:45:20.599 --> 00:45:23.239
fall -offs or noting down feed refusals, then

00:45:23.239 --> 00:45:26.119
the manager receives cleaner, more reliable data

00:45:26.119 --> 00:45:28.139
about what's really happening with the herd,

00:45:28.280 --> 00:45:30.519
which leads to better insights, better decision

00:45:30.519 --> 00:45:33.380
-making overall, and ultimately a more profitable,

00:45:33.539 --> 00:45:36.980
smoother running operation. It's this virtuous

00:45:36.980 --> 00:45:39.719
cycle, all starting with clarity and ownership.

00:45:40.590 --> 00:45:42.849
Okay, now let's tackle the inevitable comparison

00:45:42.849 --> 00:45:45.829
that always comes up. North American dairy producers,

00:45:45.929 --> 00:45:48.769
we often look... across the pond right towards

00:45:48.769 --> 00:45:50.909
european systems especially places like denmark

00:45:50.909 --> 00:45:53.349
or the netherlands they're often held up as the

00:45:53.349 --> 00:45:55.289
gold standard for things like labor efficiency

00:45:55.289 --> 00:45:58.829
really low cow to labor ratios advanced training

00:45:58.829 --> 00:46:00.929
programs yeah you hear about these farms running

00:46:00.929 --> 00:46:03.590
huge numbers of cows with just a handful of highly

00:46:03.590 --> 00:46:05.869
skilled people it sounds almost unbelievable

00:46:05.869 --> 00:46:08.170
sometimes compared to our typical structures

00:46:08.170 --> 00:46:10.610
so the natural question arises should we just

00:46:10.610 --> 00:46:12.710
try to wholesale copy what they're doing if it

00:46:12.710 --> 00:46:14.949
works so well there why not just import their

00:46:14.949 --> 00:46:18.289
model well The short answer, based on the sources

00:46:18.289 --> 00:46:22.250
and just practical reality, is probably no. Not

00:46:22.250 --> 00:46:25.670
a direct copy -paste. Context is absolutely everything

00:46:25.670 --> 00:46:27.389
here. Why not? What are the key differences?

00:46:27.730 --> 00:46:29.949
Our regulatory environment is different. Our

00:46:29.949 --> 00:46:32.190
economic pressures are different. And critically,

00:46:32.449 --> 00:46:35.090
our labor pool and training infrastructure are

00:46:35.090 --> 00:46:37.150
wildly different from what they have in many

00:46:37.150 --> 00:46:39.690
parts of the EU, particularly those leading countries.

00:46:40.230 --> 00:46:42.750
We have to acknowledge the superior systems they've

00:46:42.750 --> 00:46:45.800
often built. Admire them, even. But then be smart

00:46:45.800 --> 00:46:48.500
about it. Surgically adapt the principles that

00:46:48.500 --> 00:46:50.860
make them successful, not just try to mimic the

00:46:50.860 --> 00:46:53.039
rigid structures without the supporting foundations.

00:46:53.400 --> 00:46:55.760
Exactly. First, let's acknowledge the differences.

00:46:56.079 --> 00:46:58.059
Countries like Denmark and the Netherlands, they

00:46:58.059 --> 00:47:00.059
often operate with extremely high standards,

00:47:00.219 --> 00:47:02.280
yes, but also different structures. You might

00:47:02.280 --> 00:47:05.900
see farms running 100, 130, maybe more cows per

00:47:05.900 --> 00:47:08.880
just two to four employees. But those employees

00:47:08.880 --> 00:47:11.019
are often highly trained, specialized professionals.

00:47:11.639 --> 00:47:14.039
And crucially, they often benefit from established

00:47:14.039 --> 00:47:16.360
national certification programs, right? Like

00:47:16.360 --> 00:47:19.380
Sieges Innovation in Denmark or the programs

00:47:19.380 --> 00:47:21.880
linked to Wageningen University in the Netherlands.

00:47:22.179 --> 00:47:25.039
Correct. Their farm training is often tightly

00:47:25.039 --> 00:47:27.780
integrated with formal vocational colleges and

00:47:27.780 --> 00:47:30.880
research institutions. The training is institutionalized,

00:47:30.940 --> 00:47:33.179
it's standardized across the country, and it's

00:47:33.179 --> 00:47:35.860
often subsidized or heavily supported by industry

00:47:35.860 --> 00:47:38.329
groups or government. So a new employee arriving

00:47:38.329 --> 00:47:40.710
on a top Danish farm doesn't just show up with

00:47:40.710 --> 00:47:42.789
a willingness to work. They might arrive with

00:47:42.789 --> 00:47:45.269
a nationally accredited certification in, say,

00:47:45.389 --> 00:47:47.809
advanced milking parlor management or robotic

00:47:47.809 --> 00:47:51.269
system operation or detailed animal welfare standards.

00:47:51.349 --> 00:47:55.199
We simply do not have that same level of... deeply

00:47:55.199 --> 00:47:57.679
integrated, institutionalized, standardized training

00:47:57.679 --> 00:48:00.400
support across the board here in North America.

00:48:00.559 --> 00:48:02.760
Nor do we generally have the same kind of labor

00:48:02.760 --> 00:48:05.059
pool homogeneity or the same cultural expectation

00:48:05.059 --> 00:48:08.039
around vocational training for agriculture. So

00:48:08.039 --> 00:48:10.840
just attempting to cut staff drastically to match

00:48:10.840 --> 00:48:13.679
those incredibly high European cow -to -labor

00:48:13.679 --> 00:48:16.659
ratios without first having that bedrock of standardized

00:48:16.659 --> 00:48:19.000
training, visual communication systems, and maybe

00:48:19.000 --> 00:48:21.829
even different facility designs. It would likely

00:48:21.829 --> 00:48:24.530
be catastrophic for most U .S. or Canadian operations.

00:48:24.849 --> 00:48:27.989
You wouldn't get efficiency. You'd just magnify

00:48:27.989 --> 00:48:30.449
the existing ambiguity, overload the remaining

00:48:30.449 --> 00:48:33.090
staff, burn them out faster, and probably send

00:48:33.090 --> 00:48:35.670
that $25 ,000 turnover cost through the roof.

00:48:35.829 --> 00:48:38.889
Okay, so direct copying is out. If we can't just

00:48:38.889 --> 00:48:41.550
import their entire vocational training structure,

00:48:41.889 --> 00:48:44.909
what can North American farms practically take

00:48:44.909 --> 00:48:47.389
away from these highly efficient European models?

00:48:47.510 --> 00:48:50.599
What are the adaptable principles? We can definitely

00:48:50.599 --> 00:48:52.800
borrow some of the actionable diagnostic principles

00:48:52.800 --> 00:48:55.199
and the cultural mindset they use to maintain

00:48:55.199 --> 00:48:58.119
that high level of operational clarity and continuous

00:48:58.119 --> 00:49:00.699
improvement. Like what? Give us an example. A

00:49:00.699 --> 00:49:02.780
perfect example mentioned was the Dutch cow signals

00:49:02.780 --> 00:49:05.619
training methodology. It's a whole system, but

00:49:05.619 --> 00:49:08.699
one of its core, easily adaptable concepts is

00:49:08.699 --> 00:49:10.980
built on simplicity and employee engagement.

00:49:11.239 --> 00:49:13.880
They often encourage practices like asking employees

00:49:13.880 --> 00:49:16.199
to identify just one small improvement idea.

00:49:16.639 --> 00:49:18.860
Each week. One improvement idea per employee

00:49:18.860 --> 00:49:21.019
per week. That sounds manageable. It's about

00:49:21.019 --> 00:49:24.239
fostering a fundamental shift towards continuous,

00:49:24.239 --> 00:49:26.880
small scale, incremental process improvement

00:49:26.880 --> 00:49:29.539
driven by the people actually doing the work.

00:49:30.099 --> 00:49:33.000
not waiting for a major overhaul every five years.

00:49:33.139 --> 00:49:35.420
And we can adapt that idea immediately, right?

00:49:35.539 --> 00:49:38.119
Without needing any government programs or industry

00:49:38.119 --> 00:49:40.860
-wide certifications? Absolutely. We don't need

00:49:40.860 --> 00:49:44.119
a full -blown Dutch certification system to implement

00:49:44.119 --> 00:49:47.039
the principle of regular solicited employee feedback.

00:49:47.320 --> 00:49:49.239
We could adapt it through something as simple

00:49:49.239 --> 00:49:51.820
as those five -minute Friday crew check -ins

00:49:51.820 --> 00:49:53.539
we talked about earlier. Five minutes at the

00:49:53.539 --> 00:49:55.739
end of the week? That seems totally doable. Just

00:49:55.739 --> 00:49:58.539
ask. Okay, team, looking back at this week, what's

00:49:58.539 --> 00:50:00.719
one thing that slowed you down unnecessarily?

00:50:00.900 --> 00:50:03.320
What's one little thing we can maybe change next

00:50:03.320 --> 00:50:06.119
week? Could be a tool, a process step, where

00:50:06.119 --> 00:50:08.119
something is stored that would make your job

00:50:08.119 --> 00:50:11.159
easier, safer, or more consistent. This simple

00:50:11.159 --> 00:50:14.099
routine keeps the team thinking proactively about

00:50:14.099 --> 00:50:16.500
improvements, which, as we've established repeatedly,

00:50:16.940 --> 00:50:19.380
is far, far cheaper than the purely reactive

00:50:19.380 --> 00:50:21.989
management style. The one that only scrambles

00:50:21.989 --> 00:50:24.710
to respond after the SEC spikes or after the

00:50:24.710 --> 00:50:27.690
calf scours outbreak or after the employee turnover

00:50:27.690 --> 00:50:30.250
rate hits 30 percent because people are frustrated

00:50:30.250 --> 00:50:32.750
and stressed out by inefficient systems. The

00:50:32.750 --> 00:50:34.789
entire discussion, really, it seems to pivot

00:50:34.789 --> 00:50:37.130
on this one powerful idea captured perfectly

00:50:37.130 --> 00:50:39.809
by Dr. Jessica Pempek from Ohio State. She said,

00:50:39.889 --> 00:50:43.530
we spend months, even years, designing intricate

00:50:43.530 --> 00:50:46.960
systems for cows. Communication is about finally

00:50:46.960 --> 00:50:49.539
designing systems for people. That hits the nail

00:50:49.539 --> 00:50:52.239
on the head. We've become masters of cow biology,

00:50:52.460 --> 00:50:55.639
cow comfort, cow nutrition, the next great frontier

00:50:55.639 --> 00:50:57.820
for efficiency and profitability in dairying.

00:50:57.900 --> 00:51:00.880
It's mastering the human system interface, designing

00:51:00.880 --> 00:51:02.940
workflows and communication structures that support

00:51:02.940 --> 00:51:05.719
our people as effectively as we support our cows.

00:51:05.860 --> 00:51:08.079
This next phase of improvement in the dairy industry,

00:51:08.400 --> 00:51:10.480
it really feels like it's going to be a human

00:51:10.480 --> 00:51:12.980
system built revolution, not just another equipment

00:51:12.980 --> 00:51:15.789
built one. Agreed. The ultimate payoff isn't

00:51:15.789 --> 00:51:18.550
just better management efficiency or higher employee

00:51:18.550 --> 00:51:21.250
retention, though those are huge benefits. It's

00:51:21.250 --> 00:51:24.449
creating a thriving, stable, consistent operation

00:51:24.449 --> 00:51:27.750
where the cows ultimately benefit the most from

00:51:27.750 --> 00:51:30.349
predictable, high -quality care day in and day

00:51:30.349 --> 00:51:32.750
out. There is that final quote from a Wisconsin

00:51:32.750 --> 00:51:34.769
producer in the materials that summed it all

00:51:34.769 --> 00:51:37.469
up beautifully. Once people understand each other,

00:51:37.610 --> 00:51:39.849
the cows take care of the rest. I love that.

00:51:40.320 --> 00:51:42.300
It suggests that if you get the human element

00:51:42.300 --> 00:51:44.699
right, the clarity, the consistency, the communication,

00:51:45.000 --> 00:51:48.199
the respect, the biological system, the herd

00:51:48.199 --> 00:51:50.639
itself, will naturally perform better. And this

00:51:50.639 --> 00:51:53.460
quiet revolution focusing on communication infrastructure,

00:51:54.000 --> 00:51:56.679
it's affordable. It can literally start tomorrow

00:51:56.679 --> 00:51:58.920
morning with just asking one good question. It

00:51:58.920 --> 00:52:01.119
applies regardless of whether you're running

00:52:01.119 --> 00:52:04.539
50 cows or 5 ,000, T -Stall or robots. It really

00:52:04.539 --> 00:52:06.820
is the core infrastructure. The foundation supporting

00:52:06.820 --> 00:52:09.219
every single other dollar you spend on this farm.

00:52:09.639 --> 00:52:12.199
Hashtag tag actionable insight segment. All right.

00:52:12.260 --> 00:52:14.679
You've just finished morning milking. Maybe you're

00:52:14.679 --> 00:52:16.539
driving to the feed store or heading out to check

00:52:16.539 --> 00:52:18.400
heifers. You've absorbed all this data, all these

00:52:18.400 --> 00:52:21.260
ideas. The potential profit locked up in better

00:52:21.260 --> 00:52:24.039
communication and consistency is clearly huge.

00:52:24.539 --> 00:52:27.619
So let's boil it down. What are the three most

00:52:27.619 --> 00:52:29.900
critical, actionable things you need to take

00:52:29.900 --> 00:52:32.280
away and actually do based on this deep dive?

00:52:32.460 --> 00:52:35.019
What's the immediate, the median term and the

00:52:35.019 --> 00:52:37.679
long term play? Okay. Immediate action. And I

00:52:37.679 --> 00:52:40.159
mean this week. Before the next shift change,

00:52:40.400 --> 00:52:42.559
if possible, start with that diagnostic question

00:52:42.559 --> 00:52:44.280
we talked about. The one for the veteran employee.

00:52:44.519 --> 00:52:47.340
Yes. Find your longest standing, most trusted

00:52:47.340 --> 00:52:49.500
employee, the one who really knows the ropes,

00:52:49.639 --> 00:52:52.719
and ask them sincerely, what is the single hardest

00:52:52.719 --> 00:52:55.599
thing for someone new to learn around here that

00:52:55.599 --> 00:52:57.300
is not clearly written down or shown somewhere?

00:52:57.539 --> 00:53:00.630
And then the most important part, listen. Listen

00:53:00.630 --> 00:53:02.769
without interrupting. Your goal right now is

00:53:02.769 --> 00:53:05.130
just diagnosis, identifying those hidden knowledge

00:53:05.130 --> 00:53:07.369
gaps, those areas where institutional memory

00:53:07.369 --> 00:53:09.710
is vulnerable and undocumented. Don't try to

00:53:09.710 --> 00:53:12.829
fix it yet. Just identify it. OK, so step one,

00:53:12.949 --> 00:53:16.429
ask the question. Listen hard. Diagnose the hidden

00:53:16.429 --> 00:53:19.170
gaps. What's the medium term strategy? Thinking

00:53:19.170 --> 00:53:21.559
maybe the next three to six months out. Medium

00:53:21.559 --> 00:53:24.079
term, you need to start building the visual infrastructure.

00:53:24.599 --> 00:53:27.460
Commit to implementing clear, laminated visual

00:53:27.460 --> 00:53:30.920
SOPs for probably the five most critical, high

00:53:30.920 --> 00:53:33.920
impact, high cost tasks on your farm. Which five

00:53:33.920 --> 00:53:36.420
would you prioritize typically? It'll vary a

00:53:36.420 --> 00:53:37.980
bit farm to farm, but generally you're looking

00:53:37.980 --> 00:53:40.780
at things like the full milking procedure. prep,

00:53:40.980 --> 00:53:43.199
attachment post -dip, colostrum collection and

00:53:43.199 --> 00:53:45.960
feeding, fresh cow observation protocols, maybe

00:53:45.960 --> 00:53:47.900
critical equipment setup like the parlor wash

00:53:47.900 --> 00:53:50.780
sequence, and basic calf care routines like feeding

00:53:50.780 --> 00:53:52.880
and bedding. The things done every day where

00:53:52.880 --> 00:53:55.500
inconsistency costs the most. And focus specifically

00:53:55.500 --> 00:53:58.280
on that four -step process we detailed. Absolutely.

00:53:58.380 --> 00:54:01.599
Use the four -step process. Get good photos using

00:54:01.599 --> 00:54:04.900
your people and gear. Write minimal, clear captions.

00:54:05.000 --> 00:54:07.380
Get accurate translations for all crew languages.

00:54:07.840 --> 00:54:11.119
And... Hang the laminated cards at the point

00:54:11.119 --> 00:54:13.400
of work. Leverage that visual advantage that

00:54:13.400 --> 00:54:15.219
the research from Iowa State and Illinois Extension

00:54:15.219 --> 00:54:18.059
proved is so effective. That's how you start

00:54:18.059 --> 00:54:20.900
unlocking that 25 to 40 percent faster training

00:54:20.900 --> 00:54:24.400
time and reducing daily errors. Got it. Diagnose

00:54:24.400 --> 00:54:27.219
first, then build visual SOPs for the top five

00:54:27.219 --> 00:54:30.010
tasks. Now, what about long -term positioning?

00:54:30.269 --> 00:54:32.829
Looking out one to two years, how do you sustain

00:54:32.829 --> 00:54:35.650
this and really maximize the benefits? Long -term,

00:54:35.690 --> 00:54:37.710
it's about embedding verification and continuous

00:54:37.710 --> 00:54:40.130
improvement into your culture. Two key things

00:54:40.130 --> 00:54:42.710
here. First, you absolutely must integrate the

00:54:42.710 --> 00:54:44.570
teach -back method into all your new employee

00:54:44.570 --> 00:54:46.889
training and probably even use it for retraining

00:54:46.889 --> 00:54:49.309
or verifying existing employees on critical tasks

00:54:49.309 --> 00:54:51.610
periodically. Make it the mandatory way you confirm

00:54:51.610 --> 00:54:53.889
understanding. No more just asking, do you get

00:54:53.889 --> 00:54:56.610
it? Exactly. Show me. becomes the standard. And

00:54:56.610 --> 00:54:58.710
second, implement those short regular quarterly

00:54:58.710 --> 00:55:00.969
protocol walks we discussed. Use them to keep

00:55:00.969 --> 00:55:03.690
the SOPs alive, updated, and owned by the team.

00:55:03.869 --> 00:55:06.070
So the teach -back ensures initial competence

00:55:06.070 --> 00:55:08.989
and the protocol walks ensure ongoing relevance

00:55:08.989 --> 00:55:12.269
and maintenance. Precisely. That two -pronged

00:55:12.269 --> 00:55:15.530
system verifying with show me up front combined

00:55:15.530 --> 00:55:18.210
with regular maintenance walks is what drastically

00:55:18.210 --> 00:55:20.929
reduces that financial tuition you pay through

00:55:20.929 --> 00:55:23.150
repeated errors. That's how you realistically

00:55:23.150 --> 00:55:26.230
aim for and sustain those incredible reductions

00:55:26.230 --> 00:55:28.750
in things like scours treatments, potentially

00:55:28.750 --> 00:55:31.769
up to 70%. It secures the health of your herd

00:55:31.769 --> 00:55:33.650
and the long -term profitability and stability

00:55:33.650 --> 00:55:36.289
of your entire operation. It's about building

00:55:36.289 --> 00:55:39.369
a system of clarity that lasts. Hashtag and hand

00:55:39.369 --> 00:55:42.539
show outro. Well, this has been another deep

00:55:42.539 --> 00:55:44.539
dive from the Bullvine podcast. If this kind

00:55:44.539 --> 00:55:47.019
of analysis helps your operation, you know, analysis

00:55:47.019 --> 00:55:49.559
built on structure, clarity, solid evidence,

00:55:49.699 --> 00:55:51.820
practical application, and not just industry

00:55:51.820 --> 00:55:55.199
hype, then head over to www .thebullvine .com.

00:55:55.340 --> 00:55:56.860
There are plenty more articles and resources

00:55:56.860 --> 00:55:58.820
there that really tell you what's happening in

00:55:58.820 --> 00:56:01.000
dairy without the BS. Yeah, the bottom line from

00:56:01.000 --> 00:56:02.659
today is pretty clear, isn't it? Communication

00:56:02.659 --> 00:56:05.699
is infrastructure. It's arguably the most affordable,

00:56:05.840 --> 00:56:07.980
highest ROI capital improvement you can make

00:56:07.980 --> 00:56:10.429
on your farm right now. Absolutely. Forget the

00:56:10.429 --> 00:56:12.750
concrete and steel for a minute. Focus on the

00:56:12.750 --> 00:56:16.309
clarity. It reduces your training time. It minimizes

00:56:16.309 --> 00:56:19.170
those costly errors that bleed profits. It keeps

00:56:19.170 --> 00:56:23.090
your workers safer and more engaged. And it demonstrably

00:56:23.090 --> 00:56:26.210
boosts retention by reducing stress. It truly

00:56:26.210 --> 00:56:29.269
is the essential, maybe invisible infrastructure

00:56:29.269 --> 00:56:32.590
that supports every single other dollar you spend

00:56:32.590 --> 00:56:35.869
on feed, genetics, equipment, everything. So

00:56:35.869 --> 00:56:38.219
invest in your people systems. Design systems

00:56:38.219 --> 00:56:40.199
for your people just like you design them for

00:56:40.199 --> 00:56:43.099
your cows. The return, based on everything we've

00:56:43.099 --> 00:56:45.000
looked at today, seems pretty much guaranteed.

00:56:45.280 --> 00:56:47.039
And seriously, if you haven't already, subscribe

00:56:47.039 --> 00:56:49.380
to the podcast wherever you listen. We're putting

00:56:49.380 --> 00:56:51.960
out episodes twice weekly now. Digging into the

00:56:51.960 --> 00:56:54.019
topics that matter for your bottom line. And

00:56:54.019 --> 00:56:55.820
trust me, you are not going to want to miss what

00:56:55.820 --> 00:56:57.960
we've got lined up for next week. We're breaking

00:56:57.960 --> 00:57:00.280
down the recent impact of Dairy Future's market

00:57:00.280 --> 00:57:02.780
volatility and what it really means for farm

00:57:02.780 --> 00:57:05.239
gate pricing as we head into Q1. Yeah, we'll

00:57:05.239 --> 00:57:07.099
be dissecting the data you need to see to help

00:57:07.099 --> 00:57:08.960
set your budgets for the coming year with a bit

00:57:08.960 --> 00:57:11.159
more confidence in these crazy markets. Definitely

00:57:11.159 --> 00:57:13.260
tune in for that. Thanks for listening. See you

00:57:13.260 --> 00:57:13.619
next time.