Product Startup Podcast Episode 129: Hardware Development Best Practices

Listen Now

Guest: John Carter, Former Chief Engineer at Bose.

Host: , founder of Product Startup and the leading expert in hardware startup consulting. A hardware entrepreneur since 1999, Kevin has advised more than 1,500 founders and built and scaled MAKO Invent through its acquisition by TriMech in 2024.

How Strong Hardware Teams Develop Better Products

Former Bose chief engineer John Carter shares how leading hardware teams focus innovation, reduce risk, use customer feedback, and reach the market faster. The conversation also examines product requirements, development planning, validation, vendor coordination, commercialization, and the business choices around technical work.

Podcast cover for Episode 129 about hardware Development Best Practices

What You’ll Learn in This Episode

  • To figure out how to make a great product, he worked all around the world to find out how the best in the world did hardware product development.
  • How do you know what areas you should focus on for innovation?
  • Innovation is not free, it takes a tremendous amount of work, sustained effort, and a budget.
  • Focus on one key innovation!
  • Don’t share with customers too early, design through the concept first.
  • How do you reduce the risk that is out there?
  • Don’t feature creep.
  • Get to the market, then reiterate and improve.
  • What are the key principles of agile development, and how do they apply to hardware consumer products?
  • Empower your team!!
  • Never forget the importance of industrial design.
  • Try rotating feedback in the hardware.

Episode transcript

This transcript is provided for accessibility and reference. Download the SRT transcript.

Read the full episode transcript

Kevin Mako: Hello, product innovators. Today we learned from the past chief engineer at Bose on what you can learn from best

Kevin Mako: practices and product development processes at the biggest product brands in the world.

Narrator: You're listening to the Product Startup Podcast, the show that helps bring your product idea to life by chatting with successful inventors,

Narrator: product developers, manufacturers, and hardware industry professionals. Our goal here is to get to the bottom of what makes a product successful, from initial

Narrator: idea to getting your product on start. store shelves. We're taking you step by step to build a functional product and scale your product

Narrator: business. Hosted by Kevin Mako, one of North America's leading experts on hardware development

Kevin Mako: for small product businesses.

Kevin Mako: Now, onto the show.

Kevin Mako: Welcome back, everyone. Today I'm very excited to introduce John Carter to the show. John was the chief engineer for Bose for over 12 years, most

Kevin Mako: notably being the name behind noise-cancelling headphones. After that, he found a TC-Gen and has spent

Kevin Mako: 22 years working with some of the biggest hardware brands in the world on improving their product development processes. He's also a fellow writer with me at Forbes.

Kevin Mako: Today, John is going to share some valuable knowledge in how inventor startups and small manufacturers can use best practices

Kevin Mako: from the leading hardware development teams in the world to improve your product design, launch, and scaling journey by understand what it takes to succeed in the long run,

Kevin Mako: utilizing customer feedback, getting to the market fast, and many other development secrets. Now on to the episode. Hey, John. Welcome to the show.

Kevin Mako: Glad to be here, Kevin. It's quite interesting. For the show,

Kevin Mako: I realized that we had a client and you are also the head of technology for

John Carter: Bose. Not at the same time, but quite an interesting commonality. Exactly. And I started, my first job was at Bose. I studied

John Carter: with Professor Bose and worked with him being a teaching assistant in acoustics. And then he brought me under

Kevin Mako: his wings and he and I work closely together during earlier stages of the company.

Kevin Mako: Amazing. And give us a bit of a background on how you got from there to the major leadership

Kevin Mako: position that you're in today, working with the number of Fortune 500 hardware brands.

John Carter: And what was that pathway now? And give us a bit of a description of what you're doing today. Well, basically the journey started when I was at Bose and I was really

John Carter: trying to improve our execution and product development. And Dr. Bose was just, fantastic in terms of networks and relationships.

John Carter: So we went out and we benchmarked product development across the world and visited companies like Sony,

John Carter: Toshiba, Sharp, a lot of Japanese companies, European companies, and really got some insight into best practices and product

John Carter: development. And I took those. I wanted to do my own thing. And I took some of the lessons that

John Carter: I'd learned from that and really started to focus on a niche area, which is product development

John Carter: consulting, but really on the process side, not on the execution side. And I have such a passion for bringing technology and people together.

John Carter: And to me, this is the hardest product development and product design is how do you get one mindset? Because the technical issues are there,

John Carter: they're rational, but the human factors, you've got to work with a team and so forth. And I was able to basically share my benchmarking knowledge, my metrics

John Carter: with the number of corporations, and one of our first clients was Apple.

John Carter: And I worked with Apple and created with them the ANPP or Apple new product process. And it was built on metrics.

John Carter: That's actually how I got started. But really, as I got into it, and as they realized, they were really looking at how do they scale, how do they grow. How do they execute?

John Carter: And so we worked with them on a very light touch process that enabled them to make decisions faster and more quickly and speed the teams to market without

John Carter: tripping over each other. And then once we did work with Apple, our work expanded to a number

Kevin Mako: of global brands where we really helped them with both innovation and execution. I just have a passion for that area, Kevin. That's incredible.

Kevin Mako: I look forward to talking deeper about these processes that you built in because as hardware startups and emerging product brands,

Kevin Mako: I always want to know for these clients and for the listeners here on the show, what is it

Kevin Mako: the best in the world they're doing in their development processes so that we can try and

Kevin Mako: mimic that and try and learn from what they do well and from the mistakes that may make along

Kevin Mako: the way. You've actually had the opportunity to work with a number of these major brands.

Kevin Mako: Other ones include obviously Amazon's one of the big players that you've worked with, Bose, and of course to work with Apple and many others.

Kevin Mako: but it's incredible for you to actually see this at the highest levels so that we can understand how to apply it today.

Kevin Mako: I want to start with innovation because that's a big one that you've worked

John Carter: with a number of these firms on. How do you do innovation great from what you've seen, both in the process and what those companies actually do to succeed?

John Carter: Yeah, there are a couple secrets. One of the things that I think is probably underplayed and really important is the amount of investment that it takes to innovate.

John Carter: Innovation is not free. And this myth of suddenly a great idea, occurs to someone and they scribble on a napkin and then raise $50 million to do, a new

John Carter: product idea is crazy. That just doesn't happen. Innovation takes sustained effort and a budget

John Carter: to really propel that forward over the many potholes you're going to uncover us if you work on the innovation process.

John Carter: So the first thing is you have to allocate some spending for it. And a rule of thumb I use is about 10% of your product development. You should put in the innovation category.

John Carter: in terms of investment.

John Carter: So, you know, one out of every $10 you really spend on those transformational ideas. The second thing that I think is really important when it comes to innovation is something

John Carter: that I learned early at Bose called adjacency. And that is when you're trying to innovate, don't try and innovate a new technology,

John Carter: a new market, new customers, new features, and a whole set of new challenges. But rather, what do you do well now?

John Carter: And if you were to change one variable to make a step change in your business, but just one variable, what should it be? Should you go after new distribution?

John Carter: Should you look at really a technology leapfrog? But in all cases, it should be adjacent to your expertise. So moving from

John Carter: one category to another where they're close but different is the best way to innovate. You can make

John Carter: bold steps by making small changes, but change just one dimension at a time. And I think your innovation are most likely going to be successful.

John Carter: And the last thing is, don't share it with customers too early. There's a real dilemma about understanding product market fit

John Carter: and is your product idea going to be successful. You first really need to invest time in thinking through the concept itself

John Carter: before you bring it forward to other people look at. This is especially true in new to the world categories.

John Carter: So those are three ideas that I would really recommend that people

Kevin Mako: pursue in terms of investment, adjacency, and deferring customer contact until you have a real idea of what you plan to do.

Kevin Mako: That's incredibly powerful. And those three, they're actually somewhat connected, especially the first two. I love the fact that you coined the concept of bringing it down

Kevin Mako: to your core competency slightly adjacent, not trying to innovate in every different category at once.

Kevin Mako: And this really comes down, especially to new hardware development, and something we see all the time,

Kevin Mako: which is feature creep, trying to be too many things to too many people. It could be featured on the product itself.

Kevin Mako: It could be innovations in the way you're selling it. It can be a new market entrance itself. If you're trying to do all of these innovations together, it's going to be incredibly

Kevin Mako: difficult for many reasons. But that also applies to your concept about the cost of innovation,

Kevin Mako: because the more complicated that you actually plan to develop this, if you're probably

Kevin Mako: to do all these different innovations simultaneously and not really focusing on doing your one core

Kevin Mako: innovation great, it's going to be very costly, probably prohibitively costly to the point where you

Kevin Mako: burn out before you actually get the core innovation that would have been so great, that small incremental difference. And that is what makes such a big deal.

Kevin Mako: I don't think a lot of people realize in hardware, especially, that you don't have to make a terribly ground-shaking new product idea to be a success.

Kevin Mako: You can be just a few percent better than what's out there. And it doesn't necessarily have to be cheaper.

Kevin Mako: It could be cheaper, better, faster, more innovative, more useful, less pain points, you name it.

John Carter: There's a whole laundry list of ways that you could argue that you're a few percent better. But all it takes is a small incremental.

John Carter: shift, and that really aligns back with those three key elements that you've talked about there. Yeah, Kevin, I'm so glad you bring up this whole concept of feature creep, because

John Carter: I think companies confuse agile with feature creep, and the whole idea, especially in

John Carter: hardware development, is do your homework up front and then execute fast and then get it to market

John Carter: and then iterate, but don't spend a lot of time creeping features in the beginning of the program,

John Carter: but actually put down an invention idea, execute on it, give it to the market, they'll tell you where to take those features next.

John Carter: But otherwise, you can just burn up enormous amounts of time

Kevin Mako: and money by not knowing really what you want to do. It's much more sensible to actually do two

Kevin Mako: product iterations than to have one very long, messy product iteration. Particularly powerful in hardware, where of course Agile has been, let's call it,

Kevin Mako: borrowed from the software world with this idea of continual development. Well, the difference between software and hardware is you can't bug fix a hardware piece.

Kevin Mako: Once it's manufactured, that is the thing and it's done. Arguably, in some electronics, yes, there's maybe a hybrid role,

Kevin Mako: but for the actual physical hardware components, there's no bug fix after that gets to market. But there is feedback.

Kevin Mako: That feedback can be used to then apply the concept of Agile to your next version. So you get a few units of, and we're a huge advocate of get even a few hundred units out to

Kevin Mako: the market, especially as a small company, learn from those, and then plan in your actual

Kevin Mako: development in your business case model to do another round, as you said, your second round of

Kevin Mako: innovation there based on real user feedback from people who bought the product and are now

John Carter: giving you real deep feedback into what they like and more importantly, what they don't like,

John Carter: which can really help you guide that, let's call it, the hardware revised agile process to be more in line with how reality works in the hardware innovation space.

John Carter: I'm glad we're talking about agile as it applies to hardware because there's so many misconceptions there and they're actually

John Carter: I think you've probably seen the same kind of errors that I've seen. First of all, if you look at the 12 principles of the Agile manifesto, turns out nine out of 12

John Carter: apply to hardware.

John Carter: It's only a few that don't. And one of them is, you know, you do work in two-week increments or a sprint and that's just

John Carter: not possible with tooling and CAD design and creating hardware projects that are successful. But if you

John Carter: look at all the other attributes of the Agile manifestos, such as getting early customer feedback or

John Carter: such as an empowered team, these apply absolutely to hardware. So I think there's a big myth about application of Agile.

Kevin Mako: It doesn't work for hardware. You're absolutely right. You can't fix it in the field. If you have a defect, you're going to ship a defect. So there's some fundamental differences,

Kevin Mako: but there are also some fundamental principles that you can apply to hardware development and move

Kevin Mako: quickly. Do you want to run through some of those principles that you find have really worked well,

John Carter: especially looking at these bigger levels, like looking at products that are successful on Amazon or Apple products or even the work at Bose?

John Carter: How do those things apply to startups or even scaling product brands that are looking to do that next innovation? That's a really good question.

John Carter: I think the first and foremost is to have empowered teams, you know, to really allow the team to succeed or fail on its own scale, I think, is incredible.

John Carter: And Agile really promotes having a dedicated, empowered, self -directive team. So that, to me, is number one.

John Carter: And then number two has to do with customer contact. Now, in Agile, what they recommend doing is frequent customer contact.

John Carter: In hardware, though, it may make more sense for you to rotate through the type of feedbacks that you get.

John Carter: For example, you may want to get some feedback from your distribution or sales channel or someone that's working as a rep for your firm.

John Carter: And then a little bit later on, you might go to a reviewer, third party that's really on top of the industry, but is not a direct consumer itself.

John Carter: Neither one of those two examples are direct consumers. And then as you evolve and iterate, then it's time to really try it with

John Carter: true customers, people that would potentially buy your product. So I think when you think about

John Carter: integrating customer feedback into your design and thinking about agile, you really need to think carefully about when and who do you expose the idea. is to get feedback from.

Kevin Mako: But getting feedback is really a super idea, but not too early. You need to have crystallized idea and have a clear value proposition.

Kevin Mako: So I think those are some fundamental principles from Agile for Software that I would recommend for every hardware inventor and entrepreneur.

Kevin Mako: I love the concept of empowerment. Just from a design firm angle, we definitely see a fairly

Kevin Mako: strong divide with certain clients that are extremely self-directed, even with very little experience in the field.

Kevin Mako: Whereas others want to learn and understand from some of the best designers in the country on what they've seen over the hundreds of products that they've worked with. And you

Kevin Mako: probably see that quite a bit in your industry as well, whereas you've got so much real, tangible experience, so many people miss the opportunity to simply ask the question,

Kevin Mako: what would you do here? Or they're actually creating processes or even just fundamentally misguiding the development plan to disrupt what could be incredible

Kevin Mako: design or incredible development or incredible advice from some really seasoned experts. And I see that time and

Kevin Mako: time again, I would actually say if I look at a client mix, probably half the clients are heavily, heavily underutilizing that simply as a thought

Kevin Mako: process to say, how can I lean on these experts and how can I rely on some of their experience as opposed to, you know, how can I take my whatever the idea might be and force it.

Kevin Mako: And that's where whether it's working with your design team, which is the perspective there, or whether it's working with your customers.

Kevin Mako: You really have to have a very open mind to your customers. And I see it hand in hand again,

Kevin Mako: probably again, half the clients, when they do get that customer feedback, the first thing that

Kevin Mako: they do, the very first piece of feedback we hear is, oh, this person has no idea what they're talking about. Well, that's a real customer.

Kevin Mako: And they've got real feedback for you. So yes, maybe it is the one outlier, but what ends up happening more often than less is you start to

Kevin Mako: see a pattern. But it takes so much time because the inventor, the designers, the engineers, whatever it might be are so heavily vested into that project.

John Carter: It takes a long time before they open up their mind. They become empathetic. They put themselves in the shoes of that customer and they say, okay, maybe they've said it wrong.

John Carter: Maybe I don't necessarily believe them. But why do they feel that way? Why did they choose those words? And how can we analyze those words to make a better

John Carter: product in the future. Right. So this really brings to mind a couple of examples that are close to heart. And that is in working on the noise cancelling headphones.

John Carter: When we were first inventing it, we thought it was the biggest benefit would be sound quality. You'd have better base, clear highs and the

John Carter: performance would be vastly improved. Well, we took it out to customers and we realized they didn't care about that. What they liked is noise reduction.

John Carter: They didn't care about the sound quality. I mean, they did, but that was in the first order of improvement. And we really listened to them and optimized it

John Carter: for noise cancellation as opposed to its original invention idea. So I think it's really important not to have solution lock.

John Carter: But another problem that I face depots and at other organizations, and it must be a huge problem for you, Kevin, is that every executive thinks they know

John Carter: industrial design. You know, they may not know mechanical engineering. They may not know CAD system, but every executive thinks they know industrial design, but the fact

John Carter: is they don't. And they need to be

Kevin Mako: open enough so that they can really collaborate with creative companies like yourself to really create something that's breakthrough or novel, just not me too.

Kevin Mako: And there are so many people who kind of play the part of industrial design, but on TV only. In reality, these executives need to

Kevin Mako: open up their mind and allow some experts to take some risks. Yeah, it's interesting. You mention that. That's one of those things, right?

Kevin Mako: Everybody feels that they'd be a great politician or a great movie actor potentially, right?

Kevin Mako: But the reality is there's a tremendous amount of skill, let's say most of the time as a caveat that goes into those roles. And industrial design is no different.

Kevin Mako: Keep in mind what an industrial designer does for their entire life, from schooling through to the CAD work that they're doing to all of the work that they're doing in terms of

Kevin Mako: the meetings, their entire job is figuring out what the user wants and what technology

Kevin Mako: is available and a number of other stakeholders like the business model and the manufacturing. costs and on and on. They are the intersection of all these key attributes.

Kevin Mako: Industrial design is basically the hub of your mechanical engineering, your electronic engineering. It has electronics. And of course,

Kevin Mako: all those other stakeholders that we talked about for and a bunch more. That's what they are doing all day every day.

Kevin Mako: So through that, they get a tremendous amount of experience over the years of doing this. I look at our head industrial designers at our firms are 20 plus years of doing this all

Kevin Mako: day every day of their working career. So although it may look like something that everyone can pick up and have great advice on.

Kevin Mako: These people are incredibly talented, not just at understanding what they want. This is an opinion thing, but understanding what various stakeholders want to lead to generally

Kevin Mako: the most successful commercial product for the market, meaning

John Carter: the customers love it. It's well-priced. It's manufactured of a quality grade, and it's scalable. And that is really the core of a good and experienced industrial designer.

John Carter: So I'm a huge advocate for that. And I really appreciate that you brought up. I think you're the first person to bring it up on the show, the sheer value of what

John Carter: specifically an industrial designer does in the overall product development process. I'll add another to your list, which I think is super important, and that is all innovations.

John Carter: We talked about innovations at the beginning of this conversation. All innovations really should do something

John Carter: better. And you're going to have to do something different in order to be better. Otherwise, it would just be me too.

John Carter: Well, who knows better than an industrial designer, how to express that innovation in the physical package.

John Carter: So when a consumer sees that, they actually can see a styling that's different that communicates that innovation so the product sells itself. And so I think

John Carter: that's a fifth element of what a resource like your team can do is you take the innovation

Kevin Mako: and then you express it in design so it telegraphs or signals to a consumer. This is different and it's better and you can see why.

John Carter: So I think that your ability to catalyze an amplify innovation through physical package design and industrial design and styling is something

John Carter: really important that most entrepreneurs should consider.

Kevin Mako: John, much appreciated. And the last thing I'll ask you for before we leave, is there any other words of wisdom, you know, either high level or in the

John Carter: weeds that you want to share before we say goodbye? I just think it comes back to sticking to your guns if you want to innovate.

John Carter: You have to invest and you have to show consistent focus. And you do that and you do adjacent work, you're going to be successful.

John Carter: John, thanks so much for coming on to the show today. Much appreciated and looking forward to talking to you again. Thanks, Kevin. Take care.

Narrator: Thanks for tuning in to this episode of the Product Startup Podcast, the show that teaches you what it really takes to bring your product to market

Narrator: and turn it into a big success. This podcast series is brought to you by Mako Design + Invent,

Narrator: the original and leading firm in North America to provide global caliber into in physical consumer product development to startups, inventors, and

Narrator: small product business clients. If you're looking for product development help on your invention, head over to MakoDesign.com.

Narrator: That's ma-k-o-design.com for a free consultation from one of Mako-designs for design studios from coast to coast.

Narrator: Thanks for listening and see you next time.

Improve Your Product Development Strategy

Turn a Promising Idea Into a Disciplined Development Plan

Great hardware development depends on clear priorities, staged decisions, and the right evidence at the right time. Product Startup can help you map the journey and avoid expensive strategic mistakes.

Work directly with Kevin Mako, the leading expert in hardware startup consulting, on product requirements, development planning, validation, vendor coordination, commercialization, and the business choices around technical work.

Strengthen My Development Plan

A focused strategy call on how strong hardware teams develop better products, tailored to your product, stage, and commercial goals.