Product design and development with Rebel Engineering · 2026-03-23 · 14 min
Key moments - from our scoring
Substance score
68 / 100
Five dimensions, 20 points each
Speaker A, an engineer, uses vivid storytelling to clarify a fundamental misconception in product design: that overbuilt and over-engineered are synonymous. They're not. The episode walks through contrasting examples - a fabricator's 30-pound steel shovel versus an imagined titanium-and-carbon-fiber smart shovel with Bluetooth and Ray-Ban Meta integration - to show how both approaches can miss the mark. The real lesson emerges through practical comparisons: Kirby vacuums (overbuilt, too heavy to use), Dyson (over-engineered with unnecessary features), and commercial hotel cleaning services that choose simple Bissell units because they're lightweight and intuitive. The speaker advocates for designing with intent: understanding your end user, build quantity, and required lifespan, then building the simplest, cheapest product that meets those requirements. Examples like Apple's conservative feature rollout versus Amazon Fire's feature-bloated failure illustrate how clarity of purpose beats technological complexity. The episode also acknowledges legitimate exceptions - one-off builds, ASML's EUV lithography machines - but positions these as exceptions, not the rule.
Overbuilt means using heavy, durable materials (like steel plate or aluminum) that are stronger than necessary; over-engineered means adding unnecessary complexity and features that users don't need or want. The shovel example illustrates this: the fabricator's heavy steel shovel was overbuilt; the imagined carbon-fiber-with-carbide-edges smart shovel with Bluetooth was over-engineered.
Apple deliberately limited features to ensure high adoption and user satisfaction, while Amazon loaded the Fire with unused features like 3D scanners that made it complicated and expensive. Users wanted simplicity over unnecessary innovation.
Overbuild when making one-off items where cost-per-unit doesn't matter; over-engineer when manufacturing millions of units where cutting costs matters and the complexity serves a genuine purpose, like ASML's EUV lithography machines. Neither should be your default approach.
Design for intent by determining your end user, production quantity, and required lifespan, then build the simplest, cheapest product that meets those requirements rather than optimizing for ideal scenarios or outliers.
They use simple, lightweight Bissell units rather than overbuilt Kirby vacuums or over-engineered Dysons because they need something easy to carry, intuitive to use, and practical for daily work.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode delivers a clear distinction between overbuilding and over-engineering with concrete examples (heavy shovel, Kirby vacuum, Dyson, Bissell), plus practical design principles (design for intent, design for the 99%, understand quantity and lifespan). However, it relies heavily on extended narrative examples that, while illustrative, create padding; the core insights could be distilled more densely. The framework is useful but not groundbreaking.
Over engineering, that's something completely different... These terms get used interchangeably quite a bit.
What you need to do is design for intent. You need to figure out what is your end user. How many of these am I building? How long does it need to last?
The overbuilt-vs-over-engineered distinction is genuinely useful and not a tired framework, and the shovel/vacuum examples are colorful and memorable. However, the underlying advice - optimize for the median user, don't over-complicate, match product maturity to intent - is relatively well-trodden design wisdom. The iPhone vs. Fire Phone comparison is a common illustrative device. The thinking is sound but not particularly fresh or contrarian.
Over engineering, that's something completely different. However, these terms get used interchangeably quite a bit.
Apple has always been a little reluctant and a little slow to the game to add features... Amazon took a completely different approach. They threw all kinds of new features in that had scanners and had 3D features and things that no one asked for.
The speaker is a practicing engineer and fabricator with direct, hands-on experience designing and building products across multiple domains (custom shovels, CNC equipment, structures). The credibility is earned through real work, not theory. This is a practitioner speaking from genuine expertise, exactly the caliber needed for a B2B design podcast.
I am an engineer, so let's take maybe a, uh, more engineered approach to making the perfect shovel.
I do that all the time. If I don't know if I need a 4 inch or 6 inch or an 8 inch i beam. I don't want to spend the engineering or waste hours and hours of my time to figure out which one's going to work.
Good use of named products (Kirby, Dyson, Bissell, iPhone, Fire Phone, Google Glass, 3D TVs, ASML EUV lithography, Mack truck reference) and concrete details (50 bucks for the Kirby, $1,500 door-to-door price, $2,986-87 satirical shovel price, $10 baseline shovel, $25 trade shovel, hotel cleaning services research). However, most claims lack hard data or metrics; the vacuum comparison is anecdotal rather than tested, and the claim about ASML requires deeper substantiation. Numbers are present but selective.
I think I picked it up for like 50 bucks... They used to sell them door to door for like $1,500 or something.
this shovel is going to be available in two to three years and they should be available for about 2,900, um, 86 or $87.
This is a monologue, not a conversation - there is no host asking follow-up questions, no guest pushback, no productive debate, and no sharp questioning of the speaker's claims. The delivery is engaging and the anecdotes are well-told, but the format severely limits conversational depth. The speaker makes strong claims (hotel services use Bissell, Dyson over-engineers vacuums) without challenge or additional evidence gathering.
Let me know how that works out for you.
However, this is a situation where I don't care if it's a little too heavy and I'm only making one of them, so I don't need to worry about the cost on multiple down the road.
Computed from the transcript - who did the talking, and the words that came up most.
Get my free product development Cheat Sheet: What’s the real difference between overbuilding and overengineering? In product design and mechanical engineering, making something stronger, heavier, or more complex than necessary can quietly ruin usability, cost, and market success. Using real-world examples - from shovels and vacuums to smartphones and failed tech products - this video explains how to design for intent, avoid costly mistakes, and build products people actually want to use. If you’re an engineer, inventor, entrepreneur, or product developer, this is a must-watch before you take a physical product to market. ⏱️⏱️VIDEO CHAPTERS⏱️⏱️ 0:00 - Overbuilt vs. overengineered explained 0:29 - The 30-lb “tank” snow shovel story 1:48 - How engineers might overengineer a shovel 4:41 - Cheap vs. professional-grade tools 5:26 - Why good products still fail 6:47 - The overbuilt Kirby vacuum example 7:36 - The overengineered Dyson teardown 9:01 - What professionals actually use 9:28 - Designing for intent (not extremes) 10:16 - Designing for the 99% vs. the 1% 11:05 - When overbuilding makes sense 12:10 - Quantity, lifecycle, and smart design decisions
Transcribed and scored by The B2B Podcast Index.
Speaker A: Today we're going to discuss overbuilding versus over engineering. When something's built like a tank, most people say it's over engineered. That is completely not true. It's overbuilt. Over engineering, that's something completely different. However, these terms get used interchangeably quite a bit. People like to say things are overbuilt or over engineered to imply, um, that it's very high quality. Or someone took the time and really put some thought and effort into making a good product. I grew up in the Midwest and you have to shovel a lot of snow there. And I had a friend who had gone through the third shovel that season trying to shovel snow. Everyone he had broke and he was tired of it. He was a fabricator, so he was going to fix his problem. No more crappy shovels. He's better than that. He's going to make his own. So he went to work. He found, uh, some extra plate steel, make a real good blade on the shovel. And we can't have any of those crappy handles. So we're gonna use some schedule 40 pipe. We're gonna make a man shovel here. So anyhow, he got this shovel made and unfortunately I don't have it here. This was a long time ago. But he showed it to me and I'm like, great, I don't think you're ever gonna break that. And I said, let me know how that works out for you. So we got a good snow about maybe a week later. So he'd been sitting there, he'd been itching to use it. So I talked to him the next day and I asked him how the shovel was. Didn't bend, didn't break. In fact, it was even in pristine condition. And one of the reasons it's probably in pristine condition is about 30 seconds into shoveling his driveway, he realized that it's really hard to work with a 30 pound shovel. So that is an excellent example of overbuilding. And as a fabricator, fabricators know how to build, so they are great at overbuilding. Now I am an engineer, so let's take maybe a, uh, more engineered approach to making the perfect shovel. So we don't want any of this heavy steel plate. That's just ridiculous. What was he thinking? We're going to do this much better. We're going to make something that people can really use and it's going to be refined. So instead of that really heavy handle, let's go with, uh, some titanium. I've got some really nice titanium. This stuff's really light. Uh, this one's a little short, uh, but I can get a bigger piece. It probably like 100 bucks. But we're making a good shovel here. And I want to have a real performance blade on this thing. I don't want some, you know, low tech metal that, that's like iron age crap. So let's go with, uh, let's see what I have here. I think we can make the blade of this thing out of carbon fiber. Now we'll get some thicker stuff, but carbon fiber, stupid step. Six times stronger than steel. We're going to make the mother of all shovels. Now the edge of this is not going to hold up. When we start hitting rocks, it'll start, you know, getting some dents and I'll start chunking it out. So we're going to do this right. We're not going to skimp. I want this shovel to be something you can give to your grandkids. So I was thinking we can get some carbide and we can adhere, uh, some carbide to the edge of this. So we're going to have a nice carbon fiber blade with some silicon carbide edges. And this thing's going to show through anything. It's going to be lightweight, it's going to be strong, it's going to be stiff. We're here rocks with this thing, we're going to bust the rocks. This is going to be the best shovel ever. But, but, but, but don't stop yet. We want to be able to monitor how efficiently we are doing this and we need to be able to automatically upload this data into an Excel spreadsheet. So what I recommend is we're going to add a, uh, Bluetooth connection to the shovel. And this is going to be awesome. So not only is a bluetooth, but we're going to have it integrate with the Ray Ban meta glasses. So I'm going to be able to monitor in real time how quickly I am shoveling. And you're going to find out that I am shoveling like three times faster than the heavy thing did. Um, and probably one and a half times faster than just a normal crappy show. Oh, I almost forgot. It's going to have a remote and it's going to have LED colors. So when I get close to a gas line, it turns yellow. I get close to electric, it turns red, and I get close to a water line, it's going to turn blue. This is going to be amazing. So I think I definitely won the shovel wars here. And this shovel is going to be available in two to three years and they should be available for about 2,900, um, 86 or $87. And I'm sure all going to be lining up to buy one. For those of you that aren't going to line up and buy one of those shovels, possibly this shovel which you can get for about $10, which is neither overbuilt or over engineered and really not even very good quality, this might be a better option. It will get used by 80% of people about once a year and it'll last long enough. So let's say you're in the trades, you need something a bit better. So let's look at this. We have a nice fiberglass handle, we have a high carbon steel blade and we have a stronger attachment point. This is probably a uh, $25 shovel and it's probably overkill for most people. However, this is well engineered, this is well built and it's simple. Most of the time that is what we're going for. Most people think that a product is going to fail because it used poor materials or had poor manufacturing methods or it was just rushed into the market too fast. However, some products just fail because it was a bad idea. One example is Google glasses. They came out, they function, they were actually pretty revolutionary. The quality wasn't bad and everyone who wore them got called a glass hard, which this alone needs to make me rethink integrating these Ray Ban metaglasses with the shovel. And also why I've never worn these in public. Another example is 3D TVs. The technology was great, it sounded like a good idea. Every TV manufacturer jumped on board and dumped millions or billions of dollars into this technology. However, no one wanted it, no one wanted to sit around wearing glasses all day long like we just talked about to watch tv. And some people got dizzy from it and there was just technical aspects that weren't ready. So sometimes it's not the product, it's the idea. And then we have the California high speed rail, which is neither overbuilt nor over engineered. And it's actually the physical manifestation of um, vaporware. And if we want to talk about the mother of all inventions, we have the entire AI infrastructure which that's a topic for another video. So let's look at another real world example where different manufacturers tried to make things stronger, bigger, beefier, more advanced higher tech. Years ago I went to swap meet and they had a two or three year old Kirby vacuum cleaner there and I think I picked it up for like 50 bucks. And if you've ever seen these things. You know they're expensive. They used to sell them door to door for like $1,500 or something. Insane. That Kirby was pretty much the definition of over building something. That thing will last 100 years. Everything about it was well made, everything was heavy, had big solid aluminum case and you would rather just lug your upstairs stay dirty than having to lug it up the steps. I got rid of that overbuilt vacuum cleaner that I didn't want to use and my wife sure as hell didn't want to use and and replaced it with an old re engineered vacuum cleaner. So what we have here, we have a Dyson. I wanted to get to the bottom of it. Which one of the vacuums is better? Do we need to take out a Mack truck or do we need to fly to the moon? So I figured I'd look at what the professional hotel cleaning services are using because obviously they figured it out. What do you think? Are they using the tank or are they using the high tech wizardry? Well, it turns out they don't want anything to do with either one. They want something simple like Bissell. Um, something that's light enough to carry around and simple enough that they don't need to go get an engineering degree to use it. What should be your goal when you design something? Should you overbuild it? Should you over engineer it? I think you figured out by now that you really don't want to do either. What you need to do is design for intent. You need to figure out what is your end user. How many of these am I building? How long does it need to last? And you need to build whatever you're designing in the easiest, simple, cheapest way you can that will meet or exceed all the requirements that you expect out of this product. Two places that people run into big problems is designing for the ideal scenario or designing for the 1% outlier. It'd be great to make a product that works for absolutely everyone. However, if you have to design that product so it's too heavy, too expensive or too complicated for the average user, then you've missed the mark completely. A good example is an Apple iPhone versus an Amazon Fire phone. Apple has always been a little reluctant and a little slow to the game to add features. And they do this on purpose. They want to make sure that everything they added is well adopted, is not going to frustrate users. And they found out that their users are loyal enough that they're willing to wait one or two generations to get a feature over having to learn something to that they may not really want anyways. Amazon took a completely different approach. They threw all kinds of new features in that had scanners and had 3D features and things that no one asked for. And they ended up being very complicated. And very few of the people bought it, found a use for it and it flopped horribly. There are situations where you want to over build or maybe you want to over engineer something. If you're only making one of something. Say you're making a, uh, CNC plasma table or you're making a structure bolted to your house. In these cases, it might be better to just overbuild it. I do that all the time. If I don't know if I need a 4 inch or 6 inch or an 8 inch I beam. I don't want to spend the engineering or waste hours and hours of my time to figure out which one's going to work. I'm just going to spend the extra money and buy the 8 inch I Beam because I know it's sufficient. Cost me a couple hundred extra dollars and I know for sure I did it right. However, this is a situation where I don't care if it's a little too heavy and I'm only making one of them, so I don't need to worry about the cost on multiple down the road. If we want to look at something that's ridiculously engineered, look at the EUV lithography machines that ASML makes. Without these, we couldn't have the microchips that power our world. Is this over engineered? Well, and we're going to look back in 20 years and say it's over engineered? Because anything high tech can be made simpler at some point. But for right now, engineering the crap out of it is the only way they know how to do it. However, given our examples of vacuums and shovels, that should not be your base case. As I mentioned before, you should be designing for the 99% of people who will be using your products. And if you can't fit the needs of that last 1%, then you let them know or you build a special product for them that may be way more expensive or way more complicated. And that's okay. In addition to product intent, you need to look at quantity. If you're only making one or a few, overbuild the thing. If you're going to be making millions and millions of them, lean in the area of over engineering because that cost is spread out across everyone you make. And sometimes that's okay. But don't make something complicated just. Just to make it complicated. If you've ever worked on a German car, I can guarantee you there's simpler ways to do things. And also think about the design life cycle of the product you're trying to make. Are you trying to make something that needs to last for six months, a year? 10 years? A good engineer is going to be able to ask the difficult questions up front in order to direct the design process from the beginning through the end. If you found this useful, check out my other video on why your prototype is not production. Mhm.
009 The expensive mistake in every overbuilt prototype51 / 100008 Engineers vs Mechanics: The Real Problem With New Cars59 / 100007 The Problem with Choosing the Wrong Engineering Major | Engineering vs Engineering Technology47 / 100006 Sunken cause fallacy. Why quitting and starting over is hard81 / 100005 Is Your Product Idea Good? It Must Pass These 5 Tests!53 / 100