Who Is the Product Optimized For ?
Every pack on a shelf is a solution to a problem. The question nobody asks is: whose problem?
There are three parties in this transaction, and they don’t want the same thing.
The retailer wants the pack to sell off the wall to someone who doesn’t yet know what they need. That buyer isn’t stupid — they’re just uninformed, standing in front of forty options with no framework for evaluating any of them. So the pack has to signal value in the three seconds before they walk past it. Doo-dads do that. Extra straps, extra pockets, extra pull-tabs, a compression system with six buckles instead of two. None of it needs to work well. It needs to be visible. Feature count becomes a proxy for value because the customer has no other proxy available to them at the point of sale.
The vendor is operating inside a cost target. Every dollar spent on one part of the pack has to come from somewhere else — that’s just the arithmetic of building anything at scale. Sometimes that tradeoff is exactly the right call. Sometimes it produces a feature that photographs well on the shelf and contributes almost nothing once you’re miles from the trailhead. The doo-dads and the cost-down decisions tend to be the same decisions, viewed from two different angles — not because anyone set out to build something inferior, but because a feature that’s cheap to add and easy to see is very good at justifying its own cost, whether or not it’s earning its weight.
The buyer wants a pack that solves a problem in the backcountry. This is the party whose interest is least represented in the design brief, because they’re the hardest one to sell to and the easiest one to fool.
“Performance” is doing a lot of unpaid labor
Here’s where it gets more interesting, because even the brands that reject the shelf-appeal game and market on “performance” aren’t optimizing for the same thing as each other. Performance isn’t a single axis. It’s a name people put on whichever variable they’ve decided to index on, and then everything else gets treated as a rounding error.
An ultralight brand indexes on weight. Grams are the enemy, full stop — and durability, margin for error, and field-repairability become the variables that get quietly sacrificed to hit a number on a spec sheet. You end up with packs that are extraordinary at being light until the one time they’re not, at which point the failure is total and it happens forty miles from a trailhead.
A traditional expedition brand indexes on durability. Bombproof is the entire pitch — 500D everything, bar-tacked to oblivion, a pack that will outlive you. Weight becomes the sacrifice, and at a certain point the pack itself becomes the load you’re carrying rather than the tool that carries your load.
Both of these brands will tell you, honestly, that they build for performance. They’re not lying. They’ve just each picked a single variable and called it performance, because a single variable is a much easier story to sell than a tradeoff curve.
The variable that actually matters
Durable, light, and capable at low weight isn’t a compromise between two axes. It’s a different question entirely — not “how do I trade weight for durability” but “how much capability am I getting per unit of weight I’m carrying.”
Materials engineers have a term for this shape of problem: specific strength — strength per unit mass, not strength in isolation. It’s why aircraft don’t get built out of the strongest material available; they get built out of the material with the best strength-to-weight ratio, because mass is a cost that compounds at every other point in the system.
Gear needs the same lens. Call it capability density — how much real function you’re getting per pound carried, once you strip out everything that isn’t contributing to that ratio. Under that lens, a doo-dad isn’t a value-add, it’s dead weight with a marketing budget. Durability past the point your use case requires is the same failure in the other direction — mass spent buying you a margin of safety you’ll never actually use.
This is the actual design question, and it’s a harder one to answer than “light” or “tough,” because it forces you to be honest about what the pack is actually for, who’s actually carrying it, and what failure mode you’re really protecting against. That’s a much smaller design brief than “please everyone at the point of sale.” It’s also the only one that produces a pack that’s still the right pack a hundred miles in.
What actually belongs in the numerator
Specific strength is a clean concept in materials science because strength is a single, measurable thing. Capability isn’t. The moment you adopt this as a real design lens, you have to answer a harder question: capability at doing what, exactly? You could use performance but that term has been overused, and could mean almost anything at this point. Get sloppy and “capability density” becomes just another word people use to mean whatever they want it to mean — which is the failure mode we’re trying to get out of.
So the numerator has to include more than raw carrying capacity (volume) or structural strength (weight bearing) , and it has to be argued for, not assumed.
Comfort counts, but only the kind that holds up under load over hours, not the kind that feels good in a five-minute showroom fitting. The five-minute showroom fitting is the biggest liar out there. So is the lets put 25 lbs in it for 90 seconds. A frame system that transfers weight to the hips correctly is capability. Padding that feels plush on your shoulder for thirty seconds and then compresses flat by mile four is not — it’s mass that bought you a first impression.
Load transfer is probably the single highest-density attribute a pack can have, and it’s the one that’s hardest to market, because it doesn’t show up in a photo. A frame and belt system that actually moves weight off your shoulders and onto your hips changes what you’re capable of carrying, for the same number of pounds on your back, more than almost any other design decision.
Reliability counts directly — a buckle that doesn’t fail is capability, because a buckle that fails converts your pack into a liability at the exact moment you need it least. This is where the ultralight failure mode lives: shaving grams off a component until its failure rate stops being negligible. Fabric, that is a big one as well.
Ease of repair counts, because failure in the backcountry isn’t really about whether something breaks — everything eventually breaks — it’s about whether you can fix it with what’s in your kit and keep moving. A pack that is easily fired reparable for most systems, has more real-world capability than a pack that fails less often but catastrophically when it does.
Versatility counts, but only when it’s actually used, not when it’s theoretical. A pack that can do three jobs adequately is often more capable, pound for pound, than three packs that each do one job perfectly — but only for the person who’s actually going to use it that way. Versatility you don’t need is just complexity with better branding.
Water and weather resistance, those a purposefully separate. Water, how much is too much ? Some packs are water tight, some take on a little water, some can gain pounds in sustained rain. Weather resistance, seems odd but is real. Why? Because using a rain cover (extra weight) to make up fabric or access, can be more problematic.
Simplicity isn’t really a separate line item — it’s what’s left after everything above has been weighed honestly. A pocket that doesn’t improve load transfer, comfort, reliability, repairability, or genuine versatility isn’t a neutral addition. It’s dead weight that has to be justified against everything else on the pack, and most of the time it can’t be.
This is what makes capability density a real design filter instead of a slogan: every component on a BearingCo pack has to earn its place against these questions specifically, not against a vague sense that “less is more.” Sometimes the honest answer is that a heavier component wins, because it’s carrying more real capability than the lighter alternative. The lens doesn’t always point toward less weight. It points toward less weight that isn’t paying for itself — which is a very different, and much stricter, standard.
The real test is time
Here’s the thing about capability density as a design target: it’s easy to fake for a week. Most people, love a new toy the first couple weeks. A pack can feel extraordinary on day one — and still be the wrong pack, if what made it light was a decision that shows up as a bent or broken frame stay on month four. Also, time shows how well the comfort really is.
So this is what we’re actually optimizing for at BearingCo: the pack you’re still happy with one week in, one month in, six months in, three years down the road. Not the pack that wins the shelf in three seconds. Not the pack that impresses on the first trip and gets replaced after the second. The one you keep reaching for, trip after trip, because nothing about it has given you a reason to look elsewhere.
That’s a much harder metric to design against than a scale reading, because a scale can’t tell you anything about year three. It’s also the only metric that actually matters to the person carrying the pack instead of the person selling it. Success, for us, isn’t the unboxing. It’s still being the pack in your hand a long time after the newness has worn off.
Complexity is the enemy of performance because complexity is almost always low-capability-density mass wearing a disguise — a feature, a redundancy, a margin nobody asked for. Reductionism isn’t an aesthetic. It’s just what’s left after you optimize for the one variable that was ever worth optimizing for, over the only timeline that was ever worth optimizing over.
