Why I Stopped Blindly Specifying Johns Manville (And You Should Too)

Look, I get it. When you're writing a spec for a commercial roofing job or specifying Johns Manville fiberglass acoustical insulation for an office retrofit, it feels safe to name a brand. You know the quality's there, the installers are familiar with it, and no one gets fired for specifying Johns Manville. But I'm here to tell you that's a lazy and potentially expensive habit. I've stopped doing it, and I think you should too.

My experience is in administrative purchasing for a mid-sized company. I handle the contracts for everything from the roof over our warehouse to the screen protector film on the visitor sign-in iPad and the set of highball glasses in the executive break room. It's about $350k annually across 12 vendors. And I've learned that defaulting to a single brand—even a great one like Johns Manville—creates two things I hate: blind spots and process friction.

The Argument: Efficiency Isn't Just About Price—It's About the Process

I'm a huge proponent of efficiency. My whole job is basically making things run smoother—from ordering paper towels to consolidating a vendor list so our accounting team doesn't have a breakdown. So when I say that defaulting to a spec is inefficient, I mean it. Efficiency is about minimizing friction in the flow of work, not just the price tag on the material.

Here's what I mean by that, broken down into the arguments that changed my mind.

Argument 1: The "Spec-in-Stone" Vendor Blind Spot

For years, we had an architect specify Johns Manville TPO roofing for a major project. It's a great product—durable, good thermal performance. We got three bids from contractors who all planned to use it. One came back significantly lower. We checked the references, everything seemed fine. We went with them.

The instant the project started, we had friction. The installer used a different manufacturer's vapor barrier and a non-JM duct liner because theirs wasn't available. The general contractor argued the spec said "or equal." We spent weeks debating whether the vapor barrier was truly equivalent. The punch list became a disaster.

My takeaway was this: When you lock in a brand name like John Manville, you limit the pool of installers who might integrate that product perfectly. An installer who knows JM roofing details inside out is great. But an installer who knows three brands and can suggest the best fit for the schedule and budget is a better partner for the business.

Argument 2: The "Efficiency Trap" of the Known Entity

This is the counter-argument I hear all the time: "But we know the installation instructions, we know the warranty, it's easier." And that's true—to a point. The 80% case is standard and easy.

But it's a trap. Because the 20% case—where you need a custom color match, a specific R-value, or a vapor barrier that interfaces with a weird building detail—that's where the friction lives. Defaulting to one brand means you stop asking the question: "Is this the most efficient solution for this singular problem?"

For example, when we were quieting down a new call center, I just specified Johns Manville fiberglass acoustical insulation. It's the standard. But the room had weird duct work. A junior engineer pointed out that a different acoustic liner, pre-cut to odd angles, would cut installation time by 20%. It wasn't a JM product. I had to fight my own internal bias that easier to spec was more efficient. I was wrong. It was just lazier.

Argument 3: The Procurement Nightmare of the Non-Standard Order

This one hit me personally. I had to order a screen protector for a custom lobby display—it was a weird, non-standard 75-inch format. Then the boss decided we needed new highball glasses for the bar. Two tiny, unrelated purchases. But because our system was set up for big, capital-project-level orders (like commercial roofing), the procurement process for these small items was a nightmare.

It taught me a lesson about process: Any time you have a single point of failure—like one brand being the default—you create a bottleneck. An engineer deciding between three brands of insulation is a decision that takes a day. An admin figuring out how to clean a weird non-standard baseboard heater because the building management used a proprietary model with no clear instructions is a process that grinds the whole maintenance schedule to a halt.

How I Buy Now: A Simple Three-Question Veto

Alright, let me anticipate the pushback. "So, you're saying don't ever use Johns Manville?" No, that's not it at all. I'm saying don't default to it. Before you specify a brand—any brand—ask these three questions:

1. Does this product have a clear, documented alternative that performs the same function? If yes, spec the function, not the brand. (Reference: per ASTM C553 for fiberglass insulation—that's a functional spec, not a brand one.)
2. Does the chosen installers have proven experience with this single brand, or are they proficient with the category? A roofer who only talks about JM might be a poor fit for a job where we need a fast delivery of a competitor's product due to a supply chain delay.
3. Is this the most efficient solution for the entire lifecycle? Not just the install, but the maintenance (like that clean baseboard heater issue), the warranty claims, and the future re-ordering from a distributor who carries a mix of products.

I've stopped thinking "I need a Johns Manville roof" and started thinking "I need a roof that meets these specs, has this warranty, can be installed by this vendor, and I can get a vapor barrier for from the same distributor."

My experience is based on about 250 purchase orders—half of which were for building materials, half for office consumables. If you're a sole proprietor working on a single-family home, your mileage will vary. But if you're trying to run an efficient operation, stop treating a brand name as a process solution. It's a product solution. The process is where the real efficiency—or the real friction—lives.