The irony of herd health technology is that the search for better clarity can quickly become its own form of data overload. Most producers begin looking at these systems because they want less guessing. They want to catch sick cows sooner. Improve heat detection. Tighten breeding windows. Manage fresh cows better. Support the team. Use the vet and nutritionist more effectively. Make more confident culling and profitability decisions. But then the shopping process begins. Collars. Ear tags. Pedometers. Cameras. Cloud platforms. Local systems. Milk sensors. Robot data. Parlor integrations. Health alerts. Heat alerts. Cow location. Rumination. Activity. Components. AI analysis. Dashboards. Reports. Apps. Pretty soon, the farm is not just asking, “Which cows need attention?” It is asking, “Which system needs attention?” That is why the first step is not comparing every feature. The first step is deciding what decisions the farm is trying to improve. A good herd health system should not simply give you more data. It should help the right people make better decisions sooner, with more confidence and less confusion. That starts with a few important conversations. 1. Can The Farm Support The System? Before comparing collars, tags, software, or dashboards, start with the basics. Can the farm have reliable internet? Some systems are built around cloud connectivity. Others can operate more locally. If a farm cannot or chooses not to use internet, whether because of location, reliability, or religious reasons, that needs to be respected from the start. This is not a small technical detail. It may immediately change which systems are realistic to install, support, and maintain. A system that looks impressive in a demo can become a source of frustration if the farm infrastructure cannot support it day after day. The right question is not only, “What can this system do?” It is also, “Can this system work reliably here?” 2. Do You Need To Monitor Animals In The Pasture? The next conversation is pasture.

Most problems on a dairy don’t show up all at once. They start as little things. A dip cup not filled quite right. A liner that should have been changed last week. A fresh cow that “seems fine” but isn’t eating like she should. A service call that gets handled, but nobody writes down what changed. A team member who knows the routine, but not the reason behind it. None of those feel like a crisis by themselves. But small misses are often early warning lights. Not proof that someone failed. Proof that the system needs attention. That’s true whether you’re running a dairy, installing equipment, managing route service, or trying to grow a business without everything living in your head. Good owners don’t just ask, “Who missed this?” They ask better questions: What made this easy to miss? Where did our routine break down? Is this a training issue, a communication issue, or a design issue? Do we have a repeatable way to catch this earlier next time? The best farms and service businesses are not perfect. They are observant. They treat small problems as cheap lessons before they become expensive ones. Takeaway: This week, pick one small recurring miss and fix the system around it, not just the symptom.

Last week we talked about how small issues become big issues when we don’t have the time, systems, or routines to catch them early. That’s the hard part of running a farm or service business. It’s not that people don’t care. It’s that the urgent stuff keeps getting louder. The trash doesn’t usually get taken out because it’s “scheduled.” It gets taken out because cans are spilling over the top, the bag is overfilled, and now the simple job has become a messy one. The same thing happens in bigger, more expensive ways. This past week, one of our farm customers was dealing with an elevated PI count, which is a bacteria count that can point toward cleanliness, cooling, equipment, or milk contact surface issues. Our route specialist started thinking through possible causes. While looking things over, he noticed the milk hose and asked a simple question: “When was the last time you changed your milk hose?” The answer was one we hear more often than we should: “It’s only been a few years.” So he checked the system. It was 2017. That hose was rated for 12 months and had been on the farm for almost 10 years. Wow. And honestly, that raises a few fair questions. Where did the time go? Why did nobody think of it sooner? Should we have pressed harder since we had the data? Should the farm have had it scheduled on the calendar, the same way inflations are changed on a routine? Here’s the tricky part: the farmer didn’t think the hose was the culprit. Something else had to be causing it. But he decided to try it anyway. A few days later, our route specialist got a text: “I owe you a steak dinner. The PI counts came down immediately!” We love that. We’re thankful for customers who appreciate good work, and we’re always glad when a practical fix helps that quickly. But here’s the bigger point: The real win would have been if the PI count never went up in the first place. That’s what we’re trying to build toward. Not a business where every task waits for a problem prompt. A better question is:

This is going to be a brief on cooling milk. Raise your hand if you just love the taste of an ice-cold glass of fresh milk. Ahhhh. For those of you that work with harvesting or producing dairy products, you know first hand the panic that ensues when the tank or chiller isn't cooling. One key thing to learn about this is this rule of thumb. Bacteria in milk will double about every 15 -20 minutes at about 50 deg. F.. This means the following. Safe @ 5000 PI count. In 2 hours, here is where that goes: Starting point =5000, 10,000, 20,000, 40,000, 80,000, 160,000 and after 2 hrs., at 20-minute intervals, we're at a whopping 320,000. Add an additional hour and we're easily above 2.5 million. WOW! And, not to mention, gross! Yeah, I said it. It's gross. But, this is why it matters so much. So, what is your goal for cooling? Set temp? Time to cool? Do you use a plate cooler? Drop a question below and I'll do my best to walk you through any cooling or tank questions to help you be equipped for success on your milk cooling and milk quality! Info from Google search:https://www.journalofdairyscience.org/article/S0022-0302(16)30023-6/fulltext Here is what a quick google search AI result showed: Bacteria in milk reproduce exponentially via binary fission. The rate of growth heavily dictates the shelf-life and safety of the milk and is dictated strictly by storage temperature. [1, 2] - \(< 40^\circ\text{F} \ (4^\circ\text{C})\) (Refrigeration): Growth is radically restricted. Milk can last up to 7–21 days depending on processing. [1, 2, 3, 4, 5] - \(40^\circ\text{F} \ - \ 140^\circ\text{F} \ (4^\circ\text{C} \ - \ 60^\circ\text{C})\) (The "Danger Zone"): Bacteria thrive, with populations doubling in as little as 20 minutes. For example, at \(40^{\circ }\text{F}\) it might take 68 days to reach spoilage levels, but at \(50^{\circ }\text{F}\) (\(10^{\circ }\text{C}\)), it takes just 10 days. [1, 2] - \(> 145^\circ\text{F} \ (65^\circ\text{C})\) (Thermal processing): High heat effectively destroys most bacteria and pathogenic organisms. Standard pasteurization (HTST) holds milk at \(161^{\circ }\text{F}\) (\(72^{\circ }\text{C}\)) for 15 seconds. [1, 2]

I have recently decided that I want to do a 100-mile ride. A few key takeaways from that are worth sharing. 1. I shared this out loud - this made it more than an idea. 2. One of the people who I shared this with, offered to do the ride with me. 3. I have had challenges. Do you relate with any of these takeaways? While it can be misconstrued as bragging, my objective in saying it outload is it causes more accountability to the goal. Folks will ask "how is your training going" or "when is that ride". I'll be way more likely to do the training. I'm not doing it for other folks but I said I was going to do it and barring any legitimate reason not to, I will. I would hate to have lied to all those people. Next, I would look like a fool letting my friend train and come September, when we're doing the ride, tell him "well, I forgot I said that and so I didn't train - let's try out best". Oh boy, what a disaster that would be. Instead, he and I occasionally text each other milestones of our training. "I rode 12 miles today" or "it shaved 5 minutes off my normal ride". I did not train the way I wanted to. Weather, broken bike, sick, weather again, busy, etc. You know the feeling. You know what though, I am still finding ways to get back on the bike and keep training. So, what is your "century" that you're pressing for in 2026? Who is in your corner? Who is both challenging and encouraging you? Find that person - connect - build! Let's ride!