Tag Archives: Strategic management

It’s Foodie Friday and the topic is ground beef. I try, whenever possible, to grind my own beef and the thinking behind that is also thinking that can be used in business decision-making.

You can walk into any supermarket and purchase ground beef. In fact, you can be very specific about chuck vs. sirloin, the percentage of fat in the mix and often grass-fed vs. non. That’s great in my mind when you are making chili or meatballs or some other dish requiring that the beef cooks for quite a while. For burgers, however, I’m grinding my own. I’ll generally grind a mix of chuck, brisket, and short rib and I’ll usually grind some parboiled bacon into the meat both for fat and for flavor. The biggest reason I take the time to do this, however, isn’t the flavor. It’s food safety. I like to eat my burgers on the rare side and ground beef from a store is generally not safe to eat unless it’s cooked more than I like it to be. I know what’s in my mix and that it’s safe to eat when cooked to less than 165 degrees.

Is it a pain to clean the grinder? Yes. Does it take more time than just opening a package from the store? Of course. But the results are much better and exactly what I want even if it costs a bit more and take more time. That’s exactly the process any business goes through when making a “build vs. buy” decision. Let me run you through the steps.

First, you need to validate that you actually need the technology you’re considering. In burger terms, I’m hungry so I need food. I have a legitimate need. In considering tech, you need to figure out if you’re finding a solution without a problem existing. Next, you need to pull together core business requirements. My burger must be safe to eat when rare, it must hold together on a grill, etc. You need to involve anyone whose business is affected by the proposed tech to be sure all constituents weigh in on requirements.

The technical architecture requirements come next. If you’re looking outside, can the product fit in with your existing infrastructure? Does it meet whatever standards your business has already? It’s only after the above steps have been taken that you can start to evaluate build vs. buy. In my case, I have a need, my requirements are clear, I’ve asked my dinner guests if they like burgers, how they want them cooked, and what they put on them. I figured out I’m building the beef but buying the rolls, mayo, pickles, onions, and tomatoes even though I could also build them.

The final steps in the evaluation concern costs and support but you get the point. Some managers start evaluation solutions before they pull together requirements and the overview of the environment in which the solution will live. While it was an easy decision for me to grind my own beef, few business decisions are as easy and require planning and forethought. Make sense?