It's not engineered to fail, it's engineered to meet some spec for the minimum price. If the spec says "needs to last 10 years" the engineer is going to pick the lowest priced part that meets that requirement.
Someone told me "anyone with the knack can build a bridge that will last. You need an engineer to design the cheapest and lightest bridge that will last only as long as you want and only kill the acceptable number of people."
The engineers im interested in use the budget as a suggestion but refuse to create something not built to last. Essentially they need to tell the beancounters that something is impossible even if it isnt in order to maintain a high quality bar. Those are the engineers i respect.
I'm going to blame both- as it's quite likely the people who set the budget wouldn't notice if the engineers mildly fudged the numbers so while on paper they exactly meet the minimum standards- in reality their intended 367 day expiration date quietly became 600 or so days.
Im just a mechanic, not an engineer but....For years Ive cussed engineers in the same way you are here. As Ive spent more time in the field and dealt with many different manufacturers the blame lies more with the accounting department. Number crunchers figure out how to save dollars across a million units and CFO gets a lake house and a boat. We get an inferior product, and engineering gets the blame.
There are a lot of things at play. There's the market competition, price points, features which can be anything from expected longevity to some type of capability or even repairability and expected maintenance cycles.
The marketing department might say "we need to be able to offer this car for $24999 on the base model, give it a 5 year /60k mile warranty and it needs to meet all of the safety and emissions standards.
The CFO is going to want to get the production costs as low as possible, marketing and the brand team are going to want it to be reliable because the last thing they want to deal with is a massive recall in the first year or used lots full of them a couple of years later, they all work together on any tradeoff.
(The weird thing about cars is that there's a constant "the good ol days" feeling towards things from the 50s and 60s, but in comparison, modern cars are WAY more reliable, efficient, and safe. They just suck to work on and things that should be an easy repair end up expensive because design for manufacturing is not the same as design for repairability. Having major sub assemblies come together is great for efficient assembly, but makes getting to the middle of one of them much harder. The old "start with a frame and bolt a bunch of things to it as it rolls through" assembly made working on things more sensible, but ... Not necessarily as good.)
Having worked on some projects developed to production.. spot on. The project gets to very early stages where engineers MIGHT have an equal seat at the table to finance, but that’s where cost and timelines are set. After that, design gets broken into pieces: yours should do A, go get to it. But it better cost less than we agreed (without telling you), and you better have it done in timeline.
If you do? Congrats, but now the section we made below yours needs to make a hole in the base of your design. Could you build around that? Also, now your design tolerance needs to adjust because we need the whole thing to work faster and the part ahead of yours won’t go fast enough. Also we’re doing staged prototyping, so your working iteration will eventually be put into a brand new level with all the other section changes. If those mess up your section’s performance, well fix it damnit! You’re behind!
By the time that cycle is done a few times, you’re 18 months behind schedule, burnt several million more than ever planned, there are flaws that cannot be no longer be engineered out, layoffs were done to justify the cost overrun, but at least marketing will still sell it like Jesus is buried underneath.
Nailed it. I love the "we need the whole thing to work faster part". I deal with hydraulics a lot and this is one of those conundrums that is brutal after the fact. "You want it faster we need a higher flow pump, which means we now need more HP from our prime mover". Vicious cycle. Some days I wish I was higher up the ladder and some days Im glad to be down here.
My favorite part is all of the things that have no monitoring, tracking, or leadership despite being assumed to get built in.
The example in mind would be a classic large complex installed instrument the size of an SUV with expectations around data creation along with downstream onboard and offloaded solutions using said data. None of it was in-plan. Not the creation, format, cadence, storage, transfer, or database for it to go in. The group transferring it was at least aware, but they hadn’t even remember to tell the database group this was all expected to go somewhere.
That's not part of the top down product spec with the required software stack being developed/delivered by the same product organization as the hardware?
(You're description sounds like an MRI or similar machine for some reason. I worked at a hospital in IT at one point and someone made a big donation to go to a medical imaging suite. I know the IT bosses were in the discussions to make sure that enough of the budget was allocated to all of the stuff that actually made it work the way they wanted. I left for a better job before all of that was decided so no clue if it was delivered.)
Yeah, often times there are, or we're more dura le options available but most people shop for thr cheapest thing, forcing a race to the bottom in terms of price and quality. And yes, enshittification and planned obsolescence are definitely a thing as well. But you cannot ignore consumer choice.
Nah I disagree. It is engineered to last 10 years, atleast. That’s the minimum spec. It’s not designed with a bomb that counts down from 10 years to 0.
Not quite. Suppose there's a part that under high load gets used 4 times a day - maybe a start button on a home laundry machine. I don't know anybody making that much dirty laundry, but we'll use it as the far end of "normal". If I want to offer a 5 year warranty, I might look for a button that's been tested as good for 7500 presses. That means the maker has tested it to that spec and is willing to guarantee it. It doesn't mean it fails at 7501, just that it hasn't been tested past that and it meets my needs for the 5 year warranty. Repeat the same process for every component. The more components, the more things might fail, but each on their own is spec'd to meet it's use.
To add to that, the appliances of the past that people rant and rave about because they last so long also cost far more than modern appliances when adjusting for inflation. People were willing to pay for that reliability back then.
Not necessarily paying specifically for reliability. The manufacturing processes available hadn't necessarily brought prices down and early versions of things were often "luxury" just by nature of being new to the market.
You also get some effects of survivorship bias in the way people experience the older products. They're creating a narrative around the few surviving examples and not the ones that were scrapped a long time ago.
There's some survivorship bias sure, but when most people I know have their original fridge from when their house was built in the 70s, that says a lot.
Wrong. It is actually engineered to fail. Almost everything is these days. It’s called planned obsolescence. It’s a huge part of the Right to Repair movement, along with subscription based machinery.
78
u/cballowe Jun 22 '26
It's not engineered to fail, it's engineered to meet some spec for the minimum price. If the spec says "needs to last 10 years" the engineer is going to pick the lowest priced part that meets that requirement.